/proc/bus/usb#...empty, after upgrade to 2.6.10
 

Hi group.
Well, I took the leap, and installed, and theN compiled kernel 2.6.10 from the Slack 10.1 disk set. So far so gOod, but I suspect there is a lot to learn that is new. I do want to exploit Direct I/O. Anyway, am pleased to be state of the art, and want to thank the many participants in this Forum.
I have one question. Previously, In the directory /PROC/BUS/USB there used to be some entries (just as there are in /PROC/BUS/PCI, which is kind of what is printed with "lspci" command). The sister "lsusb" command displays nothing for me, perhaps because that directory is empty. Unless this is a new feature (which I doubt) I suspect I missed something along the lines of configuring USB or PROC virtual filesystem in my make menuconfig. Is that up the right track? If so, can someone pls tell me the name of the parameter I missed? I just can't find it, looking through my .config in /USR/SRC/LINUX (It's also 3:30am, and the eyes are weak...)
Thanks
wombat53

Search in the .config file for "# USB support" without the "", down that line comes all USB related stuff.

If you're using menuconfig, take a look at: Device Drivers -> USB support (it's at the end of the menu).

Guillrmo
Thanks for the speedy reply! It's easy to miss things in the wee hours of the nmorning...
George

Guillermo - the parms seem ok on my .config file..USB support, and the PROC pseudo file system
Are you on 2.6? Do you have lsusb and /proc/bus/usb working correctly?
There are ceratinly changes...a new "input" directory, and a new /proc/sys/...directory...
George

Yes, I'm using 2.6.6 kernel on this machine and usb stuff seems to be ok. I don't have any USB device plugged right now, but lsusb and /proc/bus/usb shows the USB controllers.

Guillermo
This is what I did. First, the correct parms were set (so I believe): CONFIG_USB=yes and CONFIG_PROC_FS=yes.
Out of desperation, what I did was to convert several USB parms from modules , to kernel.
These were:
CONFIG_USB_UHCI_HCD
CONFIG_USB_PRINTER (I have USB cable to printer, not parallel), and finally,
CONFIG_USB_HID (I have a Logitech Kbd with USB only connector)

So, basically I replaced module suppot with kernel support, and got back the /PROC/BUS/USB support (as well as lsusb). I do not know if this is the way it is supposed to work, but that is what I found.

I guess this raises the question, what can be a module and what cannot (apart from the obvious, like ext2 support, etc.)
wombat53