The post below was submitted under the 'Midor Linux General Board' section. If you can comment please post there.
Hello,
Let me apologize in advance for the length of this post. I felt it important to supply all details as I'm currently at a loss for ideas.
Background and Steps Followed:
I've successfully installed Midori Linux onto a V5 IO but it refuses to install correctly on 3 other V5 systems (all 4 units were new and unused). After flashing the BIOS chips with a BadFlash v5.40 image I installed a 6Gig Fujitsu laptop hard drive running MS-DOS 6.2 freshly installed. This disk included dolly and m4i-2.2pre1.img which I saved as midori.img. Both files had been downloaded directly to the hard drive and unmodified once saved to disk.
Booting the first V5 IO I saw the V5.40 BIOS, Primary IDE Master was the hard drive and the Secondary IDE Slave was the SanDisk. BIOS settings had been set to AUTO detect both and to boot from 'C Only'. DOS started fine and gave me a prompt. I then ran fdisk, switched to the SanDisk, removed the partitions, create a new DOS partition and rebooted. After this I ran: "dolly midori.img hd129: /c" which completed fine. At this point I shutdown the IO, removed the hard drive and cable and restarted it.
It booted and listed 'none' as Master IDE and the SanDisk as the Slave IDE. It continued to boot through displaying the Midori bootup, heard sound initialize and then X started up! WooHoo Its Alive!!
Checked ctl-alt-F4 and ctl-alt-F1 which gave no errors. DHCP worked great and I was able to statically assign an IP and everything works perfect. Note here that I have reflashed the BIOS chip in this unit again after this install to the current V5.40a BadFlash BIOS version and it continues to run perfectly. I was able to stream MP3s over the network for a 24hour period without any problems.
The Problem:
OK so the first IO is up and running perfectly and was very smooth to install. The problem now is that I've followed the exact same proceedure for 3 other identical V5 IOs and they all end in failure. Dolly seems to copy the image fine and says it completed successfully. I then reboot the IO (removing the hard drive and cable as before) only to have the Midori boot proceedure screwup with errors ('/tmp/loop30: No such device' is the first) leaving me at a prompt. I have attempted a number of different 'solutions' found on this BBS without success. I have replaced the flashed V5.40 with a flashed V5.40a and with an original V5.40a chip from BadFlash, swapped out IDE cables and have run Dolly with the /c switch and without. I've also redownloaded the dolly program and the Midori image to a different directory and tried those. I've formatted the hard drive, reinstalled DOS and downloaded dolly and the Midori image again. I've run fdisk with the /mbr switch, checked the md5sums of the images, run scandisk on both the hard drive and SanDisk and still nothing is working! I dont know what to try next! 
Here is the Midori Boot sequence with errors:
Starting init (return here with ctl-alt-F1)...
Fixing USB by tweaking PCI registers...
Mounting RW filesystems...
Building devpts...
Creating loopback interfaces...
Mounting usr partition...
/tmp/loop30: No such device
packcramfs: error opening loopback device
Thawing config partition to /tmp/config...
/tmp/loop30: No such device
packcramfs: error opening loopback device
/tmp/loop30: No such device
packcramfs: error opening loopback device
Setting timezone...
Starting logd (use ctl-alt-F4 to see it)...
Starting network...
.: Can't open /tmp/config/network
/sbin/portmap: error in loading shared libraries: libnsl.so.1: cannot open shared object file: No such file or directory
Loading hardware monitoring modules (run 'sensors' to see values)...
/sbin/init: /usr/bin/sensors: No such file or directory
spawming shell (return to root shell with ctl-alt-F1)...
BusyBox v0.60.2 () Built-in shell (ash)
Enter 'help' for a list of built-in commands.
#_
Again, this has worked on 1 system perfectly and failed on 3 others all of which are new/unused V5s with no other changes or modifications except for the BIOS. If anyone can offer any suggestions I'd appreciate it muchly!
Thanks,
Adrenolin
i-opener@irchottub.net