PDA

View Full Version : Fedora 9 and ATI


klaus
06-18-2008, 04:31 PM
has anybody installed ATI driver on fedora 9?
I have tried, neither catalyst 8.5, not 8.6 runs succesfully, after installation and reboot, the driver does not load and gdm won't start. Radeon Mobility X1400. The problem is fglrx.so cant find a symbol anywhere

What's wrong? anybody has clue?

austin17
06-19-2008, 01:38 AM
has anybody installed ATI driver on fedora 9?
I have tried, neither catalyst 8.5, not 8.6 runs succesfully, after installation and reboot, the driver does not load and gdm won't start. Radeon Mobility X1400. The problem is fglrx.so cant find a symbol anywhere

What's wrong? anybody has clue?


We have the same experience... My X crashed just now because the failure of 8.6... I only wait for Livna (not develpoment or testing) to save me :( what else can we do ?

klaus
06-19-2008, 05:45 AM
Based on googling, I've found that X-Server in Fedora 9 is so new that even ATI catalyst does not support it. But Why? Fedora 9 came just soon after catalyst 8.5, and now, with release of 8.6, IT IS NOT STILL SUPPORTED. What is ATI doing? I'm really in need of hardware acceleration because of my work, and now, nothing...

adamk
06-19-2008, 05:49 AM
It's not just that the xserver is so new, it's that the xserver is a version that hasn't been officially released. While it would be nice if AMD could support it, I don't think it's fair to expect them to support an unreleased version of the Xserver.

Adam

klaus
06-19-2008, 05:55 AM
Then this means that ATI probably won't put the support in their catalyst, till the official release of the X-Server? Is it true?

adamk
06-19-2008, 06:34 AM
I'm not from AMD, so I can't say what they will and won't do. However, it wouldn't surprise me if they waited till xserver 1.5.0 is released.

Adam

NeoBrain
06-19-2008, 09:04 AM
I'd even guess they'll need more time that just until the release of xserver 1.5, because they'll need to use a complete different driver architecture which will take a few months (especially if you add the time the support needs to stabilize)

bridgman
06-19-2008, 09:56 AM
In general we are aiming the open source drivers at upstream distros with as-yet-unreleased subsystems, and the closed source drivers more at the downstream distros, but I do think you will see earlier support of new kernels and X servers in the future.

klaus
06-19-2008, 10:09 AM
Anybody knows what is the status of open source drivers for ATI products?
In Fedora 9, default driver is the radeon, which only supports (main) display detection, not any acceleration of anykind. RadeonHD is not on any mirrors that I have browsed, and i think it does not support features of the new Fedora (Since if it was, there was somewhere link to its fedora 9 package)
Anybody got any news?

austin17
06-19-2008, 10:26 AM
Sorry to hear that.But I think if you're in real need of acceleration ,you may have to be back to Fedora 8,for ATI's good performance on it... FC9 turned me down seriously... I cannot wait any longer~

bridgman
06-19-2008, 10:28 AM
I was pretty sure the radeon (xf86-video-ati) driver in F9 had full acceleration support for everything up to 5xx and RS690, including XAA, EXA, Textured Video and 3D. You'll need to pull the latest upgrades to get full 5xx though.

If anyone is seeing worse behaviour on F9 than F8 for ATI graphics please sing out with some details either here or (even better) the normal Fedora channels. I know airlied worked hard to get the 5xx 3D into Fedora and I'm *pretty* sure it was into F9 via post-release updates, not 100% sure though.

6xx acceleration should start to show up soon but is not in any driver today (other than shadowFB). We have released the instruction set info for the shader core already ( http://www.x.org/docs/AMD/ - r600isa.pdf) and are trying to get the remaining register & setup info out the door now.

austin17
06-19-2008, 10:46 AM
I was pretty sure the radeon (xf86-video-ati) driver in F9 had full acceleration support for everything up to 5xx and RS690, including XAA, EXA, Textured Video and 3D. You'll need to pull the latest upgrades to get full 5xx though.



You may misunderstood my minds, I mean it so difficult to install a perfect video driver for my X1400 Mobility~~

so I have to use the default driver,readon, I cannot spek highly of it... Do you have a better way to solve this problem ? Thanks...

bridgman
06-19-2008, 10:52 AM
Not sure I understand what you mean by "perfect driver" -- are you talking open source or proprietary ? Today the radeon driver (supposedly the one in the latest F9 upgrades) has complete support for the 5xx parts.

Not sure if the 3D drivers include the IDs for your specific chip, but that is just a question of what equipment the developers have on hand for testing.

What problems are you having with the radeon driver, and which driver are you trying to install in its place ?

austin17
06-19-2008, 11:09 AM
Not sure I understand what you mean by "perfect driver" -- are you talking open source or proprietary ? Today the radeon driver (supposedly the one in the latest F9 upgrades) has complete support for the 5xx parts.

Not sure if the 3D drivers include the IDs for your specific chip, but that is just a question of what equipment the developers have on hand for testing.

What problems are you having with the radeon driver, and which driver are you trying to install in its place ?


The result is simple... X server crashed after I installed AMD official ATI 8.6 driver. The driver is downloaded from ati.amd.com .

I basically followed the common steps to install it, and it seemed to be installed, but actually it failed. When I reboot my laptop, X server
crashed. So I have to uninstall what I just installed~~

That is the case. Do you have any advices?

bridgman
06-19-2008, 11:16 AM
Catalyst 8.6 does not support Fedora 9 as far as I know.

The radeon driver (a different, open source driver) is included with the Fedora 9 distribution. Have you tried running the radeon driver at all ?

Again, radeon is *not* the same as Catalyst (aka fglrx). Radeon is an open source driver, also known as xf86-video-ati. For a full 3d stack you need :

- radeon or radeonhd (xf86-video-radeonhd)
- kernel driver (mesa/drm)
- 3d driver (mesa/mesa)

If you fully uninstall the 8.6 Catalyst driver then re-install the radeon/drm/mesa driver which shipped with Fedora 9 you should run fine, although you will need the latest updates for full 3D.

austin17
06-19-2008, 11:29 AM
Catalyst 8.6 does not support Fedora 9 as far as I know.

The radeon driver (a different, open source driver) is included with the Fedora 9 distribution. Have you tried running the radeon driver at all ?

Again, radeon is *not* the same as Catalyst (aka fglrx). Radeon is an open source driver, also known as xf86-video-ati. For a full 3d stack you need :

- radeon or radeonhd (xf86-video-radeonhd)
- kernel driver (mesa/drm)
- 3d driver (mesa/mesa)

If you fully uninstall the 8.6 Catalyst driver then re-install the radeon/drm/mesa driver which shipped with Fedora 9 you should run fine, although you will need the latest updates for full 3D.


Thank you. Do you mean the latest version of readon driver support FC9's
gnome 3D desktop effect and hardware acceleration? I am a greener in this aspect indeed~

NeoBrain
06-19-2008, 12:10 PM
By the way, you can use the binary fglrx driver on Fedora 9 with enabled 3D accel when you downgrade your X Server, there's a guide on the Fedora forums about that.
depending on the kernel, you may also need to downgrade the kernel or patch the driver.
http://forums.fedoraforum.org/showthread.php?t=188645
It's about the nvidia driver but can easily applied to fglrx I think.

Christian_L
06-19-2008, 04:27 PM
By the way, you can use the binary fglrx driver on Fedora 9 with enabled 3D accel when you downgrade your X Server, there's a guide on the Fedora forums about that.
depending on the kernel, you may also need to downgrade the kernel or patch the driver.
http://forums.fedoraforum.org/showthread.php?t=188645
It's about the nvidia driver but can easily applied to fglrx I think.

Here's my experience: I did not need to patch the kernel, but yes, I had to downgrade the X server to get fglrx 8.5 running with Fedora 9 on my Mobility X1400 Laptop. Runs fine now, will try out 8.6 soon.

bradycl_84043
06-19-2008, 09:08 PM
Wow. A whole 'nother month?

Actually, Fedora 9 was released well *before* 8.5. I was waiting just as anxiously for that release a month ago.

:(

NeoBrain
06-20-2008, 08:58 AM
Wow. A whole 'nother month?

Actually, Fedora 9 was released well *before* 8.5. I was waiting just as anxiously for that release a month ago.

:(

As i said, it's not about the "distro release" but the new X server, and especially the new DRI 2. It isn't that easy to just code a new DRI driver on the fly, so we'll need to wait a bit more that another month I guess.

EDIT: Oh well, I am not that sure anymore, if DRI 2 is already part of Xorg 7.4/Xserver 1.5, can anyone clarify?

jwhowarth
06-20-2008, 10:20 AM
Is there any updated information yet on when X.org will actually release 7.4? I suspect we may never see the new 1.5 xserver support
in the fglrx driver until that actually happens.

klaus
06-22-2008, 02:51 PM
My basic problem: According to Mr. Bridgman, now radeon driver should almost do the work for me, so here is the glxinfo to get the problem:

libGL: XF86DRIGetClientDriverName: 5.3.0 r300 (screen 0)
libGL: OpenDriver: trying /usr/lib/dri/r300_dri.so
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenByBusid: Searching for BusID pci:0000:01:00.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenByBusid: drmOpenMinor returns 8
drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
unknown chip id 0x7145, can't guess.
libGL error: InitDriver failed
libGL error: reverting to (slow) indirect rendering
name of display: :0.0
display: :0 screen: 0
direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose)
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: SGI
client glx version string: 1.4
client glx extensions:
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context,
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_allocate_memory,
GLX_MESA_copy_sub_buffer, GLX_MESA_swap_control,
GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_OML_sync_control,
GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync,
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap
GLX version: 1.2
GLX extensions:
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context,
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer,
GLX_OML_swap_method, GLX_SGI_make_current_read, GLX_SGIS_multisample,
GLX_SGIX_fbconfig, GLX_EXT_texture_from_pixmap
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.4 (2.1 Mesa 7.1)
OpenGL extensions:
GL_ARB_depth_texture, GL_ARB_draw_buffers, GL_ARB_fragment_program,
GL_ARB_fragment_program_shadow, GL_ARB_imaging, GL_ARB_multisample,
GL_ARB_multitexture, GL_ARB_occlusion_query, GL_ARB_point_parameters,
GL_ARB_point_sprite, GL_ARB_shadow, GL_ARB_shadow_ambient,
GL_ARB_texture_border_clamp, GL_ARB_texture_compression,
GL_ARB_texture_cube_map, GL_ARB_texture_env_add,
GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar,
GL_ARB_texture_env_dot3, GL_ARB_texture_mirrored_repeat,
GL_ARB_texture_non_power_of_two, GL_ARB_texture_rectangle,
GL_ARB_transpose_matrix, GL_ARB_vertex_program, GL_ARB_window_pos,
GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color,
GL_EXT_blend_equation_separate, GL_EXT_blend_func_separate,
GL_EXT_blend_logic_op, GL_EXT_blend_minmax, GL_EXT_blend_subtract,
GL_EXT_clip_volume_hint, GL_EXT_copy_texture, GL_EXT_draw_range_elements,
GL_EXT_fog_coord, GL_EXT_framebuffer_object, GL_EXT_multi_draw_arrays,
GL_EXT_packed_pixels, GL_EXT_paletted_texture, GL_EXT_point_parameters,
GL_EXT_polygon_offset, GL_EXT_rescale_normal, GL_EXT_secondary_color,
GL_EXT_separate_specular_color, GL_EXT_shadow_funcs,
GL_EXT_shared_texture_palette, GL_EXT_stencil_wrap, GL_EXT_subtexture,
GL_EXT_texture, GL_EXT_texture3D, GL_EXT_texture_edge_clamp,
GL_EXT_texture_env_add, GL_EXT_texture_env_combine,
GL_EXT_texture_env_dot3, GL_EXT_texture_lod_bias,
GL_EXT_texture_mirror_clamp, GL_EXT_texture_object,
GL_EXT_texture_rectangle, GL_EXT_vertex_array, GL_APPLE_packed_pixels,
GL_ATI_draw_buffers, GL_ATI_texture_env_combine3,
GL_ATI_texture_mirror_once, GL_ATIX_texture_env_combine3,
GL_IBM_texture_mirrored_repeat, GL_INGR_blend_func_separate,
GL_MESA_pack_invert, GL_MESA_ycbcr_texture, GL_NV_blend_square,
GL_NV_fragment_program, GL_NV_light_max_exponent, GL_NV_point_sprite,
GL_NV_texgen_reflection, GL_NV_texture_rectangle, GL_NV_vertex_program,
GL_NV_vertex_program1_1, GL_SGI_color_matrix, GL_SGI_color_table,
GL_SGIS_generate_mipmap, GL_SGIS_texture_border_clamp,
GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod, GL_SGIX_depth_texture,
GL_SGIX_shadow, GL_SGIX_shadow_ambient, GL_SUN_multi_draw_arrays

3 GLX Visuals
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
----------------------------------------------------------------------
0x21 24 tc 1 24 0 r y . 8 8 8 0 0 24 8 0 0 0 0 0 0 None
0x22 24 dc 1 24 0 r y . 8 8 8 0 0 24 8 0 0 0 0 0 0 None
0x54 32 tc 1 24 0 r . . 8 8 8 0 0 0 0 0 0 0 0 0 0 None

24 GLXFBConfigs:
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
----------------------------------------------------------------------
0x55 0 tc 1 24 0 r y . 8 8 8 0 0 0 0 0 0 0 0 0 0 None
0x56 0 tc 1 24 0 r y . 8 8 8 0 0 0 8 0 0 0 0 0 0 None
0x57 0 tc 1 24 0 r y . 8 8 8 0 0 24 0 0 0 0 0 0 0 None
0x58 0 tc 1 24 0 r y . 8 8 8 0 0 24 8 0 0 0 0 0 0 None
0x59 0 tc 1 24 0 r . . 8 8 8 0 0 0 0 0 0 0 0 0 0 None
0x5a 0 tc 1 24 0 r . . 8 8 8 0 0 0 8 0 0 0 0 0 0 None
0x5b 0 tc 1 24 0 r . . 8 8 8 0 0 24 0 0 0 0 0 0 0 None
0x5c 0 tc 1 24 0 r . . 8 8 8 0 0 24 8 0 0 0 0 0 0 None
0x5d 0 dc 1 24 0 r y . 8 8 8 0 0 0 0 0 0 0 0 0 0 None
0x5e 0 dc 1 24 0 r y . 8 8 8 0 0 0 8 0 0 0 0 0 0 None
0x5f 0 dc 1 24 0 r y . 8 8 8 0 0 24 0 0 0 0 0 0 0 None
0x60 0 dc 1 24 0 r y . 8 8 8 0 0 24 8 0 0 0 0 0 0 None
0x61 0 dc 1 24 0 r . . 8 8 8 0 0 0 0 0 0 0 0 0 0 None
0x62 0 dc 1 24 0 r . . 8 8 8 0 0 0 8 0 0 0 0 0 0 None
0x63 0 dc 1 24 0 r . . 8 8 8 0 0 24 0 0 0 0 0 0 0 None
0x64 0 dc 1 24 0 r . . 8 8 8 0 0 24 8 0 0 0 0 0 0 None
0x65 0 tc 1 32 0 r y . 8 8 8 0 0 0 0 0 0 0 0 0 0 None
0x66 0 tc 1 32 0 r y . 8 8 8 0 0 0 8 0 0 0 0 0 0 None
0x67 0 tc 1 32 0 r y . 8 8 8 0 0 32 0 0 0 0 0 0 0 None
0x68 0 tc 1 32 0 r y . 8 8 8 0 0 32 8 0 0 0 0 0 0 None
0x69 0 tc 1 32 0 r . . 8 8 8 0 0 0 0 0 0 0 0 0 0 None
0x6a 0 tc 1 32 0 r . . 8 8 8 0 0 0 8 0 0 0 0 0 0 None
0x6b 0 tc 1 32 0 r . . 8 8 8 0 0 32 0 0 0 0 0 0 0 None
0x6c 0 tc 1 32 0 r . . 8 8 8 0 0 32 8 0 0 0 0 0 0 None

klaus
06-22-2008, 02:54 PM
Forgot to say, the card is ATI radeon X1400, and system is a dell inspiron 6400.
What may be the problem? Is it a not-ready feature or sth like that for the driver, or there is problem with my setup? I think that may solve the problem.
Thanks in advance

adamk
06-22-2008, 03:33 PM
Fedora 9 was released before Mesa supported your card, so unless there's been an update to Mesa, Fedora does not yet support 3D acceleration on your card, just 2D.

Adam

Alex W. Jackson
06-22-2008, 03:39 PM
AFAIK, r500 3d support was pushed into Updates for F9. klaus, have you fully updated your system? (including "enhancement updates", which is what r500 3d would fall under)

bridgman
06-22-2008, 08:30 PM
I saw a reference to "updates-testing". I haven't played with Fedora enough to know the difference between "updates" and "updates-testing" but as of a week ago I think you needed "updates-testing".

klaus
06-23-2008, 09:04 AM
I update my system using yumex, not default update routines. I had fully updated 4 days ago, and again i'll update again in some hours time. I hope that would help. I'm really in need for hardware acceleration...

Thanks everyone

By the way, fedora updates before being released by community testers, meaning that some updates would be released in updates-testing repository and be tested, after test pass, it will be released in updates repository.

gylee
06-24-2008, 12:50 AM
I just upgraded my notebook to Fedora 9 x86_64 (64 bit). The system is a MacBookPro with X1600. Using RPMs from the official repository (+ updates-testing), I finally managed to get Compiz Fusion working correctly with radeon driver. My many thanks to all of you who make this possible.

However, I have a problem in using an external monitor. The MBP connector is a DVI one. If I use a DVI-DVI connection, then everything is working OK. However, if I use an analog VGA connector by using the provided DVI-VGA converter, I get no signal on the external monitor, as if it is not connected. This is what I have from xrandr.


Screen 0: minimum 320 x 200, current 1440 x 900, maximum 1600 x 1600
LVDS connected 1440x900+0+0 (normal left inverted right x axis y axis) 331mm x 207mm
1440x900 60.0*+
1360x768 59.8
1152x864 60.0
1024x768 60.0
800x600 60.3
640x480 59.9
S-video disconnected (normal left inverted right x axis y axis)
DVI-1 connected 1440x900+0+0 (normal left inverted right x axis y axis) 408mm x 255mm
1440x900 59.9*+ 75.0 59.9
1600x1024 60.2
1400x1050 60.0
1280x1024 75.0 72.0 60.0 60.0
1280x960 60.0
1360x768 59.8
1152x864 75.0 75.0 75.0 70.0 60.0
1024x768 75.1 75.0 70.1 60.0
832x624 74.6
800x600 72.2 75.0 60.3 56.2
640x480 75.0 72.8 72.8 75.0 66.7 60.0 59.9
720x400 70.1
640x350 70.1
DVI-0 disconnected (normal left inverted right x axis y axis)



Out of curiosity, I rebuild the radeonhd RPM from the "development" repository, since the provided RPM is for Fedora 10. Using this driver, everything is working OK again, even though xrandr shows different naming of the outputs.


Screen 0: minimum 320 x 200, current 1440 x 900, maximum 2560 x 2560
PANEL connected 1440x900+0+0 331mm x 207mm
1440x900 60.0*+ 59.9
2560x2048Scaled 60.5
2560x1600Scaled 60.5
2048x1536 60.0
2048x1536Scaled 60.5
1920x1440 60.0
1856x1392 60.0
1792x1344 60.0
1920x1200Scaled 60.4
1920x1080Scaled 60.5
1600x1200 60.0
1600x1200Scaled 60.4
1680x1050 60.0
1680x1050Scaled 60.3
1600x1024 60.2
1400x1050 60.0
1400x1050Scaled 60.3
1440x960Scaled 60.4
1280x1024 60.0
1280x1024Scaled 60.5
1280x960 60.0
1280x960Scaled 60.4
1280x854Scaled 60.4
1360x768 59.8
1152x864 60.0
1280x720Scaled 60.4
1152x768Scaled 60.3
1024x768 60.0
1024x768Scaled 60.4
800x600 60.3 56.2
800x600Scaled 60.3
768x576Scaled 60.4
854x480Scaled 59.8
720x480Scaled 59.8
640x480 59.9
640x480Scaled 60.1
320x240Scaled 57.6
320x200Scaled 55.7
DVI-I_1/analog connected 1440x900+0+0 408mm x 255mm
1440x900 59.9*+ 74.9 59.9
1400x1050 60.0
1280x1024 75.9 75.0 71.9 59.9 60.0
1280x960 60.0
1360x768 59.8
1152x864 75.0 75.0 74.9 70.0 60.0
1024x768 75.1 75.0 70.1 60.0
832x624 74.6
800x600 72.2 75.0 60.3 56.2
640x480 75.0 72.8 72.8 75.0 66.7 60.0 59.9
720x400 70.1
640x350 70.1
DVI-I_1/digital disconnected


Is there any specific setup to make it work with radeon?

My current xorg.conf is:


Section "ServerLayout"
Identifier "single head configuration"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection

Section "Files"

EndSection

Section "Module"
Load "synaptics"
Load "dbe"
Load "glx"
Load "dri"
Load "extmod"
EndSection

Section "ServerFlags"
Option "AIGLX" "on"
EndSection

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

Section "InputDevice"

# Synaptics Touchpad:
Identifier "Mouse0"
Driver "synaptics"
#Option "CorePointer"
Option "Device" "/dev/input/mouse1"
Option "SendCoreEvents" "true"
Option "Protocol" "auto-dev"

# not using edge scrolling
Option "HorizEdgeScroll" "0"
Option "VertEdgeScroll" "0"

# use two finger scrolling
Option "VertTwoFingerScroll" "1"
Option "HorizTwoFingerScroll" "1" # set to 0 if you don't want horizontal scrolling

# scroll speed, lower is faster
Option "HorizScrollDelta" "10"
Option "VertScrollDelta" "10"

# minimum pressure motion factor
Option "PressureMotionMinZ" "10"

# touch and untouch thresholds, higher numbers if you like to push hard
Option "FingerLow" "10"
Option "FingerHigh" "20" # change to 30 or 40 if you like

# borders based on output from synclient
Option "LeftEdge" "20"
Option "RightEdge" "1200"
Option "TopEdge" "20"
Option "BottomEdge" "370"

# speeds, smaller number for a slower mouse
Option "MinSpeed" "0.8" # 0.5 is very slow, 1.5 is very fast
Option "MaxSpeed" "1.2" # up to 1.5 works ok
Option "AccelFactor" "0.10"

# tap times, change to suit your tapping habits
Option "MaxTapMove" "100"
Option "MaxTapTime" "100"
Option "MaxDoubleTapTime" "200"

# don't change these or two finger tap stops working
Option "TapButton2" "3"
Option "TapButton3" "2"

# must be commented out or normal tapping wont work
#Option "TapButton1" "0"

# needed for disabled while typing fix
Option "SHMConfig" "on"
EndSection

Section "Modes"

# 1440x900 @ 60.00 Hz (GTF) hsync: 55.92 kHz; pclk: 106.47 MHz
Identifier "Mode0"
ModeLine "1440x900" 96.3 1440 1504 1536 1760 900 903 906 912 -hsync +vsync
EndSection

Section "Modes"

# 1440x900 @ 60.00 Hz (GTF) hsync: 55.92 kHz; pclk: 106.47 MHz
Identifier "Mode1"
ModeLine "1440x900" 136.5 1440 1536 1688 1936 900 901 904 940 -hsync +vsync
#ModeLine "1440x900" 106.5 1440 1520 1672 1904 900 901 904 932 -hsync +vsync
EndSection

Section "Monitor"

# HorizSync 31.5 - 48.5
# VertRefresh 40.0 - 70.0
#UseModes "Mode0"
#Option "PreferredMode" "Mode0"
Identifier "Monitor0"
ModelName "Panel"
#HorizSync 31.0 - 81.0
#VertRefresh 50.0 - 76.0
#Option "dpms"
EndSection

Section "Monitor"

#UseModes "Mode1"
#Option "PreferredMode" "Mode1"
Identifier "aticonfig-Monitor[1]"
HorizSync 31.0 - 81.0
VertRefresh 50.0 - 76.0
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
#Option "DPMS" "true"
EndSection

Section "Device"

Identifier "Videocard0"
Driver "radeon"
Option "AccelMethod" "EXA"
#Option "AccelMethod" "ShadowFB"
#Option "DRI"
BusID "PCI:1:0:0"
EndSection

Section "Device"
Identifier "aticonfig-Device[1]"
Driver "radeon"
Option "AccelMethod" "EXA"
#Option "AccelMethod" "ShadowFB"
#Option "DRI"
BusID "PCI:1:0:0"
Screen 1
EndSection

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1440x900" "1152x864" "1024x768" "800x600"
EndSubSection
EndSection

Section "Screen"
Identifier "aticonfig-Screen[1]"
Device "aticonfig-Device[1]"
Monitor "aticonfig-Monitor[1]"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1440x900" "1280x1024" "1280x800" "1152x864" "1024x768" "800x600"
EndSubSection
EndSection

Section "Extensions"
Option "XVideo" "true"
EndSection

janl
06-24-2008, 07:22 AM
Bridgeman is correct. In Fedora 9 you'll currently need to enable the updates-testing repository to pull in RadeonHD and the needed updates.

You can do this on a temporary basis by simply usingsu -
yum --enablerepo=updates-testing install xorg-x11-drv-radeonhd
yum --enablerepo=updates-testing update

You'll then want to change your /etc/X11/xorg.conf file to use the radeonhd driver

klaus
06-24-2008, 05:31 PM
I have completely updated my system, but even the problem exists:

drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
unknown chip id 0x7145, can't guess.
libGL error: InitDriver failed
libGL error: reverting to (slow) indirect rendering

What's the problem? I have no clue
I have tested even reinstalling mesa and radeon and radeonhd drivers, but no difference...

bridgman
06-24-2008, 05:36 PM
Either drm or mesa may simply not have your chip ID added yet. Give me a minute...

OK, 0x7145 is in mesa (added May 2nd) so you may still have older code for some reason. Is there a version number printed for mesa ?

klaus
06-25-2008, 10:17 AM
At last! Thanks bridgeman! I checked my mesa installation, and that was the latest from 'updates' repository. I enabled 'updates-testing' and updated mesa, which finally led me to have driect rendering according to glxinfo. Now I can resume my project development, which was in a stage which really needed that. My CPU was not able to render the whole scene independently. Of course I have not the rendering speed of fglrx, but for now it is good. For sure after a while when the driver is completed, rendering speed would reach the speed of fglrx.

But there is a slight problem: Having compiz enabled and running my project, it seems that the two 3d applications (compiz, the window manager and my project) are having problems for displaying themselves. My project's window will be on top, and never goes back. The frame which is handled by window decorator does not have any problems, that means that only 3d viewports have the problems.
Another thing that makes me wonder, is that in fusion-icon (I use that for enabling compiz), indirect rendering option is selected and disabled, meaning that it is not changeable, and rendering for compiz is indirect. Although compiz runs smoothly and has no problem. What is that about?

Again thanks for helping other guys, all the members of the forum

hubick
07-08-2008, 02:45 PM
So, I have Fedora 9 running with fglrx using the X.org from Fedora 8 and the following:

akmod-fglrx-8.493-1.8.05.lvn9.x86_64
kmod-fglrx-2.6.25.4-30.fc9.x86_64-8.493-1.8.05.fc9.x86_64
xorg-x11-drv-fglrx-libs-8.493-1.8.05.lvn9.x86_64
kmod-fglrx-2.6.25.3-18.fc9.x86_64-8.493-1.8.05.fc9.x86_64
kmod-fglrx-8.493-1.8.05.lvn9.x86_64
xorg-x11-drv-fglrx-8.493-1.8.05.lvn9.x86_64

But if I try to do a yum update it now gives me the following:
Error: Missing Dependency: kernel-uname-r = 2.6.25.6-55.fc9.x86_64 is needed by package kmod-fglrx-2.6.25.6-55.fc9.x86_64-8.501-1.8.06.lvn9.x86_64 (livna-testing)

Anyone else seeing this? Does anyone have any information on how this new akmod and kernel-uname-r package stuff works?

SanjayPethe
07-08-2008, 11:49 PM
So, I have Fedora 9 running with fglrx using the X.org from Fedora 8 and the following:

akmod-fglrx-8.493-1.8.05.lvn9.x86_64
kmod-fglrx-2.6.25.4-30.fc9.x86_64-8.493-1.8.05.fc9.x86_64
xorg-x11-drv-fglrx-libs-8.493-1.8.05.lvn9.x86_64
kmod-fglrx-2.6.25.3-18.fc9.x86_64-8.493-1.8.05.fc9.x86_64
kmod-fglrx-8.493-1.8.05.lvn9.x86_64
xorg-x11-drv-fglrx-8.493-1.8.05.lvn9.x86_64

But if I try to do a yum update it now gives me the following:
Error: Missing Dependency: kernel-uname-r = 2.6.25.6-55.fc9.x86_64 is needed by package kmod-fglrx-2.6.25.6-55.fc9.x86_64-8.501-1.8.06.lvn9.x86_64 (livna-testing)

Anyone else seeing this? Does anyone have any information on how this new akmod and kernel-uname-r package stuff works?

See this link for information on akmods:
http://fedorasolved.org/Members/zcat/akmods