Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum. |
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
12-05-2006, 01:58 PM
|
#1
|
|
Member
Registered: Nov 2006
Location: Vancouver, BC
Distribution: Slackware
Posts: 102
Rep: 
|
System freezes when switching back to X11 (from console) while using DRI
Here's the lay of the land:
CPU: P4 2.8GHz (single core, non-hyper threaded)
RAM: 1GB
GPU: ATI Radeon X800 GTO (AGP) (ATI's proprietary driver installed)
Default xwm is Xfce 4.2.0 (stock from Slackware 11.0 distro), I have "Launch KDE Services on startup" enabled (to use konqeror and amarok). No artifacts or problems while using X, thus far at least.
The problem is when I Ctrl + Alt + F1...6 to a console everything works like it should I can switch between the 6 consoles, however when I try to Ctrl + Alt + F7 back into X the system hangs. I get a black screen and no response to keyboard commands (3 finger salute, etc...) and my monitor's info box shows this black screen is running 720x400 resolution, same as the console (X runs at 1280x1024).
I'm 99.99% certain this has something to do with DRI being enabled because I've never had this problem when it wasn't working. The only way I can continue in this situation is to do a hard reset, and does that mean any error logs won't have a change to get written?
Is this a familiar issue to anyone? at least where should I be looking?
|
|
|
|
12-05-2006, 05:22 PM
|
#2
|
|
Member
Registered: Dec 2006
Location: UNM
Distribution: Debian Lenny
Posts: 107
Rep:
|
Try disabling the proprietary driver, and using the open-source one. that solved the problem for me. And then get an nVidia card. 
|
|
|
|
12-06-2006, 11:23 PM
|
#3
|
|
Member
Registered: Nov 2006
Location: Vancouver, BC
Distribution: Slackware
Posts: 102
Original Poster
Rep: 
|
Hmm where would I find this other driver? Or which one did you mean in particular?
|
|
|
|
12-08-2006, 04:47 PM
|
#4
|
|
Member
Registered: Dec 2006
Location: UNM
Distribution: Debian Lenny
Posts: 107
Rep:
|
The other driver should have come with Xorg. Try changing the Driver entry in your xorg.conf to "ati", after removing the proprietary one.
|
|
|
|
12-10-2006, 02:47 PM
|
#5
|
|
Member
Registered: Nov 2006
Location: Vancouver, BC
Distribution: Slackware
Posts: 102
Original Poster
Rep: 
|
Hmm well I tried using "radeon" and "ati" as the device drivers, but neither one works and X, after showing a couple of warnings, defaults to use the "Standard VGA" device which obviously doesn't give me DRI... And if I comment out that device then X dies saying it can't find a working device.
"fglxr" works as a driver though... I'll stick with it for now.
Also, these changes to xorg.config don't seem to take effect until I reboot the system, is there a script that will do this?
|
|
|
|
12-11-2006, 08:55 AM
|
#6
|
|
Member
Registered: Dec 2006
Location: UNM
Distribution: Debian Lenny
Posts: 107
Rep:
|
The changes should take effect as soon as you restart X.
|
|
|
|
12-11-2006, 09:09 AM
|
#7
|
|
Guru
Registered: Oct 2005
Location: Willoughby, Ohio
Distribution: linuxdebian
Posts: 7,231
Rep: 
|
When you view your Xserver log do you see a warning similar to this ?
cat /var/log/Xorg.0.log | grep WW
Quote:
|
(WW) RADEON(0): Direct Rendering is disabled by default on Radeon VE/7000 hardware due to instability, but has been forced on with "Option "dri" in xorg.conf. You may experience instability.
|
Disable the dri module from loading and the lockups should go away..
Here is another thread where we were troubleshooting a very similar issue. commenting out dri from the Modules sections appears to have fixed the issue for this user.
Last edited by farslayer; 12-11-2006 at 09:13 AM.
|
|
|
|
12-11-2006, 02:12 PM
|
#8
|
|
Member
Registered: Nov 2006
Location: Vancouver, BC
Distribution: Slackware
Posts: 102
Original Poster
Rep: 
|
Yes that's correct if I comment out the "dri" module the problem goes away.
I also checked those 2 logs but didn't find anything suspicious, and Radeon 7000 series is a lot older than the X800 so I doubt it would be applicable.
But reading that other thread gives me an idea. The refresh rates may be incorrect for the monitor so it might be dying while trying to change video modes.
But it seems very strange that it would cause the kernel to stop responding all together, I tried pinging the computer while it's frozen and it's dead.
|
|
|
|
12-11-2006, 08:42 PM
|
#9
|
|
Member
Registered: Nov 2006
Location: Vancouver, BC
Distribution: Slackware
Posts: 102
Original Poster
Rep: 
|
Hmm no dice with the refresh rates, they were a bit off spec, however doesn't make a difference with this problem
Just a note, this happens for regular users AND root...
|
|
|
|
12-11-2006, 09:05 PM
|
#10
|
|
Guru
Registered: Oct 2005
Location: Willoughby, Ohio
Distribution: linuxdebian
Posts: 7,231
Rep: 
|
Another interesting note..
Quote:
Option "AGPFastWrite" "boolean"
Enable AGP fast write. Enabling this option is frequently the cause of instability. Used only when the DRI is enabled. The default is off.
Option "AccelMethod" "string"
Chooses between available acceleration architectures. Valid options are XAA and EXA. XAA is the traditional acceleration architecture and support for it is very stable. EXA is a newer acceleration architecture with better performance for the Render and Composite extensions, but the rendering code for it is newer and possibly unstable. The default is XAA.
Option "DMAForXv" "boolean"
Try or don't try to use DMA for Xv image transfers. This will reduce CPU usage when playing big videos like DVDs, but may cause instabilities. Default: on.
|
http://www.die.net/doc/linux/man/man4/radeon.4.html
Yes I know this man page is for the radeon driver not the proprietary one.. but its interesting how many options make the system unstable with that driver...
The Gentoo Wiki seems to have more current info on the ATI Driver and random lockups... definitely check out this link.. it's a bit more relative to your configuration.
http://gentoo-wiki.com/HOWTO_XGL:Tro...random_lockups
and
http://www.rage3d.com/board/showthread.php?p=1333981360
Best of luck to ya.. please report back if you narrow down the issue to a specific cause.
|
|
|
|
12-11-2006, 11:04 PM
|
#11
|
|
Member
Registered: Nov 2006
Location: Vancouver, BC
Distribution: Slackware
Posts: 102
Original Poster
Rep: 
|
Interesting thing... if you look at "man radeon" it says after the Radeon 9500 series (R300 chip and onward) this driver only supports 2D acceleration and this appears true.
The options for radeon driver don't appear to be used/recognised by fglrx driver, however I tried disabling AGP Fast Write in my BIOS and got a marginal improvement!
Now the resolution switches to 1280x1024 and I can see the cursor against a black screen, but other than that the system is still frozen :\
There is no man pages or any sort of manual, or at least a list of options for the fglrx driver... which sucks.
The aticonfig utility is suposed to be used for that I guess.
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 08:55 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|