Services | Pricing | Installation | FAQ | Email List | In The News



Installing white dwarf v2.2.0 (kernel 2.4.29) on a Kontron, Tri-M, Soekris or other x86 board

A single board computer from Kontron(DIMM-PC, MoPS), Tri-M(MZ104), or Soekris(45xx or 48xx)
... or pretty much any board with >=16MB RAM and an IDE or SCSI drive >= 16MB ...

(wdlinux 2.2.0 has kernels for 386, 486, k6, elan, 586, crusoe, p2, p3, athlon, and p4 with multi-CPU support for p2, p3 and p4 boards)

Also needed, one of the following install devices:

  • floppy drive and (2) blank 3.5" 1.44MB floppies
  • ATAPI compatible IDE CDROM
  • Network install:
    • Ethernet-based Internet connection. See supported network cards.
    • DHCP server connected to the internet or ...
      • IP address of your machine
      • IP Gateway for your IP
      • Netmask for your IP
      • DNS server for your network(optional)

^ top


  1. Set the clock in the BIOS to the correct time.

    If this is not done you will end up getting a number of fsck errors as the system thinks the hard drive filesystem has gone too long without being checked.

    Password and other utilities may also be affected by an incorrect date. If you are installing via the internet and using DHCP, the date should be handled automatically on most BIOS's.

  2. Download and create the white dwarf bootdisk and rootdisk images. Full README

    Download the wdlinux 2.2.0 ISO CD image(353 MB) from our ftp server. This CD image should boot most IDE machines directly from a CDROM if your BIOS supports it.

    Note: The bootdisk steps are not needed if you are installing from CD.

    Download the bootdisk from our ftp server.
    Download the rootdisk from our ftp server.

    Using a linux machine do the following:

    dd if=wdboot.img of=/dev/fd0

    Insert another clean floppy use these commands:

    mkfs /dev/fd0
    mount /dev/fd0 /mnt
    rm -rf /mnt/lost+found/
    cp root2.tar.bz2 /mnt
    umount /mnt

    You can also use a DOS machine to do this. Use RAWRITE.EXE.

    C:\> RAWRITE

    Answer the prompts for the name of the file to write and the floppy to write it to (such as A:). Do the same for the rootdisk.

    Burn the ISO image w/o translation as an ISO9660 CD-R. This should work with any CD burner, but DO NOT burn a multisession disc.

  3. Boot your board with the bootdisk or CD.

    You should see something like following during the boot process:

    RAM disk driver initialized: 16 RAM disks of 8192 size
    hda: SunDisk SDTB-128, ATA DISK drive
    ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
    hda: SunDisk SDTB-128, 15MB w/1kB Cache, CHS=490/2/32

    If you don't see an hda (or sda for SCSI systems) device, you are likely using unsupported hardware. Please email the mailing list with your configuration details.

    The board should continue booting and find the network if you have a supported card and a DHCP server.

    If not then a prompt to insert the rootdisk or cdrom will appear. Either can be inserted. Once the root disk been loaded, the wdlinux installer will launch.

  4. Choose and Format your media.

    • Create partitions with cfdisk.
    • Add/Edit partitions to use during installation (choose 'View' if you get confused).
    • Setup RAID 1 using linux software RAID tools (optional and experimental).
    • You can format partitions as ext2, ext3 or reiserfs from the installer.

  5. Choose your install media.

    Network install is preferred, but installing from a local CD is also an option.

  6. Choose the size of your installation.

  7. Next, the installer will ask which size install to use, there are 4 options:

    • Small - suitable for embedded systems with 16-32MB Flash storage. Uses the x86 2.4.29 kernel from the base package

    • Medium - suitable for 32MB and larger storage devices, shows the custom kernel menu for CPU and boot device selection

    • Large - suitable for larger systems with >= 64MB storage, shows the custom kernel menu and all the optional packages one by one

    • Supersize - suitable for larger server systems with >= 72MB of storage, shows the custom kernel menu and installs all optional packages

  8. Select kernel.

    • If you chose medium, large or supersize, you will be asked to select a kernel.

    • Select the CPU and boot device that most closely matches your architecture
      (ie. 486 DIMM-PC boards booting from IDE would choose lk2.4.29_wd2.2_486_ide.tgz
      Tri-M MZ104 boards booting from IDE would choose lk2.4.29_wd2.2_crusoe_ide.tgz
      soekris boards booting from IDE would choose lk2.4.29_wd2.2_elan_ide.tgz
      Dual Pentium 4 boards booting from an ICP Vortex RAID would choose lk2.4.29_wd2.2_p4SMP_icp.tgz, and soon on...)

  9. Post installation

    After the installer has downloaded and installed all the selected packages you will be prompted to:

    • Choose to boot into a VGA or serial console (serial is good for soekris and other boards w/o VGA hardware).
    • Unless you chose the small install, you'll be prompted to select your timezone.
    • Finally you will need to enter a password for the root user so you can login after reboot.
    • After reboot login as root with your password and check the FAQ or mailing list for any questions.

^ top



  • Watching the install log:

    Press the 'alt' key plus F4 to see what the installer is doing (this data also lives at /tmp/wd/log).

  • System maintenance:

    Press the 'alt' key plus F2 or F3 to login to a console (login as root with no pw) if you have network access, try typing 'tools' here to load fsck and other useful tools.

  • Ethernet comes up with errors on a DIMM-PC:

    eth0: unknown interface: no such device
    cs89x0.c: No card found at 0x300

    There is a problem with the cs89x0 driver and the Crystal chipset used on the Kontron boards. The solution seems to be NOT to use 'reboot' or 'shutdown -r now' but rather a cold reboot. The best way to reboot your system is 'shutdown -h now' and hit the reset switch when told to 'Power Down.'

  • During access to hda1 (the FLASH disk), you may see the following:

    hda: hda1
    hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
    hda: drive_cmd: error=0x04 { DriveStatusError }

    This is normal AFAIK, and does not seem to cause any problems.

The Changelog is also available.

Please email the mailing list with questions.

^ top