Hi,
I decided to buy a Packard Bell EasyNote XS which will be available in

the US from Walmart as the Everex Cloudbook sometime soon.
The device comes preloaded with Windows XP, so needless to say I want

to get that off ASAP and something more useful onto it.
Basically the device is an implementation of the reference design of

the VIA Nanobook without the touch screen.
Using OpenBSD 4.2 release the box works absolutely fine, however, the

acpi code fails to understand some of the structures and gives up.
Under OpenBSD -current, however, the device does seem to recognise

some of the acpi entires correctly and tries to initialise some of the

devices. Unfortunately it sticks just after printing the message about

acpitimer0.
Here's the last few lines...
mainbus0 at root

bios0 at mainbus0: AT/286+ BIOS, date 11/02/07, BIOS32 rev. 0 @

0xfdd64 SMBIOS rev. 2.4 @ 0xdc010 (47 entries)

bios0: vendor Phoenix Technologies LTD version "6.00" date 11/02/2007

bios0: PACKARD BELL BV Pegasus

acpi0 at bios0: rev 0

acpi0: tables DSDT FACP SSDT APIC MCFG

acpi: wakeup devices PCIO(S5) SP2P(S5) LAN_(S3) LID_(S3)

acpitimer0 at acpi0: 3579545 Hz, 24 bits
Once it sticks at that location you have to hold power (>3 seconds) to

get the thing to power off and whilst checking this out I have had

current and release kernels on the root of the fs. The interesting

thing is that once you boot this kernel and it sticks like this the

release kernel fails to boot and sticks at the message about the

kernel entry point once the boot loader has loaded it. For some quirky

reason if you attach a USB CD and boot from the install CD then

restart this seems to fix this issue. Very strange indeed.
I attach the acpidump output produced from a 4.2 release install and

was wondering if there is anything else that may help identify the

problem..?
Regards,
-Andy
/*

RSD PTR: Checksum=87, OEMID=PTLTD, RsdtAddress=0x3bee5663

  */

/*

RSDT: Length=52, Revision=1, Checksum...
[ message continues ]

OK, I now have a plain -current install with 3 kernels.
One has acpi disabled entirely, one is generic and one is compiled

with ACPIVERBOSE
The additional info from ACPIVERBOSE is..
.....

acpitimer0 at acpi: 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 SSDT not configured

acpi device at acpi0 from table APIC not configured

acpi device at acpi0 from table MCFG not configured
It is at this point that the machine hangs.
Additional noteworthy points..
boot -c seems to kill the keyboard so you can't enable/disable devices

at boot time on this machine.
I think the video BIOS actually enters boot in some horrible MGA mode

since the machine boots with yellow text and no blue background

attribute. All text remains yellow on black until you start the X

server and exit (presumably exits to CGA mode).
Anyway, pointers on the acpi issue?
BTW: This machine is pretty cool apart from that, it seems to run

OpenBSD well apart from the acpi issue.
It is a small form factor (8" screen), proper keyboard with trackpad

built in. The wired network works with a stock install, the card

reader works with a stock install. It has a 1.2Ghz processor, 1Gb RAM,

30Gb HDD and comes in at #350. A very cheap and fast device that sits

midway between the Zaurus and a... well its almost as good as a larger

laptop (screen resolution is the limitation I guess).
Regards,
-Andy
>