On Tue, 14 Apr 2009 10:49:10 -0600 Theo de Raadt
<dera...@cvs.openbsd.org> wrote:

> > So I've recently installed 4.4 on a new via idot pc3500-g
> > motherboard, which is all great, but I note that ACPI isn't
> > working. Is there anything helpful I can contribute to getting it
> > working on this system?
> > 
> > Or do dmesg notes like 'pcibios0: bad IRQ table checksum' suggest
> > that the system is pretty much braindead? I've included a dmesg
> > below, but no acpidump, given how big it is.
> > 
> > Once again, thanks in advance...
> > 
> >   - Ruan
> > 
> > OpenBSD 4.4 (GENERIC) #1021: Tue Aug 12 17:16:55 MDT 2008
> >     dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
> > cpu0: VIA Esther processor 1500MHz ("CentaurHauls" 686-class) 1.51
> > GHz cpu0:
> > FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,CMOV,PAT,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,TM,SBF,SSE3
> > cpu0: RNG AES AES-CTR SHA1 SHA256 RSA real mem  = 1005023232 (958MB)
> > avail mem = 963248128 (918MB)
> > mainbus0 at root
> > bios0 at mainbus0: AT/286+ BIOS, date 10/13/08, BIOS32 rev. 0 @
> > 0xf9a60, SMBIOS rev. 2.4 @ 0xf0000 (31 entries)
> > bios0: vendor Phoenix Technologies, LTD version "FDd" date
> > 10/13/2008 bios0: PC1 PC3500G
> > apm0 at bios0: Power Management spec V1.2 (slowidle)
> > apm0: AC on, battery charge unknown
> 
> There is a heuristic which selects apm on some machines instead of
> acpi.  A few machines unfortunately fall into this set
> unintentionally, but there is nothing we can do about it at this time.
> 

The fact you guys were able to even develop a heuristic to do a
reasonable job guessing between apm and acpi (mutex) is by itself
amazing. Doing the required poking and probing without a lot of 
poorly built systems (many) croaking is even more amazing.

Ruan, you might want to note, the heuristic/mutex Theo mentioned is
available in -current 4.5 snapshots, but you're only running 4.4.
If you want to test out the the new heuristics stuff, you'll need to
grab the latest snapshot from ftp and install it.

-- 
J.C. Roberts

Reply via email to