Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 200
  • Last Modified:

Cannot type at login at boot

A while ago I tried to shutdown Slackware from inside KDE and one of the apps hung (Knemo).
When I rebooted, slackware performed a check and said Duplicate or bad block in use and then it just stopped.

Because I was just testing slackware out, I formatted the partition and install Slackware 10.0 again.

The installation worked perfectly. You're asked to remove the cd-rom and press ctrl+alt+delete to reboot, no problem so far.

But now something strange happened, I cannot type anymore at the login. It just completely ignores anything I type. Even pressing NumLock doesn't do anything (no LEDs lighting up).

I tried installing it again and again, and every time it's the same. Even if I try to go directly to KDE (at Lilo I choose another runlevel: 4). If xorg is configured, it hung at the login screen of KDE

my keyboard is connected via PS/2 and hotplug is running, so I guess it should work.

the most weird thing is that at one time I installed it, it did work. but then I got into KDE and it hung again

even if I turn num-lock on at booting, I can't even turn it off. So it doesn't look like it just doesn't find my keyboard, but it looks like it crashed.
0
nemesis3884
Asked:
nemesis3884
  • 2
1 Solution
 
alericCommented:
This is not a complete answer, because I never had this problem...
but I can tell you what I'd do in your case :/

First, I'd login into the computer using another PC on the same network;
or when that is impossible - I'd find on the net the information about
what to type on the lilo boot prompt to start the PC in bootlevel 1
(single user mode) and hope that the keyboard worked in that mode
of course; if not, I'd try a different keyboard. If that also didn't work,
then I'd get a boot/rescue disk and try to get working access that way
and when that also didn't work then I'd get a boot/root disk (thus,
totally independend of what's on your harddisk).

When thus I'd have access to the running OS, I'd look at
/var/log/messages for any error messages concerning the keyboard
(drivers).  Also type the command 'dmesg' and see if there are errors
there. Next, I'd look in /proc and figure out if the keyboard was detected
at all.  Once I found out that it was detected and the correct driver for
it was loaded (this might mean you have to reconfigure and recompile
the kernel) it would either work I assume, or I'd have a new error that
I could work from.
0
 
nemesis3884Author Commented:
I will try
0
 
nemesis3884Author Commented:
I haven't had the time to test your tips, so maybe it could stay open a little longer
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now