Linked by Thom Holwerda on Fri 14th Mar 2008 20:48 UTC, submitted by Valour
Thread beginning with comment 305462
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
"The recompiled system is working well and fast. Only downsides for me:
1. Compiled in keymap (ATKBD/UKBD_DFLT_KEYMAP) doesn't work anymore.
1. Compiled in keymap (ATKBD/UKBD_DFLT_KEYMAP) doesn't work anymore.
You should probably bring this up on the stable@ mailing list and/or file a PR. "
I'll surely do that. Up to this point, I didn't have any issues with 7.0-RELEASE so far. Setting keyboard layout manually (even in SUM) works.
"2. Sun Type 6 mouse and keyboard work, but no identification string is displayed at startup (ukbd, ums), allthough entries in usbdevs database are present.
I am not sure if this is expected. It doesn't sound like it's causing any problems though. "
That is the "fascinating" part - there is no problem except the missing identification string, but the mouse and the keyboard do work without any problems, even if constantly plugged in and out. It's just.. instead of
ukbd0: Sun Microsystems Type 6 USB keyboard, rev 1.00/1.02, addr 3, iclass 3/1
ums0: Sun Microsystems Type 6 USB mouse, rev 1.00/1.02, addr 2, iclass 3/1
I get
ukbd0: <vendor 0x0430 product 0x0005, class 0/0, rev 1.00/1.02, addr 3> on uhub1
ums0: <vendor 0x0430 product 0x0100, class 0/0, rev 1.00/1.02, addr 2> on uhub1
I checked the source code and I didn't find a hint why it could be that way. Well... I'm not a skilled kernel coder, so I don't expect myself to find the problem unless it's very obvious... :-)
But if I plug in an Apple USB keyboard, it works!
ukbd0: <Mitsumi Electric Apple Extended USB Keyboard, class 0/0, rev 1.10/4.10, addr 3> on uhub4
Strange things happen in the new kernel... :-)






Member since:
2007-08-06
1. Compiled in keymap (ATKBD/UKBD_DFLT_KEYMAP) doesn't work anymore.
You should probably bring this up on the stable@ mailing list and/or file a PR.
I am not sure if this is expected. It doesn't sound like it's causing any problems though.