Ati has noted that it will release 8.41 inside of a week from now - This bug can be a placeholder for a version bump request. As soon as I can lay my hands on it I'm building this one - will submit an ebuild based on 8.40 ebuild... Please let me know if I'm filing this incorrectly
It has been released. http://www.phoronix.com/scan.php?page=article&item=833&num=1 https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-8.41.7-x86.x86_64.run
Looked into it and the only ebuild modification that seems to be needed is the removal of the line gunzip common/usr/share/man/man8/atieventsd.8 || die "manpage unzip failed" since it is now delivered unzipped. Both the warnings patch and the 2.6.23 patch apply fine.
Bernd you beat me to it! I was just gonna post all that here too :) Hopefully it's in portage allready now, cause i'm sure that all ATi gentoo users will want this one badly.
I also had to comment #epatch ${FILESDIR}/${PV}/${P}-warnings.patch to get it to install properly. (file missing error, for obvious reasons).
(In reply to comment #4) > I also had to comment > #epatch ${FILESDIR}/${PV}/${P}-warnings.patch > to get it to install properly. (file missing error, for obvious reasons). > You have to copy that patch. cp files/8.40.4 files/8.41.7 and mv files/8.41.7/ati-drivers-8.40.4-warnings.patch files/8.41.7/ati-drivers-8.41.7-warnings.patch Then it will apply. I forgot one modification, that is needed: -doins common/etc/ati/{fglrxprofiles.csv,fglrxrc,logo*,control,atiogl.xml,signature} +doins common/etc/ati/{logo*,control,atiogl.xml,signature} Those files don't exist in the new driver.
Created attachment 130741 [details, diff] ati-drivers-8.41.7.ebuild.diff Patch for the ebuild.
This new driver isn't working with xorg-server-1.4. I get: (EE) module ABI major version (1) doesn't match the server's version (2) (EE) Failed to load module "fglrx" (module requirement mismatch, 0) That is a bummer.
Ok, I tried to use the new driver(Xpress 200M), but every application that uses OpenGL (glxgears, fgl_fglrxgears, ustunts...) segfaults. So I'll downgrade to the old driver and hope that others will have more luck.
Wow. This wasn't even a 0 day bug.. it was a -7 day bug! Impressive!
I don't know what the normal procedure here is, but I'd recommend strongly against putting this driver into portage. It is ONLY for R600 cards. Several users have reported problems, including myself having a segfault and X not even starting: (II) LoadModule: "GLcore" (II) Loading /usr/lib/xorg/modules/extensions//libGLcore.so (II) Module GLcore: vendor="X.Org Foundation" compiled for 7.2.0, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.3 (II) GLX: Initialized MESA-PROXY GL provider for screen 0 Backtrace: 0: /usr/X11R6/bin/X(xf86SigHandler+0x81) [0x80c5d91] 1: [0xffffe420] 2: /usr/lib/xorg/modules//glesx.so [0xb5c6ea24] 3: /usr/lib/xorg/modules//glesx.so [0xb5c6809c] 4: /usr/lib/xorg/modules//glesx.so [0xb5bfb3fb] 5: /usr/lib/xorg/modules//glesx.so [0xb5c0d196] 6: /usr/lib/xorg/modules//glesx.so [0xb5bfa3d9] 7: /usr/lib/xorg/modules//glesx.so [0xb5c23c12] 8: /usr/lib/xorg/modules//glesx.so [0xb5c11ebd] 9: /usr/lib/xorg/modules//glesx.so [0xb5c13469] 10: /usr/lib/xorg/modules//glesx.so [0xb5b9a6e3] 11: /usr/lib/xorg/modules//glesx.so [0xb5b8ff88] 12: /usr/lib/xorg/modules//glesx.so [0xb5b90670] 13: /usr/lib/xorg/modules//glesx.so(esutInit+0x74) [0xb5b8f484] 14: /usr/lib/xorg/modules//glesx.so [0xb5b8b17b] 15: /usr/lib/xorg/modules//glesx.so(GlesxExtensionInit+0x9b) [0xb5b8a3fb] 16: /usr/X11R6/bin/X(InitExtensions+0xa2) [0x80f4412] 17: /usr/X11R6/bin/X(main+0x2af) [0x807459f] 18: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xdc) [0xb7d94ebc] 19: /usr/X11R6/bin/X(FontFileCompleteXLFD+0x1e1) [0x8073ab1] Fatal server error: Caught signal 11. Server aborting
Everyone having problems with segfaulting opengl applications should check if the current user has r/w access to /dev/dri/cardX (usually card0), and if not - grant them.
Ebuild needs to eselect opengl set xorg-x11 at start and eselect opengl set ati at the end... installed and mostly good -- glxinfo shows direct rendering=yes and glxgears is showing much better than what I got in 8.40 on amd64 kernel. *cough* *cough* fgl_glxgears works -- but -- no texture on the cube ... perhaps because X started before I eselect opengl set ati Loading wine its complaining: fixme:win:EnumDisplayDevicesW ((null),0,0x33edac,0x00000000), stub! err:wgl:get_fbconfig_from_visualid No fbconfig found for Wine's main visual (0x27), expect problems! err:wgl:init_formats Can't get the FBCONFIG_ID for the main visual, expect problems! err:wgl:get_fbconfig_from_visualid No fbconfig found for Wine's main visual (0x27), expect problems! err:wgl:init_formats Can't get the FBCONFIG_ID for the main visual, expect problems!
(In reply to comment #12) > Ebuild needs to eselect opengl set xorg-x11 at start and eselect opengl set > ati at the end... > at start\end of what? I do have the segfaults problem with glxgears\fgl_fglxgears
(In reply to comment #11) > Everyone having problems with segfaulting opengl applications should check if > the current user has r/w access to /dev/dri/cardX (usually card0), and if not - > grant them. > ls -l /dev/dri/card0 crw-rw-rw- 1 root root 226, 0 12. Sep 23:11 /dev/dri/card0 So they are alright for me, but it still segfaults. (In reply to comment #12) > installed and mostly good -- glxinfo shows direct rendering=yes and glxgears > is showing much better than what I got in 8.40 on amd64 kernel. *cough* *cough* It does show that for me, too, but on running glxgears (or any other) it segfaults. Might this have something to do with gcc-4.2* and binutils-2.18?
(In reply to comment #13) > (In reply to comment #12) > > Ebuild needs to eselect opengl set xorg-x11 at start and eselect opengl set > > ati at the end... > > > > at start\end of what? > I do have the segfaults problem with glxgears\fgl_fglxgears > before building the driver and after building the driver --
Okay -- clean reboot - eselect opengl ati before starting X fgl_fglxgears works - about 140% of on 8.40 - -- but oddly there is no texture on the cube... Wine is still complaining about not finding FB_CONFIG_ID for main visual ( it lists this as 0x27 ) however xvinfo shows 0x27 listed -- I'm considering that I might have to rebuidl wine to use the newer ati gl library ... X-Video Extension version 2.2 screen #0 Adaptor #0: "ATI Radeon Video Overlay" number of ports: 1 port base: 83 operations supported: PutImage supported visuals: depth 24, visualID 0x23 depth 24, visualID 0x24 depth 24, visualID 0x25 depth 24, visualID 0x26 depth 24, visualID 0x27 depth 24, visualID 0x28 depth 24, visualID 0x29 depth 24, visualID 0x2a depth 24, visualID 0x2b depth 24, visualID 0x2c depth 24, visualID 0x2d depth 24, visualID 0x2e depth 24, visualID 0x2f depth 24, visualID 0x30 depth 24, visualID 0x31 depth 24, visualID 0x32 depth 24, visualID 0x33 depth 24, visualID 0x34 depth 24, visualID 0x35 depth 24, visualID 0x36 depth 24, visualID 0x37 depth 24, visualID 0x38 depth 24, visualID 0x39 depth 24, visualID 0x3a depth 24, visualID 0x3b depth 24, visualID 0x3c depth 24, visualID 0x3d depth 24, visualID 0x3e depth 24, visualID 0x3f depth 24, visualID 0x40 depth 24, visualID 0x41 depth 24, visualID 0x42 number of attributes: 12 "XV_SET_DEFAULTS" (range 0 to 1) client settable attribute "XV_AUTOPAINT_COLORKEY" (range 0 to 1) client settable attribute client gettable attribute (current value is 1) "XV_COLORKEY" (range 0 to -1) client settable attribute client gettable attribute (current value is 30) "XV_DOUBLE_BUFFER" (range 0 to 1) client settable attribute client gettable attribute (current value is 1) "XV_BRIGHTNESS" (range -1000 to 1000) client settable attribute client gettable attribute (current value is 0) "XV_CONTRAST" (range -1000 to 1000) client settable attribute client gettable attribute (current value is 0) "XV_SATURATION" (range -1000 to 1000) client settable attribute client gettable attribute (current value is 0) "XV_COLOR" (range -1000 to 1000) client settable attribute client gettable attribute (current value is 0) "XV_HUE" (range -1000 to 1000) client settable attribute client gettable attribute (current value is 0) "XV_RED_INTENSITY" (range -1000 to 1000) client settable attribute client gettable attribute (current value is 0) "XV_GREEN_INTENSITY" (range -1000 to 1000) client settable attribute client gettable attribute (current value is 0) "XV_BLUE_INTENSITY" (range -1000 to 1000) client settable attribute client gettable attribute (current value is 0) maximum XvImage size: 2048 x 2048 Number of image formats: 4 id: 0x32595559 (YUY2) guid: 59555932-0000-0010-8000-00aa00389b71 bits per pixel: 16 number of planes: 1 type: YUV (packed) id: 0x59565955 (UYVY) guid: 55595659-0000-0010-8000-00aa00389b71 bits per pixel: 16 number of planes: 1 type: YUV (packed) id: 0x32315659 (YV12) guid: 59563132-0000-0010-8000-00aa00389b71 bits per pixel: 12 number of planes: 3 type: YUV (planar) id: 0x30323449 (I420) guid: 49343230-0000-0010-8000-00aa00389b71 bits per pixel: 12 number of planes: 3 type: YUV (planar) No segfaults here - -however resetting the server (I'm running kdm and have the always reset server=true bit set) results in a display lockup - ssh in to reboot or magic sys req keys to reboot. this is on 2.6.22 gentoo sources and xorg 7.1 wine 0.9.43
(In reply to comment #16) > Okay -- clean reboot - eselect opengl ati before starting X > > fgl_fglxgears works - about 140% of on 8.40 - -- but oddly there is no > texture on the cube... > > Wine is still complaining about not finding FB_CONFIG_ID for main visual > ( it lists this as 0x27 ) <<<<< SNIPPAGE TO REDUCE SPAM >>>>> > > > this is on 2.6.22 gentoo sources and xorg 7.1 wine 0.9.43 > Rebuilt wine against the new libgl -- No change - this stands as an issue --- likely with the way wine is getting the id.... *sigh* looks like I'm gonna roll this one back after I test the X1650Pro
(In reply to comment #17) > (In reply to comment #16) > > Okay -- clean reboot - eselect opengl ati before starting X > > > > fgl_fglxgears works - about 140% of on 8.40 - -- but oddly there is no > > texture on the cube... > > > > Wine is still complaining about not finding FB_CONFIG_ID for main visual > > ( it lists this as 0x27 ) > <<<<< SNIPPAGE TO REDUCE SPAM >>>>> > > > > > > this is on 2.6.22 gentoo sources and xorg 7.1 wine 0.9.43 > > > > > Rebuilt wine against the new libgl -- No change - this stands as an issue > --- likely with the way wine is getting the id.... *sigh* looks like I'm gonna > roll this one back after I test the X1650Pro > Wine and ATI disagree on how to identify visualids apparently -- Roderick Colenbrander (wine) has opened a bug with ATI to fix this - but has posted a patch that appears to overcome the visual detection requirement - but leaves world of warcraft unplayable on wine - details on request... Im rolling this back -- I'm insufficiently happy with this version - I'll test X1650Pro agp card separately later.
I have tested the driver on my Xpress 200M IGP and it works well. When loading the fglrx module I get: [fglrx] Maximum main memory to use for locked dma buffers: 803 MBytes. [fglrx] ASYNCIO init succeed! [fglrx] PAT is enabled successfully! [fglrx] module loaded - fglrx 8.41.7 [Sep 7 2007] on minor 0 [fglrx] GART Table is not in FRAME_BUFFER range [fglrx] Reserve Block - 0 offset = 0X0 length = 0X40000 [fglrx] Reserve Block - 1 offset = 0X7ff5000 length = 0Xb000 [fglrx] Not implemented, need to call CMM to get the mem info This was not there before but does not seem to affect anything - games run fine and way faster.
the only way for me to get glxgears working without segfaults is to run it with DISPLAY=:93, btw, with 8.41 I have 2500fps instead of the 4300 of 8.40 running compiz
works like a charm here (X300) and fast!
My X1950Pro AGP hardlocks my system :/ Appears to be identical behaviour as with all releases after the 8.34, so i'm back to that one for now. Hopefully 8.42 will finally get my 2D working again.
(In reply to comment #22) > My X1950Pro AGP hardlocks my system :/ Appears to be identical behaviour as > with all releases after the 8.34, so i'm back to that one for now. Hopefully > 8.42 will finally get my 2D working again. > Oliver : I've an X1650Pro that exhibited this behaviour until I increased the size of AGP mem in the bios on my machine - the hard lock occurred as X started up and attempted to initialize DRI ... There are 2*256Mb memory pools on my card (512Mb) - I set the gart to 256M in bios and the lockups went away -- however I still (as of 8.40) did not get AGP accelleration as the driver detects the card as PCIE... have yet to test this on 8.41.
I've set it to 1GB and still get a black screen with lockups :( I have it at 256mb now and everything seems ok (with 8.34 driver). But, i can always try again at 512MiB and see what happens :)
(In reply to comment #21) > works like a charm here (X300) and fast! > same here (x300 mobility) except for that I get sometimes white horizontal stripes around my cursor. But really rarely.
i have some probs with the driver/ebuild: https://bugs.gentoo.org/show_bug.cgi?id=192540
(In reply to comment #24) > I've set it to 1GB and still get a black screen with lockups :( I have > it at 256mb now and everything seems ok (with 8.34 driver). > > But, i can always try again at 512MiB and see what happens :) > Ok I was wrong, all UP until 8.41 hardlock. 8.41 gives me some nice crash info :) (With 1G AGP mem). valexia ~ # cat 8.41.7_crashlog xauth: creating new authority file /root/.serverauth.5213 X Window System Version 7.2.0 Release Date: 22 January 2007 X Protocol Version 11, Revision 0, Release 7.2 Build Operating System: Linux 2.6.20-gentoo-r6 i686 Current Operating System: Linux valexia 2.6.22-gentoo-r6 #3 SMP PREEMPT Sun Sep 2 19:44:56 CEST 2007 i686 Build Date: 12 June 2007 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Sat Sep 15 01:07:48 2007 (==) Using config file: "/etc/X11/xorg.conf" (WW) fglrx: No matching Device section for instance (BusID PCI:1:0:1) found Backtrace: 0: X(xf86SigHandler+0xa9) [0x80af0df] 1: /usr/lib/xorg/modules//glesx.so [0xb5c09a24] 2: /usr/lib/xorg/modules//glesx.so [0xb5c0309c] 3: /usr/lib/xorg/modules//glesx.so [0xb5b963fb] 4: /usr/lib/xorg/modules//glesx.so [0xb5ba8196] 5: /usr/lib/xorg/modules//glesx.so [0xb5b953d9] 6: /usr/lib/xorg/modules//glesx.so [0xb5bbec12] 7: /usr/lib/xorg/modules//glesx.so [0xb5bacebd] 8: /usr/lib/xorg/modules//glesx.so [0xb5bae469] 9: /usr/lib/xorg/modules//glesx.so [0xb5b356e3] 10: /usr/lib/xorg/modules//glesx.so [0xb5b2af88] 11: /usr/lib/xorg/modules//glesx.so [0xb5b2b670] 12: /usr/lib/xorg/modules//glesx.so(esutInit+0x74) [0xb5b2a484] 13: /usr/lib/xorg/modules//glesx.so [0xb5b2617b] 14: /usr/lib/xorg/modules//glesx.so(GlesxExtensionInit+0x9b) [0xb5b253fb] 15: X(InitExtensions+0x8b) [0x80d34bd] 16: /lib/libc.so.6(__libc_start_main+0xe0) [0xb7c719c0] 17: X(FontFileCompleteXLFD+0xa9) [0x806d991] Fatal server error: Caught signal 11. Server aborting XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining.
works very fine here 2.6.20er thinkpad kernel x1400 coreduo t2500 IBM T60 But now i have till now two ebuilds violating sandbox (gkrellm and wxgtk) by accessing /dev/dri/card0, WHY????
btw, I have pasted the gkrellm mess here, http://phpfi.com/263679
(In reply to comment #29) > btw, I have pasted the gkrellm mess here, http://phpfi.com/263679 > 1) Bugzilla is English only since most Gentoo developers do not speak German. 2) Pastebin's suck because the content expires yet the bug lives on 3) Comment #26 references a bug that is your issue.
oh sorry for the german paste, ok i added both in the other bug, but it confirms the issue but shows no real solution and doesn't promise any advance on the issue because it is closed. So has someone an real idea on it? it may be essential to track this problem down, because before it is solved this driver can't proceed to portage.
(In reply to comment #28) > works very fine here > 2.6.20er thinkpad kernel > x1400 > coreduo t2500 > IBM T60 > > But now i have till now two ebuilds violating sandbox (gkrellm and wxgtk) by > accessing /dev/dri/card0, WHY???? > This is a known issue and will be fixed upstream. This should never land in portage as it is only ment for the hdXXXX cards which are far in inbetween still. Most users will have problems with this the ebuild should go to an overlay at best ... 8.42.x will restore full functionality for cards that were dropped in the transition.
Reopen when they get something non-broken out, please. WONTFIX meanwhile.
i have hd2400, can not use original driver, could someone release an overlay ?
Michal, don't whine, you've said this almost a month after the release of fglrx 8.41, plus, you had to live with it for montsh already anyway. 8.42 is coming in a couple of weeks, it'll do everything you want it to do (except for bake cookies)
Patch does not apply here. I've tried editing the ebuild, but so far I've been unsuccessful in getting a working ebuild.
unfortunately i have both this card three weeks ago, I'm trying to get it running from this time, on Gentoo I have stooped on : ------------------------- Error: ./default_policy.sh does not support version default:v2:x86_64:lib32::none:2.6.23-rc6-mpa; make sure that the version is being correctly set by --iscurrentdistro ------------------------- on SuSE it installed but when Xorg is starting computer reboots
