Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
MythTV Setup Guide/HOWTO
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3, 4, 5, 6, 7  Next  
Reply to topic    Gentoo Forums Forum Index Multimedia
View previous topic :: View next topic  
Author Message
strider3700
Tux's lil' helper
Tux's lil' helper


Joined: 10 Apr 2003
Posts: 94

PostPosted: Thu Sep 30, 2004 4:36 am    Post subject: Reply with quote

hauppauge wintv 250

It should work. I have to admit I didn't understand half of the directions I followed when setting up the IVTV module so If those settings aren't exact every time I would never notice
Back to top
View user's profile Send private message
Hobbes-X
l33t
l33t


Joined: 04 Feb 2004
Posts: 823
Location: Seattle, WA

PostPosted: Thu Sep 30, 2004 6:47 pm    Post subject: Reply with quote

Yep- should be fine with the PVR250.

Does dmesg register any complaints when it trys to load ivtv?

Care to post some other background info too?
kernel and ivtv version and /etc/modules.d/ivtv? Are you using the emerged ivtv, or did you compile your own separately?
Back to top
View user's profile Send private message
strider3700
Tux's lil' helper
Tux's lil' helper


Joined: 10 Apr 2003
Posts: 94

PostPosted: Fri Oct 01, 2004 6:05 am    Post subject: Reply with quote

output from dmesg mentioning ivtv. This repeats about 20 times

Code:
ivtv: api call 0x000000b7
ivtv: Firmware reset scheduled, failed API command
ivtv: init error 22. Code -16
ivtv: 100 ms time out waiting for firmware
ivtv: api call 0x000000b7



kernel 2.4.27 nothing too special in there, I can post up a list of settings if someone will tell me how to generate it.

ivtv I did the emerge, downloading the one from the site gave me an error but emerge walked through it. Version is 0.1.9-r4

/etc/modules.d.ivtv
Code:

alias char-major-81 videodev
alias char-major-81-0 ivtv
alias char-major-61 lirc_i2c
options ivtv ivtv-debug=0 mpg_buffers=90
options tuner type=2
options msp3400 once=1 simple=1 debug=0
add below ivtv msp3400 saa7115 tuner
add above ivtv lirc_dev lirc_i2c

Thanks again for any help
Back to top
View user's profile Send private message
Hobbes-X
l33t
l33t


Joined: 04 Feb 2004
Posts: 823
Location: Seattle, WA

PostPosted: Fri Oct 01, 2004 8:20 am    Post subject: Reply with quote

strider3700 wrote:
output from dmesg mentioning ivtv. This repeats about 20 times

Code:
ivtv: api call 0x000000b7
ivtv: Firmware reset scheduled, failed API command
ivtv: init error 22. Code -16
ivtv: 100 ms time out waiting for firmware
ivtv: api call 0x000000b7



kernel 2.4.27 nothing too special in there, I can post up a list of settings if someone will tell me how to generate it.

ivtv I did the emerge, downloading the one from the site gave me an error but emerge walked through it. Version is 0.1.9-r4

/etc/modules.d.ivtv
Code:

alias char-major-81 videodev
alias char-major-81-0 ivtv
alias char-major-61 lirc_i2c
options ivtv ivtv-debug=0 mpg_buffers=90
options tuner type=2
options msp3400 once=1 simple=1 debug=0
add below ivtv msp3400 saa7115 tuner
add above ivtv lirc_dev lirc_i2c

Thanks again for any help


Hmm- 'Code -16' is supposed to mean hung firmware. I saw a couple posts on the MythTV list that suggest this might be fixed by an incorrectly specified tuner type?

ivtv 0.1.9-r4 is supposedly based off of ckennedy's 0.1.10-ck71d, so might want to try changing a couple lines in your /etc/modules.d/ivtv:

Code:

alias char-major-81 videodev
alias char-major-81-0 ivtv
options ivtv ivtv_debug=0 tuner=2
options msp3400 once=1 simpler=1 simple=0
add below ivtv msp3400 saa7115 tuner
add above ivtv lirc_dev lirc_i2c


The above is based off recommendations from Chris in his how-to:
http://67.18.1.101/~ckennedy/ivtv/HOWTO.ivtv-0.1.10

But those changes might be for 2.6.6 and later kernels... Maybe worth a try with the changes to your modules.d/ivtv above, or maybe a roll-back to ivtv-0.1.9-r3?

Also, in the 1.10 series, test_ioctl has been replaced with ivtvctl. Perhaps the test_ioctl is still around from a previous installation, and the card isn't getting initialized correctly from the old version?

And before it gets too easy :D, I see another site (http://www.ihtfp.org/mythtv/) where this problem was caused by a failed video card module. One other user on the Myth list comments that he had to enable PCI bus mastering in the BIOS before the card would output video.

I'd say, try setting the encoder up using ivtvctl first:
Code:

ivtvctl -u 0x3000
ivtvctl -p 4
ivtvctl -f width=720,height=480
ivtvctl -v input=3,output=1


Using -p 4 to select the tv tuner input might be best, cause at least you'll see static, where other inputs might record video of a black screen.

If that doesn't do it, emerging -r3 of ivtv and then updating to -r4 again would most likely clear out any cruft from the older 0.1.9 versions around. Trying a test on the -r3 version is probably worth a shot too, while it's installed since it's also known to be stable.

If you've still got trouble, post the output of dmesg from right after a reboot- we can check to see if you might have other drivers that are somehow blocking the init of the card.

Hang in there, it's definately worth it! (Just came across a page in german where someone 'fixed' their Hauppauge problems by selling the card to buy some Star Trek DVD's :wink: )
Back to top
View user's profile Send private message
Luud
Apprentice
Apprentice


Joined: 05 Jun 2003
Posts: 246
Location: Netherlands

PostPosted: Fri Oct 01, 2004 8:33 am    Post subject: Reply with quote

Also,

Try not specifying any options for the modules. Let the modules figure it out themselves. This should work best usually.

Only specify options when that doesn't work. And only those necessary.

The log file should tell you what you have in there.
_________________
"Great minds don't think alike. If they did, the patent office would only have about fifty inventions." - Wally
Back to top
View user's profile Send private message
mojoandy
n00b
n00b


Joined: 25 Jul 2004
Posts: 9

PostPosted: Fri Oct 01, 2004 1:26 pm    Post subject: make menuconfig? (was Re: MythTV Setup Guide/HOWTO) Reply with quote

drunkentiger wrote:
Hi all-

I've drafted a setup guide to MythTV specifically tailored for Gentoo users. I thought it might help some people here, so here's my first post. :wink:

Major Updates:
May 27, 2004: Added 0.15 upgrade procedure.
April 27, 2004: Added MythWeb section.

Thanks.


I've applied the paxel patches to 2.6.5 to handle my 713x, but I can't seem to find 713x in my "make menuconfig". What gives? Do I need to do something manually and could someone point this n00b to the right docs (I've searched in vain)....

Also, 2.6.5 doesn't seem to have lirc or ioctl as config options (although they are listed in the howto).

Regardless, much thanks to drunkentiger for the HOWTO!

-A

Edit: Kinda fixed it by making sure the I2C was loaded (as per another thread elsewhere) and this opened up the 713x as a selectable driver under video. Not sure why. Stuck elsewhere on an x issue but I'm making progress, thanks.
Back to top
View user's profile Send private message
strider3700
Tux's lil' helper
Tux's lil' helper


Joined: 10 Apr 2003
Posts: 94

PostPosted: Sat Oct 02, 2004 3:34 am    Post subject: Reply with quote

dmesg fresh after a reboot.

Code:

Linux version 2.4.27 (root@debbie) (gcc version 3.3.4 20040623 (Gentoo Linux 3.3.4-r1, ssp-3.3.2-2, pie-8.7.6)) #2 SMP Mon Sep 27 05:01:36 Local time zone mustbe set--see zic
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000001fff0000 (usable)
 BIOS-e820: 000000001fff0000 - 000000001fff3000 (ACPI NVS)
 BIOS-e820: 000000001fff3000 - 0000000020000000 (ACPI data)
 BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
511MB LOWMEM available.
On node 0 totalpages: 131056
zone(0): 4096 pages.
zone(1): 126960 pages.
zone(2): 0 pages.
ACPI disabled because your bios is from 00 and too old
You can enable it with acpi=force
Kernel command line: root=/dev/hdb3
Local APIC disabled by BIOS -- reenabling.
Found and enabled local APIC!
Initializing CPU#0
Detected 1000.052 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 1992.29 BogoMIPS
Memory: 515028k/524224k available (1943k kernel code, 8808k reserved, 619k data, 132k init, 0k highmem)
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode cache hash table entries: 32768 (order: 6, 262144 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 32768 (order: 5, 131072 bytes)
Page-cache hash table entries: 131072 (order: 7, 524288 bytes)
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 256K
CPU serial number disabled.
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU:     After generic, caps: 0383fbff 00000000 00000000 00000000
CPU:             Common caps: 0383fbff 00000000 00000000 00000000
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
mtrr: detected mtrr type: Intel
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 256K
Intel machine check reporting enabled on CPU#0.
CPU:     After generic, caps: 0383fbff 00000000 00000000 00000000
CPU:             Common caps: 0383fbff 00000000 00000000 00000000
CPU0: Intel Pentium III (Coppermine) stepping 0a
per-CPU timeslice cutoff: 731.00 usecs.
SMP motherboard not detected.
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 1000.0964 MHz.
..... host bus clock speed is 133.3460 MHz.
cpu: 0, clocks: 1333460, slice: 666730
CPU0<T0:1333456,T1:666720,D:6,S:666730,C:1333460>
Waiting on wait_init_idle (map = 0x0)
All processors have done init_idle
PCI: PCI BIOS revision 2.10 entry at 0xfb1b0, last bus=2
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Using IRQ router PIIX/ICH [8086/7110] at 00:07.0
Limiting direct PCI/PCI transfers.
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
NTFS driver v1.1.22 [Flags: R/O]
i2c-core.o: i2c core module version 2.6.1 (20010830)
i2c-dev.o: i2c /dev entries driver module version 2.6.1 (20010830)
i2c-core.o: driver i2c-dev dummy driver registered.
i2c-algo-bit.o: i2c bit algorithm module
i2c-proc.o version 2.6.1 (20010830)
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI ISAPNP enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
FDC 0 is a post-1991 82077
loop: loaded (max 8 devices)
8139cp: 10/100 PCI Ethernet driver v1.2 (Mar 22, 2004)
8139cp: pci dev 00:0b.0 (id 10ec:8139 rev 10) is not an 8139C+ compatible chip
8139cp: Try the "8139too" driver instead.
8139too Fast Ethernet driver 0.9.26
PCI: Found IRQ 10 for device 00:0b.0
PCI: Sharing IRQ 10 with 00:07.2
eth0: RealTek RTL8139 at 0xe0800000, 00:20:18:a0:eb:c3, IRQ 10
eth0:  Identified 8139 chip type 'RTL-8139B'
Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX4: IDE controller at PCI slot 00:07.1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
hda: Maxtor 92048U8, ATA DISK drive
hdb: QUANTUM FIREBALLP LM15, ATA DISK drive
blk: queue c03f59a0, I/O limit 4095Mb (mask 0xffffffff)
blk: queue c03f5ae8, I/O limit 4095Mb (mask 0xffffffff)
hdc: LTN525, ATAPI CD/DVD-ROM drive
hdd: LG DVD-ROM DRD-8160B, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: attached ide-disk driver.
hda: host protected area => 1
hda: 40000464 sectors (20480 MB) w/2048KiB Cache, CHS=2489/255/63, UDMA(33)
hdb: attached ide-disk driver.
hdb: host protected area => 1
hdb: 29336832 sectors (15020 MB) w/1900KiB Cache, CHS=29104/16/63, UDMA(33)
hdc: attached ide-cdrom driver.
hdc: ATAPI 52X CD-ROM drive, 120kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.12
hdd: attached ide-cdrom driver.
hdd: ATAPI 48X DVD-ROM drive, 512kB Cache, UDMA(33)
Partition check:
 /dev/ide/host0/bus0/target0/lun0: p1
 /dev/ide/host0/bus0/target1/lun0: p1 p2 p3
SCSI subsystem driver Revision: 1.00
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
ohci1394: $Rev: 1045 $ Ben Collins <bcollins@debian.org>
ohci1394_0: OHCI-1394 1.0 (PCI): IRQ=[10]  MMIO=[f7000000-f70007ff]  Max Packet=[2048]
raw1394: /dev/raw1394 device initialized
sbp2: $Rev: 1074 $ Ben Collins <bcollins@debian.org>
ieee1394: sbp2: Driver forced to serialize I/O (serialize_io = 1)
Linux Kernel Card Services 3.1.22
  options:  [pci] [cardbus] [pm]
usb.c: registered new driver hub
host/uhci.c: USB Universal Host Controller Interface driver v1.1
PCI: Found IRQ 10 for device 00:07.2
PCI: Sharing IRQ 10 with 00:0b.0
host/uhci.c: USB UHCI at I/O 0xcc00, IRQ 10
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
USB Mass Storage support registered.
Linux video capture interface: v1.00
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 32768 bind 32768)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
ds: no socket drivers loaded!
scsi0 : SCSI emulation for IEEE-1394 SBP-2 Devices
kmod: failed to exec /sbin/modprobe -s -k nls_iso8859-1, errno = 2
reiserfs: found format "3.6" with standard journal
hub.c: new USB device 00:07.2-2, assigned address 2
hub.c: USB hub found
hub.c: 4 ports detected
reiserfs: checking transaction log (device ide0(3,67)) ...
for (ide0(3,67))
ide0(3,67):Using r5 hash to sort names
VFS: Mounted root (reiserfs filesystem) readonly.
Mounted devfs on /dev
Freeing unused kernel memory: 132k freed
ieee1394: sbp2: Logged into SBP-2 device
ieee1394: sbp2: Node 0-00:1023: Max speed [S400] - Max payload [2048]
ieee1394: NodeMgr: hotplug policy returned -2
ieee1394: Node added: ID:BUS[0-00:1023]  GUID[000a270002557557]
ieee1394: Host added: ID:BUS[0-01:1023]  GUID[001106000000391e]
Adding Swap: 500464k swap-space (priority -1)
i2c-core.o: driver i2c TV tuner driver registered.
i2c-core.o: driver saa7115 registered.
i2c-core.o: driver i2c msp3400 driver registered.
ivtv: version 0.1.9 (0.1.10pre2-ck71d) loading
PCI: Found IRQ 5 for device 00:0a.0
PCI: Sharing IRQ 5 with 00:0e.0
ivtv (i2c)= 0xe091e2a0
i2c-dev.o: Registered 'ivtv i2c driver #0' as minor 0
tuner: chip found @ 0xc2
i2c-core.o: client [(tuner unset)] registered to adapter [ivtv i2c driver #0](pos. 0).
saa7114.c: starting probe for adapter ivtv i2c driver #0 (0x10005)
saa7114.c: detecting saa7114 client on address 0x42
saa7115.c: writing init values
i2c-core.o: client [saa7115[0]] registered to adapter [ivtv i2c driver #0](pos.1).
status: (1E) 0x48, (1F) 0xc0
msp34xx: init: chip=MSP3448W-B3, has NICAM support, simpler (G) no-thread mode
msp34xx: $Id$ compiled on: Sep 28 2004 04:46:11
i2c-core.o: client [MSP3448W-B3] registered to adapter [ivtv i2c driver #0](pos. 2).
i2c-core.o: adapter ivtv i2c driver #0 registered as adapter 0.
tuner: type set to 2 (Philips NTSC (FI1236,FM1236 and compatibles))
ivtv: loaded
lirc_dev: IR Remote Control driver registered, at major 61
bttv: driver version 0.7.108 loaded
bttv: using 4 buffers with 2080k (8320k total) for capture
bttv: Host bridge needs ETBF enabled.
i2c-core.o: driver i2c ir driver registered.
lirc_i2c: chip found @ 0x18 (Hauppauge IR)
i2c-core.o: client [Hauppauge IR] registered to adapter [ivtv i2c driver #0](pos. 3).
lirc_dev: lirc_register_plugin:sample_rate: 10
PCI: Found IRQ 3 for device 00:09.0
blk: queue c03f59a0, I/O limit 4095Mb (mask 0xffffffff)
blk: queue c03f5ae8, I/O limit 4095Mb (mask 0xffffffff)
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
smbfs: Unrecognized mount option noexec
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: Detected Intel 440BX chipset
agpgart: AGP aperture is 128M @ 0xe8000000
bash-2.05b#


looking through there I see a few things, first it seems to have found my Ipod, which is a nice surprise since I haven't bothered to get that going yet.
second if appears to recognize the hauppage and the remote
However when booting as all the messages go by I saw an error about a problem loading BTTV which doesn't appear in here, perhaps it found a way around the issue?

The output from the card does now show up in a file that is nolonger 0 bytes it's actually pretty damn big pretty quick. However the output is a mostly green screen with some thing that looks like digital cable artifacts in it. I've temporarily hooked the card directly to cable via coax in cable box was giving me issues about channel selection or something.

ivtvctl -p 4 gives me this green screen as does 1,2 and 3 5 - 9 gives me a black screen.
Back to top
View user's profile Send private message
Hobbes-X
l33t
l33t


Joined: 04 Feb 2004
Posts: 823
Location: Seattle, WA

PostPosted: Sat Oct 02, 2004 4:15 am    Post subject: Reply with quote

Quote:


The output from the card does now show up in a file that is nolonger 0 bytes it's actually pretty damn big pretty quick. However the output is a mostly green screen with some thing that looks like digital cable artifacts in it. I've temporarily hooked the card directly to cable via coax in cable box was giving me issues about channel selection or something.



Sounds like a working card :) You should be able to use ptune.pl to change channels (or myth), or you can change inputs with ivtvctl, like you were trying before.
Back to top
View user's profile Send private message
strider3700
Tux's lil' helper
Tux's lil' helper


Joined: 10 Apr 2003
Posts: 94

PostPosted: Sat Oct 02, 2004 5:04 am    Post subject: Reply with quote

Nothings ever easy is it ;)

Code:
./ptune.pl
Can't locate Video/Frequencies.pm in @INC (@INC contains: /etc/perl /usr/lib/perl5/site_perl/5.8.4/i686-linux /usr/lib/perl5/site_perl/5.8.4 /usr/lib/perl5/site_perl/5.8.3/i686-linux /usr/lib/perl5/site_perl/5.8.3 /usr/lib/perl5/site_perl/5.8.2/i686-linux /usr/lib/perl5/site_perl/5.8.2 /usr/lib/perl5/site_perl/5.8.0/i686-linux /usr/lib/perl5/site_perl/5.8.0 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.4/i686-linux /usr/lib/perl5/vendor_perl/5.8.4 /usr/lib/perl5/vendor_perl/5.8.2/i686-linux /usr/lib/perl5/vendor_perl/5.8.2 /usr/lib/perl5/vendor_perl/5.8.0/i686-linux /usr/lib/perl5/vendor_perl/5.8.0 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.4/i686-linux /usr/lib/perl5/5.8.4 /usr/local/lib/site_perl /usr/lib/perl5/site_perl/5.8.3/i686-linux /usr/lib/perl5/site_perl/5.8.3 /usr/lib/perl5/site_perl/5.8.2/i686-linux /usr/lib/perl5/site_perl/5.8.2 /usr/lib/perl5/site_perl/5.8.0/i686-linux /usr/lib/perl5/site_perl/5.8.0 .) at ./ptune.pl line 8.
BEGIN failed--compilation aborted at ./ptune.pl line 8.


Thanks for all the help so far
Back to top
View user's profile Send private message
strider3700
Tux's lil' helper
Tux's lil' helper


Joined: 10 Apr 2003
Posts: 94

PostPosted: Sat Oct 02, 2004 5:24 am    Post subject: Reply with quote

OK I found frequencies.pm on source forge, and ivtv.pm but Inifiles.pm is stumping me

Never mind Google is my friend ;)


However now that I can change channels I still get nothing but a funky green screen
Back to top
View user's profile Send private message
Hobbes-X
l33t
l33t


Joined: 04 Feb 2004
Posts: 823
Location: Seattle, WA

PostPosted: Sun Oct 03, 2004 6:51 pm    Post subject: Reply with quote

As long as the cable signal is working, then the green screen is most likely the card trying to use the wrong tuner. (esentially the green is from a weak signal) Try checking dmesg for signs of the card assuming a certain tuner.

Are you in NTSC, or PAL land? :)
Back to top
View user's profile Send private message
strider3700
Tux's lil' helper
Tux's lil' helper


Joined: 10 Apr 2003
Posts: 94

PostPosted: Sun Oct 03, 2004 8:28 pm    Post subject: Reply with quote

ntsc.
I'm assuming it's a tuner issue, I'll take some time and run through them all and see what I get.
Back to top
View user's profile Send private message
Hobbes-X
l33t
l33t


Joined: 04 Feb 2004
Posts: 823
Location: Seattle, WA

PostPosted: Sun Oct 03, 2004 9:41 pm    Post subject: Reply with quote

NTSC should be tuner type 2, but you can check the eeprom on the card to be sure:

Quote:
Q: How can I figure out what tuner type I should use?
A: If you have a Hauppauge card, try
insmod tveeprom

and then check out dmesg to find out more detailed information on your card as defined in its EEPROM.


(EDIT: This is from the FAQ at the ivtv wiki: http://ivtv.writeme.ch/tiki-index.php)


Last edited by Hobbes-X on Mon Oct 04, 2004 6:33 am; edited 1 time in total
Back to top
View user's profile Send private message
strider3700
Tux's lil' helper
Tux's lil' helper


Joined: 10 Apr 2003
Posts: 94

PostPosted: Sun Oct 03, 2004 9:47 pm    Post subject: Reply with quote

Code:
tvee: Hauppauge: model=32032, rev=B182, serial#=2778465
tvee: tuner=<unknown> (idx=82, type=-1)
tvee: tuner fmt=NTSC(M) (eeprom=0x08, v4l2=0x00001000)
tvee: audio_processor=MSP3440 (type=11)


type -1 can't be correct I'm assuming that is set somehow with ptune.pl?
Back to top
View user's profile Send private message
JHuizingh
Tux's lil' helper
Tux's lil' helper


Joined: 05 Jul 2002
Posts: 100

PostPosted: Sun Oct 03, 2004 9:54 pm    Post subject: Certain hauppage pvr-250 cards unsupported? Reply with quote

I spent many hours of trying to get a driver to load which only caused the system to hang for a pvr-250 card that has the label:
Code:
NTSC/NTSC-J
32552
Rev B123


I tried buying a pvr-250 from the store that had a different label, and the driver loaded right up. Apperently the above model is not supported, or at least I couldn't figure it out. Hopefully other people who have that model will see this message and save some frustration by getting a different version of the card, or maybe somebody will have some hints of how to get the thing to work.
Back to top
View user's profile Send private message
JHuizingh
Tux's lil' helper
Tux's lil' helper


Joined: 05 Jul 2002
Posts: 100

PostPosted: Sun Oct 03, 2004 10:12 pm    Post subject: Can not see any channels Reply with quote

I got the ivtv driver to load for my hauppage pvr-250 card, and it seems to be working (sort of). I get the correct /dev/video0 device, and when I "cat /dev/video0 > test_capture.mpg" it creates a file that gets gradually bigger. I can play back the file in mplayer and xine, but it is just a black window... Seems ok so far.

I think I have mythtv set up properly, and when I go into mythfrontend and go to watch tv, I just see static. I am able to cycle through all of the channels that I have set up, but I just see static on all of them. I just have broadcast tv, but A tv that's on the other side of the room gets all of those channels clearly.

I'm not sure what to do to find this problem. Is it the problem of the antenna? Is it the problem with the capture card? Is it the problem of the mythtv settings? Can somebody point me in the right direction?
Back to top
View user's profile Send private message
strider3700
Tux's lil' helper
Tux's lil' helper


Joined: 10 Apr 2003
Posts: 94

PostPosted: Sun Oct 03, 2004 10:29 pm    Post subject: Reply with quote

JHuizingh this is exactly the problem that I'm stuck at currently. Hobbes-X has been a huge help to get me this far and he thinks that it's an issue of tuning.
I'm in agreement, A couple days ago I got staticor a green screen but now all I get is black. not sure whats changed.
Back to top
View user's profile Send private message
Hobbes-X
l33t
l33t


Joined: 04 Feb 2004
Posts: 823
Location: Seattle, WA

PostPosted: Mon Oct 04, 2004 6:49 am    Post subject: Reply with quote

Hi Strider3700-

Might have found something for you on the ivtv mailing list: http://www.poptix.net/ivtv/Sep-2004/msg00112.html

Looks like there might be another type of tuner showing up. Short answer is try tuner type 39, but you might want to check the message out and see if anything looks familiar.

Looks like someone else has an idx 82, anyways. Hopefully you won't need to edit driver files :)
Back to top
View user's profile Send private message
Hobbes-X
l33t
l33t


Joined: 04 Feb 2004
Posts: 823
Location: Seattle, WA

PostPosted: Mon Oct 04, 2004 7:05 am    Post subject: Reply with quote

JHuizingh,

Looks like you might have a similar problem to Strider- as long as you get a file bigger than 0 bytes when you run cat /dev/video0 >> test.mpg, the black screen means that you're capturing from an input other than the tuner. Myth seems to do some smart-checking to match to the tuner input on it's own (or at least, it identifies the tuner input correctly when it lists the inputs available when setting the card up.)

Since you're getting static when running myth, the card is probably detecting the wrong tuner, or you've got it specified to use one that doesn't match.

Try this out (from the ivtv wiki's FAQ) to see which tuner the card identifies itself with:
Quote:
Q: How can I figure out what tuner type I should use?
A: If you have a Hauppauge card, try
insmod tveeprom

and then check out dmesg to find out more detailed information on your card as defined in its EEPROM.


Normally, NTSC tuners are type 2, and PAL tuners are type 1, but it looks like there's a newer tuner type showing up in some cards. If you get an unknown tuner type from tveeprom, give tuner 39 a shot :)

Also, if you see something along the lines of 'tuner unset' in your kernel messages, try removing the 'options tuner type=X' line in your /etc/modules.d/ivtv, and add 'tuner=X' to the 'options ivtv line. (Probably only for the 1.10 (or ivtv-r4) versions with 2.6 kernels, but might work with others???)
Back to top
View user's profile Send private message
strider3700
Tux's lil' helper
Tux's lil' helper


Joined: 10 Apr 2003
Posts: 94

PostPosted: Mon Oct 04, 2004 7:23 am    Post subject: Reply with quote

ok I dropped the old options line and added the new one to modules.d/ivtv

did a modprobe -r ivtv and then modprobe ivtv.

Nothing but static when I use mplayer to directly read the stream. nothing buy jumping green when piped to a file and played through xine.

I did a modprobe -r tveeprom and then the insmod tveeprom to see what it says and it still shows it as an unknown tuner type. Perhaps tommorrow evening I can take some time to learn about driver hacking ;)
Back to top
View user's profile Send private message
Hobbes-X
l33t
l33t


Joined: 04 Feb 2004
Posts: 823
Location: Seattle, WA

PostPosted: Mon Oct 04, 2004 7:28 am    Post subject: Reply with quote

strider3700 wrote:
Perhaps tommorrow evening I can take some time to learn about driver hacking ;)


Heh :) ,

I think you might have to specify a channel again once you remove and reload the driver, just in case you hadn't tried that already. A couple of times I've re-installed my cards, and the tuner didn't seem to kick in until after a couple channel changes (but then, I was getting at least a little bit of a signal).
Back to top
View user's profile Send private message
JHuizingh
Tux's lil' helper
Tux's lil' helper


Joined: 05 Jul 2002
Posts: 100

PostPosted: Tue Oct 05, 2004 1:30 am    Post subject: Reply with quote

Hobbes-X,

Thanks. I triend tuner=39. Now it works... sort of. When I do the 'cat /dev/video0 > first_capture.mpg', and then play that file back in mplayer, I actually see the video and hear the audio!

Unfortunately it doesn't quite work when I try to watch live tv in myth. Yesterday when I posted, I was getting the heads up display in front of static. Now I can hear the audio, but I don't see the HUD or the static. I made sure that I was using the right opengl drivers by doing 'opengl-update nvidia', I'm not sure where else to check. Can you point me in the right direction?

Thanks for the help so far.
Back to top
View user's profile Send private message
Hobbes-X
l33t
l33t


Joined: 04 Feb 2004
Posts: 823
Location: Seattle, WA

PostPosted: Tue Oct 05, 2004 2:13 am    Post subject: Reply with quote

Does that mean you get audio, but a black screen with no OSD? I get the same issue if I have another XV capable video player that is still open, like kaffeine in the system tray, after playing a video.
Back to top
View user's profile Send private message
JHuizingh
Tux's lil' helper
Tux's lil' helper


Joined: 05 Jul 2002
Posts: 100

PostPosted: Tue Oct 05, 2004 2:41 am    Post subject: Reply with quote

Hobbes-X,

You interpreted my post correctly. I meant OSD, not HUD. I knew I'd seen some acronym like that before and HUD was the one I thought of first. I must have had another player open, because I rebooted and it was solved.

Now I just need to get rid of the cards that I couldn't get to work and buy another card that I could get to work, and then I can start enjoying :). Thanks for the help.
Back to top
View user's profile Send private message
Hobbes-X
l33t
l33t


Joined: 04 Feb 2004
Posts: 823
Location: Seattle, WA

PostPosted: Tue Oct 05, 2004 3:18 am    Post subject: Reply with quote

strider3700 wrote:

I did a modprobe -r tveeprom and then the insmod tveeprom to see what it says and it still shows it as an unknown tuner type. Perhaps tommorrow evening I can take some time to learn about driver hacking ;)


I missed part of this yesterday, must have been too tired... tveeprom only reads info straight from the card itself, the tuner type 82 will always be unreferenced in the driver (at least until you have one compiled with changes, either made by you, or an updated driver...)

If it's the unrecognized tuner type that's the problem, we're just trying to force the driver to choose another equivlent type of tuner with the tuner=39 part. Don't need to actually change the driver, as long as you can get it to choose a preexisting compitible one.

You might have already figured that out before I post this, but after reading my last post about it, I wasn't sure if that was clear or not. Just want to make sure you're checking dmesg to see that it's actually selecting the tuner we're trying to force it to, before you start writing yourself a new driver :)
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Multimedia All times are GMT
Goto page Previous  1, 2, 3, 4, 5, 6, 7  Next
Page 6 of 7

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum