[F7] Bluescreen for ATI notebook users?

[Florian Sievert]

Hi,

in fact I am wondering that nobody else was writting here about getting
a blue screen when having a ATI chipset in his notebook. I am using here
a IBM Thinkpad Z61M with an ATI Radeon Mobility X1400 and at that moment
anaconda should start the system boots into a blue screen. After this
point the text console is also messed up. I guess that this is a problem
with the chip and the tft screen and could effect several other people
using an ati card on an notebook.

So it looks like the problem is related to a bug reported end of april
and it's dup:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=238298 (dup)
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=235066 (might related)

I tried several boot options so far (nofb, resolution etc), but the
system stays completly unusable. I was able to perform an installation
via vnc and after installation the problem remains, however I was able
to logon via ssh getting access to the Xorg.0.log:

[root at deimos ~]# cat /var/log/Xorg.0.log | grep EE
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(II) Loading extension MIT-SCREEN-SAVER
(EE) AIGLX: Screen 0 is not DRI capable
[root at deimos ~]# cat /var/log/Xorg.0.log | grep WW
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(WW) No monitor specified for screen "Screen0".
(WW) No FontPath specified.  Using compiled-in default.
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(WW) VESA(0): No valid modes left.  Trying less strict filter...
(WW) <default pointer>: No Device specified, looking for one...

Anybody with an idea how to work arround this problem, especially using
a boot option in order to make F7 avaible for users that don't have a
second pc. Or will the be forced to use text console? Anybody else who
can confirm this problem?

Best regards,
Florian