[Bug 389169] New: Keyboard sometimes doesn't work after boot
https://bugzilla.novell.com/show_bug.cgi?id=389169 User jmleziva@tiscali.cz added comment https://bugzilla.novell.com/show_bug.cgi?id=389169#c1 Summary: Keyboard sometimes doesn't work after boot Product: openSUSE 10.3 Version: Final Platform: 32bit OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jmleziva@tiscali.cz QAContact: kernel-maintainers@forge.provo.novell.com CC: jmleziva@tiscali.cz Found By: Customer Steps to reproduce: 1. select "openSUSE 10.3 - 2.6.22.17-0.1" in the GRUB menu, press ENTER 2. the Suse splash screen appears. Press ESC to show running commands. Here are two situations. If the splash screen disappears, you can see commands and will be able to log into the system. But if the splas screen stays, the login screen appears but you cannot log because the keyboard does not work. The mouse works properly. The only possibility is to shutdown the system using mouse. The problem started after upgrading from openSUSE 10.2 to 10.3 . I think this problem doesn't depend on the X-Window. I have set the default runlevel to 3 and the problem occured too. If the problem occures I was not able to enter username and password at the command line prompt. The boot was successfull roughly in 7 trials of 11 ones in my tests. It is annoying to repeat booting due this problem. The hardware is the notebook Fujitsu Siemens Amilo Pro V2030, with openSUSE 10.3, with the latest updates. The video driver is OpenChrome. The command "uname -a" gives this output: Linux mlnb 2.6.22.17-0.1-default #1 SMP 2008/02/10 20:01:04 UTC i686 i686 i386 GNU/Linux. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=389169
User rvojcik@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389169#c1
Robert Vojcik
https://bugzilla.novell.com/show_bug.cgi?id=389169
User jmleziva@tiscali.cz added comment
https://bugzilla.novell.com/show_bug.cgi?id=389169#c2
--- Comment #2 from Jiri Mleziva
https://bugzilla.novell.com/show_bug.cgi?id=389169
Jiri Mleziva
https://bugzilla.novell.com/show_bug.cgi?id=389169
Martin Mrazik
https://bugzilla.novell.com/show_bug.cgi?id=389169
User rvojcik@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389169#c3
Robert Vojcik
https://bugzilla.novell.com/show_bug.cgi?id=389169
User jmleziva@tiscali.cz added comment
https://bugzilla.novell.com/show_bug.cgi?id=389169#c4
--- Comment #4 from Jiri Mleziva
https://bugzilla.novell.com/show_bug.cgi?id=389169
Jiri Mleziva
https://bugzilla.novell.com/show_bug.cgi?id=389169
Martin Mrazik
https://bugzilla.novell.com/show_bug.cgi?id=389169
Cyril Hrubis
https://bugzilla.novell.com/show_bug.cgi?id=389169
Greg Kroah-Hartman
https://bugzilla.novell.com/show_bug.cgi?id=389169
Jeff Mahoney
https://bugzilla.novell.com/show_bug.cgi?id=389169
User jkosina@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389169#c5
Jiri Kosina
https://bugzilla.novell.com/show_bug.cgi?id=389169
User jmleziva@tiscali.cz added comment
https://bugzilla.novell.com/show_bug.cgi?id=389169#c6
--- Comment #6 from Jiri Mleziva
https://bugzilla.novell.com/show_bug.cgi?id=389169
Jiri Mleziva
https://bugzilla.novell.com/show_bug.cgi?id=389169
User jkosina@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389169#c7
--- Comment #7 from Jiri Kosina
https://bugzilla.novell.com/show_bug.cgi?id=389169
Jiri Kosina
https://bugzilla.novell.com/show_bug.cgi?id=389169
User jmleziva@tiscali.cz added comment
https://bugzilla.novell.com/show_bug.cgi?id=389169#c8
--- Comment #8 from Jiri Mleziva
https://bugzilla.novell.com/show_bug.cgi?id=389169
Jiri Mleziva
https://bugzilla.novell.com/show_bug.cgi?id=389169
User jkosina@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389169#c9
Jiri Kosina
I am not a skilled Linux user so please correct my steps to test a new kernel: 1. backup of the filesystem /
This really shouldn't be needed, but of course it never harms :)
2. install the new kernel ... #rpm -i kernel-default-2.6.22.18-0.1.i586.rpm
This is correct.
Do I have to install the patch input-add-amilo-pro-v-to-nomux.patch ? How to do it?
You don't have to do that, the testing kernel I have built for you already contains that patch.
Does the present kernel 2.6.22.17-0.1-default remain in the system after runnig rpm -i ?
It definitely should, but you can easily check to be 100% sure after installing the kernel, that its entry remained in the /boot/grub/menu.lst and that the /boot/vmlinuz-* and /lib/modules files for the old kernel are still there.
3. add a new section to the file /boot/grub/menu.lst , for the new kernel, without any boot parameters
It will be added automatically, when you install the RPM.
4. run the test
Thanks. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=389169
User jmleziva@tiscali.cz added comment
https://bugzilla.novell.com/show_bug.cgi?id=389169#c10
--- Comment #10 from Jiri Mleziva
https://bugzilla.novell.com/show_bug.cgi?id=389169
User jmleziva@tiscali.cz added comment
https://bugzilla.novell.com/show_bug.cgi?id=389169#c11
--- Comment #11 from Jiri Mleziva
https://bugzilla.novell.com/show_bug.cgi?id=389169
Jiri Mleziva
https://bugzilla.novell.com/show_bug.cgi?id=389169
User jkosina@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389169#c12
Jiri Kosina
I installed the new kernel 2.6.22.18-0.1 successfully. I removed the boot parameter "i8042.nomux=1" from the /boot/grub/menu.lst , other parameters remained. After that I restarted the system. But the keyboard didn't work, the problem was worse than at the kernel 2.6.22.17-0.1. I tried booting twice and the keyboard didn't work in any case. After that I added the parameter "i8042.nomux=1" to the menu.lst and the keyboard worked again.
Apparently, Fujitsu-Siemens decided to alter the DMI information for this hardware somehow. Could you please attach output of 'dmidecode', so that I can prepare new kernel for you to test? Thanks. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=389169
User jmleziva@tiscali.cz added comment
https://bugzilla.novell.com/show_bug.cgi?id=389169#c13
--- Comment #13 from Jiri Mleziva
https://bugzilla.novell.com/show_bug.cgi?id=389169
User jmleziva@tiscali.cz added comment
https://bugzilla.novell.com/show_bug.cgi?id=389169#c14
Jiri Mleziva
https://bugzilla.novell.com/show_bug.cgi?id=389169
User jkosina@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389169#c15
Jiri Kosina
https://bugzilla.novell.com/show_bug.cgi?id=389169
Jiri Kosina
https://bugzilla.novell.com/show_bug.cgi?id=389169
User jmleziva@tiscali.cz added comment
https://bugzilla.novell.com/show_bug.cgi?id=389169#c16
Jiri Mleziva
https://bugzilla.novell.com/show_bug.cgi?id=389169
User jkosina@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389169#c17
Jiri Kosina
https://bugzilla.novell.com/show_bug.cgi?id=389169
User meissner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389169#c18
--- Comment #18 from Marcus Meissner
participants (1)
-
bugzilla_noreply@novell.com