public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mark Knecht" <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] OT - MythTV problems
Date: Fri, 15 Sep 2006 11:04:25 -0700	[thread overview]
Message-ID: <5bdc1c8b0609151104s764b5693h694aade82fd48cd5@mail.gmail.com> (raw)
In-Reply-To: <1158339682.11883.3.camel@bullet.espersunited.com>

On 9/15/06, Michael Sullivan <michael@espersunited.com> wrote:
<SNIP>
>
> OK.  I did what you said, and I do get a signal from /dev/video0 now,

That's good...

> but mythfrontend still won't show LiveTV.

That's not good...

<SNIP>

>
> If it's helpful, here's my dmesg info:
>
> camille ~ # dmesg | grep 'ivtv'
> ivtv:  ==================== START INIT IVTV ====================
> ivtv:  version 0.7.0 (tagged release) loading
> ivtv:  Linux version: 2.6.17-gentoo-r8 SMP mod_unload 486 gcc-4.1
> ivtv:  In case of problems please include the debug info between

<SNIP>

> total)
> ivtv0: Create encoder radio stream
> ivtv0: Initialized Hauppauge WinTV PVR-250, card #0
> ivtv:  ====================  END INIT IVTV  ====================
> ivtv0: Removed Hauppauge WinTV PVR-250, card #0

I do not understand this message just above. I've never seen that before.


> ivtv:  ==================== START INIT IVTV ====================
> ivtv:  version 0.7.0 (tagged release) loading
> ivtv:  Linux version: 2.6.17-gentoo-r8 SMP mod_unload 486 gcc-4.1
<SNIP>

> ivtv0: Initialized Hauppauge WinTV PVR-250, card #0
> ivtv:  ====================  END INIT IVTV  ====================
> ivtv0: Removed Hauppauge WinTV PVR-250, card #0

And again.......


> ivtv:  ==================== START INIT IVTV ====================
> ivtv:  version 0.7.0 (tagged release) loading
> ivtv:  Linux version: 2.6.17-gentoo-r8 SMP mod_unload 486 gcc-4.1
> ivtv:  In case of problems please include the debug info between
> ivtv:  the START INIT IVTV and END INIT IVTV lines, along with
> ivtv:  any module options, when mailing the ivtv-users mailinglist.
> ivtv0: Autodetected Hauppauge WinTV PVR-250 card (cx23416 based)
> tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
> tda9887 0-0043: chip found @ 0x86 (ivtv i2c driver #0)
> saa7115 0-0021: saa7115 found @ 0x42 (ivtv i2c driver #0)
> msp3400 0-0040: MSP4448G-A2 found @ 0x80 (ivtv i2c driver #0)
> ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
> ivtv0: Encoder revision: 0x02050032
> ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB
> total)
> ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB
> total)
> ivtv0: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB
> total)
> ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB
> total)
> ivtv0: Create encoder radio stream
> ivtv0: Initialized Hauppauge WinTV PVR-250, card #0
> ivtv:  ====================  END INIT IVTV  ====================

How many PVR-250's are in this machine? Two or three?

Here's what mine has:

Linux video capture interface: v1.00
ivtv:  ==================== START INIT IVTV ====================
ivtv:  version 0.7.0 (tagged release) loading
ivtv:  Linux version: 2.6.17-gentoo-r2 SMP preempt mod_unload PENTIUM4 gcc-3.4
ivtv:  In case of problems please include the debug info between
ivtv:  the START INIT IVTV and END INIT IVTV lines, along with
ivtv:  any module options, when mailing the ivtv-users mailinglist.
ivtv0: Autodetected Hauppauge WinTV PVR-150 card (cx23416 based)
ACPI: PCI Interrupt 0000:01:01.0[A] -> GSI 22 (level, low) -> IRQ 21
ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
tveeprom 0-0050: Hauppauge model 26032, rev C199, serial# 8095579
tveeprom 0-0050: tuner model is TCL 2002N 5H (idx 99, type 50)
tveeprom 0-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 0-0050: audio processor is CX25841 (idx 35)
tveeprom 0-0050: decoder processor is CX25841 (idx 28)
tveeprom 0-0050: has no radio, has IR remote
tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
cx25840 0-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0)
cx25840 0-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
wm8775 0-001b: chip found @ 0x36 (ivtv i2c driver #0)
ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
ivtv0: Encoder revision: 0x02050032
ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total)
ivtv0: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total)
ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total)
tuner 0-0061: type set to 50 (TCL 2002N)
ivtv0: Initialized Hauppauge WinTV PVR-150, card #0
ivtv:  ======================  NEXT CARD  ======================
ivtv1: Autodetected Hauppauge WinTV PVR-250 card (cx23416 based)
ACPI: PCI Interrupt 0000:01:02.0[A] -> GSI 17 (level, low) -> IRQ 22
ivtv1: Unreasonably low latency timer, setting to 64 (was 32)
tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #1)
tveeprom 1-0050: Hauppauge model 32062, rev C182, serial# 7913638
tveeprom 1-0050: tuner model is LG TAPC H791F (idx 82, type 39)
tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 1-0050: audio processor is MSP3445 (idx 12)
tveeprom 1-0050: decoder processor is SAA7115 (idx 19)
tveeprom 1-0050: has no radio, has IR remote
saa7115 1-0021: saa7115 found @ 0x42 (ivtv i2c driver #1)
msp3400 1-0040: MSP3445G-B8 found @ 0x80 (ivtv i2c driver #1)
msp3400 1-0040: MSP3445G-B8 supports radio, mode is autodetect and autoselect
ivtv1: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
ivtv1: Encoder revision: 0x02050032
ivtv1: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
ivtv1: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total)
ivtv1: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total)
ivtv1: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total)
tuner 1-0061: type set to 39 (LG NTSC (newer TAPC series))
ivtv1: Initialized Hauppauge WinTV PVR-250, card #1
ivtv:  ====================  END INIT IVTV  ====================


I have a sneaky suspicion that you possibly have some ivtv-0.4.5 stuff
left over. I've had that happen a number of time. Best I can advise I
would suggest emerge -C on ivtv, then clean out the existing
/lib/modules/2.6.17-gentoo-r8. I'd probably delete the whole
directory. I'd then run make modules_install from the kernel source to
set it up again from scratch. I'd then reemerge ivtv-0.7 again and
either modprobe or reboot.

I've never seen these messages about removing cards but they seem like
part of the problem.

Note: We are running a slightly older SMP kernel here with no problems:

dragonfly modules.d # uname -a
Linux dragonfly 2.6.17-gentoo-r2 #3 SMP PREEMPT Tue Aug 15 09:41:09
PDT 2006 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz GNU/Linux
dragonfly modules.d #


Maybe it's specific to 2.6.17-gentoo-r8? You could try backing up to
-r2 that I'm running.

Good luck,
Mark




> camille ~ #
>
> Also, I'm using mythtv-0.19_p9163-r1:
>
> camille ~ # emerge -pv mythtv
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild     U ] media-tv/mythtv-0.19_p10505 [0.19_p9163-r1] USE="alsa
> debug dvb dvd jack joystick lirc mmx opengl vorbis (-altivec)
> -backendonly -dbox2 -frontendonly -ieee1394 -lcd -xvmc"
> VIDEO_CARDS="i810 via -nvidia" 0 kB
>
> Total size of downloads: 0 kB
> camille ~ #
>
>
> --
> gentoo-user@gentoo.org mailing list
>
>
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-09-15 18:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-15 15:35 [gentoo-user] OT - MythTV problems Michael Sullivan
2006-09-15 16:03 ` [gentoo-user] " Michael Sullivan
2006-09-15 16:38 ` [gentoo-user] " Mark Knecht
2006-09-15 17:01   ` Michael Sullivan
2006-09-15 18:04     ` Mark Knecht [this message]
2006-09-15 23:53       ` Michael Sullivan
2006-09-16  0:36         ` Mark Knecht
2006-09-16  1:01           ` Michael Sullivan
2006-09-16  2:05             ` Mark Knecht
2006-09-16  2:17           ` [gentoo-user] OT - MythTV problems [SOLVED] Michael Sullivan
2006-09-16  2:29             ` Mark Knecht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5bdc1c8b0609151104s764b5693h694aade82fd48cd5@mail.gmail.com \
    --to=markknecht@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox