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.


2. Download and create the white dwarf bootdisk and rootdisk images. Full README
   
   Download the ISO CD image from our ftp server
   This CD image should boot most IDE machines directly from the cd if your BIOS supports i.
   Note: These steps are not needed if you have the CD or the ISO
   
   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
   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 JUMPtec with the bootdisk.
   
   You should see the following during the boot process:
   
   RAM disk driver initialized: 16 RAM disks of 5000K 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 the hda device, you have a hardware problem.
   It should continue booting and then prompt for the rootdisk or cdrom.
   Either one can be inserted. Once that has been loaded, login as 'root' and type 'setup'
   


4. Choose and Format your media.
   
   

   Type in your partition using backspace as needed When it asks if you already have a partition choose no, unless you have already done this step, then choose yes to skip. If you choose no fdisk will be run for you. Delete any existing partitions using the 'd' command Create a new partition using 'n' The partition number should be 1 and the size should be default (16MB) Use the 'p' command to see the partition after creating it. You should see: Command (m for help): p Disk /dev/hda: 2 heads, 32 sectors, 490 cylinders Units = cylinders of 64 * 512 bytes Device Boot Start End Blocks Id System /dev/hda1 1 490 15664 83 Linux native Use the 'w' command to save changes and 'q' to quit if needed. If you want to format the chosen partiton chose yes at the next prompt



5. Choose CD or network install
   
   If you choose CD, skip step 6


6. Set up your networking.
   
   

   Next, the installer will run the 'netconfig' command Answer all the questions regarding your network You should see the following after netconfig has finished: eth0: Attempting TP eth0: using 10Base-T (RJ-45) The installer will use ping to make sure you can reach the selected host



7. Download the packages.
   
   

   The installer will install some required packages and allow you to choose from a list of others After completion, remove all floppies Press the reset switch If all goes well, the server should boot linux 2.4.18(or 2.2.20) from the FLASH drive and setup the following services: inetd(with telnet and ftp support) crond View a full list of white dwarf linux packages.

   
   

back to top


TROUBLESHOOTING:

• Ethernet comes up with errors:
  
  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 Jumptec board.
  The solution seems to be NOT to use 'reboot' or 'shutdown -r now' or anything but a cold reboot.
  The best way to reboot your system is 'shutdown -h now' and hit the reset switch once everything
  has been umounted. EMJ is working with Jump to try to fix this.
  
  
• 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 linux@emjembedded.com with questions. Check back for updates.


back to top