Bugzilla – Bug 115189
Cannot login to Gnome keyboard not responding
Last modified: 2005-09-14 11:54:59 UTC
After a sweet install on my Sony Vaio VGN-T1XP, I adjusted the screen in SAX2 and restarted. When rebooting, I wanted to go into YAST, but was logged in under my user account, added during setup. The system asked me for the root password but when I type, nothing appeared in the edit box. Since I had made the system automatically log me in under my user account, as default, I thought I would remove this to give me a chance to log in as root. Rebooted OK, but then at the login screen I still can't get any input from the keyboard so system completely unusable now.
Is the keyboard not working at all? Can you switch to console1? So, this failed after you did some changes in sax2, didn't it?
Hi. When you switch to the console, using the Windows key, the keyboard works fine. The problem appears to be related to XWindows. Whenever you want to interact with the system, it will not accept any key strokes. In my case, when I try to get into YAST2, it asks for the root password, I type, but nothing goes into the edit box. I hope this helps.
Sorry, thought this may also help. I cannot be positive, but the order things happened in were as follows: 1) Went to SAX2 and altered screen resolution to 1280x768 2) Did a reboot to accept changes 3) Tried to get into YAST to sort out my wireless LAN and was asked for root password. This is when I first discovered that the system was not accepting my key-strokes into the edit boxes. Thanks
I wish I could tell you that I can type in other applications but I just cant get into GNOME at all now. Also, I hit the windows key again to get to the console window. There are quite a few errors in there about tpm, ipw2200, mDNSResponder, pcc_acpi, mttr overlaps etc. I am pretty new to Linux; I have entered from the NetWare side of things. If it was any use and I could get this console output off the system I am happy to email this?? Thanks Ged
I haven't seen this in any other beta 4 reports AJ, I suspect this is not gnome specific. Ged, can you attach the output of hwinfo?
I can attatch the hwinfo if you tell me what this is, where it is and how to get at it etc. I am a newbee on Linux. My Vaio has no floppy, it has no wireless LAN of course, but it does have USB and I have a floppy and a pen drive. Also, the Ethernet was working when I tried to look for some updates to try and fix the problem. I got YAST working under the console. Finally, I only have the console remember. So, if you want to give me some instructions then I will get this and anything else you need. Thanks Ged
Log in as root and run 'hwinfo > hwinfo.txt' from the command line. Attach hwinfo.txt to this bug.
This is the same issue that happend in beta 2 and fixed with a patch. See the following dmesg. ath_rate_sample: module not supported by Novell, setting U taint flag. ath_rate_sample: Unknown symbol ath_hal_computetxtime ath_pci: Unknown symbol ath_rate_tx_complete ath_pci: Unknown symbol _ath_hal_attach ath_pci: Unknown symbol ath_rate_attach ath_pci: Unknown symbol ath_rate_newassoc ath_pci: Unknown symbol ath_hal_computetxtime ath_pci: Unknown symbol ath_rate_dynamic_sysctl_register ath_pci: Unknown symbol ath_hal_mhz2ieee ath_pci: Unknown symbol ath_hal_detach ath_pci: Unknown symbol ath_hal_probe ath_pci: Unknown symbol ath_rate_node_cleanup ath_pci: Unknown symbol ath_rate_detach ath_pci: Unknown symbol ath_rate_node_init ath_pci: Unknown symbol ath_rate_findrate ath_pci: Unknown symbol ath_hal_init_channels ath_pci: Unknown symbol ath_rate_newstate ath_pci: Unknown symbol ath_rate_setupxtxdesc ath_pci: Unknown symbol ath_hal_getwirelessmodes
#9 can be ignored - or just install the kernel-default-nongpl package. Screening Team, can you help here?
I created hwinfo.txt but cannot get it to my pen drive. Not sure what it has been mounted as or where to find it. Is there a file management tool under the terminal? Any other help?
It will be mounted as /media/usbdisk likely.
Created attachment 48792 [details] HWINFO Ok getting the hang of this a bit more now. Thanks for the info about the USB_DISK. Here is the file, I hope it helps. Ged
assigned to holger, not sure if its a gdm problem
Holger is not available now.
Maybe stefan has an idea about the X driver involved?
Possibly something else to try to see if it is gdm - open /etc/sysconfig/displaymanager as root and then change the line: DISPLAYMANAGER="gdm" to DISPLAYMANAGER="xdm" (or kdm if KDE is installed). Reboot and the login screen should be different, try to type and report if it works or not.
No. I don't.
Hi there. I changed the DISPLAYMANAGER to gdm and rebooted. This brought me into a different x but I still cannot use the keys. I will try again with "xdm" but I imagine this won't work either. Unless I come back within the next 5 minutes then you can assume it has not! Ged
One more thing I noticed, not sure if it is relevant? When I got into xdm, the small console in the left hand corner had the following messages: Sep 6 23:04:46 linux kernel: mttr: base(0xe8020000) is not aligned on a size(0x300000) boundary Sep 6 23:04:50 linux kernel: mttr: 0xe8000000,0x8000000 overlaps existing 0xe8000000,0x4000000 Does this have any relevance?? Ged
please send /var/log/boot.msg and messages (from booting on, not the whole file) have you tried booting with failsafe?
Booting with failsafe will not start gnome so this make no difference really. I will get the log file together now.
Created attachment 49029 [details] boot.msg This is the whole file. It is not so big and I was not really sure where to start so better to have it all than miss something.
Created attachment 49030 [details] Messgages As per boot.msg - whole thing. Ged
From comment #19, you changed DISPLAYMANAGER to 'gdm'? What was it before? And to be clear, neither gdm or xdm allow you to use the keyboard?
I dod not even know what DISPLAYMANAGER was until comment 17 above. When I went to change it as requested, it already said gdm. Maybe this is the problem - it must have somehow got set to gdm at some point, but it certainly was not me. If you tell me what it should be for Gnome then perhap so I can put it back. Then, if that works, the only issue then is how it got there in the first place. Thanks Ged
Its supposed to be gdm for a default GNOME install, its the (G)NOME (D)isplay (M)anager. Its what you see when you log in. If the keyboard is failing just with gdm (you should probably reboot after changing the value) its a gnome/gdm issue. If the keyboard also fails with the value set to "xdm" its more likely a general X issue.
Re-reading #3, it looks like you can enter text at the graphical login screen to do the initial login right? If so... Do any other apps like gedit work? (When logged in, try Alt-F2 and then type "gedit" and try to enter something in the text editing area).
The very first time after the install, everything worked fine. NB.During the install, I configured a user account "gedt" and ticked the box to tell the system to automatically boot to that account. So, after the first boot, I went into SAX2, the system asked for the root password. I entered root OK and made my mods in SAX to my Vaio screen resolution. I then re-booted, and it again, logged me straight back into Gnome using my default user account. Then I tried to get into YAST; the system asked for the root password, at this point I could no longer enter text into the login box. After this, I used YAST in the console and stopped the system logging in with my default user password, to see if it was a user account issue. No change, still could not log in. Then tried the DISPLAYMANAGER etc etc but using gdm, or xmd, it is not possible to use the keyboard to login. Hope this clears things up. Ged
AJ, based on this it sounds like an X configuration problem. Should it be assigned elsewhere?
Let's assign to screening team.
please send more information about your X configuration, please call as root siga no -x11 hwinfo --keyboard >> /tmp/siga/siga.txt and attach the file /tmp/siga/siga.txt to this bug
Created attachment 49079 [details] Siga.txt As requested. Ged
the attachment is wrong ... please retry siga no -x11 this should take a while and you should see something like this on the screen: f219:/var/log # siga no -x11 siga - System Information gathering 10.002 mlasars@suse.de & jsj@suse.de 2005 08 26 - root test done, making temporary directory... - X test done - *** using w3m - *** using pico -w - beginning gathering ... this may take a while [...] after that you have a file /tmp/siga/siga.txt, this is what i need. If you look at the file you should see all kind of information. to make it easier, just make another attachment: hwinfo --keyboard > /tmp/hwinfo_kdb and also attach /tmp/hwinfo_kbd thanks
Created attachment 49148 [details] hwinfo_kdb
Created attachment 49149 [details] siga.txt Just as you described. This has content.
thanks, files are now ok. please try: - boot with safe settings, login as root and execute init 5 is the keyboard now working? - boot into runlevel 3 and reconfigure your X with sax2, don't enable 3D copy first your old config with cp /etc/X11/xorg.conf /root/
Sorry, please can you give me a little more info. How do I boot into runlevel 3? How do I configure my X with sax2 I guess the copy is to make a backup before I start? Thanks Ged
to start in runlevel 3: at the grub bootmenue press F2 for other options, now just enter 3 and press enter to boot sax2: just login as root and enter sax2 after the configuration (without enabling 3d) enter init 5 to start X. yes, the copy is for a backup
Tried - boot with safe settings, login as root and execute init 5 is the keyboard now working? NO - No change. Will try next option via SAX2
Sax2 mods worked. All is well again. Is there anything else you guys need? Can you tell me the outcome?
ALSO... How do I get my nice login screen back?? Ged
what do you mean with that? you have to start now without failsafe or 3 and the graphical login should come up again. please send me the file /etc/X11/xorg.conf
What I mnean is that instead of getting the nice login window, I get the agricultural grey one, that says Welcome ai Linux above the Login/Password box, with the little console window in the bottom left hand corner. thanks
you have to change DISPLAYMANAGER="xdm" to DISPLAYMANAGER="gdm" in /etc/sysconfig/displaymanager please send me the file /etc/X11/xorg.conf
gdm worked. thanks for all the help, it has been a nice learning curve if nothing else. Hope this produces a fix along the line somewhere. keep up the good work!
please send me the file /etc/X11/xorg.conf
Created attachment 49440 [details] xorg.conf Here it is. Also, I have another bug, possibly?? Now I am back into Gnome, I dragged the file onto the icon on the desktop (mounted USB_DISK) and it said the disk was full. Also, it did this when I explored the disk, but when I copied by right clicking on the file and then pasted inside the file browser view it worked fine. Also, when you mount the disk, it does not re-appear on the desktop etc. Should I report these seperately or can you take care of it?
The first bug you're describing in #48 is https://bugzilla.novell.com/show_bug.cgi?id=113421 As for the second, please open a new bug with further detail. I'm seeing mounted removable disks on the desktop.
Marcus & Stefan: It works now after reconfiguring X with sax. One difference i can see is that the first config was with vnc enabled. Section "InputDevice" Driver "rfbkeyb" Identifier "Keyboard[2]" Option "InputFashion" "VNC" EndSection Can you see another difference which maybe causes the problem? please look at attachment sdiff for easier reading.
Created attachment 49584 [details] sdiff of new and original xorg.conf
Could you please attach the new xorg.conf. I'm not convinced that it's easy to read the sdiff ...
its already there, see #48
Ok. Then attach the old one.
Created attachment 49595 [details] original xorg.conf
done .. this is from the siga output ... i wonder a little bit why there is no sax header
> (EE) Couldn't load XKB keymap, falling back to pre-XKB keymap Probably this is the problem. Pleaes uninstall xkeyboard-config and remove the remaining files below /etc/X11/xkb and reinstallall xkeyboard-config again. rpm -e xkeyboard-config --nodeps rm -rf etc/X11/xkb rpm -Uhv <path_to_pkg>/xkeyboard-config.rpm Then try again. Attach the new logfile.
it works with the new xorg.conf (from #48) after configuring it with sax2 again. Should the customer still try this?
Yes.
Ged: please try what Stefan said. make a backup of the working config: cp /etx/X11/xorg.conf /etc/X11/xorg.conf_work copy your old xorg.conf to /etc/X11/xorg.conf (if you don't have it anymore, use the one from #55 rpm -e xkeyboard-config --nodeps rm -rf etc/X11/xkb rpm -Uhv <path_to_pkg>/xkeyboard-config.rpm (the rpm should be on CD1/suse/noarch/)
Sorry guys; been on site coding all week (in windows!). Should have time to do this tonight. Ta Ged
I got as far as rm but then could not find the xkeyboard-config.rpm on the CD1 of beta4. Any ideas where this actually is? Ged
insert cd1, mount it, zgrep xkeyboard /mountpoint/ARCHIVES.gz should show on which cd it is, or simply reinstall it with yast.
Sorry, I found it. It was not quite called xkeyboard-config, but some variant. I did as follows: 1.Made a backup of my working xorg.conf 2.Copied in my old xorg.conf that had the problem from #55 3.ran rpm -e xkeyboard-config --nodeps OK 4.rm -rf etc/X11/xkb OK 5.Ran the RPM for the xkeyboard OK. 6.Reboot Everything was OK, the keyboard is working fine still. What was meant to happen?
Then I assume this problem won't happen any more. Reopen when a fresh installation with RC1 still triggers this keybaord problem. Thanks for testing!