Re: USB keyboard locking up on 7-RELEASE/amd64
On Wed, Apr 09, 2008 at 05:07:24PM -0500, H. Wade Minter wrote: The install went fine, but post-install I'm running into a problem where the USB keyboard will just lock up. I can still ping and SSH into the system, but after about 2 minutes of activity, the keyboard becomes nonresponsive. As far I understood this is caused by the BIOS which emulates PS/2 for USB keyboard and mouse. So FreeBSD double-detects your keyboard as PS/2 by atkbd(c) and directly via USB. There is no Option in the (my) BIOS to disable this USB-PS/2 emulation. Banning atkbd(c) and psm from the kernel worked for me. $ cat /usr/src70/sys/amd64/conf/DELL755 # Kernel-Config for Dell Optiplex 755 / amd64 # # From: Baldur Gislason baldur at foo.is # To: freebsd-gnats-submit at FreeBSD.org # Cc: # Subject: Re: usb/119509: USB flaky on Dell Optiplex 755 # Date: Mon, 4 Feb 2008 15:30:52 + # include GENERIC ident DELL755 nodevice atkbdc # AT keyboard controller nodevice atkbd # AT keyboard nodevice psm # PS/2 mouse YMMV Regards Raphael -- Raphael Becker [EMAIL PROTECTED] http://rabe.uugrn.org/ GnuPG:E7B2 1D66 3AF2 EDC7 9828 6D7A 9CDA 3E7B 10CA 9F2D .|.|.|.|.|.|.|.. pgpC3DLmUJKwI.pgp Description: PGP signature
Re: USB keyboard locking up on 7-RELEASE/amd64
On Wed, 2008-04-09 at 17:07 -0500, H. Wade Minter wrote: I have a Dell Optiplex 755, with an Intel Core 2 Duo chip. I have installed 7-RELEASE/amd64 on it. 2GB of RAM, 6GB of swap. The install went fine, but post-install I'm running into a problem where the USB keyboard will just lock up. I can still ping and SSH into the system, but after about 2 minutes of activity, the keyboard becomes nonresponsive. I can move the USB plug to a different port, and see that it's recognize, and the keyboard comes back, but a couple of minutes later, it locks again. I've checked with things in the BIOS, but can't find any setting that makes a difference. I've tried both the 4BSD and ULE scheduler, no changes. Any thoughts or known issues that would explain this? When the lockup happens, there's nothing in /var/log/messages or dmesg to indicate a problem. The only other clues are that sometimes, right before it locks, it will go into a repeat loop on a keypress, and it seems to be able to be reliably triggered by switching virtual consoles (though not exclusively). I've tried different keyboards, so it doesn't appear to be a hardware issue. I have seen this happening with OptiPlex 740 and OpenSuSE 10.3. Updating the BIOS on the OptiPlex fixed the problem. In my case, I was able to find reports of this behavior on the Dell's Linux forums, so it certainly was not limited to my specimen. I do realize that your machine is different, so YMMV. Thoughts? --Wade ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- Alexandre Sunny Kovalenko (Олександр Коваленко) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
USB keyboard locking up on 7-RELEASE/amd64
I have a Dell Optiplex 755, with an Intel Core 2 Duo chip. I have installed 7-RELEASE/amd64 on it. 2GB of RAM, 6GB of swap. The install went fine, but post-install I'm running into a problem where the USB keyboard will just lock up. I can still ping and SSH into the system, but after about 2 minutes of activity, the keyboard becomes nonresponsive. I can move the USB plug to a different port, and see that it's recognize, and the keyboard comes back, but a couple of minutes later, it locks again. I've checked with things in the BIOS, but can't find any setting that makes a difference. I've tried both the 4BSD and ULE scheduler, no changes. Any thoughts or known issues that would explain this? When the lockup happens, there's nothing in /var/log/messages or dmesg to indicate a problem. The only other clues are that sometimes, right before it locks, it will go into a repeat loop on a keypress, and it seems to be able to be reliably triggered by switching virtual consoles (though not exclusively). I've tried different keyboards, so it doesn't appear to be a hardware issue. Thoughts? --Wade ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
