Date: Fri, 13 Jan 2012 17:00:29 GMT From: John Baldwin <jhb@freebsd.org> To: freebsd-amd64@FreeBSD.org Subject: Re: amd64/164036: Moused fails on 9_0_RELENG Message-ID: <201201131700.q0DH0TXv093329@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR amd64/164036; it has been noted by GNATS. From: John Baldwin <jhb@freebsd.org> To: Justin Smith <freebsd.users@gmail.com> Cc: freebsd-amd64@freebsd.org, freebsd-gnats-submit@freebsd.org Subject: Re: amd64/164036: Moused fails on 9_0_RELENG Date: Fri, 13 Jan 2012 11:54:36 -0500 On Friday, January 13, 2012 11:17:35 am Justin Smith wrote: > On Fri, Jan 13, 2012 at 11:18 PM, John Baldwin <jhb@freebsd.org> wrote: > > On Friday, January 13, 2012 9:20:53 am Justin Smith wrote: > >> Yeah, its strange for sure. But I have this issue on two different > >> systems with different hardware (ASUS board & BIOSTAR Board). > >> > >> devinfo -vr : http://paste.pocoo.org/show/534240/ > > > > Hmm. So the "problem" is your BIOS putting the keyboard resources on the PS/2 > > port. You can fix this by editing your AML and moving the IO Port resources > > out of _CRS for the PS2M device and moving them to the PS2K device instead. > > > > However, fixing it automatically would be a bigger pain as we would need to > > patch both the atkbdc and psmcpnp drivers to cooperate to move the I/O ports > > over. We already have a similar hack for handling IRQ 12. We should perhaps > > expand that further so that we have atkbdc somehow attach to both PS/2 devices > > and merge any resources into a single logical device. > > > > -- > > John Baldwin > > Been there done that (ASUS board AML), doesn't work. I have no > settings for PS2M to PS2K on BIOSTAR BIOS. Err, not a BIOS setting, but actually editing the AML. Assuming you edited the ASUS AML, can you show me a diff of the original and modified AML? -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201201131700.q0DH0TXv093329>