[ivtv-devel] RE: help getting X started on PVR-350 w/ Fedora Core 3

[David Morrison]

Hi John,
If you are speaking of the patch in the in the enclosed posting, I had already applied it before posting this message??
http://gossamer-threads.com/lists/ivtv/devel/16645?page=unread#unread

I seem to be having an issue that is different from that described in that thread though.  It seems that if I try to force the ivtv module to load during startup the workstation freezes. 

What I am seeing is the boot process will get to the line "/sbin/modprobe ivtv" (in rc.local) and start to display the debug info that is normally put into the dmesg log (but without carrige returns?) and then hangs up? 

I suspect that this is from the autoloading of ivtv-fb module. I took out the line telling linux to autoload the ivtv-fb module from the modprobe.conf and tried to load the two modules individually (via command line) before starting X. When I do it that way it seems to execute the "/sbin/modprobe ivtv" without issue but when I issue the "/sbin/modprobe ivtv-fb" command I get the above described system hangup.

The strange thing is that this only happens when I call the the  "/sbin/modprobe ivtv-fb" from the rc.local, if I execute that from a terminal window while running X-windows it seems to execute ok?

A couple of questions:
1. I am running the ivtv-0.2.0-rc3d version of the release candidate, should I be running the ivtv-0.2.0-rc3C version?
2. When I compiled it I followed the readme and did the following:
# cd driver
# make
# make install
# cd ../utils
# make
# make instal
# install -c -m 0444 ivtvdev_drv_o /usr/X11R6/...

is there anything else that I should have done?

Since the machine locks up I can't get the messages out of the /var/log/dmesg log to send you, any ideas of what I can do to capture this?

dave