Please mention the messages you're seeing. Do the
various drivers ID themselves on the console or in
a log file as they're starting up? Did you see the
appropriate driver announce itself?
The code in dev_ifsioc() in net/core/dev.c is what's
ultimately executed as part of the ioctl that's
supposed to accomplish the SIOCGIFFLAGS action.
It shows that, as long as some driver has managed to
register itself as handling the device in question,
the call pretty much cannot fail, and when nobody
has registered it returns ENODEV.
Since that's consistent with what you're seeing it's
reasonable to wonder if you either failed to include
the proper driver in your kernel or it couldn't find
the NIC. If the latter you may have to give it a clue
about where to look by supplying parameters on the
kernel commandline, like I have to do in my lilo.conf
in order that my NICs get recognized properly:
append="ether=5,0x9400,eth1 ether=9,0x9000,eth0"
That line is only an example and is guaranteed to be
wrong for your machine. You said: "the BIOS finds,
identifies and allocates resources for my 2nd network
card", so may be able to divine the proper values
by looking at your BIOS startup messages, which may
announce which addresses and interrupts the NICs
are rigged to use.
*****************************************************************
To unsubscribe from this list, send mail to [EMAIL PROTECTED]
with the text 'unsubscribe gnhlug' in the message body.
*****************************************************************
