Not sure I'll try to check my output tonight.

Please look in the XF86 log file and tell us what error is preventing X from loading.

With step 1 (the extra modprobe entries into /etc/mythtv/modules/ivtv),
the TV is simply dark, and nothing unusual is on the monitor, just the usual wraparound text messages. The error in /var/log/XFree86.0.log is
--------------------------------------------------------------------------
(II) LoadModule: "ivtvdev"
(II) Loading /usr/X11R6/lib/modules/drivers/ivtvdev_drv.o
(II) Module ivtv: vendor="The XFree86 Project"
compiled for 4.3.0, module version = 0.10.6
ABI class: XFree86 Video Driver, version 0.6
(II) LoadModule: "mouse"
(II) Loading /usr/X11R6/lib/modules/input/mouse_drv.o
(II) Module mouse: vendor="The XFree86 Project"
compiled for 4.3.0.1, module version = 1.0.0
Module class: XFree86 XInput Driver
ABI class: XFree86 XInput driver, version 0.4
(II) v4l driver for Video4Linux
(II) IVTVDEV_TST: driver for framebuffer: PVR-350
(II) Primary Device is: PCI 01:05:0
(WW) ivtvdev: No matching Device section for instance (BusID PCI:0:18:0) found
(EE) No devices detected.

Fatal server error:
no screens found
---------------------------------------------------------------------

Without Step 1, I get exactly the same error in /var/log/XFree86.0.log, but the behavior is different. It tries 3 times to set up gdm, then give up, dumping me into a display of the XFree86.0.log file. In the other case (with step 1), it does not do this, it simply makes the TV dark and leaves the wraparound text on the monitor.

The file /var/log/syslog file contains the following (after a boot configured like step 1):

--------------------------------------------------------------------------
Mar 23 16:03:15 mythtv kernel: ivtv0-osd warning: ivtvfb_check_var
Mar 23 16:03:15 mythtv kernel: ivtv0-osd warning: ivtvfb_set_par
Mar 23 16:03:15 mythtv gdm[4669]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0
Mar 23 16:03:19 mythtv kernel: ivtv0-osd warning: ivtvfb_check_var
Mar 23 16:03:19 mythtv kernel: ivtv0-osd warning: ivtvfb_set_par
Mar 23 16:03:19 mythtv gdm[4896]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0
Mar 23 16:03:23 mythtv kernel: ivtv0-osd warning: ivtvfb_check_var
Mar 23 16:03:23 mythtv kernel: ivtv0-osd warning: ivtvfb_set_par
Mar 23 16:03:23 mythtv gdm[4940]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0
Mar 23 16:03:23 mythtv gdm[4665]: deal_with_x_crashes: Running the XKeepsCrashing script
Mar 23 16:05:01 mythtv /USR/SBIN/CRON[5027]: (root) CMD (nice -n 19 /tv/mythlink.sh)
-----------------------------------------------------------------------------------

Has anyone come across these ivtv0-osd warnings? What to do about them? It seems like it would be normal not to see a module called ivtvdev_drv, because the above log file entries indicate that it loaded.

Thanks!

The extra modprobe entries are needed, keep those. Step 1 would not be needed only if they were already there.

Did you try making your BusID PCI 01:05:0 in the XF86Config file. It looks like it's detected at 01:05:0, but your are forcing it to use 0:18:0. It's worth a shot. It looks like your almost there.

I don't have ivtvdev_drv either. I don't think that is your problem.

Thanks for all the help guys! I haven't solved it, but I'm going to take a break. For now, I will use monitor for menus and TV for livetv.

BTW the 01:05:0 is actually the AGP graphics card, ... I don't think that forcing it to use 0:18:0 is the problem because that is the value I get from both lspci and scanpci.

I did a google search on the warnings for
ivtvfb_check_var
and
ivtvfb_set_par

Over here
http://www.gossamer-threads.com/lists/ivtv/devel/28130
someone has a similar problem (but not quite identical) but the thing is he says that it didn't work with two motherboards but finally worked in only one slot of a third motherboard. In my case I am using a PVR350 which has worked before with previous versions (R5A30.2), but on a different motherboard/cpu. So I've removed as many PCI cards as possible and
put it in a couple different PCI slots, but no luck. Anyway, I will fiddle with it more later. Its taken too much time for now. At least it is usable with the monitor. Thanks!!!