How-to: DVB-T USB TV tuner with Genie 619W (Afatech Chip)

How to do things, solutions, recipes, tutorials
Message
Author
paulski
Posts: 130
Joined: Fri 06 Oct 2006, 15:30
Location: Cologne, Germany &/or Perth, Australia

How-to: DVB-T USB TV tuner with Genie 619W (Afatech Chip)

#1 Post by paulski »

I got a Genie 618W USB DVB-T dongle as a gift.
Found out the Chip in the thing is from Afatech with Vendor ID 015a4, PID 09016

I got it working in Puppy 3 series, could not get it to run in puppy 4 series, but now have it working in Puppy 5.11 Lucid

Most of the information in this thread goes into how it worked for the older Puppies or the attempts to get it going. For Puppy 5 its quick and easy - just keep reading.

First regardless of the Puppy version you need to do this:

From http://www.linuxtv.org get hold of a firmware file "dvb-usb-af9015.fw" and copy it to /lib/firmware/

I am using firmware version 4.95 found at
http://www.otit.fi/~crope/v4l-dvb/af901 ... es/4.95.0/


For Puppy 5.11


You still need to install linux tv apps
http://dotpups.de/dotpups/Multimedia/Mp ... -1.1.1.pet

That gives you the scan command not included in Puppy 5.11

Find in the internet the initial scan file for your area
http://linuxtv.org/hg/dvb-apps/file/afd ... can/dvb-t/
and run scan as following in a console
(in the example my initial scan file is called "de-Bonn")

Code: Select all

scan de-Bonn | tee channels.conf
Watch it tune in to the stations it finds and build a channels.conf file.

Put channels.conf in your root directory.

Now get a reasonable media player like VLC. You will find it in the quickpet software.

Make this script to start VLC

Code: Select all

#!/bin/sh
vlc -vvv /root/channels.conf
Use the next track arrow thingo to change channels, or the playlist --- easy!


The Puppy 4 series story

Problem is I needed to run it on a Puppy 4.0 or a Retro Puppy 4.1 as my old machines are all IDE hard drive based.
In other words I needed to get the device drivers working on a 2.6.21.7 Kernel


Then reading the info at linuxtv.org I realized I would need the following drivers (modules)
- af9013.ko
- dvb-usb-af9015.ko
And one of tuner modules:
- mt2060.ko
- tda18271.ko

Great now I tried to compile some of the 9015 drivers- borrowed a pup 3 kernel source sfs (no true puppy 4.0 version around)
http://distro.ibiblio.org/pub/linux/dis ... rc_301.sfs
and the devx sfs
http://distro.ibiblio.org/pub/linux/dis ... vx_400.sfs
and away I went.
Compiling went okay. Copied the files to:
/lib/modules/2.6.21.7/kernel/drivers/media/dvb/frontends/af9013.ko
/lib/modules/2.6.21.7/kernel/drivers/media/dvb/dvb-usb/mt2060.ko
/lib/modules/2.6.21.7/kernel/drivers/media/dvb/dvb-usb/dvb-usb-af9015.ko

Then turned on the device using:

Code: Select all

modprobe dvb_usb
insmod /lib/modules/2.6.21.7/kernel/drivers/media/dvb/frontends/af9013.ko
insmod /lib/modules/2.6.21.7/kernel/drivers/media/dvb/dvb-usb/mt2060.ko
insmod /lib/modules/2.6.21.7/kernel/drivers/media/dvb/dvb-usb/dvb-usb-af9015.ko
(Note the order of these commands was important)
and looked at the output of dmesg

Code: Select all

dmesg | grep dvb
and it seemed to be working - hurrah!

Then after running scan (see other DVB-T threads for the linuxtv-DVB-apps-1.pet package with DVB utilities)
and a suitable initial scan file I scoured from the internet (in this case de-Bonn)

Code: Select all

scan de-Bonn >mychannels.conf
I got tuning failed errors. :(
Nevertheless the modules may be okay for other Afatech based units - They are attached to this thread (Lintv modules, not the oem ones)
NOTE: If you are using a newer kernel (like 2.6.25 - normal versions of puppy 4.1 etc you may have to compile your own). This one here is only for 2.6.21.7 kernel - Puppy 4.0 and retro versions of newer puppies.

Further searching lead me to some OEM drivers that were somehow GPL released.
I compiled them and copied them to
/lib/modules/2.6.21.7/kernel/drivers/media/dvb/dvb-usb/

Then initialized the unit with:

Code: Select all

modprobe dvb_usb
insmod /lib/modules/2.6.21.7/kernel/drivers/media/dvb/dvb-usb/dvb-af901x.ko
Tried scan again as above and this time it worked.
Copied my "mychannels.conf" to channels.conf in root/.xine/
Ran the MAKEDEV-DVB.sh script (part of the DVB utilties)
Ran Gxine and the first channel in channels.conf popped up. YES!!!!
I have also run mplayer successfully - see other threads on how to run it from the command line.

Attached is a small archive of the oem driver modules and the firmware file in the right place for puppy 4.0 and possible retro puppys

For more tips on DVB-T with puppy there are quite a few threads
try them with DVB as a keyword in puppy google search
http://wellminded.com/puppy/pupsearch.html[/b]
Attachments
oem-afatech901x-modules-pup4.tar.gz
(83.86 KiB) Downloaded 1112 times
Last edited by paulski on Sat 20 Nov 2010, 22:05, edited 8 times in total.

paulski
Posts: 130
Joined: Fri 06 Oct 2006, 15:30
Location: Cologne, Germany &/or Perth, Australia

#2 Post by paulski »

Here are some helpful links if you need to compile it yourself.
Perhaps someone can do it for Puppy 4.1.2??

Linuxtv source files for af9015 kernel modules

http://linuxtv.org/hg/~anttip/af9015/
one such example
http://linuxtv.org/hg/~anttip/af9015/ar ... 282.tar.gz
Afatech version - not further developed but worked for me
http://www.digittrade.de/shop/info/stic ... 2.6.20.tar
Firmware files
http://www.otit.fi/~crope/v4l-dvb/af901 ... -af9015.fw
Other useful links
Mplayer download (look in the folder there for the extra libraries too)
http://puppyfiles.org/dotpupsde/dotpups ... er-1.0rc1/

DVD tv applications (like scan and the script for making the device nodes)
http://dotpups.de/dotpups/Multimedia/Mp ... -1.1.1.pet

Initial scan files for the scan utility
http://linuxtv.org/hg/dvb-apps/file/afd ... can/dvb-t/

Background information on other afatech chip based usb dongles

http://linuxtv.org/wiki/index.php/Afatech_AF9015

http://www.linuxtv.org/wiki/index.php/H ... ck#Drivers

One of the many interesting threads on other DVB-T devices with a few more useful tips
http://www.murga-linux.com/puppy/viewtopic.php?t=29513

and don't forget to try puppy search as mentioned in the first post in this thread.

paulski
Posts: 130
Joined: Fri 06 Oct 2006, 15:30
Location: Cologne, Germany &/or Perth, Australia

Backward compatibility with puppy3

#3 Post by paulski »

I tried the drivers on a Puppy 3.01 based pupeee for Eeepc
I got "segmentation fault"s using them with insmod command. I think that means the DVB support modules included with Puppy 3.01 are outdated or not compatible with these modules even though they are okay for a 2.6.21 kernel, or the pupeee distro is missing them.

Update: Got this to work too - copied the modules and firmware file across then did

Code: Select all

depmod
Then restart puppy and
in a console use modprobes in this order:

Code: Select all

modprobe dvb-pll
modprobe dvb-core
modprobe dvb-af901x
modprobe dvb-usb
I'm not exactly sure why but hey it works in Pupeee too!
Last edited by paulski on Wed 17 Dec 2008, 20:19, edited 2 times in total.

User avatar
davids45
Posts: 1326
Joined: Sun 26 Nov 2006, 23:33
Location: Chatswood, NSW

#4 Post by davids45 »

G'day,

Thanks for posting these links and results with your DVB card.

I have a hybrid Tevion (Kworld) card which I'm hoping to get running on the digital transmissions so your info looks a great starting point.
I have the analog part working via tvtime and xawtv but without sound.

David S.

paulski
Posts: 130
Joined: Fri 06 Oct 2006, 15:30
Location: Cologne, Germany &/or Perth, Australia

not going yet for Puppy 4.11 2.6.25

#5 Post by paulski »

Now I'm trying to get the same unit going in puppy 4.11 with the 2.6.25 kernel.
Its not proving as easy as the older 2.6.21 kernel puppies (pup 3.1, 4.0, or the 4.11, 4.12 retros).

I'm probably already 90% there, just one error

Compiling the OEM Linux_MT2060_2.6.20.tar does not work.
A newer driver from digitrade is much the same as the "mercurial" one from linux TV and seems to be suited for 2.6.26 kernels.
http://www.digittrade.de/

They both compile - the problem is when I insert the modules I get a conflict.

First unload these modules already in puppy

Code: Select all

rmmod dvb-usb
rmmod dvb-pll
rmmod dvb-core
Then insert these

Code: Select all

insmod dvb-pll.ko
insmod dvb-core.ko
insmod dvb-usb.ko
insmod af9013.ko
insmod mt2060.ko
insmod dvb-usb-af9015.ko
Problem is when I check it all with "dmesg" I get something like
dvb-usb-af9015 does not agree with dvb-usb-init - unknown symbol.

Mmm - I think it does not like some other module built into puppy. Perhaps i2c-core is too old, or the compiled modules for the dvb stuff are all too new.

Checked other distros info- a lot of hate mail out there
One guy apparently got it working for gentoo on a 2.6.25 kernel.

Any ideas what I could try next?

paulski
Posts: 130
Joined: Fri 06 Oct 2006, 15:30
Location: Cologne, Germany &/or Perth, Australia

#6 Post by paulski »

Now testing using Puppy 4.31, newer kernel (2.6.30.5)

Most of the modules are now built in except the mt2060.ko.
That compiled from the latest source from the mercurial repository, copied across to the /lib/modules......./frontends/ folder
then I did

Code: Select all

depmod
then a similar modprobe list as posted earlier

dmesg looks good, w_scan appears to work
...
Edit: Note - There are firmware files in Puppy already there- tarballed up.
At this point I am unsure if they unpack automatically or not but you can put any dvb-usb-af015.fw file in /lib/firmware and it gets picked up
I've tried the latest (4.95.0) and four older firmware files with no success.

I've tried removing usbhid (rmmod usbhid) to stop any confusion about the device being a keyboard with no sucess.

I've even tried compiling some of the "vendor supplied" modules mentioned on the linuxtv.org website - but they either don't compile or really hate other features of the new kernel.

Surprisingly dmesg output gives no errors:

Code: Select all

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
lsmod also outputs reasonable stuff (just the relevant stuff shown below)

Code: Select all

Module                  Size  Used by
mt2060                  4720  1 
af9013                 20048  1 
dvb_usb_af9015         29196  0 
dvb_usb                19352  1 dvb_usb_af9015
dvb_core               87368  1 dvb_usb
i2c_core               23776  7 mt2060,af9013,dvb_usb_af9015,dvb_usb,videodev,nvidia,i2c_nforce2
usbcore               138160  9 dvb_usb_af9015,dvb_usb,gspca_pac207,gspca_main,usbhid,usb_storage,ohci_hcd,ehci_hcd
I cant revert to an older retro puppy on this computer so I must keep trying.

Other forums for other distros show similar problems.

Either w_scan or scan work partially but cannot tune in
Scan tries something and then "tuning failed!" crops up on every channel.

My guess is it lies in the order of modprobing somehow, and finding a way to stop the automatic modprobing done with the new kernel. That was the case with the modules that worked on older puppies.

Having said that I have never got the drivers from mecurial repositories to work for me, only the old OEM drivers.

Any new ideas to try would be appreciated.
...
Last edited by paulski on Sun 03 Jan 2010, 23:04, edited 2 times in total.

GeePS
Posts: 19
Joined: Fri 31 Jul 2009, 02:30

#7 Post by GeePS »

paulski wrote:Now testing using Puppy 4.31, newer kernel (2.6.30.5)

Now trying to get it to work with gxine or mplayer - not going yet but I think its a small problem
I was running Puppy 4.2 but recently upgraded to 4.3. Awesome stuff. I also tried out the MacPup version with Firefox, which is what I am running now. I like it, as my work machine is a Mac. I am impressed with the various desktop configurations available with Puppy compared to other LInux I have been trying out.

I have a Hauppagge 850 that was detected, but I ended up having to locate and install firmware for it. That part is working according to dmesg. My problem is that now if I try gxine or xine, I keep getting the message that it cannot find channels.conf. I have located sample files and created one in the correct format. I tried putting them in the .gxine, the .xine, the .tzap and the dvb directories. Either I am putting the file in the wrong place, or that isn't really the problem. Here is my dmesg if anyone has any ideas, please let me know. If there is a better player to use for HDTV signals over the air I would appreciate any info on that as well.

DMESG:
usb 1-1: new high speed USB device using ehci_hcd and address 5
usb 1-1: configuration #1 chosen from 1 choice
au0828: i2c bus registered
tveeprom 2-0050: Hauppauge model 72301, rev B3F0, serial# 6165768
tveeprom 2-0050: MAC address is 00-0D-FE-5E-15-08
tveeprom 2-0050: tuner model is Xceive XC5000 (idx 150, type 76)
tveeprom 2-0050: TV standards NTSC(M) ATSC/DVB Digital (eeprom 0x88)
tveeprom 2-0050: audio processor is AU8522 (idx 44)
tveeprom 2-0050: decoder processor is AU8522 (idx 42)
tveeprom 2-0050: has no radio, has IR receiver, has no IR transmitter
hauppauge_eeprom: hauppauge eeprom: model=72301
au8522 2-0047: creating new instance
au8522_decoder creating new instance...
tuner 2-0061: chip found @ 0xc2 (au0828)
xc5000 2-0061: creating new instance
xc5000: Successfully identified at address 0x61
xc5000: Firmware has not been loaded previously
xc5000: waiting for firmware upload (dvb-fe-xc5000-1.1.fw)...
i2c-adapter i2c-2: firmware: requesting dvb-fe-xc5000-1.1.fw
xc5000: firmware read 12332 bytes.
xc5000: firmware upload
au8522 2-0047: attaching existing instance
xc5000 2-0061: attaching existing instance
xc5000: Successfully identified at address 0x61
xc5000: Firmware has been loaded previously
DVB: registering new adapter (au0828)
DVB: registering adapter 0 frontend 0 (Auvitek AU8522 QAM/8VSB Frontend)...
Registered device AU0828 [Hauppauge HVR850]

paulski
Posts: 130
Joined: Fri 06 Oct 2006, 15:30
Location: Cologne, Germany &/or Perth, Australia

#8 Post by paulski »

Hi GeePS,

Looks like you are well along the way to getting your DVB going.
Check out some links to more thorough threads earlier in this thread, as this one is very device specific. The other threads mention mplayer and a few other alternatives. Dont forget puppy search also mentioned earlier in this thread and put in "AU0828"- someone may already have worked out what to do with your card.

Generally put your channels.conf in root/.xine/ and it should work, so either the file is not good or not readable or its just not the problem. Try opening it in a text editor and see if it looks okay.

I don't know much about your device but I see no evidence of a tuner in the dmesg. I'm out of my depth there, but if you haven't got a working tuner, then channels.conf won't help good or bad.

Try in the terminal wscan and see if it works.


....................................

For others following the use of the Afatech DVB chip here - I still can't get it going in puppy 4.31 and neither can a lot of people in other new distros (Ubuntu, Suse etc.) with the newer kernels. I think it comes down to automatic modprobing that is loading the modules in the wrong order before I can do anything to stop it. Will investigate.

GeePS
Posts: 19
Joined: Fri 31 Jul 2009, 02:30

#9 Post by GeePS »

paulski wrote:
I don't know much about your device but I see no evidence of a tuner in the dmesg. I'm out of my depth there, but if you haven't got a working tuner, then channels.conf won't help good or bad.

Line 6 in dmesg above is the following:
tveeprom 2-0050: tuner model is Xceive XC5000 (idx 150, type 76)
Looks like tuner info to me, but let me know if I am interpreting wrong. Not sure what to do with an Xceive XC5000 anyway.


Try in the terminal wscan and see if it works.
wscan doesn't seem to exist on my distro or I am running it in the wrong directory. Any special syntax I should use?

I will do some additional searching on your other suggestions.

Thanks



....................................

For others following the use of the Afatech DVB chip here - I still can't get it going in puppy 4.31 and neither can a lot of people in other new distros (Ubuntu, Suse etc.) with the newer kernels. I think it comes down to automatic modprobing that is loading the modules in the wrong order before I can do anything to stop it. Will investigate.

John Lewis
Posts: 148
Joined: Mon 03 Dec 2007, 10:19
Location: Albany West Australia

#10 Post by John Lewis »

Paulski,

I don't know if you solved your problem or not. Perhaps this will work for you. It worked on mine which seems to likely have the same chip.

John Lewis

http://www.murga-linux.com/puppy/viewtopic.php?t=51421

paulski
Posts: 130
Joined: Fri 06 Oct 2006, 15:30
Location: Cologne, Germany &/or Perth, Australia

#11 Post by paulski »

Thanks John,

No I haven't got mine going yet. Yours is apparently working, that's really good news (also good to know that SBS have digital in the southwest, which I need when I get home).

Could you send me the output of your dmesg and lsmod commands with the DVB-T unit plugged in, perhaps in a personal message so they don't clutter things up here.
It might just help me debug my system. I think it comes down to the tuner.

just do

Code: Select all

dmesg > output1.txt
and

Code: Select all

lsmod > output2.txt
and you should be able to capture it.

paulski
Posts: 130
Joined: Fri 06 Oct 2006, 15:30
Location: Cologne, Germany &/or Perth, Australia

Its the tuner combination

#12 Post by paulski »

John sent me a personal message with the lsmod and dmesg output.

His DVB-T unit has the Afatech chip (same) but a different tuner (MXL5005S or MaxLinear MXL5005S)

That's gotta be the reason. The built in drivers are okay for his tuner and DVB-T chip combination but are dodgy (unreliable/bad) for the mt2060 tuner with the Afatech chip together in the Genie device.

Thanks John, its a step in the right direction. Now I know where I am going with this, even if a solution isnt totally obvious.

John Lewis
Posts: 148
Joined: Mon 03 Dec 2007, 10:19
Location: Albany West Australia

#13 Post by John Lewis »

Glad to help paulski even if it didn't resolve your problem. The problem seems to be that even the same device can have different component chips depending when and where it was made.

I'm trying to sort one out for a friend that uses an rtl2832u driver. I've not cracked it yet and may need to ask for help soon. I have the purported sources but can't get them to compile.

I hope you eventually succeed with yours.

John Lewis

Edit: I just reread your posts. Sudden thought. I was getting similar "tuning failed" errors to yours until I connected a different decent antenna. The little toy supplied didn't work at all.

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

Working - 'Afatech DVB-T USB1.1 stick' on Puppy 4.3.1

#14 Post by peebee »

Success report...........

Got dvb-t working fairly painlessly on Puppy 4.3.1 K2.6.30.5 running on HP 550 laptop.

Plugged in the 'Afatech DVB-T USB1.1 stick' which was detected and firmware from file 'af9005.fw' was loaded. (Cheap usb dvb-t stick bought off ebay)
(Vendor id 15a4 device id 9020 15a4:9020)

Installed the Xine media player xine-ui-0.99.5 using the Package Manager

Ran the scan command in terminal window to create the channels.conf file:
scan /usr/share/dvb/dvb-t/uk-Malvern > /tmp/channels.conf

Copied the channels.conf to /root/.xine

Ran xine and clicked the DVB-T button and could view dvb-t transmitted from the Malvern transmitter.

Well done yet again Puppy :-)

Cheers!
Peter - in Malvern

John Lewis
Posts: 148
Joined: Mon 03 Dec 2007, 10:19
Location: Albany West Australia

#15 Post by John Lewis »

Great to hear you have it working.

Have a look here about halfway down the Gtb-DVB.pet.

You do need to install a couple of extras, GtkBasic003e.pet and PuppyBasic-2.6.pet. to get it to work but it does make life easier.
Links to all you need are on the above link

John Lewis

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

#16 Post by peebee »

Hi John

I've loaded the Gtb-DVB .pet and its dependancies as you suggested but regret to say have not had great success.

When started, Gtb-DVB took over my whole screen, gxine seemed to give errors but in blank screens and Gxine only displayed a very small picture in a window that seemed broken up and corrupted.

I had to kill all the windows and reboot to get back to normal.

It was such a complex interaction that it is difficult to exactly describe what happened.

Xine seems to work much more relaibly although its gui is a bit clunky - but it does show DVB-T programmes in full screen .....

Not a success I'm afraid.

Cheers
Peter

caramelo
Posts: 1
Joined: Thu 17 Jun 2010, 20:48

#17 Post by caramelo »

Hi all

Someone can explain me how to compile the drivers please?

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

#18 Post by peebee »

Which version of Puppy are you running?? You should always include this info in your posts

Certainly from 4.3.1 non-retro the drivers are built-in so no compiling is needed???

Cheers
Peter

Got dvb-t working fairly painlessly on Puppy 4.3.1 K2.6.30.5 running on HP 550 laptop.

Plugged in the 'Afatech DVB-T USB1.1 stick' which was detected and firmware from file 'af9005.fw' was loaded. (Cheap usb dvb-t stick bought off ebay)
(Vendor id 15a4 device id 9020 15a4:9020)

User avatar
Whitesnow
Posts: 118
Joined: Tue 20 Nov 2007, 19:18
Location: Italy

Afatech DVB-T 2

#19 Post by Whitesnow »

Hi, I have a problem on 4.3.1. My usbkey (eBay's one) doesn't work. I compiled missing modules from source at Linuxtv (update for this chip), but it isn't enough. Firmware is from packages in this thread.

Could you please help?

Where I can find dvb-utils/apps? I don't locate them with forum search tool.

Thanks in advance.

Bye.


Sep 15 15:49:58 (none) user.info kernel: usb 2-1: new high speed USB device using ehci_hcd and address 9
Sep 15 15:49:58 (none) user.info kernel: usb 2-1: configuration #1 chosen from 1 choice
Sep 15 15:49:58 (none) user.warn kernel: af9015: tuner id:179 not supported, please report!
Sep 15 15:49:58 (none) user.info kernel: Afatech DVB-T 2: Fixing fullspeed to highspeed interval: 10 -> 7
Sep 15 15:49:58 (none) user.info kernel: input: Afatech DVB-T 2 as /devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.1/input/input13
Sep 15 15:49:58 (none) user.info kernel: generic-usb 0003:15A4:9016.0008: input: USB HID v1.01 Keyboard [Afatech DVB-T 2] on usb-0000:00:1d.7-1/input1


# lsmod | grep dvb
dvb_pll 8776 0
dvb_usb_af9015 22892 0
dvb_usb 15960 1 dvb_usb_af9015
dvb_core 83840 1 dvb_usb
i2c_core 23776 7 tda18271,dvb_pll,dvb_usb_af9015,dvb_usb,mt2060,af9013,i2c_i801
usbcore 138160 7 dvb_usb_af9015,dvb_usb,usbhid,hsfosspec,uhci_hcd,ehci_hcd
#
[b][i][color=darkred][size=134]*.* Snow *.*[/size][/color][/i][/b] :wink:

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

DVB help

#20 Post by peebee »

paulski wrote:Here are some helpful links
DVD tv applications (like scan and the script for making the device nodes)
http://dotpups.de/dotpups/Multimedia/Mp ... -1.1.1.pet

Initial scan files for the scan utility
http://linuxtv.org/hg/dvb-apps/file/afd ... can/dvb-t/
Have you tried a Puppy with a later kernel than 4.3.1 - e.g. Lupu or Wary?? They may support the 9015.....

The utilities were given by paulski earlier in this very thread....as a ready made pet

Does this help?
Cheers
peebee

Post Reply