From: Paul on 28 Jan 2010 20:59 On 01/28/10 07:51 PM, Aaron W. Hsu wrote: > On Thu, 28 Jan 2010 18:48:53 -0500, Paul <pminottawa(a)yahoo.ca> wrote: > >> I am now using the ATI proprietary driver. > > That's why you're getting those errors then. Those errors will only show > up when you are not running the DRI enabled ATI Proprietary driver with > the correct kernel modules loaded. In other words, the OpenGL errors > that you see indicate to me that you don't have a working proprietary > driver configuration. Did you follow the ATI instructions and build the > Slackware packages? Did you then follow the post-install message and run > aticonfig with the appropriate encantation to replace your xorg.conf? > > Aaron W. Hsu > Yes I did....I think. I could not get the ATI installer to work as downloaded, so I followed advice given on another forum: expanded the driver package, modified kcl_io.c to include linux/signal.h and then ran the installer using --buildandinstallpkg Slackware/All After that I ran aticonfig --initial Did I miss something?
From: Paul on 28 Jan 2010 21:00 On 01/28/10 07:48 PM, Aaron W. Hsu wrote: > On Thu, 28 Jan 2010 17:58:42 -0500, Paul <pminottawa(a)yahoo.ca> wrote: > >> Last night I set the compositing type to XRender. Desktop Effects now >> work > > Keep in mind that Xrender only provides a subset of the effects > available to you when you use OpenGL. > > Aaron W. Hsu > And this brings me back to the original problem: why won't it work with OpenGL?
From: Aaron W. Hsu on 28 Jan 2010 21:18 On Thu, 28 Jan 2010 20:59:43 -0500, Paul <pminottawa(a)yahoo.ca> wrote: > Did I miss something? Well, something isn't right. You should post your Xorg.0.log and xorg.conf file. What did you do with the aticonfig? Also, you might try downloading the new driver that amd posted on the 27th, and try to go through the standard package instead of doing all the manual work, which you shouldn't have to do on a Slackware 13.0 installation. It works just fine for me on my Slackware64 13.0 box with an ATI Mobility Radeon HD 3650. Aaron W. Hsu -- A professor is one who talks in someone else's sleep.
From: Aaron W. Hsu on 29 Jan 2010 00:39 On Thu, 28 Jan 2010 22:26:55 -0500, Paul <pminottawa(a)yahoo.ca> wrote: > That is the driver I have: 9.12. However my problems are independent of > that driver...I was originally using the open source drivers, radeon and > radeonhd, that were part of X. Okay, you should grab the latest driver and use that. > The only ati configuring I did was with aticonfig --initial. However I > am certainly willing to reinstall. How do I uninstall? You should just uninstall the packages that were installed. They should start with fgl or something like that. > Originally all the drivers worked for me, but I had to reinstall Linux. If you had to reinstall, did you also reinstall the drivers? You need to make sure your kernel versions match up with the modules that were compiled when you installed the driver. When you download the new driver, this is what I do to install it (assuming I've removed the old drivers): $ su # sh <installer> --buildpkg Slackware/All # installpkg fglrx*.tgz # aticonfig --initial=dual-head --screen-layout=right # shutdown -r now Notice that you *need* to be super user unless you've added the sbin directories to your path as a regular user; sudo won't cut it here. I don't know if my globs are correct, but they're close enough. I also have a dual-head setup, so you can alter that as you see fit. You also need to restart the machine for the new modules to kick in unless you just want to manually unload the old modules and reload the new ones, and then reboot your X Server manually. That's possible as well, but for me, I like to make sure that the whole thing works from start to finish. I also added the DRI with mode 0666 Section stuff to my Xorg.conf on a passing whim from a site that I found. I don't know if that is needed or not. > I included both the xorg.conf and Xorg.0.log files in my original post. > However I will include my lastest versions below: > > 1) xorg.conf That's significantly more complex than my dual-head xorg.conf. Maybe it puts all that in automatically, in which case you are probably alright. I would start by removing your xorg.conf file and then running the aticonfig file, so that you don't carry in any unnecessary baggage. > 2) Xorg.0.log >> (II) fglrx(0): driver needs X.org 1.4.x.y with x.y >= 99.906 >> (WW) fglrx(0): could not detect X server version (query_status=-1) >> (EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized. >> (WW) fglrx(0): *********************************************** >> (WW) fglrx(0): * DRI initialization failed! * >> (WW) fglrx(0): * (maybe driver kernel module missing or bad) * >> (WW) fglrx(0): * 2D acceleraton available (MMIO) * >> (WW) fglrx(0): * no 3D acceleration available * >> (WW) fglrx(0): ********************************************* * >> (II) fglrx(0): FBADPhys: 0xf00000000 FBMappedSize: 0x10000000 >> (II) fglrx(0): FBMM initialized for area (0,0)-(1280,8191) >> (II) fglrx(0): FBMM auto alloc for area (0,0)-(1280,1280) (front color >> buffer - assumption) Well there you go right there. :-) That says it all, doesn't it? You should read all of the (EE) Entries in your Xorg.0.log file and see where the trouble begins. I think the main problem you'll find is your modules and problems with loading those. :-) If you just used sudo to do the build, you may have missed the build failures (it doesn't do a good job of making them obvious) if you didn't have the right stuff in the path to make the package. If you subsequently expected the installer program to do the installation for you, then you could have had more problems from there. I would follow the above steps and make sure that the packages are created correctly, with no errors in the output. Aaron W. Hsu -- A professor is one who talks in someone else's sleep.
From: Paul on 29 Jan 2010 03:50 On 01/29/10 12:39 AM, Aaron W. Hsu wrote: > On Thu, 28 Jan 2010 22:26:55 -0500, Paul <pminottawa(a)yahoo.ca> wrote: > >> That is the driver I have: 9.12. However my problems are independent >> of that driver...I was originally using the open source drivers, >> radeon and radeonhd, that were part of X. > > Okay, you should grab the latest driver and use that. > >> The only ati configuring I did was with aticonfig --initial. However I >> am certainly willing to reinstall. How do I uninstall? > > You should just uninstall the packages that were installed. They should > start with fgl or something like that. > >> Originally all the drivers worked for me, but I had to reinstall Linux. > > If you had to reinstall, did you also reinstall the drivers? You need to > make sure your kernel versions match up with the modules that were > compiled when you installed the driver. When you download the new > driver, this is what I do to install it (assuming I've removed the old > drivers): > > $ su > # sh <installer> --buildpkg Slackware/All > # installpkg fglrx*.tgz > # aticonfig --initial=dual-head --screen-layout=right > # shutdown -r now > > Notice that you *need* to be super user unless you've added the sbin > directories to your path as a regular user; sudo won't cut it here. I > don't know if my globs are correct, but they're close enough. I also > have a dual-head setup, so you can alter that as you see fit. You also > need to restart the machine for the new modules to kick in unless you > just want to manually unload the old modules and reload the new ones, > and then reboot your X Server manually. That's possible as well, but for > me, I like to make sure that the whole thing works from start to finish. > I also added the DRI with mode 0666 Section stuff to my Xorg.conf on a > passing whim from a site that I found. I don't know if that is needed or > not. > >> I included both the xorg.conf and Xorg.0.log files in my original >> post. However I will include my lastest versions below: >> >> 1) xorg.conf > > That's significantly more complex than my dual-head xorg.conf. Maybe it > puts all that in automatically, in which case you are probably alright. > I would start by removing your xorg.conf file and then running the > aticonfig file, so that you don't carry in any unnecessary baggage. > >> 2) Xorg.0.log > >>> (II) fglrx(0): driver needs X.org 1.4.x.y with x.y >= 99.906 >>> (WW) fglrx(0): could not detect X server version (query_status=-1) >>> (EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized. >>> (WW) fglrx(0): *********************************************** >>> (WW) fglrx(0): * DRI initialization failed! * >>> (WW) fglrx(0): * (maybe driver kernel module missing or bad) * >>> (WW) fglrx(0): * 2D acceleraton available (MMIO) * >>> (WW) fglrx(0): * no 3D acceleration available * >>> (WW) fglrx(0): ********************************************* * >>> (II) fglrx(0): FBADPhys: 0xf00000000 FBMappedSize: 0x10000000 >>> (II) fglrx(0): FBMM initialized for area (0,0)-(1280,8191) >>> (II) fglrx(0): FBMM auto alloc for area (0,0)-(1280,1280) (front >>> color buffer - assumption) > > Well there you go right there. :-) That says it all, doesn't it? You > should read all of the (EE) Entries in your Xorg.0.log file and see > where the trouble begins. I think the main problem you'll find is your > modules and problems with loading those. :-) If you just used sudo to do > the build, you may have missed the build failures (it doesn't do a good > job of making them obvious) if you didn't have the right stuff in the > path to make the package. If you subsequently expected the installer > program to do the installation for you, then you could have had more > problems from there. I would follow the above steps and make sure that > the packages are created correctly, with no errors in the output. > > Aaron W. Hsu > The installer always exits with two failures. That is why I used the roundabout method I used. I built and installed the driver with the method you indicated--same errors, same results. DRI initialization is still failing. I have absolutely no clue as to why I get the build errors or the Xorg errors above.
First
|
Prev
|
Next
|
Last
Pages: 1 2 3 4 5 Prev: ATI xorg - Slackware 12.2/Slamd64 Next: Problems in dual boot |