Author Topic: model m & blue cube needs to be plugged in again after linux boot  (Read 1342 times)

0 Members and 1 Guest are viewing this topic.

Offline fuchs

  • Thread Starter
  • Posts: 1
model m & blue cube needs to be plugged in again after linux boot
« 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

Offline snoopy

  • The Flying Ace
  • * Elevated Elder
  • Posts: 1828
  • Location: Industrial Environment
  • Gone with the Wind
Re: model m & blue cube needs to be plugged in again after linux boot
« Reply #1 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.

Offline Hellmark

  • Posts: 349
  • Location: Maryland Heights, Mo, USA
Re: model m & blue cube needs to be plugged in again after linux boot
« Reply #2 on: Mon, 18 November 2013, 06:58:06 »
What does dmesg show?

Offline terran5992

  • Posts: 1485
  • Location: Singapore
  • One With The Cup Rubber
Re: model m & blue cube needs to be plugged in again after linux boot
« Reply #3 on: Mon, 18 November 2013, 07:04:16 »
Whats a blue cube?

Listokei Custom  |  HHKB Pro 2  |  Topre Realforce 103UBH  |  Armageddon MKA-3


Offline tuxsavvy

  • Posts: 441
  • 白HHKBの魔法使い
Re: model m & blue cube needs to be plugged in again after linux boot
« Reply #4 on: Mon, 18 November 2013, 10:55:21 »
Whats a blue cube?

I believe they are referring to this as a "blue cube".

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.
HHKB Pro JP Type-S | Northgate Omnikey 101 | APC/"Clicker" F-21 (GOG3YL) | Cherry G80-5000 HAMDE

僕の日本語が下手です。我的中文也一樣爛。

Offline E TwentyNine

  • Posts: 884
    • Some of My Keyboards
Re: model m & blue cube needs to be plugged in again after linux boot
« Reply #5 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.
Daily driver: SSK or Tenkeyless IBM AT
1984 Model M Industrial Prototype ⌨ 1992 Black Oval Industrial SSK ⌨ 1982 5251 Beam Spring ⌨ 89 Key "SSK" ⌨ M13 triplets