:: URGENT:: I use openSUSE 12.1. I was installing Virtual Box in the root user and browsing the web in another user. When I tried to switch my user, the screen hanged and I had to do a cold boot. After that, SUSE is not detecting my keyboard. On-screen keyboard is opening but not working. I can’t log in as I can’t type my password. [My keyboard is OK as it is functioning in the grub]. I have the bootable live USB of openSUSE thorugh which I had installed my OS. I could not find any repair option in it. If anyone knows how to repair using the installation media (like it is possible in Windows), please mention. It will be a great help. Another thing, my keyboard works when SUSE is booting up (as the Caps bulb is glowing when I press the Caps Lock button). But as soon as the login screen appears, the keyboard stops functioning. Please help fast as I am not being able to use my computer…
Just a thought, you can try the failsafe entry in Grub to see if it works. Or, you could enter the single number** 3** at the Grub options request and press enter. openSUSE will load, but the graphics desktop will not. You could then try login in as root and try removing the xorg file at the terminal prompt as in:
rm /etc/X11/xorg.conf
Reboot and log back in normally. If this does not help, but you find you can log in, we might determine some other files to remove or modify.
Thank You,
Thanx for the solution. I did it. OpenSUSE got loaded in CUI terminal mode. But, when I typed the command provided by you, it said, ‘no such file or directory exists’. In the grub, there is an option called Failsafe OpenSUSE… That too is opening SUSE in terminal mode but with a SUSE background.I have my installation media (Live USB). I inserted it and opened SUSE which installed in the pendrive. From there, I went to the HDD partition where my SUSE is installed and browsed through etc/X11 and found a folder ‘xorg.conf.d’ which contained 10 files. Was this the folder you were talking about? If required, I can delete it using the SUSE installed in my pen-drive.
If required, I can copy some of the files from the ‘File System’ from the SUSE installed in my pen drive to the one in my HDD.
openSUSE does not require an xorg.conf, but it can be used to modify the video and keyboard operation. The fact that it is not there is normal, but was worth a try just in case it was. Using the option of 3, keeps the desktop from loading while failsafe throws in every major fix, but reduces your operation to a very basic hardware setup, enough to work in terminal its hoped. Just for the heck of it, I wonder what happens if instead of typing a 3 as an option, you instead type in the command nomodeset, which switches you to a more basic video driver?
Thank You,
On 2012-05-26 09:56, americast wrote:
> the HDD partition where my SUSE is installed and browsed through etc/X11
> and found a folder ‘xorg.conf.d’ which contained 10 files. Was this the
> folder you were talking about? If required, I can delete it using the
> SUSE installed in my pen-drive.
No, don’t delete those.
Have a look at /var/log/Xorg.0.log and /var/log/Xorg.0.log.old (in the hard
disk), look for error messages.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Thanx for replying…
SUSE opens with nomodeset but in there too, the keyboard is not working.
In both the files you mentioned, I found this line ‘(WW) warning, (EE) error, (NI) not implemented, (??)’. No other errors I could see. [Both the files had this same line.]
Check your BIOS. Is there a setting there for USB that puts USB to legacy mode? Do you have that selected ? **
Please also confirm that you do not have a KVM switch hardware inbetween your keyboard and PC. I’ve seen this behaviour with a USB switch, where I merely needed to power cycle the KVM switch to solve the problem.
No, nothing like that. No KVM. It’s just my personal home computer (and only one computer). My keyboard is not a USB one. There is a special port for it (little circular in shape).
It reads that your keyboard is a PS2 keyboard and that it does happen to work in run level 3 (the full screen terminal mode you referred to).
You could reboot your PC, and press ‘3’ (no quotes) when the full screen menu appears such that there is a ‘3’ in the options line after the vga entry (with a space in between) and then boot your PC to the full screen terminal mode. Then login as a regular user to this full screen terminal mode. After logging in, type ‘su’ (no quotes) and enter root password. And then with root permissions, type ‘yast’ and see if you can configure your PC with that. ( yast > hardware > system keyboard settings ).
Or you could try yast > software > software management and install sax3 and then after sax3 is installed, run sax3 by typing ‘su’ (enter root password) followed by typing ‘sax3’ and see if you can use sax3 to help configure your keyboard.
You can navigate yast by using the arrow keys, enter key, tab key, and spacebar.
On 2012-05-27 11:56, oldcpu wrote:
>
> It reads that your keyboard is a PS2 keyboard and that it does happen to
> work in run level 3 (the full screen terminal mode you referred to).
>
> You could reboot your PC, and press ‘3’ (no quotes) when the full
> screen menu appears such that there is a ‘3’ in the options line after
> the vga entry (with a space in between) and then boot your PC to the
> full screen terminal mode. Then login as a regular user to this full
> screen terminal mode. After logging in, type ‘su’ (no quotes) and enter
> root password. And then with root permissions, type ‘yast’ and see if
> you can configure your PC with that. ( yast > hardware > system keyboard
> settings ).
In text mode you can log in directly as root, the warning about not login
as root do not apply to this mode (you get the same powers and dangers the
instant you do “su”)
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Hello… any more ideas???..
In yast > hardware, there is no system keyboard settings but system keyboard layout option is present. I don’t think that will be able to solve my problem. I installed sax3 but when I am opening it, there is only a blue screen with a blue rectangle with white borders. When i press any key, terminal shows, ‘Segmentation fault’. I can try and reinstall it, but I can’t understand some of the yast symbols. In Yast, Sax3 can be seen but how to uninstall? In the first coloumn, ‘i’ is written, which I think means installed. When I press enter, ‘i’ becomes ‘>’ and again on pressing enter, it becomes ‘-’. Which one of ‘>’ and ‘-’ mean uninstall?
Sadly it appears even before it was complete, support for sax3 was dropped and it appears to be no longer maintained. Its most unfortunate.
To remove sax3 , simply type with root permissions:
rpm -e sax3
I have no further suggestions for your PS2keyboard problem. Can you try a USB-2.0 keyboard ?
On 2012-05-28 10:46, americast wrote:
> In Yast,
> Sax3 can be seen but how to uninstall? In the first coloumn, ‘i’ is
> written, which I think means installed. When I press enter, ‘i’ becomes
> ‘>’ and again on pressing enter, it becomes ‘-’. Which one of ‘>’ and
> ‘-’ mean uninstall?
Did you not see the help button?
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Today, I am a little away from my computer, so I cant access in right now… I will be back in 2-3 days. But I had noticed one thing, ie, when failsafe used to start, a line, something like ‘VIrtual Box failed to start’, used to appear. So I feel that all these problems are happening due to VB… So please tell me how to uninstall a s/w from yast …for apps which get listed ion yast, in the first coloumn, ‘i’ is written, which I think means installed. When I press enter, ‘i’ becomes ‘>’ and again on pressing enter, it becomes ‘-’. Which one of ‘>’ and ‘-’ mean uninstall?
On 2012-05-29 16:46, americast wrote:
>
> Today, I am a little away from my computer, so I cant access in right
> now… I will be back in 2-3 days. But I had noticed one thing, ie, when
> failsafe used to start, a line, something like ‘VIrtual Box failed to
> start’, used to appear. So I feel that all these problems are happening
> due to VB…
Is this a guest installation inside virtualbox inside another host system?
If so, ask in the virtualbox forum about your keyboard problem.
If not, ignore the message.
So please tell me how to uninstall a s/w from yast …for
> apps which get listed ion yast, in the first coloumn, ‘i’ is written,
> which I think means installed. When I press enter, ‘i’ becomes ‘>’ and
> again on pressing enter, it becomes ‘-’. Which one of ‘>’ and ‘-’ mean
> uninstall?
Again, did you not see the help button? It is explained there. I will not
explain lest I make a mistake.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
The " ‘-’ " or -] means delete (same as uninstall which is Windows terminology) and ‘>’ means update.
Sorry. Since I was out of station, I could not reply. I have uninstalled Sax3 using yast. I clearly remember having Virtual Box 4.1 installed in my user (not root). But in yast, I see that it is not installed. Is there any way I can identify if it is installed (might be something like hidden)?
[My SUSE is not installed in VB but I was trying to install VB in my SUSE so as to be able to run other OS in my SUSE].