[SOLVED]Xorg vs Gentoo-Dev-Sources vs ATI:freeze on shutdown

shazow · Last edited by shazow on Wed Dec 29, 2004 12:40 pm; edited 2 times in total

Greetings again.
Off to my issue of the season:

In short, when I shutdown from Xorg (running KDE 3.3), it seems it logs out and everything, and then just when it gets to the console part where it would normally start unloading modules, unmount drives, and all that fun, it freezes. The second Xorg is gone, my screen fills with a bunch of repeated ASCII characters. (Usually either |'s or ASCII blocks, tiled on my entire screen) And there's no response from keyboard or anything, so it's a hard lock.

Now, the suspect. This only seems to happen with gentoo-dev-sources*. I've been using mm-sources for a while, and it was fine (this was the reason I switched to mm-sources). But I need gentoo-dev-sources for now (see footnote marked *).

Finally, my gentoo specs:
- (kernel) gentoo-dev-sources-2.6.10-r1 (been happening since I switched to 2.6 with ati drivers installed)
- (xorg) xorg-x11-6.7.0-r2 **
- (ati drivers) ati-drivers-3.14.6 (tried several versions)
- (kde) kde-3.3.1

And my system specs:
- (motherboard) Asus A7N8X-D
- (videocard) Asus (Radeon) 9600 XT
- (hard drives) 2x Maxtor 120GB SATA

Here is my current .config and xorg.conf that I'm using.

Can't think of anything else relevent.

Thanks in advance to any insight.

Your beloved,
- shazow

* The reason I need gentoo-dev-sources is because of another issue. My ATI drivers don't seem to want to work properly with mm-sources. There's a dozen patches out there I need to apply to get it to work, but to no avail so far. Mainly ATI's fault, because I hate them so.

** I could be wrong, but if my memory serves me, this problem did NOT occur when I briefly tried xorg 6.8.x. But as you all know, 6.8 and ATI are not friends, so I had to revert.

Update: In anticipation to some questions, here are answers --
- Does it also happen if I use `shutdown -h now` from root while in xorg? Yes.
- What about outside of xorg (ie, not have it load on boot)? Nope, works fine until xorg starts... or rather, until it ends.
- Does this happen if ati drivers aren't installed? No. I suspect it has something to do with module unloading, but I'm not positive, and I can't find any angle to approach it from.

Solution: `CONFIG_FB_RADEON=y` was the culprit. Changing framebuffer to VESA did the trick.

pjp · Administrator Joined: 16 Apr 2002 Posts: 20093

Moved from Installing Gentoo.
_________________
Quis separabit? Quo animo?

Wedge_ · Posted: Tue Dec 28, 2004 10:44 am Post subject:

If you're using the "radeon" framebuffer driver, that might be the cause - it can often cause problems when used along with the fglrx driver.

shazow · Posted: Tue Dec 28, 2004 3:30 pm Post subject:

Nope. As you can see from my xorg.conf and kernel config, I'm purely using fglrx.

Wedge_ · Posted: Tue Dec 28, 2004 4:59 pm Post subject:

shazow · Posted: Tue Dec 28, 2004 5:04 pm Post subject:

Heh don't know, seems every new patch is an experimental patchset in windows

I thought you meant the "radeon" driver for xorg, my mistake. I'll give VESA a shot.

Yes, you're right about my xorg config. I mostly used the old working one I had from XF86Config. I'll remove the excess values, thanks.

- shazow

Jimmy Jazz · Guru Joined: 04 Oct 2004 Posts: 331 Location: Strasbourg

Same problem here but with a geforce card in twinview mode...So i think its most a X11 problem as a kernel driver one.

I can only leave xorg after a brutal "xdm stop" in a xterm terminal otherwise crash garanteed.

Jj

shazow · Posted: Wed Dec 29, 2004 12:38 pm Post subject: