2.4.3-ac3 XIRCOM_CB only working as module

It looks like the new xircom_cb driver only works as module - if built
in kernel there is no sign of eth0 setup.

--alessandro <[email protected]> <[email protected]>

Linux:  kernel 2.2.19/2.4.3-ac3 glibc-2.2 gcc-2.96-69 binutils-2.11.90.0.4
Oracle: Oracle8i 8.1.7.0.1 Enterprise Edition for Linux
motto:  Tell the truth, there's less to remember.

Built as a module works beutifully :) No need to "ifconfig -promisc" to make it work after a suspend.

Anyway, you still have to unload the card and reload it again to get back the network working. I'm using hotplug.

Pau

I haven't tried this; I'll look into this once I get back to work (eg where my cardbus machine is). I would not be surprised if it
turns out to be of the "yenta_socket is not initialized yet, so the card is invisible at pci scan time" type....

Greetings,
Arjan van de Ven

I have built this as a module due to the RedHat system I use (to be consistent). I found that the xircom_cb driver works fine as a module except for when using dhcp for dynamic ip address. If I set the ip address of the network card to a static ip number it work fine. Yet if I choose to use the dhcp to get my ip address packets leave, as seen via tcpdump, but it doesn't get an address. I watched tcpdump at the dhcp server and saw the packets come in from the laptop and the responses go out. The laptop either is ignoring the message coming from the dhcp server or some other bizarre reason.

I cannot say if I noticed anything about the yenta_socket driver. If I could get dhcp to work fine I would be willing to give it a go.

Stephen
[email protected]

-----------------------------------------------
Buyer's Guide for a Operating System:
Don't care to know: Mac
Don't mind knowing but not too much: Windows
Hit me! I can take it!: Linux