Author |
Message |
aspain
|
Posted: Wed Jan 11, 2006 7:24 pm |
|
Joined: Fri May 06, 2005 6:31 am
Posts: 79
Location:
Spain
|
Anyone can help me ?
When I execute : perl ./pvr.pl
I receive a 404 (Not Found) for file R5Alpha15-pvr350.pl
Here is the log
--20:20:31-- http://dc1.snapperworld.net/files/mytht ... -pvr350.pl
=> `R5Alpha15-pvr350.pl'
Resolving dc1.snapperworld.net... 66.129.44.59
Connecting to dc1.snapperworld.net[66.129.44.59]:80... connected.
HTTP request sent, awaiting response... 404 Not Found
20:20:40 ERROR 404: Not Found.
|
|
Top |
|
|
SnapperDragon
|
Posted: Thu Jan 12, 2006 6:31 pm |
|
Joined: Sat Feb 28, 2004 10:04 am
Posts: 173
Location:
Canton, MI USA
|
Sorry, but I never tested that version, so there is no script for it...
Currently, the following are supported:
R4v5
R5A12
R5A16
R5A20
R5A22
R5A26
R5A30.1
R5A30.2
I don't have a copy of R5A15 so I can't test this version. You can try downloading the R5A12 or R5A16 and see if you can make them work, but there may be specific differences in R5A15 that may not work properly with either script. In any case, don't use a system that you can not afford to trash in the event this does not work.
These direct links should work if you would like to give it a shot...
http://dc1.snapperworld.net/files/mytht ... -pvr350.pl
http://dc1.snapperworld.net/files/mytht ... -pvr350.pl
_________________ MythRig: Shuttle SN41G2 + PVR-350->TV + KnoppMyth R5Beta7
Last edited by SnapperDragon on Sat Feb 11, 2006 5:20 pm, edited 1 time in total.
|
|
Top |
|
|
ryanpatterson
|
Posted: Sun Jan 15, 2006 5:29 pm |
|
Joined: Fri Aug 26, 2005 9:54 pm
Posts: 617
|
For R5A30.1 I was able to get my pvr-350 to work by running the R5A26 script then downloading and installing the pvr-350 framebuffer driver.
enter these commands as root to install the driver:
Code: cd /tmp wget http://dl.ivtvdriver.org/xdriver/0.10.6/ivtvdev_drv.o.bz2 bunzip2 ivtvdev_drv.o.bz2 install -m 0444 ./ivtvdev_drv.o /usr/X11R6/lib/modules/drivers/
|
|
Top |
|
|
jdinnis
|
Posted: Mon Jan 16, 2006 8:55 pm |
|
Joined: Sun Jan 15, 2006 2:35 pm
Posts: 10
|
I am having trouble getting this to work. I am running KnoppMyth R5Alpha30 with a pvr350 and a RIVA nVidia based VGA card. I know the script is not set up for R5Alpha30, so I tried to use the manual equivlant from
http://knoppmythwiki.org/index.php?page ... stallation
Problem is my /var/log/messages doesn't show any information about a frame buffer device. I tied another route to get the info, that which is quoted below. This gives me fb0, so I used that, along with the BUSID to modify /etc/X11/XF86Config-4 as described above and as your script does. I then did a cold boot (more than 1 minute power off).
When I reboot, X fails to start, and I get the following error in the debug window.
<snip>
(EE) open /dev/fb0: No such device
(EE) Screen 0 deleted because of no matching config section
(EE) Device(s) detected, but none match those in the config file.
Fatal server error:
no screens found
<end>
In the detailed X output, I see that IVTVdev does load, but when it gets to the section for the framebuffer, something has gone wrong, note that the PCI BUSID in the output below is that of my VGA card, the BUSID of my pvr350 is 01:09:0. I double checked the XF86Config-4 file and it has the right PCI BUSID.
<snip>
(II) Primary Device is: PCI 01:06:0
(--) Chipset PVR-350 found
(EE) open /dev/fb0: No such device
(EE) Screen 0 deleted because of no matching config section
(II) UnloadModule: "ivtvdev"
(EE) Device(s) detected, but none match those in the config file.
<end>
Have done this several times on clean installs, and tried setting vga=normal in /etc/lilo.conf then doing lilo -v
same result each time.
It seems that the pvr350 is not being recognized as a fb device at boot time. The info in /var/logs/messages seems to support this, as the only time it is listed as a fb is when I did
/sbin/modprobe ivtv-fb
when I do this, I get the following in /var/log/messages
kernel: ivtv0-osd: fb0: iTVC15 TV out frame buffer device
so not sure what I am doing wrong.
configuration details
KnoppMyth R5Alpha30
CPU Athlon 64 3200+
MB MSI K8N Neo4F (NFORCE CK804)
1GB RAM
15GB HDD
Hauppage pvr350
VGA nvidia RIVA based card,make and model unknown
SnapperDragon wrote: For the FB number, use: cat /var/log/messages | grep "ivtv-osd: fb". If that does not work for the FB number, try this: /sbin/modprobe ivtv-fb; dmesg | grep "x"ivtv-osd: fb"
Please use either this thread or PM me for issues specifically concerning these scripts.
|
|
Top |
|
|
SnapperDragon
|
Posted: Fri Jan 20, 2006 9:53 pm |
|
Joined: Sat Feb 28, 2004 10:04 am
Posts: 173
Location:
Canton, MI USA
|
ryanpatterson, thanks for the heads up on what to do. I'm hoping to bring my box down to the dungeon and swap disks and update the script for R5A30.1 possibly on Saturday 1/21/2006. Your post should allow me to make the update quicker since you have already found out what is different.
Thanks.
_________________ MythRig: Shuttle SN41G2 + PVR-350->TV + KnoppMyth R5Beta7
|
|
Top |
|
|
SnapperDragon
|
Posted: Sun Jan 22, 2006 1:44 pm |
|
Joined: Sat Feb 28, 2004 10:04 am
Posts: 173
Location:
Canton, MI USA
|
Support was just added for R5A30.1. I did minimal testing, but when running the script, it resulted in a working config for me the first time out.
_________________ MythRig: Shuttle SN41G2 + PVR-350->TV + KnoppMyth R5Beta7
|
|
Top |
|
|
tdhutton
|
Posted: Tue Jan 31, 2006 3:04 pm |
|
Joined: Tue Jan 31, 2006 1:18 pm
Posts: 2
|
First of all, I realize that I am using an unsupported version. This is my first attempt at Myth, and I just grabbed the standard ISO. I wish I would have gotten an older version now.
Anyway, I tried to run the script anyway. I made it through to pvr.pl when checks version. I decided to select option 6. The script must be broken because it didn't pull the R5A30.1 script. Here is the screen print:
6
Downloading script R5 Alpha 30.2-pvr350.pl
Please run that script in order to setup PVR-350 TV-out.
The command to use is: perl ./R5 Alpha 30.2-pvr350.pl -i
Use no options to see the availalbe options, or -d for debug mode.
root@mythtv:/tmp# ls
dead-files mpg-files pvr.pl ssh-yvBjWW4592 wget-pvr.log2
getpvr.pl nuv-files rm-dead-files wget-getpvr.log wget-pvr.log3
Since it didn't get the script, I decided to get it myself. So, I did this:
wget http://dc1.snapperworld.net/files/mytht ... -pvr350.pl
Then,
chmod +x R5Alpha30.1-pvr350.pl
I then ran this script.
root@mythtv:/tmp# perl ./R5Alpha30.1-pvr350.pl -i
Creating new /etc/X11/XF86Config-4 file
Need to update your MythTV config so that it knows to use the
PVR-350 as outut for TV playback. Press ENTER to continue
OK, that should do it...your MythBox should now output to your
TV set. Make sure you have the cables correctly plugged in and
reboot your system.
Press ENTER to exit.
When I reboot, the mythfrontend shows on my tvout (through RCA not SVIDEO). But, when I select watch TV, the screen goes black. So, the hardware MPEG2 decoder isn't working. Turned the Hardware MPEG2 decode off through the myth frontend settings menu and I was able to display the TV.
I have tried multiple things to try to fix this, but I am at a loss.
|
|
Top |
|
|
jdinnis
|
Posted: Tue Jan 31, 2006 5:22 pm |
|
Joined: Sun Jan 15, 2006 2:35 pm
Posts: 10
|
I'n not sure what the differences are, but I used the R5A30.1 script on my install of 55A30.2 successfully. The one thing that I did do differently (and per the instrustions in the script) was to run the script once, reboot, and then run the script again. This worked for me.
John
|
|
Top |
|
|
tdhutton
|
Posted: Tue Jan 31, 2006 8:17 pm |
|
Joined: Tue Jan 31, 2006 1:18 pm
Posts: 2
|
I tried to run the script, reboot, run script again. This didn't work either. I get a black screen when I try to watch live TV. I am able to view an MPEG though with these settings. So, I am not sure why the recorded MPEG will play, but live TV is just black.
Update - I figured out the program. I need to specify /dev/video16 under the TV setup menu on the Use pvr-350 hardware screen.
Last edited by tdhutton on Thu Feb 02, 2006 8:38 am, edited 1 time in total.
|
|
Top |
|
|
ke6oms
|
Posted: Wed Feb 01, 2006 3:01 pm |
|
Joined: Tue May 25, 2004 2:33 pm
Posts: 42
|
SnapperDragon, I must send you my most heartfelt thanks. I recently was forced to upgrade due to a catastrophic failure (kernel oops from something) and was having one heck of a time getting R5A16 to display anything except the dreaded horizontal lines. I had it working at one point, but had to do a reinstall and my second attempt was a failure. Ran your script once, and when it rebooted, MythTV was up on my tv like it was meant to be. I didn't
even have to run the script the second time, since it seems what I screwed up was fixed in the first pass run of the script.
In short, you rule.
_________________ Athlon 700 + PVR-350. KnoppMyth R5A16. ReiserFS on an LVM volume for myth data. Thanks to SnapperDragon, everything seems quite happy.
|
|
Top |
|
|
fjdowney1108
|
Posted: Sat Feb 04, 2006 12:48 am |
|
Joined: Thu Feb 02, 2006 10:13 pm
Posts: 2
|
Awesome script. Works great.
Thanks SnapperDragon
|
|
Top |
|
|
achilles1942
|
Posted: Sun Feb 05, 2006 4:06 pm |
|
Joined: Sun Nov 13, 2005 7:27 pm
Posts: 14
|
i remember seeing something at the end of the process that told me how to go back to the vga output but i forgot it. Could you please tell me what it is and if i can easily go back to the tvout
|
|
Top |
|
|
fueledbyramen
|
Posted: Thu Feb 09, 2006 2:10 am |
|
Joined: Wed Feb 08, 2006 2:49 am
Posts: 1
|
I was having problems with R5A30.2 (blank/green tinted screen) until i read Mikael's post and manually used the BusID I got from using
Code: lspci -X | grep iTV
The script was giving me "Busid=PCI:00:02:0" which i changed to "PCI:0:18:0" as per the aforementioned command's output. I just wanted to thank Mikael and recommend that anyone who is having problems with R5A30.2 like I was, should try using this method for getting BusID. Thanks for the help everyone .
Mikael wrote: For some reason the script kept on setting BusID as "00:00:0". I manually edited /etc/X11/XF86Config-4 based on the output of "lspci -X".
mikael@mythtv:~$ cat /var/log/messages | grep "ivtv0-osd: fb" Nov 3 08:39:48 mythtv kernel: ivtv0-osd: fb1: iTVC15 TV out frame buffer device
mikael@mythtv:~$ lspci -X | grep iTV PCI:0:16:0 Multimedia video controller: Internext Compression Inc iTVC15 MPEG-2 Encoder
--------Part of /etc/X11/XF86Config-4----------
Section "Device" Identifier "Hauppauge PVR 350 iTVC15 Framebuffer" Driver "ivtvdev"
### change fb1 to whatever number you got in the previous section Option "fbdev" "/dev/fb1" Option "ivtvdev" "/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 "PCI:0:16:0" EndSection
------------------------------------------------
|
|
Top |
|
|
SnapperDragon
|
Posted: Sat Feb 11, 2006 5:17 pm |
|
Joined: Sat Feb 28, 2004 10:04 am
Posts: 173
Location:
Canton, MI USA
|
To restore your original settings, rerun the script using the "-r" option instead of -i.
Ad for the botched up BUSID number, I'll have to actually build R5A30.2 and test this. The script I posted was not tested but I took it on faith from someone else that no changes were needed. I'll try and see if the glitch happens 100% or not. Thanks for the heads up.
_________________ MythRig: Shuttle SN41G2 + PVR-350->TV + KnoppMyth R5Beta7
|
|
Top |
|
|
SnapperDragon
|
Posted: Sat Feb 11, 2006 5:19 pm |
|
Joined: Sat Feb 28, 2004 10:04 am
Posts: 173
Location:
Canton, MI USA
|
This gives me a new idea for the script to make it a little more flexible..
For all the settings that it "detects", I'll add the ability to override in the event the script fails to get the right values giving the user a chance to put in the correct ones.
_________________ MythRig: Shuttle SN41G2 + PVR-350->TV + KnoppMyth R5Beta7
|
|
Top |
|
|