ACPI/PCI-bus issue with compaq evo n160

[Wilko Bulte]

On Wed, Dec 17, 2003 at 03:12:53PM +0100, Fredrik Lindberg wrote:

Excellent, thanks to Mauritz!

Battery information leaves some stuff to be desired, at least on
my N160:

wkb at chuck ~: apm
APM version: 1.2
APM Management: Disabled
AC Line status: off-line
Battery status: low
Remaining battery life: 0%
Remaining battery time:  2:59:00
Number of batteries: 1
Battery 0:
        Battery status: low
        Remaining battery life: 0%
        Remaining battery time:  2:59:00
Resume timer: unknown
Resume on ring indicator: disabled
APM Capabilities:
        unknown
wkb at chuck ~: 

I love the milliWatthours and milliVolts below:

chuck#acpiconf -i batt
Battery 0 information
Design capacity:        -1 mWh
Last full capacity:     -1 mWh
Technology:             secondary (rechargeable)
Design voltage:         -1 mV
Capacity (warn):        800 mWh
Capacity (low):         16 mWh
Low/warn granularity:   100 mWh
Warn/full granularity:  100 mWh
Model number:           BAT1
Serial number:          0000
Type:                   LION
OEM info:               COMPAQ

;-)

But this is still a great improvement from no ACPI at all!

Wilko


> The solution suggested by Mauritz worked, the ACPI stuff works now. 
> This is what I have in my loader.conf
> 
> debug.acpi.disable="lid pci_link"
> hw.pci.allow_unsupported_io_range="1"
> hw.cbb.start_memory="536870912"
> 
> I would like to thank everybody who have helped me troubleshoot this.
> 
>    Fredrik
> 
> (please remove the NOSPAM stuff if you reply private)
> 
> On Wed, Dec 17, 2003 at 10:02:43AM +0100, Mauritz Sundell (mauritz.sundell) wrote:
> > 
> > It is enough to disable pci_link for booting
> > debug.acpi.disable="pci_link"
> > 
> > But I also disable lid because otherwise it goes to some kind of sleep (S1) when I close the lid.
> > debug.acpi.disable="lid pci_link"
> > 
> > Also for I have
> > hw.cbb.start_memory="0xd0208000"
> > since pci/pcib allocates the memory assigned to fxp0 by BIOS to pccard otherwise.
> > 
> > Now I always use acpiconf -s S4 to suspend and save to disk instead of turning the power off, wonderful.
> > 
> > 
> > -----Original Message-----
> > From: Fredrik Lindberg <>
> > To: freebsd-mobile at freebsd.org
> > Date: Fri, 12 Dec 2003 15:28:56 +0100
> > Subject: ACPI/PCI-bus issue with compaq evo n160
> > 
> > Hi,
> > Thank you for your reply.
> > The information you requested is avaiable at
> > 
> > http://shapeshifter.se/~fredde/tmp/db
> > http://shapeshifter.se/~fredde/tmp/dmesg.acpi-pci.enabled
> > 
> >   Fredrik 
> > 
> > On Thu, Dec 11, 2003 at 01:42:06PM -0500, John Baldwin (jhb) wrote:
> > > [ Resent due to NO.*SPAM bounce the first time ]
> > > 
> > > On 10-Dec-2003 Fredrik Lindberg wrote:
> > > > Hi,
> > > > 
> > > > I have a Compaq evo n160 running 
> > > > FreeBSD biocandy 5.2-RC FreeBSD 5.2-RC #10: Mon Dec  8 19:08:38 CET 2003
> > > > 
> > > > The machine fails (and always has) to boot with acpi enabled 
> > > > (locks up when mounting /), however, I managed to find out that 
> > > > booting with the following option 
> > > > 
> > > > debug.acpi.disable="pci" 
> > > > 
> > > > in /boot/loader.conf made the machine boot correctly and acpi related 
> > > > functions such as battry monitoring worked just fine.
> > > > 
> > > > But, and a huge but, no pci devices are detected during boot 
> > > > (maybe quite obvious because of that debug option) 
> > > > All pci-devices works perfectly with acpi disabled.
> > > > 
> > > > Now, is there any chance to make freebsd use acpi and the 
> > > > "normal" pci-bus driver at the same time, overriding the 
> > > > acpi pci-bus implementation?
> > > > 
> > > > I believe linux has a kernel option called pci=noacpi (atleast acording to google),
> > > > which does this.
> > > > 
> > > > With acpi enabled scanpci reports all the pci devices, but pciconf -l
> > > > doesn't return anything.
> > > > With acpi disabled, scanpci reports all pci devices, pciconf -l 
> > > > reports all devices.
> > > > 
> > > > dmesg output with acpi enabled 
> > > > http://shapeshifter.se/~fredde/tmp/dmesg.acpi.enabled
> > > > 
> > > > dmesg out with acpi disabled
> > > > http://shapeshifter.se/~fredde/tmp/dmesg.acpi.disabled
> > > > 
> > > > Any, and I mean any, help on this will be very appreciated.
> > > 
> > > If you can drop into ddb and do a 'show intrcnt' when the machine
> > > locks up that might help fix the hang.  It sounds like the interrupt
> > > routing may not have worked correctly.  Also, a dmesg of acpi
> > > with pci enabled would be helpful.
> > > 
> > > -- 
> > > 
> > > John Baldwin <jhb>  <><  http://www.FreeBSD.org/~jhb/
> > > "Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/
> > 
> > ----- End forwarded message -----
> > _______________________________________________
> > freebsd-mobile mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
> > To unsubscribe, send any mail to "freebsd-mobile-unsubscribe"
> > 
> > 
> > 
> 
> 
> _______________________________________________
> freebsd-mobile at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
> To unsubscribe, send any mail to "freebsd-mobile-unsubscribe at freebsd.org"
---end of quoted text---

-- 
|   / o / /_  _   		
|/|/ / / /(  (_)  Bulte		wilko at FreeBSD.org