Karsten M. Self wrote:
on Tue, Aug 21, 2001 at 06:34:25PM +1000, Darren Marsh ([EMAIL PROTECTED])
wrote:
Karsten M. Self wrote:
on Mon, Aug 20, 2001 at 07:10:49PM +1000, Darren Marsh ([EMAIL PROTECTED])
wrote:
I updated from the testing tree 2 days ago and after all the packages
were installed the keyboard appeared to go dead. The system was still
running fine as I could telnet to it and all services appeared to be
running correctly but it would not accept any input on the console. It's
like getty isn't running even though it is.
If I boot to single user (runlevel 1) the keyboard works fine but when I
go to runlevel 2 it goes dead. The keyboard works fine on another
machine and was working fine before the update so I know it's not the
keyboard.
What's in /etc/rc2.d/ ?
S10sysklogd S20bind9 S20lpd S23ntp S99fetchmail
S11klogd S20exim S20makedev S30squid S99rmnologin
S12kerneld S20gpm S20nfs-kernel-server S50wu-ftpd
S14ppp S20inetd S20samba S89atd
S19nfs-common S20logoutd S22ntpdate S89cron
The only way I can think of to fix this is to reinstall Debian from
scratch and I'm not too keen on that idea.
Slow down, not so fast.
Boot single.
Then: Run each of the 'S*' scripts above until something breaks. I
suspect...hmm...not sure. Maybe gpm, but that's a long shot.
As a programmer I'm almost ashamed that I didn't think of something so
simple in order to locate the problem. Thank you very much. It was gpm,
it was configured for a ps/2 mouse while I have a serial mouse and ps/2
keyboard. I have the same problem when I start kdm but now I know what
path to go down.
Thanks for the suggestion too Anita now I know how the default keymap
gets loaded :-)
Thanks,
Darren
