Date: Wed, 05 Sep 2001 22:23:08 +0900 From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> To: "Ilmar S. Habibulin" <ilmar@watson.org> Cc: freebsd-current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp, msmith@freebsd.org, iwasaki@freebsd.org Subject: Re: my psm0 doesn't work with new acpi :( Message-ID: <200109051323.WAA13583@zodiac.mech.utsunomiya-u.ac.jp> In-Reply-To: Your message of "Wed, 05 Sep 2001 08:44:08 -0400." <Pine.BSF.3.96.1010905084215.65549A-100000@fledge.watson.org> References: <Pine.BSF.3.96.1010905084215.65549A-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
As I wrote in another mail to Harti Brandt and cc'ed to you, it now appears that ACPI on your motherboard declares IRQ 12 BOTH in the PS/2 mouse resource descriptors and in the system reserved resource descriptors. The system reserved resources are sucked by the sysresource driver in the acpi module. If the psm driver can get at IRQ 12 BEFORE the sysresource driver, or the sysresource driver is made to be probed AFTER all other acpi device nodes are probed, all should be fine... As some other people are not having this problem, this may be called a quirk or anomaly, to say the least. Kazu >> Then, would you remove my previous small patch from psm.c, and put the >> following line in /boot/device.hints instead and reboot? >> debug.acpi.disable="sysresource" >> Or, you may type >> set debug.acpi.disable="sysresource" >> at the loader prompt before "boot -v". > >Wow, my NetScroll is back in bussiness!!! ;-))) >So is it buggy BIOS, chipset, ASUS or PS/2 mouse? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200109051323.WAA13583>