3D working but now it won't shutdown or log off

toasty_ghosty · 09-25-2007, 11:09 AM

Hello.
I just got my 3D acceleration working. It wasn't as hard as I had thought. But I've had a weird aftereffect. Since then, whenever I shutdown or log off, my screen shuts down. Almost like I'm stopping using the ATI drivers. And I know thats what should happen when your computer shuts down, but the rest of my computer is staying on. Weird. The only change I made what to get my 3D working, which is working quite nicely I might add. But I would like to be able to shutdown my computer. Any Ideas? Thanks.

dracolich · 09-25-2007, 02:44 PM

What ATI card is it and which driver did you install? Are you using any other hardware and drivers that might cause a conflict (ndiswrapper, for example)? Which windows manager are you using? I recently had an experience after switching from KDE to Fluxbox and when using ndiswrapper I would have a similar problem on a laptop that uses xorg's ati driver. With KDE it never happened and upgrading ndiswrapper to 1.47 fixed it.

toasty_ghosty · 09-25-2007, 03:03 PM

I have an ATI X850XT. I was using the current ATI drivers from their website. I don't using ndiswrapper or anything like that as it on a desktop. And as a X manager I am using Fluxbox as well.

toasty_ghosty · 09-25-2007, 06:57 PM

I have uninstalled the ATI drivers and so I can now shutdown my PC, but if I could fix this it would be nice as I would like to have 3d acceleration. Any ideas?

T3slider · 09-25-2007, 08:30 PM

Are you starting in runlevel 3 (ie you boot to a command prompt)? If so, when you exit X, it is possible that there is a problem with the framebuffer. Try changing /etc/lilo.conf to use the "vga = normal" video driver instead of a framebuffer (ie comment out whatever is currently being used [put a # before the only uncommented line vga=???] and uncomment "vga = normal" [by removing the # in front of it]). Then run lilo as root (and reboot).

Note that this is only one possibility -- I may be way off here. I'm just guessing that when X exits it doesn't restore the framebuffer properly. Using the standard (though ugly) console display may fix it.

toasty_ghosty · 09-25-2007, 09:42 PM

Here is /etc/lilo.conf. This is what it looked like. I haven't changed a thing...

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/sda
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset

# Normal VGA console
vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda1
label = Linux
read-only
# Linux bootable partition config ends

toasty_ghosty · 09-25-2007, 10:12 PM

Another thing I just found out. When I do glxgears I get this:

theking@slackware:~$ glxgears
FGLTexMgr: open of shared memory object failed (Permission denied)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
FGLTexMgr: open of shared memory object failed (Permission denied)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
FGLTexMgr: open of shared memory object failed (Permission denied)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
FGLTexMgr: open of shared memory object failed (Permission denied)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
FGLTexMgr: open of shared memory object failed (Permission denied)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
FGLTexMgr: open of shared memory object failed (Permission denied)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
FGLTexMgr: open of shared memory object failed (Permission denied)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
FGLTexMgr: open of shared memory object failed (Permission denied)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
FGLTexMgr: open of shared memory object failed (Permission denied)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
FGLTexMgr: open of shared memory object failed (Permission denied)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
FGLTexMgr: open of shared memory object failed (Permission denied)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
FGLTexMgr: open of shared memory object failed (Permission denied)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
FGLTexMgr: open of shared memory object failed (Permission denied)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
FGLTexMgr: open of shared memory object failed (Permission denied)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
FGLTexMgr: open of shared memory object failed (Permission denied)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
47691 frames in 5.0 seconds = 9538.166 FPS

It starts to give me FPS readings though, but not before I get all the permission denied's. That and when I run something such as bzflag I get some more permission denieds and it is almost like I do not have 3D rendering by the way the screen looks. And something I just now found out is when I went to KUser I got this error:

Error opening /etc/shadow for reading.

Any ideas. I would really like to continue to use Linux but this is beginning to be a huge pain and I have reinstalled about 3 times when running into graphic driver issues.

toasty_ghosty · 09-26-2007, 01:17 PM

I am already had those changes when I opened up that text file. So any ideas anyone? I feel like I'm slowly killing my PC every time I have to basically pull the plug.

dracolich · 09-26-2007, 02:30 PM

Have you tried the ati and/or radeon drivers provided with Xorg? I'm not familiar with your card model so I don't know if they'll work with it. Also, have you tried KDE instead of Fluxbox? Personally, I love Fluxbox but sometimes it helps to try a different window manager for troubleshooting.

The "permission denied" errors and your comment about bzflag sounds like your user is not a member of the video group. Make sure it is (and the audio group while you're at it). For KUser, did you have root permissions when trying to use it?

toasty_ghosty · 09-26-2007, 06:22 PM

I used the default radeon drivers (I think) when I first installed Slack, but I could not get 3D acceleration. So I had to use these.

toasty_ghosty · 09-27-2007, 02:40 PM

I really like Slackware, but I think I may try another distro. Not Ubuntu or anything but maybe something Slackware deprived. But then again, when it is setup it will be worth it.

T3slider · 09-28-2007, 09:40 PM

ATI drivers have always spelled trouble. They are now open-sourcing their drivers, so hopefully they will improve in time, but they have some issues at the moment. You would have to do some searching around the forums for ATI drivers or something to solve your problem (I have an nVidia card and therefore am of little help to you). Of course, switching to another distro is always an option if you want, but don't make it specifically because of the video card issue which can be solved. (If you want to switch go for it, however)

gnashley · 09-29-2007, 03:52 AM

"Slackware deprived" -that's really funny!

toasty_ghosty · 09-29-2007, 04:57 PM

To be honest, I really like Slackware and the ideas that it implies. Also, switching distros will be just a temporary solution as they will also have their issues. That and if anything is going to have issues it is going to be ATI drivers as we all know how good they currently are. So I think that I may just have to live without 3D acceleration as of now and wait for some new drivers.