Suse/NovellThis Forum is for the discussion of Suse Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I tried installing Suse 10.3 some hours before - it went through w/o any problems and I even got the "Installation complete! Login to start working" sort of message.
However, the first few login trials failed, because right after the first key was depressed, the same letter continued getting typed infinitely!!??
A few reboots later, and instead of using the graphical option (using the Ctrl-Alt-F*), the problem acquired a different level - this time, the keyboard froze - as in, simply refused to accept any input even for the username!!
Ultimately, after ~ 5 of such wierd runs, I was finally able to login in the graphical mode (which took a veeery long time, though). Nevertheless, it was all back to square one, when I opened a terminal because the infinite-key-repetition-phenomena occurred again!
Right now, I'm working in the fail-safe option, which is running absolutely fine! Loading/re-installing the "keyboard" modules/drivers in yast here doesn't help - trying to login into normal mode still gives at least one out of all possible permutations of the problems listed above..
Please let me know what could be possibly wrong! I've a 500 GB HDD (was thrusted to use it, so don't have an alternative) - could such a high storage capacity be the cause of this instability?
I upgraded from Suse 10.2 to 10.3 yesterday and I'm experiencing something similar.
The keyboard is frozen or giving a keystroke multiple times. (I also kept rebooting). Only a very few times it seems to work fine.
I'm running on Asus a7n8-Deluxe rev2 (yes it's old... ;-) and CPU is an Athlon 2200+ - Keyboard is a PS2 connected wireless desktop from Logitech.
With 10.2 I haven't seen anything like that.
I tried changing the keyboard to a wired version but that didn't make any difference. I tried to play around with the bios settings on keyboard parameters (disabling USB support etc.) but that didn't help neither.
So if anyone should have some hints or ideas how to check the keyboard settings, please share. I would appreciate that.
I tried to use the system paramters you posted here. - Did not work for me :-(
What I found is the following:
I started the system with parameter "3" to get to runlevel 3
Keyboard works - I can log in as "root"
I switched to runlevel 5 (by typing "init 5")
When graphical interface comes up I have the keyboard available and can log in as expected.
I tried this twice and it worked both times. So I at least have a workaround for the time being but to me this looks a bit weird...
Having exactly the same problem as described here, after upgrading from 10.2 to 10.3
I have found that when the problem occurs, if you switch out to a virtual terminal, with, say ctrl-alt-f1, and then switch back to the graphical terminal, with ctrl-alt-f7, then the problem goes away until the next reboot.
>> Oh, another workaround is to edit
>> KBD_TTY="tty1 tty2 tty3 tty4 tty5 tty6 tty10"
>> on my system it was set to:
>> KBD_TTY="tty1 tty2 tty3 tty4 tty5 tty6 tty7 tty8 tty9 tty10 tty12 tty13 tty14 tty15 tty16 tty17 tty18 tty19 tty20"