Dave, I already have tried a lot of times from scratch as you said, with the same bad result. Then I was reading on the list, and I found that I could run make [target].
Then, since the makeimage.sh script was complaining about some files not found, I re-make 2 packages: busybox, and grub. Then, I ran again the script, and this time it displayed like this: grub> setup (hd0) Checking if "/boot/grub/stage1" exists... yes Checking if "/boot/grub/stage2" exists... yes Checking if "/boot/grub/e2fs_stage1_5" exists... yes Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 16 sectors are embedded. succeeded Running "install /boot/grub/stage1 (hd0) (hd0)1+16 p (hd0,0)/boot/grub/stage2 /boot/grub/grub.conf"... succeeded Done. Unfortunately, I wrote the disk.img to the CF, but it didn't work. It doesn't boot. But, as you said, maybe is something missing during the entire make process.. the problem is to find out wich one. Arturo, ----- Original Message ----- From: "Dave Liszt" <[EMAIL PROTECTED]> To: "Discussion of AstLinux - Asterisk on Compact Flash" <[EMAIL PROTECTED]> Sent: Friday, June 23, 2006 12:50 PM Subject: Re: [Astlinux-users] Need some help with makeimage.sh script > 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 _______________________________________________ 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]
