ati and xorg 6.8.2

Message

Brain Fury · Post by **Brain Fury** » Tue Feb 22, 2005 9:54 pm

I updated my xorg to version 6.8.2 and now xorg tells me that there is no fglrx module.
Is the driver not compatible to 6.8.2? Should I downgrade?

Wedge_ · Post by **Wedge_** » Tue Feb 22, 2005 10:13 pm

The drivers should work fine. Did you also upgrade your kernel recently? If you did, you will need to emerge the drivers again to get a new fglrx module compiled for the new kernel.

Brain Fury · Post by **Brain Fury** » Wed Feb 23, 2005 9:00 pm

i updated my kernel, i remerged ati-drivers, didn't work

Wedge_ · Post by **Wedge_** » Wed Feb 23, 2005 10:24 pm

When you run emerge ati-drivers, watch the output carefully for compilation errors. If you're running a new or heavily patched kernel, it's quite likely the driver will fail to compile without extra patches being applied.

Jengu · Post by **Jengu** » Wed Feb 23, 2005 10:29 pm

Everytime your kernel changes you need to re-emerge the drivers because they're compiled for the specific kernel you're running. Are you sure you re-emerge'd them after changing your kernel? When you updated your kernel did you update the symbolic link /usr/src/linux to point to the folder for the kernel you're actually using first?

float- · Post by **float-** » Wed Feb 23, 2005 10:38 pm

a good idea could be to check your symlink to /usr/src/linux

StUiT · Post by **StUiT** » Wed Feb 23, 2005 10:46 pm

Hi, I had the same problem on my amd64 xorg-6.8.2 installation, when I downgraded to the previous version, the driver loaded correctly..

Sander

Brain Fury · Post by **Brain Fury** » Thu Feb 24, 2005 8:47 am

okay, here is what i did

I updated to xorg 6.8.2 - The driver didn't work
I remerged ati-drivers - didn' work
I updated the kernel (from gentoo-dev-sources 2.6.10-r2 to -r7) and after that remerged ati-drivers - didn't work

it seems that I have to downgrade

Wedge_ · Post by **Wedge_** » Thu Feb 24, 2005 10:34 am

What do you mean when you say they didn't work? Can you load the fglrx module? What errors are you getting in your /var/log/Xorg.0.log?

Brain Fury · Post by **Brain Fury** » Thu Feb 24, 2005 6:58 pm

modprobe fglrx works fine but when I want to start X it says that the module cannot be loaded

Unfortunetaly i can't post the error log at the moment because i am on another computer right now

JackDog · Post by **JackDog** » Thu Feb 24, 2005 7:09 pm

Check if the fglrx modules is built by using modprobe. If it cant find it, its either not built for your running kernel or not in the modules directory. If the module loads and Xorg doesnt use it, then you have another problem.

My guess is it either built against the wrong kernel (/usr/src/linux is linked wrong) or it didnt actually build it. Some kernels, notably mm-sources do not always work as a target kernel for the ati-drivers. Next time you do an emerge, look at the text and see if there is an error. My experience has been that sometimes the emerge "works" but the module was never built because of a problem linking against the target kernel.

Do an lsmod to see if the module is actually loaded. check dmesg to see if it ops'd.

If you want to downgrade go for it. But I know for a fact the 9500Pro and 9800Pro work just fine with 6.8.2.

Wedge_ · Post by **Wedge_** » Thu Feb 24, 2005 7:41 pm

Brain Fury wrote:modprobe fglrx works fine but when I want to start X it says that the module cannot be loaded

Unfortunetaly i can't post the error log at the moment because i am on another computer right now

OK, that means that emerge ati-drivers is doing what it should do. If you can post your /var/log/Xorg.0.log when you get a chance that would be helpful.

infirit · Post by **infirit** » Thu Feb 24, 2005 9:31 pm

I having the same issue with amd64 + ati-drivers 8.x + xorg 6.8.2. Xorg.0.log is at this link.

Thanks.

Wedge_ · Post by **Wedge_** » Thu Feb 24, 2005 10:04 pm

If this is actually an AMD64-only problem I can't help much, I don't know a lot about the differences in how things are setup on AMD64 systems compared to x86. If it is AMD64-only, try posting in the AMD64 forum here instead. It looks like the fglrx driver modules are either in the wrong place or just not there, but I don't know where they're supposed to be on an AMD64 system in the first place

Brain Fury · Post by **Brain Fury** » Fri Feb 25, 2005 5:53 pm

since 1 have an amd64 as well i think this could really be an arch-related problem..

could some mod please move this thread?

StUiT · Post by **StUiT** » Fri Feb 25, 2005 6:57 pm

Actually, if you search in the AMD64 you'll find a 22-paged thread about ati drivers coming out in December.
There are some posts about this subject.. There has been a bug report for it, I read somewhere..

Jengu · Post by **Jengu** » Fri Feb 25, 2005 7:10 pm

Brain Fury wrote:okay, here is what i did

I updated to xorg 6.8.2 - The driver didn't work
I remerged ati-drivers - didn' work
I updated the kernel (from gentoo-dev-sources 2.6.10-r2 to -r7) and after that remerged ati-drivers - didn't work

it seems that I have to downgrade

Did you check the /usr/src/linux symlink yet? And the order should be to re-emerge ati-drivers _after_ changing your kernel like you did the last time, just so you know.

mope · Post by **mope** » Fri Feb 25, 2005 8:26 pm

I have the same problem and I am not using AMD64. I am on a 2100+ and 9800pro, so it doesn't seem to be the architeture. I am having the same problem with fglrx and it only occurred after I read on the forums that 6.8.2 was redone to correct an error or something. It was working before I re-emerged 6.8.2, now x won't start.

Brain Fury · Post by **Brain Fury** » Fri Feb 25, 2005 11:57 pm

Jengu wrote:Did you check the /usr/src/linux symlink yet?

yes I did

geaaru · Post by **geaaru** » Sat Feb 26, 2005 12:11 am

Well, or not!?! I installed new ati-drivers, but I had a lot of problems.
I have 6.8.2 and a Radeon 9000 128mb; I use a 2.4.x kernel because I have a Raid chip (Highpoint 372) not supported in 2.6.x., so I also installed x11-drm driver (as FAQ find). After that I installed ati drivers I see that its don't work well, so I uninstall all. When I restart system and I installed xorg drivers I see that my system goes in panic if I use DRI. If I remove "Load dri" from xorg.conf file, X is ok.
I can't use dri with xorg driver because system goes in panic. Then, if I try to run Windows, I can't use nothing. Only run Windows in VGA mode.
I think that my video card is ko.
Hence, if you have a radeon 9000 128mb with kernel 2.4.x, you don't install ati driver because is dangerous for your video card.

Bye.

P.S. I very angry for this bad bad driver:evil: !

MrIch · Post by **MrIch** » Sat Feb 26, 2005 11:42 am

hello,

I have exactly the same problem... dmesg says module is loaded wihtout problems...

but xorg does not start

Code: Select all


fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
[fglrx] Maximum main memory to use for locked dma buffers: 919 MBytes.
ACPI: PCI interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 169
[fglrx] module loaded - fglrx 8.10.19 [Feb  9 2005] on minor 0

------------

(II) Loading extension GLX
(II) LoadModule: "dri"
(II) Loading /usr/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/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
(II) LoadModule: "fglrx"
(WW) Warning, couldn't open module fglrx
(II) UnloadModule: "fglrx"
(EE) Failed to load module "fglrx" (module does not exist, 0)
(II) LoadModule: "mouse"
(II) Loading /usr/lib64/modules/input/mouse_drv.o
(II) Module mouse: vendor="X.Org Foundation"
        compiled for 6.8.2, module version = 1.0.0
        Module class: X.Org XInput Driver
        ABI class: X.Org XInput driver, version 0.4
(II) LoadModule: "kbd"
(II) Loading /usr/lib64/modules/input/kbd_drv.o
(II) Module kbd: vendor="X.Org Foundation"
        compiled for 6.8.2, module version = 1.0.0
        Module class: X.Org XInput Driver
        ABI class: X.Org XInput driver, version 0.4
(EE) No drivers available.

Fatal server error:
no screens found

Please consult the The X.Org Foundation support
         at http://wiki.X.Org
 for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.

Wedge_ · Post by **Wedge_** » Sat Feb 26, 2005 1:12 pm

geaaru wrote:Well, or not!?! I installed new ati-drivers, but I had a lot of problems.
I have 6.8.2 and a Radeon 9000 128mb; I use a 2.4.x kernel because I have a Raid chip (Highpoint 372) not supported in 2.6.x.,

The HPT372 is definitely supported is 2.6, I have a board with the same controller. Try upgrading before you do anything else. You should just need to enable "Device drivers -> ATA/ATAPI/MFM/RLL support -> HPT36X/37X chipset support" in the kernel config.

infirit · Post by **infirit** » Sat Feb 26, 2005 3:36 pm

Ok the problem is that xorg-6.8.2 makes a mess of the /usr/lib64 symlink to /usr/lib for at least amd64 users.
It overwrites the synlink and makes it a "normal' directory. See this post on how i solved it.

I do not know if this bug is also affecting non amd64 users.

Sebell · Post by **Sebell** » Sat Feb 26, 2005 5:04 pm

Please see the following link -> the issue with glx locking the box hard has been solved by
1)

Code: Select all

 emerge --unmerge -C xorg-x11 opengl-update ati-drivers ati-drivers-extra

2) validate kernel sources link in /usr/src
(i.e. /usr/src/linux points to the kernel that the host will run concurrent with the X install)
3) rm -rf /usr/lib/modules/ <- this did NOT get cleaned out by the unmerge above, and DOES NOT get properly overwritten if something is using one of those files -- I dont know for sure what was using them last time make damn sure its /usr/lib /modules yer deleting.)

http://forums.gentoo.org/viewtopic-t-22 ... ight-.html

Now for where I am :

Xorg.0.log reports Direct Rendering Enabled, with both radeon (xorg-x11 driver) and fglrx (ati-driver)
dri section is set 666 and the permissions are correct on /dev/dri/card0
Again... *something* is locking the box up hard. AND neither root nor users can get glxinfo to believe that opengl, direct rendering and glx are enabled. Attempting to use a glx app will lock the box up hard, but its far less consistent.

I have a really silly question for everyone out there -- which version of libGL gets used at WHAT stage of the process.

interesting point --- after running opengl-update ati :

Code: Select all

lrwxrwxrwx  1 root root 36 Feb 24 22:00 /usr/lib/libGL.a -> /usr/lib/opengl/xorg-x11/lib/libGL.a
-rw-r--r--  1 root root 741 Feb 26 11:16 /usr/lib/libGL.la
lrwxrwxrwx  1 root root 32 Feb 26 11:16 /usr/lib/libGL.so -> /usr/lib/opengl/ati/lib/libGL.so

lrwxrwxrwx  1 root root 12 Feb 23 19:58 /usr/lib/opengl/ati/lib/libGL.so.1 -> libGL.so.1.2
-rwxr-xr-x  1 root root 798730 Feb 23 19:58 /usr/lib/opengl/ati/lib/libGL.so.1.2
-rw-r--r--  1 root root 756 Feb 23 19:58 /usr/lib/opengl/ati/lib/libGL.la
lrwxrwxrwx  1 root root 12 Feb 23 19:58 /usr/lib/opengl/ati/lib/libGL.so -> libGL.so.1.2

lrwxrwxrwx  1 root root 12 Feb 23 19:55 /usr/lib/opengl/xorg-x11/lib/libGL.so.1 -> libGL.so.1.2
-rw-r--r--  1 root root 688966 Feb 23 19:55 /usr/lib/opengl/xorg-x11/lib/libGL.a
-rwxr-xr-x  1 root root 587834 Feb 23 19:55 /usr/lib/opengl/xorg-x11/lib/libGL.so.1.2
-rw-r--r--  1 root root 763 Feb 23 19:55 /usr/lib/opengl/xorg-x11/lib/libGL.la
lrwxrwxrwx  1 root root 12 Feb 23 19:55 /usr/lib/opengl/xorg-x11/lib/libGL.so -> libGL.so.1.2

I have to wonder where libGL.la in /usr/lib came from -- I believe that it comes out of opengl-update rebuilding the library or something. -- I have to ask -- why are we building libraries on the fly instead of simply moving softlinks around? Seems to me that code consistency being what it is it would be wiser to build it once and simply flip the softlink between installations... --- the issue then is that the downstream code that compiles against that static library has to be completely rebuilt every time ... ouch.

Modules:

Code: Select all

 
Module                 Size       Used by
fglrx                 237724        7
ehci_hcd             30664        0
amd_k7_agp        6156         1
agpgart              28916        2 fglrx,amd_k7_agp

xorg.conf fglrx options:

Code: Select all

    Option "no_accel"                   "no"
    Option "no_dri"                     "no"
    Option "DesktopSetup"               "0x00000000"
    Option "MonitorLayout"              "AUTO, AUTO"
    Option "IgnoreEDID"                 "off"
    Option "HSync2"                     "unspecified"
    Option "VRefresh2"                  "unspecified"
    Option "ScreenOverlap"              "0"
    Option "NoTV"                       "yes"
    Option "TVStandard"                 "NTSC-M"
    Option "TVHSizeAdj"                 "0"
    Option "TVVSizeAdj"                 "0"
    Option "TVHPosAdj"                  "0"
    Option "TVVPosAdj"                  "0"
    Option "TVHStartAdj"                "0"
    Option "TVColorAdj"                 "0"
    Option "GammaCorrectionI"           "0x06419064"
    Option "GammaCorrectionII"          "0x00000000"
    Option "Capabilities"               "0x00000000"
    Option "VideoOverlay"               "on"
    Option "OpenGLOverlay"              "off"
    Option "CenterMode"                 "off"
    Option "PseudoColorVisuals"         "off"
    Option "Stereo"                     "off"
    Option "StereoSyncEnable"           "1"
    Option "FSAAEnable"                 "yes"
    Option "FSAAScale"                  "1"
    Option "FSAADisableGamma"           "no"
    Option "FSAACustomizeMSPos"         "no"
    Option "FSAAMSPosX0"                "0.000000"
    Option "FSAAMSPosY0"                "0.000000"
    Option "FSAAMSPosX1"                "0.000000"
    Option "FSAAMSPosY1"                "0.000000"
    Option "FSAAMSPosX2"                "0.000000"
    Option "FSAAMSPosY2"                "0.000000"
    Option "FSAAMSPosX3"                "0.000000"
    Option "FSAAMSPosY3"                "0.000000"
    Option "FSAAMSPosX4"                "0.000000"
    Option "FSAAMSPosY4"                "0.000000"
    Option "FSAAMSPosX5"                "0.000000"
    Option "FSAAMSPosY5"                "0.000000"
    Option "UseFastTLS"                 "0"
    Option "BlockSignalsOnLock"         "on"
    Option "UseInternalAGPGART"         "no"
    Option "ForceGenericCPU"            "no"

Output from Xorg.0.log

Code: Select all

       ABI class: X.Org Font Renderer, version 0.4
(II) fglrx(0): Direct rendering enabled

output from glxinfo:

Code: Select all

@ajftl1 ~ $ glxinfo
name of display: :0.0
display: :0  screen: 0
direct rendering: No
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:

device:

Code: Select all

ls -l /dev/dri
total 0
crw-rw-rw-  1 root root 226, 0 Feb 26 11:17 card0

I'm gonna have to hurt somone, or something, likely myself or the computer to get past this...

geaaru · Post by **geaaru** » Sat Feb 26, 2005 6:11 pm

Wedge_ wrote: The HPT372 is definitely supported is 2.6, I have a board with the same controller. Try upgrading before you do anything else. You should just need to enable "Device drivers -> ATA/ATAPI/MFM/RLL support -> HPT36X/37X chipset support" in the kernel config.

First: Sorry for OT!
But Is it supported with Raid in Stripping and ad unique hardisk?Because, when I had try with kernel 2.6.x, the system find HPT372, but not the stripping. However, I try....

While, for Radeon I think that problems are with motherboard, because if I mount video card in other computer it works.
However, also in this case I try.... and say you!
Thanks for your response!!!
Good Gentoo!!!