SuSE 9.1 ATI 3.9.0 driver - problems with Dell Inspiron 8600 (ATI Mobility Radeon 9600 PRO Turbo)
Hi, I've installed Suse 9.1 on a Dell Inspiron 8600 (with ATI Mobility Radeon 9600 PRO Turbo card and 1920x1200 laptop display panel). Sax2 wouldn't recognize the 1900x1200 panel, so I googled a bit and managed to put together an XF86Config file (attached) that works quite well using the unaccelerated "radeon" driver. Then I decided to install the latest version of the ATI 3.9.0 driver available from Suse's ftp site following instructions in the README. Driver installs successfully, however when I run "sax2 -r -m 0=fglrx -b /usr/X11R6/lib/sax/profile/firegl", the screen goes blank, then parts of the screen go white, then green, :-) , at which moment I usually kill Sax with Ctrl-Shift-Backspace, and it exists generating the attached log file. The log says a) "DRI initialization failed"; and b) there are lots of unresolved symbols. I've already fixed error messages about MTRR overlaps using instructions from http://odin.prohosting.com/wedge01/gentoo-radeon-faq.html#4_mtrroverlap. I'd appreciate any suggestions. These are the relevant (I think) package versions: fglrx-3.9.0-2.1 km_fglrx-3.9.0-2.1 kernel-source-2.6.5-7.95 kernel-default-2.6.5-7.95 Regards, Vadym ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon August 2 2004 15:12, Vadym Krevs wrote:
Hi,
I've installed Suse 9.1 on a Dell Inspiron 8600 (with ATI Mobility Radeon 9600 PRO Turbo card and 1920x1200 laptop display panel). Sax2 wouldn't recognize the 1900x1200 panel, so I googled a bit and managed to put together an XF86Config file (attached) that works quite well using the unaccelerated "radeon" driver.
Then I decided to install the latest version of the ATI 3.9.0 driver available from Suse's ftp site following instructions in the README. Driver installs successfully, however when I run "sax2 -r -m 0=fglrx -b /usr/X11R6/lib/sax/profile/firegl", the screen goes blank, then parts of the screen go white, then green, :-) , at which moment I usually kill Sax with Ctrl-Shift-Backspace, and it exists generating the attached log file. The log says a) "DRI initialization failed"; and b) there are lots of unresolved symbols. I've already fixed error messages about MTRR overlaps using instructions from http://odin.prohosting.com/wedge01/gentoo-radeon-faq.html#4_mtrroverlap.
I'd appreciate any suggestions.
These are the relevant (I think) package versions:
fglrx-3.9.0-2.1 km_fglrx-3.9.0-2.1 kernel-source-2.6.5-7.95 kernel-default-2.6.5-7.95
#lsmod | grep fglrx If not present #modprobe fglrx then #sax2 -r -m 0=fglrx -b /usr/X11R6/lib/sax/profile/fglrx Buy the way what chipset does that run? Via, NForce/2, SiS? (it matters) Cheers, Curtis.
Regards, Vadym
********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
- -- Spammers Beware: Tresspassers will be shot, survivors will be shot again! Warning: Individuals throwing objects at the crocodiles will be asked to retrieve them! If pro is the opposite of con, then the opposite of progress must be congress! In the Ocean it's called salvage, on land it's called grave robbing! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBDxwU7CQBg4DqqCwRAgfIAJ0UnUUq7DYrXHqViMk6ZjaPBpiT+gCeMcoP ECDkkbE4qCIwJAdtYHn3UVU= =C+gN -----END PGP SIGNATURE-----
Hi Curtis, The notebook uses Intel 855PM chipset. I've already tried makimg sure that fglrx module is loaded before SAX2 is executed - to no avail. Because of the following warning in the XFree86 logs mtrr: 0xd0000000,0x8000000 overlaps existing 0xd0000000,0x4000000 I've executed # echo "disable=2" >/proc/mtrr # echo "base=0xd8000000 size=0x8000000 type=write-combining" >/proc/mtrr and then, as you suggested, # lsmod | grep fglrx # modprobe -v fglrx insmod /lib/modules/2.6.5-7.95-default/kernel/drivers/char/drm/fglrx.ko # lsmod | grep fglrx fglrx 200356 0 then #sax2 -r -m 0=fglrx -b /usr/X11R6/lib/sax/profile/fglrx still fails and the screen shows those psychedelic colors before I kill X server. I've tried editing my current XF86Config file to force it to load the fglrx driver (see attached file), however that did not help either - the same garbage on the screen is shown after "init 5" and then I kill the Xserver. However, as the attached XFree86 log shows, the drivers appears to have been loaded sucessfully, DRI got initialized, etc .. Regards, Vadym Curtis Rey wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mon August 2 2004 15:12, Vadym Krevs wrote:
Hi,
I've installed Suse 9.1 on a Dell Inspiron 8600 (with ATI Mobility Radeon 9600 PRO Turbo card and 1920x1200 laptop display panel). Sax2 wouldn't recognize the 1900x1200 panel, so I googled a bit and managed to put together an XF86Config file (attached) that works quite well using the unaccelerated "radeon" driver.
Then I decided to install the latest version of the ATI 3.9.0 driver available from Suse's ftp site following instructions in the README. Driver installs successfully, however when I run "sax2 -r -m 0=fglrx -b /usr/X11R6/lib/sax/profile/firegl", the screen goes blank, then parts of the screen go white, then green, :-) , at which moment I usually kill Sax with Ctrl-Shift-Backspace, and it exists generating the attached log file. The log says a) "DRI initialization failed"; and b) there are lots of unresolved symbols. I've already fixed error messages about MTRR overlaps using instructions from http://odin.prohosting.com/wedge01/gentoo-radeon-faq.html#4_mtrroverlap.
I'd appreciate any suggestions.
These are the relevant (I think) package versions:
fglrx-3.9.0-2.1 km_fglrx-3.9.0-2.1 kernel-source-2.6.5-7.95 kernel-default-2.6.5-7.95
#lsmod | grep fglrx
If not present
#modprobe fglrx
then
#sax2 -r -m 0=fglrx -b /usr/X11R6/lib/sax/profile/fglrx
Buy the way what chipset does that run? Via, NForce/2, SiS? (it matters)
Cheers, Curtis.
Regards, Vadym
********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
- -- Spammers Beware: Tresspassers will be shot, survivors will be shot again!
Warning: Individuals throwing objects at the crocodiles will be asked to retrieve them!
If pro is the opposite of con, then the opposite of progress must be congress!
In the Ocean it's called salvage, on land it's called grave robbing! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFBDxwU7CQBg4DqqCwRAgfIAJ0UnUUq7DYrXHqViMk6ZjaPBpiT+gCeMcoP ECDkkbE4qCIwJAdtYHn3UVU= =C+gN -----END PGP SIGNATURE-----
********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue August 3 2004 01:17, Vadym Krevs wrote:
Hi Curtis,
The notebook uses Intel 855PM chipset.
I've already tried makimg sure that fglrx module is loaded before SAX2 is executed - to no avail. Because of the following warning in the XFree86 logs mtrr: 0xd0000000,0x8000000 overlaps existing 0xd0000000,0x4000000
I've executed # echo "disable=2" >/proc/mtrr # echo "base=0xd8000000 size=0x8000000 type=write-combining" >/proc/mtrr
and then, as you suggested, # lsmod | grep fglrx # modprobe -v fglrx insmod /lib/modules/2.6.5-7.95-default/kernel/drivers/char/drm/fglrx.ko # lsmod | grep fglrx fglrx 200356 0
then
#sax2 -r -m 0=fglrx -b /usr/X11R6/lib/sax/profile/fglrx
still fails and the screen shows those psychedelic colors before I kill X server.
I've tried editing my current XF86Config file to force it to load the fglrx driver (see attached file), however that did not help either - the same garbage on the screen is shown after "init 5" and then I kill the Xserver. However, as the attached XFree86 log shows, the drivers appears to have been loaded sucessfully, DRI got initialized, etc ..
Regards, Vadym
Curtis Rey wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mon August 2 2004 15:12, Vadym Krevs wrote:
Hi,
I've installed Suse 9.1 on a Dell Inspiron 8600 (with ATI Mobility Radeon 9600 PRO Turbo card and 1920x1200 laptop display panel). Sax2 wouldn't recognize the 1900x1200 panel, so I googled a bit and managed to put together an XF86Config file (attached) that works quite well using the unaccelerated "radeon" driver.
Then I decided to install the latest version of the ATI 3.9.0 driver available from Suse's ftp site following instructions in the README. Driver installs successfully, however when I run "sax2 -r -m 0=fglrx -b /usr/X11R6/lib/sax/profile/firegl", the screen goes blank, then parts of the screen go white, then green, :-) , at which moment I usually kill Sax with Ctrl-Shift-Backspace, and it exists generating the attached log file. The log says a) "DRI initialization failed"; and b) there are lots of unresolved symbols. I've already fixed error messages about MTRR overlaps using instructions from http://odin.prohosting.com/wedge01/gentoo-radeon-faq.html#4_mtrroverlap.
I'd appreciate any suggestions.
These are the relevant (I think) package versions:
fglrx-3.9.0-2.1 km_fglrx-3.9.0-2.1 kernel-source-2.6.5-7.95 kernel-default-2.6.5-7.95
#lsmod | grep fglrx
If not present
#modprobe fglrx
then
#sax2 -r -m 0=fglrx -b /usr/X11R6/lib/sax/profile/fglrx
Buy the way what chipset does that run? Via, NForce/2, SiS? (it matters)
Cheers, Curtis.
Regards, Vadym
Ok, a couple of things. First turn mtrr off in the XFconfig. My Device section is as follows, Section "Device" BoardName "RV350 AR" BusID "2:0:0" Driver "fglrx" Identifier "Device[0]" Option "no_dri" "no" Option "MonitorLayout" "AUTO" Option "mtrr" "off" Option "UseInternalAGPGART" "no" Option "DesktopSetup" "0x00000000" Option "no_accel" "no" Screen 0 Option "Rotate" "off" VendorName "ATI" EndSection What is the native res of your monitor, sax might be tripping over the res or refresh rates. Alot of these problems can often me monitor related - especially with LCDs or similar flat panel/notebooks. Seems I remember coming across some specific X settings for laptop on google. I'll see if I can't find these over the next couple of days. Google is your friend. By the way whats your XF86Config file look like, what is sax2 messages on fail? Cheers, Curtis. - -- Spammers Beware: Tresspassers will be shot, survivors will be shot again! Warning: Individuals throwing objects at the crocodiles will be asked to retrieve them! If pro is the opposite of con, then the opposite of progress must be congress! In the Ocean it's called salvage, on land it's called grave robbing! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBD1JB7CQBg4DqqCwRAmVzAJ9u9utJC+C8czX0tKp5vkcocrHhfACgqhn0 hSGwTGeoWtFWh6TXvhfM3bs= =x1Yf -----END PGP SIGNATURE-----
Curtis Rey wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tue August 3 2004 01:17, Vadym Krevs wrote:
Hi Curtis,
The notebook uses Intel 855PM chipset.
I've already tried makimg sure that fglrx module is loaded before SAX2 is executed - to no avail. Because of the following warning in the XFree86 logs mtrr: 0xd0000000,0x8000000 overlaps existing 0xd0000000,0x4000000
I've executed # echo "disable=2" >/proc/mtrr # echo "base=0xd8000000 size=0x8000000 type=write-combining" >/proc/mtrr
and then, as you suggested, # lsmod | grep fglrx # modprobe -v fglrx insmod /lib/modules/2.6.5-7.95-default/kernel/drivers/char/drm/fglrx.ko # lsmod | grep fglrx fglrx 200356 0
then
#sax2 -r -m 0=fglrx -b /usr/X11R6/lib/sax/profile/fglrx
still fails and the screen shows those psychedelic colors before I kill X server.
I've tried editing my current XF86Config file to force it to load the fglrx driver (see attached file), however that did not help either - the same garbage on the screen is shown after "init 5" and then I kill the Xserver. However, as the attached XFree86 log shows, the drivers appears to have been loaded sucessfully, DRI got initialized, etc ..
Regards, Vadym
Curtis Rey wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mon August 2 2004 15:12, Vadym Krevs wrote:
Hi,
I've installed Suse 9.1 on a Dell Inspiron 8600 (with ATI Mobility Radeon 9600 PRO Turbo card and 1920x1200 laptop display panel). Sax2 wouldn't recognize the 1900x1200 panel, so I googled a bit and managed to put together an XF86Config file (attached) that works quite well using the unaccelerated "radeon" driver.
Then I decided to install the latest version of the ATI 3.9.0 driver available from Suse's ftp site following instructions in the README. Driver installs successfully, however when I run "sax2 -r -m 0=fglrx -b /usr/X11R6/lib/sax/profile/firegl", the screen goes blank, then parts of the screen go white, then green, :-) , at which moment I usually kill Sax with Ctrl-Shift-Backspace, and it exists generating the attached log file. The log says a) "DRI initialization failed"; and b) there are lots of unresolved symbols. I've already fixed error messages about MTRR overlaps using instructions from http://odin.prohosting.com/wedge01/gentoo-radeon-faq.html#4_mtrroverlap.
I'd appreciate any suggestions.
These are the relevant (I think) package versions:
fglrx-3.9.0-2.1 km_fglrx-3.9.0-2.1 kernel-source-2.6.5-7.95 kernel-default-2.6.5-7.95
#lsmod | grep fglrx
If not present
#modprobe fglrx
then
#sax2 -r -m 0=fglrx -b /usr/X11R6/lib/sax/profile/fglrx
Buy the way what chipset does that run? Via, NForce/2, SiS? (it matters)
Cheers, Curtis.
Regards, Vadym
Ok, a couple of things. First turn mtrr off in the XFconfig. My Device section is as follows,
Section "Device" BoardName "RV350 AR" BusID "2:0:0" Driver "fglrx" Identifier "Device[0]" Option "no_dri" "no" Option "MonitorLayout" "AUTO" Option "mtrr" "off" Option "UseInternalAGPGART" "no" Option "DesktopSetup" "0x00000000" Option "no_accel" "no" Screen 0 Option "Rotate" "off" VendorName "ATI" EndSection
Done that - I still get exactly the same results as before. The only difference is that with mtrr turned off, I no longer have to manually do the same by writing into /proc/mtrr.
What is the native res of your monitor, sax might be tripping over the res or refresh rates. Alot of these problems can often me monitor related - especially with LCDs or similar flat panel/notebooks.
The native resolution is 1920x1200, and the contents of th monitor section are below: DisplaySize 330 210 HorizSync 31.5-94 Identifier "Monitor[0]" ModelName "W3866 154U1 MONITOR" Option "DPMS" VendorName "SEC" VertRefresh 50-90 UseModes "Modes[0]"
Seems I remember coming across some specific X settings for laptop on google. I'll see if I can't find these over the next couple of days. Google is your friend.
By the way whats your XF86Config file look like, what is sax2 messages on fail?
Both are attached to my previous messages.
Cheers, Curtis. - -- Spammers Beware: Tresspassers will be shot, survivors will be shot again!
Warning: Individuals throwing objects at the crocodiles will be asked to retrieve them!
If pro is the opposite of con, then the opposite of progress must be congress!
In the Ocean it's called salvage, on and it's called grave robbing! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFBD1JB7CQBg4DqqCwRAmVzAJ9u9utJC+C8czX0tKp5vkcocrHhfACgqhn0 hSGwTGeoWtFWh6TXvhfM3bs= =x1Yf -----END PGP SIGNATURE-----
********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
At last - it works now with the ATI 3.11.1 version of the driver downloaded from SuSE's ftp site. See the attached XF86Config file. I had to turn off the kernel's agpgart module in order to use the driver's module instead as described in the README. Curtis, thanks for all your help! Regargs, Vadym Vadym Krevs wrote:
Curtis Rey wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tue August 3 2004 01:17, Vadym Krevs wrote:
Hi Curtis,
The notebook uses Intel 855PM chipset.
I've already tried makimg sure that fglrx module is loaded before SAX2 is executed - to no avail. Because of the following warning in the XFree86 logs mtrr: 0xd0000000,0x8000000 overlaps existing 0xd0000000,0x4000000
I've executed # echo "disable=2" >/proc/mtrr # echo "base=0xd8000000 size=0x8000000 type=write-combining"
/proc/mtrr
and then, as you suggested, # lsmod | grep fglrx # modprobe -v fglrx insmod /lib/modules/2.6.5-7.95-default/kernel/drivers/char/drm/fglrx.ko # lsmod | grep fglrx fglrx 200356 0
then
#sax2 -r -m 0=fglrx -b /usr/X11R6/lib/sax/profile/fglrx
still fails and the screen shows those psychedelic colors before I kill X server.
I've tried editing my current XF86Config file to force it to load the fglrx driver (see attached file), however that did not help either - the same garbage on the screen is shown after "init 5" and then I kill the Xserver. However, as the attached XFree86 log shows, the drivers appears to have been loaded sucessfully, DRI got initialized, etc ..
Regards, Vadym
Curtis Rey wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mon August 2 2004 15:12, Vadym Krevs wrote:
Hi,
I've installed Suse 9.1 on a Dell Inspiron 8600 (with ATI Mobility Radeon 9600 PRO Turbo card and 1920x1200 laptop display panel). Sax2 wouldn't recognize the 1900x1200 panel, so I googled a bit and managed to put together an XF86Config file (attached) that works quite well using the unaccelerated "radeon" driver.
Then I decided to install the latest version of the ATI 3.9.0 driver available from Suse's ftp site following instructions in the README. Driver installs successfully, however when I run "sax2 -r -m 0=fglrx -b /usr/X11R6/lib/sax/profile/firegl", the screen goes blank, then parts of the screen go white, then green, :-) , at which moment I usually kill Sax with Ctrl-Shift-Backspace, and it exists generating the attached log file. The log says a) "DRI initialization failed"; and b) there are lots of unresolved symbols. I've already fixed error messages about MTRR overlaps using instructions from http://odin.prohosting.com/wedge01/gentoo-radeon-faq.html#4_mtrroverlap.
I'd appreciate any suggestions.
These are the relevant (I think) package versions:
fglrx-3.9.0-2.1 km_fglrx-3.9.0-2.1 kernel-source-2.6.5-7.95 kernel-default-2.6.5-7.95
#lsmod | grep fglrx
If not present
#modprobe fglrx
then
#sax2 -r -m 0=fglrx -b /usr/X11R6/lib/sax/profile/fglrx
Buy the way what chipset does that run? Via, NForce/2, SiS? (it matters)
Cheers, Curtis.
Regards, Vadym
Ok, a couple of things. First turn mtrr off in the XFconfig. My Device section is as follows,
Section "Device" BoardName "RV350 AR" BusID "2:0:0" Driver "fglrx" Identifier "Device[0]" Option "no_dri" "no" Option "MonitorLayout" "AUTO" Option "mtrr" "off" Option "UseInternalAGPGART" "no" Option "DesktopSetup" "0x00000000" Option "no_accel" "no" Screen 0 Option "Rotate" "off" VendorName "ATI" EndSection
Done that - I still get exactly the same results as before. The only difference is that with mtrr turned off, I no longer have to manually do the same by writing into /proc/mtrr.
What is the native res of your monitor, sax might be tripping over the res or refresh rates. Alot of these problems can often me monitor related - especially with LCDs or similar flat panel/notebooks.
The native resolution is 1920x1200, and the contents of th monitor section are below:
DisplaySize 330 210 HorizSync 31.5-94 Identifier "Monitor[0]" ModelName "W3866 154U1 MONITOR" Option "DPMS" VendorName "SEC" VertRefresh 50-90 UseModes "Modes[0]"
Seems I remember coming across some specific X settings for laptop on google. I'll see if I can't find these over the next couple of days. Google is your friend.
By the way whats your XF86Config file look like, what is sax2 messages on fail?
Both are attached to my previous messages.
Cheers, Curtis. - -- Spammers Beware: Tresspassers will be shot, survivors will be shot again!
Warning: Individuals throwing objects at the crocodiles will be asked to retrieve them!
If pro is the opposite of con, then the opposite of progress must be congress!
In the Ocean it's called salvage, on and it's called grave robbing! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFBD1JB7CQBg4DqqCwRAmVzAJ9u9utJC+C8czX0tKp5vkcocrHhfACgqhn0 hSGwTGeoWtFWh6TXvhfM3bs= =x1Yf -----END PGP SIGNATURE-----
********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Am Freitag, 6. August 2004 21:27 schrieb Vadym Krevs:
I had to turn off the kernel's agpgart module in order to use the driver's module instead
If you're using a SiS-Chipset, you may try my sis-agp patch: http://kohm.de.tf/markus/sis-agp-2004-07-08.tar.gz to use the kernel's agpgart module. -- Markus
participants (3)
-
Curtis Rey -
Markus Kohm -
Vadym Krevs