I've got an older HP Pavilion dv8000 laptop with ATI Radeon XPRESS 200M 5955 video. This worked fine out-of-the-box with 13.1. With 13.37 I can't get KDE desktop effects to work, glxgears reports about 50 fps, and the system can suspend but not resume. I have no xorg.conf at all. Here is the glxinfo and current Xorg log. Any pearls of wisdom of where to look next would be appreciated.

Just to note, this is with Slackware64 13.37 with the multilib stuff installed.

Attached Files

	Xorg.0.log (70.7 KB, 30 views)
	glxinfo.txt (23.4 KB, 31 views)

Well, I got the desktop effects to work . . . once. After that the next person who logs into KDE will have the splash screen freeze, although the computer doesn't actually lock up. The mouse pointer still moves and the login music plays. It's just that the screen otherwise remains frozen there. When you restart X, the desktop effects don't work anymore. The only entry in the Xorg log that seemed to be any different was this one:

[ 1988.009] (II) AIGLX: Suspending AIGLX clients for VT switch

Not sure what that means. Hope this helps. Resume doesn't work regardless.

Well, the "good" news is that I tested the laptop with a live CD of Kubuntu 11.04 and it shows the same behavior. 3D seems to work tolerably because I was able to play Quake Live with a decent framerate (albeit with an annoying amount of artifacts). Disabling the desktop effects doesn't seem to be the worst thing in the world as it speeds KDE up quite a bit.

I still would like to get the machine to suspend and resume. It's not mission-critical because the laptop doesn't really go anyplace, but it is causing an unnecessary drain of battery power.

OK, I still haven't figured out the desktop effects, but I have figured out the suspend/resume problem. I had to add this kernel parameter to the "append" line in my lilo.conf:

Now it works. I'm going to do some further tests to make sure that I didn't mess anything else up.

1 members found this post helpful.

That line make Quake Live into something less than a slideshow. It will also cause X to segfault when a new user logs in for the first time.

I've been searching for threads related to this problem as my "thing" is restoring older laptops and putting them back into use...with Slackware of course... I can confirm that this works on this Compaq Presario V5000 which has the ATI Radeon XPRESS 200M 5955 video chip. I was unable to replicate marmold's comment about segfaulting.
BTW this older "obsolete" laptop runs _very well_ with slack64 -current and all of alienbob's multilib's giving me access to skype, Virtualbox, FirstClass email etc...

radeon requires KMS for direct rendering to work, so if you're going to disable it you may as well go for the proprietary fglrx driver as well which generally has better suspend/resume and 3D support than the foss driver stack.

But doesn't support either the_penguinator or marnold's GPUs.

Adam

Correct - for some reason I thought that one was newer than it was, but it's the RS480, they dropped support for those old chipsets along with the rest of X series and earlier.

First off.. you should create a xorg.conf file. If you haven't done so by now I suggest doing so.

This could solve even parts of the modesetting issue on boot. X11 can automatically detect what video card you have, but don't second guess yourself that skipping a configuration step is helping you out any. Configure your X server properly and you have less issues with it.

As far as the rest of the issues... have you tried installing a package from SlackBuilds called "driconf"? This it out and it should help with some of the issues if you set up your video card through it.

did that as you suggested with xorgsetup...machine reverted to previous behaviour of not coming back from suspend

did that too...no change to failure to come out of suspend and in addition, GoogleEarth failed to start
did $rm ~/.drirc
and GoogleEarth now starts, but machine still doesn't come back from suspend so for now I'll go back to marnold's original kludge...at least it works

may try the proprietary driver...or not
cheers

Question... but this may seem a silly question, but I better ask it...

Are you using the AMD Turion 64 model DV8000Z or the Intel Core Duo model DV8000T?