Bug 4159 - keyboard is not functional on problematic boots
keyboard is not functional on problematic boots
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
sparc Linux
medium Severity high
: ---
: ---
Assigned To: David Lawrence
Depends On:
  Show dependency treegraph
Reported: 1999-07-22 10:25 EDT by Viraj Alankar
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-08-31 16:01:40 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Viraj Alankar 1999-07-22 10:25:04 EDT
When booting up and there is a failure to mount a
filesystem, Redhat prompts for root password or ctrl-d for
normal startup. At this point no matter what is entered it
is considered a failed password attempt. Even ctrl-d will
not work. Pressing ctrl-c a couple of times will break out
and drop to a shell prompt.
Comment 1 Jay Turner 1999-07-22 11:03:59 EDT
My guess would be that the filesystem that is having trouble getting
mounted has /etc on it, therefore no password is going to be accepted.
There is really nothing that can be done about this short of booting
from a rescue disk and trying to repair the filesystem.  Reopen this
bug if the filesystem which is having the problems is not the root
Comment 2 Viraj Alankar 1999-07-22 16:56:59 EDT
/ was mounted read-only and /etc/passwd (and shadow) were accessible
when this occurred. The mount failure was on another filesystem.
Comment 3 Bill Nottingham 1999-07-29 15:34:59 EDT
Are you using a particular keymap?
Comment 4 David Miller 1999-08-02 04:29:59 EDT
Guys, this is broken on every single Sparc install.
I detailed this to Jeff slightly over a month ago.
The net result is that any key typed in during this
phase of the boot will send incorrect keycodes to the
kernel.  This is with a default installation, it happens
every time.  My guess is that the loading of keymaps which
happens very very early on in the boot process, is what
corrupts the keyboard codes.

As an experiment to try and figure out whats wrong and
fix this, just change the root filesystem fsck with some
other application program, such as a shell, for testing
purposes.  My prediction is that you'll see the same
behavior because of something funny done by the boot time
Comment 5 Bill Nottingham 1999-08-02 11:33:59 EDT
Hmm. I can't reproduce this here on two different sparcs running
6.0 - the keyboard is fine both before and after the loadkeys.

Out of curiousity, does /etc/sysconfig/console/default.kmap look
anything like a sun keymap, or does it look totally bogus?
Comment 6 Bill Nottingham 1999-08-31 16:01:59 EDT
closed, lack of input.

Note You need to log in before you can comment on or make changes to this bug.