Greetings to you also. Thanks for your ASL patch suggestion - that worked perfectly. I now have a PS/2 mouse being detected with ACPI on on my Compaq Presario 2100 latop. Woohoo. My instrumentation code in psm.c now shows the mouse being initially identified via the psmpnp driver path, which is what I was expecting to see. Last night, I was rapidly coming to the conclusion that acpi-ca simply couldn't see the mouse and it wasn't in the ACPI resource list. Taku, the second .asl on my website was modified by me. the _CID block was straight from the original asl. I had at one stage tried to re-order the pnp ids within the block so that PNP0F03 was first, but that didn't help either. So, it sort of looks as though acpi-ca doesn't understand the multiple entries in _CID block syntax, even though their compiler does. I'm going to put a summary of this on my web server and index it with google, hopefully this fix will apply to many of the other with laptop mouse problems. Thanks everyone for your help. Brendon > Greetings, > > > I've read your ASLs and figured out how psm0 fails to attach. > > Both of the two ASLs have _CID (compat id) of MSE0 (read: psm0) as a package. > But, unfortunately, our current code does not handle such _CIDs. > > So, for interim solution, I would propose following snippet of ASL. > > Device (MSE0) // psm0/psmcpnp0 > { > Name (_HID, EisaId ("SYN0105")) > Name (_CID, EisaId ("PNP0F13")) /// XXX - for now > Name (_CSR, Buffer (6) > { > 0x23, 0x00, 0x10, 0x01, 0x79, 0x00 > }) > } > > For long time solution, we have to modify the logic of acpi_isa_pnp_probe() > (defined in src/sys/dev/acpica/acpi.c) to support multiple _CID EisaIds. > > I ever saw such patch before. (as long as my memory serves right) > # Mmm, takawata-san's work? > > yours sincerely, > Taku > -- > -|-__ YAMAMOTO, Taku <taku_at_cent.saitama-u.ac.jp> > | __ < > > > On Sun, 14 Dec 2003 20:59:14 -0800 > Brendon and Wendy <wendy.humphrey_at_comcast.net> wrote: > Quick update regarding problem below. > > I have cvsupped the kernel again as of today, in order to get the new > ACPI implemention. Sadly, it does not seem to improve on the mouse > problem. > > I quickly installed Gentoo 1.4 just to verify that Linux manages to find > psm, and it does. > > So, I'm now slowly working my way through the initialisation code to see > if I can at least pinpoint where the decision on IRQ availability is > made. Will report what/if I find. > > Thanks, > Brendon > > > On Fri, 2003-12-05 at 08:09, Brendon and Wendy wrote: > > Dear list, > > > > I am going to join the slowly growing number of users that are reporting > > that use of ACPI on 5.1-current on Compaq Presario (maybe just Compaq!) > > laptops results in the PS/2 mouse being undetectable by the OS (PSM: > > Unable to allocate IRQ). > > > > This has been an ongoing thing for me - I've been aware of the problem > > for some time, but have not had the time to do anything about it. I > > could sware that 5.0 + ACPI used to work, in fact I might reinstall it > > to see. > > > > I have already tried rebuilding my DSDT, and am going to try some > > further experiments (the Compaq raw .aml, does not compile cleanly with > > iasl and needs work). Going to try copying the resource allocation code > > from a desktop machine that seems ok with ACPI into the laptop (that'll > > be fun). I may also start walking through the resource > > allocation/discovery code in the kernel to see what the device driver is > > doing. My basic premise is that the kernel is having difficulty > > determining which IRQ to use for the PS/2 mouse. > > > > Nate if you have suggestions of things to try I'm perfectly happy to do > > so. > > > > For Nate, my boot -v output is at > > > > http://humphrey.dyndns.org/dmesg.boot > > > > original disassembled DSDT is at > > > > http://humphrey.dyndns.org/presario2100us.asl > > > > slightly tweeked (and no doubt munged) version: > > > > http://humphrey.dyndns.org/presario2100us2.asl > > http://humphrey.dynsdns.org/presario2100usdiff > > > > Thanks, > > Brendon > > > > _______________________________________________ > freebsd-current_at_freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org" >Received on Mon Dec 15 2003 - 07:46:12 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:34 UTC