[Clfs-support] The case of the dead keyboard with the loaded driver...

[A.J. Venter]

ssh isn't an option as yet (also had that idea) since my network card
isn't working yet (onboot error says eth0 doesn't exist - I suspect a
naming error but haven't been able to get the information to debug
further).

I'll try a few tricks like single user and init=/bin/bash, maybe even
try one with devpts removed from fstab in case this is a udev issue.
Interestingly if I unplug and replug it at the login prompt I can see
the message pop up that it was found, but still no response.

I'm using the same keyboard in the host system (linux mint 17.2) to
write this mail btw.

I also believe I've ruled out the kernel almost entirely - I actually
took the backup of my previous non-multilib LFS system, copied out the
kernel, modules and firmware and placed them onto the new clfs system,
updated the bootloader and booted that - no change. That suggest a
problem happening post-kernel.

Here is my lsusb output from the host machine:
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 04d9:1603 Holtek Semiconductor, Inc. Keyboard
Bus 001 Device 004: ID 0458:014c KYE Systems Corp. (Mouse Systems)
Bus 001 Device 003: ID 0e8f:0012 GreenAsia Inc. USB Wireless 2.4GHz Gamepad
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub



On Wed, Sep 16, 2015 at 3:29 AM, William Harrington
<kb0iic at berzerkula.org> wrote:
> On Wed, 16 Sep 2015 02:12:21 +0200
> "A.J. Venter" <ajventer at gmail.com> wrote:
>
>> I haven't the foggiest idea how to debug further. I can only do so
>> much from within a chroot, but to debug it with the live kernel is
>> rather tricky when that kernel won't let me type and log in.
>>
>> Any suggestions ? I am happy to send any logs or details that will
>> help if you give me an idea what to look for.
>
> Hello,
>
> I remember someone having issues with a USB device not working. The issue was the USB ports and kernel drivers. I think it was a USB device using an XHCI port or something like that. Maybe try an EHCI or OHCI USB port. Which ports do you have? Since the keyboard works fine in the boot menu, then somewhere along the line the kernel drivers and port initialization may be causing issues.
>
> Maybe you can ssh into the machine with the kernel which has no working keyboard input and try to debug that way. Load modules, unload modules, change usb ports for the connected keyboard, and maybe that will help you figure it out. You can also try to login single user mode and see if it works very early, or maybe maintenance mode.
>
> Sincerely,
>
> William Harrington



-- 
"Semper in excretum set alta variant" - My father
A.J. Venter - http://www.silentcoder.co.za