SliTaz Forum
You are not logged in.
Pages: 1
Would like to be able to use my dvb dongle in Slitaz. The kernel isn't recognising it or laoding any drivers for it. Under Xubuntu it sows as follows:
lsusb
Bus 001 Device 002: ID 1b80:e395 Afatech
dmesg
[ 14.812122] dvb-usb: found a 'KWorld USB DVB-T TV Stick II (VS-DVB-T 395U)' in warm state.
[ 14.812323] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 14.876096] dvb-usb: schedule remote query interval to 500 msecs.
[ 14.876109] dvb-usb: KWorld USB DVB-T TV Stick II (VS-DVB-T 395U) successfully initialized and connected.
[ 14.890698] usbcore: registered new interface driver dvb_usb_af9015
[ 14.875126] Quantek QT1010 successfully identified.
lsmod
dvb_usb_af9015 22397 0
dvb_usb 23826 1 dvb_usb_af9015
dvb_core 94814 1 dvb_usb
rc_core 21263 10 ir_lirc_codec,ir_mce_kbd_decoder,ir_sony_decoder,ir_jvc_decoder,ir_rc6_decoder,ir_rc5_decoder,ir_nec_decoder,dvb_usb_af9015,dvb_usb
Offline
OK made progress. Found the v4l-dvb package in the stable 4.0 repository: v4l-dvb-development_2.6.37.tazpkg, installed rebooted and dvb dongle found and modules loaded.
Problem now seems to be with usage. Mplayer and Mplayer-SVN seem to have so many options disabled that the "mplayer dvb://" command is killed. This also prevents any more activity in the terminal window (?).
Looks like I'll have to compile mplayer from source ?
Offline
No-one using dvb on their Slitaz ?
Offline
This is where I have got to so far, following guidance from the Linuxtv wiki:
1. Firmware copied over from Xubuntu
2. Modules loaded for dvb-t dongle
3. dvb-apps installed from source
4. Trying to run anything (e.g. scan) against the dvb-t device results in a "Killed" output
5. Although v4l-dvb is installed and apparently working from slitaz cooking, attempted installing v4l-dvb from source, but this fails as Slitaz doesn't have "lsdiff". If it does, where is it?
6. Double checking against xubuntu install everything seems the same, but just doesn't want to work.
7. Lots of errors pop up in dmesg after trying to run a dvb app
Here is dmesg output on bootup:
WARNING: You're using an experimental version of the DVB stack. As the driver
is backported to an older kernel, it doesn't offer enough quality for
its usage in production.
Use it with care.
dvb-usb: found a 'KWorld USB DVB-T TV Stick II (VS-DVB-T 395U)' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (KWorld USB DVB-T TV Stick II (VS-DVB-T 395U))
af9013: firmware version:4.95.0
DVB: registering adapter 0 frontend 0 (Afatech AF9013 DVB-T)...
Quantek QT1010 successfully identified.
input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:04.1/usb1/1-1/input/input6
dvb-usb: schedule remote query interval to 150 msecs.
dvb-usb: KWorld USB DVB-T TV Stick II (VS-DVB-T 395U) successfully initialized and connected.
usbcore: registered new interface driver dvb_usb_af9015
and here it is after running mplayer dvb://
BUG: unable to handle kernel paging request at 80a86fad
IP: [<f9a566c3>] dvb_generic_ioctl+0x5/0x32 [dvb_core]
*pde = 00000000
Oops: 0000 [#1] SMP
last sysfs file: /sys/devices/virtual/bdi/0:20/uevent
Modules linked in: qt1010 af9013 dvb_usb_af9015 dvb_usb dvb_core button nvidia(P) agpgart i2c_core snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore snd_page_alloc
Pid: 2043, comm: mplayer Tainted: P 2.6.37-slitaz #2 EB1012/EB1012
EIP: 0060:[<f9a566c3>] EFLAGS: 00010286 CPU: 0
EIP is at dvb_generic_ioctl+0x5/0x32 [dvb_core]
EAX: f3e523c0 EBX: ffffffea ECX: bf8b7278 EDX: 80a86f3d
ESI: f3e523c0 EDI: f9a566be EBP: f40a9f24 ESP: f40a9f1c
DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
Process mplayer (pid: 2043, ti=f40a8000 task=f60ab860 task.ti=f40a8000)
Stack:
ffffffea f3e523c0 f40a9f90 c108c045 f40a9f34 c103f498 f40a9fac c101d50e
08177d88 00000000 f610a774 f610a740 00000008 f60ab860 08177d88 00000004
00000020 f3e523c0 00000282 00000020 f3e523c0 00000003 f40a9f94 c1080a54
Call Trace:
[<c108c045>] ? do_vfs_ioctl+0x4ad/0x4e8
[<c103f498>] ? up_read+0x8/0xa
[<c101d50e>] ? do_page_fault+0x30c/0x336
[<c1080a54>] ? do_sys_open+0xc4/0xce
[<c108c0ae>] ? sys_ioctl+0x2e/0x48
[<c137a079>] ? syscall_call+0x7/0xb
Code: 37 73 c7 85 c0 75 09 eb 0c bb ea ff ff ff eb 05 bb f2 ff ff ff 89 f8 e8 99 80 62 c7 8d 65 f4 89 d8 5b 5e 5f 5d c3 55 89 e5 56 53 <8b> 72 70 bb ed ff ff ff 85 f6 74 16 8b 76 34 b3 ea 85 f6 74 0d
EIP: [<f9a566c3>] dvb_generic_ioctl+0x5/0x32 [dvb_core] SS:ESP 0068:f40a9f1c
CR2: 0000000080a86fad
---[ end trace 4401045504d808e5 ]---
can anyone point me in the right direction?
Offline
About the Warning, and from the Linux video input infrastructure (V4L/DVB) development discussion and bug report mailing list:
Since the migration to -git, less developers are using the -hg tree. Also, some
changes are happening upstream that would require much more than just compiling
the tree with an older version, to be sure that the backport won't break anything,
like the removal of BKL.
As normal users might not be aware of those issues, and bug reports may be sent
based on a backported tree, add some messages to warn about the usage of a
backported experimental (unsupported) tree.
So the driver may be buggy, in unstable condition or working well, we don't know but It seems to load pretty well.
Maybe some udev rules are missing (I'm lazy, I didn't check) so /dev/dvb is not fully populated?
You should see a folder hierarchy under /dev/dvb which looks like this:
[c]# ls /dev/dvb
adapter0
# ls /dev/dvb/adapter0
demux0 dvr0 frontend0 net0
#[/c]
--dom
Offline
Thanks for responding dom
I have that folder, and all the virtual devices are there
Offline
Pages: 1
[ Generated in 0.017 seconds, 7 queries executed - Memory usage: 1.54 MiB (Peak: 1.77 MiB) ]