Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Tue 29 Jul 2014, 19:26
All times are UTC - 4
 Forum index » Advanced Topics » Hardware
Two DVB-T Tuners in Lucid; neither works (Back to 4.1.2)
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 1 [12 Posts]  
Author Message
Mercedes350se

Joined: 16 Apr 2008
Posts: 632

PostPosted: Sat 29 Jun 2013, 02:13    Post subject:  Two DVB-T Tuners in Lucid; neither works (Back to 4.1.2)  

Back in early 2012 I eventually got the Nova T-500 DVB-T card working. My method was described here.

This was in puppy 4.1.2.

I am also interested in SDR so recently purchased a Ezcap USB DVB-T tuner.

Details are: Ezcap EzTV645 which has the rtl2832u chip and the FC0013 tuner. This site shows the following for my device ID of 0x0bda 0x2838: Tuner E4000. However the tuner, is in fact, a FC0013. Looking more closely at the information provided by Hardinfo the product ID is 0xbda 0x2838 i.e. not 0x0bda. Even more confused!

Now trying to get them working in Lucid.

No joy yet for the Ezcap as discussed here.

Is it DOA? The dvb-usb-rtl2832u.ko file exists in
/lib/modules/2.6.33.2/kernel/drivers/media/dvb/dvb-usb/dvb-usb-rtl2832u.ko
so all seems to be good there at least.

To check I thought I would try the Nova. No joy here either. Check to see that the mt2060.ko file exists.

Yes, in
/lib/modules/2.6.33.2/kernel/drivers/media/common/tuners/mt2060.ko

Totally confused given that the Nova works a treat in 4.1.2.

For the sake of discussion I have part of the output from dmesg:

dvb-usb: found a 'RTL2832U DVB-T USB DEVICE' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (RTL2832U DVB-T USB DEVICE)
8139too 0000:00:10.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
eth0: RealTek RTL8139 at 0xf8534000, 00:18:4d:e9:9c:55, IRQ 19
DVB: registering adapter 0 frontend 0 (Realtek RTL2832 DVB-T RTL2836 DTMB)...
dvb-usb: RTL2832U DVB-T USB DEVICE successfully initialized and connected.
dvb-usb: found a 'RTL2832U DVB-T USB DEVICE' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (RTL2832U DVB-T USB DEVICE)
DVB: registering adapter 1 frontend 0 (Realtek RTL2832 DVB-T RTL2836 DTMB)...
dvb-usb: RTL2832U DVB-T USB DEVICE successfully initialized and connected.
usbcore: registered new interface driver dvb_usb_rtl2832u
C-Media PCI 0000:00:05.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
dib0700: loaded with support for 14 different device-types
dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T)
DVB: registering adapter 2 frontend 0 (DiBcom 3000MC/P)...
MT2060: successfully identified (IF1 = 1220)
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T)
DVB: registering adapter 3 frontend 0 (DiBcom 3000MC/P)...
MT2060: successfully identified (IF1 = 1220)
input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:0f.2/usb2/2-1/input/input5
dvb-usb: schedule remote query interval to 50 msecs.
dvb-usb: Hauppauge Nova-T 500 Dual DVB-T successfully initialized and connected.
usbcore: registered new interface driver dvb_usb_dib0700

Clues/ideas/suggestions please.

EDIT: I would be pleased if anyone with a working USB tuner in their PC would post the equivalent part of the dmesg output so that I may get some idea ...

TIA.

Last edited by Mercedes350se on Mon 05 Aug 2013, 00:59; edited 5 times in total
Back to top
View user's profile Send private message 
Mercedes350se

Joined: 16 Apr 2008
Posts: 632

PostPosted: Sun 30 Jun 2013, 01:32    Post subject:  

Hmm. Today my dmesg is:

dvb-usb: found a 'RTL2832U DVB-T USB DEVICE' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (RTL2832U DVB-T USB DEVICE)
DVB: registering adapter 0 frontend 0 (Realtek RTL2832 DVB-T RTL2836 DTMB)...
dvb-usb: RTL2832U DVB-T USB DEVICE successfully initialized and connected.
dvb-usb: found a 'RTL2832U DVB-T USB DEVICE' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (RTL2832U DVB-T USB DEVICE)
DVB: registering adapter 1 frontend 0 (Realtek RTL2832 DVB-T RTL2836 DTMB)...
dvb-usb: RTL2832U DVB-T USB DEVICE successfully initialized and connected.
usbcore: registered new interface driver dvb_usb_rtl2832u
C-Media PCI 0000:00:05.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
dib0700: loaded with support for 14 different device-types
dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in cold state, will try to load a firmware
usb 2-1: firmware: requesting dvb-usb-dib0700-1.20.fw
dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw'
dib0700: firmware started successfully.

dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T)
DVB: registering adapter 2 frontend 0 (DiBcom 3000MC/P)...
ip_tables: (C) 2000-2006 Netfilter Core Team
MT2060: successfully identified (IF1 = 1220)
nf_conntrack version 0.5.0 (16171 buckets, 64684 max)
CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or
sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T)
DVB: registering adapter 3 frontend 0 (DiBcom 3000MC/P)...
MT2060: successfully identified (IF1 = 1220)
input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:0f.2/usb2/2-1/input/input5
dvb-usb: schedule remote query interval to 50 msecs.
dvb-usb: Hauppauge Nova-T 500 Dual DVB-T successfully initialized and connected.
usbcore: registered new interface driver dvb_usb_dib0700

I have highlighted what I think are the important differences for the Nova-T.
I can now get the correct tzap output using for example

Code:
tzap -r -a 2 win


and because it is a twin tuner in another terminal

Code:
tzap -r -a 3 seven


I have done nothing between yesterday and today - totally confused!

I used this .pet thinking it would be correct.

Note the Sandberg Mini DVB-T/DAB dongle mentioned does work according to another post.

Two things.

1. Why is the RTL2832U initially found in a warm state but the Nova-T is found in a cold state?

2 It would seem that the firmware for the RTL2832U is not found. What is the correct name for it? A 'net search will then follow.

UPDATE: Both xine and gxine freeze when trying to play DVB. Oh dear!
Back to top
View user's profile Send private message 
Mercedes350se

Joined: 16 Apr 2008
Posts: 632

PostPosted: Mon 01 Jul 2013, 04:28    Post subject:  

A few small steps for mankind!

1. I have come to the conclusion that for the Nova-T to be properly initialised it needs to be started from complete reboot.

Question: Is it possible to determine why it is not initialised properly from a warm boot - probe the system somehow?

2. Given that xine in Lucid didn't work I removed it and installed 0.99.5 which does work in 4.1.2. Installed the lib .pet package and also the extra codec package.

I get to the stage where I can call up the playlist - channels that can be selected - and xine freezes. If I start it in ROX I get

input_dvb: continuing in get_instance

Question: Any ideas why?

3. According to this site the output from dmesg regarding the USB tuner is correct.

Question: If the USB tuner is recognised and initialised correctly then why don't I get the FE_HAS_LOCK when I run tzap?
Back to top
View user's profile Send private message 
Mercedes350se

Joined: 16 Apr 2008
Posts: 632

PostPosted: Mon 01 Jul 2013, 21:53    Post subject:  

Added USB tuner details in first post.
Back to top
View user's profile Send private message 
Mercedes350se

Joined: 16 Apr 2008
Posts: 632

PostPosted: Tue 02 Jul 2013, 03:53    Post subject:  

Mercedes350se wrote:


1. Why is the RTL2832U initially found in a warm state but the Nova-T is found in a cold state?



For reference purposes I include this for a different device:

usb 1-9: new high speed USB device using ehci_hcd and address 3
usb 1-9: configuration #1 chosen from 1 choice
Afatech DVB-T: Fixing fullspeed to highspeed interval: 16 -> 8
input: Afatech DVB-T as /devices/pci0000:00/0000:00:02.1/usb1/1-9/1-9:1.1/input/input5
generic-usb 0003:15A4:9016.0001: input: USB HID v1.01 Keyboard [Afatech DVB-T] on usb-0000:00:02.1-9/input1
dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in cold state, will try to load a firmware
usb 1-9: firmware: requesting dvb-usb-af9015.fw
dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw'

dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (Afatech AF9015 DVB-T USB2.0 stick)
af9013: firmware version:4.95.0
DVB: registering adapter 0 frontend 0 (Afatech AF9013 DVB-T)...
MT2060: successfully identified (IF1 = 1220)
dvb-usb: Afatech AF9015 DVB-T USB2.0 stick successfully initialized and connected.
usbcore: registered new interface driver dvb_usb_af9015

The highlighted lines do not appear for my device which I assume means that no tuner driver is being loaded hence no joy with tzap.
Back to top
View user's profile Send private message 
DC


Joined: 30 Apr 2006
Posts: 353
Location: Maidenhead, England

PostPosted: Tue 09 Jul 2013, 12:41    Post subject:  

Hi Mercedes350se,

my dmesg

Code:
# dmesg | grep dvb
usb 1-5: dvb_usb_v2: found a 'Realtek RTL2832U reference design' in warm state
usbcore: registered new interface driver dvb_usb_rtl28xxu
usb 1-5: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
usb 1-5: dvb_usb_v2: schedule remote query interval to 400 msecs
usb 1-5: dvb_usb_v2: 'Realtek RTL2832U reference design' successfully initialized and connected


This is a Sandberg Mini DVB-T/DAB dongle.
Which works in Fatdog 620/621 various precise puppys and lupu 528
playing through VLC (ver 2.06 in Fatdog)

The RTL2832U driver is now part of the kernel after version 3.8 I think
So nothing to do in fatdog
I have some old bash scripts which pass the DVB channels to VLC which I use mostly for listening to the radio (DVB)

Not tried sdr yet but today started looking which is how I saw this thread. Looking at http://www.rtl-sdr.com/sdr-j-decoding-dab-radio-in-software-using-rtl-sdr/ it does require a 64bit OS.

DC

_________________
a little bit of knowledge and I'm dangerous
Back to top
View user's profile Send private message 
Philh

Joined: 17 May 2006
Posts: 99
Location: England

PostPosted: Tue 09 Jul 2013, 13:54    Post subject:  

Ive tried two devices Avermedia Green volar and a DTV300 Realtek
usb 2-3: new high-speed USB device number 4 using ehci_hcd
usb 2-3: New USB device found, idVendor=07ca, idProduct=a835
usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-3: Product: A835
usb 2-3: Manufacturer: AVerMedia TECHNOLOGIES, Inc
usb 2-3: SerialNumber: 3047456001790


usb 2-3: new high-speed USB device number 5 using ehci_hcd
usb 2-3: New USB device found, idVendor=1f4d, idProduct=d803
usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-3: Product: RTL2838UHIDIR
usb 2-3: Manufacturer: Realtek
usb 2-3: SerialNumber: 000000041

I couldnt get the avermedia one to work.
But the Realtek worked after installing
dvb-usb-rtl2832u_k2.6.33.2.pet
http://www.murga-linux.com/puppy/viewtopic.php?mode=attach&id=40774&sid=dd5c80080fe5ff69467acbf891841239

usb 2-3: new high speed USB device using ehci_hcd and address 4
dvb-usb: found a 'USB DVB-T Device' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (USB DVB-T Device)
DVB: registering adapter 0 frontend 0 (Realtek RTL2832 DVB-T RTL2836 DTMB)...
dvb-usb: USB DVB-T Device successfully initialized and connected.dvb-usb: found a 'USB DVB-T Device' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (USB DVB-T Device)
DVB: registering adapter 1 frontend 0 (Realtek RTL2832 DVB-T RTL2836 DTMB)...
dvb-usb: USB DVB-T Device successfully initialized and connected.
usbcore: registered new interface driver dvb_usb_rtl2832u

I guess the avermedia needs a correct .ko file

I tried them both in slacko 550 but neither worked.
Back to top
View user's profile Send private message 
gcmartin

Joined: 14 Oct 2005
Posts: 4116
Location: Earth

PostPosted: Tue 09 Jul 2013, 17:00    Post subject: Historical PUP distros which interoperate with TV tuners  

@DC offers couple platforms ideas which can provide OOTB functionality.

Another platform is Pemasu's distros, which too, has a history of interoperability with TV tuners. His latest distros are here. ===> Here to help

_________________
Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Engine or use DogPile
Back to top
View user's profile Send private message 
Mercedes350se

Joined: 16 Apr 2008
Posts: 632

PostPosted: Wed 10 Jul 2013, 02:12    Post subject:  

DC wrote:
This is a Sandberg Mini DVB-T/DAB dongle.
Which works in Fatdog 620/621 various precise puppys and lupu 528
playing through VLC (ver 2.06 in Fatdog)


I know the Sandberg does because it is mentioned in another post.

The driver .pet that I installed in Lucid does not have the driver for the fc0013 tuner in the Ezcap dongle.

gcmartin wrote:
Here to help


Thank you.

I have gone back to 4.1.2 because xine does not work in Lucid, well mine anyway, - this is the subject of another thread.

All I need to do now is find the correct .fw file and, fingers crossed, good to go. I have seen a driver file on the 'net somewhere patched for kernel 3. something, which is supposed to compile in 2.6 kernels, but naturally I did not bookmark it and now for the life of me I cannot find it.
Back to top
View user's profile Send private message 
peterw

Joined: 19 Jul 2006
Posts: 66
Location: UK

PostPosted: Wed 10 Jul 2013, 02:22    Post subject: dvb-t hardware
Subject description: Adding tuner hardware
 

Hi philh

Just a correction to your so file comment. What you need is a .fw in your /lib/firmware. For instance I always add dvb-usb-adstech-usb2-02.fw to mine. It never seems to appear in puppies. I think I have seen a fw file for Avermedia units but am away from home now and so can't be sure.

Regards
peterw
Back to top
View user's profile Send private message 
pemasu


Joined: 08 Jul 2009
Posts: 5463
Location: Finland

PostPosted: Wed 10 Jul 2013, 05:32    Post subject:  

# modinfo dvb-usb-rtl28xxu
filename: /lib/modules/3.9.8-upup/kernel/drivers/media/usb/dvb-usb-v2/dvb-usb-rtl28xxu.ko
license: GPL
author: Thomas Mair <thomas.mair86@googlemail.com>
author: Antti Palosaari <crope@iki.fi>
description: Realtek RTL28xxU DVB USB driver
alias: usb:v185Bp0620d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1D19p1104d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1B80pD393d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1B80pD3A8d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0CCDp00D7d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1D19p1102d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0CCDp00D3d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0413p6680d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1D19p1101d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1F4DpC803d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0CCDp00E0d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0CCDp00B3d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1F4DpB803d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0CCDp00A9d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0BDAp2838d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0BDAp2832d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v14AAp0161d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v14AAp0160d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0BDAp2831d*dc*dsc*dp*ic*isc*ip*in*
depends: dvb_usb_v2,rtl2830,rc-core
intree: Y
vermagic: 3.9.8-upup SMP mod_unload modversions 686
parm: adapter_nr:DVB adapter numbers (array of short)
#
Back to top
View user's profile Send private message 
Philh

Joined: 17 May 2006
Posts: 99
Location: England

PostPosted: Wed 10 Jul 2013, 10:32    Post subject:  

I did try putting dvb-usb-af9035-01.fw in /lib/firmware in 528 but it didnt bring it to life.

But Ive just tried the avermedia in Pemasu raring 3.9.8.1
dmesg told me it wanted dvb-usb-af9035-02.fw
So I put that in and it works
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 1 of 1 [12 Posts]  
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Hardware
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
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1037s ][ Queries: 11 (0.0034s) ][ GZIP on ]