trinux-talk

[Trinux-talk] Re: Trinux pcmcia -smc

[Matthew F. <mf...@ci...>]

> > I am trying to configure it to support my SMC 8041 PCMCIA, and I followed these directions, per SMC:
> > 
> >        If the file /etc/pcmcia/config exists,add following
> >        lines in this file:
> > 
> >        card "SMC 10/100 PC Card"
> >        version "SMC", "8041TX-10/100-PC-Card"
> >        bind "pcnet_cs"
> > 
> > The problem is, savecfg doesn't save /etc/pcmcia/, so the changes are lost when I reboot.  I've tried to edit the file (via nano) on another box, but Trinux doesn't like the resulting .tgz.  I could restart it manually, what's the Trinux equivalent of "/etc/init.d/pcmcia restart"?
> > 
> 
 1) As you can see--/etc/init.d/pcmcia is pretty stupid. If you want to
 restart pcmcia, killall cardmgr and then run cardmgr
 
 #/etc/init.d/pcmcia
 echo "Starting PCMCIA card services"
 insmod pcmcia_core
 insmod i82365
 insmod ds
 echo "Waiting for kernel modules to settle..."
 sleep 4
 echo "Starting cardmgr...."
 cardmgr
 echo "Waiting some more...."
 sleep 3
 echo "Attempting to configure network..."
 netcfg
 
 You'll also need http://trinux.sf.net/pkg/2.4.5/pcmcia-pcnet.tgz
 
 2) I updated the /etc/pcmcia/config file in the pcmcia-bin.tgz package
 available withint http://trinux.sf.net/pkg/
 
 3) The ability to override files (especially config files) within a
 tarball is something I'm thinking about and your question is a good
 example why. Basically what I'm planning is a "virtual" etc directory on
 the boot device (/tux/config/vetc) that would contain config files that
 would overwrite what is inside the tarball.
 
 - mdf

[Trinux-talk] Re: Trinux pcmcia -smc

[Matthew F. <mf...@ci...>]

Yep. the 8390.o was missing. I've built the modules for 2.4.19 and will
release a floppy that should work and a bootable CD-ROM with working
PCMCIA tonight. :)

- mdf


> Thanks for the prompt reply. I see your change, but now I get these error
> messages:
> 
> cardmgr[187]: watching 2 sockets
> cardmgr[187]: initializing socket 1
> cardmgr[187]: socket 1 : SMC 10/100 PC Card
> cardmgr[187]: module/lib/modules/2.4.5/net/8390.o not available
> cardmgr[187]: executing: 'modprobe 8390'
> cardmgr[187]: modprobe exited with status 2
> cardmgr[187]: executing: 'insmod/lib/modules/2.4.5/pcmcia/pcnet_cs.o'
> ....followed by a "Resource temporarily unavailable"
> 
> Art
> 
> ----- Original Message -----
> From: "Matthew Franz" <mf...@ci...>
> To: "Arthur Davis" <art...@ie...>
> Cc: <tri...@ci...>
> Sent: Thursday, September 05, 2002 12:16 PM
> Subject: Re: Trinux pcmcia -smc
> 
> 
> > > I am trying to configure it to support my SMC 8041 PCMCIA, and I
> followed these directions, per SMC:
> > >
> > >        If the file /etc/pcmcia/config exists,add following
> > >        lines in this file:
> > >
> > >        card "SMC 10/100 PC Card"
> > >        version "SMC", "8041TX-10/100-PC-Card"
> > >        bind "pcnet_cs"
> > >
> > > The problem is, savecfg doesn't save /etc/pcmcia/, so the changes are
> lost when I reboot.  I've tried to edit the file (via nano) on another box,
> but Trinux doesn't like the resulting .tgz.  I could restart it manually,
> what's the Trinux equivalent of "/etc/init.d/pcmcia restart"?
> > >
> >
> > 1) As you can see--/etc/init.d/pcmcia is pretty stupid. If you want to
> > restart pcmcia, killall cardmgr and then run cardmgr
> >
> > #/etc/init.d/pcmcia
> > echo "Starting PCMCIA card services"
> > insmod pcmcia_core
> > insmod i82365
> > insmod ds
> > echo "Waiting for kernel modules to settle..."
> > sleep 4
> > echo "Starting cardmgr...."
> > cardmgr
> > echo "Waiting some more...."
> > sleep 3
> > echo "Attempting to configure network..."
> > netcfg
> >
> > You'll also need http://trinux.sf.net/pkg/2.4.5/pcmcia-pcnet.tgz
> >
> > 2) I updated the /etc/pcmcia/config file in the pcmcia-bin.tgz package
> > available withint http://trinux.sf.net/pkg/
> >
> > 3) The ability to override files (especially config files) within a
> > tarball is something I'm thinking about and your question is a good
> > example why. Basically what I'm planning is a "virtual" etc directory on
> > the boot device (/tux/config/vetc) that would contain config files that
> > would overwrite what is inside the tarball.
> >
> > - mdf
> >
> 
> 
> 

-- 
Matthew Franz                 mf...@ci...
Critical Infrastructure Assurance Group (CIAG)
Cisco Systems, Inc.                 Austin, TX

[Trinux-talk] Re: Trinux pcmcia -smc

[Arthur D. <art...@ie...>]

The 8390.o error is gone with the new iso, now the error is:
modprobe: can't open dependencies file
lib/2.4.19/modules.dep



> Yep. the 8390.o was missing. I've built the modules for 2.4.19 and will
> release a floppy that should work and a bootable CD-ROM with working
> PCMCIA tonight. :)
>
> - mdf
>
>
> > Thanks for the prompt reply. I see your change, but now I get these
error
> > messages:
> >
> > cardmgr[187]: watching 2 sockets
> > cardmgr[187]: initializing socket 1
> > cardmgr[187]: socket 1 : SMC 10/100 PC Card
> > cardmgr[187]: module/lib/modules/2.4.5/net/8390.o not available
> > cardmgr[187]: executing: 'modprobe 8390'
> > cardmgr[187]: modprobe exited with status 2
> > cardmgr[187]: executing: 'insmod/lib/modules/2.4.5/pcmcia/pcnet_cs.o'
> > ....followed by a "Resource temporarily unavailable"
> >

Re: [Trinux-talk] Re: Trinux pcmcia -smc

[Matthew F. <mf...@ci...>]

Hmmm... And this matters?

Try touch /lib/2.4.19/modules.dep and then either re-insert the card or
kill cardmgr and restart.

I don't think I have depmod in the distro.

What does lsmod show?

- mdf

> The 8390.o error is gone with the new iso, now the error is:
> modprobe: can't open dependencies file
> lib/2.4.19/modules.dep
> 
> 
> 
> > Yep. the 8390.o was missing. I've built the modules for 2.4.19 and will
> > release a floppy that should work and a bootable CD-ROM with working
> > PCMCIA tonight. :)
> >
> > - mdf
> >
> >
> > > Thanks for the prompt reply. I see your change, but now I get these
> error
> > > messages:
> > >
> > > cardmgr[187]: watching 2 sockets
> > > cardmgr[187]: initializing socket 1
> > > cardmgr[187]: socket 1 : SMC 10/100 PC Card
> > > cardmgr[187]: module/lib/modules/2.4.5/net/8390.o not available
> > > cardmgr[187]: executing: 'modprobe 8390'
> > > cardmgr[187]: modprobe exited with status 2
> > > cardmgr[187]: executing: 'insmod/lib/modules/2.4.5/pcmcia/pcnet_cs.o'
> > > ....followed by a "Resource temporarily unavailable"
> > >
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old
> cell phone?  Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> _______________________________________________
> Trinux-talk mailing list
> Tri...@li...
> https://lists.sourceforge.net/lists/listinfo/trinux-talk

-- 
Matthew Franz                 mf...@ci...
Critical Infrastructure Assurance Group (CIAG)
Cisco Systems, Inc.                 Austin, TX

[Trinux-talk] 3c59x/vortex driver not seen as eth0

[Matt S. <ma...@ma...>]

This may be a known issue, but I couldn't find a workaround...

My laptop has a minipci 3c59x (vortex driver) ethernet adapter in it.  Not
PCMCIA.  During boot, it is detected and installed as eth0, but it is not
advertised as eth0 in the dmesg output.  As a result, the netcfg script
doesn't "see" it when it parses dmesg and it doesn't initialize the
interface.

Can anyone suggest a workaround?

Thanks.


--Matt

Re: [Trinux-talk] 3c59x/vortex driver not seen as eth0

[P60 <akd...@ka...>]

Hi,

I am using the vortex driver for my NIC and it works well.
But your problem reminds me to an issue I once had with another card
(3c509). At that time I had an IRQ-conflict (graphics-card and NIC shared an
IRQ).
NIC was detected during boot but NOT activated by trinux.
The simple solution was to reconfigure the NIC to work with another
IRQ-number.

Perhaps this helps.
Arne

Subject: [Trinux-talk] 3c59x/vortex driver not seen as eth0


> This may be a known issue, but I couldn't find a workaround...
>
> My laptop has a minipci 3c59x (vortex driver) ethernet adapter in it.  Not
> PCMCIA.  During boot, it is detected and installed as eth0, but it is not
> advertised as eth0 in the dmesg output.  As a result, the netcfg script
> doesn't "see" it when it parses dmesg and it doesn't initialize the
> interface.
>
> Can anyone suggest a workaround?
>
> Thanks.
>
>
> --Matt