Go Back   DriverHeaven > Forums > Graphics Cards > ATI Radeon Drivers > Linux Radeon Display Drivers
Register Members List Search Today's Posts Mark Forums Read

Reply
 
LinkBack Thread Tools Display Modes
Old Aug 18, 2005, 06:48 PM   #1 (permalink)
jeanoangelo
DriverHeaven Newbie
 
Join Date: Aug 2005
Posts: 2
jeanoangelo is on a distinguished road

ATI radeon xpress 200M on Suse Linux 9.3 64 pro

Hi all
I downloaded and installed the new driver fglrx64_6_8_0-8.16.20-1.x86_64.rpm in my notebook hp amd 64. Then i runned fglrxconfig and configured all with defaults options, except resolution that i setted to 1024. After that, i reboot and when the system go to start X all become black in my screen. What am I doing wrong? I tryed ati-driver-installer-8.16.20-x86_64.run too with automatic and specific mode and I got the same problem.

Thanks in advantage.

Jean
jeanoangelo is offline   Reply With Quote
Old Aug 19, 2005, 05:17 AM   #2 (permalink)
RIV@NVX
Freedom is a feature.
 
RIV@NVX's Avatar
 
Join Date: Jul 2002
Location: Croatia, Rijeka
Posts: 4,339
RIV@NVX is on a distinguished road

Have you tried editing your xorg.conf manually? Sometimes (it actually happens to me all the time) fglrxconfig generates xorg.conf file that I can't startx with.
__________________
RIV@NVX is offline   Reply With Quote
Old Aug 19, 2005, 06:42 PM   #3 (permalink)
jeanoangelo
DriverHeaven Newbie
 
Join Date: Aug 2005
Posts: 2
jeanoangelo is on a distinguished road

Thanks for your reply.
Well, what shall I look for in xorg.conf?
jeanoangelo is offline   Reply With Quote
Old Sep 8, 2005, 10:42 AM   #4 (permalink)
masanlop
DriverHeaven Newbie
 
Join Date: Jul 2005
Posts: 17
masanlop is on a distinguished road

Quote:
Originally Posted by RIV@NVX
Have you tried editing your xorg.conf manually? Sometimes (it actually happens to me all the time) fglrxconfig generates xorg.conf file that I can't startx with.
Indeed, it 's not that clear where to start looking at within xorg.conf: I also get the same
blank screen when using the conf file that worked, albeit always falling back to mesa, with the previous version of the driver.
masanlop is offline   Reply With Quote
Old Sep 9, 2005, 04:47 AM   #5 (permalink)
RIV@NVX
Freedom is a feature.
 
RIV@NVX's Avatar
 
Join Date: Jul 2002
Location: Croatia, Rijeka
Posts: 4,339
RIV@NVX is on a distinguished road

I can't be exact since I'm not sure what to look for, but you should perhaps compare original non-fglrx xorg.conf that worked (from what I understand) and the one fglrx generated.

What I always do is just use my original xorg.conf without generating it by fglrx and change the Driver (under graphics card device) from "ati" to "fglrx". You might check if it works for you.

Hope it helps a bit
__________________
RIV@NVX is offline   Reply With Quote
Old Sep 9, 2005, 12:29 PM   #6 (permalink)
masanlop
DriverHeaven Newbie
 
Join Date: Jul 2005
Posts: 17
masanlop is on a distinguished road

Quote:
Originally Posted by RIV@NVX
I can't be exact since I'm not sure what to look for, but you should perhaps compare original non-fglrx xorg.conf that worked (from what I understand) and the one fglrx generated.

What I always do is just use my original xorg.conf without generating it by fglrx and change the Driver (under graphics card device) from "ati" to "fglrx". You might check if it works for you.

Hope it helps a bit
Unfortunately it didn't work. That's exactly what I meant: I used an xorg.conf file that wasn't giving problems, but I got this blank screen when switching to the new driver. Note that, albeit
not giving "problems" with the older version of fglrx, it wasn't really working either because
I couldn't get 3D working.

The point is that I get the same blank screen when using the xorg.conf generated by fglrxinfo.
masanlop is offline   Reply With Quote
Old Sep 10, 2005, 05:26 AM   #7 (permalink)
RIV@NVX
Freedom is a feature.
 
RIV@NVX's Avatar
 
Join Date: Jul 2002
Location: Croatia, Rijeka
Posts: 4,339
RIV@NVX is on a distinguished road

Perhaps it's a bug in new driver then (I haven't tried so I can't say).
You can probably get 3D working with older drivers using these instructions.
__________________
RIV@NVX is offline   Reply With Quote
Old Nov 9, 2005, 06:14 PM   #8 (permalink)
masanlop
DriverHeaven Newbie
 
Join Date: Jul 2005
Posts: 17
masanlop is on a distinguished road

Quote:
Originally Posted by RIV@NVX
Perhaps it's a bug in new driver then (I haven't tried so I can't say).
You can probably get 3D working with older drivers using these instructions.
Did anyone have any success in getting the Xpress200M working -including 3D ?? It would be great if you could share it, specially if you have a HP/Compaq laptop that comes with that card and the AMD64 cpu.

In my case it installs ok, but when starting X system I get a blank screen, the cpu gets at full throtle and there is no response to any key...

Thanks in advance,
MA
masanlop is offline   Reply With Quote
Old Nov 11, 2005, 09:02 PM   #9 (permalink)
masanlop
DriverHeaven Newbie
 
Join Date: Jul 2005
Posts: 17
masanlop is on a distinguished road

Ok, I've tested the two lastest drivers 8.18.8 and 8.19.10 .

I have a Compaq Presario R400 with AMD64 3200, Xpress200M and Suse9.3 pro,
and kernel 2.6.11.4-21.9-default. Up to now, I did not succeed in getting 3D working
with any driver.

Here I post what I think may be a minimal xorg.conf file. The key is in loading modules
glx and/or dri. If loading both, DRI initializes completely and ok, but I get a blank screen,
no access to any console, and the only thing a may do is using CTRL+ALT+DEL to put the
laptop in kind of a shutdown state -or suspend state, as power led keeps lighting. If
loading only one of both modules, I get 2D acceleration and I can use my laptop but DRI
fails to initialize and thus have no 3D.

In addition I show a vimdiff result of both Xorg.0.log files between using only glx and
using both modules, annotating the difference when using each of the two lastest ATI drivers .

I hope this may help someone in either pointing me to a solution or finding out why it
happens...maybe any of ATI friends here around...rgregori ?

Any way, I really would appreciate your comments.

Thanks in advance,
MA

xorg.conf:
***********
# /.../
# Minimal xorg.xconf for getting at least 2D accel with Xpress200M
# on a Compaq Presario R4000
#

Section "DRI"
Group "video"
Mode 0666
EndSection

Section "Module"
# Combining following both modules makes
# DRI to get correctly initialize but the
# X server does not load => BLANK SCREEN,
# and keyboard does not respond but to crtl+alt+del
# starting kind of a shutdown or suspend, as power led
# remains lighting.
# Disabling one or both, gives
# ONLY 2D accel., but not 3D -DRI fails to initialize.
Load "glx"
# Load "dri"
EndSection

Section "InputDevice"
Driver "kbd"
Identifier "Keyboard[0]"
Option "Protocol" "Standard"
Option "XkbLayout" "us,bg,es"
Option "XkbModel" "pc104"
Option "XkbRules" "xorg"
Option "XkbVariant" "xfree86"
EndSection

Section "InputDevice"
Driver "synaptics"
Identifier "Mouse[1]"
Option "Device" "/dev/input/mice"
Option "Name" "SynPS/2 Synaptics TouchPad"
Option "Protocol" "explorerps/2"
Option "Buttons" "5"
Option "InputFashion" "Mouse"
Option "ZAxisMapping" "4 5"
Option "Vendor" "Sysp"
EndSection

Section "InputDevice"
Driver "mouse"
Identifier "Mouse[3]"
Option "Buttons" "7"
Option "Device" "/dev/input/mice"
Option "InputFashion" "Mouse"
Option "Name" "USB-Mouse;ExplorerPS/2 on USB"
Option "Protocol" "ExplorerPS/2"
Option "ZAxisMapping" "4 5"
EndSection

Section "Monitor"
DisplaySize 330 210
HorizSync 30-82
Identifier "Monitor[0]"
ModelName "JMN4A1P060590 MONITOR"
Option "DPMS"
VendorName "QDS"
VertRefresh 43-75
UseModes "Modes[0]"
EndSection

Section "Modes"
Identifier "Modes[0]"
Modeline "1280x800" 71.00 1280 1328 1360 1440 800 802 808 823 +csync
Modeline "1024x768" 71.00 1024 1200 1232 1440 768 786 792 823
Modeline "800x600" 71.00 800 1088 1120 1440 600 702 708 823
EndSection

Section "Screen"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "Modes[0]"
EndSubSection
Device "Device[0]"
Identifier "Screen[0]"
Monitor "Monitor[0]"
EndSection

Section "Device"
BoardName "ATI Graphics Adapter"
BusID "1:5:0"
Driver "fglrx"
Identifier "Device[0]"
Screen 0
EndSection

Section "ServerLayout"
Identifier "Layout[all]"
InputDevice "Keyboard[0]" "CoreKeyboard"
InputDevice "Mouse[1]" "CorePointer"
InputDevice "Mouse[3]" "SendCoreEvents"
Screen "Screen[0]"
EndSection
************************************************** *************************************

Following is a vimdiff result comparing the Xorg.0.logs when using only module glx,
left of the `|' and when loading both modules, right of symbol `|'. When appropriate,
different results between both drivers are stated. The same result is obtained whe
using the xorg.conf generated with `aticonf --initial'.

************************************************** *******************************************
For ATI drivers 8.18.8 and 8.19.10 here is a
vimdiff of Xorg.0.log for xorg.conf using...
only glx => NO 3Daccel | both glx and dri => Blank screen & no keyboard access.
************************************************** *******************************************
--------------------------------------------------------| (II) LoadModule: "dri"
--------------------------------------------------------| (II) Loading /usr/X11R6/lib64/modules/extensions/libdri.a
--------------------------------------------------------| (II) Module dri: vendor="X.Org Foundation"
--------------------------------------------------------| compiled for 6.8.2, module version = 1.0.0
--------------------------------------------------------| ABI class: X.Org Server Extension, version 0.2
--------------------------------------------------------| (II) Loading sub module "drm"
--------------------------------------------------------| (II) LoadModule: "drm"
--------------------------------------------------------| (II) Loading /usr/X11R6/lib64/modules/linux/libdrm.a
--------------------------------------------------------| (II) Module drm: vendor="X.Org Foundation"
--------------------------------------------------------| compiled for 6.8.2, module version = 1.0.0
--------------------------------------------------------| ABI class: X.Org Server Extension, version 0.2
--------------------------------------------------------| (II) Loading extension XFree86-DRI

************************************************** **********************************************
for driver 8.18.8 ...

(II) fglrx(0): pEnt->device->identifier=0x717e80 | (II) fglrx(0): pEnt->device->identifier=0x717df0

************

for driver 8.18.9 ...
(II) fglrx(0): pEnt->device->identifier=0x717e80 | (II) fglrx(0): pEnt->device->identifier=0x717ea0
************************************************** **********************************************

************************************************** **********************************************
Only for driver 8.18.8...

(II) fglrx(0): VESA VBE Total Mem: 131072 kB | (II) fglrx(0): VESA VBE Total Mem: 528384 kB

(==) fglrx(0): cpuSpeedMHz: 0x000003e5 | (==) fglrx(0): cpuSpeedMHz: 0x000007ca

*****************

For driver 8.19.10 in both (xorg.conf) cases...

(II) fglrx(0): VESA VBE Total Mem: 528384 kB

(==) fglrx(0): cpuSpeedMHz: 0x000007ca

But for both drivers in both (xorg.conf) cases...

(II) fglrx(0): VESA BIOS detected
(II) fglrx(0): VESA VBE Version 2.0
(II) fglrx(0): VESA VBE OEM: ATI MOBILITY RADEON Xpress 200G Series
(II) fglrx(0): VESA VBE OEM Software Rev: 1.0
(II) fglrx(0): VESA VBE OEM Vendor: ATI Technologies Inc.
(II) fglrx(0): VESA VBE OEM Product: MS48
(II) fglrx(0): VESA VBE OEM Product Rev: 01.00
************************************************** ********************************************

************************************************** ********************************************
Only for driver 8.19.10...

(II) Loading /usr/X11R6/lib64/modules/linux/libdrm.a | (II) Reloading /usr/X11R6/lib64/modules/linux/libdrm.a

(II) Module drm: vendor="X.Org Foundation" | ---------------------------------------------------------------------------
compiled for 6.8.2, module version = 1.0.0 | ---------------------------------------------------------------------------
ABI class: X.Org Server Extension, version 0.2 | ---------------------------------------------------------------------------
drmOpenDevice: node name is /dev/dri/card0 | drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (Unknown error 999) | drmOpenDevice: open result is 6, (OK)
drmOpenDevice: open result is -1, (Unknown error 999) | ---------------------------------------------------------------------------
drmOpenDevice: Open failed | --------------------------------------------------------------
************************************************** **************************************



(WW) fglrx(0): ******************************************| (II) Loading extension ATIFGLRXDRI
(WW) fglrx(0): * DRI initialization failed! | (II) fglrx(0): doing DRIScreenInit
(WW) fglrx(0): * (maybe driver kernel module missing or b| drmOpenDevice: node name is /dev/dri/card0
(WW) fglrx(0): * 2D acceleraton available (MMIO) |
(WW) fglrx(0): * no 3D acceleration available |
(WW) fglrx(0): ******************************************|


(II) fglrx(0): Largest offscreen area available: 1280 x 7387 | Largest offscreen area available: 1280 x 402




Solid Horizontal and Vertical Lines | 8x8 mono pattern filled rectangles
---------------------------------------------------------| Solid Lines
---------------------------------------------------------| Dashed Lines
Offscreen Pixmaps | Offscreen Pixmaps
Setting up tile and stipple cache: | Setting up tile and stipple cache:
32 128x128 slots | 30 128x128 slots
32 256x256 slots | -------------------------------------------------
16 512x512 slots | -------------------------------------------------
(II) fglrx(0): Acceleration enabled | (II) fglrx(0): Acceleration enabled
(II) fglrx(0): Direct rendering disabled | (II) fglrx(0): X context handle = 0x00000001
(II) Loading extension FGLRXEXTENSION | (II) fglrx(0): [DRI] installation complete
(II) Loading extension ATITVOUT |
(==) RandR enabled | NOTHING MORE GETS WRITTEN BEYOND THIS POINT
. | IN THIS CASE
. |
.
Symbol DRIGetDeviceInfo from module /usr/X11R6/lib64/modules/drivers/fglrx_| -------------------------------
Symbol DRIGetDrawableInfo from module /usr/X11R6/lib64/modules/drivers/fglr| ----------------------------
(II) Setting vga for screen 0. | ---------------------------
(II) Initializing built-in extension MIT-SHM | --------------------------
(II) Initializing built-in extension XInputExtension | -------------------------
(II) Initializing built-in extension XTEST | ------------------------
(II) Initializing built-in extension XKEYBOARD | -----------------------
(II) Initializing built-in extension LBX | ----------------------
(II) Initializing built-in extension XC-APPGROUP | ---------------------
(II) Initializing built-in extension SECURITY | --------------------
(II) Initializing built-in extension XINERAMA | -------------------
(II) Initializing built-in extension XFIXES | ------------------
(II) Initializing built-in extension XFree86-Bigfont | -----------------
(II) Initializing built-in extension RENDER | ----------------
(II) Initializing built-in extension RANDR | ---------------
(II) Initializing built-in extension COMPOSITE | --------------
(II) Initializing built-in extension DAMAGE | -------------
(II) Initializing built-in extension XEVIE | ------------
(**) Option "CoreKeyboard" | -----------
(**) Keyboard[0]: Core Keyboard | ----------
(**) Option "Protocol" "Standard" | ---------
(**) Keyboard[0]: Protocol: Standard | --------
(**) Option "AutoRepeat" "500 30" | -------
.
.
.
masanlop is offline   Reply With Quote
Old Nov 12, 2005, 01:01 AM   #10 (permalink)
jec0s
DriverHeaven Junior Member
 
Join Date: Feb 2005
Posts: 45
jec0s is on a distinguished road

Have you ran 32bit, or a distro other than Suse? Could be an issue with Suse 64bit, there was one with dri on Ubuntu 64bit that got fixed...

Install 32bit. Your losing tons of apps just to run in a 64bit environment that is not noticably faster than 32bit by any means!

Last edited by jec0s : Nov 12, 2005 at 01:14 AM.
jec0s is offline   Reply With Quote
Reply



Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On




 

 
Powered by: vBulletin
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
LinkBacks Enabled by vBSEO 3.1.0
Artwork by Allan 'Zardon' Campbell, vBulletin implementation by Craig '5320' Humphreys based on original artwork by Ratchet.

All times are GMT -5. The time now is 08:57 PM. Copyright ©2008 DriverHeaven.net