Re: Keyboard occasionally nonresponsive on bootup with Debian Sid
Adam Rosi-Kessel wrote: Hmm. I'm fairly certain the keyboard fails to work when I haven't pressed any keys yet (not even 'return' to select the kernel in GRUB--it usually just picks the first one after 5 seconds). I can't for the life of me think of what would make it occur only occasionally, though. My gut instinct is to declare, with a 98.625% confidence level, that your keyboard/keyboard connector is flakey. You may have missed the part where I said that I had this problem on two different laptops. I was certain it was hardware as well on the first laptop (a Dell Latitude), but then I got a brand new IBM Thinkpad X40, and the same behavior occurred immediately out of the box. The Latitude was nearly new as well. Ah, yes, I did miss that. What is your confidence level that two brand new laptops would both have the same keyboard/connector flakiness, that only occurs after the bootloader is done, but not before? I missed that as well. My confidence level has dropped substantially now. Never mind. -- Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Keyboard occasionally nonresponsive on bootup with Debian Sid
> > Hmm. I'm fairly certain the keyboard fails to work when I haven't > > pressed any keys yet (not even 'return' to select the kernel in > > GRUB--it usually just picks the first one after 5 seconds). I can't > > for the life of me think of what would make it occur only > > occasionally, though. > My gut instinct is to declare, with a 98.625% confidence level, that > your keyboard/keyboard connector is flakey. You may have missed the part where I said that I had this problem on two different laptops. I was certain it was hardware as well on the first laptop (a Dell Latitude), but then I got a brand new IBM Thinkpad X40, and the same behavior occurred immediately out of the box. The Latitude was nearly new as well. What is your confidence level that two brand new laptops would both have the same keyboard/connector flakiness, that only occurs after the bootloader is done, but not before? -- Adam Rosi-Kessel http://adam.rosi-kessel.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Keyboard occasionally nonresponsive on bootup with Debian Sid
On Sun, 19 Sep 2004 22:01:55 -0500, Kent West <[EMAIL PROTECTED]> wrote: > Adam Rosi-Kessel wrote: > > >Hmm. I'm fairly certain the keyboard fails to work when I haven't > >pressed any keys yet (not even 'return' to select the kernel in GRUB--it > >usually just picks the first one after 5 seconds). I can't for the life > >of me think of what would make it occur only occasionally, though. > > > > > My gut instinct is to declare, with a 98.625% confidence level, that > your keyboard/keyboard connector is flakey. > > -- > Kent > > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > i was having a similar problem using xdm, whenever linux would start xdm, the keyboard would become non functional. I have since removed xdm from init.d, and manually startx now, and it works fine. i'm confused :P -- Mike Arnold -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Keyboard occasionally nonresponsive on bootup with Debian Sid
Adam Rosi-Kessel wrote: Hmm. I'm fairly certain the keyboard fails to work when I haven't pressed any keys yet (not even 'return' to select the kernel in GRUB--it usually just picks the first one after 5 seconds). I can't for the life of me think of what would make it occur only occasionally, though. My gut instinct is to declare, with a 98.625% confidence level, that your keyboard/keyboard connector is flakey. -- Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Keyboard occasionally nonresponsive on bootup with Debian Sid
Thanks for your suggestions: On Sun, Sep 19, 2004 at 03:30:52PM -0700, Stefan O'Rear wrote: > To enter text into the terminal, open up a file using your destop (like > say /etc/passwd), select one letter, then middle click in the terminal. > Will be slow, should work. The problem with this is that I need to login before I can open a terminal, and the keyboard is nonfunctional from the start. I use gdm as login manager. I suppose I could configure it to auto-login to troubleshoot this problem, but I'd rather not eliminate password authentication as a condition of using the machine. > Perhaps your X server is improperly configured, and depending one what > keys you press after bootup, it sometimes misdetects your keyboard type? Hmm. I'm fairly certain the keyboard fails to work when I haven't pressed any keys yet (not even 'return' to select the kernel in GRUB--it usually just picks the first one after 5 seconds). I can't for the life of me think of what would make it occur only occasionally, though. > can you Ctrl-Alt-BackSpace the server? Nope, ctrl-alt-backspace is as nonfunctional as ctrl-alt-del. -- Adam Rosi-Kessel http://adam.rosi-kessel.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Keyboard occasionally nonresponsive on bootup with Debian Sid
On Sunday 19 September 2004 06:30 pm, Stefan O'Rear wrote: > To enter text into the terminal, open up a file using your destop (like > say /etc/passwd), select one letter, then middle click in the terminal. > Will be slow, should work. At first this whole post left me baffled, and wondering what kind of funky substances you might have been ingesting. Then I realized how clever that is. I wonder if I would have thought of that? I'm afraid I might not have. Another idea for an easy place to get letters. Try (if you have it installed) running KCharselect or the GNOME equivalent. -- Michael McIntyre Silvan <[EMAIL PROTECTED]> Linux fanatic, and certified Geek; registered Linux user #243621 http://www.geocities.com/Paris/Rue/5407/ http://rosegarden.sourceforge.net/tutorial/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Keyboard occasionally nonresponsive on bootup with Debian Sid
On Sun, Sep 19, 2004 at 05:39:11PM -0400, Adam Rosi-Kessel wrote: > Please cc me on replies. > > I've got a couple of problems for which I can't identify the responsible > subsystem, so I thought I'd ask in a general forum like this. Here's the > first: > > Running Debian Sid, various 2.6.x kernels. To enter text into the terminal, open up a file using your destop (like say /etc/passwd), select one letter, then middle click in the terminal. Will be slow, should work. > About one out of every three times I boot up my laptop, my keyboard is > totally unresponsive. The mouse works fine. I can do machine fn-calls, > e.g., fn-f5 to activate bluetooth, or fn-f7 to switch CRT/LCD. But the X > server doesn't respond to any keystrokes, and keys like Caps Lock don't > change the status light. I don't know if the keyboard would work in > console, since I can't switch over there. (I've never had this problem > occur when I boot up to a lower runlevel, however). To change consoles without a working keyboard, use the chvt command. E.g. use copy&paste and: sudo chvt 1 your password > I was pretty sure this was linked to my specific hardware, but I recently > moved from a Dell Latitude to a IBM Thinkpad X40, and still get the same > behavior. There's very little in common (hardware) between the two > systems, so I think that excludes hardware. > > On those times when the keyboard doesn't work, it *does* work in the > bootloader (GRUB); it's only after booting up that the keyboard doesn't > work. > > Ctrl-alt-del is also non-functional, so the only way I can restart is to > power off. sudo init 0 sudo init 6 > Nothing unusual in the log files. Also occurs with several different 2.6 > kernels, including 2.6.8.1. I'm not sure it has ever happened with a > 2.4.x kernel, but for various reasons I can't use those kernels, so I > haven't experimented that much. > > Can anyone suggest a way to hunt down this problem? I can't even guess > the origin. > > (likely irrelevant, but I do get 'atkbd.c: Spurious ACK on > isa0060/serio0. Some program, like XFree86, might be trying access > hardware directly.' a lot in dmesg). Perhaps your X server is improperly configured, and depending one what keys you press after bootup, it sometimes misdetects your keyboard type? If your boot to a lower non-X runlevel and run: sudo XFree86 can you Ctrl-Alt-BackSpace the server? -- The world's most effective spam filter: ln -sf /dev/full /var/mail/$USER -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Keyboard occasionally nonresponsive on bootup with Debian Sid
Please cc me on replies. I've got a couple of problems for which I can't identify the responsible subsystem, so I thought I'd ask in a general forum like this. Here's the first: Running Debian Sid, various 2.6.x kernels. About one out of every three times I boot up my laptop, my keyboard is totally unresponsive. The mouse works fine. I can do machine fn-calls, e.g., fn-f5 to activate bluetooth, or fn-f7 to switch CRT/LCD. But the X server doesn't respond to any keystrokes, and keys like Caps Lock don't change the status light. I don't know if the keyboard would work in console, since I can't switch over there. (I've never had this problem occur when I boot up to a lower runlevel, however). I was pretty sure this was linked to my specific hardware, but I recently moved from a Dell Latitude to a IBM Thinkpad X40, and still get the same behavior. There's very little in common (hardware) between the two systems, so I think that excludes hardware. On those times when the keyboard doesn't work, it *does* work in the bootloader (GRUB); it's only after booting up that the keyboard doesn't work. Ctrl-alt-del is also non-functional, so the only way I can restart is to power off. Nothing unusual in the log files. Also occurs with several different 2.6 kernels, including 2.6.8.1. I'm not sure it has ever happened with a 2.4.x kernel, but for various reasons I can't use those kernels, so I haven't experimented that much. Can anyone suggest a way to hunt down this problem? I can't even guess the origin. (likely irrelevant, but I do get 'atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.' a lot in dmesg). -- Adam Rosi-Kessel http://adam.rosi-kessel.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
