From owner-freebsd-bugs Wed Jan 8 06:20:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA06989 for bugs-outgoing; Wed, 8 Jan 1997 06:20:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA06977; Wed, 8 Jan 1997 06:20:02 -0800 (PST) Date: Wed, 8 Jan 1997 06:20:02 -0800 (PST) Message-Id: <199701081420.GAA06977@freefall.freebsd.org> To: freebsd-bugs Cc: From: Mark Schleifer Subject: Re: kern/2409: psm0: unable to set the command byte. psm0 not found at 0x60 Reply-To: Mark Schleifer Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR kern/2409; it has been noted by GNATS. From: Mark Schleifer To: Kazutaka YOKOTA Cc: Mark Schleifer , FreeBSD-gnats-submit@freebsd.org Subject: Re: kern/2409: psm0: unable to set the command byte. psm0 not found at 0x60 Date: Wed, 8 Jan 1997 09:16:25 -0500 (EST) On 1/8/1997 (14:05:08 +0900), Kazutaka YOKOTA wrote: ] >] >>How-To-Repeat: ] >] > ] >] >Kernel made with following config file. This file worked with SNAPs and ] >] >ALPHA after applying PAO patches. Also tried with PSM_NO_RESET with BETA ] >] >but that caused the keyboard to lockup at first input request. ] >] ] >] PSM_NO_RESET is no longer available in 2.2-BETA, thus, has nothing to do ] >] with the keyboard lockup; the lockup which shouldn't be happening *sigh* ] > ] >Interesting...It was just giving me the errors until I added that ] >config option (which it didn't complain about). With that option in, ] >it doesn't allow keyboard input. ] ] You mean, PSM_NO_RESET made `psm' to recognize your PS/2 mouse ] (trackball) successfully? Strange. I am very sure that PSM_NO_RESET ] has no effect on `psm' now... I'm sorry I wasn't clear...PSM_NO_RESET didn't make it recognize successfully. Let me back up. I've had the following results, in all cases psm0 is _not_ recognized successfully: w/ kernel.GENERIC: psm0 enabled in the kernel: System boots but doesn't take anything I type. I have to powercycle after boot to get out. psm0 disabled in the kernel: System works OK unless something tries to open psm0. w/ config OTOR-SCSI (the one sent in with the bug report): psm0 enabled in the kernel: System works OK unless something tries to open psm0. w/ config OTOR-SCSI + PSM_NO_RESET: psm0 enabled in the kernel: System boots but doesn't take anything I type. I have to powercycle after boot to get out. ] [...] ] > ] >] I would also ask you to add ] >] options "KBDIO_DEBUG=2" ] >] to your config file. With this option `sc' and `psm' drivers will log ] >] quite a few messages via `syslogd' on boot and later. The messages are ] >] marked with "kbdio: blugh blugh". ] > ] >I did this but saw nothing in the syslogs. What does it log them ] >under? kern.debug? ] ] Yes, you should find logs under kern.debug. You should see something like: ] ] ..... kbdio: X char read (empty_both_buffers) ] ..... kbdio: RESET_KBD return code:00fa ] ..... kbdio: RESET_KBD status:00aa ] ..... sc0 at 0x60-0x6f irq 1 on motherboard ] ..... sc0: VGA color <16 virtual consoles, flags=0x0> ] ] ..... kbdio: TEST_AUX_PORT status:0000 ] ..... kbdio: RESET_AUX return code:00fa ] ..... kbdio: RESET_AUX status:00aa ] ..... kbdio: RESET_AUX ID:0000 ] ..... psm0 at 0x60-0x64 irq 12 on motherboard ] ..... psm0: device ID 0, 3 buttons Hum, none of this to the screen or to syslog. Wait, I'm sorry. I was overtired last night and removed the "" from "KBDIO_DEBUG=2". I just put them in and rebuilt the kernel. Here are the results: Jan 8 09:03:03 otor /kernel: Probing for devices on the ISA bus: Jan 8 09:03:03 otor /kernel: kbdio: RESET_KBD return code:00fa Jan 8 09:03:04 otor /kernel: kbdio: RESET_KBD status:00aa Jan 8 09:03:04 otor /kernel: sc0 at 0x60-0x6f irq 1 on motherboard Jan 8 09:03:04 otor /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> [...] Jan 8 09:03:04 otor /kernel: kbdio: TEST_AUX_PORT status:0000 Jan 8 09:03:04 otor /kernel: kbdio: RESET_AUX return code:00fa Jan 8 09:03:04 otor /kernel: kbdio: RESET_AUX status:00aa Jan 8 09:03:04 otor /kernel: kbdio: RESET_AUX ID:0000 Jan 8 09:03:04 otor /kernel: psm0: unable to set the command byte. Jan 8 09:03:04 otor /kernel: psm0 not found at 0x60 ] >Just for grins, I tried starting moused again, which crashed immediately: ] > ] ># moused -p /dev/psm0 -t ps/2 ] ] You need to apply the patch to prevent the crash. Patch applied and it did indeed fix that problem. For some reason when I first read your mail I thought you were saying that the patch had already been applied between the ALPHA and the BETA. Sorry for the confusion. - Mark