LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware - Installation (http://www.linuxquestions.org/questions/slackware-installation-40/)
-   -   Keyboard typing doubles when x86 installer is booted (http://www.linuxquestions.org/questions/slackware-installation-40/keyboard-typing-doubles-when-x86-installer-is-booted-4175467485/)

YellowApple 06-26-2013 12:18 PM

Keyboard typing doubles when x86 installer is booted
 
Howdy,

I'm trying to install Slackware 14.0 on a rather low-spec machine (DT Research WebDT DT160 client) for use as a basic web kiosk, using UNetBootin to create a bootable USB stick from the Slackware 14.0 DVD .iso. The USB stick boots fine, and it reaches the keyboard layout prompt; however, I'm stuck there, since from that point forward, every keypress is repeated once, resulting in, say, 'aa' instead of 'a' or 'ffddiisskk' instead of 'fdisk'. Arrow keys and backspace also produce doubles, making it remarkably difficult to actually proceed with the installation.

Any ideas?

What I've managed to observe:
  • I've installed Slackware on a DT160 before with no problems. The previous DT160, however, had a different hardware configuration (video outputs for TVs), and I believe a different BIOS version.
  • This is a USB keyboard. I've tried with multiple keyboards; same results each time.
  • The machine lacks a PS/2 port, and I lack a PS/2<->USB adapter, so I am unable to test with a PS/2 keyboard at this time.
  • The BIOS setup menu works fine; keypresses don't abnormally repeat. This seems to rule out a hardware issue, though I'm wondering if there's a BIOS setting I might be able to tweak.
    • Disabling legacy USB support doesn't help
    • Disabling EHCI support makes the boot process excruciatingly slow and still does not solve the problem.
    • I haven't tried disabling USB 2.0 and forcing USB 1.1 operation.
  • The Windows XP Embedded Edition currently installed works fine.
  • The Debian 7.1.0 DVD installer (as a USB stick) is slow to initialize the USB keyboard, but once it does, it works fine, with no double-typing.

Didier Spaier 06-26-2013 05:41 PM

I don't know if UNetBootin would make a plausible culprit, but just in case you could either try a PXE install (just boot on a Slackware DVD on another box linked to the low-spec one by a cross Ethernet cable and type 'pxesetup' instead of 'setup', then follow instructions) or make a bootable USB stick possibly including the packages, with instructions provided here:
http://mirrors.slackware.com/slackwa...xe-installers/

YellowApple 06-27-2013 12:53 PM

Quote:

Originally Posted by Didier Spaier (Post 4979252)
I don't know if UNetBootin would make a plausible culprit, but just in case you could either try a PXE install (just boot on a Slackware DVD on another box linked to the low-spec one by a cross Ethernet cable and type 'pxesetup' instead of 'setup', then follow instructions) or make a bootable USB stick possibly including the packages, with instructions provided here:
http://mirrors.slackware.com/slackwa...xe-installers/

I'll try that; it'll involve me setting up a second workstation to run pxesetup, but that shouldn't be terribly difficult.

Diantre 06-27-2013 02:44 PM

I experienced something similar some time ago, in my case it was caused by the keyboard repeat rate setting in the BIOS set too high. I don't know if this would apply in your case, but it might be worth investigating. Good luck.

TracyTiger 06-27-2013 11:25 PM

Quote:

Originally Posted by YellowApple (Post 4979104)
... every keypress is repeated once, resulting in, say, 'aa' instead of 'a' or 'ffddiisskk' instead of 'fdisk'.
  • I've installed Slackware on a DT160 before with no problems. The previous DT160, however, had a different hardware configuration (video outputs for TVs), and I believe a different BIOS version.

Hi Ryan. Welcome to the Slackware section of LQ.

Just to clarify ...

Are the repeated characters being sent to the system or are they just echoed on the screen?

That is, does typing "ls" result in an error about "llss" not found?

YellowApple 06-27-2013 11:45 PM

Quote:

Originally Posted by Diantre (Post 4979799)
I experienced something similar some time ago, in my case it was caused by the keyboard repeat rate setting in the BIOS set too high. I don't know if this would apply in your case, but it might be worth investigating. Good luck.

The BIOS does have a keyboard repeat function, but setting it doesn't seem to have any positive effect.

Quote:

Originally Posted by Tracy Tiger (Post 4980002)
Hi Ryan. Welcome to the Slackware section of LQ.

Just to clarify ...

Are the repeated characters being sent to the system or are they just echoed on the screen?

That is, does typing "ls" result in an error about "llss" not found?

I don't recall if it did; once I get back to work (I'm at home right now), I'll test. I'm inclined to say they're being sent, since the enter/return key doubles as well (causing the install environment to blow through the login prompt when one presses Enter to pass through the keyboard layout selection).

Also, interesting that you know my name; I suppose I have it displayed somewhere on this site... :P

TracyTiger 06-28-2013 01:05 AM

User Standards
 
Quote:

Originally Posted by YellowApple (Post 4980010)
Also, interesting that you know my name;

There are user standards that must be met for Slackware users. A background check is done on all new Slackware users. That's how we know all about you. If users don't meet the standards then their Slackware installation is corrupted and they aren't allowed to get Slackware successfully working.

You may have read that Slackware has a reputation for being difficult to install and get working? It's because a lot of people didn't meet the Slackware user standards.


Your previous post.

YellowApple 06-28-2013 03:45 AM

Quote:

Originally Posted by Tracy Tiger (Post 4980046)
There are user standards that must be met for Slackware users. A background check is done on all new Slackware users. That's how we know all about you. If users don't meet the standards then their Slackware installation is corrupted and they aren't allowed to get Slackware successfully working.

You may have read that Slackware has a reputation for being difficult to install and get working? It's because a lot of people didn't meet the Slackware user standards.


Your previous post.

Ah, that's right. Well, nice to know that folks around here actually care enough to reference prior posts, rather than my prior suspicion that the Penguin Cabal is on my tail again.

Thanks for the warm welcome :)


All times are GMT -5. The time now is 11:36 PM.