I've tried re-compiling the same kernel and different kernels with different configurations in order to get my PCMCIA LinkSys EtherFast NIC to auto-configure the IP address when I boot (my pc detects a PCMCIA card but doesn't set up the IP address). This has not worked. A PCMCIA card site says that there are two types of LinkSys EtherFast cards and says that the one type needs tulip drivers.

If I follow their advice to compile a module, could I break my pc or NIC card with the module? I'm using kernel 2.4.29 compiled so that PCMCIA cards are detected.

This is what the http://www.linksys.com/support/support.asp?spid=26 site says:

EtherFast 10/100 CardBus PC Card
The following must be done as root.

All of the setup instructions are contained in your Linux package. When you unpack your archive, look for a "how-to" document concerning the installation of PCMCIA cards. When you find the file, read it and follow the directions. You'll need to install the PCMCIA services, enable networking, recompile the kernel if needed.

Recently the controller chip used on our card has had a rev change. The old version was a DEC 21143 TC the new version is a DEC 21143 TD. Some compatability issues with the Tulip driver have been noted and are currently undergoing developement and testing to include the new chip changes. We will provide a link the the driver as soon as it is available.

You must add the following to /etc/pcmcia/config: device "tulip_cb"
class "network" module "cb_enabler", "tulip_cb"

card "Linksys EtherFast 10/100 CardBus PC Card"
manfid 0x0149, 0xc2ab
bind "tulip_cb"

You must obtain the latest tulip.c driver from Donald Becker. This is a special version for PCMCIA cards.

Compile tulip.c with this command:

gcc -DMODULE -D__KERNEL__ -I/usr/src/linux/net/inet
-Wall -Wstrict-prototypes -O6 -c tulip.c -o tulip_cb.o
`[ -f /usr/include/linux/modversions.h ] && echo -DMODVERSIONS`
-DCARDBUS

After this is complete, copy tulip_cb.o to /lib/modules/< kernel.version >/pcmcia.
Issue a kill -HUP < cardmgr pid >, or if you are using redhat issue /etc/rc.d/init.d/pcmcia stop, then start or just reboot the computer.

After this point, the PC Card will be automatically recognized as soon as you plug it in. You must have version 3.0.5 of the Linux PCMCIA services or higher to support CardBus. You can ftp the latest version here

I would think you can trust the tulip developper, tulip module has been in the kernel source
from a long time. It would be well known if that module breaks computer or net cards

Look in the /etc/pcmcia/config file and find the line that lists the exact name your card reports. See what driver it has a bind for. Try editing that line and replace the driver listed with the other option i.e. tulip or whatever the name of the other driver is and try that.

I use a Linksys NP100 Network Everywhere and it reports as "Linksys Network Everywhere NP100"
that listing in pcmcia/config bind it to the pcnet driver when in fact it requires the axnet driver. A simple edit solves the problem and the card works great.

Well, I didn't break anything. Unfortunately that tulip driver didn't work though. Thanx mason for pointing out that it already exists on my harddrive.

Mason, what lines did you add to your pcmcia/config and how did you see that it reports as "Linksys Network Everywhere NP100"?

I don't think I have a reference to any LinkSys hardware. The only network hardware I see is pcnet_cs in the modules:

For me lsmod shows:

Module Size Used by Not tainted
snd-pcm-oss 37224 0 (autoclean)
snd-mixer-oss 12248 0 (autoclean) [snd-pcm-oss]
snd-es1938 11240 0 (autoclean)
gameport 1404 0 (autoclean) [snd-es1938]
snd-pcm 55944 0 (autoclean) [snd-pcm-oss snd-es1938]
snd-page-alloc 5912 0 (autoclean) [snd-pcm]
snd-opl3-lib 5700 0 (autoclean) [snd-es1938]
snd-hwdep 4260 0 (autoclean) [snd-opl3-lib]
snd-timer 13412 0 (autoclean) [snd-pcm snd-opl3-lib]
snd-mpu401-uart 3200 0 (autoclean) [snd-es1938]
snd-rawmidi 12260 0 (autoclean) [snd-mpu401-uart]
snd-seq-device 3680 0 (autoclean) [snd-opl3-lib snd-rawmidi]
snd 30340 0 (autoclean) [snd-pcm-oss snd-mixer-oss snd-es1 938 snd-pcm snd-opl3-lib snd-hwdep snd-timer snd-mpu401-uart snd-rawmidi snd-seq -device]
apm 9712 1
soundcore 3396 6 (autoclean) [snd]
usb-ohci 19368 0 (unused)
usbcore 58828 1 [usb-ohci]
pcnet_cs 11260 1
8390 5776 0 [pcnet_cs]
crc32 2880 0 [8390]
ds 6548 1 [pcnet_cs]
yenta_socket 10436 1
pcmcia_core 39140 0 [pcnet_cs ds yenta_socket]
ide-scsi 9392 0
agpgart 45092 0 (unused)

And lspci shows:

00:00.0 Host bridge: ALi Corporation M1541 (rev 04)
00:01.0 PCI bridge: ALi Corporation M1541 PCI to AGP Controller (rev 04)
00:07.0 ISA bridge: ALi Corporation M1533 PCI to ISA Bridge [Aladdin IV] (rev 0a)
00:09.0 Multimedia audio controller: ESS Technology ES1969 Solo-1 Audiodrive (rev 02)
00:0a.0 CardBus bridge: Texas Instruments PCI1211
00:0f.0 Communication controller: Lucent Microelectronics 56k WinModem (rev 01)
00:10.0 IDE interface: ALi Corporation M5229 IDE (rev 20)
00:11.0 Bridge: ALi Corporation M7101 PMU (rev 09)
00:14.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage LT Pro AGP-133 (rev dc)

To be honest. I'm not sure how to get the exact reported name in Slack. I used an automated tool in mepis to get that info a while back. (I keep a mepis livecd around for emergenies)

dmesg should show the chipset of your device. From there, since you know what your device is, scroll through the /etc/pcmcia/config file until you find the listing for your card. Look at the drivers listed "bind *driver*"
If the driver doesn't match your chipset, edit it out and edit in the correct driver.
No need to add any lines, just edit the existing one for your card to reflect the correct driver bind.

It looks like I edited etc/pcmcia/config right. I did a search for LinkSys and picked:

card "Linksys EtherFast 10/100 Fast Ethernet"
version "Linksys", "EtherFast 10/100 Integrated PC Card (PCM100)"
#manfid 0x0149, 0xc1ab
bind "pcnet_cs"

All the LinkSys cards use pcnet_cs. I changed it to what that web page above recommended:

manfid 0x0149, 0xc2ab
bind "tulip_cb"

That didn't work on boot, so I commented out the manfid line with no difference. When it boots and detects a PCMCIA card, there are 2 beeps that have always been the same (that's a good think I take it?). Now the 2 beep tones are different and a MAC address isn't assigned.

I changed it back to bind "pcnet_cs". The beep tones are the same, a MAC address is assigned, but the IP address is still only idassigned if I turn the modem on between the PCMCIA card recognition beeps...and it only works half the time.

Did I do something wrong?

OK, sounds like you have the correct driver.
Before shutting down, remove the card and look in /etc/dhcpc.
If the files eth0.cache and eth0.info are present, delete them.

I've noticed that for some reason dhcpcd doesn't delete these files on shutdown and a new lease isn't issued. If you delete these files and then restart your machine or pcmcia, it works. Don't know why, but seems to be a bug in shutdown.

What I do is, after I start up, I remove the card, delete those two files, and then put card back in. Seems to work.

If you see a eth0.pid file in there when card is removed. definately delete that one as well. Don't remove eth0.exe or dhcpcd won't work.

You could write yourself a small script to delete the files for you to make it a little quicker and easier.

Wow-you were right, mason. I pulled the card, renamed the files you mentioned and then re-started with the card back in and the modem on. I got right on...without the hoping and having to turn the modem on when the PCMCIA card is recognized.

Looks like I'll write a small script to delete these files when I shutdown. Do you know if I can delete these files while I'm online? How would I shut down my eth0 connection if I need to that first?

ok, the files delete without shutting down ifconfig eth0. Here's the script I wrote:

cd /etc/dhcpc
mv -f dhcpcd-eth0.cache dhcpcd-eth0.cache.bak
mv -f dhcpcd-eth0.info dhcpcd-eth0.info.bak
mv -f dhcpcd-eth0.pid dhcpcd-eth0.pid.bak

Now I just need to figure out how to make a script auto-execute when I log out (I tried putting it in /etc/rc.d/rc.6 and it didn't work right).

Thanks for all the help!

Upon further tinkering with this problem, I've narrowed it down to just one file that needs to be deleted. It's the eth0.cache file. Delete that one file and your NIC will restart properly. No need to make a backup as dhcpcd will write a new one when it starts the card.

By the way, I did discover how to get the exact reported card name, just for future reference. If you have KDE, open the Info Center and look at the PCMCIA listing. It will give the exact reported name of the card.


*edit* I added the line 'rm /etc/dhcpc/dhcpcd-eth0.cache' to the /etc/rc.d/rc.6 script and that fixed the problem. I placed it just below the line to kill the dhcpcd.