> You don't mention which kernel version you are using, what one are you
> using?
2.4.18.
I tried the suggestion in this thread:
http://marc.theaimsgroup.com/?l=linux-kernel&m=100912381726661&w=2
It made no difference. I also looked through the messages on
linux-usb-devel, but they seem to be more related to having USB floppies
or USB hard drives recognized, instead of network cards, which I believe
is my problem. The kernel decides that there aren't any network devices,
so it doesn't do IP autoconfiguration, which is how it does NFS root in my
case.
In the output while booting, after it says:
Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Insert root floppy and press ENTER
hub.c: USB new device connect on bus2/1, assigned device number 2
pegasus.c: eth0: D-Link DSB-650
There is no perceptible delay between these messages, so it seems like the
code to detect the USB devices executes after the IP autoconfig section,
which is what is preventing this from working.
Is this a topic that should be discussed on one of the linux-usb lists
instead of linux-kernel?
Thanks.
On Fri, 15 Mar 2002, Greg KH wrote:
> On Thu, Mar 14, 2002 at 08:29:54PM -0600, rob1@rekl.yi.org wrote:
> >
> > Is there any way to get the USB network device recognized before IP
> > autoconfig is executed?
>
> You don't mention which kernel version you are using, what one are you
> using?
>
> You might try the patches mentioned in this thread:
> http://marc.theaimsgroup.com/?l=linux-usb-devel&m=101501210231463
> as it seems that the problem is your device is not seen by the USB
> subsystem before the network code starts up.
>
> greg k-h
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Mar 23 2002 - 22:00:12 EST