No subject


Fri Dec 2 23:53:25 EST 2005


might
be a slightly different model, since things like the fan level and
fan_policy settings
are slightly strange (fan is always at 38 and policy levels are all 0 except
for levels
6 and 7 which have reasonable values).  I can change fan on and fan off
values,
but they don't seem to have an effect.

Setting LCD brightness levels work, as does reading battery status, but
again
an oddity: when running on AC power, the status value is 0x80 and this
registers
as "unknown" when you cat /proc/omnibook/battery.

The DMI info is:
BIOS Vendor:   TOSHIBA
BIOS Version:  V1.20
BIOS Release:  09/12/2003
System Vendor: TOSHIBA
Product Name:  Satellite P10
Version:       PSP10E-34FJR
Serial Number: Y3639949G
Board Vendor:  TOSHIBA
Board Name:    DAL00
Board Version: Null

I can also supply the DSDT if anyone is interested in looking a little
deeper.
Likewise, I'd like to take a look at the DSDT from a known XE3GF machine
so that I can compare them and perhaps learn about the differences. (maybe
even fix the ACPI readings for the battery level too).

echo "off" > /proc/omnibook/fan will go into an infinite loop in kernel mode
on this machine.  That code probably should only be enabled by a compile
time option to save nasty problems.

I'd really like to get the fan stuff working, and also feel assured that the
machine
won't mysteriously power down for no apparent reason--this has happened
twice now after doing a lot of compiling--it's not an overheating problem
since
the temperature is around 40-50 when it happens (it's cooled down).  The
second time it happened I noticed the battery LED was blinking (== low
power)
even though it was on AC power and had been that way for a few hours.
Removing the AC lead and re-connecting it stopped the blinking.  Sounds
a bit nasty :/   I run this box as a dual boot into WinXP and wonder if the
toshiba power management drivers are leaving something nasty in memory when
I reboot...

Anyway, if anyone has any information on this model (perhaps you can
positively
identify the controller?), I'd love to hear it.

Thanks!

--Wez.




More information about the OmniBook mailing list