On 2/1/2013 12:35 PM, Robert Knight wrote:
On 01/30/2013 05:06 AM, Robert Knight wrote:
I'm still stuck at the install finishes but produces an un-IPLable
disk image. I see in the bug quoted above (and the repair in that
bug's referenced bug) that this has been trouble.
I can hack out the crash in the iutil.py code that blows up anaconda,
but the chreipl is not working. It looks from the logs like it
thinks it has installed the "boot loader", although the disk still
won't boot.
Sorry that Dan's bug reference became unattributed. It was
On 1/30/2013 2:32 AM, Dan HorĂ¡k wrote:
>> the "reipl" step blocks other steps including setting up the network
in
>> the installed image, see
>>
https://bugzilla.redhat.com/show_bug.cgi?id=858996
>> IIRC the workaround is to copy the ifcfg-ctc0 file from /tmp
>> to /mnt/sysimage/etc/sysconfig/network-scripts and also setting the
>> root's password is needed after "chroot /mnt/sysimage"
Making
those two changes allowed me to install successfully on an LVM.
One of my sources of confusion was that, unlike the Fedora 14
installation, the F18 installation quits writing to the main console
once the CTC has started.
I'm still having trouble with the standard partition -- just after IPL,
it goes into a tight loop.
I was successful in doing a "yum update", but the new kernel shows the
same symptom -- IPLing into it goes into a tight loop at the same
addresses. It makes me think that ZIPL needs something I'm not providing.
Should I be taking some other action following the new kernel
installation that is not done by the yum update?