Opened 14 years ago

Closed 5 years ago

Last modified 4 years ago

#5658 closed bug (fixed)

Microsoft Wireless Multimedia Keyboard doesn't work on kernel debugging land

Reported by: fano Owned by: mmlr
Priority: normal Milestone: R1/beta2
Component: Drivers/Keyboard/USB Version: R1/Development
Keywords: Cc: mdisreali@…
Blocked By: Blocking:
Platform: All

Description

Pressing Alt-SysReq (R Sist on the Micro$oft keyboard) - D you obtain correctly the kernel debugging land prompt (and it recognized correctly that the keyboard is USB) but then when you try to write nothing happens... you've to found a legacy PS/2 keyboard to do your operation and press "co" to return to the OS. After OS is "restarted" the wireless keyboard is working again correctly.

Maybe using a wired USB keyboard is used it works, but I not have one, I've only a legacy wired PS/2 keyboard!

Attachments (2)

listusb_am5620.txt (12.9 KB ) - added by Disreali 14 years ago.
listdev_am5620.txt (3.5 KB ) - added by Disreali 14 years ago.

Download all attachments as: .zip

Change History (15)

comment:1 by fano, 14 years ago

Component: - GeneralDrivers/Keyboard/USB
Owner: changed from nobody to mmlr

comment:2 by Disreali, 14 years ago

Cc: mdisreali@… added

comment:3 by Disreali, 14 years ago

I have the a similar issue with my wired usb keyboard. However, my system does not have any ps/2 ports, just 10 or more usb ports, so when it enters KDL or some gdb screens all I can do is do a hard-reset.

by Disreali, 14 years ago

Attachment: listusb_am5620.txt added

by Disreali, 14 years ago

Attachment: listdev_am5620.txt added

comment:4 by mmlr, 14 years ago

That's not actually a bug. Normal OS operation and KDL are two totally different things, the KDL is a highly limited environment. Only limited USB keyboard support has been implemented. For example it requires being hooked to a UHCI root port right now, so not a hub and not an OHCI controller.

in reply to:  4 ; comment:5 by Disreali, 14 years ago

Replying to mmlr:

Only limited USB keyboard support has been implemented.

Are you saying that my issue should be filed on a separate ticket?

in reply to:  5 comment:6 by mmlr, 14 years ago

Replying to Disreali:

Replying to mmlr:

Only limited USB keyboard support has been implemented.

Are you saying that my issue should be filed on a separate ticket?

No, I just added the comment to explain what's going on. The issue is most likely the same.

comment:7 by Disreali, 14 years ago

I don't know about the reporter, but now my usb keyboard works in gdb and kdl prompts on hrev36336. Thanks.

comment:8 by Disreali, 14 years ago

Correction:

If the system goes int gdb the usb keyboard works and I can use ALT+SysRq+D to bring up KDL where keyboard also works.

I system goes into KDL directly, the keyboard does not work and only recourse is a hard reset.

comment:9 by anevilyak, 14 years ago

That's a known issue that applies to all USB keyboard, for them to work in KDL you have to enter and leave KDL manually at least once first.

comment:10 by fano, 14 years ago

patch: 0

I'm trying ALHA2 now pressing ALT+SySREQ+D does nothing anymore using my USB WIreless keyboard... well maybe is best: as you MUST reboot to exit in that case.

So, sorry, it is not solved for me!

comment:11 by Disreali, 12 years ago

You may want to test again. There have been many changes in the past 19 months. On my system, I no longer need to enter and then leave KDL manually for my keyboard to work in actual KDL crashes.

comment:12 by waddlesplash, 5 years ago

Resolution: fixed
Status: newclosed

Probably fixed, no reply in 7 years.

comment:13 by nielx, 4 years ago

Milestone: R1R1/beta2

Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone

Note: See TracTickets for help on using tickets.