Wow. I admit that I was suspicious of that ls output, but I tried it anyway... I got the same YUKKY output from ls -l /proc/bus/usb when I insmod 2.3.99-pre7-8 modules on kernel 2.3.99-pre7-6 (shouldn't DO that), but when I insmod 2.3.99-pre7-6 modules on the same kernel, I see 001/, devices, and drivers as expected. Based on my experience of not being able to boot pre7-8 after building it this morning (looks like proc-fs problems), I suspected some incorrect proc code in the backport, but the backport is pre7-1, and I haven't seen or heard of this problem earlier. Other ideas? ~Randy > -----Original Message----- > From: Ron Gage [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, May 09, 2000 3:28 PM > To: [EMAIL PROTECTED] > Subject: Re: [linux-usb] RE: [linux-usb-devel] USB Usage problems > > > Brad: > > On Wed, 10 May 2000, you wrote: > > Ron Gage wrote: > > > I can tell you that /proc/bus/usb is empty when the > Linksys is empty. As for > > > extracting out the exact messages, I'll have to dial-up > with that machine and > > > send them seperately. It'll be a few minutes before I > can get that set-up. > > This is symptomatic of not mounting the usbdevfs. Try: > > mount -t usbdevfs flamewar /proc/bus/usb > > > > and send the contents of /proc/bus/usb/devices and > /proc/bus/usb/drivers > > OK, did it. > > Reported that devices, drivers, 001, and 002 "no such file or > directory". > > This was from an 'ls' command from /usr/bus/usb. > > -- > Ron Gage - Saginaw, MI > ([EMAIL PROTECTED]) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
