In linux.debian.user, you 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. > > Any ideas? > > Thanks, > Darren > >
I looked at what is in /etc/rcS.d and what is in /etc/rc2.d and found S05keymap.sh S05keymaps-lct.sh I'm guessing that the reason it starts in Single is because these are there and I did not find them in rc2.d. That doesn't explain what happened with the upgrade, but it could have something to do with the keymap. I remember something in a recent woody (testing) upgrade that asked if I wanted to use my current config file or something like that and the word keymap was in it. I just chose the default, N, as I recall. I'm sorry that I don't recall what that was. You might be able to check if it has something to do with this, by going into Single and adding those two links into /etc/rc2.d. I just double checked and it appears that the second one is a broken link, because keymaps-lct.sh does not appear in my /etc/init.d directory. So just go to /etc/rc2.d (or whatever runlevel you use) and do: ln -s /etc/init.d/keymap.sh S05keymap.sh and see what happens when you reboot. Meanwhile, maybe someone knows where to look for the config file that might have got changed. I found something called /etc/console/boottime.kmap.gz and there is an old one too. It looks like mine was updated on the last upgrade. Maybe that has something to do with it. I don't really know how it all works; so I can't give you any real answer. Sorry. Anita
