SiS USB controller not working (ohci)

Bug #8705 reported by Kyle Schneider
16
Affects Status Importance Assigned to Milestone
linux-source-2.6.15 (Ubuntu)
Fix Released
Medium
Fabio Massimo Di Nitto

Bug Description

My USB keyboard is not detected once I get past the boot screen on the recent install CDs. Was
told to file a new bug report, ( https://bugzilla.ubuntu.com/show_bug.cgi?id=1881 ).

Revision history for this message
Kyle Schneider (kschneider2003) wrote :

Created an attachment (id=284)
lspci data

Revision history for this message
Kyle Schneider (kschneider2003) wrote :

Created an attachment (id=285)
lspci-n

Revision history for this message
Kyle Schneider (kschneider2003) wrote :

This is on a Gigabyte GA-8SG800 motherboard and a Logitech 967234-0102 keyboard.

Revision history for this message
Colin Watson (cjwatson) wrote :

Fixes uploaded:

discover1-data (1.2004.09.12-0ubuntu9) warty; urgency=low

  * Add usb/ehci-hcd for 10397002 (closes: Ubuntu #1971).

 -- Colin Watson <email address hidden> Fri, 1 Oct 2004 23:46:23 +0100

usb-discover (0.18ubuntu3) warty; urgency=low

  * Build with discover1-data 1.2004.09.12-0ubuntu9 (closes: Ubuntu #1971).
  * Add USB HCI detection using PCI classes read from sysfs.

 -- Colin Watson <email address hidden> Sat, 2 Oct 2004 00:24:06 +0100

The last part of that usb-discover change, a suggestion by Matt Zimmerman,
should make this whole class of problems go away.

Revision history for this message
Kyle Schneider (kschneider2003) wrote :

My keyboard is still not detected on the 10-11-2004 daily build. As soon as I hit enter at the boot
prompt, my keyboard stops responding (not even able to toggle num lock).

Revision history for this message
Matt Zimmerman (mdz) wrote :

Can you try booting with pci=noacpi, noapic, or acpi=off?

Revision history for this message
Colin Watson (cjwatson) wrote :

Other bugs suggest that this is probably a matter of BIOS configuration and/or
kernel parameters rather than an installer bug; I'm downgrading this in the
meantime until we know more.

Revision history for this message
Kyle Schneider (kschneider2003) wrote :

PCI=noacpi and noapic produce no result. However, acpi=off allows the keyboard to work properly.

Revision history for this message
Matt Zimmerman (mdz) wrote :

Thanks. In this case, it is a kernel problem, and not an installer problem.

Unfortunately, it is difficult to collect debugging information when the
keyboard does not work. Are you able to plug in a PS/2 keyboard for debugging
purposes?

Revision history for this message
Matt Zimmerman (mdz) wrote :

*** Bug 8795 has been marked as a duplicate of this bug. ***

Revision history for this message
Kyle Schneider (kschneider2003) wrote :

Sadly, the PS/2 keyboard port on my computer doesn't work, which is why I'm using a USB keyboard.

Revision history for this message
Wayne (ubuntu-noob00) wrote :

Created an attachment (id=501)
Working kernel log

Noticed after installing restricted upgrade patch for 386 and 686 kernel

Revision history for this message
Wayne (ubuntu-noob00) wrote :

Created an attachment (id=502)
Non working kernel log

Revision history for this message
Herbert Xu (herbert-gondor) wrote :

(In reply to comment #12)
> Created an attachment (id=501) [edit]
> Working kernel log
>
> Noticed after installing restricted upgrade patch for 386 and 686 kernel

This is an old kernel with MSI turned on. Please retest with the latest kernel
package (2.6.8.1-16). Thanks.

Revision history for this message
Herbert Xu (herbert-gondor) wrote :

Eric, after your system comes up what does /proc/interrupts contain?

Revision history for this message
Eric Donkersloot (eric-lordchaos) wrote :

(In reply to comment #15)
> Eric, after your system comes up what does /proc/interrupts contain?

ericd@falcon ~ $ cat /proc/interrupts
           CPU0
  0: 1288694 XT-PIC timer
  2: 0 XT-PIC cascade
  5: 2 XT-PIC ohci1394
  7: 1 XT-PIC parport0
  8: 1 XT-PIC rtc
  9: 3 XT-PIC ehci_hcd
 10: 5449 XT-PIC ohci_hcd, ohci1394, eth0
 11: 6743 XT-PIC ohci_hcd
 12: 18563 XT-PIC EMU10K1, ohci_hcd
 14: 16324 XT-PIC ide0
 15: 4186 XT-PIC ide1
NMI: 0
LOC: 0
ERR: 0
MIS: 0

Revision history for this message
Herbert Xu (herbert-gondor) wrote :

Thanks, what about the case where it doesn't work?

Revision history for this message
Eric Donkersloot (eric-lordchaos) wrote :

(In reply to comment #17)
> Thanks, what about the case where it doesn't work?

ericd@falcon ~ $ cat interrupts
           CPU0
  0: 176072 XT-PIC timer
  1: 147 XT-PIC i8042
  2: 0 XT-PIC cascade
  5: 2 XT-PIC ohci1394
  7: 1 XT-PIC parport0
  8: 1 XT-PIC rtc
  9: 3 XT-PIC acpi, ehci_hcd
 10: 34 XT-PIC ohci1394, eth0
 12: 3 XT-PIC EMU10K1
 14: 6551 XT-PIC ide0
 15: 1157 XT-PIC ide1
NMI: 0
LOC: 0
ERR: 0
MIS: 0

Revision history for this message
Wayne (ubuntu-noob00) wrote :

I found a work around and was able to use both the keyboard and mouse by
disabling their support in the Bios
(In reply to comment #0)
> My USB keyboard is not detected once I get past the boot screen on the recent
install CDs. Was
> told to file a new bug report, (
https://bugzilla.ubuntu.com/show_bug.cgi?id=1881 ).

Revision history for this message
Herbert Xu (herbert-gondor) wrote :

Wayne, you've got an unrelated problem of USB handoff so please file a new bug.
 The other two are having an IRQ issue.

Revision history for this message
Herbert Xu (herbert-gondor) wrote :

(In reply to comment #8)
> PCI=noacpi and noapic produce no result. However, acpi=off allows the
keyboard to work properly.

Even though the keyboard doesn't work, the machine should still boot up fully
and log to the disk. So please attach the working and non-working kern.log entries.

Revision history for this message
Herbert Xu (herbert-gondor) wrote :

Scratch that comment, you're all having USB handoff problems :)

Revision history for this message
Eric Donkersloot (eric-lordchaos) wrote :

Created an attachment (id=521)
kern.log - acpi=off

Revision history for this message
Eric Donkersloot (eric-lordchaos) wrote :

Created an attachment (id=522)
kern.log - non working ohci

Revision history for this message
Herbert Xu (herbert-gondor) wrote :

Can everyone please try the kernel at

http://gondor.apana.org.au/~herbert/ubuntu/acpi/vmlinuz-2.6.8.1-3-686.2

and see if it fixes the problem? It's built for the 686 flavour package of course.

Revision history for this message
Eric Donkersloot (eric-lordchaos) wrote :

(In reply to comment #25)
> Can everyone please try the kernel at
>
> http://gondor.apana.org.au/~herbert/ubuntu/acpi/vmlinuz-2.6.8.1-3-686.2
>
> and see if it fixes the problem? It's built for the 686 flavour package of course.

I'll try it tonight...I'll keep you posted, thanks.

Revision history for this message
Eric Donkersloot (eric-lordchaos) wrote :

(In reply to comment #25)
> Can everyone please try the kernel at
>
> http://gondor.apana.org.au/~herbert/ubuntu/acpi/vmlinuz-2.6.8.1-3-686.2
>
> and see if it fixes the problem? It's built for the 686 flavour package of course.

Works fine, thanks...do you need the kern.log or any other info ?

Revision history for this message
Herbert Xu (herbert-gondor) wrote :

Thanks for testing. This issue is fixed by the same patch as in #1922 (but it
is a different bug).

Revision history for this message
Eric Donkersloot (eric-lordchaos) wrote :

(In reply to comment #28)
> Thanks for testing. This issue is fixed by the same patch as in #1922 (but it
> is a different bug).

Will the patch be included in the next ubuntu kernel ?

Revision history for this message
Herbert Xu (herbert-gondor) wrote :

It should be.

Revision history for this message
gela (gerald-orixa) wrote :

Created an attachment (id=679)
Kernel configuration file

I experienced the same problem, no USB devices recognized (using the SiS
chipset)
after reconfiguring and compiling the kernel USB works fine...
(I was just happy to get it working, so I didn't try to match the bug to a
specific change in the config...)

Revision history for this message
Matt Zimmerman (mdz) wrote :

(In reply to comment #31)
> Created an attachment (id=679) [edit]
> Kernel configuration file
>
> I experienced the same problem, no USB devices recognized (using the SiS
> chipset)
> after reconfiguring and compiling the kernel USB works fine...
> (I was just happy to get it working, so I didn't try to match the bug to a
> specific change in the config...)

Did you perhaps disable CONFIG_PCI_MSI?

Revision history for this message
Matt Zimmerman (mdz) wrote :

(In reply to comment #32)
> (In reply to comment #31)
> > after reconfiguring and compiling the kernel USB works fine...
> > (I was just happy to get it working, so I didn't try to match the bug to a
> > specific change in the config...)
>
> Did you perhaps disable CONFIG_PCI_MSI?

Hmm, no, you didn't...

Revision history for this message
Eric Donkersloot (eric-lordchaos) wrote :

(In reply to comment #33)
> (In reply to comment #32)
> > (In reply to comment #31)
> > > after reconfiguring and compiling the kernel USB works fine...
> > > (I was just happy to get it working, so I didn't try to match the bug to a
> > > specific change in the config...)
> >
> > Did you perhaps disable CONFIG_PCI_MSI?
>
> Hmm, no, you didn't...

(In reply to comment #30)
> It should be.

I hope the patch will be uploaded soon, since keyboard and mouse are not working
when trying to install 4.10.
I'll guess I'll have to wait 'till the next official release ?

Revision history for this message
Matt Zimmerman (mdz) wrote :

Herbert, if this patch is not already integrated upstream, could you provide us
with a copy?

Revision history for this message
Herbert Xu (herbert-gondor) wrote :

It's the same patch as I used in #1922. That in turn was integrated in 2.6.10
if not 2.6.9. See also http://bugzilla.kernel.org/show_bug.cgi?id=3191.

Revision history for this message
Matt Zimmerman (mdz) wrote :

OK, so this is fixed in current Hoary, which uses 2.6.10. Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.