AMD 8.42.3 Driver Released -- The Baby Is Born! [Archive] - Page 5

Kiri

10-25-2007, 08:46 AM

Can someone know why i have this problem?

I have this problem:

jesus@tux-CT:~$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI RADEON 9600 Series
OpenGL version string: 2.0.6958 Release

jesus@tux-CT:~$ glxinfo |grep direct
direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose)
OpenGL renderer string: Mesa GLX Indirect

xorg.conf

# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf(5) manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "Files"
FontPath "/usr/share/fonts/X11/misc"
FontPath "/usr/share/fonts/X11/cyrillic"
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
FontPath "/usr/share/fonts/X11/Type1"
FontPath "/usr/share/fonts/X11/100dpi"
FontPath "/usr/share/fonts/X11/75dpi"
# path to defoma fonts
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection

Section "Module"
Load "bitmap"
Load "dbe"
Load "ddc"
Load "dri"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "vbe"
Load "v4l
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "es"
Option "XkbOptions" "lv3:ralt_switch"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection

Section "Device"
Identifier "ATI Technologies Inc RV350 AQ [Radeon 9600]"
Driver "fglrx"
BusID "PCI:1:0:0"
Option "VideoOverlay" "on"
Option "OpenGLOverlay" "off"
Option "XaaNoOffscreenPixmaps"
Option "UseFastTLS" "2"
Option "BusType" "AGP"
Option "PseudoColorVisuals" "off"
Option "TexturedVideo" "true"
Option "UseInternalAGPGART" "no"
Option "mtrr" "off"
Option "no_accel" "no"
Option "no_dri" "no"
Option "EnablePrivateBackZ" "no"
EndSection

#Section "ServerFlags"
# Option "AIGLX" "off"
#EndSection

#Section "Extensions"
# Option "Composite" "Disable"
#EndSection

Section "Monitor"
Identifier "SyncMaster"
Option "DPMS"
HorizSync 30-70
VertRefresh 50-160
EndSection

Section "Screen"
Identifier "Default Screen"
Device "ATI Technologies Inc RV350 AQ [Radeon 9600]"
Monitor "SyncMaster"
DefaultDepth 24
SubSection "Display"
Depth 1
Modes "1280x1024" "1152x864" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "1280x1024" "1152x864" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "1280x1024" "1152x864" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 15
Modes "1280x1024" "1152x864" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1280x1024" "1152x864" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1280x1024" "1152x864" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
EndSection

Section "DRI"
Mode 0666
EndSection

And Xorg.log.0 (http://webs.ono.com/jesusvpct/Xorg.log.0)

Did you make sure to uninstall the xgl server? In gutsy after you install it the package starts automatically with gnome.

Berniyh

10-25-2007, 08:50 AM

I don't think I've seen this. Post the image to like www.imageshack.us and then post a link here.

http://img263.imageshack.us/img263/6493/garbagepu8.th.png (http://img263.imageshack.us/my.php?image=garbagepu8.png)

I've got a feeling, that this might be related to HW Cursor, because sometimes (when switching windows) something similar is around the cursor, but goes away after switching windows again.

Sorry for the bad quality, I've only got a mobile phone and on screenshot this doesn't appear.

Normally after a restart of the X Server it is gone, but it'll come back after a while (or if I'm lucky it stays away for a session).

Michael

10-25-2007, 08:52 AM

http://img263.imageshack.us/img263/6493/garbagepu8.th.png (http://img263.imageshack.us/my.php?image=garbagepu8.png)

I've got a feeling, that this might be related to HW Cursor, because sometimes (when switching windows) something similar is around the cursor, but goes away after switching windows again.

Sorry for the bad quality, I've only got a mobile phone and on screenshot this doesn't appear.

Normally after a restart of the X Server it is gone, but it'll come back after a while (or if I'm lucky it stays away for a session).

Okay, that's some corruption. With Fedora I had experienced that but only with the watermark, but on Ubuntu even with the watermark I don't experience that. I know AMD is aware of it.

Berniyh

10-25-2007, 08:56 AM

Okay, that's some corruption. With Fedora I had experienced that but only with the watermark, but on Ubuntu even with the watermark I don't experience that. I know AMD is aware of it.
Ok, good to know.
What really bothers me is, that I know that I have to wait for a month till this get fixed, although it looks like a minor problem (maybe it isn't).

They really should start releasing bugfix releases. ;)
It's really sad, because apart from that the driver (for me) is better in every way (Even switching to console works now sometimes and doesn't always result in a hang.).

hobbes

10-25-2007, 09:29 AM

This is to someone who could possibly share some light about it: (Michael?)

It's getting closer to 48 hours since the 8.42.3 came out unofficially, this could means ATI/AMD is trying to at least fix some packages install problems, like the one is happening with Ubuntu 7.10 64bits?

Anyone?

Cerebral

10-25-2007, 09:32 AM

Okay, that's some corruption. With Fedora I had experienced that but only with the watermark, but on Ubuntu even with the watermark I don't experience that. I know AMD is aware of it.
Exactly the same corruption I saw on my 9600XT in 8.41 and now 8.42 - this is realistically the only thing holding me back from using 8.42 - I can tolerate glibc double-free errors when GL applications close, and so long as I have RENDER and Composite firmly _disabled_ in xorg.conf performance seems fine.

Glad someone got a shot of it - I couldn't get a screenie.

Trek1701

10-25-2007, 09:41 AM

Try disabling OpenGLOverlay in xorg.conf.

Hi,

Already disabled.

:confused:

################################################## ##
# Xorg configuration created by Trek1701 - MONITOR #
################################################## ##

# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the /etc/X11/xorg.conf manual page.
# (Type "man /etc/X11/xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "Files"
FontPath "/usr/share/fonts/X11/misc"
FontPath "/usr/X11R6/lib/X11/fonts/misc"
FontPath "/usr/share/fonts/X11/cyrillic"
FontPath "/usr/X11R6/lib/X11/fonts/cyrillic"
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
FontPath "/usr/share/fonts/X11/Type1"
FontPath "/usr/X11R6/lib/X11/fonts/Type1"
FontPath "/usr/share/fonts/X11/100dpi"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi"
FontPath "/usr/share/fonts/X11/75dpi"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi"
# path to defoma fonts
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection

Section "Module"
Load "i2c"
Load "bitmap"
Load "ddc"
Load "dri"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "vbe"
Load "dbe" # Double buffer extension
Load "fbdevhw"
Load "record"
Load "type1"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "abnt2"
Option "XkbLayout" "br"
Option "XkbVariant" "abnt2"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "Emulate3Buttons" "true"
EndSection

Section "Device"
Identifier "ATI Technologies Inc RV350 AS [Radeon 9550]"
Driver "fglrx"
Option "OpenGLOverlay" "off"
Option "XAANoOffscreenPixmaps" "true"
Option "FSAAEnable" "off"
BusID "PCI:1:0:0"
EndSection

Section "Monitor"
Identifier "SyncMaster"
VendorName "Samsung"
ModelName "Samsung SyncMaster 753DF(X)/703DF(X)/783DF(X)/CD173A(T)"
DisplaySize 320 240
HorizSync 30.0 - 71.0
VertRefresh 50.0 - 160.0
Option "DPMS"
EndSection

Section "Screen"
Identifier "Default Screen"
Device "ATI Technologies Inc RV350 AS [Radeon 9550]"
Monitor "SyncMaster"
DefaultDepth 24
SubSection "Display"
Depth 1
Modes "1280x1024" "1024x768" "832x624" "800x600" "720x400" "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "1280x1024" "1024x768" "832x624" "800x600" "720x400" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "1280x1024" "1024x768" "832x624" "800x600" "720x400" "640x480"
EndSubSection
SubSection "Display"
Depth 15
Modes "1280x1024" "1024x768" "832x624" "800x600" "720x400" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1280x1024" "1024x768" "832x624" "800x600" "720x400" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1280x1024" "1024x768" "832x624" "800x600" "720x400" "640x480"
EndSubSection
EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
EndSection

Section "DRI"
Mode 0666
EndSection

Section "Extensions"
Option "Composite" "Enable"
EndSection

Svartalf

10-25-2007, 09:47 AM

I can tolerate glibc double-free errors when GL applications close

Oh...my...LORD...

That's just...BAD.

I guess I need to break down and set up something and see this train wreck for myself, then.

Cerebral

10-25-2007, 09:49 AM

Oh...my...LORD...

That's just...BAD.

I guess I need to break down and set up something and see this train wreck for myself, then.
Well, it only really happens when Dual-Head is turned on, but yeah, it's kind of crazy that would get into the release.

FunkyRider

10-25-2007, 09:54 AM

Guess what, all those bugs completely broke Linux as being "Stable". When you are doing your work and suddenly being kicked out of X, you will be pissed off.......

jeffjoker

10-25-2007, 10:09 AM

Sorry to bother again but I have posted my config on page 38 and no answer yet ? :(
Please help ! :confused:

JCTWeb

10-25-2007, 10:16 AM

Sorry to bother again but I have posted my config on page 38 and no answer yet ? :(
Please help ! :confused:

What's the problem? Your post says that fglrxinfo is showing you're running the ATI driver successfully...did I miss a different post stating the issue?

carpman

10-25-2007, 10:21 AM

I was seeing that too, but it went away when I enabled compiz.

http://img263.imageshack.us/img263/6493/garbagepu8.th.png (http://img263.imageshack.us/my.php?image=garbagepu8.png)

I've got a feeling, that this might be related to HW Cursor, because sometimes (when switching windows) something similar is around the cursor, but goes away after switching windows again.

Sorry for the bad quality, I've only got a mobile phone and on screenshot this doesn't appear.

Normally after a restart of the X Server it is gone, but it'll come back after a while (or if I'm lucky it stays away for a session).

DanL

10-25-2007, 10:27 AM

Sorry to bother again but I have posted my config on page 38 and no answer yet ? :(
Please help ! :confused:

jeffjoker,
Sorry about the non-responsiveness. There's a lot of people reporting problems and posting xorg.conf's. I can PM you my xorg.conf if you'd like, as I have desktop effects working. Before we do that, you should try adding:

Section "ServerFlags"
Option "AIGLX" "on"
EndSection

oliver

10-25-2007, 10:27 AM

are you using compiz or not, if you are then try disableing it to run games, that may do the trick, the other thing may the problems with AGP and the drivers (but i thought they had resolved that with these drivers, or it may of been the open source version) all in all just try disabling compiz, u really shouldn't be having these problems though.

bullant

I don't have compiz installed/enabled, AIGLX is set to false in xorg.conf and i added composite disabled now. There may have been a slight chance that the rmmod fglrx, install ati-drivers, modprobe fglrx needed a reboot, but that would be silly :p

A new day, more chances. So i'm gonna play/test some more with it. AIGLX was disabled btw from the log, and composite wasn't anywhere mentioned in the log. So i'm guessing it should be disabled by default.

For the guy mentioning the tearing on iceweasel; i had something similar, and turned out to be agp memory that was set to small. Try changing that in your bios, Dunno about pci-express but they may still use a similar option to map memory.

Edit: Ok tried it, same results. I played a little longer with these drivers, and i can deffinatly say except for some framerate spikes, overal performance was far worse then what I had with 8.42.3 go figure.
I also tried ut2003 and got the same corruptions mentioned earlier. (saw screenies) but don't ask me where it was exactly :p

So for me, it's back to 8.34 as those are the only old drivers that actually work for me.

*sigh* and everybody else is having a blast with super speedy nice drivers :(

jeffjoker

10-25-2007, 10:30 AM

What's the problem? Your post says that fglrxinfo is showing you're running the ATI driver successfully...did I miss a different post stating the issue?

Yes, I try to activate the desktop effects and I get an error message box saying that it failed.

jeffjoker

10-25-2007, 10:33 AM

jeffjoker,
Sorry about the non-responsiveness. There's a lot of people reporting problems and posting xorg.conf's. I can PM you my xorg.conf if you'd like, as I have desktop effects working. Before we do that, you should try adding:

Section "ServerFlags"
Option "AIGLX" "on"
EndSection

I know there are a lot of posts and a lot of questions, I was just refreshing mine ;)
Thanks for your answer, I ll try that ASAP.

carpman

10-25-2007, 10:48 AM

Fglrx might still be blacklisted in /usr/bin/compiz, look for a line that says whitelist and add fglrx to the list of drivers.

Yes, I try to activate the desktop effects and I get an error message box saying that it failed.

Berniyh

10-25-2007, 11:15 AM

I was seeing that too, but it went away when I enabled compiz.

I tried with enabled and disabled AIGLX/composite and I tried SW Cursor, nothing helped.

I don't really want to downgrade to 8.40.4 either, because I've got it now running with xorg-server-1.4 quite well and downgrading would result in a lot of package recompiling (to make sure it is running).

I'm a bit disappointed because I know, that I have to wait at least one month till this gets fixed. :(

givemesugarr

10-25-2007, 11:23 AM

Normally after a restart of the X Server it is gone, but it'll come back after a while (or if I'm lucky it stays away for a session).

try adding:
Option "HWCursor" "On" to the Device section of /etc/X11/xorg.conf. it should fix that issue.

new bench report for x200m:

it works with beryl-0.2.1, emerald-0.2.1, kde-3.5.8, xorg-7.2, kernel-2.6.22-r9 with about 650fps, which is 1/3 of best results without aiglx/beryl. i must say that this new driver is not bad at all, but still lacks some features and has some bugs, like the problem with this hw cursor. usually it gets out with firefox when right clicking and goes away with xorg restart. i now found out this hwcursor stuff and i will try it out to see what happens. the other problem is the xv compatibility. i cannot play some old files in xv, but only in opengl with bad textures all around, so this is not a great thing.
the only fact that i'm happy with is the performance gain (6 times 8.40) and it relative stability (it doesn't crash) and that finally i can use hibernate with it (i couldn't with old 8.40). the only tests that i still have to run are with xorg-7.3 and kernel-2.6.23 (i still have some issues with madwifi so until i fix these i won't actually try it).

Berniyh

10-25-2007, 11:26 AM

try adding:
Option "HWCursor" "On" to the Device section of /etc/X11/xorg.conf. it should fix that issue.
As I stated before I tried with HWCursor and SWCursor.

This is from my running session:
(==) fglrx(0): Using hardware cursor
It's there again...

So HW/SW Cursor isn't the solution.

Neo4

10-25-2007, 12:03 PM

As I stated before I tried with HWCursor and SWCursor.

This is from my running session:
(==) fglrx(0): Using hardware cursor
It's there again...

So HW/SW Cursor isn't the solution.

sometimes i have that problem too but around the mouse...
this new driver really sucks!

i guess the baby has born a litle retarded! lol :rolleyes:

Berniyh

10-25-2007, 12:10 PM

sometimes i have that problem too but around the mouse...
this new driver really sucks!

i guess the baby has born a litle retarded! lol :rolleyes:
Just move to a border or a input box (where the cursor changes) and it will be gone.
But it still is a hateful problem.

Neo4

10-25-2007, 12:14 PM

yeah i know that but as you said is still a problem...

hluk

10-25-2007, 12:35 PM

jackkerouac

10-25-2007, 12:53 PM

Well, since 8.40.4 works fine for me and the only problems I have with 8.42.3 are its slowness and video flickering, I'm actually looking forward to the next few releases. Hopefully, they can fix the speed and the video problems soon and I can actually use AIGLX on a regular basis instead of XGL.

Uchikoma

10-25-2007, 01:07 PM

Well for those who are still having issues, check out my install process and maybe you'll notice something you missed or another.

http://phoronix.com/forums/showpost.php?p=16698&postcount=4

For those who have the driver up, but can't get compiz to load, make sure that

a) it's not mesa (glxinfo)
b) composite is enabled in your /etc/X11/xorg.conf

Berniyh

10-25-2007, 01:15 PM

For me screen corruptions disappeared after putting the lines below into xorg.conf's device section (where my current fglrx 8.42.3 driver was).

Option "OpenGLOverlay" "off"
Option "BlockSignalsOnLock" "on"
Option "KernelModuleParm" "locked-userpages=0"

ps: It's either all lines or one of them - so, good luck ;).
The first one I've got already, so that shouldn't be it.
(I'm using XV overlay for videos, so OpenGL is off.)

I'll try the other ones.

Edit: The second one alone isn't it either, I'm currently running third line alone,
let's see if that helps.

Svartalf

10-25-2007, 01:19 PM

Well, it only really happens when Dual-Head is turned on, but yeah, it's kind of crazy that would get into the release.

Memory issues of that nature are very, very bad and they should have been testing double-head as well as single. A double free like that on a production driver on something this simple (Any OpenGL app with double head on...) is a brown paper bag over the head moment for them.

givemesugarr

10-25-2007, 01:30 PM

Option "OpenGLOverlay" "off"
Option "BlockSignalsOnLock" "on"
Option "KernelModuleParm" "locked-userpages=0"

i've always had them but i still used to get that problem. now i'm curently trying that hwcursor with opengloverlay on and it seems to go on quite well. the problem is that i have problems running xv on xine or mplayer and some files turn to opengl, thus verrrrrrryyyyy sloooooooow... :(

Berniyh

10-25-2007, 01:34 PM

i've always had them but i still used to get that problem. now i'm curently trying that hwcursor with opengloverlay on and it seems to go on quite well. the problem is that i have problems running xv on xine or mplayer and some files turn to opengl, thus verrrrrrryyyyy sloooooooow... :(
If the OpenGLOverlay would be the problem that would be very odd, because it is only used for multimedia apps and I've not run any multimedia apps today so far.

givemesugarr

10-25-2007, 01:46 PM

If the OpenGLOverlay would be the problem that would be very odd, because it is only used for multimedia apps and I've not run any multimedia apps today so far.

i didn't say that that is the problem. i've only said that i'm using the opengloverlay set to on and the hwcursor to on and till now (3 hours and 47minutes i didn't have any sign of that annoying stuff). i've also been using firefox for the same time and still haven't had that issue. there's a great possibility that this is only some coincidence, but it still may be not. or it may be that i've just upgraded to firefox 2.0.0.8 from 2.0.0.6 (i've only had that issue after some right clicking in firefox not from other apps so it can also be some gtk+-kde or gtk+ bidings problem since firefox is a gtk+ app). i don't know yet if this is the solution. you can give it a try if you want and see what happens.

EnderWiggin

10-25-2007, 01:46 PM

I've been having some mixed success with the driver. It's been awhile since I ran XGL, but I am fairly certain that XGL was faster and smoother than the AIGLX implementation on this driver. I have had some luck with various tweaks to the driver options in xorg.conf, but I don't know all the available options to try. Does anyone know where to find ALL of the xorg.conf params that would affect this device. I want to see how much tuning I can to and to what help they would be.

I think this driver is exactly where most of us expected it to be. Moreover, it is about the level it should be at considering the maturity of this new code base from ATI. It did deliver on the AIGLX extensions and some other performance improvements as promised, but as with any new release of this size, there are integration bugs (some significant). Even the Linux kernel follows this release methodology, where some releases are marked as "stable" releases which have less new content and have been tested thoroughly. These are then maintained separately from the mainline until the next stable release with bug fixes back ported where necessary. I believe 2.6.20 was the last "stable" release, where 2.6.21-2.6.23 all delivered significant content updates (new scheduler, new allocator, tickless kernel, etc.) each with their host of associated bugs. So to that end, I think ATI did the right thing releasing the driver now. As with all "early adopters", it's up to us to find the pain points and pass that feedback back to ATI so that 8.43 will be better. Realistically, I doubt this new code base will be stable until 8.45 or 8.46.

If we want to hold ATI to a monthly release cycle, we have to expect some significant bumps in the road. If we want every release to be perfectly stable while also delivering new content, then we would have to accept longer release cycles that give ATI more time to test internally. I think that ATI's methodology is very in line with modern development practice. The only think they could add would be to mark some releases as stable and back port bug fixes, but that requires resources which are likely already committed to driver development. Hopefully in the future they will adopt this paradigm.

ATI's commitment to Linux seems genuine but their ability to test and develop drivers is always going to be limited to resource availability and funding. Whining or complaining that the driver isn't what you expected won't help with either and will only frustrate everyone else on the list.

givemesugarr

10-25-2007, 01:55 PM

Does anyone know where to find ALL of the xorg.conf params that would affect this device. I want to see how much tuning I can to and to what help they would be.

i'm also looking out for them. i recall to have seen some setting for igp boards that let the driver get a different ammount of vram (as in the windows catalyst where i can chose an amount from 1/2 to 2 times the original reported vram) and i'd be interested in finding it since i've seen that fglrx says that my aperture is limited to 256MB of vram, that is 2x the actual memory. if i can use more memory i should have a better experience, or at least i think so.
i've tried to set it to 256 on windows and it ran smoother and i could adjust a little better the video settings.

(**) fglrx(0): ATI GART size: 256 MB
(II) fglrx(0): [pcie] 258048 kB allocated with handle 0xdeadbeef
(II) fglrx(0): [drm] DRM buffer queue setup: nbufs = 100 bufsize = 65536

Cerebral

10-25-2007, 02:02 PM

Realistically, I doubt this new code base will be stable until 8.45 or 8.46.
In which case the driver should come with a note that it is unstable. The kernel guys tell us which are stable releases - why can't AMD? They did it well enough with 8.41. Actually, I'm also curious, like many in this thread, why there hasn't BEEN a direct announcement by AMD on their site yet.

If we want to hold ATI to a monthly release cycle, we have to expect some significant bumps in the road.AMD set that release cycle for themselves, and we have to suffer by expecting them to hold up their end of the bargain? If they want to devote more time to each release, then they should, and say that's what they're doing, plain and simple. We're not holding them to anything they haven't decided for themselves.

I think that ATI's methodology is very in line with modern development practice.Releasing code with clear memory issues (glibc double-free?) isn't very much in line with that.

ATI's commitment to Linux seems genuine but their ability to test and develop drivers is always going to be limited to resource availability and funding.
I find it hard to believe AMD would have trouble getting the resources - they make the cards, and likely test their windows drivers on them all. Funding I'd believe - they might not have the money in the budget to invest the man-hours, who knows?

Whining or complaining that the driver isn't what you expected won't help with either and will only frustrate everyone else on the list.
While I've been generally disagreeable in this reply, I do agree with this statement. However, I don't think it's wrong for people to expect no on-screen corruption, no memory errors, or a driver that at least works, even if performance sucks.

8.42 has on-screen corruption, glibc double-free stack traces spewing out, and for some people just doesn't plain work at all. I have to disable Composite or my computer locks up when I try to quit X with this version. That's why it's been disappointing, especially given the hype that's been generating around this release.

Regardless, and call me a hopeless hopeful if you will, I still have faith in 8.43.

Berniyh

10-25-2007, 02:03 PM

i didn't say that that is the problem. i've only said that i'm using the opengloverlay set to on and the hwcursor to on and till now (3 hours and 47minutes i didn't have any sign of that annoying stuff). i've also been using firefox for the same time and still haven't had that issue. there's a great possibility that this is only some coincidence, but it still may be not. or it may be that i've just upgraded to firefox 2.0.0.8 from 2.0.0.6 (i've only had that issue after some right clicking in firefox not from other apps so it can also be some gtk+-kde or gtk+ bidings problem since firefox is a gtk+ app). i don't know yet if this is the solution. you can give it a try if you want and see what happens.
No, it certainly isn't the solution.
HWCursor doesn't help for me, because that is standard (I'm always using HWCursor.).
Yesterday I also had a time of several hours, where this garbage didn't appear, so you can't really be sure unless it didn't appear for let's say 2 days or so.

BTW, this is not a problem of some software (KDE, Firefox or whatever).
This is a problem of the driver, because if you make a screenshot, it is not there.

Berniyh

10-25-2007, 02:09 PM

i'm also looking out for them. i recall to have seen some setting for igp boards that let the driver get a different ammount of vram (as in the windows catalyst where i can chose an amount from 1/2 to 2 times the original reported vram) and i'd be interested in finding it since i've seen that fglrx says that my aperture is limited to 256MB of vram, that is 2x the actual memory. if i can use more memory i should have a better experience, or at least i think so.
i've tried to set it to 256 on windows and it ran smoother and i could adjust a little better the video settings.

A lot of options can be found here:
http://debian.wgdd.de/temp/fglrx_man/fglrx.4x.html

Fenix-TX

10-25-2007, 02:37 PM

Did you make sure to uninstall the xgl server? In gutsy after you install it the package starts automatically with gnome.

Ohh!! I didn't know that!!! That waas the problem. Thanks!!!!

EDITED: Wow! This driver is very very great!

rapsure

10-25-2007, 09:33 PM

The bugs in the 8.42.3 driver are as follows for an ATI RADEON X800XL video card: No XV by default, unstable (computer locks up daily on the driver), Vesa console doesn't work and results in a black screen for the terminal. DVI output will cause the system to freeze. The driver does have features, but the R300 driver isn't very far off. My computer has been locking up daily with the fglrx 8.42.3 driver.

For the opensource Radeon driver there needs to be about five opengl extensions added to make the game ET:QW work. After that Render accel needs to implemented for a fast 2D desktop. Oh, and the opensource driver supports XV, and system stability, and isn't fussy with the Vesa console nor with the DVI output. For anything older than a Radeon X850 the radeon driver will work, and give decent performance, and the one thing I like a lot, stability.

Trek1701

10-25-2007, 10:28 PM

Hi again,

On my last two posts I spoke about the "white screen" problem. I get this with both compiz and beryl.

Looking At beryl, the default is "--use-tfp" (Pixmap Texture) then I've changed to "--use-copy" and the white screen problem vanished but the effects got really slow.

So, I'm having a problem in texture from pixmap. I really have no idea on what does it mean. :confused:

drystan1

10-25-2007, 11:38 PM

jeffjoker

10-26-2007, 01:20 AM

Thansk for the help.
I just needed to add fglrx to the white list of drivers ;)

But as many reported my compiz effects are slow, much slower than with the radaeon driver :mad:

I have not had time to test the 3D rendering yet.

Phlogiston

10-26-2007, 02:14 AM

What distro/kernel and ATI device are you using? I too concur that the SLUB problem is gone for my Mobility FireGL v5200, but I cannot get Xorg to run on resume no matter what I try. Text mode is fine, but kinda defeats the point....

I'm using gentoo with suspend2 patched kernel. Maybe you are missing a certain config line in xorg.conf. I will post it soon.

kimba

10-26-2007, 03:18 AM

Hi does anyone know if there is a workaround for the black screen bug in Gutsy yet. I built the drivers ok on a amd64 but on restart the x server crashes to a black screen ! Now this is reported in the bug tracker for Gutsy, has anyone managed to fix it ? any help would be very useful.

Cheers

Hi. I have the same problem on debian testing/lenny. I have a mobility 9700. The same thing appears with fglrx 8.40. I resolve installing fglrx 8.38

Sorry for my bad english...

Berniyh

10-26-2007, 04:12 AM

For me screen corruptions disappeared after putting the lines below into xorg.conf's device section (where my current fglrx 8.42.3 driver was).

Option "KernelModuleParm" "locked-userpages=0"

This seems to work for me.
I didn't have those screen corruptions since 7 or 8h running time.
Although to be sure it is solved, of course I have to see if it comes back the next days.

Just make sure, that the kernel module is unloaded before the x server starts again after you put that option in xorg.conf, or better: restart.

xeros

10-26-2007, 04:16 AM

Am I the only one who has the problem with X beeing killed with compiz start? - The same with 0.3.6, 0.5.2, 0.5.5 on Kubuntu 7.04 Feisty Fawn with Xorg 7.2. X server is killed just after emerald start and I don't have X logs because X server restarts with KDM login screen and logs are overwritten.

ffbadkill

10-26-2007, 04:47 AM

let's try the driver to see whether it works or not
i have waited AIGLX support for a long time

kimba

10-26-2007, 05:18 AM

Berniyh

10-26-2007, 07:45 AM

This seems to work for me.
I didn't have those screen corruptions since 7 or 8h running time.
Although to be sure it is solved, of course I have to see if it comes back the next days.

Just make sure, that the kernel module is unloaded before the x server starts again after you put that option in xorg.conf, or better: restart.
I knew it. ;)

Now the screen corruption came back, so that isn't the solution either, but it might help a little bit.

container

10-26-2007, 07:50 AM

For some reason, Compiz (the one in Feisty) performed miserably. Beryl is ok for me, too, though I only use it when I want to zoom in on Flash videos. But the new driver seems to perform well, and I haven't noticed any major bugs yet. Installation was a bit difficult in Feisty, as I'm not used to Ubuntu, having preferred Fedora since FC2.
Of course, the Firefox scrolling business seems to be an issue across the board. It's so unresponsive that I'll simply not use either Compiz or Beryl. The same goes for window resizing with wobble and pop-up window previews. That is, Beryl and the like seem to perform too badly with an x800xl, amd64 3000+ and 2 gb of RAM.
But in any case, this version of the driver seems to me to be a really good one. I haven't read all of this thread, but it looks like a lot of people have had trouble with installing it, and I suppose many have blamed ATI/AMD when it didn't work properly or at all.

heng

10-26-2007, 08:39 AM

I can confirm that the xv and gl video is watchable using xcompmgr over compiz. Its still buggy; it refuses to accept a transparency given by transset and if the background changes (e.g scrolling a web page behind the movie) then the video disappears (apparently replaced by the background) for a fraction of a second (much like the compiz choppyness). I wonder if the xv/gl stuff doesn't like compositing and compiz is more inclined to refresh background windows.

Phlogiston

10-26-2007, 09:01 AM

I'm using gentoo with suspend2 patched kernel. Maybe you are missing a certain config line in xorg.conf. I will post it soon.

Do you have these options?:
Option "UseInternalAGPGART" "no"
Option "KernelModuleParm" "agplock=0"

Cerebral

10-26-2007, 09:07 AM

Do you have these options?:
Option "UseInternalAGPGART" "no"
Isn't this option deprecated now? I thought they removed all support for internal AGPGart

morppheu

10-26-2007, 11:45 AM

Nice one.
I am installing it right now. :D

Thanks!

hluk

10-26-2007, 11:47 AM

I knew it. ;)

Now the screen corruption came back, so that isn't the solution either, but it might help a little bit.

The screen corruption is gone for me - either with AIGLX/composite or without (but opengl/sdl is very slow when AIGLX/composite is on). So, here's everything ok - except the switching-from-X-to-console-and-back ancient bug :-(. Alright, I'm posting the whole Device section, maybe it will help you get rid of the screen corruption.

Section "Device"
Identifier "ATI Radeon 9600"
Driver "fglrx"
VendorName "ATI Technologies Inc"
BusID "PCI:1:0:0"
Option "VideoOverlay" "on"
Option "OpenGLOverlay" "off"
Option "UseFastTLS" "2"
Option "KernelModuleParm" "locked-userpages=0"
Option "no_accel" "no"
Option "no_dri" "no"
Option "EnablePrivateBackZ" "no"
Option "backingstore" "true"
Option "XAANoOffscreenPixmaps" "true"
Option "ForceMonitors" "notv"
EndSection

Berniyh

10-26-2007, 12:28 PM

The screen corruption is gone for me
I hope you're spitting that not too fast out. My screen was clean for lets say 12 hours, but then it came back.
Actually if it takes that long it would be acceptable, but I really would like to see AMD releasing a bug fix for this before next driver release (I know that's not gonna happen...).

Another thing that they really should release a fix for before the next release (8.43) is the wrong SONAME issue of libGL.so which may hold off this driver of gentoo's portage.

See here:
http://ati.cchtml.com/show_bug.cgi?id=843

That shouldn't be a big issue and I guess it would be fixable by just releasing a fixed libGL.so, but of course that is not going to happen either. :(

givemesugarr

10-26-2007, 12:57 PM

Option "XAANoOffscreenPixmaps" "true"

this options seems to remove the screen corruption. after i've added it i have not experienced any corruption anymore.
the other thing is that you seem to have to force the xv with the videooverlay and disable the opengl overlay. after that i had to set beryl from texture from pixmaps to copy and my fps have not gone down anymore. now i'm stable at 700-800 fps with every environment which is quite good.

Another thing that they really should release a fix for before the next release (8.43) is the wrong SONAME issue of libGL.so which may hold off this driver of gentoo's portage.

just use the sabayon ebuild or modify the 8.40.4 one removing the gunzip line and by adding the libGL.so.{major} where there is the libGL symlinking in the ebuild.
for some reason the sabayon ebuild has removed the fgl_glxgears and some other things, but on my gentoo they work flawlessly. another important thing is to always run the atieventsd service at boot time. after i've had it added some time ago i was able to correct a lot of problems. i don't know what it really does but it seems to be of some kind of use.

Berniyh

10-26-2007, 01:14 PM

just use the sabayon ebuild or modify the 8.40.4 one removing the gunzip line and by adding the libGL.so.{major} where there is the libGL symlinking in the ebuild.
The sabayon ebuild is just wrong. I can't believe, that they actually put something like that in their tree.
Did they even test this? It spits out some errors during installation.
I'm mean, after an emerge, when you made (or modified an ebuild), you should just go through the install process at least once and see if it did everything correctly.
Sorry, but you just can't add some (proprietary) software one day after it has been released to your tree and with that they can't be taken serious by anybody again...
... or at least not by me.

The thing with the libGL.so is not that it has the wrong (file-)name. The thing, is that the SONAME of it is wrong, which brings the whole needing for the symlink in in first place.
See the gentoo bug about 8.42.3 for information.
https://bugs.gentoo.org/show_bug.cgi?id=196820

I'll try the other option and see if that helps, tomorrow.

givemesugarr

10-26-2007, 02:45 PM

Berniyh

10-26-2007, 04:28 PM

i don't really know if the sabayon ebuild works... i didn't tried it myself. i've patched manually the old 8.40.4 and installed from that one. for me it worked without problems. i had the driver installed about 1 hour after it was released and it works fine for now.
i could test the new ebuild, but since the old patched one works fine i don't really see a reason to change it. maybe when i got to try the 2.6.23 (not so fast since it seems for this driver to have problems with this kernel).
Then you sort of did what sabayon people did.
The thing is (and maybe this is also the reason you didn't expect any problems) that ATI changed the installer package and therefore on AMD64 systems two of the 32bit libs don't get installed (because their location has changed). Of course if you modify the ebuild yourself this is ok, because then you know that you may run into problems, but if the ebuild is provided by your distributor you think, that it will work.
With your current ebuild you might expect problems running 32bit apps, that use opengl, for example, if you run a game with wine.

as for the soname issue, i don't really think that this is a real problem since it is fixed with a simple symlink. of course that should be fixed in the next release and i think that ati would correct that feature by next month's release. for now just add the symlink part in the ebuild and you'll have it working.
Once again you can fix this of course locally very easy, but you can't write sth. like that in the ebuild, because the ebuild works as it should (it writes the libGL.so.1.2 to /usr/lib/opengl/ati/lib and then symlinks libGL.so.1 and libGL.so to it in that directory). Because there are seperate opengl impelementations (xorg-x11 and ati) you need a programm to select the right one and that is eselect, which sets the symlink to /usr/lib. The ebuild should not do that, so there is nothing from the side of the ebuild, that could be done.
The real problem is, that because of the wrong SONAME the wrong libname is included by env-update/ldconfig and that is the reason it doesn't find the lib.
So this is a problem that should be fixed by ati, not a dirty hack in the ebuild.

givemesugarr

10-26-2007, 05:03 PM

With your current ebuild you might expect problems running 32bit apps, that use opengl, for example, if you run a game with wine.

i didn't try that since i don't run games or wine apps. i'm quite ok with only linux and linux apps.

Then you sort of did what sabayon people did.

well, they seem to have removed a lot of stuff. some things related to the fgl_glxgears, some things from the /etc/ati/ dir, and some other stuff. i only removed what didn't compiled and fixed the symlinking (that there was also there before in the gentoo ebuild for some dirs).
about the distro thing: sabayon isn't the gentoo distributor. is an overlay and a sabayon distributor. so if you want a distributor for gentoo use the gentoo base repo. that's why i don't relay much on sbayon stuff. some things compile and work, some others do not. i personally like to use xeffects, gentoo and at last if none of the gentoo,xeffects compile and work the sabayon ebuilds.
as for the soname, i've said that i think ati would correct the issue in the next release, since now it's out. in the meantime, let's hack the ebuild and have the driver installed.... :D:D

Berniyh

10-26-2007, 05:40 PM

well, they seem to have removed a lot of stuff. some things related to the fgl_glxgears, some things from the /etc/ati/ dir, and some other stuff. i only removed what didn't compiled and fixed the symlinking (that there was also there before in the gentoo ebuild for some dirs).
Doesn't build up confidence either, because it just needs sandbox-2.18.1-r1 to make that compile.

about the distro thing: sabayon isn't the gentoo distributor. is an overlay and a sabayon distributor. so if you want a distributor for gentoo use the gentoo base repo. that's why i don't relay much on sbayon stuff.
I've never said that they are a gentoo distributor, but they call themselves a distribution and that means, that you test the stuff you push out.
But I stop mocking about them here... ;)

as for the soname, i've said that i think ati would correct the issue in the next release, since now it's out. in the meantime, let's hack the ebuild and have the driver installed.... :D:D
Gentoo people wouldn't do that. Of course in your local overlay you can do stuff like that, but in the official ebuild from gentoo I guess you won't see that.

What I tried to say is that ATI maybe should break their release cycle if trivial bugs are spotted that could be fixed by an updated package, or a extra file.
I know that they did that once, why not do this more often?

mintcoffee

10-26-2007, 06:45 PM

I'm using gentoo with suspend2 patched kernel. Maybe you are missing a certain config line in xorg.conf. I will post it soon.

I'm on Arch Linux too, and I can't get X to resume after I suspend as well. It freezes the entire system. I have a FireGL V5200 running Xorg 1.3.

willytax

10-26-2007, 06:49 PM

happycampers

10-26-2007, 07:38 PM

this options seems to remove the screen corruption. after i've added it i have not experienced any corruption anymore.
the other thing is that you seem to have to force the xv with the videooverlay and disable the opengl overlay. after that i had to set beryl from texture from pixmaps to copy and my fps have not gone down anymore. now i'm stable at 700-800 fps with every environment which is quite good.

I tried setting XAANoOffscreenPixmaps and I thought it was working - no corruption for 8 - 10 hours, then I came back to my system after the screen locked, and it was there, big as life. Oh, well. BTW, I'm not running dual-head at the moment and I still get the corruption. So far, it's only very occasional, but still... issues like this seem more like something you would expect in a Beta, or even Alpha release.

marshalle

10-26-2007, 08:44 PM

https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-8.42.3-x86.x86_64.run

Is anyone else getting screen tearing on ATI? It used to be mentioned in the release notes, now it seems to have dissappeared but still be unfixed.

Any replies appreciated.

givemesugarr

10-27-2007, 04:41 AM

I'm on Arch Linux too, and I can't get X to resume after I suspend as well. It freezes the entire system. I have a FireGL V5200 running Xorg 1.3.

get back to 8.40.4 since the 8.41.7 and 8.42.3 don't support firegl. or pass to the opensource ati drivers. they should work quite well for firegl boards.

I tried setting XAANoOffscreenPixmaps and I thought it was working - no corruption for 8 - 10 hours, then I came back to my system after the screen locked, and it was there, big as life. Oh, well. BTW, I'm not running dual-head at the moment and I still get the corruption. So far, it's only very occasional, but still... issues like this seem more like something you would expect in a Beta, or even Alpha release.

Hi, can you please tell me how did you get the xv video working?

unset the opengl overlay with Option "OpenGLOverlay" "off" and force xv with Option "VideoOverlay" "on". that should do the trick. you'll have some speed loss in terms of fps but you'll be able to run beryl,aiglx, and have no tearing. or at least that's what is happening to me.

Doesn't build up confidence either, because it just needs sandbox-2.18.1-r1 to make that compile

guess that me having -sandbox for the ati-drivers does compiles them. i've removed sandbox for ati when i tried to compile the 8.41.7. so now after removing it it seems to go well.
by the way, i've just got sandbox-2.18.1-r2 stable on amd64.

I've never said that they are a gentoo distributor, but they call themselves a distribution and that means, that you test the stuff you push out.
But I stop mocking about them here...
maybe they only test id it does install on their system (which is not gentoo) so installing on gentoo may be different.

Gentoo people wouldn't do that.
in fact the ebuild isn't out yet.

willytax

10-27-2007, 08:05 AM

unset the opengl overlay with Option "OpenGLOverlay" "off" and force xv with Option "VideoOverlay" "on". that should do the trick. you'll have some speed loss in terms of fps but you'll be able to run beryl,aiglx, and have no tearing. or at least that's what is happening to me.

I've already done that modification to xorg.conf, in fact I've xv acceleration, but videos are watchable only in fullscren mode. When windowed (i.e. using vlc) the video is black. If i use X11 as output, videos are fine, but my laptop fan never stops (high cpu load)!
Obviously all works fine without compiz...
Sorry for bad english!

givemesugarr

10-27-2007, 08:46 AM

Obviously all works fine without compiz...

of what is written around phoronix forums it seems that this driver doesn't work fine with compiz. i've also experimented it but found it to be unsable... maybe we will be luckier next month.:)

willytax

10-27-2007, 09:07 AM

of what is written around phoronix forums it seems that this driver doesn't work fine with compiz. i've also experimented it but found it to be unsable... maybe we will be luckier next month.:)

You're right...

thunderhawk

10-27-2007, 10:39 AM

I hope the driver is good, going to try it today or tomorrow with my hd2600 :)

Neo4

10-27-2007, 10:48 AM

Crunchy

10-27-2007, 10:57 AM

8.42.3 is now up on ATI's download drivers page.

mirv

10-27-2007, 11:41 AM

I'm getting the following message when exiting X:

(EE) fglrx(0): [drm] failed to remove DRM signal handler

It doesn't cause any problems (far as I can tell) but I'm not exactly sure what it's about either. Anyone know what it's about?
Cheers!

redfox76

10-27-2007, 12:08 PM

O, I need your help. I've Ubuntu 7.04 on notebook HP NC8430, ATI X1600. I've installed 8.42.3 and 3d works but...
1. on top left corner there is a random coloured single pixel row: it's a quarter of my screen and if I capture screen this row is not visible;
2. when I switch to text console (CTRL+ALT+F1) the xserver crash and returns on login screen (GDM restart)
3. If I start compiz the screen fills of strange colored pixel, if I stop compiz the screen returns normal (with top left strange row, of course: an example is here www.bizzarri.net/Schermata.png (http://www.bizzarri.net/Schermata.png))

I've tried a lot of xorg.conf variatons but without any visible effect: latest Device section is

Section "Device"
Identifier "aticonfig-Device[0]"
Driver "fglrx"
Option "EnableMonitor" "lvds"
Option "VideoOverlay" "on"
Option "OpenGLOverlay" "off"
Option "OverlayOnCRTC2" "0"
Option "Centermode" "off"
Option "PseudoColorVisuals" "on"
Option "BlockSignalsOnLock" "on"
Option "KernelModuleParm" "locked-userpages=0"
Option "XAANoOffscreenPixmaps" "true"
Option "AddARGBGLXVisuals" "On"
Option "AllowGLXWithComposite" "true"
EndSection

I've read a lot of post but I cannot figure if this issue is relative to my hardware or is a configuration problem...

Any ideas?

Regards,
Claudio

givemesugarr

10-27-2007, 02:17 PM

i've tried that think hwcursor to stop that desktop problem and it didn't was solved, i'm still have problems around my mouse and in the right corner of my desktop.
i have an x700 mobile.

i'm getting tired of ati
my next laptop and desktop won't definitely have ati cards!

can you post your /etc/X11/xorg.conf, what distro are you running, the kernel and if you run /etc/init.d/atieventsd at boot. maybe i can find out if it's a misconfiguration problem.
ps. do you get this thing with the normal kwin/gnome decorator?

It doesn't cause any problems (far as I can tell) but I'm not exactly sure what it's about either. Anyone know what it's about?
Cheers!

how do you log in x?! startx or /etc/init.d/xdm? do you per chance have compiled and loaded the drm kernel module (lsmod | grep drm). that should not be the case and should not load with fglrx but you never know...
ps. does it prevent you from working again normally after that error?

mirv

10-27-2007, 02:59 PM

how do you log in x?! startx or /etc/init.d/xdm? do you per chance have compiled and loaded the drm kernel module (lsmod | grep drm). that should not be the case and should not load with fglrx but you never know...
ps. does it prevent you from working again normally after that error?

startx - old habit from long ago.
drm is not enabled in the kernel at all, and no modules are loaded.
It does not prevent me from working again "normally" afterwards (i.e I still have a few things that go wrong - unable to load an opengl app first go; have to first open one, ctrl+c, then it all works just fine, but I did update to xserver 1.4 as well).

The following is reported from the x.org log:
(II) [drm] DRM interface version 1.0
(II) [drm] DRM open master succeeded.
(II) fglrx(0): [drm] Using the DRM lock SAREA also for drawables.
(II) fglrx(0): [drm] framebuffer handle = 0x13000
(II) fglrx(0): [drm] added 1 reserved context for kernel
(II) fglrx(0): [drm] installed DRM signal handler
(II) fglrx(0): [drm] register handle = 0x00015000
With the error line appearing only when I shut down X.

xeros

10-27-2007, 03:02 PM

i've tried that think hwcursor to stop that desktop problem and it didn't was solved, i'm still have problems around my mouse and in the right corner of my desktop.
i have an x700 mobile.

This line in Device section of xorg.conf should repair this problems with mouse and right corner of the desktop:
Option "XAANoOffscreenPixmaps" "true"

I had the same problem and this helped me - from two days I don't have this screen corruption.

i'm getting tired of ati
my next laptop and desktop won't definitely have ati cards!

I was hoping that ATI will fix most bugs but now I'm planning to buy Geforce 8600GT soon.

givemesugarr

10-27-2007, 03:43 PM

It does not prevent me from working again "normally" afterwards (i.e I still have a few things that go wrong - unable to load an opengl app first go; have to first open one, ctrl+c, then it all works just fine, but I did update to xserver 1.4 as well).

i first must say that i still use xorgserver 1.3 since on gentoo the 1.4 is stil unstable, so it should still have some problems with deps or so. normally using it should do well, but you never know, so i've decided to remain with the 1.3.
if you now use the 1.4 i'd suggest you download and install the svn version so that you really have it fully updated and bugfixed, as for mesa and xorg-x11. if you passed to 1.4 pass also to xorg 7.3 and use for all of them the svn version. then reinstall the ati drivers after being sure that you use the 2.6.22-9 max if you use 64bit arch, or you'll have some problems. anyway, before doing this try setting the following options and tell me how they work for you. i'm really interested in knowing how an igp board behaves with xorgserver 1.4.
Option "CapabilitiesEx" "0x00000000"
Option "Capabilities" "0x00000000"
this should set the capabilities of the board to the default options with less stuff for the board to do, but with some more stability.
then remember: XAANoOffscreenPixmaps true, hwcursor on, and the videooverlay on. remember to also start atieventsd at boot, and look out for the signature, control and fglrxrc files inside /etc/ati.
then restart x after loading atieventsd and see what happens.

I was hoping that ATI will fix most bugs but now I'm planning to buy Geforce 8600GT soon.

if you don't really need it right now i'd suggest you wait for one or two months and see if the 3d part of the specs are released for r600+ series. if that would be the case buying an hd2600 would be better. as far as i've read about the radeon-hd the driver is progressing really fast.

mirv

10-28-2007, 05:22 AM

I'll wait for official portage ati-drivers ebuild to update everything x again (ati-drivers blocking xserver and all) - I have been having an issue with transparent Eterms causing a few slowdowns which the changes to xorg.conf seem to have fixed, thanks! I rather expected a few things to act weird as I tend to use the unstable packages a lot, but getting everything top-notch again gives me something to do.

givemesugarr

10-28-2007, 08:44 AM

try removing this:

Option "EnableMonitor" "lvds"
Option "AddARGBGLXVisuals" "On"

and insert
Option "DPMS"

in the monitor section (notebook should always have dpms included into the monitors).
the lvds thing is not needed (i think) for running it on a notebook monitor and the other option used to break my xorg.
i'm not familiar with gnome since i don't like it at all and the 7.04 has both xorg7.3 and xorg-server 1.4 and maybe also the 2.6.23 kernel, but i also don't know much of it since i personally hate ubuntu too.
these options should fix the issue, but if it doesn't then i'm afraid that i cannot be of use for you. on my notebook work like a charm, but i have an older igp series board and not a quite new one.

I'll wait for official portage ati-drivers ebuild to update everything x again (ati-drivers blocking xserver and all) - I have been having an issue with transparent Eterms causing a few slowdowns which the changes to xorg.conf seem to have fixed, thanks! I rather expected a few things to act weird as I tend to use the unstable packages a lot, but getting everything top-notch again gives me something to do.

you just need to downgrade xorg and xorg-server too 7,2 and 1,3 and ati drivers should work well. they should also work with 7,3 and 1,4 as state the release notes but i haven't personally tested it yet. as for the time of compilation, i hope that you've installed ccache with at least 2gb of cache, otherwise you'd be very sloooooow on upgrading/downgrading stuff. and on base packages as xorg or kdebase i also use the buildpkg feature of portage so that i can reinstall quickly the older packages if something doesn't work.

Berniyh

10-28-2007, 10:22 AM

you just need to downgrade xorg and xorg-server too 7,2 and 1,3 and ati drivers should work well. they should also work with 7,3 and 1,4 as state the release notes but i haven't personally tested it yet. as for the time of compilation, i hope that you've installed ccache with at least 2gb of cache, otherwise you'd be very sloooooow on upgrading/downgrading stuff. and on base packages as xorg or kdebase i also use the buildpkg feature of portage so that i can reinstall quickly the older packages if something doesn't work.
I've got it running with xorg-server-1.4 here and it is working fine. I didn't expect any problems that could be related to xorg-server-1.4, but I don't use AIGLX, so I don't know about that.

Just to inform you: I compiled 8.42.3 against the new kernel 2.6.24-rc1 (with current 2.6.23 patches) and it worked, so 8.43 should not only officially support 2.6.23, it should support 2.6.24 as well.
I didn't really try it, because my network shows bugs and doesn't work.

givemesugarr

10-28-2007, 11:36 AM

Just to inform you: I compiled 8.42.3 against the new kernel 2.6.24-rc1 (with current 2.6.23 patches) and it worked, so 8.43 should not only officially support 2.6.23, it should support 2.6.24 as well.
I didn't really try it, because my network shows bugs and doesn't work.

lucky you!!! i'm still with 2.6.22.... madwifi gave me an error some days ago when i last tried to compile it with 2.6.23 and since that is not an option i still stay with older stuff; i've seen today with the sync that there's a new version of madwifi so maybe i'll try out 2.6.23 and see what happens with it and with the ati-drivers.
what patch do i have to add to the ebuild to make it work? (i remember to have successfully compiled the 8.40.4 without any patchset when i last tried 2.6.23).

I've got it running with xorg-server-1.4 here and it is working fine. I didn't expect any problems that could be related to xorg-server-1.4, but I don't use AIGLX, so I don't know about that.

for this i don't know anything, since i don't use it, but if you say that you don't have encountered problem running it i might decide to try it out too.

Berniyh

10-28-2007, 11:45 AM

lucky you!!! i'm still with 2.6.22.... madwifi gave me an error some days ago when i last tried to compile it with 2.6.23 and since that is not an option i still stay with older stuff; i've seen today with the sync that there's a new version of madwifi so maybe i'll try out 2.6.23 and see what happens with it and with the ati-drivers.
what patch do i have to add to the ebuild to make it work? (i remember to have successfully compiled the 8.40.4 without any patchset when i last tried 2.6.23).
For 8.40.4 there is a patch in the tree.

For 8.42.3, go to the bugreport read comment #40 and those that follow.

willytax

10-28-2007, 01:15 PM

Uchikoma

10-28-2007, 01:49 PM

Someone could please tell me how to get te suspend2ram working.
I'm using Gutsy (amd64) with an ati mobility x700 and fglrx 8.42.3
I googled around and found that the problem is related to the slub support of the fglrx driver (slub used by default with Gutsy).

I'd prefer not to have to recompile the kernel with slab...:(

There is no fix. Either you

a) Recompile the kernel using the SLAB allocator
b) Downgrade to a kernel that uses the SLAB allocator (eg. some of the feisty kernels)
c) Wait till ATI hopefully fixes it within the next driver. Or ... for many months...

That's about it. You can try some of the workarounds mentioned before, but from experience, they didn't work for me (and I don't even think they were addressing this particular issue: SLAB + fglrx)

jd10008

10-28-2007, 10:55 PM

Looks like this driver does not support the xv protocol.
When running xine, I get the error:

video_out_xv: Xv extension is present but I couldn't find a usable yuv12 port.
Looks like your graphics hardware driver doesn't support Xv?!

Review: http://www.phoronix.com/vr.php?view=11287

Digg: http://digg.com/linux_unix/AMD_8_42_Driver_Brings_Fixes_AIGLX

(This codename came from all of the discussion in this Phoronix Forums thread: http://www.phoronix.com/forums/showthread.php?t=5422)

Michael

10-29-2007, 07:03 AM

mile

10-29-2007, 07:37 AM

Looks like you don't have TexturedVideo enabled from your xorg.conf.

i have TexturedVideo in device section, but yuv12 is missing on my m56p

willytax

10-29-2007, 07:58 AM

There is no fix. Either you

a) Recompile the kernel using the SLAB allocator
b) Downgrade to a kernel that uses the SLAB allocator (eg. some of the feisty kernels)
c) Wait till ATI hopefully fixes it within the next driver. Or ... for many months...

That's about it. You can try some of the workarounds mentioned before, but from experience, they didn't work for me (and I don't even think they were addressing this particular issue: SLAB + fglrx)

Finally got the suspend2ram work. I recompiled the kernel with slab and now it works like a charm :D.
In dmesg, after I resumed, I've these lines:

[ 48.633608] [fglrx] firegl_gps_setpowerdown .
[ 0.463238] [fglrx] firegl_gps_setpowerup .
[ 3.430609] [fglrx:firegl_cmmqs_reinit] *ERROR* CMMQS reinitialization is failed.

but all works fine.
Hope the next relase (8.43) will support SLUB!

Porter

10-29-2007, 10:36 AM

Does anyone have an inside track on when the 8.42.3 driver will be rolled out in the Ubuntu repositories? Is there a timeline?

Thanks!

givemesugarr

10-29-2007, 10:40 AM

Does anyone have an inside track on when the 8.42.3 driver will be rolled out in the Ubuntu repositories? Is there a timeline?

i don't know if it will reach the new gusty. the problem is that the 7+ release uses the new slub which don't work well with slub, i don't think it will reach the official repo soon. first it has to be patched in some way, but since i've read that it needs to recompile the kernel with slab to have some functions to work, i don't think that the official packagers would insert a broken package inside their repo.

Uchikoma

10-29-2007, 11:18 AM

Porter

10-29-2007, 12:37 PM

i don't know if it will reach the new gusty. the problem is that the 7+ release uses the new slub which don't work well with slub, i don't think it will reach the official repo soon. first it has to be patched in some way, but since i've read that it needs to recompile the kernel with slab to have some functions to work, i don't think that the official packagers would insert a broken package inside their repo.
Well, the current fglrx driver included in Ubuntu 7.10 is just as broken with regard to SLUB, so I'm not sure why it would matter.

ATI fglrx 8.42.3 will NOT be added to the Ubuntu repositories.
Do you know if there is a certain reason why this is? Considering that the current fglrx is also broken?

Uchikoma

10-29-2007, 12:51 PM

Well, the current fglrx driver included in Ubuntu 7.10 is just as broken with regard to SLUB, so I'm not sure why it would matter.

Do you know if there is a certain reason why this is? Considering that the current fglrx is also broken?

The fglrx version in Gutsy is the same as Feisty. (fglrx version 8.37).

It's been decided that they will not include the driver for the following reasons:

a) Poor performance (w/ Compiz notably)
b) They usually don't do linux-restricted-module backports either
c) It's not regression free as many a person has noted here.

That about sums it up. You can view the launchpad entry with full details and comments from users and the Ubuntu team.

https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.22/+bug/156325

Perhaps in time, when 8.43 comes out, and everything is more stable (for instance no tearing/choppy video in Xv with Compiz), then they'll consider backporting it. Best to wait till we get an fglrx release that is relatively stable and works well with compiz before asking again.