LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware - Installation (https://www.linuxquestions.org/questions/slackware-installation-40/)
-   -   Problems with keyboard and test26.s (https://www.linuxquestions.org/questions/slackware-installation-40/problems-with-keyboard-and-test26-s-369767/)

jimswe 10-04-2005 03:32 PM

Problems with keyboard and test26.s
 
Hi!

I have ran into a keyboard related problem when trying to install the 2.6.13 kernel at installation (I got a wireless usb keboard). I type in test26.s at boot and the installation starts. But when Im supposed to press 1 to change keyboard layout the installer refuse any inputs. I have to plug in antoher keyboard to get on with the installation. When I have the other keyboard plugged in, the installer accepts input from the usb one as well. When the installation is finished and I boot my slack installation and are supposed to log in, the keyboard refuses to work as well. The strange thing is, the keyboard works as it is supposed to expect from those to places, keyboard layout at install and login!

Why does my keyboard behave like this?

Alien Bob 10-05-2005 01:45 PM

You could try and activate "USB legacy support" in your computer's BIOS. It might be called a little different, but the result will be that your USB keyboard will keep working after the BIOS POST finishes and before Slackware loads the USB HID support.
From what you tell, itt seems to me that this 2.6 test kernel was not compiled with support for USB input devices.

Eric

jimswe 10-05-2005 03:00 PM

Quote:

Originally posted by Alien Bob
You could try and activate "USB legacy support" in your computer's BIOS. It might be called a little different, but the result will be that your USB keyboard will keep working after the BIOS POST finishes and before Slackware loads the USB HID support.
From what you tell, itt seems to me that this 2.6 test kernel was not compiled with support for USB input devices.

Eric

Will try! But one thing that speaks against it is that I can use the usb keyboard at the boot: promt, to type in "test26.s".

Alien Bob 10-05-2005 03:04 PM

Maybe because at the time of the boot: prompt, it is still isolinux that is in control of your PC. after typing "test26.s" the 2.6 kernel will get loaded by isolinux, and takes over control.
Isolinux does have USB input support, and seemingly this 2.6test kernel does not.

Eric

jimswe 10-05-2005 03:17 PM

Quote:

Originally posted by Alien Bob
Maybe because at the time of the boot: prompt, it is still isolinux that is in control of your PC. after typing "test26.s" the 2.6 kernel will get loaded by isolinux, and takes over control.
Isolinux does have USB input support, and seemingly this 2.6test kernel does not.

Eric

Makes sense. Will try the BIOS theory ASAP.

Anonymo 10-06-2005 08:48 AM

My USB mouse didn't work on the test26 kernel.

What I did was install Slackware 10.2 with the 2.4 kernel. Then go and install the 2.6 kernel from the CD.

There is a guide on this forum.

http://www.linuxquestions.org/questi...icle&artid=487

Alien Bob 10-06-2005 01:55 PM

It says clearly in the RELEASE_NOTES that the test26.s kernel is only to be used for installation, in case you have hardware that fails to work with any of the available 2.4 kernels. Since a mouse is never used during installation, it has no need in the test26.s kernel.

You are right in that after Slackware is installed onto your computer, you can install the 2.6 kernel that you'll find in the /testing directory of the Slackware package tree. That kernel has full support for all hardware known to Linux.

Eric

jimswe 10-08-2005 08:36 AM

Quote:

Originally posted by Anonymo
My USB mouse didn't work on the test26 kernel.

What I did was install Slackware 10.2 with the 2.4 kernel. Then go and install the 2.6 kernel from the CD.

There is a guide on this forum.

http://www.linuxquestions.org/questi...icle&artid=487

All right. I did all steps in that guide but when I rebooted with the new kernel I got this:

Code:

VFS: cannot open root device "802" or unknown-block(8,2)
Please append a correct "root=" bootable option.
Kernel panic - not syncing:VFS: unable to mount root fs on unknown-block(8,2)

This is the Linux options in my lilo.conf
Code:

# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sda2
  label = Linux
  read-only
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz-generic-2.6.13
  initrd = /boot/initrd.gz
  root = /dev/sda2
  label = Linux-2.6.13
  read-only
# Linux bootable partition config ends

I get this error on both Linux kernels now...whats wrong?

Theory: Maybe I must add some SATA parameters to the mkinitrd command? If thats the case, wich ones?

sweetnsourbkr 10-12-2005 12:15 PM

I had the same error after attempting to recompile my kernel to support SMP and himem. However, after a lot of fighting with the kernel config, the system eventually gave up booting and I had to reinstall the distro. Now, with SMP enabled and himem supported, the 2.6 kernel is booting normally.

Just no USB mouse support.

I'm thinking it could be something in the kernel config, so I will have to spend some more time working with that.

/etc/lilo.conf is the same as jimswe's except for the initrd part, which I don't have.

I believe it's due to a buggy BIOS or buggy support for the MB from Linux. I'm running an nvidia nforce4 chipset, so it's fairly new. I don't believe everything is working yet, as my USB controllers tend to be flaky even in Windows. I'm hoping for a better BIOS update to come soon.

|2ainman 10-29-2005 04:29 AM

I've had a similar problem with the keyboard before. It would work fine just up until I was about to login. The keyboard would be totally dead then, no lights, nothing. I experimented by tapping the capslock key after choosing my kernel, to find out at what point exactly my keyboard stopped working. It seems to stop working when the hotplug script and/or gpm is loaded. I disabled both of those (which I won't need cuz im running a server) and on reboot the keyboard worked fine. Probably not a good solution to your problem, but maybe something to look in to.


All times are GMT -5. The time now is 04:17 PM.