Red Hat Bugzilla – Bug 160573
FC4 does not install to PPC LPAR: --virtpconsole: unknown option
Last modified: 2007-11-30 17:11:07 EST
Description of problem: FC4 is not installable to IBM PPC logical partitions. How reproducible: Steps to Reproduce: 1. Attempt to install to IBM PPC LPAR Actual results: Running anaconda, the Fedora Core system installer - please wait... Error bad argument --virtpconsole: unknown option :install exited abnormally sending termination signals...done sending kill signals...done disabling swap... unmounting filesystems... /mnt/runtime done disabling /dev/loop0 /proc done /dev/pts done /sys done /tmp/ramfs done /mnt/source done /selinux done you may safely reboot your system Expected results: Installation to proceed normally Additional info: I've tried a handful of install kernel options, to no avail, including: console=hvc0 vnc askmethod
Same story with IBM JS-20 BladeCenter
Created attachment 115546 [details] Fixed anaconda Typo - fixed on fc4 branch. I can give instructions for an updates.img/RHupdates - what type of install are you doing (nfs, nfs + iso, http, CD?)
I'll be very appreciative, if you can give me simple instructions on how to do this. I'm planing to use nfs + iso kind of installation. And thanks in advance for fast responce.
I would like: 1) install entirely from CDs 2) boot from disc 1, point to NFS
How to create updates.img: https://www.redhat.com/archives/anaconda-devel-list/2003-September/msg00093.html mount then cp the file onto the disk into a flat dir structure. For nfs iso: 'updates.img' file in 'Fedora/base' directory For nfs exploded tree: Create a dir called RHupdates parallel to Fedora (top level dir). and drop the anaconda replacement file there. Best of luck
Thanks! That helped to fix this problem. But a new one occured: Anaconda shows following graffiti: +----------------+ Error +-----------------+ | | | Error opening /tmp/sda: No medium found | | | | +-------+ +--------+ | | | Retry | | Cancel | | | +-------+ +--------+ | | | | | +------------------------------------------+ And after a few cancels we end up with this: +------------+ No Drives Found +-------------+ | | | An error has occurred - no valid devices | | were found on which to create new file | | systems. Please check your hardware for | | the cause of this problem. | | | | +----+ | | | OK | | | +----+ | | | | | +--------------------------------------------+
*** Bug 161206 has been marked as a duplicate of this bug. ***
this error also occurs for systems without LPAR enabled but have their console set to the serial port.
Due to the code paths in anaconda this bug (really just a typo) will affect all non mac ppc hardware, please confirm if using an updates.img/RHupdates fixes it for you.
Created attachment 116662 [details] python problem using new anaconda on power5 with VIOserver disks: sda=20GB and sdb=146GB (whole real disk allocated from server), using CD1 to boot, I can access patched nfs install sources. When installation starts, I hit attached python problem during disk format part of install. > File "/mnt/source/RHupdates/anaconda", line 1160, in ? intf.run(id, dispatch) ... that anaconda file is a copy of the patch Paul posted. Is this a new bug, or something needing correction in the existing patch?
Mark in future can you attach logs as plain ascii text rather than rtf. This looks to be a seperate issue - what partitioning scheme were you using? Is this reproducible?
Hi Paul, yes will make future attaches txt. Was using all defaults, so "autopartition". I've not tried recreating it. Didn't know if you'd want some info from python or another tool before rebooting. It's still at the python prompt. So please assist me with some suggested debugging steps (ctrl-z, command line prompt, go get contents of some log, etc) (or email me offline). I will open a new bug for this different problem. Thanks.
I'm having this same bug on an IBM JS20 blade. I want to do an FC4 install from CD, and anaconda bombs every time. I'm confused as to what the solution to this bug is...I take it I need to fix the anaconda that's on the FC4 install CD and reburn the disc. Can someone elaborate on this for me?
Hi folks, I can agree. It does not work on a JS20. The "updates.img" workaround runs fine. But the " Error opening /tmp/sda: No medium found" issue is still available. I have already seen this error when installing a RHEL4 via SOL or serial console and I "fixed" it with installing via VNC. But this does not work with Fedora. Can anybody give some informations how to sail round this issue? Thanks, Torsten
Has someone resolved this problems of FC4 in a complete and satisfactory way? Thanks, Alessandro
There is an unofficial updated fedora ppc tree here: ftp://zeniv.uk.linux.org/pub/people/dwmw2/fc4-pegasos