(EE) No screens found etc

pickarooney

Linux automatically detects my gfx card, and picks what seems to be the right driver, but can't find any screens. It tests itself, and finds no usable screens.
I can get by with the vesa driver, but the output is very blocky with AVIs etc. There's no hardware acceleration either obviously.

I'm guessing this is to do with the words "powered by ATI" on the box, which mean the ATI radeon 7000 driver delivered with Mandrake 9.1 won't work for it?

If not, what does the message
"(EE) Screens(s) found, but none have a usable configuration.
Fatal Server Error:
no screens found" really mean?

I'm not using any bizarre resolutions (1024x768) or colour depths (24 bpp).

If I try to reconfigure the gfx card now with XFreedrake, it goes:

"Shutting down X font server:
Starting X font server:
xfs is not running at /usr/lib/libDrakX/Xconfig/test.pm line 47."

and stops.

Which is nice.

Do I need to apply SwiftKick 2003 to the damn pikey card?

[edit] Forgot to mention it's a connect 3d card, with dual monitor support. I have only one monitor attached, which may have something to dow ith it. I never asked it to go setting itself up for two monitors, though.
Arthur Two-monitors Jackson I am not. [/edit]

Typedef

Vert & Horizontal settings in your monitor section are the cause of the error .

Not the driver for the gfx card.

Section "Monitor"

Identifier "Dell_Drone"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

HorizSync 31.5 - 64.3

# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

VertRefresh 50-100

EndSection

Something like that should work just fine

Slackware.....
go on

pickarooney

The installer identified the monitor correctly, and added these lines to XF86Config-4

Section "Monitor"
Identifier "monitor1"
VendorName "Plug'n Play"
ModelName "Dell D1025HE"
HorizSync 31.0-92.0
VertRefresh 50.0-120.0

# Sony Vaio C1(X,XS,VE,VN)?
# 1024x480 @ 85.6 Hz, 48 kHz hsync
ModeLine "1024x480" 65.00 1024 1032 1176 1344 480 488 494 563 -hsync -vsync

# TV fullscreen mode or DVD fullscreen output.
# 768x576 @ 79 Hz, 50 kHz hsync
ModeLine "768x576" 50.00 768 832 846 1000 576 590 595 630

# 768x576 @ 100 Hz, 61.6 kHz hsync
ModeLine "768x576" 63.07 768 800 960 1024 576 578 590 616
EndSection

These match the actual monitor settings, and work fine with the vesa driver.

pickarooney

I'm trying with various values of HorizSync, to see can I get the card recognised, but I can't run the
screen-test, because of this error:

"Shutting down X font server:
Starting X font server:
xfs is not running at /usr/lib/libDrakX/Xconfig/test.pm line 47."

Sorry to keep on about this, but I've been going around in circles for nearly a year trying to get this card working under various Linuces, to no avail...

Magic Monkey

pickarooney, I don't know if this will help you, but I had problems similar to yours (I think so anyway, it was a while ago) with Debian 3.0r1 and XF86Config-4. In the "Monitor" section of the XF86Config-4 file, I had to change the "DPMS" option to false to get X to load, i.e.

Section "Monitor"
Identifier "Unknown Monitor"
HorizSync 28-48
VertRefresh 43-72
Option "DPMS" "false"
EndSection


Once I did that, "startx" worked. Hope this helps somewhat

Oh, also, I ran knoppix prior to a Debian reinstall to get specific information about the hardware, quite handy.

pickarooney

Thanks for the tip, but once again, it failed
Knoppix is based on Debian, right? Would it be worth my while getting a copy and trying it. I don't see what hardware information I could be missing, though.

pickarooney

Could the fact that there's two monitor connectors be causing the display trouble? Bear in mind I've tried connecting the monitor to each one in turn when installing, but without success.

Downloading Knoppix now, to see can it shed any light.

niallb

Originally posted by pickarooney
Could the fact that there's two monitor connectors be causing the display trouble? Bear in mind I've tried connecting the monitor to each one in turn when installing, but without success.

Are they both on a dual head card or do you have two graphics cards? They're two very different setups.
If you've two, check your BIOS to see whether PCI or AGP is your primary display.
Boot messages will only display on that one.
I haven't run Knoppix on a dual display setup yet, but you could try XFdrake. It knows about dual display.

Get things working with solidly one display first, then worry about the other one. (I guess this is still the Radeon 7000 system?)

This might help. From a Radeon user:
a4lcI was browsing the net and i found that when you're configuring the base system,
you're suppose to disable Kernel frame buffering. It worked so I am happy. Thanks for offering your help though.

If that's true, try setting vga=normal in your lilo or grub conf.

NiallB

pickarooney

It's a dual-head card, with just one monitor attached. I've no interest in having a dual display, as I have only one screen, but maybe XFDrake tries to test a dual-display when I choose the Radeon driver from its list? Doubt it, though.

Where exactly in lilo.conf should I enter the line "vga=normal", or does it matter?

(I'm in work at the moment and am not sure if I possess such a thing as a lilo.conf, but assuming I do )

I think I need to find someone with exactly the same card and monitor combo and copy his XF86Config-4 file.

niallb

If you have lilo installed (Graphical boot menu?)
you need to look for a line in /etc/lilo.conf
starting with append= and add vga=normal

lilo.conf probably has a few references to vga=.
Change them all to vga=normal instead of the number of the vesa mode (eg: vga=789). Your console screen will revert to 80x25.

You'll know it's worked when you no longer see the little penguin at boot time. :-(

While you're in there, take out the word quiet from the append lines, you'll get much more info at bootup.

Once you've the file saved, run lilo as root.
You should see it list the items in the menu with an asterisk beside the default one.

If that comment is relevant, this should get you a bit further.

NiallB

pickarooney

Tried it, no gfx on startup

At least Knoppix is cooked, nothing left but to try it out.

Typedef

Goole for an XF86Config-4 file with the same ATI version as your own, instead of fscking around with different distros!

niallb

Good luck,
seems a lot of people have grief with your card.
Some of them have managed it though.

The first card I ever tried to configure with X was
a Realtek RTG3106 (a 1Meg ISA card way back when).
Never got it to work.
This was in the days where you'd to persuade a card
to report its clocks, or find them on a newsgroup.
After that you simply dug out the graph paper and
calculated your modelines.
(If you think I'm joking, head over to "The Linux Journal"'s website at ssc.com,
they had a series of articles on it in the mid nineties, should be in the archive)

I found it a couple of years later in a drawer and stuck
it into a machine just so I could feel no card had beaten me.
It just wouldn't work, no matter how many tricks I threw at it. Sometimes you just need to get something else :-(

Keep us posted,
NiallB

pickarooney

Thought I might have had it with an Option "CrtScreen" in there, but no such luck.
Posting this from Knoppix. Impressive little thing, set itself up in about 2 minutes.. but went for the vesa driver, no questions asked.

Sod it, I'll eventually get round to getting a better (supported) gfx card.

Thanks for all the help.


/reboots lest he gets too comfy with knoppix

ssh

No screens found means that Xfree has failed to find a suitable graphics device to use.

This usually is because you have the incorrect driver specified in the Device section of your XF86.

What is your output when you type lspci -v

It should give you a clue.

niallb

Hi ssh,
we know what the card is - it's a Radeon 7000 Connect 3D dual head.
and it works fine with the vesa driver - though slowly I assume.

It's the 'radeon' driver he's been having trouble with.
Have you any experience with one of those?

NiallB

ssh

My experience with the Radeon 7000 and the Xfree86 radeon driver is that I couldn't get it to work But that doesn't mean you can't.

It was a friends card, and I went looking for drivers produced by ATI, but didn't find it.

They have since improved their site, and do seem to provide xfree86 support without specifically mentioning the 7000.

It's all on their website.

longword

Originally posted by ssh
My experience with the Radeon 7000 and the Xfree86 radeon driver is that I couldn't get it to work But that doesn't mean you can't.

I had no problem getting it to work dual-head with the XFree86 radeon driver as shipped with Red Hat 9. Unfortunately the (stupidly expensive) card has a second Radeon 7000 chip on it and I failed miserably in all attempts to get it working with either of the two heads on that :-(

niallb

Hi longword,
what kernel version are you using on the redhat install
that works? I know redhat patch their kernels pretty heavily.

uname -a will tell you what it is.

If the install is gone, was it just the default installed kernel?
If the install isn't gone, could you send the /etc/X11/XF86Config-4 file to pickarooney!

Seems a few people have this card, so it's worth persevering.
Anyone want to loan me one some weekend?

BTW, are you certain it was using the radeon driver, and not the vesa one? :-)

NiallB

longword

Sorry, it's all whitewashed because the card couldn't be made to function fully (with the 2nd chip enabled for screens 3 and 4). It was Red Hat 9 with one of their standard kernels (may have been upgraded slightly to whatever Red Hat's latest update was at the time) but it was 2.4.20. I was using Red Hat's standard XFree86 (though I later built my own RPM from CVS source). It was most definitely using the radeon driver. You'd have zero chance getting two screens running with a vesa/fb driver!

To be honest I don't recall having to do anything special to get one screen running. It was a TFT screen, but through analog VGA. Getting two screens running was a touch more challenging, but no more so than any other dual head card I've worked with. There may be an issue if your motherboard's AGP chipset isn't supported by agpgart - I know that's a problem with ATI's binary driver. I was using it on an i850 board so if that is a problem I wouldn't have encountered it.

Can you post the complete copy of /var/log/XFree86.0.log somewhere?

pickarooney

Here's a copy of my /var/log/XFree86.0.log(renamed to txt to attach) ...

pickarooney

... and the var/log/XFree86.9.log for good measure

Typedef

(EE) RADEON(0): No valid mode found for this DFP/LCD (II)

You don't have a valid modeline for that monitor duder!

In fact read this
http://www.mail-archive.com/xfree86@xfree86.org/msg07101.html

You don't have something plugged into the composite port on that Radeon do you?

Unless you specifically configure X to run off of one monitor/tv or the other or in (cloned mode and you have modelines for both monitors) the X startup will fail!

In any case it looks as if you simply need to define the correct modeline in your X config file.

pickarooney

Yep, the s-video cable to the TV is connected to the card.

Current modelines:

Section "Monitor"
Identifier "monitor1"
HorizSync 31.5-69.0
VertRefresh 50.0-110.0

# Sony Vaio C1(X,XS,VE,VN)?
# 1024x480 @ 85.6 Hz, 48 kHz hsync
ModeLine "1024x480" 65.00 1024 1032 1176 1344 480 488 494 563 -hsync -vsync

# TV fullscreen mode or DVD fullscreen output.
# 768x576 @ 79 Hz, 50 kHz hsync
ModeLine "768x576" 50.00 768 832 846 1000 576 590 595 630

# 768x576 @ 100 Hz, 61.6 kHz hsync
ModeLine "768x576" 63.07 768 800 960 1024 576 578 590 616
EndSection

I'll give it a go with nothing plugged in, but I gots to have TV-out...

Typedef

You have monitor 1 working do you?

In any case, for a start.

The modeline you are using for your TV, is farily far beyond "PAL-I" or the type of PAL used in the UK,Hong Kong & Ireland.

I have a working modeline for PALI that I'm using for my Nvidia, which I can post for you.

I'm assuming you want to get both monitors working at once?

I'm not familiar with the ATI card, but I'm sure there's some sort of clone that has to be configured to get both Monitor and TV working at once.

I used the nvidia specific "twin view" X extensions to get that sort of stuff working on my TV.

You should probably outline "exactly" what you want to do with the TV & Monitor and then post your XF86Config file.

Typedef

Here.

Try this as a PAL I modeline

# PAL 60
ModeLine "640x480x60" 25.2 640 656 752 800 480 490 492 525
ModeLine "800x600x60" 39.7901 800 840 968 1056 600 601 605 628

# PAL 50
ModeLine "640x480x50" 21.0 640 656 752 800 480 490 492 525
ModeLine "800x600x50" 33.1584 800 840 968 1056 600 601 605 628

Also, I'm quite sure there is some configuration needed to get cloning working in X for your ATI.

I'd google for that or look at ATI's site if I was you.

pickarooney

Nah, can't even get my (single) monitor working, with the s-video cable plugged out.

My TV is PAL GB I think (Dutch standard), i'll double check and look for a corresponding modeline somewhere, but I doubt it's much different, AFAIK only the sound signal is different to PAL I.

This will have to be after I reformat my machine again though, I fear. It's become unusably slow for even the simplest things recently. It's hanging for 5 minutes at a time when switching between windows... piece of crap

Typedef

Hmm.

Maybe you should think about posting your X config.

Could be that even though the S-Video cable is unplugged, the X server is still trying to put video output through it.

There's no way to tell without getting a look at your config file though.

pickarooney

Here it is (again) in all its glory. Bear in mind this is it as it stands, with the vesa driver selected and the S-video cable plugged back in again.

Typedef

Try one of these modelines

Modeline "1024x768" 65 1024 1032 1176 1344 768 771 777 806 -hsync -vsync

Modeline "1024x768" 75 1024 1048 1184 1328 768 771 777 806 -hsync -vsync

Modeline "1024x768" 85 1024 1032 1152 1360 768 784 787 823

Also I notice you're using the vesa driver that comes with X.

Afaik ATI provides drivers for X.

Here

http://mirror.ati.com/support/driver.html

Go, download and install[1] as appropite

[1]Following the install instructions to the T.

pickarooney

We've been round and round this a few times.
I'm using the vesa drivers because the ATI drivers (distributed with Mandrake 9.1) don't work for my card.
At least I haven't been able to get them to, hence the "Screens not found" message.

The ones from the ATI website (AFAICT the same ones) were developed for the 8500 series and up. The supplied Check.sh file just gives errors when run.

longword

Originally posted by pickarooney
We've been round and round this a few times.
I'm using the vesa drivers because the ATI drivers (distributed with Mandrake 9.1) don't work for my card.
At least I haven't been able to get them to, hence the "Screens not found" message.

The ones from the ATI website (AFAICT the same ones) were developed for the 8500 series and up. The supplied Check.sh file just gives errors when run.

If you're using the VESA FB drivers your chances of getting TV out, or any decent speed from video playback, are pretty much zero.

XFree86 4, as included with Mandrake, ships with a driver called 'radeon' which should support your card perfectly. This driver has nothing to do with the binary-only driver published by ATI. I don't know Mandrake these days, it's possible they ship ATI's driver in addition to the standard XFree86 driver and perhaps their autodetect tool incorrectly assumes your card will work with ATI's driver. You can try messing with the Device section of your XF86Config file yourself, setting the Driver to "radeon".

pickarooney

The Tv-out works like a charm with the vesa drivers, auto-deteced on first installation. Playback speed is a bit limited however.
The "radeon" driver from XFree doesn't work, hasn't worked in the 12 months since I got the card, and doesn't show any signs of working now, with or without the TV-out option.
If I switch to the radeon driver using the config tool, the XFdrake test won't execute ("xfs is not running" error) and if I change it manually (and use the suggested Modeline entries) X won't start up at all ("no screens found" error).

I'm not actually sure whether or not the ATI driver from their site is the same as the one that comes with X (which correctly recognises my card as a Radeon 7000) but the end result was the same when I tried it a while back.

Apologies for any percieved slight/brusque tone, I'm a bit annoyed, but only with the card. I really do appreciate the help.

Typedef

If you have TV out working with the vesa driver, then all you have to do is find a valid modline to get your LCD working.

Once you have that, you can configure the cloning.

longword is right though, you won't get great performance with the X supplied drivers (certainly not the vesa one).

niallb

Originally posted by pickarooney
If I switch to the radeon driver using the config tool, the XFdrake test won't execute ("xfs is not running" error).

Try running service xfs start and then run the XFdrake test again.

How many different versions of the driver have you used
over the last 12 months? Mandrake have updated X packages out as of last week, and probably a kernel to match.
urpmi.update -a and try installing them!

NiallB

pickarooney

When you run XFDrake and change gfx driver, then hit Test, it first shuts down the xfs, then tries to restart it using the new drivers. It's at this stage that the "xfs not running" appears and the test fails.

I ran urpmi.update -a. It downloaded a few header files and got a series of rsynch errors (does that indicate a missing update from the remote server?).
Ehm, what do I do once it finishes that?

niallb

Hi,
the xfs is the X font server rather than the Xserver itself.

I just took a quick look at XFdrake and there's no mention of xfs in it at first glance.

The X server will fail if it can't open the default font.

Mandrake now relies on a font server for all of its fonts,
so if it's not running you won't get X.
You can manually add in a few fontpath lines,
but its only worth it if you're very low on memory.

Are you preparing to run XFdrake by going to console mode using
telinit 3 or some dm menu for console mode?
If you are, that's when xfs is getting shut down.

Try going to console mode in the same way, and just running startx.
If this is the problem, X won't start up even though its using the config file that worked 2 minutes earlier.
start service xfs will make it happen again.

Well, it might be involved!

Good luck again,
NiallB

longword

Originally posted by Typedef
longword is right though, you won't get great performance with the X supplied drivers (certainly not the vesa one).

The radeon driver in XFree86 4.3.0 should be decent enough for anything 2D but will be less than satisfying in 3D. There's no other choice for that card though.

pickarooney

Update: I removed the S-Video cable and did an update install. This time the card was detected properly and with a usable screen. Success! Or is it...

I've kind of robbed Peter to pay Paul, the TV-out module doesn't seem to want to work with the Radeon driver and the vesa driver doesn't do hardware acceleration so I still can't watch movie files with a decent framerate on the TV.
Also, Xine now plays with a black screen, sound OK (seems to be using the vx driver instead of the X11, as changing these around gives the same result in mplayer, but when I click on the video preferences tab as xine all that appears is "There is no configuration option avaiable in this user experience level" whether logged as myself or root), and mplayer plays in a tiny window unless I run it with switches from the command line - not too practical when you want to click and play a couple of files in succession. I've yet to find an automatic -zoom option in the prefs...
</tangent>

Anyhow, TV-out in, no go, TV-out out, driver is usable but limited. The battle continues.

Typedef

Here are all the valid config options for that card.

http://www.xfree86.org/4.3.0/radeon.4.html

Option "CloneDisplay" "integer"

This option is only used for dual-head cards with only single screen section specified in the configuration file.

0 -- disable
1 -- auto-detect (default)
2 -- force on
3 -- auto-detect + 2nd head overlay
4 -- force on + 2nd head overlay
others -- auto-detect

disable means only one CRTC is used for both heads. auto-detect means the secondary head will be driven by CRTC2 if a monitor is detected there. force on means the secondary head will be driven by CRTC2 even no monitor is detected there. 2nd-head overlay means the only hardware overlay will be placed to the secondary head.

Primary/Secondary head for dual-head cards:
(when only one port is used, it will be treated as the primary regardless)
Primary head:
DVI port on DVI+VGA cards
LCD output on laptops
Internal TMDS prot on DVI+DVI cards
Secondary head:
VGA port on DVI+VGA cards
VGA port on laptops
External TMDS port on DVI+DVI cards
Option "CloneMode" "string"
Set the first mode for the secondary head. It can be different from the modes used for the primary head. If you don't have this line while clone is on, the modes specified for the primary head will be used for the secondary head.
Option "CloneHSync" "string"
Set the horizontal sync range for the secondary monitor. It is not required if a DDC-capable monitor is connected.
The default value is undefined.
Option "CloneVRefresh" "string"
Set the vertical refresh range for the secondary monitor. It is not required if a DDC-capable monitor is connected.
The default value is undefined.

Now, if your Radeon is anything like my Nvidia.

When you connect the S-Video cable to a EuroScart and plug the scart into a TV and boot your machine.

You should get (both) displays active.
If you don't, X won't work later on.

If you do get that.
You have to decide whether you want to 'clone' or to run the TV exclusively as your monitor.

I'm not sure if cloning is 'valid' for an SVideo connection... but I reckon it should be.

Remember though, if the TV has no display on boot (ie the BIOS outputting video to that port) you're foobared.
If it does you at least have that much working.

pickarooney

With the S-video connected and this line added to XF86Config-4:
Option "CloneDisplay" "1"
everything output to the screen during booting, then once X tried to start it failed with the usual "No screens found" error.
May just need to throw an extra modeline or try different integer values.

pickarooney

Nope, none of the integer values worked.
I don't get how the card can find a valid mode for the TV with the standard vesa driver, but not be able to use the same mode with the radeon one?

Current monitor section, with radeon driver and s-video connector unplugged:


Section "Monitor"
Identifier "monitor1"
HorizSync 31.5-69.0
VertRefresh 50.0-110.0

# Sony Vaio C1(X,XS,VE,VN)?
# 1024x480 @ 85.6 Hz, 48 kHz hsync
ModeLine "1024x480" 65.00 1024 1032 1176 1344 480 488 494 563 -hsync -vsync

# TV fullscreen mode or DVD fullscreen out
# 768x576 @ 79 Hz, 50 kHz hsync
ModeLine "768x576" 50.00 768 832 846 1000 576 590 595 630

# 768x576 @ 100 Hz, 61.6 kHz hsync
ModeLine "768x576" 63.07 768 800 960 1024 576 578 590 616
EndSection

Typedef

I suspect it's however the cloning is setup that is chucking you out.

Something like this should work.

http://www.mail-archive.com/devel@xfree86.org/msg01594.html

Edit.

I'm not entirely sure the screen colours won't be fncked up, without you informing X that you want to use a PAL (as opposed to NTSC) video output for screen #2.

pickarooney

So, first I need a second Monitor entry, the names are only for reference I suppose?
Then, a new device entry, with Screen 1 instead of Screen 0. Not sure what the PCI BusID entry is about.
Then, a new Screen entry using Screen 1, referencing the new device entry.

That config file seems to be splitting the output over the two screens though? Not cloning, which is what I want to do.

Typedef

I've never cloned but.

# Option "CloneDisplay" "true" Option "CloneMode" "1280x1024" Option "CloneHSync" "30-95"
# Option "CloneVRefresh" "50-120"

With 640x480 (much closer to PAL) and setting Clone to true might work... might not.

Try this

http://spacepants.org/conf/XF86Config-4

Also X should pick up that PCI id thingy.

It's a reference to the location of your AGP as far as I remember, but X probes for that anyway.

pickarooney

Seems plausible. Is there any chance of damaging the TV with wrong HSynch and VRefresh values?

Typedef

Yes, it's possible.

That is why you should stick to the PAL-I modeline.

pickarooney

It's a PAL G/B TV though, which is my concern.

Typedef

So you say.

"PAL-B" : used in Belgium, Denmark, Finland, Germany, Guinea,
Hong Kong, India, Indonesia, Italy, Malaysia, The
Netherlands, Norway, Portugal, Singapore, Spain,
Sweden, and Switzerland
"PAL-D" : used in China and North Korea
"PAL-G" : used in Denmark, Finland, Germany, Italy, Malaysia,
The Netherlands, Norway, Portugal, Spain, Sweden,
and Switzerland
"PAL-H" : used in Belgium
"PAL-I" : used in Hong Kong and The United Kingdom
"PAL-K1" : used in Guinea
"PAL-M" : used in Brazil
"PAL-N" : used in France, Paraguay, and Uruguay
"PAL-NC" : used in Argentina
"NTSC-J" : used in Japan
"NTSC-M" : used in Canada, Chile, Colombia, Costa Rica, Ecuador,
Haiti, Honduras, Mexico, Panama, Puerto Rico, South
Korea, Taiwan, United States of America, and Venezuela

You'd want to disjunct between PAL B or PAL G.

In any case one of these modlines (I suggest the 640x480 for safety should work).

ModeLine "800x600PAL" 36.00 800 816 820 960 600
653 655 750
ModeLine "640x480PAL" 29.50 640 676 680 944 480
530 535 625

If indeed it is PAL-B.
http://slog.dk/~jensen/inspiron8200/redhat-setup/XF86Config-4

However.

Try googling for PAL-G modeline, if it's not PAL-B.
I'm thinking at 640x480 that most PAL - like modelines will be safe for your TV.

Indeed I ran my TV at 1024x768, before reading all the documentation on how bad modelines can kill your monitor/TV, with no ill effects[1].

[1]Mileage may vary.
[2]I'm using the corret PAL-I mode now.

pickarooney

I'm pretty sure the TV itself receives both PAL-B and PAL-G regardless, it's only a minor difference in the signal. Some stations broadcast in B and others in G in Holland, I think (or else the cable providors reencode them differently). Here goes with the 640x480 ModeLine, to start off at least...

*fingers crossed*

pickarooney

Nah, none of the options for that nvidia card match the options for the Radeon one - no TV options at all on my card apparently.