View Single Post
Old 18th August 2008
lvlamb's Avatar
lvlamb lvlamb is offline
Real Name: Louis V. Lambrecht
Spam Deminer
 
Join Date: May 2008
Location: .be
Posts: 221
Default

So far:
Box one: OpenBSD.
Snapshot 4.4 beta i/386 of April? works by just putting the harddrive from the former MB in it.
New install of 4.4 amd64 snapshot of August 13th, went fine, including pkg_add of *everything* I use. Since I rebooted it just halts after Pentium MT? support (in the blue background lines, so no logs).
Test will be kernel and world installed from source on a fresh or zeroed drive.

Box two: WinXP Pro SP3
No problem, still have to install coLinux and UWIN. Still is WinXP 32bit.
ArchLinux 64. Funny. First installed the core, selecting all available packages from base. System hang on installation of BIND (or was it DNS?).
New install with defaults then pacman -Sy no problem.
Fwiw, I could get a new Western Digital RE3 drive. Nice piece. Only buy the product numbers ending in *YS from WD.
Maxtor must have same high specs, but didn't found the proper webpages.

CentOS 64: first tried on OpenBSD box, but forgot that anaconda hates A6 partitions. Didn't got the usual message "partition is active", didn't got any massage at all.
Will retry later.

Slackware (always 32bit), till now, no way to install.

So, basically, my headless server/router works on OpenBSD, all I need.
My WinXP "emulation" machine can emulate many Linuces and has UWIN. Can dual boot with ArchLinux on which I can install the VirtualBox and emulate what coLinux can't.
As said, basically, I fill the bill of materials, run the stoopid Windows only apps, have darn Flash. Hope to get rid of the Windows if Wine works (Now release and not beta anymore).

Now two Morex Venus cubes taking the place of one midi-tower, each drawing 70W when the harddrives are working.
Noting that my half terabyte backup is in a separate eSATA/USB Antec enclosure.
My small contribution against greenhouse gases.

The Atom boards are really recent and new, they still have bugs.
I downloaded the specifications update (June 2008, hey! you call this an update ?
The document is named: 319978.pdf
The errata AAF4 seems to describe what I experience as this is application dependent, not OS.
Code:
AAF4         Writing the Local Vector Table (LVT) when an Interrupt is Pending
             May Cause an Unexpected Interrupt
Problem:
             If a local interrupt is pending when the LVT entry is written, an interrupt may be taken on the new interrupt vector even if the mask bit is set.

Implication: 
An interrupt may immediately be generated with the new vector when a LVT entry is  written, even if the new LVT entry has the mask bit set. If there is no Interrupt  Service Routine (ISR) set up for that vector the system will GP fault. If the ISR does  not do an End of Interrupt (EOI) the bit for the vector will be left set in the in-service  register and mask all interrupts at the same or lower priority.

Workaround: 
Any vector programmed into an LVT entry must have an ISR associated with it, even if that vector was programmed as masked. This ISR routine must do an EOI to clear any unexpected interrupts that may occur. The ISR associated with the spurious  vector does not generate an EOI, therefore the spurious vector should not be used  when writing the LVT.
BTW: re0 is a Realtek 8801, sound also is Realtek.
All in all, I find those 1.6GHz CPUs very cumfy for my usage. PC533 DRAMs and high specs hard drives surely play their part too.
__________________
da more I know I know I know nuttin'
Reply With Quote