[Discuss] line in for Intel sound chipset apparently has quit working with Debian Jessie kernel upgrade

John Tag hart jean.philippe.taggart at gmail.com
Tue Jun 6 13:20:07 PDT 2017


Hello, 

I have an other haulage wintv card with dual tuners and even a PCI-e in a box if you're looking for a replacement. I was going to build a myth tv box a while back but never got around to it. 

You're welcome to either or both. 

Sent from my iPhone

> On Jun 6, 2017, at 12:22 AM, Alan W. Irwin <irwin at beluga.phys.uvic.ca> wrote:
> 
> Hi Peter:
> 
>> On 2017-06-05 20:04-0700 pw wrote:
>> 
>> Hello Alan,
>> 
>> I have Hauppauge card which shows up  with dmesg:
>> 
>> $ dmesg | grep ivtv
>> [   13.754774] ivtv: Start initialization, version 1.4.3
>> [   13.754843] ivtv0: Initializing card 0
>> [   13.754845] ivtv0: Autodetected Hauppauge card (cx23415 based)
>> [   13.807849] ivtv0: Autodetected Hauppauge WinTV PVR-350
>> [   13.900645] saa7115 0-0021: saa7115 found @ 0x42 (ivtv i2c driver #0)
>> [   14.630083] saa7127 0-0044: saa7129 found @ 0x88 (ivtv i2c driver #0)
>> [   14.843816] msp3400 0-0040: MSP4448G-A2 found @ 0x80 (ivtv i2c driver #0)
>> [   15.774714] ivtv0: Registered device video0 for encoder MPG (4096 kB)
>> [   15.774755] ivtv0: Registered device video32 for encoder YUV (2048 kB)
>> [   15.774792] ivtv0: Registered device vbi0 for encoder VBI (1024 kB)
>> [   15.774829] ivtv0: Registered device video24 for encoder PCM (320 kB)
>> [   15.774863] ivtv0: Registered device radio0 for encoder radio
>> [   15.774899] ivtv0: Registered device video16 for decoder MPG (1024 kB)
>> [   15.774934] ivtv0: Registered device vbi8 for decoder VBI (64 kB)
>> [   15.774970] ivtv0: Registered device vbi16 for decoder VOUT
>> [   15.775006] ivtv0: Registered device video48 for decoder YUV (1024 kB)
>> [   15.775008] ivtv0: Initialized card: Hauppauge WinTV PVR-350
>> [   15.775054] ivtv: End initialization
>> [   15.810391] ivtv-alsa: module loading...
>> [   15.810756] ivtv0-alsa: snd_ivtv_init: Instance 0 registered as ALSA card 1
>> [   17.092460] ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
>> [   17.171917] ivtv0: Loaded v4l-cx2341x-dec.fw firmware (262144 bytes)
>> [   17.368494] ivtv0: Encoder revision: 0x02060039
>> [   17.368646] ivtv0: Decoder revision: 0x02020023
>> [   17.517677] ivtv0: Loaded v4l-cx2341x-init.mpg firmware (155648 bytes)
>> 
>> 
>> lspci shows:
>> 
>> 5:00.0 Multimedia video controller: Internext Compression Inc iTVC15 (CX23415) Video Decoder (rev 01)
>> 
>> Does that look similar?
>> The important bit is the proper driver for the chip
>> (in this case CX23451)
> 
> No, mine is quite different because I am using an ancient Hauppauge WINTV-GO card (the first TV card that
> was Linux compatible, I believe) which has the following quite
> different information:
> 
> irwin at raven> dmesg |grep bt |grep -v subtractive
> [    6.714024] snd_bt87x 0000:04:00.1: bt87x0: Using board 1, analog, digital (rate 32000 Hz)
> [    6.939279] bttv: driver version 0.9.19 loaded
> [    6.939283] bttv: using 8 buffers with 2080k (520 pages) each for capture
> [    6.939328] bttv: Bt8xx card found (0)
> [    6.939412] bttv: 0: Bt878 (rev 17) at 0000:04:00.0, irq: 16, latency: 64, mmio: 0xfdffe000
> [    6.939424] bttv: 0: detected: Hauppauge WinTV [card=10], PCI subsystem ID is 0070:13eb
> [    6.939426] bttv: 0: using: Hauppauge (bt878) [card=10,autodetected]
> [    6.941956] bttv: 0: Hauppauge/Voodoo msp34xx: reset line init [5]
> [    6.972740] bttv: 0: Hauppauge eeprom indicates model#44801
> [    6.972742] bttv: 0: tuner type=8
> [    7.456487] bttv: 0: audio absent, no audio device found!
> [    7.513649] bttv: 0: Setting PLL: 28636363 => 35468950 (needs up to 100ms)
> [    7.544026] bttv: PLL set ok
> [    7.544719] bttv: 0: registered device video0
> [    7.544778] bttv: 0: registered device vbi0
> [ 9529.244185] bttv: 0: PLL can sleep, using XTAL (28636363)
> [11070.224010] bttv: 0: timeout: drop=28 irq=555286/591006, risc=2202c024, bits: VSYNC HSYNC OFLOW FDSR
> [18408.008165] bttv: 0: reset, reinitialize
> [18408.008202] bttv: 0: PLL can sleep, using XTAL (28636363)
> 
> irwin at raven> lspci |grep -i bt
> 04:00.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11)
> 04:00.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11)
> 
> irwin at raven> lsmod |grep bt
> bttv                  126534  0 btcx_risc              12555  1 bttv
> tveeprom               20593  1 bttv
> videobuf_dma_sg        17248  1 bttv
> videobuf_core          21832  2 bttv,videobuf_dma_sg
> snd_bt87x              13400  5 rc_core                22404  1 bttv
> v4l2_common            12995  5 bttv,tuner,tda7432,msp3400,tvaudio
> videodev              126451  6 bttv,tuner,tda7432,msp3400,tvaudio,v4l2_common
> snd_pcm                88662  4 snd_bt87x,snd_hda_codec,snd_hda_intel,snd_hda_controller
> snd                    65338  38 snd_hda_codec_realtek,snd_bt87x,snd_hwdep,snd_timer,snd_pcm,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
> i2c_algo_bit           12751  2 bttv,i915
> i2c_core               46012  14 drm,bttv,i915,i2c_i801,tuner,drm_kms_helper,tda7432,i2c_algo_bit,msp3400,tvaudio,v4l2_common,tveeprom,tuner_simple,videodev
> 
> Note, snd_bt87x is documented at
> <https://www.kernel.org/doc/html/v4.10/sound/cards/bt87x.html> which
> remarks
> 
> "Some cards do not bother to connect anything to the audio input pins
> of the chip, and some other cards use the audio function to transport
> MPEG video data, so it’s quite possible that audio recording may not
> work with your card."
> 
> Anyhow, I plan to follow up on this possibility by doing google
> searches for whether you can capture audio for this particular
> WINTV-GO card, where I emphasize "particular" because there were
> several different cards with that brand name way back when.
> 
> However, it does seem promising to me that the correct kernel sound
> module is loaded to deal with the digital audio capture from this
> card, and alsamixer recognizes that audio capture possibility with
> what it calls
> 
> Card: Brooktree Bt878
> Chip: Bt87x
> 
> However, I have never done audio capture so I don't know exactly how
> that should be set up so any general advice on that topic would be
> useful to me.  For example, I assume the first step is to use
> alsamixer to mute line-in (since that is not working since yesterday
> in any case to capture the analog output from this card) and unmute
> the digital capture possibility above and put the corresponding volume
> to 100 per cent.  Under these alsamixer conditions my other sound
> tests continue to work well, and alsamixer states the LR capture
> volume is 100 per cent for the "pulseaudio" device. But so far those
> steps don't give me anything but silence on the speakers connected to
> line-out when watching the video part of TV channels from the TV card.
> So in general is there something more I have to do to use audio
> capture and redirect that data to the speakers?
> 
> As I wait for further advice here, I will continue to pursue this
> digital capture possibility via appropriate google searches for my
> specific WINTV-GO card as well as trying different kernels to see if I
> can resurrect the analog audio TV card output connected to line-in
> method that worked before.
> 
>> Hope you are well.
> 
> Yes I am (except for this first Linux headache I have had in a long
> time), and I hope you are well also.
> 
> Alan
> __________________________
> Alan W. Irwin
> 
> Astronomical research affiliation with Department of Physics and Astronomy,
> University of Victoria (astrowww.phys.uvic.ca).
> 
> Programming affiliations with the FreeEOS equation-of-state
> implementation for stellar interiors (freeeos.sf.net); the Time
> Ephemerides project (timeephem.sf.net); PLplot scientific plotting
> software package (plplot.sf.net); the libLASi project
> (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
> and the Linux Brochure Project (lbproject.sf.net).
> __________________________
> 
> Linux-powered Science
> __________________________
> 
> _______________________________________________
> Discuss mailing list
> Discuss at vlug.org
> http://vlug.org/mailman/listinfo/discuss_vlug.org



More information about the Discuss mailing list