But it looks altboot with root fs on SD is not usable righ now. It's pitty.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=120756\"][{POST_SNAPBACK}][/a][/div]
Funny, I use that day in day out....
[div align=\"right\"][a href=\"index.php?act=findpost&pid=120999\"][{POST_SNAPBACK}][/a][/div]
Ok, then please help me. I am on tosa and have tried the experimental altboot version. When booting either sd (1GB in 3 partitions, 2 ext2, one vfat)) or cf (one partition ext2) it hangs in the /dev/loop0-sequence. It cannot read the file-system. OZs are stored in the /boot-images/ folder and they are correctly recognized.
Normal boot into opie works fine.
Thank you in advance for advice
Sebastian
[div align=\"right\"][a href=\"index.php?act=findpost&pid=121117\"][{POST_SNAPBACK}][/a][/div]
Are you sure you are trying to boot a ext2 loop-image and not a .jffs2 fashable rootfs?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=121118\"][{POST_SNAPBACK}][/a][/div]
Ok, got that. Be patient with me, I am only a philosopher. But altboot is still resisting. It had problems accepting the sd-card configuration mentioned above, with a splitted card (500 mb vfat and 500 ext2) it is more happy. After having learned by myself how to transfer bz2-archives into tar.gz ones (why that, by the way? why do we find files in the feed we cannot use?), the rootfs-building process of the e-17 image went fine ... just until the end. Again altboot is not satisfied with loop0, next time I will write the exact formulation, but it is looking for something that doesn't exist.
Has anybody here installed e-17 image via altboot on tosa using altboot? Am I doing something wrong or is there a mistake inside...?
Thanx!
The message is: losetup:ioctl: LOOP_CLR_FD: No such device or adress