Beneath
11-22-2002, 09:51 AM
Hello, i'm cross posting here. Eek.
But i just thought maybe no one replied to a post in the other one because it was mis-placed.
If no one has an idea, maybe you could recomend another forum/ng about this kind of stuff?
I'll set up Pan and search round usenet in a bit...
Quote:
--
Bit of a weird problem here.
Everything is working fine, but keyboard suddenly stops accepting any input.
Changed a lot of things lately, now using:
Slack 8.1 (8.0 before)
Custom kernel 2.4.19
Different mobo to what i was before, with a different keyboard too (because new mobo had ps2 socket)
Different processor and ram too, but i doubt that makes a difference.
When it happens, i can move the mouse about (USB), go about my normal business... except no keyboard. It's not just X that stops accepting it, i tried doing ctrl-alt-Fx to get into a normal shell and it wouldn't work.
I also ssh'ed in from another machine (which worked fine btw), killed X, and tried to type on the console. No worky. I then proceeded to kill every process (from the remote machine) that had been started since i logged in, to see if any of them were causing the problem. Nothing changed.
I thought i was going to have to reboot, but then i unplugged the keyboard, plugged it back in, and it worked.
Uhh?
It is quite an old keyboard (a nice old clicky DELL thing from pre-winkey days), but even so, could that cause it to hang like that?
As far as i can think... there is no driver issues that could be causing this, because doesn't the kernel get keyboard input scancodes directly from the BIOS?
Any suggestions welcome.
If anyone thinks it *could* be the actual keyboard itself, then i'll go and buy a new one tomorrow... but i can't see how it can be myself.
Thanks for any help.
But i just thought maybe no one replied to a post in the other one because it was mis-placed.
If no one has an idea, maybe you could recomend another forum/ng about this kind of stuff?
I'll set up Pan and search round usenet in a bit...
Quote:
--
Bit of a weird problem here.
Everything is working fine, but keyboard suddenly stops accepting any input.
Changed a lot of things lately, now using:
Slack 8.1 (8.0 before)
Custom kernel 2.4.19
Different mobo to what i was before, with a different keyboard too (because new mobo had ps2 socket)
Different processor and ram too, but i doubt that makes a difference.
When it happens, i can move the mouse about (USB), go about my normal business... except no keyboard. It's not just X that stops accepting it, i tried doing ctrl-alt-Fx to get into a normal shell and it wouldn't work.
I also ssh'ed in from another machine (which worked fine btw), killed X, and tried to type on the console. No worky. I then proceeded to kill every process (from the remote machine) that had been started since i logged in, to see if any of them were causing the problem. Nothing changed.
I thought i was going to have to reboot, but then i unplugged the keyboard, plugged it back in, and it worked.
Uhh?
It is quite an old keyboard (a nice old clicky DELL thing from pre-winkey days), but even so, could that cause it to hang like that?
As far as i can think... there is no driver issues that could be causing this, because doesn't the kernel get keyboard input scancodes directly from the BIOS?
Any suggestions welcome.
If anyone thinks it *could* be the actual keyboard itself, then i'll go and buy a new one tomorrow... but i can't see how it can be myself.
Thanks for any help.