Video driver problem on upgrade to Hardy

[NoOp]

On 04/26/2008 03:03 AM, Paolo wrote:

> 
> It is a strange user experience ;-)
> 
> Having installed the proprietary ATI driver, I notice only one change: I now 
> have a cursor visible in Thunderbird when writing emails. Before, the cursor was 
> invisible.
> 
> Changes to the xorg.conf file, with respect to the file I posted, since 
> installing the proprietary driver are minimal:
> 
> Section "Device"
> has: 	Driver	 "fglrx"  (changed from "ati")

Maybe the cause? I'm not sure if you actually require fglrx vs glrx. I
honestly don't know about it to say either way, but you can goole for
'Ubuntu +fglrx vs glrx' and see what you come up with. Remember at the
start of this thread, you were looking to remove fglrx... You can remove
it by:

sudo apt-get remove --purge xorg-driver-fglrx

My _guess_ would be to go back to the Ubuntu ATI driver unless
recommended elsewhere.

> 
> And the 2 sections "DRI" and "Extensions" have been deleted.
> 
> Meanwhile, in var/log/Xorg.0.log: Here are the (WW) and (EE) entries...
> 
> Lines 227-230:
> (II) LoadModule: "v4l"
> (WW) Warning, couldn't open module v4l
> (II) UnloadModule: "v4l"
> (EE) Failed to load module "v4l" (module does not exist, 0)

http://ati.amd.com/products/catalyst/linux.html
Q8:  	  Is v4l video capture supported for ALL IN WONDER cards?
A8: 	The ATI Proprietary Linux driver does not currently provide video
capture functionality. Video capture support for most ALL IN WONDER
cards should be available from the GATOS project.

A proper result should be:
~$ cat /var/log/Xorg.0.log | grep v4
(II) LoadModule: "v4l"
(II) Loading /usr/lib/xorg/modules/drivers//v4l_drv.so
(II) Module v4l: vendor="X.Org Foundation"
(II) v4l driver for Video4Linux

When you have the following in your xorg.conf file:

Section "Module"
	Load	"v4l"

Remember, your initial had:

Section "Module"
	Load		"glx"
	Load		"GLcore"
	Load		"v4l"

> 
> Lines 455-463 contain this line repeated:
> (EE) fglrx(0): === [swlDalHelperAddCustomizeMode] === 
> CWDDEDI_DisplayGetSetModeTimingOverride failed: 2
> 
> Line 622:
> (WW) fglrx(0): could not detect X server version (query_status=-3)
> 
> Line 749:
> (WW) fglrx(0): Option "MergedFB" is not used

This would be normal if the Frame Buffer is not enabled.
> 
> Line 784-863 have lines similar to this one:
> (WW) AIGLX: 3D driver claims to not support visual 0x23

I _think_ that this should return something like this:

~$ cat /var/log/Xorg.0.log | grep 3D
(--) Chipset ATI 3D Rage Mobility Found
(--) MACH64(0): ATI Rage Mobility graphics controller detected.

I only have one ATI left & it's an IBM Thinkpad A21M. The above is the
output from that machine (Hardy).

Unfortunately, that machine only has 128MB of memory, so trying anything
beyond basic graphics would be futile.

Have you tried the previous suggestion of:

> Note: If all else fails, reboot and select "Recovery Mode" from the Grub
> menu. When that recovery menu comes up, select "xfix Try to fix the X
> server" and when it finishes, select "resume resume normal boot". That
> will load a generic xorg.conf (that's why you save your old one :-),

RE: > I can also confirm what Onderstekop  writes at the bottom of
> https://bugs.launchpad.net/bugs/221764
> 
> I have just started a failsafe GNOME session and it works perfectly!

That is because failsafe GNOME doesn't load any of your init scripts.

Try this: create a new user, reboot and log in as that user using the
standard login. See if that works. If if does, then it's not the
xorg.conf file, but instead something in the actual user init scrips.

> 
> This does make me feel better. No how do I look for what is going wrong in a 
> "normal" session?

Don't know (yet :-). Sorry.