geekhack

geekhack Community => Keyboards => Topic started by: fuchs on Mon, 18 November 2013, 05:48:22

Title: model m & blue cube needs to be plugged in again after linux boot
Post by: fuchs on Mon, 18 November 2013, 05:48:22

Hi,
I have recently gotten my first Model M(1391403). I am using it in combination with the blue cube adapter, which is working fine.
After booting, i can use the keyboard to make selections in GRUB. However, as soon as debian starts, i am no longer able to use it. Unplugging it and plugging it in again fixes the problem. Has anyone else encountered this, or knows a solution to it?

BTW, this is how the blue cube is registered by lsusb:
Bus 001 Device 014: ID 0d3d:0001 Tangtop Technology Co., Ltd HID Keyboard

Title: Re: model m & blue cube needs to be plugged in again after linux boot
Post by: snoopy on Mon, 18 November 2013, 06:34:56

had the same problem with ubuntu in combination with ssk and bluecube... but I never really looked for a solution, cause I didn't reboot that often... :)

I know, not really helpful... but at least now you know that you're not the only one.

Title: Re: model m & blue cube needs to be plugged in again after linux boot
Post by: Hellmark on Mon, 18 November 2013, 06:58:06

What does dmesg show?

Title: Re: model m & blue cube needs to be plugged in again after linux boot
Post by: terran5992 on Mon, 18 November 2013, 07:04:16

Whats a blue cube?

Title: Re: model m & blue cube needs to be plugged in again after linux boot
Post by: tuxsavvy on Mon, 18 November 2013, 10:55:21

Quote from: terran5992 on Mon, 18 November 2013, 07:04:16

Whats a blue cube?

I believe they are referring to this as a "blue cube" (http://www.amazon.com/gp/product/B000BSJFJS/ref=s9_simh_gw_p23_i1?pf_rd_m=ATVPDKIKX0DER&pf_rd_s=center-2&pf_rd_r=1908CC5H97TXY4FTEF57&pf_rd_t=101&pf_rd_p=470938631&pf_rd_i=507846).

Source:
http://geekhack.org/index.php?topic=28386.0
http://geekhack.org/index.php?topic=9892.0

As to the OP, I don't have a model M keyboard neither do I use a blue cube, the only thing that is remotely related is by me running linux (Arch here). I am guessing it is something to do with USB initialisation and the need to possibly force load it up at boot. Under Archlinux such is probably doable via mkinitcpio if the USB is compiled as a kernel module (something like {e,h,o}hci_hcd).

It might also be udev starting a bit late (but I am leaning to an unlikely scenario). When you (OP) said that you cannot use the keyboard again after making your selection at GRUB menu. Was it right up to when the machine is fully booted or during the bootup phase? If it is bootup phase only that you cannot access your keyboard it would most likely be the USB as kernel module is not initialised as mentioned above. Otherwise it might be a conflict somewhere which may cause it.

Though I would agree with what Hellmark says, dmesg is usually very useful for finding out the booting sequence and for other general purpose troubleshooting.

Title: Re: model m & blue cube needs to be plugged in again after linux boot
Post by: E TwentyNine on Mon, 18 November 2013, 13:13:22

If it is plugged into a USB-3 port, try using a USB-2 port instead if you have one.