My Config: ATI MACH 64 GX, LG Studioworks 563N, FC2
My Problem: X doesnt start it says ATI card doesnt support 16 depth. I copied XF86Config from Knoppix ( which incidently works for me in FAILSAFE mode) That didnt work
I typed out 'system-config-display --set-driver=vesa' and then it worked @ all colour modes but i am not getting a) 1024x768 ( i had it in FC1 ;-( b) Clear movies : its all choppy on my FC2 Box
Now now can anyone help me put ATI correctly since it used to work @ all depths in Windoze
XORG is the problem:!!!!!!!!!!!!!!!!!!!!
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Sunday 30 May 2004 08:01, Ankit Malik wrote:
My Config: ATI MACH 64 GX, LG Studioworks 563N, FC2
My Problem: X doesnt start it says ATI card doesnt support 16 depth. I
Did you try setting the depth to 32 or 24 then?
copied XF86Config from Knoppix ( which incidently works for me in FAILSAFE mode) That didnt work
I typed out 'system-config-display --set-driver=vesa' and then it worked @ all colour modes but i am not getting a) 1024x768 ( i had it in FC1 ;-(
What is in your xorg.conf then? This tells X what resolutions your monitor and card can handle. X can be told to go ask the monitor over DDC what it can handle, for some cards and monitors that doesn't work and you need to tell X directly in the config file with HorizSync and VertRefresh lines.
b) Clear movies : its all choppy on my FC2 Box
vesa driver is a lowest common denominator driver, using your video BIOS to get modes and so on. It doesn't support xv, which is what provides smooth accellerated video. So the mere fact you are using the vesa X driver means many things will be unsupported and sluggish. (Hey, it's the same in XFree86).
Now now can anyone help me put ATI correctly since it used to work @ all depths in Windoze
More info and less complaining would help people help you.
XORG is the problem:!!!!!!!!!!!!!!!!!!!!
How did you work that out? That's the second time in two days I see people blaming xorg as The Demon. Why don't you find out more about where your problem is coming from before choosing what to curse out.
- -Andy
- -- Automatic actions for USB cameras, cardreaders, memory sticks, MP3 players http://warmcat.com/usbautocam
Andy Green wrote:
XORG is the problem:!!!!!!!!!!!!!!!!!!!!
How did you work that out? That's the second time in two days I see people blaming xorg as The Demon. Why don't you find out more about where your problem is coming from before choosing what to curse out.
I agree with the OP. The Xorg "ati" driver appears to me to be deficient, at least with the ATI Rage Mobility card. I am also unable to get more than 8 bits at 1024x480 on my Sony C1VFK Picturebook with Xorg under FC2, whereas I had 16 bits with this screen with XFree86 under FC1.
If I use the same config file (calling it xorg.conf) that I used successfully with XFree86 with DefaultDepth 16, I get a shrinking black oval which becomes a blank white screen. But there is no error indicated in Xorg.0.log . According to this, all is well.
In my view, that must be a bug in Xorg.
However, I'm more than happy to pursue any suggestion you might have.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Monday 31 May 2004 01:39, Timothy Murphy wrote:
Andy Green wrote:
XORG is the problem:!!!!!!!!!!!!!!!!!!!!
How did you work that out? That's the second time in two days I see
I agree with the OP.
IIRC you were the first person mentioned above ;-)
The Xorg "ati" driver appears to me to be deficient, at least with the ATI Rage Mobility card. I am also unable to get more than 8 bits at 1024x480 on my Sony C1VFK Picturebook with Xorg under FC2, whereas I had 16 bits with this screen with XFree86 under FC1.
That is an unusual resolution, I wonder if that is something to do with the problem. How much video memory is on the video card? AGP apeture size in BIOS? When you ask for 16 bits NOT using the config from yesteryear, what do you see in the xorg log file as the reason it rejected 16bpp? Did you try 32 or 24 bpp? What happens if you ask for the same deal using a "normal" resolution like 1024x768 (useless as that may be on your widescreen display).
If I use the same config file (calling it xorg.conf) that I used successfully with XFree86 with DefaultDepth 16, I get a shrinking black oval which becomes a blank white screen. But there is no error indicated in Xorg.0.log . According to this, all is well.
I have seen this on my Dell (using XF86 at that time....) it seems to be caused by the video chip stopping driving the LCD while the backlight is still on. From X's point of view everything IS well, it asked for such and such a video mode and as far as it can tell, got it. You can try Fn-F8 or whatever it is in your BIOS to flip between CRT and LCD, this something resets the chip from the BIOS code providing output again.
In my view, that must be a bug in Xorg.
Well, xorg's ATI driver seems to have changed functionality from what you were last using. It can be a bug or just something changed: since xorg IS XFree86 branched at a certain point blaming "xorg" makes no sense to me.
- -Andy
- -- Automatic actions for USB cameras, cardreaders, memory sticks, MP3 players http://warmcat.com/usbautocam
On Sun, 2004-05-30 at 03:01, Ankit Malik wrote:
My Config: ATI MACH 64 GX, LG Studioworks 563N, FC2
http://freedesktop.org/~xorg/X11R6.7.0/doc/ati.html
<snip>
XORG is the problem:!!!!!!!!!!!!!!!!!!!!
And you know this how?
Craig Thomas
-
Andy Green -
Ankit Malik -
Craig Thomas -
Timothy Murphy