I'm delighted to report that my instance of this bug was fixed by the
latest released of the Catalyst drivers (10.7). I've tested this along
with kernel 2.6.32-24 and Xserver 2:1.7.6-2ubuntu7.3 (all 32 bit).
Compiz and GL in general work fine.
Many thanks to the fglrx team for the fix
Manuel
--
Thanks for the hint Felix,
as you suggested I downloaded the latest Catalyst, installed the
generated packages (rel 8.741 in my case) and run aticonfig.
Unfortunately it failed with the same behaviour as before. Is there any
way to put the driver in any sort of 'verbose mode' so I can gather more
I noticed you're using an nVidia MCP51 chipset. I've seen other reports
of our driver hanging systems with that chipset.
--
fglrx fails to identify attached monitor, displays blank screen
https://bugs.launchpad.net/bugs/560570
You received this bug notification because you are a member of Ubuntu
Indeed, I'm using a socket AM2 motherboard equipping the nForce 430
chipset (aka MCP51); to be more precise it is an Asus model A8MN-BR,
marketed as Hematite-GL8E by HP. I presume Chris from post #13 has the
same model.
I'll check for other reports with this particular gpu/chipset combo to
see
After some digging, I've found ticket filed for this same issue in ATI's
bugzilla:
http://ati.cchtml.com/show_bug.cgi?id=1794
what I gathered from other thread references in the ticket is that the
issues with MCP51 follow a regression in Catalyst 9.9
** Bug watch added: ATi Linux Platform Bugs
Have you tried it with the latest Catalyst driver (Catalyst 10.6, driver
release 8.743)?
To update using generated Ubuntu packages, download Catalyst into an
empty directory and run
ati-driver-installer...run --buildpkg
dpkg --install *.deb
aticonfig --initial -f
and reboot.
--
Just to report that the behaviour experienced after updating flgrx to
the latest version (2:8.723.0ubuntu4) is identical (brief flash in
Plymouth, then Xorg hangs with 100% CPU load on boot). The outputs for
all logs all the same (nothing meaningful, AFAIU).
I reiterate my offer to the developers
Hi,
I have what looks to be exactly the same problem with 10.04 and an
Saphire 5450 (512 DD3 model) as Manuel. The card is working fine under
Windoze. Maybe just a coincidence but I also have an HP Pavilion with a
Hermatite motherboard. May not be so surprising as I think many opt to
put these
looking at the XorgLog it looks similar to the one in the bug I raised
for my card https://bugs.launchpad.net/ubuntu/+source/fglrx-
installer/+bug/566239. I am having this issue since catalyst 9.9 so it
looks like some change was made since 9.9 which causes the error however
I reported this to
Thanks Gary, I'm afraid my problem doesn't have to do with multiple
monitors as I only have 1 attached. I will try to get hold of a second
one to test whether this is due to the monitor not being supported, but
from the way it hangs X I doubt so (otherwise it should bail out with
no screens found
As by my previous post, I don't think this is a duplicate of Bug#552644,
since the latest update didn't fix it. It may be related, though.
** Description changed:
After installing fglrx 2:8.721.0ubuntu10 on Lucid Lynx beta 1 and
running 'aticonfig --initial', X (1.7.5) only displays a blank
If your card drives multiple monitors, I recall my HD5970 card at least
ID'd my monitor correctly when I switched them. It didn't seem to make
sense to me, but it might be worth a try.
--
fglrx fails to identify attached monitor, displays blank screen
https://bugs.launchpad.net/bugs/560570
You
*** This bug is a duplicate of bug 552644 ***
https://bugs.launchpad.net/bugs/552644
I'm afraid I wasn't as lucky as Nick and 2:8.723-0ubuntu1 didn't fix my
problem. The only difference I could notice is that there is a slight
flash of the screen when it hangs on the splash screen, while the
It would be helpful to see an Xorg.0.log file with fglrx active. Both
XorgLog.txt and XorgLogOld.txt attached to this bug are with RADEON
active.
--
fglrx fails to identify attached monitor, displays blank screen
https://bugs.launchpad.net/bugs/560570
You received this bug notification because
Hello Felix,
I'm enclosing the correct version of the log files, along with the
xorg.conf file generated by aticonfig. There is a slight change of
behaviour since updating gdm; now rather than stalling on a blank
screen, X now stalls on the ubuntu 10.04 splash (screen white lettering
on top of
The log file just stops half way through the driver initialization.
There's no backtrace. There are two possibilities:
1. the Xserver is still spinning at 100% CPU load in the background
2. the system crashed hard and didn't have a chance to write the complete log
file to the disk
You could try
*** This bug is a duplicate of bug 552644 ***
https://bugs.launchpad.net/bugs/552644
** This bug has been marked a duplicate of bug 552644
Lucid Lynx 64 bit nightly build hangs on boot
--
fglrx fails to identify attached monitor, displays blank screen
*** This bug is a duplicate of bug 552644 ***
https://bugs.launchpad.net/bugs/552644
I think this is a duplicate of Bug#552644.
I'm having similar symptoms to both. System appears to hang at end of
splash screen, but is actually running, just broken video. Cannot get
to other terminals via
*** This bug is a duplicate of bug 552644 ***
https://bugs.launchpad.net/bugs/552644
Yes, it appears to be working. I'm always amazed at the speed of fixes
in Ubuntu!
--
fglrx fails to identify attached monitor, displays blank screen
https://bugs.launchpad.net/bugs/560570
You received this
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/43764367/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/43764368/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/43764370/Dependencies.txt
**
I should mention that aticonfig --initial does not work at all for me,
since the file /etc/ati/control does not appear to be installed (I have
tried to remove and reinstall the package several times).
--
fglrx fails to identify attached monitor, displays blank screen
21 matches
Mail list logo
