Can you post your complete Xorg.conf file that you are using. I cant see anything obviously different from my setup at the moment other than the list of extensions loaded.
John > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:ivtv-devel- > [EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] > Sent: 31 December 2004 04:41 > To: [email protected] > Subject: [ivtv-devel] PVR350 X output issues using ivtv-0.2.0-rc3, ivtv- > dev > > Hi, > Over break I decided to rebuild my myth system to use LVM. The previous > system was gentoo based, 2.4 kernel, and used the ivtv-0.1.9 from about > april or so. Everything worked really well, including using the video out > from the PVR350 via Xwindows (Xfree 4.3). As a result, I'm pretty > confident of my hardware, since this ran for months > > I've rebaselined my box, using gentoo-dev-sources 2.6.9-r9, and Xorg > 6.8.0-r3, and udev. I am using the ivtv-0.2.0-rc3c downloaded from Chris > Kennedy's site (not using the ebuild in gentoo portage). Everything works > really well, ie I can capture video and play it back with mplayer, I can > get the test image using saa7127 test_image=1 on the tvout (composite and > svideo out) and I get great tvout if I load the ivtv_fb while in KDE > 3.3.1like so (from the ivtv.sourceforge.net wiki pages): > /usr/local/bin/test_ioctl -u 0x3000 -p 4 > ivtvfbctl /dev/fb1 -noglobalalpha -localalpha > ivtvfbctl /dev/fb1 -globalalpha -nolocalalpha -alpha 0 > dd if=/dev/video of=/dev/video16 bs=64k > > This will show great video and soundout of whatever channel is default (I > have not tried changing the channel). I have let this run for 30 minutes > or so with no issues. > > The issue that I am having is when I try to start using the pvr video out > with Xwindows. The end result is that I get a black screen, with a large > X mouse cursor in the center of the screen. No input from the keyboard or > the mouse are accepted. I can ssh into it from another box. Killing X > does no good when I try to get back to the console (either > ctrl-alt-backspace or remote kill -9 any X looking process). Here is what > I've done, and what data I've dug up. > > When I type startx with the ServerLayout for the ivtv stuff commented, > everything works fine, I get the nice musical kde startup, picture on the > montior. > > If I comment out the videocard/monitor and related stuff, I get a black > screen, with the Xwindows mouse cursor (not kde mousecursor). ie a big X > in the middle of the tvscreen that can't be moved. no kde startup music > either. > > 1. I've installed the X11 driver per the directions in the ivtvdev_drv_o > (and I found the site at http://membres.lycos.fr/badzzzz/ and have > downloaded the latest binary driver with the same results). > 2. Relevant xorg.conf stuff (note: I've commented out any reference to > my other video card to rule out conflicts with the video (I've tried a > radeon 8500 and an old matrox MGA card)): > > Section "ServerLayout" > Identifier "ivtv tv" > Screen 0 "IVTV TVOut" 0 0 > InputDevice "Mouse0" "CorePointer" > InputDevice "Keyboard0" "CoreKeyboard" > EndSection > Section "Monitor" > Identifier "TV" > HorizSync 30-68 > VertRefresh 50-120 > Mode "720x480" > # D: 34.563 MHz, H: 37.244 kHz, V: 73.897 Hz > DotClock 34.564 > HTimings 720 752 840 928 > VTimings 480 484 488 504 > Flags "-HSync" "-VSync" > EndMode > EndSection > ection "Device" > Identifier "ivtv" > # Driver "fbdev" > Driver "ivtvdev" > Option "fbdev" "/dev/fb/1" #note I have tried /dev/fb1 which udev > creates as a symlink to /dev/fb/1 > # Option "ivtv" "/dev/fb1" > ### change the busid to whatever is reported by lspci. Note that > ### output of lspci is hex, so add a preceding "0x" to the BusID > # Xorg -scanpci returned this number (which is decimal) > BusID "PCI:0:8:0" > Section "Screen" > Identifier "IVTV TVOut" > Device "ivtv" > Monitor "TV" > DefaultDepth 24 > DefaultFbBpp 32 > Subsection "Display" > Depth 24 > FbBpp 32 > Modes "720x480" > EndSubsection > EndSection > > 2. My Xorg.log has no really interesting stuff, other than the only error > in the log: > (EE) IVTVDEV(0): FBIOPAN_DISPLAY: Invalid argument > > I've seen on a previous post that this isn't a relavant error. I've > posted my entire Xorg.0.log at > http://watsonweb.dnsalias.org/ivtv/Xorg.0.log-LOCKEDUPIVTV > > There is nothing remotely intersting in any of my syslogs (I use metalog). > If it would help, I've posted them here: > (from /var/log/everything) > http://watsonweb.dnsalias.org/ivtv/everything_log > > (from /var/log/kernel) > http://watsonweb.dnsalias.org/ivtv/kernel_log > > An interesting thing to note is that if I leave the computer running, the > picture starts getting white dots on it, at apparently random places. It > starts off black with the X mouse cursor, but degrades. > > I do want to thank in advance anyone who takes the time to read this, and > to the developer a big thankyou, both from myself and my family who enjoy > the fruits of your efforts. > > L8R... > > Randy > > > > > > > > > ------------------------------------------------------- > The SF.Net email is sponsored by: Beat the post-holiday blues > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > _______________________________________________ > ivtv-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/ivtv-devel ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ ivtv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
