utkjamie
November 22nd, 2008, 04:59 AM
I am using the ATI open source driver as recommended by Ubuntu and have a script that changes the video resolution for tv-out, switches to tv-out mode, etc. After upgrading to Intrepid, switching to tv-out mode causes the computer to freeze up. TV-out worked fine prior to upgrading to Intrepid and there appears to be an xrandr bug that causes lockups so it may be the problem if that bug made it into Intrepid.
The problem I have now is that switching to tv-out mode caused the screen to switch to a lower resolution and then freeze up the system. I had no choice but to kill the power. When I log back in, the screen resolution goes into low-resolution and freezes up again. I assume this is KDE restoring the previous session, but I don't know for sure. I've tried a few times but KDE keeps freezing up after logging me in. I tried logging in using fail-safe mode but that fails by just going back to the login prompt without explanation.
I'm having to boot into WinXP just to post this. If anyone can tell me how to get back into KDE, I'd be very appreciative.
As for the ATI drivers, people keep saying that the ATI binary drivers are the way to go. The problem is that the installation of those drivers is prevented by a segmentation fault. So we ATI users are sort of in a bind when it comes to using Intrepid.
The problem I have now is that switching to tv-out mode caused the screen to switch to a lower resolution and then freeze up the system. I had no choice but to kill the power. When I log back in, the screen resolution goes into low-resolution and freezes up again. I assume this is KDE restoring the previous session, but I don't know for sure. I've tried a few times but KDE keeps freezing up after logging me in. I tried logging in using fail-safe mode but that fails by just going back to the login prompt without explanation.
I'm having to boot into WinXP just to post this. If anyone can tell me how to get back into KDE, I'd be very appreciative.
As for the ATI drivers, people keep saying that the ATI binary drivers are the way to go. The problem is that the installation of those drivers is prevented by a segmentation fault. So we ATI users are sort of in a bind when it comes to using Intrepid.