Re: ati driver update problems
- From: Richard Stonehouse <richard@xxxxxxxxxxxxxxxxxx>
- Date: 14 Aug 2006 20:27:16 GMT
It's working for me on SuSE 9.3 using a recent fglrx driver. I'm no
expert on this stuff but hope the following may be some use.
On 2006-08-14, Duluoz <jamierc1@xxxxxxxxx> wrote:
I followed the Jem Report guide, to try to get 3D support working in
Suse 10.1
(A caveat - I'm on SuSE 9.3 and not familiar with the Jem report).
(download latest ati drivers, install them, run aticonfig to point to
new xorg file, run sax2 to set 0=fglrx)
I didn't do it in that order. As I understand it, aticonfig takes an
existing xorg.conf and updates it, inserting additional "Monitor",
"Device" and "Screen" sections for the fglrx driver and the monitor
attached to it. So I generated a basic xorg.conf using sax2, then ran
aticonfig using that as the input configuration:
aticonfig --initial\
--resolution=0,1600x1200,1280x1024,1152x864,\
1024x768,800x600,640x480\
--verbose\
--input=xorg.conf
On my (9.3) system, if you use sax2 to generate a config for fglrx
using the profile provided by SUSE, you get a whole lot of options in
the xorg.conf that, I think, are not used by (and may even be harmful
to) more recent versions of the fglrx driver.
The relevant sections in the new, working xorg.conf are:
Section "Monitor"
Identifier "aticonfig-Monitor[0]"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection
Section "Device"
Identifier "aticonfig-Device[0]"
Driver "fglrx"
EndSection
Section "Screen"
Identifier "aticonfig-Screen[0]"
Device "aticonfig-Device[0]"
Monitor "aticonfig-Monitor[0]"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1600x1200" "1280x1024" "1152x864" "1024x768" "800x600" "640x480"
EndSubSection
EndSection
A lot simpler than X configuration files for fglrx used to be!
However, now it wont boot to a gui, just straight to a shell login.
A familiar symptom. Is there an error message somewhere in the log
file (/var/log/Xorg.0.log)? Also try the system log (dmesg command or
/var/log/messages).
This is what I've tried to correct it, with no luck.
- changed aticonfig to point its initial path to the original xorg file
This is correct, I think.
- uninstalled the rpm package that the ati driver installed.
Shouldn't be necessary.
- tried to run sax2 (which wont work as it cant find an Xserver
As indicated above, I don't think sax2 will help a lot, apart from
generating the initial xorg.conf file (which I would generate for
'radeon', the standard driver released with X), and which you then
modify using aticonfig.
Any suggestions at all will be gratefully tried. I think I might need
to remove the 'fglrx' module from the kernel, but I dont know what the
opposite of the insmod command is, and I don't want to do something I
dont understand.
The opposite of insmod is rmmod - but I don't think that's what you
want to do - insmod just loads the module for the current session (or
until unloaded) and the fglrx driver will load the kernel module when
needed anyway. So you don't need to do anything here.
If the worst comes to the worst, and I need to reinstall,
You shouldn't need to reinstall. At worst, you might have to
regenerate the X configuration file. If the existing X configuration
is in such a state that sax2 won't run, try blowing it away (delete
or, better, rename it). I think sax2 should then work, even though
there is no X config file at all -if not, you can generate a very
basic X config using the 'xorgconfig' command (see man xorgconfig and
xorgconfig --help) and you should then be able to run sax2.
--
Richard Stonehouse
(Richard at R Stonehouse dot Co dot U.K.)
.
- References:
- ati driver update problems
- From: Duluoz
- ati driver update problems
- Prev by Date: Re: install problem
- Next by Date: Re: installing Suse with windows and Uninstalling !?
- Previous by thread: ati driver update problems
- Next by thread: Re: ati driver update problems
- Index(es):
Relevant Pages
|
