ACPI and Linksys 10/100 PC Card (ed1)

Matthew Dillon dillon at apollo.backplane.com
Fri Jul 30 12:07:36 PDT 2004


:Hi Matt,
:
:Thanks for the response.  I currently have disabled ACPI across the 
:board and that seems to work fine.  I will try and get some verbose 
:output from my bootup with ACPI enabled (busy investigating how to get 
:all the debug info required) and send that in with my ACPI tables.  I 
:should have a moment to do that tonight.
:
:I assume that if I want to enable some verbose options I use the same 
:method you described to boot with the -a option?
:
:I am also in the process of upgrading to the latest base system.  Maybe 
:that helps.
:
:Thanks again for the assistance.  On the side.  I am very impressed with 
:DragonFly.  Keep up the good work!
:
:Kind regards,
:
:Henry

    Yah, use boot -a -v.

    It sounds like you simply have one of those systems which only works
    without ACPI.  It is likely, however, that only one or two of the ACPI
    features are the cause of the failure.  You can disable particular
    ACPI functions at the boot prompt or in /boot/loader.conf.  Quoting
    from YONETANI Tomokazu:

------- begin quote -----
There's a kernel environment variable called debug.acpi.disabled, to
disable ACPI features. This helps narrowing down which part of ACPI code
is causing trouble. You can specify one or more of the following keywords,
separated by spaces.
   acad bus button children cmbat cpu ec
   isa lid pci pci_link sysresource thermal timer

"acpi" disables everything
"bus" disables "children"
"pci" disables "pci_link"

pci-related code in the acpi code in our tree is said to be incorrect,
so you may want to try disabling it first. There's also been a report
of lock-up which was worked around by disabling thermal code, but I'm
not sure whether it applies to your T42p.
------- end quote -----

						-Matt






More information about the Bugs mailing list