Talk:Ubuntu Dapper Installation Guide: Difference between revisions
(roricacol) |
|||
Line 1: | Line 1: | ||
cagetmonl | |||
it gets replaced only if there is a second device section in xorg.conf | it gets replaced only if there is a second device section in xorg.conf | ||
so make sure, when it works with libGL.so.1.2 that there is no other device section than fglrx | so make sure, when it works with libGL.so.1.2 that there is no other device section than fglrx |
Revision as of 03:31, 20 December 2008
cagetmonl it gets replaced only if there is a second device section in xorg.conf so make sure, when it works with libGL.so.1.2 that there is no other device section than fglrx
copy of libGL.so.1.2 to /usr/lib/ works fine but check, if there is also one in /usr/lib/fglrx/libGL.so.1.2 if so, the copied version is replaced (i don't know why). so both have to be replaced.
Wow, I followed this and it doesn't work, either method......
Now what? nobody to turn to, no more help available. Is it an ATI problem or a Dapper one?
I would have never believed that as "advanced" as this O/S is that it is this difficult to get a display driver to work.
This is absolutely incredible....
the problem is the driver, not the operating system.. ATI should take a lesson from nVidia.
[UBfusion reporting]: Many ATI chipsets suffer from this, due to faulty libGl.so.1.2 in the new ATI drivers - use the old file from old drivers, read http://ubuntuforums.org/showthread.php?t=185033
try using ONLY 128MB of UMA memory instead of Sideport+UMA
This is a really strange problem with the HP/Compaq R4000/zv6000:
Once upon a time, ATI driver fglrx_6_8_0-8.13.4-1.i386.rpm provided full DRI and 3D support on Ubuntu 5.04 kernel 2.6.10. ( wget http://www2.ati.com/drivers/linux/fglrx_6_8_0-8.13.4-1.i386.rpm )
Then, ATI's new releases only worked if we used 128MB of shared/system/UMA memory along with the 128MB of onboard video memory many of these laptop models have.
Now, after installing Ubuntu 6.0.6 kernel 2.6.15, the ATI driver will only work with full DRI and 3D support if I totally disable the 128MB of onboard video memory and use ONLY shared/system/UMA memory( 128MB )....
Now, with my fully functioning Ubuntu 5.0.4 installation, when I go from only Sideport to only UMA, the glxgears output goes from ~1200fps to ~500fps
With the new kernel and Xorg server of Ubuntu 6.0.6 running only UMA video memory and the 5.0.4 version of glxgears, output from that program is ~800fps. Still a 30% decrease in performance from using the 128MB of onboard/Sideport video memory.
IMO, running like this is not a fix but a crippled hack and it would be really nice if HP/Compaq or ATI would tell us what the problem is, why it exists, how it is to be fixed. So try just 128M of UMA in your BIOS and see if that enables you to get DRI/Direct Rendering working with the ATI/fglrx driver.
OK - I noticed that the wiki had been updated to reflect the 8.26.18 release but the line relating to the Xpress 200M card not functioning with the 8.25.18 drivers was unchanged. Can someone confirm if the 8.26.18 drivers work with the 200M card or not?
- I just tried it with the 8.28.8 drivers and while it does run with Sideport and UMA on it doesn't run well, including drawing errors and freezes shortly after logging in.
Also effected my xpress 200m on 64bit hp pavillion. changing to fglrx and using the guide worked. but only at 128mb uma. this could be a problem for a few people and could be mentioned.
almost work in Compaq nx7010
Hi,
I tryied everything I found with this $#%&"@ ati video card and, after 3 days of little sleeping and several distros & reinstallations, the closest to a working configuration I got was with Ubuntu dapper and method 1 in your guide (including HP zt3000 / Compaq nx7000 troubleshooting). Logically it seems to work (fglrxinfo reports OpenGL vendor string: ATI Technologies Inc., etc.) but phisically it doesn't (see the picture at [1]). Image is barely usable (loggin in that way I was able to run fglrxinfo), it covers 60% of the screen horizontally and flickers a lot.
Any ideas how to fix it?
File:Http://www.tirata.com/nx7010/nx7010.jpg
Mhhh could you post please your xorg.conf file in order to double check it? You could add the following too: max resolution (seems to be 1280 x 800 TFT), GPU Model (seems to be an ATI Radeon Mobility 9200, issue a lspci -v to know exactly the chipset type). With that info in hand __perhaps__ something can be done, some log files would be appreciated too.
As you describe it could be a problem with the Modelines configuration in xorg driving the TFT display out of sync. Try a lower resolution (say 1024x768, 800x600, 640x480); if it doesn't work try defining a manual modeline for the resolution you are trying. Good luck and keep posting! :-)
nx7000 problem
I have a strange problem with the ModeLine. It works when i use the ModeLine for the nx7010, but only the default resolution of 1680x1050. When i choose a lower resolution for example 1024x768 the screen is not useable. Can somebody help me? I have testet some ModeLine generaters, but nothing works.
debhelper
I found that I also needed to "apt-get install debhelper" before I could manually install the ati drivers
It worked in Etch for me.
I have Etch installed, with a Radeon 9550 card. I followed this guide, and the drivers installed without event. It was flawless. I want to thank whoever wrote this tutorial. Documentation does not get any better than this! This is why Ubuntu will take over the world, because of its fantastic user community!
Guide for edgy
Can you write installation instructions for Ubunty Edgy. When installing I get error message:
./ati-installer.sh: 176: Syntax error: Bad substitution
There is something about finding Firefox browser in 176th line of this file.
--82.143.132.112 02:59, 13 October 2006 (CDT)
There already IS a guide for edgy: http://wiki.cchtml.com/index.php/Ubuntu_Edgy_Installation_Guide
Stefan Dox
Genuinely interested by the website
Method 1 snipped, why?
On 10/28/06 user 211.232.210.154 snipped Method 1. I was going to revert it back to prior version but wanted to put out a call here first in case anyone knows why that would have been intentional. -- It was removed by spam bots. I've restored it.