acpi battery state

2006-03-01 Thread Steffen Wendzel
Hi,

I try to find out how many energy is left on my battery. I run
OpenBSD 3.8. My notebook does not support APM but ACPI and I
compiled ACPI support in my kernel. I run acpid and acpidump
displays a lot of output I don't understand ;-)

I read that i can get my battery values via

sysctl hw.sensors

but there is no 'sensors' sub under 'hw'. It seems that this is
because my hardware is not supported because it works fine on
my workstation for the temperature stuff.

Is there any way to get the battery-values? I bootet knoppix 4.0
and it was able to display my battery-values in KDE but I want
to use OpenBSD.

If it is not possibly: Is is generally possibly to develop some
code in userspace to do that or does the kernel not support it?

My dmesg output follows;
--snip-
OpenBSD 3.8 (AMILO) #5: Tue Feb 28 16:47:49 CET 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/AMILO
cpu0: Intel(R) Celeron(R) M processor 1.40GHz (GenuineIntel
686-class) 1.40 GHz
cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,
CMOV,PAT,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,SBF
real mem  = 199532544 (194856K)
avail mem = 175292416 (171184K)
using 2461 buffers containing 10080256 bytes (9844K) of memory
User Kernel Config
UKC quit
Continuing...
mainbus0 (root)
acpi0 at mainbus0: revision 0 attached
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpi device at acpi0 from table DSDT not configured
acpi device at acpi0 from table FACP not configured
acpi device at acpi0 from table APIC not configured
acpi device at acpi0 from table APIC not configured
acpi device at acpi0 from table SSDT not configured
acpi device at acpi0 from table SSDT not configured
bios0 at mainbus0: AT/286+(d2) BIOS, date 09/28/05, BIOS32 rev. 0 @
0xfd780
pcibios0 at bios0: rev 2.1 @ 0xfd780/0x880
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdf40/160 (8 entries)
pcibios0: PCI Interrupt Router at 000:17:0 (VIA VT82C596A ISA rev
0x00)
pcibios0: PCI bus #2 is the last bus
bios0: ROM list: 0xc/0xfc00 0xd/0x4000! 0xdf000/0x1000!
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 vendor VIA, unknown product 0x0314
rev 0x00
pchb1 at pci0 dev 0 function 1 vendor VIA, unknown product 0x1314
rev 0x00
pchb2 at pci0 dev 0 function 2 vendor VIA, unknown product 0x2314
rev 0x00
pchb3 at pci0 dev 0 function 3 vendor VIA, unknown product 0x3208
rev 0x00
pchb4 at pci0 dev 0 function 4 vendor VIA, unknown product 0x4314
rev 0x00
pchb5 at pci0 dev 0 function 7 vendor VIA, unknown product 0x7314
rev 0x00
ppb0 at pci0 dev 1 function 0 VIA VT8377 PCI-PCI rev 0x00
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 vendor VIA, unknown product 0x3344
rev 0x01: aperture at 0xf000, size 0x1000
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
vendor Broadcom, unknown product 0x4318 (class network subclass
miscellaneous, rev 0x02) at pci0 dev 6 function 0 not configured
cbb0 at pci0 dev 12 function 0 vendor Texas Instruments, unknown
product 0x8031 rev 0x00: irq 5
vendor Texas Instruments, unknown product 0x8032 (class serial bus
subclass Firewire, rev 0x00) at pci0 dev 12 function 2 not configured
pciide0 at pci0 dev 15 function 0 VIA VT8237 SATA rev 0x80: DMA
pciide0: using irq 9 for native-PCI interrupt
wd0 at pciide0 channel 0 drive 0: ST94813AS
wd0: 16-sector PIO, LBA48, 38154MB, 78140160 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
pciide1 at pci0 dev 15 function 1 VIA VT82C571 IDE rev 0x06: ATA133,
channel 0 configured to compatibility, channel 1 configured to
compatibility
pciide1: channel 0 ignored (disabled)
atapiscsi0 at pciide1 channel 1 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: HL-DT-ST, RW/DVD GCC-4244N, 1.00 SCSI0
5/cdrom removable
cd0(pciide1:1:0): using PIO mode 4, Ultra-DMA mode 2
uhci0 at pci0 dev 16 function 0 VIA VT83C572 USB rev 0x81: irq 10
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: VIA UHCI root hub, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1 at pci0 dev 16 function 1 VIA VT83C572 USB rev 0x81: irq 10
usb1 at uhci1: USB revision 1.0
uhub1 at usb1
uhub1: VIA UHCI root hub, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
ehci0 at pci0 dev 16 function 4 VIA VT6202 USB rev 0x86: irq 5
usb2 at ehci0: USB revision 2.0
uhub2 at usb2
uhub2: VIA EHCI root hub, rev 2.00/1.00, addr 1
uhub2: 4 ports with 4 removable, self powered
pcib0 at pci0 dev 17 function 0 VIA VT8237 ISA rev 0x00
auvia0 at pci0 dev 17 function 5 VIA VT8233 AC97 rev 0x60pci_intr_map:
no mapping for pin C: couldn't map interrupt
VIA VT82C686 Modem rev 0x80 at pci0 dev 17 function 6 not configured
vr0 at pci0 dev 18 function 0 VIA RhineII-2 rev 0x78: irq 10 address
00:40:ca:da:4a:65
ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface
ukphy0: OUI 0x004063, model 0x0032, rev. 10
cardslot0 at cbb0 slot 0 flags 0
cardbus0 at 

Re: acpi battery state

2006-03-01 Thread Marco Peereboom
This is bad advice at the moment.  ACPI has some memory leaks and 
eventually will deplete device buffer memory.  It is under heavy 
development and nowhere near consumable quality.


Don't run with ACPI unless you are writing me some diffs.

Rogier Krieger wrote:

On 3/1/06, Steffen Wendzel [EMAIL PROTECTED] wrote:

I try to find out how many energy is left on my battery. I run
OpenBSD 3.8. My notebook does not support APM but ACPI


In that case, you should probably give -current snapshots a spin.
There has been quite a bit of work on ACPI since 3.8. Apart from the
list/source-changes archives, you may want to take a look at several
articles at undeadly.org regarding ACPI.



but there is no 'sensors' sub under 'hw'. It seems that this is
because my hardware is not supported because it works fine on
my workstation for the temperature stuff.


Possibly, you have lm(4) or other sensor devices on your workstation.
The sysctl output should show you which sensor it uses.



Is there any way to get the battery-values? I bootet knoppix 4.0
and it was able to display my battery-values in KDE [...]


Fortunately, that means your hardware itself is probably OK. You
should really try a -current snapshot to see whether ACPI support will
work for you.

Cheers,

Rogier

--
If you don't know where you're going, any road will get you there.