after upgrading to 686 kernel, mouse and keyboard stop working

[Ryan Rawdon]

This happens both in dapper and in 5.10 (I did not try 5.04)
As soon as I upgrade the kernel to 686 in either case (on this one particular system), the keyboard and mouse input is not recognized at all. This happens in "Recovery Mode" boot too (no keystrokes are recongized)

Booting with the 386 kernel works fine, the lspci information below is from running on 386. I will try to boot the 686 and ssh in to get a dmesg output from the 686 boot, but I cannot post that at this time.

I'm not sure what hardware information you need.

lspci:

0000:00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev c4)
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP]
0000:00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40)
0000:00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
0000:00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 16)
0000:00:07.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 16)
0000:00:07.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40)
0000:00:08.0 SCSI storage controller: Adaptec AHA-2940U/UW/D / AIC-7881U
0000:00:0a.0 Ethernet controller: National Semiconductor Corporation DP83815 (MacPhyter) Ethernet Controller
0000:01:00.0 VGA compatible controller: Matrox Graphics, Inc. G400/G450 (rev 82)

My apologies if you need other information, just ask ;)

[Ryan Rawdon (flieslikeabrick)]

this is the output of dmesg on the 686 (when the keyboard and mouse are not working)

[Ryan Rawdon (flieslikeabrick)]

According to the person who uses this desktop, it started working, just apparently taking forever to recognize input from input devices.

I guess this is no longer a problem, but it is still intermittent that it recognizes input from the mouse/keyboard within a reasonable amount of time

[Ryan Rawdon (flieslikeabrick)]

Only the latest build of 2.6.15-686 seems not to work (build 20 doesn't work, 19 works just fine). This bug still exists

[Dennis Kaarsemaker (dennis)]

How about the -22 kernel?

[Ryan Rawdon (flieslikeabrick)]

it appears that all 686 kernels are hit-and-miss (including -22), mostly miss. 386 appear to work all the time. the computer is dual 866 pentium 3, so 686 is the proper kernel for it.

[Vassilis Pandis (pandisv)]

Is this still a problem?

[Ryan Rawdon (flieslikeabrick)]

Funny you should post in this now... I just checked on this yesterday and was about to post a comment.

With all of the 686 kernels in the dapper repos, yes it is still a problem. I have not yet tried anything from the edgy repos.

I tried compiling a custom kernel and I don't think that worked either. Any suggestions on what specific options might be related to this? I want to try altering the custom kernel options more and find out exactly what might be causing this, assuming it is an option-related thing and not a flat-out bug.

[Launchpad Janitor (janitor)]

[Expired for linux-source-2.6.15 (Ubuntu) because there has been no activity for 60 days.]