After upgrade kernel to 2.6.16 and above I recive error that 8042 Can't read CTR and my keyboard isn't responding. This issue ISN'T apply to vanilla sources. I'm using now 2.6.17-rc3 but 2.6.18-rc4 is also working. I don't know what would help to resolve so I add some info: lspci: 00:00.0 Memory controller: nVidia Corporation CK804 Memory Controller (rev a3) 00:01.0 ISA bridge: nVidia Corporation CK804 ISA Bridge (rev a3) 00:01.1 SMBus: nVidia Corporation CK804 SMBus (rev a2) 00:02.0 USB Controller: nVidia Corporation CK804 USB Controller (rev a2) 00:02.1 USB Controller: nVidia Corporation CK804 USB Controller (rev a3) 00:04.0 Multimedia audio controller: nVidia Corporation CK804 AC'97 Audio Controller (rev a2) 00:06.0 IDE interface: nVidia Corporation CK804 IDE (rev a2) 00:07.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev a3) 00:08.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev a3) 00:09.0 PCI bridge: nVidia Corporation CK804 PCI Bridge (rev a2) 00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a3) 00:0b.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) 00:0c.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) 00:0d.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) 00:0e.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:0a.0 FireWire (IEEE 1394): Texas Instruments TSB82AA2 IEEE-1394b Link Layer Controller (rev 01) 05:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6600] (rev a2) Kernel config is at: http://home.autocom.pl/albert/config-2.6.17-rc3 If anythine else is needed I can provide everything you need.
Please, don't refer to third-party links in bugs. Attach your .config here and reopen then. Thanks.
Created attachment 94331 [details] Config of 2.6.17-rc3
Reaopen after .config posted
Please confirm that gentoo-sources-2.6.17-r5 is affected, and if so, revert these two patches in this order: http://dev.gentoo.org/~dsd/genpatches/trunk/2.6.17/4401_speakup-serio.patch http://dev.gentoo.org/~dsd/genpatches/trunk/2.6.17/4400_speakup-20060618.patch See if that solves the problem
I confirm that gentoo-sources-2.6.17-r5 is affected. Unpatching that two patches makes kernel usable and my keyboard is working again.
Is this still present in gentoo-sources-2.6.19-r1?
(In reply to comment #6) > Is this still present in gentoo-sources-2.6.19-r1? > Yes, but this time dmesg give me little more informations: i8042.c: Can't read CTR while initializing i8042. i8042: probe of i8042 failed with error -5 And also, unpatching speakup fixes that problem.
I'm fairly sure the patch in bug #157493 (on top of 2.6.19) will fix this for you. Please scream loudly on that bug if it doesn't. *** This bug has been marked as a duplicate of 157493 ***
Hi, I tried that patch for 2.6.18-r5 and 2.6.19-r2, but unfortunatly it didn't help so I'm screaming loudly :P
And unpatching speakup still solves the problem? speakup modifies the order that things are built in drivers/Makefile, which in turn alters the order in which subsystems are loaded during boot. speakup moves these 3 lines up in the Makefile: obj-$(CONFIG_SERIO) += input/serio/ obj-$(CONFIG_GAMEPORT) += input/gameport/ obj-$(CONFIG_INPUT) += input/ This means input is loaded earlier which allows speakup to be disabled earlier. Assuming unpatching speakup solves the problem, perhaps you could try something like: Manually revert the changes in the speakup patch to drivers/Makefile and ensure that it solves the problem. Assuming it does, start moving the input/ lines higher and higher until you find the place where the problem gets introduced.
Sorry for no response, but you know, end of the year... Anyway I found solution. Following patch resolves my problem. I hope that it didn't break anything for other systems.
Created attachment 105139 [details, diff] Patch for no keyboard issue
Thanks! it's scary, we'll have to see :)
I completely dropped the makefile reordering as it's just too risky. Fixed in gentoo-sources-2.6.19-r3
