Chapman McDaniel wrote: > Thanks for the reply Kevin. I did install the binaries from the ATRPMs > repository, and am running an X11 Gui with gnome on my video card per > the default FC5 install. It sounds like the dual-X-server setup is what > I am looking for -- assuming that it isn't too difficult to set them up > to clone each other.
OK, you're running a default FC5 install. If you have a graphical login screen, you are probably running GDM to provide it to you. GDM is the Gnome Display Manager, and by default, it controls only display :0. Your /etc/X11/xorg.conf file is configured for your video card. It must be working right, because X is running on your system. > After a control-alt-backspace, I don't see anything on either screen(and > never have, on any of my ctl-alt-back adventures). I'm not presented > with a gui or text logon screen. The screen turns off for a second, > then I have a black (but definitely on) monitor. I'm not entirely sure > I am running a display manager (still relatively new to linux, learning > a lot, reading lots of manpages).. is there a way for me to check > that? From reading the manpages, it sounds like my choice to install > both KDE and Gnome may have caused FC5 not to install a display > manager. Is this correct? How should a display manager/xinit behave on > a control-alt-backspace? If you kill your X server via Ctrl-Alt-Backspace, the display manager is supposed to notice this, and restart another X server (ie, run GDM again for you to login through). You can double check this by lookgin at your /etc/inittab file. You should find line like: id:5:initdefault: This indicates that your system will run X11 whenever you start it (the system will enter runlevel 5, which includes running your X11 display manager). If instead, it looks like: id:3:initdefault: then your system is still running in text mode. Since you indicated that your monitor turns black after a Ctrl-Alt-Backspace, it seems that you have successfully terminated your X11 server. The question remains as to why another session was not presented to you by the display manager.... > Pre-IVTV dying, I would see a green screen on boot during udev load, I > assume as the framebuffer was detected. Now, I don't see that. I'm > going to add another root partition under LVM tonight and reinstall FC5 > and go at it again, see if I can get it working, but if anyone can think > of a way to recover the IVTV functionality, I'd love to give it a try. Check out your log files. Look in /var/log/messages for your last boot. You should see something similar to: ivtv0-osd: fb1: cx23415 TV out frame buffer device If so, you've properly configured the frame buffer on your PVR-350. It might say fb0 (instead of fb1) if you have no frame buffer configured for your video card. (I do, I appended the vga=791 line to my grub.conf boot line.) If this is the case, then you need to configure an X-server to run on the PVR-350 framebuffer. Herein lies the big problem. Unless you have a second keyboard/mouse that you can use with the second X-server, you will either need to run it without one, or disable your primary X server (thus the C-A-B suggestion). The reason is that 2 X11 servers sharing the same keyboard/mouse will get very confusing trying to figure out which server gets the keyboard input you are typing.... Of course, all of this assumes that you are comfortable running programs in Linux text mode and can get yourself logged into one of the text consoles after you have killed X11. Usually this is accomplished via the Ctrl-Alt-F1 key-sequence. This should bring up a text console, with a login prompt for you. Use the same userid/password you used in the gui login screen. (I think this is the step you missed from before. When you killed the X server, you remained in the X11 virtual console, which is now black. I think you just needed to switch to a text console in order continue to work. You might want to verify that the following line exists in your inittab: 1:12345:respawn:/sbin/mingetty tty1 If so, you should have at least 1 text console you can login on!) If you can get this far, you should save a copy of your xorg.conf file (in case you really screw it up!) before starting the necessary modifications to try and get an X-server running on your TV. I have heard that some people have configured the Hauppauge remote control as their pointing device, but you'll have to google around to figure out how to make it work. WARNING: I have not attempted any of this myself! Its been a while since I've even run multiple X-servers on the same VGA card (in different virtual consoles), and you're trying to run a server on a different video device. You can start an X-server manually via a "startx" command. Look at its man page for options on how start a server on your :1 display, and how to specify a different xorg.conf file than the system default. After you have it running manually, you can look into how to modify the GDM configuration file to start it automatically. > Chapman McDaniel > > > On 6/4/06, *Kevin J. Cummings* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > 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 > > <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] <mailto:[EMAIL PROTECTED]> > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]> > Registered Linux User #1232 (http://counter.li.org) > > _______________________________________________ > ivtv-users mailing list > [email protected] <mailto:[email protected]> > http://ivtvdriver.org/mailman/listinfo/ivtv-users > > > > ------------------------------------------------------------------------ > > _______________________________________________ > ivtv-users mailing list > [email protected] > http://ivtvdriver.org/mailman/listinfo/ivtv-users -- 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
