FC6 x64 ati 9600 M10 no luck (Mesa problems)

[Benjamin]

Machine is amd64 2GB Ram, ATI 9600 M (64Mb ) , FC 6

I have done what has been described and get the buildpkg Fedora/FC6 to work and get to install the drivers but whatever I do the dam thing still references the Mesa gl libs so I get no direct rendering .
can't locate anything with Mesa/mesa in it . rpm -qa |grep Mesa gives me nothing. Even doing a yum install kmod-fglrx from livna after uninstalling the control panel shows the dam mesa drivers. Are the drivers in the kernel or something? Were else can the be buried .

Here is the output from glxinfo
glxinfo
name of display: :0.0
Xlib: extension "XFree86-DRI" missing on display ":0.0".
display: :0 screen: 0
direct rendering: No
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating,
GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_OML_swap_method,
GLX_SGI_make_current_read, GLX_SGIS_multisample, GLX_SGIX_hyperpipe,
GLX_SGIX_swap_barrier, GLX_SGIX_fbconfig, GLX_MESA_copy_sub_buffer
client glx vendor string: ATI
client glx version string: 1.3
client glx extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context,
GLX_ARB_get_proc_address, GLX_SGI_video_sync, GLX_ARB_multisample,
GLX_ATI_pixel_format_float, GLX_ATI_render_texture
GLX version: 1.2
GLX extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context,
GLX_ARB_multisample
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.5.1)
OpenGL extensions:
GL_ARB_imaging, GL_ARB_multitexture, GL_ARB_texture_border_clamp,
GL_ARB_texture_cube_map, GL_ARB_texture_env_add,
GL_ARB_texture_env_combine, GL_ARB_texture_env_dot3,
GL_ARB_transpose_matrix, GL_EXT_abgr, GL_EXT_blend_color,
GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_texture_env_add,
GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3,
GL_EXT_texture_lod_bias

visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav
id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat
----------------------------------------------------------------------
0x22 24 tc 0 24 0 r y . 8 8 8 0 0 16 0 0 0 0 0 0 0 None
0x23 24 tc 0 24 0 r y . 8 8 8 0 0 16 8 16 16 16 0 0 0 None
0x24 24 tc 0 32 0 r y . 8 8 8 8 0 16 8 16 16 16 16 0 0 None
0x25 24 tc 0 32 0 r . . 8 8 8 8 0 16 8 16 16 16 16 0 0 None

Still the mesa crap .

[Michael]

What does your /var/log/X.0.lorg show when installing fglrx and trying to start X with the fglrx drivers?

Provide more information and I (and other forum users) would be more than happy to assist.

Edit: Also, the R300 Mesa drivers should support your 9600 if you wanted to use those, unless you are looking for something that is specifc to the fglrx drivers.

[Benjamin]

/dev/dri/card0 no such device

Here is the important part . I feel like the fedora installer messed up when installing FC6 because X server wouldn't even start after a fresh install( blank login screen after graphical boot) . I had to mod the xorg.conf just to get xserver to run, I feel like FC6 installer missed something. Anyway to force fedora to probe for video cards all over . I don't think reinstall will work , it will just mess up again. ( I did three fresh installs thinking I did something wrong but there is bug in bugzilla for it) . Are the drivers still screwed up or something . Mainly I want to have direct rendering enabled.
Thanks,
Ben

************************************************** *****************
************************************************** ****************
(II) fglrx(0): UMM Bus area: 0xd85e9000 (size=0x03a17000)
(II) fglrx(0): UMM area: 0xd85e9000 (size=0x03a17000)
(II) fglrx(0): driver needs X.org 7.1.x.y with x.y >= 0.0
(II) fglrx(0): detected X.org 7.1.1.0
(II) Loading extension ATIFGLRXDRI
(II) fglrx(0): doing DRIScreenInit
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
[drm] failed to load kernel module "fglrx"
(II) fglrx(0): [drm] drmOpen failed
(EE) fglrx(0): DRIScreenInit failed!
(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): ********************************************* *
************************************************** **************
************************************************** *************

[Michael]

Here is the important part . I feel like the fedora installer messed up when installing FC6 because X server wouldn't even start after a fresh install( blank login screen after graphical boot) . I had to mod the xorg.conf just to get xserver to run, I feel like FC6 installer missed something. Anyway to force fedora to probe for video cards all over . I don't think reinstall will work , it will just mess up again. ( I did three fresh installs thinking I did something wrong but there is bug in bugzilla for it) . Are the drivers still screwed up or something . Mainly I want to have direct rendering enabled.
Thanks,
Ben

************************************************** *****************
************************************************** ****************
(II) fglrx(0): UMM Bus area: 0xd85e9000 (size=0x03a17000)
(II) fglrx(0): UMM area: 0xd85e9000 (size=0x03a17000)
(II) fglrx(0): driver needs X.org 7.1.x.y with x.y >= 0.0
(II) fglrx(0): detected X.org 7.1.1.0
(II) Loading extension ATIFGLRXDRI
(II) fglrx(0): doing DRIScreenInit
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
[drm] failed to load kernel module "fglrx"
(II) fglrx(0): [drm] drmOpen failed
(EE) fglrx(0): DRIScreenInit failed!
(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): ********************************************* *
************************************************** **************
************************************************** *************

As root try running

aticonfig --initial

and then rebooting again, your X config might be messed up.

[Benjamin]

Working sorta Blank screen

Ok I have the fglrx module loading and all but when I do the disable extensions part I get a blank screen when xserver starts up . Check the log file no errors at all. Says everything is good to go .
Here is my xll config file , yes the disable extensions is missing , but if I put it in I get a blank screen . I am on a laptop.
# Xorg configuration created by pyxf86config

Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "aticonfig-Screen[0]" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Synaptics" "CorePointer"
EndSection

Section "Files"
EndSection

Section "Module"
Load "dri"
Load "glx"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Synaptics"
Driver "synaptics"
Option "Device" "/dev/input/mice"
Option "Protocol" "auto-dev"
Option "Emulate3Buttons" "yes"
EndSection

Section "Monitor"
Identifier "aticonfig-Monitor[0]"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection

Section "Device"
Identifier "Videocard0"
Driver "radeon"
EndSection

Section "Device"
Identifier "aticonfig-Device[0]"
Driver "fglrx"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

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

[Michael]

Is anything appended to the log when you get a blank screen? What happens when you try to startx manually?

[Benjamin]

Modlines maybe

I think it is related to mode lines . I googled and found similar problems on other ati cards where the fglrx driver bombs out xserver. IE the display can't handle the output thus you get a blank screen . I think I need to mod the xorg.conf file to hanve the proper mode lines. If you can point me to any other post or something that deals with the mode lines that would help . Thanks,
Ben

[Benjamin]

FC6 Fedora 6 2.6.18-1 kernel linux blank black screen

For those experiencing a blank login screen in FC6 or some other distro with ati fglrx drivers. If ssh into the machine and cpu is usage of Xorg is high or 98% or something like that there is bug in the kernel or drivers but never fear here is fix that work for me . The chipset is ATI 9600 M10 on a laptop. I had to mod the xorg config file . I install the fglrx from livna using yum install fglrx and installed the kernel module from the installer , I used a rpm produced by the installer for that. This has been noted by others a kernel bug,but I don't know exactly but here is my xorg.conf file . As long as someone has the drivers installed correctly from linva or ati installer and is experiencing blank log in screen with kernel 2.6.18-1.2798 / .fc6 2.6.18-1 . Here is two method they can try . Adjusting the AGP aperture size in their bios ( I cannot do it on my machine ) or moding the xorg config file as shown. The main part is device section . Turning the one option off ie comment it out reproduces the error. There is might be a way to ajust AGP settings from Xorg config file but I don't have time for that right now . I am working and everything is good to go for now. If it still loads the mesa drivers for opengl try looking at your Xorg.0.log file by doing
cat /var/log/X11.0.log |grep EE
if a lib file is missing try doing a locate on the lib file and making a symbolic link .

I had to add the following symbolic link ln -s /usr/X11R6/lib64/modules/dri/fglrx_dri.so /usr/lib64/dri/



************************Comment below taken from config file do not add this section to your config file but part that is important *******************************


Section "Device"
Identifier "aticonfig-Device[0]"
Driver "fglrx"
Option "DesktopSetup" "clone"
Option "BusType" "PCI" ####<<<-This is the line
EndSection
***********************************End Comment
# Xorg configuration created by system-config-display

Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "aticonfig-Screen[0]" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Synaptics" "CorePointer"
InputDevice "Mouse0" "AlwaysCore"
EndSection

Section "Files"

# Multiple FontPath entries are allowed (they are concatenated together)
# By default, a font server independent of the X server is
# used to render fonts.
FontPath "unix/:7100"
EndSection

Section "Module"
Load "dbe"
Load "extmod"
SubSection "extmod"
Option "omit xfree86-dga"
EndSubSection
Load "GLcore"
Load "fbdevhw"
Load "glx"
Load "record"
Load "freetype"
Load "type1"
Load "synaptics"
Load "dri"
EndSection

Section "InputDevice"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# To disable the XKEYBOARD extension, uncomment XkbDisable.
# Option "XkbDisable"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# Or if you just want both to be control, use:
# Option "XkbOptions" "ctrl:nocaps"
#
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "yes"
EndSection

Section "InputDevice"
Identifier "Synaptics"
Driver "synaptics"
Option "Device" "/dev/input/mice"
Option "Protocol" "auto-dev"
Option "Emulate3Buttons" "yes"
EndSection


### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:

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"
Option "DesktopSetup" "clone"
Option "BusType" "PCI"
EndSection



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


Section "DRI"
Group 0
Mode 066
EndSection

Section "Extensions"
Option "Composite" "Disable"
EndSection