| View previous topic :: View next topic |
| Author |
Message |
73H3V1LR351D3N7
n00b
Joined: 26 Apr 2006
Posts: 6
|
 Posted: Mon Aug 07, 2006 7:38 am Post subject: ati-drivers>8.24.8 random lockup issues |
 |
|
Hi there I seem to be having some random lockup issues with my Radeon Xpress R200 aswell as lockups when running any program requiring dri. This seems to happen with any set of ati-drivers newer than 8.24.8 . I think it has something to do with the deprecation of the xorg.conf Option "KernelModuleParam" "agplock=0" under the fglrx device section since I now get the following in my /var/log/messages:
| Code: |
Aug 4 12:06:40 localhost fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
Aug 4 12:06:40 localhost [fglrx] Maximum main memory to use for locked dma buffers: 552 MBytes.
Aug 4 12:06:40 localhost [fglrx] module loaded - fglrx 8.27.10 [Jul 27 2006] on minor 0
Aug 4 12:06:43 localhost [fglrx:drm_parse_option] *ERROR* "agplock" is not a valid option
Aug 4 12:06:43 localhost [fglrx] Maximum main memory to use for locked dma buffers: 552 MBytes.
Aug 4 12:06:43 localhost [fglrx] total GART = 134217728
Aug 4 12:06:43 localhost [fglrx] free GART = 118226944
Aug 4 12:06:43 localhost [fglrx] max single GART = 118226944
Aug 4 12:06:43 localhost [fglrx] total LFB = 128839680
Aug 4 12:06:43 localhost [fglrx] free LFB = 122548224
Aug 4 12:06:43 localhost [fglrx] max single LFB = 122548224
Aug 4 12:06:43 localhost [fglrx] total Inv = 0
Aug 4 12:06:43 localhost [fglrx] free Inv = 0
Aug 4 12:06:43 localhost [fglrx] max single Inv = 0
Aug 4 12:06:43 localhost [fglrx] total TIM = 0
|
graphics section in xorg.conf:
| Code: |
Section "Device"
Identifier "aticonfig-Device[0]"
Driver "fglrx"
Option "no_dri" "no"
Option "no_accel" "no"
Option "DynamicClocks" "on"
Option "mtrr" "on"
Option "DesktopSetup" "Single"
Option "ScreenOverlap" "0"
Option "Capabilities" "0x00000000"
Option "CapabilitiesEx" "0x00000000"
Option "VideoOverlay" "on"
Option "OpenGLOverlay" "off"
Option "CenterMode" "off"
Option "PseudoColorVisuals" "off"
Option "Stereo" "off"
Option "StereoSyncEnable" "1"
Option "FSAAEnable" "no"
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"
Option "KernelModuleParm" "agplock=0"
Option "PowerState" "1"
BusID "PCI:1:5:0"
EndSection
|
any suggestions as to how to set this options with the newer ati-drivers or any other leads on what the problem could be would be much appreciated. Thanks |
|
| Back to top |
|
 |
wynn
Advocate
Joined: 01 Apr 2005
Posts: 2421
Location: UK
|
| Posted: Mon Aug 07, 2006 9:48 am Post subject: |
|
|
In xorg.conf's created by 8.25.x, there is no KernelModuleParm option.
Googling, the parameter is also written "agpclock=0" 
Probably the best way forward is to save your xorg.conf and, with 8.25.10 installed, run
| Code: | | aticonfig --initial |
and then compare the saved xorg.conf with the new one and change things in the "InputDevice" and "Monitor" sections (if you think it necessary) but leave ATIs constructed "Device" section(s) alone.
_________________
The avatar is jorma, a "duck" from "Elephants Dream": the film and all the production materials have been made available under a Creative Commons Attribution 2.5 License, see orange.blender.org for details. |
|
| Back to top |
|
|
73H3V1LR351D3N7
n00b
Joined: 26 Apr 2006
Posts: 6
|
| Posted: Mon Aug 07, 2006 4:39 pm Post subject: |
|
|
Those extra options are never generated by the aticonfig even in the versions before 8.25.x.
I can assure you that I have tried many a time to use the standard device section generated by aticonfig --initial but it still gives me persistent and frequent lockups as mentioned above.
what I need is to find some sort of documentation for the fglrx module so that I can find the appropriate replacement option for the agplock=0 if one exists
as for the option being agpclock instead of agplock, that might be true but if so, its refering to a different setting since agplock seems to be much more well known among linux forum posts in general and I am sure of this option working with the <=8.24.8 drivers |
|
| Back to top |
|
|
wynn
Advocate
Joined: 01 Apr 2005
Posts: 2421
Location: UK
|
| Posted: Mon Aug 07, 2006 7:00 pm Post subject: |
|
|
Sorry, I didn't make myself clear.
The idea of using aticonfig --initial was to get rid of the "KernelModuleParam", I thought that running aticonfig from the latest drivers would give a sensible set of options. I have never seen "KernelModuleParam" and I thought it was because I have never used anything earlier than 8.25.18.
Just removing that line will remove the warning message. I hope it solves your problem too.
| Quote: | | what I need is to find some sort of documentation for the fglrx module so that I can find the appropriate replacement option for the agplock=0 if one exists |
I've looked for documentation in the files which came with the ATI installer and on their web site. There doesn't seem to be anything.
Looking again at /var/log/messages, is it reasonable (on your system) to allow up to 552 megabytes of main memory to be used for "locked dma buffers"?
_________________
The avatar is jorma, a "duck" from "Elephants Dream": the film and all the production materials have been made available under a Creative Commons Attribution 2.5 License, see orange.blender.org for details. |
|
| Back to top |
|
|
73H3V1LR351D3N7
n00b
Joined: 26 Apr 2006
Posts: 6
|
| Posted: Tue Aug 08, 2006 6:07 am Post subject: |
|
|
Yes, I know what you're saying. I know that removing that line or using the default section generated by the aticonfig will remove the error message but as I said before this does NOT solve the problem.
regarding the locked dma buffers, you might be on to something there, but I've never had problems with running out of memory before |
|
| Back to top |
|
|
wynn
Advocate
Joined: 01 Apr 2005
Posts: 2421
Location: UK
|
| Posted: Tue Aug 08, 2006 9:48 am Post subject: |
|
|
You might find ATIs "Linux Feedback Program" useful, http://apps.ati.com/linuxDfeedback/
_________________
The avatar is jorma, a "duck" from "Elephants Dream": the film and all the production materials have been made available under a Creative Commons Attribution 2.5 License, see orange.blender.org for details. |
|
| Back to top |
|
|
chrb
n00b
Joined: 23 Jun 2002
Posts: 19
|
| Posted: Tue Aug 15, 2006 9:04 pm Post subject: |
|
|
| Try setting UseFastTLS to 2 |
|
| Back to top |
|
|
|
Kernel & Hardware
