| Author |
Message |
|
mongo
|
 Posted: Fri Sep 17, 2004 9:28 am |
|
|
Joined: Fri Sep 17, 2004 6:16 am
Posts: 8
|
Ok here it goes....
Been following MYTV for awile, trolling the mailing list and the boards here...
From what I was reading pvr-250 & pvr-350 recording stable, pvr-350 output not so hot...
So when the Tivo died, I built a system with a Pundit & pvr-250. I went ahead and put together a second system with old parts (pIII 733) and a 350, with the plan if I have too much trouble with the output, I'll switch out to a Nvida video card.
the outcome... 350's output has been ROCK solid, Live TV, recording, xvid, avi, DVD playback, DVD ISOs (Yes, Mythvideo will play an ISO), you name it. A complete shock to me after all the trolling...
but I having big issues of keeping the encoders up.
Quote: Sep 5 10:54:43 mythtv01 kernel: saa7115[0] set audio: 0x02
Sep 5 10:54:43 mythtv01 kernel: saa7115[0]: decoder set picture bright=128 contrast=63 saturation=64 hue=0
Sep 5 10:54:43 mythtv01 kernel: saa7115[0]: decoder set picture bright=128 contrast=63 saturation=63 hue=0
Sep 5 10:54:43 mythtv01 kernel: saa7115[0]: decoder set picture bright=127 contrast=63 saturation=63 hue=0
Sep 5 10:55:03 mythtv01 last message repeated 5 times
Sep 5 10:55:03 mythtv01 kernel: saa7115[0]: decoder set size
Sep 5 10:55:03 mythtv01 kernel: Setting full NTSC width
Sep 5 10:55:03 mythtv01 kernel: Setting full NTSC height
Sep 5 10:55:04 mythtv01 kernel: ivtv: 100 ms time out waiting for firmware
Sep 5 10:55:04 mythtv01 kernel: ivtv: api call 0x000000c9
Sep 5 10:55:04 mythtv01 kernel: ivtv: init error 1. Code -16
Sep 5 10:55:05 mythtv01 kernel: ivtv: 100 ms time out waiting for firmware
Sep 5 10:55:05 mythtv01 kernel: ivtv: api call 0x000000c7
Sep 5 10:55:05 mythtv01 kernel: ivtv: init error 2. Code -16
Sep 5 10:55:06 mythtv01 kernel: ivtv: 100 ms time out waiting for firmware
Sep 5 10:55:06 mythtv01 kernel: ivtv: api call 0x000000b9
Sep 5 10:55:06 mythtv01 kernel: ivtv: init error 3. Code -16
Sep 5 10:55:07 mythtv01 kernel: ivtv: 100 ms time out waiting for firmware
Sep 5 10:55:07 mythtv01 kernel: ivtv: api call 0x000000bb
Sep 5 10:55:07 mythtv01 kernel: ivtv: init error 4. Code -16
Sep 5 10:55:08 mythtv01 kernel: ivtv: 100 ms time out waiting for firmware
Sep 5 10:55:08 mythtv01 kernel: ivtv: api call 0x0000008f
Sep 5 10:55:08 mythtv01 kernel: ivtv: init error 5. Code -16
Sep 5 10:55:09 mythtv01 kernel: ivtv: 100 ms time out waiting for firmware
Sep 5 10:55:09 mythtv01 kernel: ivtv: api call 0x00000091
Sep 5 10:55:09 mythtv01 kernel: ivtv: init error 6. Code -16
Sep 5 10:55:10 mythtv01 kernel: ivtv: 100 ms time out waiting for firmware
Sep 5 10:55:10 mythtv01 kernel: ivtv: api call 0x00000099
Sep 5 10:55:10 mythtv01 kernel: ivtv: init error 7. Code -16
Sep 5 10:55:11 mythtv01 kernel: ivtv: 100 ms time out waiting for firmware
Sep 5 10:55:11 mythtv01 kernel: ivtv: api call 0x00000095
Sep 5 10:55:11 mythtv01 kernel: ivtv: init error 8. Code -16
Sep 5 10:55:12 mythtv01 kernel: ivtv: 100 ms time out waiting for firmware
Sep 5 10:55:12 mythtv01 kernel: ivtv: api call 0x00000097
Sep 5 10:55:12 mythtv01 kernel: ivtv: init error 9. Code -16
Sep 5 10:55:13 mythtv01 kernel: ivtv: 100 ms time out waiting for firmware
Sep 5 10:55:13 mythtv01 kernel: ivtv: api call 0x000000b1
Sep 5 10:55:13 mythtv01 kernel: ivtv: init error 10. Code -16
Sep 5 10:55:14 mythtv01 kernel: ivtv: 100 ms time out waiting for firmware
Sep 5 10:55:14 mythtv01 kernel: ivtv: api call 0x000000c5
Sep 5 10:55:14 mythtv01 kernel: ivtv: init error 11. Code -16
Sep 5 10:55:15 mythtv01 kernel: ivtv: 100 ms time out waiting for firmware
Sep 5 10:55:15 mythtv01 kernel: ivtv: api call 0x000000bd
Sep 5 10:55:15 mythtv01 kernel: ivtv: init error 12. Code -16
Sep 5 10:55:16 mythtv01 kernel: ivtv: 100 ms time out waiting for firmware
Sep 5 10:55:16 mythtv01 kernel: ivtv: api call 0x0000009b
Sep 5 10:55:16 mythtv01 kernel: ivtv: init error 13. Code -16
Sep 5 10:55:17 mythtv01 kernel: ivtv: 100 ms time out waiting for firmware
Sep 5 10:55:17 mythtv01 kernel: ivtv: api call 0x0000009d
Sep 5 10:55:17 mythtv01 kernel: ivtv: init error 14. Code -16
Sep 5 10:55:18 mythtv01 kernel: ivtv: 100 ms time out waiting for firmware
Sep 5 10:55:18 mythtv01 kernel: ivtv: api call 0x0000009f
Sep 5 10:55:18 mythtv01 kernel: ivtv: init error 15. Code -16
Sep 5 10:55:19 mythtv01 kernel: ivtv: 100 ms time out waiting for firmware
Sep 5 10:55:19 mythtv01 kernel: ivtv: api call 0x000000a1
Sep 5 10:55:19 mythtv01 kernel: ivtv: init error 16. Code -16
Sep 5 10:55:20 mythtv01 kernel: ivtv: 100 ms time out waiting for firmware
Sep 5 10:55:20 mythtv01 kernel: ivtv: api call 0x000000d0
Sep 5 10:55:20 mythtv01 kernel: ivtv: init error 17. Code -16
its happening daily, on both systems. I'm guessing CK's driver is the way to go, but not sure whats a good stable version.
*Edit* I know I'm missing what modules to load, will check it & post when I get home from work.
Last edited by mongo on Fri Sep 17, 2004 2:05 pm, edited 1 time in total.
|
|
| Top |
|
 |
|
gr8nash
|
Posted: Fri Sep 17, 2004 10:22 am |
|
|
Joined: Thu Apr 01, 2004 10:44 am
Posts: 677
Location:
WA
|
there isnt a stable release yet.. its Not officialy stable, and there isnt a version people agree is stable that i have seen. everyone uses a totaly different version.. my recomendation is jump in with a newer one and see how it goes. i would imagine that the 250 side of ivtv would be pretty stable by now.
here is the links to kennedy's cvs.
http://67.18.1.101/~ckennedy/ivtv/
|
|
| Top |
|
|
|
Xsecrets
|
Posted: Fri Sep 17, 2004 10:32 am |
|
|
Joined: Mon Oct 06, 2003 10:38 am
Posts: 4978
Location:
Nashville, TN
|
|
If you managed to get smooth divx/xvid playback on a 733 you definitely need to post a howto somewhere, because from everything I've read even a 3.6 EE won't give you smooth playback with the pvr350 tvout.
_________________ Have a question search the forum and have a look at the KnoppMythWiki.
Xsecrets
|
|
| Top |
|
|
|
cesman
|
Posted: Fri Sep 17, 2004 11:31 am |
|
|
Joined: Fri Sep 19, 2003 7:05 pm
Posts: 5088
Location:
Fontana, Ca
|
It is interesting when someone states they got something working yet don't post how they did it...  Perhaps after R5 is done, I should just use it myself and not release it...
_________________
cesman
When the source is open, the possibilities are endless!
|
|
| Top |
|
|
|
ceenvee703
|
Posted: Fri Sep 17, 2004 11:53 am |
|
|
Joined: Fri Apr 02, 2004 10:08 am
Posts: 1637
Location:
Virginia, USA
|
Quote: It is interesting when someone states they got something working yet don't post how they did it...
Maybe he will--it's only been a few hours since he posted...
|
|
| Top |
|
|
|
mongo
|
Posted: Fri Sep 17, 2004 12:25 pm |
|
|
Joined: Fri Sep 17, 2004 6:16 am
Posts: 8
|
Quote: It is interesting when someone states they got something working yet don't post how they did it... Perhaps after R5 is done, I should just use it myself and not release it...
Well, I almost followed this post... http://mysettopbox.tv/phpBB2/viewtopic. ... ht=ivtvdevI downloaded the binary ivtvdev driver and configured X, including the lspci part. I didn't change the ivtv driver or anything else... Mind you I was beating my head agaist the wall for a few hours trying to get it to work, until I moved the 350 one slot over... Quote:
root@mythtv02:~ # lspci -v
00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev c4)
Flags: bus master, medium devsel, latency 0
Memory at d0000000 (32-bit, prefetchable) [size=64M]
Capabilities: [a0] AGP version 2.0
Capabilities: [c0] Power Management version 2
00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP] (prog-if 00 [Normal decode])
Flags: bus master, 66Mhz, medium devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 0000c000-0000cfff
Memory behind bridge: d4000000-d7ffffff
Prefetchable memory behind bridge: dc000000-ddffffff
Capabilities: [80] Power Management version 2
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 1b)
Subsystem: VIA Technologies, Inc. VT82C686/A PCI to ISA Bridge
Flags: bus master, stepping, medium devsel, latency 0
00:07.1 IDE interface: VIA Technologies, Inc. VT82C586/B/686A/B PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
Flags: bus master, medium devsel, latency 32
I/O ports at d000 [size=16]
Capabilities: [c0] Power Management version 2
00:07.2 USB Controller: VIA Technologies, Inc. USB (rev 0e) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
Flags: bus master, medium devsel, latency 32, IRQ 5
I/O ports at d400 [size=32]
Capabilities: [80] Power Management version 2
00:07.3 USB Controller: VIA Technologies, Inc. USB (rev 0e) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
Flags: bus master, medium devsel, latency 32, IRQ 5
I/O ports at d800 [size=32]
Capabilities: [80] Power Management version 2
00:07.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 20)
Flags: medium devsel, IRQ 9
00:07.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio Controller (rev 21)
Subsystem: Sigmatel Inc Onboard Audio
Flags: medium devsel, IRQ 10
I/O ports at dc00 [size=256]
I/O ports at e000 [size=4]
I/O ports at e400 [size=4]
Capabilities: [c0] Power Management version 2
00:08.0 Multimedia video controller: Internext Compression Inc iTVC15 MPEG-2 Encoder (rev 01)
Subsystem: Hauppauge computer works Inc.: Unknown device 4000
Flags: bus master, medium devsel, latency 64, IRQ 11
Memory at d8000000 (32-bit, prefetchable) [size=64M]
Capabilities: [44] Power Management version 2
00:0c.0 Network controller: Compaq Computer Corporation Netelligent 10/100 (rev 10)
Flags: bus master, medium devsel, latency 32, IRQ 11
I/O ports at ec00 [size=16]
Memory at df000000 (32-bit, non-prefetchable) [size=16]
Expansion ROM at <unassigned> [disabled] [size=64K]
01:00.0 VGA compatible controller: 3Dfx Interactive, Inc. Voodoo 3 (rev 01) (prog-if 00 [VGA])
Subsystem: 3Dfx Interactive, Inc. Voodoo3 AGP
Flags: 66Mhz, fast devsel, IRQ 11
Memory at d4000000 (32-bit, non-prefetchable) [size=32M]
Memory at dc000000 (32-bit, prefetchable) [size=32M]
I/O ports at c000 [size=256]
Expansion ROM at <unassigned> [disabled] [size=64K]
Capabilities: [54] AGP version 1.0
Capabilities: [60] Power Management version 1
root@mythtv02:~ #
and yea its a VIA chipset... Go figure.
I can post the XF86Config-4 file if anyone wants.
|
|
| Top |
|
|
|
cesman
|
Posted: Fri Sep 17, 2004 1:05 pm |
|
|
Joined: Fri Sep 19, 2003 7:05 pm
Posts: 5088
Location:
Fontana, Ca
|
mongo wrote: Well, I almost followed this post... http://mysettopbox.tv/phpBB2/viewtopic. ... ht=ivtvdevQuote: You almost... What does that mean? Why even post the link if that isn't what you did? Quote: I downloaded the binary ivtvdev driver and configured X, including the lspci part. I didn't change the ivtv driver or anything else...
I can assume you you followed the 350 TV out howto on the ivytv wiki. But that is only because I've read it a few times myself, then used a binary driver. Is that correct? What about ivtv-fb? I'm certain folks would appreciate a more detailed howto...
_________________
cesman
When the source is open, the possibilities are endless!
|
|
| Top |
|
|
|
tvtime
|
Posted: Fri Sep 17, 2004 1:20 pm |
|
|
Joined: Tue Apr 27, 2004 7:37 pm
Posts: 21
|
I already owe Cesman a case of beer...I may as well get one for you too.
If you could post what you did to get flawless PVR350 playback it would be greatly appreciated. 
|
|
| Top |
|
|
|
mongo
|
Posted: Fri Sep 17, 2004 2:02 pm |
|
|
Joined: Fri Sep 17, 2004 6:16 am
Posts: 8
|
cesman wrote: mongo wrote: Well, I almost followed this post... http://mysettopbox.tv/phpBB2/viewtopic. ... ht=ivtvdevQuote: You almost... What does that mean? Why even post the link if that isn't what you did? Quote: I downloaded the binary ivtvdev driver and configured X, including the lspci part. I didn't change the ivtv driver or anything else...
I can assume you you followed the 350 TV out howto on the ivytv wiki. But that is only because I've read it a few times myself, then used a binary driver. Is that correct? What about ivtv-fb? I'm certain folks would appreciate a more detailed howto... On that post above was a link to: http://membres.lycos.fr/badzzzz/Site is now gone The site contained IVTV driver to compile, & ivtvdev X driver (binary), directions on compiling the ivtv and configure X with the ivtvdev driver. So I'm going with memory here... 1. disable kernel FB. edit /etc/lilo.conf and change vga=XXX to vga=normal run lilo & reboot. 2. download ivtvdev_drv.o from *need a place to host file* and copy to /usr/X11R6/lib/modules/drivers/ 3. run lspci, locate the bus info for the 350. In my case 00:08.0 Quote: 00:08.0 Multimedia video controller: Internext Compression Inc iTVC15 MPEG-2 Encoder (rev 01)
Here is a copy of my XF86Config-4 Quote: Section "ServerLayout"
Identifier "XFree86 Configured"
Screen 0 "TV Screen"
InputDevice "PS/2 Mouse" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "ServerFlags"
Option "AllowMouseOpenFail" "true"
EndSection
Section "Files"
RgbPath "/usr/X11R6/lib/X11/rgb"
ModulePath "/usr/X11R6/lib/modules"
FontPath "/usr/X11R6/lib/X11/fonts/misc:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/misc"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo"
FontPath "/usr/X11R6/lib/X11/fonts/PEX"
# Additional fonts: Locale, Gimp, TTF...
FontPath "/usr/X11R6/lib/X11/fonts/cyrillic"
# FontPath "/usr/X11R6/lib/X11/fonts/latin2/75dpi"
# FontPath "/usr/X11R6/lib/X11/fonts/latin2/100dpi"
# True type and type1 fonts are also handled via xftlib, see /etc/X11/XftConfig!
FontPath "/usr/X11R6/lib/X11/fonts/Type1"
FontPath "/usr/share/fonts/ttf/western"
FontPath "/usr/share/fonts/ttf/decoratives"
FontPath "/usr/share/fonts/truetype"
FontPath "/usr/share/fonts/truetype/openoffice"
FontPath "/usr/share/fonts/truetype/ttf-bitstream-vera"
FontPath "/usr/share/fonts/latex-ttf-fonts"
FontPath "/usr/X11R6/lib/X11/fonts/defoma/CID"
FontPath "/usr/X11R6/lib/X11/fonts/defoma/TrueType"
EndSection
Section "Module"
Load "ddc" # ddc probing of monitor
# Load "GLcore"
Load "dbe"
Load "v4l"
Load "extmod"
# Load "glx"
Load "bitmap" # bitmap-fonts
Load "speedo"
Load "type1"
Load "freetype"
Load "record"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "CoreKeyboard"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection
Section "InputDevice"
Identifier "Serial Mouse"
Driver "mouse"
Option "Protocol" "Microsoft"
Option "Device" "/dev/ttyS0"
Option "Emulate3Buttons" "true"
Option "Emulate3Timeout" "70"
Option "SendCoreEvents" "true"
EndSection
Section "InputDevice"
Identifier "PS/2 Mouse"
Driver "mouse"
Option "Protocol" "auto"
Option "ZAxisMapping" "4 5"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "true"
Option "Emulate3Timeout" "70"
Option "SendCoreEvents" "true"
EndSection
Section "Monitor"
Identifier "NTSC Monitor"
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
Section "Device"
Identifier "Hauppauge PVR 350 iTVC15 Framebuffer"
Driver "ivtvdev"
### change fb1 to whatever number you got in the previous section
Option "fbdev" "/dev/fb0"
### 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 "00:08.0"
EndSection
Section "Screen"
Identifier "TV Screen"
Device "Hauppauge PVR 350 iTVC15 Framebuffer"
Monitor "NTSC Monitor"
DefaultDepth 24
DefaultFbbpp 32
Subsection "Display"
Depth 24
FbBpp 32
Modes "720x480"
EndSubsection
EndSection
Section "DRI"
Mode 0666
EndSection
4. change BusID "00:08.0" in the FX86Config to your ID that you got from lspci
5. reboot! should have X desktop on the 350.
*remember* if you don't get the green screen when the module loads try moving the 350 around. don't forget to update the XF86Config-4 with the new busID.
If you have a black screen try:
rm -f /dev/fb0autodetect
rm -f /dev/fb0
mknod /dev/fb0 c 29 1
chmod 666 /dev/fb0
chown root:tty /dev/fb0
I'm looking for a place to host the driver. BTW I did not write the X driver and don't know who did... but THANK YOU!!!!!!!!!!!!!!!!
|
|
| Top |
|
|
|
gr8nash
|
Posted: Fri Sep 17, 2004 2:24 pm |
|
|
Joined: Thu Apr 01, 2004 10:44 am
Posts: 677
Location:
WA
|
Quote: . Sad Perhaps after R5 is done, I should just use it myself and not release it...
and then my world came crashing down....
|
|
| Top |
|
|
|
cesman
|
Posted: Fri Sep 17, 2004 2:40 pm |
|
|
Joined: Fri Sep 19, 2003 7:05 pm
Posts: 5088
Location:
Fontana, Ca
|
gr8nash wrote: and then my world came crashing down.... I was just kidding...
_________________
cesman
When the source is open, the possibilities are endless!
|
|
| Top |
|
|
|
gr8nash
|
Posted: Fri Sep 17, 2004 3:05 pm |
|
|
Joined: Thu Apr 01, 2004 10:44 am
Posts: 677
Location:
WA
|
|
| Top |
|
|
|
mongo
|
Posted: Fri Sep 17, 2004 5:13 pm |
|
|
Joined: Fri Sep 17, 2004 6:16 am
Posts: 8
|
Ok home now... Here is the copy of my /etc/mythtv/modules file.
Quote: alias char-major-81 videodev
alias char-major-61 lirc_i2c
options ivtv debug=1
options tuner type=2
options msp3400 once=1 simple=1
options saa7127 enable_output=1 output_select=1
add below ivtv msp3400 saa7115 saa7127 tuner
add above ivtv lirc_dev lirc_i2c ivtv-fb
Here is a link to the driver http://www.sewell-fam.us/mythtv/ivtvdev_drv.zip
|
|
| Top |
|
|
|
hooverzilla
|
Posted: Sun Sep 19, 2004 10:08 pm |
|
|
Joined: Sun Sep 19, 2004 10:01 pm
Posts: 7
Location:
Ottawa
|
|
Greetings from the great white north. I've followed all the instruction in this thread and I get the green tv screen at the module load but it turn into a black tv screen after a few seconds with a blinking cursor. I can ssh into it and I see that everything appears to be working fine. Has anyone encountered this before ?
|
|
| Top |
|
|
|
mongo
|
Posted: Mon Sep 20, 2004 4:31 am |
|
|
Joined: Fri Sep 17, 2004 6:16 am
Posts: 8
|
hooverzilla wrote: Greetings from the great white north. I've followed all the instruction in this thread and I get the green tv screen at the module load but it turn into a black tv screen after a few seconds with a blinking cursor. I can ssh into it and I see that everything appears to be working fine. Has anyone encountered this before ? ah, yes, Ive seen this on one of my friend's system. the kernel is still trying to use the 350 as its fb. a few things to check... 1. make sure you set vga=normal in /etc/lilo.conf AND execute lilo 2. slide the card to a different slot 3. add append="video=vc:0-0" to your lilo.conf (don't forget to run lilo) Quote: # Boot up Linux by default.
#
default=Linux
image=/boot/vmlinuz-2.4.25-chw
append="video=vc:0-0"
label=Linux
initrd=/boot/initrd.gz
read-only
# restricted
# alias=1
Hope this helps
|
|
| Top |
|
|
View unanswered posts
View active topics
KnoppMyth 
Print view
Previous topic Next topic 
LinHES Home
Board index
FAQ
Search
Login 
Register
