OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
Re: OQO2, was ""

From: Mark Kettenis (mark.kettenisxs4all.nl)
Date: Fri Feb 01 2008 - 16:26:49 CST


> Date: Thu, 31 Jan 2008 23:15:41 +0100
> From: =?UTF-8?Q?M=C3=A5ns_Nilsson?= <mansaxelkthnoc.net>
>
> >> Date: Tue, 22 Jan 2008 22:57:09 +0100
> >> From: =3D?UTF-8?Q?M=3DC3=3DA5ns_Nilsson?=3D <mansaxelkthnoc.net>
> >>=20
> >> That worked out just nicely. Sorry for lagging. The .tgz containing the
> >> files is here:
> >>=20
> >>OQO.tgz>
> >=20
> > Thanks.
> >=20
> > 0:15:0: VIA VX700 IDE
> > 0x0000: Vendor ID: 1106 Product ID: 0581
> > 0x0004: Command: 0007 Status ID: 0290
> > 0x0008: Class: 01 Subclass: 01 Interface: 8a Revision: 00
> > 0x000c: BIST: 00 Header Type: 00 Latency Timer: 20 Cache Line
> > Size: 00 0x0010: 00000000
> > 0x0014: 00000000
> > 0x0018: 00000000
> > 0x001c: 00000000
> > 0x0020: 0020d801
> >=20
> > Looking at this, something is screwed up with this machine. To
> > determine whether it's the hardware or the BIOS that's causing us
> > grieve, can you try the attached diff?
>
> <http://vvv.besserwisser.org/Public/OQO2-2.tar>

Cool, that made your disk quite a bit faster didn't it?

It also tells me that the hardware is fine, and that it's the BIOS
that is screwed up. It might be that there is a BIOS update for your
machine that fixes this. Could you check that out?