Chapman McDaniel wrote: > first things first: > Fedora Core 5 i386 > (may have been upgraded to 686 kernel as a dependency for ivtv-kermod)) > Hauppage PVR-350 > ATI Radeon 7200 > AMD Sempron Processor > MSI K8N Motherboard > 2.6.16-1.2122_FC5 > ivtv installed packages are: > ivtv 1:0.6.2 for i386 > firmware, firmware-audio, firmware-dec, firmware-enc > ivtv-kernheaders > kernel modules for 2.6.16-1.2122 i686 > ivtv_xdriver > perl-Video-ivtv > all were installed through the yum gui in FC5
I assume you means that you installed from the ATRPMs repository? > I had been following jarod wilson's Fedora Mythtv setup guide > <http://wilsonet.com/mythtv/fcmyth.php?SID&expandables=closed&ivtv=open&pvr350out=open#capture> > attempting to set up IVTV tv-out. I couldn't find the ivtv development > package that he mentions, and had assumed that the ivtv_xdriver had > replaced those. Everything was working fine with the video capture, i > was getting video and sound. I added the vga=791 to my grub.conf, and > turned on the PVR-350 line in my modprobe.conf: > 'install ivtv /sbin/modprobe --ignore-install ivtv; /sbin/modprobe ivtv-fb' > i had the framebuffer working on /dev/fb1, and both tests jarod mentions > were working. I got a test pattern to show up on my TV, and had success > piping the video in and directly back out through the card. I had also > replaced the ivtv tveeprom module with the kernel-supplied one, and had > no issues. > > Finally, I had updated my xorg.conf to include the PVR-350 device, but > instead of "ivtvdev", i put "ivtv_xdriver", because I didn't have the > ivtvdev module. Is this intended to be your only X11 server running on your computer? Or a second one in addition to the normal one running on your ATI Radeon 7200 video card? > I followed jarod's instructions and hit control-alt-backspace to kill > off the xdriver, but nothing showed up on the tv screen. Eventually, I > shut down the PC with a Ctl-Alt-Del, and rebooted, but now udev wouldn't > load. After booting into rescue mode, I returned xorg.conf to it's > original state, still no udev on boot. Finally, I went into > modprobe.conf and commented out the line that loads the framebuffer, and > that allows udev to load on boot. Unfortunately, since it won't boot > (after udev times out -assumedly trying to detect the framebuffer-, the > system will get a bit further in the boot process before it grinds to a > halt), I don't have the standard ivtv load log, so i can't tell you what > I see. On a successful boot with the framebuffer line commented out, > the ivtv capture won't load. error message when I type modprobe ivtv is: > WARNING: Error inserting tveeprom > (/lib/modules/2.6.16-1.2122_FC5/updates/drivers/media/video/tveeprom.ko): > Operation not permitted > FATAL: Error inserting ivtv > (/lib/modules/2.6.16-1.2122_FC5/updates/media/video/ivtv.ko ): Unknown > symbol in module, or unknown parameter (see dmesg). > > dmesg says: > - signature keyid: 009227b3bcb5ebae ver=3 > ivtv: Unknown symbol tveeprom_read > ivtv: Unknown symbol tveeprom_hauppage_analog > > What did Control-Alt-Backspace do? Is there any way that I can get the > system back to the previous state without wiping the root partition and > starting from the beginning? I need a little more information about your setup. Are you running an X11 GUI on your ATI video card? If so, then you need to run 2 X servers, one on your ATI Radeon 7200, and one on your TV (through the PVR-350). If not, what are you able to see on your TV? Do you see the normal Linux start-up messages in the frame buffer console? This would assume that you're trying to use your TV as a PC monitor. If so, is there an X11 GUI available to you on your TV or just a text mode login prompt. To answer your question, when you are already running an X server, and you issue a ctrl-alt-backspace, it will cause the X-server you are running to abort. If you are running a managed display (like running under gdm or kdm or xdm), then it will re-display a gui login screen as the new X-server starts running. If you are trying to get an X server running for the first time, and the automatic configuration scripts don't help, try running the startx command directly from a command prompt. If you need a special xorg.xonf file in order to run it on a different display than your usual X11 device, it can be specified as an argument to the startx command. You will of course then be running a 2nd X-server, one on your monitor, and a 2nd on your TV. I suggest this method as it is generally easier to see (or capture) the raft of messages sent to your screen, and possibly see the error messages of why it isn't working (if you can separate them from the rest of the cruft sent to the screen). If nothing else, invoke it with a "2>&1 > X11.log" trailer and look at the X11.log file after it dies for your messages. Remember that you might need to specify the :1 display name if you already have a first X-server running as DISPLAY :0. -- Kevin J. Cummings [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Registered Linux User #1232 (http://counter.li.org) _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
