I'm attempting to test Fedora 7 Test 2 on a HP Compaq nw8440 and the install is
unable to load the vesa (or any other) drivers to do a graphical install. Its
also unable to load any drivers for firstboot causing it to fail.
I'm sure the ATI drivers would work once they are fixed but that still leaves
the problem of graphical installs, and firstboot. Besides the fact that untill
the ATI drivers are fixed there isn't any graphical solution for this card.
Running lspci on the nw8440 shows the following video card.
01:00.0 VGA compatible controller: ATI Technologies Inc M56P [Radeon Mobility X1600]
The vesa drivers did work for FC6, RHEL 5b2, and F7t1, but do not work on the
latest packages from rawhide.
Why does the vesa driver fail? Can you attach /var/log/Xorg.0.log from a failed
Created attachment 149503 [details]
Created attachment 149504 [details]
Xorg log from system-config-display
Created attachment 149505 [details]
temporary X config used by system-config-display
The driver fails during install when anaconda attempts to go graphical, and also
fails to start when I attempt to use system-config-display.
All of these work fine for FC6 on the same machine. I've attached the
anaconda.xlog and the files from system-config-display.
Could we get at least (when Rawhide Xorg didn't install properly)
/var/log/Xorg.0.log from FC6, to get all collected information about your
hardware, please? Thanks a lot.
Created attachment 149635 [details]
Created attachment 149638 [details]
anaconda.xlog from FC6
OK I uploaded the logs from the FC6 install I did today.
Let me make a ks.cfg for this FC6 install and then I'll try and do a rawhide
kickstart from scratch, rather than a F7t2 install. Probably sometime tomorrow.
Er, this _should_ be working with 1.3.0-4, it's just not the one that's in the
test2 install image. Does X work after install?
It didn't, after the install I did a full yum update and rebooted. Still
couldn't configure X.
Does it fail differently at least? Can you attach a log from 1.3.0-4? The one
in comment #2 doesn't appear to be from 1.3.0-4, and I'm almost certain I fixed
that failure case.
I still haven't had a chance to rekick the system. I can confirm that its also
broken in the just released RHEL-5 however. :-(
Created attachment 150280 [details]
Created attachment 150281 [details]
OK, I finally had a chance to install from the devel tree. I've atached the
anaconda logs. Let me know if you need anything else. X won't start at all so
I can't get a Xorg log for you. :-(
Does xorg-x11-drv-vesa 1.3.0-5 resolve this? It really should, there's a second
validation pass now that won't try to do strict intersection between EDID and
VBE mode lists.
I'm having trouble getting the latest rawhide to install at all on the box.
There seems to be something wrong with the ramdisk in the current rescue cds.
I have confirmed that the Fedora 7 Test 4 anaconda still fails. I assume that
it does include version 1.3.0-5 or higher of the vesa drivers?
I'm having the same issue with an x1300 Dell at the moment. Exactly the same
issue. FC6 I can install using graphical mode fc7 test versions I can't. Same
details during the install it switches to the vesa drivers and goes in text
mode. Then after the install I can't load X even with vesa put in the xorg line.
Maybe related bug is bug 240591 (crash which looks like in xfs, which is
strange; but hardware and distro are same).
*** Bug 240591 has been marked as a duplicate of this bug. ***
Not sure if this helps. Gentoo 2007.0 Livecd has the same issues as does Ubuntu
Bug reports here
I'm hoping this can get fixed before fc7 goes public but I'm having my doubts :(
I'm changing the product version over to F7 since this bug maid it to the GA
version of F7
The gnome Live-cd loaded my x1300 fine. Am I the only one that this is fixed for?
Marc, Russell -- could you give me both output of
rpm -q xorg-x11-drv-ati
[root@Strikelap log]# rpm -q xorg-x11-drv-ati
(In reply to comment #27)
> [root@Strikelap log]# rpm -q xorg-x11-drv-ati
Thanks for jumping on that for me Marc. That is the same version I'm seeing the
This seems to be fixed with the latest round of updates. Now I just need to
figure out how to make a new iso so anaconda will work as well.
This is a vesa bug, not a radeon bug. And I expect it's fixed by
*** This bug has been marked as a duplicate of 241491 ***