On Mon, Sep 26, 2011 at 7:38 PM, Ali Saidi <sa...@umich.edu> wrote: > On Mon, 26 Sep 2011 19:34:25 -0400, Anirudh Sivaraman <sk.anir...@gmail.com> > wrote: >> >> On Mon, Sep 26, 2011 at 6:34 PM, Ali Saidi <sa...@umich.edu> wrote: >>> >>> The image needs some sort of partition table and this one works perfectly >>> fine. >> >> Hi >> >> Thanks for the clarification. I ran the Android kernel ( built using >> the config files you provided) with the partition table based file >> image ( from the gem 5 site) and it seems to boot alright . At least >> there are no kernel panics. >> 1. I guess I ll have to add something to make a shell appear, because >> m5term seems to be idle after displaying some journaling messages >> related to the file system. > > The android kernel might not boot a normal file system. > >> 2. Do I need to add the partition table to the ext images I created as >> well ? Is that the reason I got a kernel panic in the first place. >> > > Yes.
Hi The journaling message appears whether I run an Android kernel or an Ubuntu kernel ( the one on the GEM5 site). It's because I am trying to run gem5 on the arm-natty-headless image which is an ext3 file system that requires journaling . m5term being idle without booting into the shell is also explained by the fact that the arm-natty-headless image is really large ie 3.5 GB or so. It probably takes a while to check the file system before booting ? Do you know roughly how long it takes to boot up this larger image without any checkpointing ? I switched to the linux-arm-ael.img file ( a much smaller image) & it boots into the shell correctly and quickly with both the Android and Ubuntu kernels where I could login as 'root'. No journaling messages were seen there because that seems to be an ext2 image . I would like to know how I can add these partition tables you mentioned to ext images that I create so that I can use them instead of the images from the site. The gem5 site only mentions how to create ext images. Also, I could document all of this once I am done, so that someone can find this useful later. Anirudh > > > Ali >> >> Anirudh >> >>> >>> Ali >>> >>> >>>> Hi >>>> >>>> I have a related question. I downloaded both the old and new versions >>>> of the ARM binaries and disk images from http://www.gem5.org/Download >>>> Once I extracted the tars, I cded to the disks directory and ran 'file >>>> *' in both. I see that the file type is x86 boot sector in the newer >>>> arm-system-2011-08.tar.bz2 tar ball and the file type is Linux ext2 >>>> file system in the older one. Have x86 file system images been bundled >>>> into the arm tar balls by mistake ? Below is the output from file* : >>>> >>>> anirudh@anirudh:~/Downloads$ file arm-system/disks/* >>>> arm-system/disks/ael-arm.ext2: Linux rev 1.0 ext2 filesystem data, >>>> UUID=7d6b3d62-f52a-4e74-9502-8ed8ee648c5c >>>> >>>> anirudh@anirudh:~/Downloads$ file arm-system-2011-08/disks/* >>>> arm-system-2011-08/disks/arm-ubuntu-natty-headless.img: x86 boot >>>> sector; partition 1: ID=0x83, starthead 1, startsector 63, 6291873 >>>> sectors, extended partition table (last)\011, code offset 0x0 >>>> arm-system-2011-08/disks/linux-arm-ael.img: x86 boot >>>> sector; partition 1: ID=0x83, starthead 1, startsector 63, 1048257 >>>> sectors, extended partition table (last)\011, code offset 0x0 >>>> >>>> >>>> Anirudh >>> >>> _______________________________________________ >>> gem5-users mailing list >>> gem5-users@gem5.org >>> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >>> > > _______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
