1) changes more modes to show gnome login screen than radeonhd
2) dri crashed(due to not using latest mesa & dri), but it crashed the
X server as well
3) glxgears ~650, entirely using the CPU alone
4) was unable to change resolution via gui (GNOME) ?
can anyone find anything interesting in the logs(logverbose 7) ?
-JoJo
PS: xorg.log is uploaded to pastebin
---------------- Xorg.log --------------------
also uploaded to
http://pastebin.com/f2cec15a1
---------------- Xorg.log --------------------
Hi Michel
I did ;-), earlier
but mailing list message size limit (40KB) was reached (~150KB) :-<
and message awaiting moderator approval bounce message.
so removed the entire long xorg.log & put a link instead.
(since I am not pointing a specific line in the log, I cant cut it short)
-JoJo
Hi Alex
Well, we still want to test & report the DRI status to you guys anyways.
The framebuffer in bios ?, if that means RAM allocated to IGP(GART size?),
it was explicitly set to 256 MB for the above logs.
And the delay before showing gdm login screen is due to -ati trying
various settings?
but radeonHD takes less time to come up.
OK so resolution change gui is not -ati driver's fault, gnome has to fix it.
(we will use xrandr or xorg.conf in the meanwhile for testing)
the package builders face no problems with building modular drivers(very good),
but are at a loss with mesa & DRI/DRM, hopefully you will help advice/address
the situation when you have some freetime.
there is some inconsistency in naming -ati (drivers) & radeon (in bugzilla)
(will that change?). Also some inconsistency in x.org git (via gitweb) which
i reported on X.org ML. Which page should we refer to in x.org wiki
for -ati drivers?
ciao
-JoJo
----- Original Message Follows -----
Thanks
----- Original Message Follows -----
>
Regards,
Maciej Cencora
He...He please forward your findings to radeon mailinglists.
(remember to file bug report for fglrx uninstall)
-JoJo