Bug#523867: xinput: Notebook Keyboard lost after normal bootup
Hi all! After noticing, that my ACPI problem was caused by splash being installed, I removed splashy from this machine. After rebooting my keyboard is now back -- so this is possibly another «duplicate» of the splashy bugs. Regards Christoph -- /\ ASCII Ribbon : GPG-Key ID: 0x0372275D \ /Campaign : X against HTML : Working for Debian / \ in eMails : http://www.debian.org/ http://www.christoph-egger.org/ signature.asc Description: Digital signature
Bug#523867: xinput: Notebook Keyboard lost after normal bootup
Hi! I just discovered, that my USB Keyboard is not working in X as well if it was plugged in on boot. I had to reconnect it to have X getting the input. Regards Christoph -- /\ ASCII Ribbon : GPG-Key ID: 0x0372275D \ /Campaign : X against HTML : Working for Debian / \ in eMails : http://www.debian.org/ http://www.christoph-egger.org/ signature.asc Description: Digital signature
Bug#523867: xinput: Notebook Keyboard lost after normal bootup
On Tue, 2009-04-14 at 14:24 +0200, Christoph Egger wrote: Hi! I just discovered, that my USB Keyboard is not working in X as well if it was plugged in on boot. I had to reconnect it to have X getting the input. Do the corresponding device files in /dev/input/ exist? If yes, what does 'evtest' (from the joystick package) report about them? Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523867: xinput: Notebook Keyboard lost after normal bootup
On Tue, Apr 14, 2009 at 01:58:40PM +0100, Julien Cristau wrote: On Tue, 2009-04-14 at 14:24 +0200, Christoph Egger wrote: Hi! I just discovered, that my USB Keyboard is not working in X as well if it was plugged in on boot. I had to reconnect it to have X getting the input. Do the corresponding device files in /dev/input/ exist? If yes, what does 'evtest' (from the joystick package) report about them? OK. Theusb keyboard should have /dev/input/event7 but it is not there untill I reconnect it. The output of evtest on event7 is attached as well as the output for event3, which is the internal keyboard which *is* present while not working. -- /\ ASCII Ribbon : GPG-Key ID: 0x0372275D \ /Campaign : X against HTML : Working for Debian / \ in eMails : http://www.debian.org/ http://www.christoph-egger.org/ Input driver version is 1.0.0 Input device ID: bus 0x11 vendor 0x1 product 0x1 version 0xab54 Input device name: AT Translated Set 2 keyboard Supported events: Event type 0 (Sync) Event type 1 (Key) Event code 1 (Esc) Event code 2 (1) Event code 3 (2) Event code 4 (3) Event code 5 (4) Event code 6 (5) Event code 7 (6) Event code 8 (7) Event code 9 (8) Event code 10 (9) Event code 11 (0) Event code 12 (Minus) Event code 13 (Equal) Event code 14 (Backspace) Event code 15 (Tab) Event code 16 (Q) Event code 17 (W) Event code 18 (E) Event code 19 (R) Event code 20 (T) Event code 21 (Y) Event code 22 (U) Event code 23 (I) Event code 24 (O) Event code 25 (P) Event code 26 (LeftBrace) Event code 27 (RightBrace) Event code 28 (Enter) Event code 29 (LeftControl) Event code 30 (A) Event code 31 (S) Event code 32 (D) Event code 33 (F) Event code 34 (G) Event code 35 (H) Event code 36 (J) Event code 37 (K) Event code 38 (L) Event code 39 (Semicolon) Event code 40 (Apostrophe) Event code 41 (Grave) Event code 42 (LeftShift) Event code 43 (BackSlash) Event code 44 (Z) Event code 45 (X) Event code 46 (C) Event code 47 (V) Event code 48 (B) Event code 49 (N) Event code 50 (M) Event code 51 (Comma) Event code 52 (Dot) Event code 53 (Slash) Event code 54 (RightShift) Event code 55 (KPAsterisk) Event code 56 (LeftAlt) Event code 57 (Space) Event code 58 (CapsLock) Event code 59 (F1) Event code 60 (F2) Event code 61 (F3) Event code 62 (F4) Event code 63 (F5) Event code 64 (F6) Event code 65 (F7) Event code 66 (F8) Event code 67 (F9) Event code 68 (F10) Event code 69 (NumLock) Event code 70 (ScrollLock) Event code 71 (KP7) Event code 72 (KP8) Event code 73 (KP9) Event code 74 (KPMinus) Event code 75 (KP4) Event code 76 (KP5) Event code 77 (KP6) Event code 78 (KPPlus) Event code 79 (KP1) Event code 80 (KP2) Event code 81 (KP3) Event code 82 (KP0) Event code 83 (KPDot) Event code 85 (Zenkaku/Hankaku) Event code 86 (102nd) Event code 87 (F11) Event code 88 (F12) Event code 89 (RO) Event code 90 (Katakana) Event code 91 (HIRAGANA) Event code 92 (Henkan) Event code 93 (Katakana/Hiragana) Event code 94 (Muhenkan) Event code 95 (KPJpComma) Event code 96 (KPEnter) Event code 97 (RightCtrl) Event code 98 (KPSlash) Event code 99 (SysRq) Event code 100 (RightAlt) Event code 102 (Home) Event code 103 (Up) Event code 104 (PageUp) Event code 105 (Left) Event code 106 (Right) Event code 107 (End) Event code 108 (Down) Event code 109 (PageDown) Event code 110 (Insert) Event code 111 (Delete) Event code 112 (Macro) Event code 113 (Mute) Event code 114 (VolumeDown) Event code 115 (VolumeUp) Event code 116 (Power) Event code 117 (KPEqual) Event code 118 (KPPlusMinus) Event code 119 (Pause) Event code 121 (KPComma) Event code 122 (Hanguel) Event code 123 (Hanja) Event code 124 (Yen) Event code 125 (LeftMeta) Event code 126 (RightMeta) Event code 127 (Compose) Event code 128 (Stop) Event code 140 (Calc) Event code 142 (Sleep) Event code 143 (WakeUp) Event code 155 (Mail) Event code 156 (Bookmarks) Event code 157 (Computer) Event code 158 (Back) Event code 159 (Forward) Event code 163 (NextSong) Event code 164 (PlayPause) Event code 165 (PreviousSong) Event code 166 (StopCD) Event code 172 (HomePage) Event code 173 (Refresh) Event code 183 (F13) Event code 184 (F14) Event code 185 (F15) Event code 217 (Search) Event code 226 (Media) Event type 4 (Misc) Event code 4 (ScanCode) Event type 17 (LED) Event code 0 (NumLock) Event code 1 (CapsLock) Event code 2 (ScrollLock) Even signature.asc Description: Digital signature
Bug#523867: xinput: Notebook Keyboard lost after normal bootup
On Tue, Apr 14, 2009 at 03:40:21PM +0200, Christoph Egger wrote: On Tue, Apr 14, 2009 at 01:58:40PM +0100, Julien Cristau wrote: On Tue, 2009-04-14 at 14:24 +0200, Christoph Egger wrote: Hi! I just discovered, that my USB Keyboard is not working in X as well if it was plugged in on boot. I had to reconnect it to have X getting the input. Do the corresponding device files in /dev/input/ exist? If yes, what does 'evtest' (from the joystick package) report about them? OK. Theusb keyboard should have /dev/input/event7 but it is not there untill I reconnect it. The output of evtest on event7 is attached as well as the output for event3, which is the internal keyboard which *is* present while not working. So the event7 file was actually empty for no obvious reason ... reattached -- /\ ASCII Ribbon : GPG-Key ID: 0x0372275D \ /Campaign : X against HTML : Working for Debian / \ in eMails : http://www.debian.org/ http://www.christoph-egger.org/ Input driver version is 1.0.0 Input device ID: bus 0x3 vendor 0x1241 product 0x1503 version 0x110 Input device name: USB Keyboard Supported events: Event type 0 (Sync) Event type 1 (Key) Event code 1 (Esc) Event code 2 (1) Event code 3 (2) Event code 4 (3) Event code 5 (4) Event code 6 (5) Event code 7 (6) Event code 8 (7) Event code 9 (8) Event code 10 (9) Event code 11 (0) Event code 12 (Minus) Event code 13 (Equal) Event code 14 (Backspace) Event code 15 (Tab) Event code 16 (Q) Event code 17 (W) Event code 18 (E) Event code 19 (R) Event code 20 (T) Event code 21 (Y) Event code 22 (U) Event code 23 (I) Event code 24 (O) Event code 25 (P) Event code 26 (LeftBrace) Event code 27 (RightBrace) Event code 28 (Enter) Event code 29 (LeftControl) Event code 30 (A) Event code 31 (S) Event code 32 (D) Event code 33 (F) Event code 34 (G) Event code 35 (H) Event code 36 (J) Event code 37 (K) Event code 38 (L) Event code 39 (Semicolon) Event code 40 (Apostrophe) Event code 41 (Grave) Event code 42 (LeftShift) Event code 43 (BackSlash) Event code 44 (Z) Event code 45 (X) Event code 46 (C) Event code 47 (V) Event code 48 (B) Event code 49 (N) Event code 50 (M) Event code 51 (Comma) Event code 52 (Dot) Event code 53 (Slash) Event code 54 (RightShift) Event code 55 (KPAsterisk) Event code 56 (LeftAlt) Event code 57 (Space) Event code 58 (CapsLock) Event code 59 (F1) Event code 60 (F2) Event code 61 (F3) Event code 62 (F4) Event code 63 (F5) Event code 64 (F6) Event code 65 (F7) Event code 66 (F8) Event code 67 (F9) Event code 68 (F10) Event code 69 (NumLock) Event code 70 (ScrollLock) Event code 71 (KP7) Event code 72 (KP8) Event code 73 (KP9) Event code 74 (KPMinus) Event code 75 (KP4) Event code 76 (KP5) Event code 77 (KP6) Event code 78 (KPPlus) Event code 79 (KP1) Event code 80 (KP2) Event code 81 (KP3) Event code 82 (KP0) Event code 83 (KPDot) Event code 86 (102nd) Event code 87 (F11) Event code 88 (F12) Event code 89 (RO) Event code 92 (Henkan) Event code 93 (Katakana/Hiragana) Event code 94 (Muhenkan) Event code 95 (KPJpComma) Event code 96 (KPEnter) Event code 97 (RightCtrl) Event code 98 (KPSlash) Event code 99 (SysRq) Event code 100 (RightAlt) Event code 102 (Home) Event code 103 (Up) Event code 104 (PageUp) Event code 105 (Left) Event code 106 (Right) Event code 107 (End) Event code 108 (Down) Event code 109 (PageDown) Event code 110 (Insert) Event code 111 (Delete) Event code 113 (Mute) Event code 114 (VolumeDown) Event code 115 (VolumeUp) Event code 116 (Power) Event code 117 (KPEqual) Event code 119 (Pause) Event code 121 (KPComma) Event code 122 (Hanguel) Event code 123 (Hanja) Event code 124 (Yen) Event code 125 (LeftMeta) Event code 126 (RightMeta) Event code 127 (Compose) Event code 128 (Stop) Event code 129 (Again) Event code 130 (Props) Event code 131 (Undo) Event code 132 (Front) Event code 133 (Copy) Event code 134 (Open) Event code 135 (Paste) Event code 136 (Find) Event code 137 (Cut) Event code 138 (Help) Event code 183 (F13) Event code 184 (F14) Event code 185 (F15) Event code 186 (F16) Event code 187 (F17) Event code 188 (F18) Event code 189 (F19) Event code 190 (F20) Event code 191 (F21) Event code 192 (F22) Event code 193 (F23) Event code 194 (F24) Event code 240 (Unknown) Event type 4 (Misc) Event code 4 (ScanCode) Event type 17 (LED) Event code 0 (NumLock) Event code 1 (CapsLock) Event code 2 (ScrollLock)
Bug#523867: xinput: Notebook Keyboard lost after normal bootup
reassign 523867 xserver-xorg-input-evdev kthxbye Sorry for miss-placing this, should have read thepackage description and not guessing from the name -- /\ ASCII Ribbon : GPG-Key ID: 0x0372275D \ /Campaign : X against HTML : Working for Debian / \ in eMails : http://www.debian.org/ http://www.christoph-egger.org/ signature.asc Description: Digital signature
Bug#523867: xinput: Notebook Keyboard lost after normal bootup
On Mon, 2009-04-13 at 09:55 +0200, Christoph Egger wrote: After booting my notebook, the keyboard seems to be absolutely lost in X (works if I switch to vt[1-6]). Attaching an USB Keyboard to the notebook works however. Please send your /proc/bus/input/devices (and tell us whether that's with or without the usb keyboard), and output of lshal. Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523867: xinput: Notebook Keyboard lost after normal bootup
On Mon, 2009-04-13 at 13:50 +0200, Christoph Egger wrote: On Mon, Apr 13, 2009 at 11:11:56AM +0100, Julien Cristau wrote: On Mon, 2009-04-13 at 09:55 +0200, Christoph Egger wrote: After booting my notebook, the keyboard seems to be absolutely lost in X (works if I switch to vt[1-6]). Attaching an USB Keyboard to the notebook works however. Please send your /proc/bus/input/devices (and tell us whether that's with or without the usb keyboard), and output of lshal. Cheers, Julien OK I have both attached (with USB Keyboard) weird. /proc/bus/input/devices shows your keyboard: I: Bus=0011 Vendor=0001 Product=0001 Version=ab54 N: Name=AT Translated Set 2 keyboard P: Phys=isa0060/serio0/input0 S: Sysfs=/class/input/input3 U: Uniq= H: Handlers=kbd event3 B: EV=120013 B: KEY=4 200 3803078 f800d001 fedf ffef fffe B: MSC=10 B: LED=7 but it doesn't appear in lshal. Is there anything in dmesg that could be related? CC:ing the hal maintainers. Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523867: xinput: Notebook Keyboard lost after normal bootup
On Mon, Apr 13, 2009 at 01:05:18PM +0100, Julien Cristau wrote: weird. /proc/bus/input/devices shows your keyboard: I: Bus=0011 Vendor=0001 Product=0001 Version=ab54 N: Name=AT Translated Set 2 keyboard P: Phys=isa0060/serio0/input0 S: Sysfs=/class/input/input3 U: Uniq= H: Handlers=kbd event3 B: EV=120013 B: KEY=4 200 3803078 f800d001 fedf ffef fffe B: MSC=10 B: LED=7 but it doesn't appear in lshal. Is there anything in dmesg that could be related? CC:ing the hal maintainers. Cheers, Julien There's only one line in dmesg where the Keyboard seems to be detected but nothing more and nothing that looks like an error. Regards Christoph -- /\ ASCII Ribbon : GPG-Key ID: 0x0372275D \ /Campaign : X against HTML : Working for Debian / \ in eMails : http://www.debian.org/ http://www.christoph-egger.org/ signature.asc Description: Digital signature
