From: [email protected]

Package: pcmcia-cs
Version: 3.2.5-8

My ethernet card is fully recognized, but "/etc/pcmcia/network start eth0"
does not get called. If I call it manually, everything works. I use network.opts such that ifup eth0 is called when this is done.

The PCMCIA ethernet card in question is branded as "Netgear 32bit Notebook Adapter 10/100 Mps Fast Ethernet FA511".

When comparing it to my old card (with which the setup perfectly works), I found out, that the info given by cardctl has missing information. Right
now, I unfortunately cannot find out again how I came to that conclusion (it was a couple of months ago and wanted to wait until I found fix, I shouldn't have waited :( )

Here is the output of "cardctl ident":

Socket 0:
no product info available
Socket 1:
no product info available

"cardctl status":

Socket 0:
no card
Socket 1:
3.3V CardBus card
function 0: [ready]

Thus grep_stab() and get_info() in /etc/pcmica/shared will fail.

The related dmesg output looks perfectly normal to me:

Linux Kernel Card Services
options: [pci] [cardbus] [pm]
PCI: IRQ 0 for device 0000:00:0a.0 doesn't match PIRQ mask - try pci=usepirqmask
PCI: Assigned IRQ 5 for device 0000:00:0a.0
PCI: Sharing IRQ 5 with 0000:00:0a.1
Yenta: CardBus bridge found at 0000:00:0a.0 [0000:0000]
Yenta: ISA IRQ mask 0x0498, PCI irq 5
Socket status: 30000007
PCI: Found IRQ 5 for device 0000:00:0a.1
PCI: Sharing IRQ 5 with 0000:00:0a.0
Yenta: CardBus bridge found at 0000:00:0a.1 [0000:0000]
Yenta: ISA IRQ mask 0x0498, PCI irq 5
Socket status: 30000821
Linux Tulip driver version 1.1.13 (May 11, 2002)
PCI: Enabling device 0000:06:00.0 (0000 -> 0003)
PCI: Setting latency timer of device 0000:06:00.0 to 64
tulip0: MII transceiver #1 config 3100 status 7849 advertising 05e1.
eth0: ADMtek Comet rev 17 at 0x4800, 00:09:5B:60:92:89, IRQ 5.
[...]
eth0: Setting full-duplex based on MII#1 link partner capability of 45e1.
eth0: no IPv6 routers present

The problem persisted as long as I have the card (> 8 months), thus it's nothing related to new kernels or software versions.

I am using one of the pre-packaged kernels:
Linux XXX 2.6.7-1-686 #1 Thu Jul 8 05:36:53 EDT 2004 i686 GNU/Linux
Source: kernel-image-2.6.7-i386
Version: 2.6.7-2

So this is probably an issue with the tulip driver. I would gladly
incooperate any workaround -- I am just tired of always manually starting
the network device. If you need any further information, please do not hestitate to contact me. Thanks for your work.

Best regards,
Peter Kolloch

--
NEU: Bis zu 10 GB Speicher f�r e-mails & Dateien!
1 GB bereits bei GMX FreeMail http://www.gmx.net/de/go/mail



--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)