F17 self-built boot.iso queries

Amit Saha amitksaha at fedoraproject.org
Tue May 8 02:16:41 UTC 2012


On Mon, May 7, 2012 at 8:27 PM, Tim Flink <tflink at redhat.com> wrote:
> On Mon, 7 May 2012 20:09:53 +0530
> Amit Saha <amitksaha at fedoraproject.org> wrote:
>
>> Hello all:
>>
>> I built a boot.iso with 'lorax' using Fedora 17 release,version using
>> the default templates:
>>
>> $ sudo lorax --buildarch=i386 -p fedora -v 17 -r 17 -s
>> http://mirror.optus.net/fedora/linux/development/17/i386/os/ lorax_op
>>
>> I faced a couple of issues:
>>
>> 1. When i boot it using qemu/VirualBox, after selecting the install
>> option, the process stops with a white screen. Any reason for this?
>
> Do you have any logs for the install? That doesn't ring any bells
> regarding bugs that we've seen thus far but I'm also not sure that
> we've done any spins with just F17 stable, either.

No, unfortunately I didn't see anything other than the white screen.
(However, I am afraid something is wrong at my end; and I don't have
access to sufficient bandwidth to be able to try out the spins). I
shall see if I can have something more on this.

>
>> 2. When I boot it on bare metal after burning to a USB stick, the
>> installer goes to the storage device selection stage. I already have
>> a Fedora 17 installation on disk, which the new installation isn't
>> very happy with and complains that it cannot proceed with the
>> installation. Is this expected?
>
> It's likely that the packages on the boot.iso are older than your base
> system if you've been keeping it up to date with updates-testing. I'm
> not 100% clear on how upgrades work on the same base version but that
> could be part of the problem (assuming that F17->F17 'upgrades' are
> supposed to work and I'm not sure that they are).

Before building my boot.iso, I had done a 'yum update' with my
updates-testing enabled, yes. More details in the reply to Adam's
question.

Thanks!
-Amit

-- 
http://echorand.me


More information about the test mailing list