On 30 November 2010 21:07, Martin Hejl <mar...@hejl.de> wrote:
> Hi Per,
>
>> Booted OK but stuck on /dev/sda1 does not exist as no partition exist.
>>
>>
>> Tried several ways of creating a partition with no  .
>> Linux host does not recognize a filesystem.
>>
>> I also tried making a disk.img with qemu-img and from
>> qemu -cdrom sysrecover.iso -hda disk.img -boot order=d
>>     fdisk  /dev/sda
>>     mkfs.vfat  /dev/sda1
>>     syslinux /dev/sda
>>
>> Back in host i tried mount -o loop offset=nnn  + losetup method
>> With losetup on disk.img, fdisk  can see the partition.
>> BUT don't seem to be able to mount and get a reconisabel filesystem
>>
>> Can someone provide a real Image from a 64 M CF-card.
>> For analysing and comparing of structure
>>
>> David I belive the subject needs a wiki-page, where do you want it in the 
>> structure user/installation or development?
>> I can write it. (please enable talk page for taspts)
> I don't know if things might have changed (I haven't tried Bering uClibc
> 4.0 yet, due to lack of time) - but I wrote down the aproach that has
> worked for me countless times (setting up both VMs as well as "real"
> boxes with a CF) in the help section of the hdsupp package:
>
> http://leaf.cvs.sourceforge.net/viewvc/leaf/src/bering-uclibc/apps/hdsupp/buildtool.cfg?revision=1.25&content-type=text%2Fplain
>
> As long as you get the box to boot (via CD-Rom, PXE or some other
> means), and have access to the additional LRPs, it should work (IMHO -
> as I said, untested on Bering uClibc 4.0).

Hi Martin,

Your logic is good. I tried booting qemu from the CD-ROM image and
with a (blank) hard drive image this morning, with a view to using the
hdsupp tools to fix up the hard drive image and then copy the files
from the CD-ROM. It *should* work but right now we have a problem with
/sbin/fdisk from hdsupp.lrp which I have just confirmed - See
http://sourceforge.net/apps/trac/leaf/ticket/11 :-(

If I understand correctly what Per is trying to achieve, he also wants
to be able to copy (as in "dd") the configured image to a real CF card
or similar, so for that we need to crack the problem of what a CF
image looks like (I think the issue is disk geometry).

Not sure it is possible to fix this in a generic way... Floppy disks
are standard, so a floppy disk image is standard, but I get the
impression that USB and CF flash drives are much more variable. Still,
if someone can start with their own real flash drive, partition and
format it, then "image' it it should be possible to mess with the
image using qemu or similar and copy it back to the physical flash
drive later.

dMb

>
> Martin
>
> --
> He will win who knows when to fight and when not to fight.
>        Sun Tzu, The Art of War
>

------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev

_______________________________________________
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to