Slack 9.2 USB 2.0 Woes

olias · 10-26-2003, 08:53 AM

I installed slack for the first time last night and it wasn't to difficult. Problem is that my nForce2 board hangs at boot if I connect any type of USB device. I'm using an old PS2 mouse for now.

I did a dmesg | grep -i 'usb' and here's what I got...

Code:

usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
ehci_hcd 00:02.2: nVidia Corporation nForce2 USB Controller
usb.c: new USB bus registered, assigned bus number 1
ehci_hcd 00:02.2: USB 2.0 enabled, EHCI 1.00, driver 2003-Jun-19/2.4
hub.c: USB hub found
usb-ohci.c: USB OHCI at membase 0xe0c3b000, IRQ 10
usb-ohci.c: usb-00:02.0, nVidia Corporation nForce2 USB Controller
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
usb-ohci.c: USB OHCI at membase 0xe0c3d000, IRQ 9
usb-ohci.c: usb-00:02.1, nVidia Corporation nForce2 USB Controller (#2)
usb.c: new USB bus registered, assigned bus number 3
hub.c: USB hub found
uhci.c: USB Universal Host Controller Interface driver v1.1
usb-uhci.c: $Revision: 1.275 $ time 18:40:47 Sep  2 2003
usb-uhci.c: High bandwidth mode enabled
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver

Then I plug my 2 USB devices in and then I get this...

Code:

usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
ehci_hcd 00:02.2: nVidia Corporation nForce2 USB Controller
usb.c: new USB bus registered, assigned bus number 1
ehci_hcd 00:02.2: USB 2.0 enabled, EHCI 1.00, driver 2003-Jun-19/2.4
hub.c: USB hub found
usb-ohci.c: USB OHCI at membase 0xe0c3b000, IRQ 10
usb-ohci.c: usb-00:02.0, nVidia Corporation nForce2 USB Controller
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
usb-ohci.c: USB OHCI at membase 0xe0c3d000, IRQ 9
usb-ohci.c: usb-00:02.1, nVidia Corporation nForce2 USB Controller (#2)
usb.c: new USB bus registered, assigned bus number 3
hub.c: USB hub found
uhci.c: USB Universal Host Controller Interface driver v1.1
usb-uhci.c: $Revision: 1.275 $ time 18:40:47 Sep  2 2003
usb-uhci.c: High bandwidth mode enabled
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
hub.c: new USB device 00:02.0-2, assigned address 2
usb.c: USB device 2 (vend/prod 0x46d/0xc501) is not claimed by any active driver.
hub.c: new USB device 00:02.0-1, assigned address 3
usb.c: USB device 3 (vend/prod 0x51d/0x2) is not claimed by any active driver.
usb.c: registered new driver usbmouse
input0: Logitech USB Receiver on usb2:2.0
usbmouse.c: v1.6:USB HID Boot Protocol mouse driver
usb.c: registered new driver hiddev
usb.c: registered new driver hid
hiddev0: USB HID v1.00 Device [American Power Conversion Back-UPS 350 FW: 5.5.D USB FW: c1 ] on usb2:3.0
hid-core.c: USB HID support drivers

Looks like they are both there... My board is a Soltek NV-400-L64. Any clues would be great.

Thanks, olias

olias · 10-26-2003, 12:53 PM

oops, I ment to say Slack 9.1 and it appears to be the gpm service that hangs when I remove the PS2 mouse. How do I remove this from the start-up?

thanks, olias

Wonderer · 10-27-2003, 04:17 AM

I had the same problems and could not get it working.

USB keyboard & mouse problem in Slackware 9.1

Simple question: Has anyone been able to boot Slack 9.1 Instal. CD with HID USB k&m?

Going backward to go forward

BTW, forget about passing 'nousb' suggestions as it does not work.

Post at alt.os.linux.slackware

Slack 9.1, RTFM and bare.i nousb

Quote:

this means that if usb detection causes problems, i.e. if a usb device is
detected that isn't there, or something is detected incorrectly, and this
keeps bare.i from booting successfully, then you can skip usb detection by
passing nousb. but this is not your problem.

the second remark is:

> In the event that the keyboard
> doesn't work right away when the install CD is booted, wait. It will
> boot automatically after two minutes without a key press, and then the
> kernel should find your keyboard."

this also doesn't apply to you, because this talks about the *boot prompt*
(i.e., the prompt where you typed 'bare.i nousb'), *not* about the login
prompt or the bash prompt. it says that if at the boot prompt your usb
keyboard does not work, you can just wait two minutes, after which the
bare.i kernel will be loaded automatically, which should recognise the usb
keyboard.

in your case, the keyboard works fine until (IIUC) you select a keyboard
map. if that is the case, you should be able to use the keyboard if you
skip the keymap selection menu, and if you remove the executable bit on
/etc/rc.d/rc.keymap before you reboot.

does your keyboard work if you install 9.1 and use a 2.4.20 kernel? 2.4.20
is the kernel that comes with 9.0, and IIRC you mentioned that your
keyboard worked fine under 9.0. if it also works with 9.1 and a 2.4.20
kernel, then it might be a good idea to contact one of the mailing lists at
<http://www.linux-usb.org>, because something may have changed in the usb
drivers that caused a bug.

--
Joost Kremers

As per my post above [Going backward to go forward] I finally had to install Slack 9.0

olias · 10-31-2003, 07:58 PM

Thanks, Wonderer:

I was away on a biz trip all week and just got back. I read through all your trials and tribs and will try again tonight. I'll start by checking my BIOS and then do a clean install. I'll report back here soon if all goes well.

olias

olias · 10-31-2003, 10:26 PM

All I did was disable 'USB Keyboard' and it worked !!! I don't even have a USB keyboard but the default in BIOS was 'enabled'.

Thanks Wonderer for getting me on the right path... olias