| LinHES Forums http://forum.linhes.org/ |
|
| desprate for help w/tvout pvr350 searched to no avail http://forum.linhes.org/viewtopic.php?f=2&t=2745 |
Page 1 of 1 |
| Author: | rkremser [ Wed Oct 20, 2004 2:14 pm ] |
| Post subject: | desprate for help w/tvout pvr350 searched to no avail |
Ok, I'm getting annoyed with this now. I am using r4v4 and have a stable system can record, watch live tv. Everything i want to, except for the tv out. I've tried to follow the wiki which ended by rebooting to a blinking cursor which i didn't know how to get rid of. So i made a clean install of v4 and tried another guide (http://ivtv.writeme.ch/tiki-index.php?page=TvOutHowto) still same results while more promising. I get the color bars on the screen, even get live tv with the dd if=/dev/video of=/dev/video16 bs=64k command. Again after restart i'm left with a blinking cursor. Other than simple trouble shooting of how to fix this. Is there any way to change settings after i get to the point of a blinking cursor? I have heard about ssh sessions but i'm somewhat new to linux and have never done this before.(also only other computer is windows so not sure if possible) Any help would be great. |
|
| Author: | ceenvee703 [ Wed Oct 20, 2004 2:52 pm ] |
| Post subject: | |
Can't help with the PVR-350 setup but yes, it's possible to connect via ssh to your Linux box via Windows. One way is via PuTTY: http://www.chiark.greenend.org.uk/~sgtatham/putty/ Type in the IP number of your Linux box, choose to connect via ssh, then login with (default) username mythtv, password mythtv. |
|
| Author: | rkremser [ Wed Oct 20, 2004 3:17 pm ] |
| Post subject: | |
ahhh, much better. Well now I can do this so i suppose i can edit files to get them to work if i get stuck at the blinking cursor. Now any suggestions on fixing the blinking cursor? |
|
| Author: | Human [ Thu Oct 21, 2004 10:00 am ] |
| Post subject: | |
The blinking cursor probably indicates that X Windows (aka 'X') failed to start. (Remember, tvout on the PVR-350 makes the PVR-350 into a pseudo video card for X.) If you had a monitor hooked up to the computer, you could switch to the first virtual terminal with CTRL-ALT-F1, log in as root, and try running 'startx' to see why X fails to start. (You may be able to do the same thing via ssh, though it's been a while since I've tried such a thing.) If you have no virtual consoles (i.e. you hit CTRL-ALT-F1 and see nothing), ivtv-fb may be hosing them. There's a fix, though. Make this edit to /etc/lilo.conf and rerun lilo, like so: 1. # vi /etc/lilo.conf 2. At the end of the big append line toward the end of the file, add video=vc:0-0 right after nomce Be sure there's a single space between the entires. 3. # lilo Upon reboot, you should have access to your virtual consoles again. You should also double-check some of your steps regarding your X Driver, frame buffer device file (/dev/fb0? /dev/fb1?), and busID for your PVR-350. |
|
| Author: | rkremser [ Thu Oct 21, 2004 10:53 am ] |
| Post subject: | |
Ok as dumb as it may sound when i was running through the guide i ended up replacing all of XF11Config-4 with what was in the guide and not adding it to the existing file. I was able to use ssh to get into the box and upon changing my mistake (luckly i backed up the origional) Everything seems to be working perfectly. Now just to get my remote working and I may just be done till the next version comes out. THanks for the help |
|
| Author: | rkremser [ Tue Nov 09, 2004 6:36 pm ] |
| Post subject: | |
hopefully someone is still following this but i got suck back in the same position after a reformat. This time though if i ran startx from an ssh terminal it will load and work fine. Again not on the first time though there are errors that come up on the second time though. root@mythtv:/etc/X11 # startx xauth: creating new authority file /root/.Xauthority xauth: creating new authority file /root/.Xauthority X: warning; process set to priority -11 instead of requested priority -10 XFree86 Version 4.3.0 (Debian 4.3.0-0ds4 20030416150820 dstone@aedificator) Release Date: 18 March 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.21-pre5 i686 [ELF] Build Date: 16 April 2003 Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.4.25-chw (root@km_dev.mysettopbox.tv) (gcc version 3.3.2 20030812 (Debian prerelease)) #1 Sat Apr 10 15:46:31 PDT 2004 Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.0.log", Time: Wed Nov 10 04:31:24 2004 (==) Using config file: "/etc/X11/XF86Config-4" Skipping "/usr/X11R6/lib/modules/fonts/libspeedo.a:spencode.o": No symbols found (EE) FBDEV(0): FBIOPAN_DISPLAY: Invalid argument Couldn't load XKB keymap, falling back to pre-XKB keymap Warning: font renderer for ".pcf" already registered at priority 0 Warning: font renderer for ".pcf.Z" already registered at priority 0 Warning: font renderer for ".pcf.gz" already registered at priority 0 Warning: font renderer for ".snf" already registered at priority 0 Warning: font renderer for ".snf.Z" already registered at priority 0 Warning: font renderer for ".snf.gz" already registered at priority 0 Warning: font renderer for ".bdf" already registered at priority 0 Warning: font renderer for ".bdf.Z" already registered at priority 0 Warning: font renderer for ".bdf.gz" already registered at priority 0 Warning: font renderer for ".pmf" already registered at priority 0 any thoughts? |
|
| Author: | Human [ Tue Nov 09, 2004 10:25 pm ] |
| Post subject: | |
(EE) FBDEV(0): FBIOPAN_DISPLAY: Invalid argument That line indicates the reason X didn't start, but it's admittedly a little cryptic, at least to me. It seems to mean that fbdev 0 isn't responding to some request, command, or what have you. My guess is that it's something to do with your Device section of your XF86Config-4 file. Mine looks like this: Section "Device" Identifier "Hauppauge PVR 350 iTVC15 Framebuffer" Driver "fbdev" ### change fb1 to whatever number you got in the previous section Option "fbdev" "/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 BusID "1:0x06:0" EndSection Do you have the right device file listed on the Option line? In my case, it's /dev/fb1 because there's already a framebuffer device on the motherboard, which is recognized as /dev/fb0, and I want to use my PVR-350 card. What about the BusID? Is it correct? Double-check these things and let us know. If you need more detailed help, just reply to this thread. |
|
| Page 1 of 1 | All times are UTC - 6 hours |
| Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |
|