Hey Arturo, In case this reply is not too late to be useful..
I find makeimage.sh to be pretty scary in general, and that it's hard to know which warnings and errors can safely be ignored and which cannot. In particular, I've also seen this error: On 6/22/06, Arturo Ochoa <[EMAIL PROTECTED]> wrote: .. > >> 5.grub> setup (hd0) > >> Checking if "/boot/grub/stage1" exists... no > >> Checking if "/grub/stage1" exists... no > >> Error 15: File not found and that's one that should not be there, I think. In my case it meant that something had screwed up during my prior 'make' attempt(s), and I was now trying to makeimage.sh on an incomplete and/or busted root filesystem. In my case the path to the solution was to go back and recheck and redo the previous steps, in particular the 'make', trying to ensure that everything seemed to go okay there -- such as not ending with output mentioning 'Error's or lines beginning with '***' and stuff like that. Getting a 'cleaner start' with: rm -rf build_i586 rm -rf toolchain_build_i586 on occasion also helped, particularly once I started changing .config for one thing or another. In the astlinux tree at the moment, in my experience astmanproxy (recently discussed on this list) and chan_sccp are two of the things that particularly like to blow up and fail to build successfully, each for their own particular reasons. But there's a million variations and it all seems like a pretty rapidly moving target, so it's hard to be more specific... - Dave > >> > >> > >> I'm getting this warnings and errors, and when it finishes then I'm using > >> the physdiskwrite.exe program to write on to the CF, but it doesn't boot. > >> I > >> can't see anything related with astlinux, not even the boot loader. > >> > >> Best Regards, > >> > >> Arturo, > > > > Arturo, > > > > SIZE should be a number (in megabytes) - I have been using 48 > > > > -- > > Kristian Kielhofner > > _______________________________________________ > > Astlinux-users mailing list > > [email protected] > > http://lists.kriscompanies.com/mailman/listinfo/astlinux-users > > > > Donations to support AstLinux are graciously accepted via PayPal to > > [EMAIL PROTECTED] > > > > Kristian, > > I already tried with 32, 48 as you said, 128, even 256. That is why I wrote > SIZE. > So, I think it doesn't matter the size of the disk.img since inside the > script the following line will create the disk.img using the size parameter: > > #dd if=/dev/zero of=disk.img bs=1024k count=$SIZE > > I think the problem is when the script calls the fdisk, but I couldn't find > anything related to the errors and warnings that is displaying. > > Best Regards, > > Arturo > > > _______________________________________________ > Astlinux-users mailing list > [email protected] > http://lists.kriscompanies.com/mailman/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to [EMAIL > PROTECTED] > _______________________________________________ Astlinux-users mailing list [email protected] http://lists.kriscompanies.com/mailman/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
