[Clfs-support] Unable to login Keyboard not responding

Ian Macdonald iamacdo at gmail.com
Mon Mar 5 16:37:04 PST 2012


Hi,

Just completed CLFS Multilib build using Version 1.2.0 book without any
major problems in the chroot environment.
Copied the new kernel to a pre-existing /boot partition and modified
menu.lst to boot with per-existing grub.
The kernel appears to load but the bootscripts initially failed with a
checkfs error '..Press Enter to Continue'.

Pressing Enter does nothing.

After removing the fsck option from fstab the boot scripts run without
error to the login prompt but I can't enter a
username; the keyboard appears not to be responding. The only thing that
works is the reboot button.

The syslog file is written and looks ok; the only reference to keyboards is

            kernel: [    1.561827] serio: i8042 KBD port at 0x60,0x64 irq 1

and the only errors are

EXT3-fs (sda5): error: couldn't mount because of unsupported optional
features (240)
2012-03-04T17:15:30.099106+10:00 naked kernel: [    2.119196] EXT4-fs
(sda5): couldn't mount as ext2 due to feature incompatibilities
2012-03-04T17:15:30.099107+10:00 naked kernel: [    2.124038] EXT4-fs
(sda5): INFO: recovery required on readonly filesystem
2012-03-04T17:15:30.099164+10:00 naked kernel: [    2.124815] EXT4-fs
(sda5): write access will be enabled during recovery
2012-03-04T17:15:30.099165+10:00 naked kernel: [    2.130172] EXT4-fs
(sda5): recovery complete
2012-03-04T17:15:30.099167+10:00 naked kernel: [    2.131069] EXT4-fs
(sda5): mounted filesystem with ordered data mode. Opts: (null)

which seems to resolve itself and googling suggests it is not a problem. (
The syslog gets written to sda5 so it appears to be mounted ).

I have set udev.conf to 'debug' and get pages of output, the only mention
of errors being

           'error: /dev/sde: No medium found'

which doesn't look like a problem.

After a day and a half of recompiling the kernel (3.2.9), rebooting and
trying to follow the bootscript process (by inserting 'sleep' ) I'm out of
ideas.

Where and how does the keyboard get 'loaded' or the problem somewhere else?

Any pointers would be much appreciated.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clfs.org/pipermail/clfs-support-clfs.org/attachments/20120306/4959d430/attachment.html>


More information about the Clfs-support mailing list