You can run cfdisk (or fdisk) on the image and see what it says.
$ fdisk my.img
Command (m for help): p
Disk my.img: 536 MB, 536739840 bytes
16 heads, 63 sectors/track, 1040 cylinders, total 1048320 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End
Blocks Id System
my.img 63 1048319
524128+ 83 Linux
Command (m for help): q
Honestly, I haven’t used gem5img is quite some time and just create disk images
manually. I usually do something like this:
$ truncate disk.img -s 1000M
$ parted disk.img mklabel msdos
$ parted disk.img mkpart primary 1MB 1047MB #Note this starts at 1MB rather
than the usual 32kb (sector 63) above. This is sector 2048
$ losetup -o 1048576 /dev/loop1 disk.img
$ mkfs.ext3 /dev/loop1
$ mount /dev/loop1 /mnt
<istall files>
$ umount /mnt
$ losetup -d /dev/loop1
Ali
On May 17, 2014, at 5:48 AM, Kiyeon Lee via gem5-users <[email protected]>
wrote:
> Hi, Ali.
> Thanks for your quick response.
> How can I check and set the partition type to Linux (83)?
>
> Are there something else I need to do besides running the gem5img.py script?
>
> Thanks.
>
> --Kiyeon
> Seems like maybe the partition time isn't set to Linux (83)?
>
>
> Ali
>
>
> On 16.05.2014 10:37, Kiyeon Lee via gem5-users wrote:
>
>> Hi.
>>
>> I need a 32-bit Linux disk image for hardfloat ABI compiled ARM binaries.
>> The pre-built disk images provided by the gem5 website
>> (http://www.gem5.org/dist/current/arm/arm-system-2011-08.tar.bz2) only
>> support softfloat ARM binaries.
>>
>> I followed the instructions written in the following webpage:
>> http://gem5.org/Ubuntu_Disk_Image_for_ARM_Full_System
>> I am using Ubuntu Core 12.04
>> (http://cdimage.ubuntu.com/ubuntu-core/releases/12.04/release/ubuntu-core-12.04.4-core-armhf.tar.gz)
>> to build a gem5 compatible disk image.
>>
>> However, I get the following error message during system bootup.
>>
>> "mount: unknown filesystem type 'none'
>> I tried ext2 and ext3 file systems when I created a blank disk image using
>> gem5img.py. Both ext2 and ext3 are giving me the same error message as above.
>>
>> Does anyone have any idea what I may have been missing?
>>
>> Thanks!
>>
>> -- Kiyeon
>>
>>
>>
>> _______________________________________________
>> gem5-users mailing list
>> [email protected]
>> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
>
>
> _______________________________________________
> gem5-users mailing list
> [email protected]
> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
