https://bugzilla.novell.com/show_bug.cgi?id=665720 https://bugzilla.novell.com/show_bug.cgi?id=665720#c11 --- Comment #11 from Felix Miata <mrmazda@earthlink.net> 2011-02-20 04:24:17 UTC --- (In reply to comment #9)
When you run kbdrate -r 20 -d 250 on a system that it isn't working on, does it fix it? If not, can you provide the output of strace <kbdrate command>?
Likewise with setleds +num.
I finally remembered to try this on a M6 system (kt880) before duping to RC1. kbdrate & setleds from root prompt do what they're supposed to do. I did double check, and the problem is only exhibited on alternate boots, except if because on current boot it was ignored I've run kbdrate & setleds manually, in which case on subsequent boot it was ignored again, breaking the alternate boot pattern. All the above only applied if restart was via command 'init 6' (>6 successive boots). Then I switched to restart via command 'reboot' for the next several boots, in which keyboard file was always ignored, and after switching back to 'init 6' for three more boots; then since (>8 successive boots), the alternate boot pattern has been back. In all of this testing specifically for this bug I've only been booting into runlevel 3, via 3 on Grub cmdline, in part because of common loss of sync between NUM state and NUM led when switching back & forth between X & consoles. Then on an init 6 restart I removed the 3 from Grub's cmdline. KDM came up, I switched to tty2, found NUM lit with NUM state on and kbd repeat at 20, logged in root, ran an rpm query, logged out, went back to KDM, and selected restart. On restart I again removed 3 from Grub cmdline before proceeding, but this time I was left on tty1, with NUM led off to see "...runlevel 5 has been reached", and no access to X's tty7. I logged in root on tty2, then 'init 3; init 5' to reach KDM, switched back to tty2 to find NUM state off but NUM led on, and kbd rate maximized. I exited login, switched to KDM, selected reboot, removed 3 from Grub cmdline again, and found myself left on tty1 in runlevel 5 same as last restart. I repeated this 5/KDM restart process once more with same result. Tired of this, I changed repos to RC1 iso only, zypper ref; zypper al kernel-desktop; zypper dup, and repeated booting via command 'reboot'. /etc/sysconfig/keyboard was obeyed on 3-4 successive runlevel 3 boots, then not on the next. So, I 'zypper rl kernel-desktop', switched repo from RC1 iso to factory's OSS & non-OSS, 'zypper ref', 'zypper in kernel-desktop', and rebooted via command 'reboot'. That resulted in no boot, just GRUB. I fixed Grub using Knoppix CD, then booted RC1, and rebooted 4 times using 'init 6'. /etc/sysconfig/keyboard's NUM, delay and rate settings were disobeyed every time. Then I restarted using 'reboot', and they were obeyed. I did it again, and they were not, and again twice more, both not. Then I tried 'init 6' again, and they were obeyed, and again thrice, but next two not after turning NUM on manually each time, and next not after turn NUM on manually, then turning it back off before init 6. Next I left NUM off, but after init 6 again disobeyed 7 cycles before being obeyed again. Next disobeyed runlevel 3 boot, after login I did 'init 1', typed root password, 'init 3', and enjoyed normal runlevel 3 function. Next I booted via 'reboot' directly to runlevel 1, typed root password, 'init 3', and happiness again, at least 7 straight cycles.
From where I sit, this is seriously wierd, and very annoying, since network does not come up automatically on every normal (3) boot when keyboard settings are ignored.
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.