On Wednesday 24 May 2006 23:58, Shawn Holland wrote:
Here is my new Xorg.conf <snip> I got the modeline I'm running from:
http://www.tkk.fi/Misc/Electronics/faq/vga2rgb/calc.html
I selected 640x480 NTSC TV Interlaced
The "monitor" section I'm not sure its right. I just left it the default settings of the Monitor it picked up when I loaded SaX2 -m 0=nvidia
I just adjusted the refresh rates.
here is my Xorg.0.log file output <snip> What happens is it switches to Composite and you can see a big black box where KDE should be loading. But nothing ever loads in there.
I feel I'm so close but for all I know I could be way off :)
Hi Shawn, I've had a look and my impression is your module is built and loading correctly :-) Here is what X found during it's probes: (--) PCI:*(1:0:0) nVidia Corporation NV15DDR [GeForce2 Ti] rev 164, Mem @ 0xfd000000/24, 0xc0000000/27, BIOS @ 0xfeaf0000/16 ... (--) Chipset NVIDIA GPU found ... (--) NVIDIA(0): Linear framebuffer at 0xC0000000 (--) NVIDIA(0): MMIO registers at 0xFD000000 ... (--) NVIDIA(0): VideoBIOS: 03.15.01.06.06 (--) NVIDIA(0): Interlaced video modes are supported on this GPU ... (--) NVIDIA(0): VideoRAM: 65536 kBytes ... (--) NVIDIA(0): Detected TV Encoder: Philips 7108 (--) NVIDIA(0): Display device TV-0: maximum pixel clock at 8 bpp: 350 MHz (--) NVIDIA(0): Display device TV-0: maximum pixel clock at 16 bpp: 350 MHz (--) NVIDIA(0): Display device TV-0: maximum pixel clock at 32 bpp: 300 MHz There are *no* (EE) errors, *no* (!!) notices, *no* (NI) not implemented and *no* (??) unknowns. ;-) This is a very good sign. (WW) warnings are another matter, but they don't really look very serious: * There's the usual collection of 'missing' font paths/fonts (they're just not installed on your system.) AFAIK, this shouldn't 'break' your installation. * (WW) Open APM failed (/dev/apm_bios) (No such file or directory) Note: I don't know if this is a 'show stopper' or not... it looks like 'Advanced Power Management' to me, but I could be wrong... You probably want to check it out. ;-) * (WW) NVIDIA(0): Not using mode "512x384" (not a valid TV mode) Note: This one *definitely* needs investigating. You also have 77 tried/invalid display mode entries... "(vrefresh out of range)" ... "(hsync out of range)" ... "(bad mode clock/interlace/doublescan)" and "(no mode of this name)" and, finally, this highly targeted and informative warning: * (WW) NVIDIA(0): WAIT (0, 1, 0x2000, 0x00000494, 0x00000494, 0) :-) I 'see' three possible approaches to this: * configure the system to work on the primary display, first, without having the TV connected and plan on 'adding' the TV after the card is configured. * configure the system to work using the TV as the primary display, first, without having your usual primary display (monitor) connected to the system (i.e. "unplug the monitor") then 'adding' your monitor after the card is configured. * proceed as you are, attempting to configure the system with both the TV and your primary display connected. I don't recommend this.* (*)I'm a big fan of reducing problems down to the least common denominator... the least complexity... until I can establish a solid foundation (no 'unknowns' at play) that I can confidently build upon. It's your system, your time & effort and, eventually your how-to :-) so obviously the decision here is your's. The only other items I saw that raised a flag were these (==) default settings (Note... "TrueColor is 24-bit vs. a 'DefaultDepth' set to 16-bit): (==) NVIDIA(0): RGB weight 565 (==) NVIDIA(0): Default visual is TrueColor (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0) compared to these settings from xorg.conf: Section "Screen" DefaultDepth 16 SubSection "Display" Depth 16 Modes "640x480" EndSubSection Device "Device[0]" Identifier "Screen[0]" Monitor "Monitor[0]" EndSection I wouldn't start hacking xorg.conf again. At this point, with the card correctly detected and initialized and with no errors from loading the module, I'd see if SaX2 (with only one display connected... probably your monitor and not the TV)... can sort out the necessary settings on it's own. Looking at 'man SaX2' I see these possibilities: sax2 -r (reinit the hw db/detection and try again) sax2 -a (attempt autoconfigure) sax2 -m 0=nvidia (try SaX2's GUI again, specifying the module) I'm sure you and others will have some good ideas about how to proceed, as well. regards, Carl