Re: Bootable USB images
- To: Robert Millan <rmh@aybabtu.com>
- Cc: debian-bsd@lists.debian.org
- Subject: Re: Bootable USB images
- From: Aurelien Jarno <aurelien@aurel32.net>
- Date: Sun, 3 Jan 2010 03:31:24 +0100
- Message-id: <20100103023124.GK5837@hall.aurel32.net>
- In-reply-to: <20100101013020.GA21541@thorin>
- References: <20091216235341.GB4963@doyle> <Pine.BSM.4.64L.0912171253550.21089@herc.mirbsd.org> <5a6cd4690912170531q263ba724p4982788e3a968b26@mail.gmail.com> <Pine.BSM.4.64L.0912171343380.21089@herc.mirbsd.org> <20091221223728.GA22598@thorin> <20091230203911.GT5695@hall.aurel32.net> <20091231141237.GA24833@thorin> <20091231142006.GG11637@hall.aurel32.net> <Pine.BSM.4.64L.0912311445480.8418@herc.mirbsd.org> <20100101013020.GA21541@thorin>
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.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
Reply to: