gediaParticipant25 April 2013 at 16:15Post count: 6
Well, I was a little too quick to report success with HS3’s version 4.0 firmware.
I have installed debian on a KVM virtual machine, and I’m using virtio for storage which means that the disks are reported as /dev/vda and /dev/vdb
In my case, vda holds the root partition for debian and vdb is configured as follows:
Disk /dev/vdb: 2147 MB, 2147483648 bytes
16 heads, 63 sectors/track, 4161 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xe81e0ec8
Device Boot Start End Blocks Id System
/dev/vdb1 1 5 2488+ 1 FAT12
/dev/vdb2 6 2087 1049328 83 Linux
/dev/vdb3 2088 3124 522648 6 FAT16
/dev/vdb4 3125 4161 522648 6 FAT16
I then edited hsmain with a hex editor and replaced all disk instances such as “/dev/?d?” with “/dev/vdb”. This used to work in the past.
Now, however, although I was able to upload initial configuration via the serial port, uploading any other project via the network fails with “Project too large” errors. (Projekt zu gross – Projekt wurde vom Geraet abgewiesen)
Any ideas how to solve this?gediaParticipant29 April 2013 at 14:14Post count: 6
Problem solved thanks to post #1449 by micha. Instead of replacing all instances of /dev/hdb with /dev/vdb with a hex editor, replace all instances of hdb with vdb (match case to be safe).
- You must be logged in to reply to this topic.