when you boot up when you get the boot prompt try 'linux single' to boot up to single user mode. See if that lets you use the keyboard

@gbonvehi: It seems I can't get into the "rescue console" anymore. I don't know why, I used the same boot kernel and everything as before. I mean I can boot from the Slack's CD but the same thing happens as in normal boot -> keyboard not working.
Here's the funny deal, before when I was able to go into the rescue I had a us keyboard map, but now (even in rescue console) it loads the slovene.map. I think this must be the problem but I can't seem to change it.

These are the last two lines when booting (after these two, they keyboards doesn't work anymore):

>>
loading /usr/share/kbd/keymaps/i386/qwertz/slovene.map.gz
starting gpm: /usr/sbin/gpm -m /dev/mouse - t imps2

login:
<<

@Franklin: The slovene keyboard map worked OK in the installation process.

I will try some more things but if I won't be succesfull I think I'll have to reinstall Slack without the slovene keyboard map.

Thanks, everyone.

Try with CD 2 which is actually the rescue cd Slackware provides. Or if you've another live distribution i would suggest you to try with it instead of Slack's cd.

Yes I did try with CD2.

Anyway, single (linux single) mode actually works :\ so I guess this rulles out that it might be a problem with a keymap since I was able to change it in single mode to us.keymap.
I can't think of anything else that could be causing this. I remember reading someone had the same problem but when he reinstalled he didn't install gpm and it worked. Could gpm have anything to do with this?

Well it has conflicted with people many times, personally I never had a problem with it, try: chmod -x /etc/rc.d/rc.gpm
That will make it to not execute on boot.
By the way, try to spot if the problem occurs after hotplug, maybe it loads some conflicting driver...

another thing that may cause conflicts and will give you a starting point on diagnoses is to chmod -x /etc/rc.d/rc.udev This will make it so that udev won't auto-detect harware.

OK, I did chmod -x and now it seems to work. I can use the keyboard untill I start X. I logged in and started X (started OK, even got into KDE) but neither mouse nor keyboard work in X. I guess I have to edit Xorg.conf's input devices lines to suite my needs. I have a Keytronic keyboard (102 keys?) with Windows keys and a Microsoft Optical Blue switched into USB.

Seems like we will get this to work after all

Thanks again to everyone.

Glad to hear that you got it fixed
Just to know which things did you chmod -x, gpm or udev or both?

I did gpm but I think I did that already yesterday so I don't know why it didn't work then. Maybe it was a typo

OK, I'm back

I can't get the keyboard and mouse to work in X. I've tried nearly every possibility so I'm stuck. X boots fine, even KDE loads (and works) but the damn keyboard and mouse don't work. I have tried editing xorg.conf with no luck, I ran xorgsetup and xorgconfig with various different settings and I still can't get any of them to work. The mouse should have worked because it's a "standard" Microsoft Blue optical and I never had any trouble with it on other distros (though they were running XFree).

Has anyone got a xorg.conf they could paste for this setup;

keyboard: Keytronic KT-2001 Pro
mouse: Microsoft Optical Blue
monitor: Samsung 959NF (19")
device: ATI Radeon 9800 Pro 128 MB

This could be helpful, I am still open for suggestions if this doesn't work




thanks!

hi von Vader,
have you found a solution to this problem yet? i have exactly the same problem by the sound of things. i have also tried everything suggested and googled like crazy... still nothing.

i have a standard 101 keyboard and a usb mouse also, slack10 with the 2.4.22 kernel worked fine for me so im wondering if its a kernel issue.

if anyone can help it would be much appreciated

thanks

if you have an USB mouse:

Section "InputDevice"
Identifier "Mouse"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "Buttons" "5"
Option "ZAxisMapping" "4 5"
EndSection

with your screen section:

InputDevice "Mouse" "CorePointer"

is this a usb keyboard or regular?

my keyboard section looks like this:

Section "InputDevice"

Identifier "Keyboard1"
Driver "kbd"
Option "AutoRepeat" "500 30"
Option "XkbRules" "xorg"
Option "XkbModel" "pc104"
Option "XkbLayout" "us"

EndSection

hi mAineAc

my mouse and keyboard sections seem to be fine in my xorg.conf file. i have tried absolutely everything i can think of, i even had an old xorg.conf file that was backed up from my system before i reinstalled and that still doesnt work.

thanks for the response

post /var/log/Xorg.0.log

Sorry for replying so late.

@mAineAc: thanks for that .conf I changed it a little and it worked. Has anyone noticed how wierd is the default x86conf? I can finally do "anything" now
Though I still have some problems with KDE I think I can manage that.

So thanks guys for your help!



@slackinblack: You mean the keyboard doesn't work while you start X (in KDE) or in console while you try to login? If it doesn't work in X you will have to toy around a little with xorg.conf to get it. You can try "xorgsetup" or "xorgconfigure" or just edit it by hand with mc. Maybe try to find a .conf of someone with the same keyboard/mouse as you. For me it didn't work at all and "chmod -x /etc/rc.d/rc.gpm" fixed it. I can't say more than that, I'm not the expert here