[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bootable USB images



On Sun, Jan 03, 2010 at 03:31:24AM +0100, Aurelien Jarno wrote:
> On Fri, Jan 01, 2010 at 02:30:20AM +0100, Robert Millan wrote:
> > On Thu, Dec 31, 2009 at 02:52:25PM +0000, Thorsten Glaser wrote:
> > > Is there something you special-cased when handling CDs or not-CDs? (For
> > > example, grub-legacy doesn’t handle iso9660 from media with !2048by
> > > sectors at all.)
> > 
> > There is, but I don't think it has any relation to this problem.  iso9660
> > filesystems in non-CD are known-stable code.  Only the boot mechanism is new.
> > 
> > In fact, I have some ideas on what could be causing this, but unless I can
> > reproduce it, I'm wary of sending shots in the dark.  And despite all my
> > efforts I've been unable to reproduce it:
> > 
> >   - I grabbed Aurelien's mini.iso and extracted its files.
> >   - I used the same version of grub-pc and grub-common as Aurelien
> >     (1.98~20091229-1) to generate a new image.
> >   - I did this on kfreebsd-i386 (I specifically installed the i386
> >     flavour to test this).
> > 
> > I also tried today's Bazaar trunk and kfreebsd-amd64 before that.  It _always_
> > works for me.
> > 
> > Except when I use the mini.iso directly, of course, but that's not very
> > useful...
> > 
> > Aurelien, could you try building the image in another environment?  E.g.
> > kfreebsd-amd64 and/or using a newer grub-pc.
> > 
> 
> I upgraded both my kfreebsd-i386 and kfreebsd-amd64 machines to 
> 1.98~20090101-1. It still fails on kfreebsd-i386, but works on
> kfreebsd-amd64. I haven't investigated why though.
> 

It is due to (the size?) of /boot/mfsroot.gz. Using the one from
kfreebsd-amd64 on kfreebsd-i386 makes it working, though it later fails
when trying to run /sbin/init.

-- 
Aurelien Jarno	                        GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel32.net


Reply to: