Red Hat Bugzilla – Bug 374201
anaconda fails to start installation
Last modified: 2008-01-03 19:32:22 EST
Description of problem:
anaconda raises a python exception during display configuration
Version-Release number of selected component (if applicable):
Run installation on PS3
Steps to Reproduce:
1. Enter F8 installation on PS3
Anaconda starts, then stops with a python traceback
(around rhpxl/videocard.py, line 149, in __init__
elif os.uname().count("ppc") > 0 and card.pcidom > 0:
AttributeError: device instance has no attribute 'pcidom'
installation to proceed normally
(I tried installing in text-only mode but couldn't figure out how.)
/me looks suspiciously at
AFAICT both hunks of that are broken -- the first because of the trace observed,
and the second because it'll change the fallback case on PowerPC machines to
'vesa' instead of fbdev.
Hm, I think it's even more broken than it seems at first glance. The assumption
that devices in domains > 0 will be mapped above 4GiB is completely bogus in the
first place -- we support machines where that isn't the case, on which X works fine.
If you want to avoid using 'real' X drivers on cards where the resources are
mapped above 4GiB, then perhaps the best way to achieve that is to try checking
where the resources are mapped, rather than making up broken heuristics?
Besides -- if X maps the resources correctly through sysfs, why does it care
about the physical address of them anyway?
For the record: I have reverted the above change, and dropped the modified
module into a RHupdates directory. With this, I was able to get F8 installed on
Thanks a lot for the quick help !
*** This bug has been marked as a duplicate of 370761 ***
*** Bug 381541 has been marked as a duplicate of this bug. ***
Any chance of getting this fixed, please?
*** Bug 389301 has been marked as a duplicate of this bug. ***