Biostar iDEQ 220k and Fedora Core 4

Table of Contents:
Last update: 2007-01-09 (replacement with a new machine)

I got a new machine to replace two older Linux machines, including shell accounts, e-mail, cvs, web, and firewall. The old machines are traditional towers with 5 total hard disks and a half dozen or more noisy fans. The new machine is "small form-factor", will have one hard disk and low/adjustable-RPM fans.

The higher-powered of the machines it is replacing is a 1GHz Duron with 512 megs of RAM. In most respects this is still a perfectly adequate machine, but its OS (FC1) is beginning to show its age, and the RAM is often inadequate, especially since Ingrid is running a full set of desktop apps on it, including Firefox and OpenOffice. The new hardware should be overkill in most respects: More MHz, more RAM, more disk.

Hopefully this machine will live up to the reliability standards of the old machines: until the power goes out, or the reset switch gets hit, or the power supply capacitors catch fire. (Note to self: find a supplier for a replacement power supply, since you can't just hook up any old ATX one)

The lists below are mostly notes for myself about the services I'll be moving to the new machine, but may someday be useful for others searching for info on the Biostar iDEQ 220k, especially when it comes to running Linux, Unix, RedHat or Fedora Core on it.


Virtually everthing worked out of the box. The only thing I didn't try to do was use the onboard Via UniChrome PRO video. I copped out and put in a spare G400 AGP card before I booted the Fedora installer. So far, I'm happy with this machine and would suggest it to someone wanting to build a powerful but small AMD64 system. Until a year or so has gone by, though, I won't know if bad reliability or increasing fan noise will turn me against the iDEQ.

2005-09-06: I had a few unexplained lockups, but after connecting the "ATX12V" power they seem to have stopped. After a year, I remain pleased overall with the purchase. The performance is entirely adequate, the reliability is good, and the fan noise is still not bad.

2006-09-06: I tried the onboard Via UniChrome PRO video. With the "vesa" driver, the console turned black and wasn't usable again without rebooting. Back to the G400 AGP card.

2006-09-21: I installed the BIOS update "Vbk1227bf" from a floppy disk. Now, powernow-k8 can successfully change the CPU speed but I have had several lockups in the 24 hours since enabling the cpuspeed daemon.

2007-01-09: In view of the decision of the Fedora Legacy project to shut down, I have decided to move my server to Ubuntu 6.06 LTS. Because it takes quite some time to set up the large number of services, I've used this to justify the purchase of a new system. The ideq is still a perfectly adequate machine, but I just couldn't handle the X2 envy an longer. Later on, I plan to reinstall the ideq with Ubuntu LTS and work on an emc2 port to 64-bit machines.


The total cost of the hardware I bought was $688 with second-day shipping from, If I had to do it again, I'd skip buying the DVD drive and temporarily put in a drive from a different machine instead.

I scrounged these parts from home and office:

If you're on more of a budget, get less RAM, a smaller disk, and a 32-bit AMD processor instead. You should be able to get down to around $500 this way. Yes, it's bigger than a Mac Mini, but it's also more powerful.

iDEQ 220k: What's in the box

Since Biostar hasn't bothered putting the manuals online yet, and newegg didn't say, I wondered what was included with the iDEQ, especially whether there were SATA power and data cables. Well, there are.

iDEQ 220k: Inside the case

The case has an external 5 1/4 and 3 1/2 inch bays plus two internal 3 1/2 bays. Each bay has the appropriate power cable and drive cable nearby, and the internal bays have both a traditional and SATA power connector. There's only one SATA data cable included, and it is packaged separately rather than preinstalled.

Others have said that the inside of the case is very nice, with rounded edges and prerouted cables. For the most part I've found this to be true. Two exceptions:

iDEQ 220k: Unexpected Parallel bonus

Near the front panel, there is a 26-pin connector marked JPRNT1. Using a spare cable from the office, I've routed this to the back where there's a punch-out hole for a DB25 connector. The cable was just long enough to reach from the connector to the back of the case. There does not appear to be a second serial port, however.

iDEQ 220k: BIOS settings

The BIOS allows you to choose whether or not to pause the bootup process for certain errors (e.g., missing keyboard), and whether the power should be on, off, or the same as before a power loss. Another nice feature is a keystroke to change the boot device just once, so that you can leave the hard disk as the default device, but easily boot an installation CD once in a blue moon.

iDEQ 220k: PC Health measurements

These values are from the BIOS setup screens. Linux' lm_sensors installs but doesn't give plausible results.

Supply Actual Voltage Error ATX tolerance
VCore (+1.4) 1.36 2.85% low N/A
+1.5 (AGP) 1.61 7.3% high N/A
+3.3 3.20 3.0% low 4%
+5.0 4.86 2.8% low 5%
+12.0 11.45 4.58% low 5%
V bat. (3.3?) 3.13 5.2% low? N/A

iDEQ 220k: Power Management

2006-09-21: I installed the BIOS update "Vbk1227bf" from a floppy disk. Now, powernow-k8 detects a capable CPU:
powernow-k8: Found 1 AMD Athlon 64 / Opteron processors (version 1.60.2)
powernow-k8:    0 : fid 0xa (1800 MHz), vid 0x6 (1400 mV)
powernow-k8:    1 : fid 0x2 (1000 MHz), vid 0x12 (1100 mV)
cpu_init done, current fid 0xa, vid 0x6
Before the BIOS update, there was an error in dmesg instead: powernow-k8: BIOS error - no PSB or ACPI _PSS objects

But now I have had several lockups in the 24 hours since enabling the cpuspeed daemon, and will be going back to a fixed-CPU-speed setup..

iDEQ 220k: The Stupid Color-Changing LED

The blinding blue hard-drive activity LED is bad enough, but the "power on" LEDs change colors constantly in a predefined sequence of colors. I wish I could make it stop. For now, lowering the plastic piece that hides the drive bays mostly blocks the light and also prevents accidentally touching the power switch. 2006-09-06: Fixed! While the front panel items all go to a single connector at the motherboard, the power LED has a separate connector in the middle, which I've now disconnected.

CPU Markings

Bottom: 27973
Top: SDA3000AIO2BX / LBBWE 0527RPAW / Z722797G54288 / Assembled In Malaysia

SCSI Tape Backup

2006-09-21: I replaced the internal PCI network card with a USB NIC (DUB-E100 rev-B which required kernel patching before use---beware this device) so that I could add a BusLogic SCSI controller, which runs an external HP SureStore DLT70 tape drive. This works nicely so fa but the fan in the tape drive's enclosure is unfortunately quite loud.


I'm running the 64-bit version of Fedora Core 4. The main tasks the machine performs are:

Other software: memtest

I let memtest run for about 80% of a cycle. No errors were detected. The full cycle would have taken something over an hour.

Other software: FreeBSD 4.11 (32 bit)

Installed great from Mini Install CD. Recognized drive as SATA. Kernel compiled in under 3 minutes wall time.

Other software: Ubuntu 'Hoary Hedgehog' (32 bit)

Installed great from CD. Recognized drive as SATA. "dd" and "hdparm" both reported very nice numbers, over 60 MB/second, for disk transfer rates. Kernel only used 860MB(?) of RAM.

Fedora Core 4

I had already downloaded the 2.7GB of stentz-binary-x86_64, and burned the first CD. Using linux askmethod, I used the .iso images from the network. One install errored out, something to do with the Logical Volume Manager (LVM). When I installed again, I made traditional partitions, not LVM partitions, and everything worked. This is apparently a known bug.

After the install, there were over 600 megabytes of updates, which "yum" took its sweet time downloading. I also installed a few more packages with "yum", and rebuilt icewm from a source RPM.

There's been one really weird thing since installation: Some .pyc file became corrupted. I don't know if it was corrupt on disk, or in RAM. The symptom was that running 'yum' would exit with a traceback about site-packages/PIL/ I fixed it by removing a bunch of .pyc files. I'm tempted to do a longer memtest run to see if it exposes a problem.

Software: mock

Contrary to what I expected, rpmbuild --arch i386 ... is not enough to build a 32-bit RPM on an x86_64 machine. Instead, something called mock must be used.

The full incantation ends up looking something like this: rpmbuild -bs foo.spec; setarch i386 mock --no-clean ../SRPMS/foo-1.0-0.src.rpm. Without the additional setarch, one build failed when it tried to run gccmakedep-x86_64, which wasn't installed in the mock environment.

Software: tightvnc, tightvnc-server

I was unable to get tightvnc to build, either as a 64-bit or 32-bit package. Instead, I installed a binary package for fc3/i386. It seems to work.

Using mock I've now built a binary package for fc4/i386. I haven't tested it yet.

Software: irssi

The package "irssi-0.8.9-7.x86_64.rpm" doesn't work. When running irssi, a dynamic linker error libgc undefined symbol: pthread_mutex_trylock is printed. I installed an fc4/i386 package instead. Since that time, I upgraded to gc-6.6-4.fc4.x86_64 and irssi-0.8.10-1.x86_64 which work properly.

Software: uw-imap

Due to license issues, Fedora has dropped uw-imap. However, I have all my mail in their "mbx" format. So I've built a uw-imap RPM based on my own spec file. It's now lightly tested and seems to work just fine. At the moment I'm using dovecot, though.

Software: swish-e

Swish-e isn't packaged in fedora or fedora-extras (what full-text indexer is?) and the included specfile doesn't work. So I had to built it myself. The good thing is that it seems to work properly on 64-bit systems.

System Information

dmesg lspci cpuinfo

SATA, Audio, USB, and ethernet all work out of the box.

FireWire appears to be detected, but I have no devices to test with.

The onboard video does not work with Fedora Core 4's X server using the "vesa" driver.

Future Upgrades

There's not much of an upgrade path for this machine. Nevertheless, there are a few things I might change before this system becomes obsolete. It should be possible to place a second hard drive in the case, or to add an external USB 2.0 or firewire drive. It would be possible to upgrade the CPU, but options are limited for "socket 754".


Here are some of the pages I've found while searching for information about the hardware I bought.


There's nothing scientific here, but how is that different from many of those hardware review sites?
Traceback (most recent call last):
  File "/home/jepler/", line 766, in markup
    text = getattr(this_module, 'markup_'+command)(text, meta, **thing_context)
AttributeError: module '__main__' has no attribute 'markup_comments'

Website Copyright © 2004-2024 Jeff Epler