From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020314
Description of problem:
When I insert the xircom_cm pcmcia card, the module seems to be
properly loaded by the pcmcia services, but hotplug seems to
fail to notice this, and fails to start the network.
If I type "ifup eth0", network starts right up.
Here is the end of my messages file:
Mar 28 15:47:25 libra kernel: cs: cb_alloc(bus 2): vendor 0x115d, device 0x0003
Mar 28 15:47:25 libra kernel: PCI: Enabling device 02:00.0 (0000 -> 0003)
Mar 28 15:47:25 libra kernel: PCI: Setting latency timer of device 02:00.0 to
64Mar 28 15:47:25 libra kernel: eth0: Xircom cardbus revision 3 at irq 11
Mar 28 15:47:25 libra kernel: PCI: Enabling device 02:00.1 (0000 -> 0003)
Mar 28 15:47:25 libra /etc/hotplug/net.agent: invoke ifup eth0
Mar 28 15:47:25 libra kernel: ttyS04 at port 0x4080 (irq = 11) is a 16550A
Mar 28 15:47:25 libra cardmgr: initializing socket 0
Mar 28 15:47:25 libra cardmgr: socket 0: Xircom CBEM56G-100 CardBus 10/100
Ethernet + 56K Modem
Mar 28 15:47:25 libra /etc/hotplug/pci.agent: Setup xircom_cb for PCI slot 02:00.0
Mar 28 15:47:25 libra /etc/hotplug/pci.agent: missing kernel or user mode driver
Mar 28 15:47:25 libra /etc/hotplug/pci.agent: ... no modules for PCI slot 02:00.1
The module is properly loaded, and works fine. Seems
to be a problem with the hotplug recognition of the loaded
module. I tried to track it down, but had no luck.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Uplug the Xircom card
2. Replug the Xircom card. Card is recognized properly every time
but ifup command doesn't get done.
Expected Results: The network should be up after I plug in the card, without
needing to type ifup eth0.
Likely related problem with a linksys 10/100 NE2000 clone.
Log shows hotplug/net.agent trying the "ifup eth0",
but nothing results from that. In my case, nothing like the
above messages from pci.agent. Just nothing at all after
the ".../net/agent: invoke ifup eth0".
All works fine if I manually do "ifup eth0", which is what
makes me think it is related.
Duplicate of bug #61705.
*** This bug has been marked as a duplicate of 61705 ***