[VU+ Ultimo] Dvbt stick

[jareks49]

Hi everybody,

My first post, so I would like to take this oportunity to thank Andy and the whole VIX team for the image.
I have been using it since it was first made - so one can say that I am a bit expienced.
Generally there were no problems to install dib0700 and as102 dvbt sticks on many versions VIX images on my Vu duo and ultimo, althou VIX was always installed in multiboot. ( Yes, I know that no team supports images in multiboot)

For me the easiest way to make dvbt stick working was to follow Angelofsky1980'advice of BH forum (MeoBoot and DVB USB devices).
After putting Angelofsky'file 'usbtunerhelper' into tmp I usually use PUTTY (ipkg install /tmp/usbtunerhelper_1.0+git0+02a71102c0acc752d030d6f1fe2a222f0db8b232-r1_mipsel.ipk), or just remote control to install it.
In this way I succesfully installed dvbt sticks on VIX2.4.96 and101 on my both duo and ultimo.

But after a day or two since VIX.101 was issued it is impossibile for me to get dvbt working.
Tried almost everything (fresh image-10 times, no addons, downloading drivers from VIX server etc.) without succes.

One thing is stange for me: messages read in PUTTY or on tv screan during downloading files from VIX server inform about errors.

Can it be possibile that DVBT files on VIX server are broken? (after maintanence)

Althou I have quite good images in my multiboots (BH, AAF,OpenPLI,VTI) I find the VIX image the best.

After ten days of various tests I have no idea what can I do more- that's the reason for my post.

If anybody would like to help- thanks in advance.

Vuultimo-HH mount(90east-45west plus7sat multifocus) , 1TB HD,4GBstick(meoboot,picon,EPG ),16GBstick(timeshift)
Vuduo- 7sat multfocus,1TB HD, 4GB stick(EPG,picon,meoboot),16GB stick(timeshift)

sorry for my english

jarek

 

[stick50jr]

For me the easiest way to make dvbt stick working was to follow Angelofsky1980'advice of BH forum (MeoBoot and DVB USB devices).
After putting Angelofsky'file 'usbtunerhelper' into tmp I usually use PUTTY (ipkg install /tmp/usbtunerhelper_1.0+git0+02a71102c0acc752d030d6f1fe2a222f0db8b232-r1_mipsel.ipk), or just remote control to install it.
In this way I succesfully installed dvbt sticks on VIX2.4.96 and101 on my both duo and ultimo.

But after a day or two since VIX.101 was issued it is impossibile for me to get dvbt working.
Tried almost everything (fresh image-10 times, no addons, downloading drivers from VIX server etc.) without succes.

Next Release Note after build 101 ---

2.4 Build 112:
enigma2: HelpMenu: fix posible BSOD.
enigma2: fix 3D setting on Vu's.
openwebif: add new ViX setting menu to Menu Panel (still needs work).
picons: update zonka.cc to 2012-05-17
system: merge from PLi 18-05-2012 - this includes Linux 3.3 for ET's.
vix-skins: update transponder info for new PliExtraInfo, fix simple channelselection screen title.

The openPLi merge has gotten rid of the usbtunerhelper and now the detection of dvbt frontends etc is supposed to be handled directly. Perhaps you should try to install the devices without your old methods. I think it is supposed to detect your devices automatically?

cheers

 

[jareks49]

Thanks for quick answer.

I've tried Your advice. Sorry, - no result.

Frankly speaking I tried this earlier with VIX2.4.101 and now with VIX2.4.135 (no succes).


Any way of instalation of dvbt stick should result in appearing files 'usbtunerhelper' in etc/initd and in usr/bin (I suppose)
No matter which way of instalation I choose there are no such files and dvbt stick isn't seen in tuner configuration although it is able to gather
DVBT EPG (strange for me).

Having read Raitsa's opinion (VU DUO talk forum) I decidet to put VIX2.4.135 in my ultimo's flash (I mean without meoboot)- no succes.
The same was done with VIX2.4.101- the same result

To make things more clear I'd like to say that in my ultimo there is VIX2.4.101 in multiboot and there my dvbt sicks (as102&dib0700)work ok.
As I've written in my first post it was very easy before buid 112.
But being lazy I dowloaded some plugins thru TS Panel and I one of them I had to remove -this made my box unable to update VIX.

For the time being my only suspicion is that there can be something wrong with ultimo's dvbt drivers on VIX server (sorry saying this)
Can it be the reason for my problems?

Any help is appreciated, thanks in advance

jarek

 

[stick50jr]

The usbtunerhelper will no longer help you!

This is what I'm talking about:http://openpli.git.sourceforge.net/git/gitweb.cgi?p=openpli/enigma2;a=commit;h=4a319f3f3c122aba0a157f296101d4289ee93a18

authorpieterg <pieterg@users.sourceforge.net>
 Sat, 7 Apr 2012 16:53:22 +0000 (18:53 +0200)
committerpieterg <pieterg@users.sourceforge.net>
 Sat, 7 Apr 2012 16:53:22 +0000 (18:53 +0200)
commit4a319f3f3c122aba0a157f296101d4289ee93a18
treefb9ba9e8cabd5e1bdd7040b975f38be9e9df79b9tree
parent133f10afa473de9548857c43685ac3dc2a587cc3
commit | diff

dvb/frontend: handle usb vtuner mapping internally

When we make the mapping ourselves, we know which usb frontend
is mapped to which virtual vtuner frontend, so we can open
the usb frontend instead of the virtual frontend, and avoid
having to pump control and status messages around.

This implementation replaces the external usbtunerhelper.

lib/dvb/dvb.cpp
diff | blob | history
lib/dvb/dvb.h
diff | blob | history
lib/dvb/frontend.cpp
diff | blob | history
lib/dvb/frontend.h
diff | blob | history

If your device is not automatically detected then maybe start a telnet session:

opkg install firmware-dvb-usb-dib0700-1.20
opkg install kernel-module-dvb-usb-dib0700

or something similar.

Then reboot, do not run usbtunerhelper!

 

[jareks49]

Thanks stick50jr for Your interest and time.

I have followed Your suggestions and done:

1 fresh install build 135
2 with plugin panel downloaded dib0700 drivers
(during instalation , among infos noticed "fatal: module dvb usb_dib0700 not found")
3 reboot
4 usb tuner not visible in infobar, nor in tuner configuration although it is seen in telnet after typing "lsusb" and total commander in
/0:/etc/modutils/


next test:

1 fresh install build 135
2 with PUTTY: opkg install firmware-dvb-usb-dib0700-1.20 and after this: opkg install kernel-module-dvb-usb-dib0700
(telnet displayed lots of infos on downloadings and installings different drivers but ended with "fatal:
module dvb usb_dib0700 not found")
3 reboot
4 usb tuner not visible in infobar, nor in tuner configuration although it is seen in telnet after typing "lsusb",
seen also in /0:/etc/modutils/ (total commander)

Do You or anybody tried to install dvbt stick recently (I mean after VIX 2.4.112)? 'cause seen 2 infos abt problems

Any help apreciated - thanks in advance

jarek

 

[stick50jr]

I must confess that I am away from home this month and will be looking into the issue of usb dvb-t installation on the new Vix for duo (2.4 etc) when I get home. (Currently running on Vix 2.3.204). I usually use an Avermedia A825 TwinStar (dual afatech 9035 chipset) but I also have a Hauppauge Nova TD Stick (dual dib0700). I will let you know how I get on in two weeks time if you haven't solved the problem by then!

Sorry I haven't been able to suggest anything that worked so far. BTW the fatal error doesn't mean anything much... it has always cropped up recently but hasn't prevented the device being recognised after a proper re-boot.

cheers

 

[jareks49]

OK, thanks

Must admit there is a sign of progress: managed to make dvbt usb running on VIX135 in flash
(without multiboot).
That was only possibile by FTP enigma2-plugin-drivers-dvb-usb-dib0700_1.0-r3_mipsel.rar.

Keep trying to install by downloading drivers from VIX server.
Thanks for asistance, will inform abt results

jarek

 

[MarsArtis]

Mates I'm having the very some issue:
the USB DVB-T support is not working as it should.

This time I tried installing an Avermedia A867 (the Sky Italy with blue led)
Stating to some info available on the net the a867 should belong to the af9035 drivers family. But Installing using that driver not worked.
So, back to another post in which stick50jr suggested to install the dib0700 firmware i tried that too, no luck. No usb Tuner detected.

From the sifteam forum I got the a867 driver and I extracted some files from the .ipk installer made by Sifteam for the latest Koala (based on Pli)
so I installed dvb-usb-a867 in /etc/modutils
and dvb-usb-a867.ko in modules/3.1.1./kernel/drivers/media/dvb/dvb-usb

but I noticed that in the latest path there was missing the dvb-usb.ko and I put it there. Rebooted (not simple e2 restart) and the Tuner was there. Choosed the right setting for Italy started a scan and 0 services found. Damn. I tried many other terrestrial.xml but with no luck.

here are some results of telnet:
mesg | grep dvb
dvb_bcm7335: module license 'Proprietary' taints kernel.
dvb-usb: found a 'AVerMedia A867 DVB-T Recevier' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
dvb-usb: AVerMedia A867 DVB-T Recevier successfully initialized and connected.
usbcore: registered new interface driver dvb-usb-a867
usbcore: registered new interface driver dvb_usb_af9035
usbcore: registered new interface driver dvb_usb_dib0700
usbcore: registered new interface driver dvb_usb_dibusb_mc

lsusb
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 006: ID 13fd:0540 Initio Corporation
Bus 001 Device 005: ID 07ca:a867 AVerMedia Technologies, Inc.
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

lsmod
Module Size Used by
tun 16458 0
nfsd 285146 11
zd1211rw 55901 0
8192cu 542837 0
rtl8187 54063 0
rt73usb 24424 0
rt2800usb 13089 0
rt2800lib 44771 1 rt2800usb
rt2500usb 18185 0
rt2x00usb 10921 3 rt73usb,rt2800usb,rt2500usb
rt2x00lib 40442 5 rt73usb,rt2800usb,rt2800lib,rt2500usb,rt2x00usb
r8712u 169530 0
pl2303 12486 0
keyspan 32756 0
ipv6 348670 10
ftdi_sio 30425 0
exportfs 3994 1 nfsd
dvb_usb_dibusb_mc 3254 0
dvb_usb_dibusb_common 4822 1 dvb_usb_dibusb_mc
dvb_pll 8404 1 dvb_usb_dibusb_common
dvb_usb_dib0700 69808 0
dib7000p 27910 1 dvb_usb_dib0700
dib0090 22622 1 dvb_usb_dib0700
dib7000m 14940 1 dvb_usb_dib0700
dib0070 8368 1 dvb_usb_dib0700
dib8000 30230 1 dvb_usb_dib0700
dib9000 29991 1 dvb_usb_dib0700
mt2266 4051 1 dvb_usb_dib0700
tuner_xc2028 19906 1 dvb_usb_dib0700
dib3000mc 11212 2 dvb_usb_dibusb_common,dvb_usb_dib0700
xc5000 12405 1 dvb_usb_dib0700
s5h1411 8457 1 dvb_usb_dib0700
mt2060 4211 2 dvb_usb_dibusb_common,dvb_usb_dib0700
lgdt3305 14600 1 dvb_usb_dib0700
xc4000 19738 1 dvb_usb_dib0700
dibx000_common 6837 6 dvb_usb_dib0700,dib7000p,dib7000m,dib8000,dib9000, dib3000mc
dvb_usb_af9035 11403 0
mxl5007t 7531 2 dvb_usb_dib0700,dvb_usb_af9035
af9033 15600 1 dvb_usb_af9035
tda18218 3573 1 dvb_usb_af9035
tua9001 2263 1 dvb_usb_af9035
dvb_usb_a867 211662 1
carl9170 83694 0
belkin_sa 6809 0
usbserial 30919 4 pl2303,keyspan,ftdi_sio,belkin_sa
ath9k_htc 63975 0
mac80211 211445 7 zd1211rw,rtl8187,rt2800lib,rt2x00usb,rt2x00lib,car l9170,ath9k_htc
ath9k_common 1442 1 ath9k_htc
ath9k_hw 310668 2 ath9k_htc,ath9k_common
ath 16979 3 carl9170,ath9k_htc,ath9k_hw
appletalk 28439 0
psnap 1836 1 appletalk
llc 3665 1 psnap
brcmfb 1127 2
dvb_bcm7335 4932784 19 brcmfb
procmk 1397 1 dvb_bcm7335

Any clue?

 

[MarsArtis]

a little correction for the previous post.
the correct path for the dvb-usb-a867.ko
is:
/lib/modules/3.1.1./kernel/drivers/media/dvb/dvb-usb

Now I want to add some other infos:
checking the content of /lib/firmware the dvb related firmware files are:
dvb-usb-af9035-01.fw
dvb-usb-dib0700-1.20.fw
dvb-usb-dibusb-5.0.0.11.fw
dvb-usb-dibusb-6.0.0.8.fw
dvb-usb-dibusb-an2235-01.fw
all with 644 permissions

so apparently something strictly related do a867 is not present (this encouraging my thoughts that a867 is an af9035-01.fw based tuner).
on the openpli forum there's this topic related to a867, but I'm not a coder and I'm not able to follow them as I wished.

 

[MarsArtis]

it seems that openpli has a driver for kernel 3.1.1
this should be:
kernel-module-dvb-usb-a867_3.1.1-r16.7_vuduo.ipk
but I really don't know how to grab it from their feed. Any help?

 

[MarsArtis]

Ok mates, I managed to grab a867 kernel module both for DUO and ULTIMO.
Here are the links:
kernel-module-dvb-usb-a867_3.1.1-r4.16_vuduo.ipk

kernel-module-dvb-usb-a867_3.1.1-r4.16_vuultimo.ipk

I've not tested them since I'm at work.
The only thing I noticed is that theese ipk DO NOT embed any .FW.
So, maybe we have to first install the af9035 driver (a867 seems to belong to that family) and than the a867 kernel module. But we may need to tweek the af9035 to point to a867 modules, I syppose. Am i wrong?

 

[MarsArtis]

EDIT:
the two above links are from SIFTEAM distribution for KOALA image. So the control file inside the ipk points to path not similar to our VIX.

for what I've seen here are the contents of that ipk:
control.tar.gz

which contains:
control which content is:

Package: kernel-module-dvb-usb-a867
Version: 3.1.1-r4.16
Description: dvb-usb-a867 kernel module; AVerMedia A867
Section: base
Priority: optional
Maintainer: OpenEmbedded Team <openembedded-devel@lists.openembedded.org>
License: GPL
Architecture: vuduo
OE: linux-vuplus
Homepage: unknown
Build: master/f0f4b12
Depends: update-modules, kernel-3.1.1, kernel-module-dvb-usb
Source: file:///sifteam/openembedded/recipes/linux/linux-vuplus_3.1.1.bb http://archive.vuplus.com/download/kernel/linux-3.1.1_r2.tar.bz2 file://vuduo_defconfig file://dvb-usb-af9035.patch file://dvb-usb-it9135.patch file://tda18218-7mhz-lopass.patch file://dvb-usb-a867.patch file://PCTV-DVB-S2-stick-460e.patch file://cxd2820r-enable-LNA-for-DVB-T.patch file://cxd2820r-changed-condition-to-break-out-from-wait-lock-loop.patch file://dvb-usb-smsdvb_fix_frontend.patch file://dvb-usb-rtl2832.patch file://cxd2820r-output-full-range-SNR.patch file://xc3028-fix-center-frequency.patch file://cinergy_s2_usb_r2.patch file://af9015-output-full-range-SNR.patch file://fix_cpu_proc_vuduo.patch file://linux_3.1.1_vuduo.patch file://linux-sata_brcm.patch​

postinst
#!/bin/sh

if [ -n "$D" ]; then
mipsel-oe-linux-depmod -A -b $D -F /sifteam/build-vuduo/tmp/sysroots/vuduo-oe-linux/kernel/System.map-3.1.1 3.1.1
else
depmod -a 3.1.1
update-modules || true
fi

if [ x"$D" = "x" ]; then
modprobe dvb-usb-a867 || true
fi​

postrm

#!/bin/sh
update-modules || true​

data.tar.gz with two main folders pointing to the following paths:

/etc/modutils/dvb-usb-a867​

​

/lib/modules/3.1.1./kernel/drivers/media/dvb/dvb-usb/dvb-usb-a867.ko
​

debian.binary it only says 2.0

for what I understand (correct me please) it seems that the driver relay on many different other files and patches for tha af9035, the it9135, the PCTV and so on.

So, what could be a possible way to have he a867 installed and working.

I've not been able to get the two ipk installer from OPENpli feed so I realy don't know if the openpli ones point to different paths and on different dependencies, modules.

 

[stick50jr]

Ok mates, I managed to grab a867 kernel module both for DUO and ULTIMO.
Here are the links:
kernel-module-dvb-usb-a867_3.1.1-r4.16_vuduo.ipk

kernel-module-dvb-usb-a867_3.1.1-r4.16_vuultimo.ipk

I've not tested them since I'm at work.
The only thing I noticed is that theese ipk DO NOT embed any .FW.
So, maybe we have to first install the af9035 driver (a867 seems to belong to that family) and than the a867 kernel module. But we may need to tweek the af9035 to point to a867 modules, I syppose. Am i wrong?

As advised in your topic link, there is no firmware needed for the a867 because the equivalent code is within the driver.

I had a look and see that there is a driver in the Vix feeds which can be installed from a telnet session:

opkg install kernel-module-dvb-usb-a867

This is a later release 3.1.1-r16.8 than the one you mentioned earlier and the ones above.

I don't have an a867 but maybe you should try installing this and then do a re-boot.

This will install the following files only:

/etc/modutils/dvb-usb-a867
/lib/modules/3.1.1./kernel/drivers/media/dvb/dvb-usb/dvb-usb-a867.ko

I don't think that it relies on all those other files. The modutils entry will guide the system in discovering the driver file when you do the re-boot (with any luck!).

I have an a825 which is supported by the af9035 driver. With this latest version of Vix (ie 2.4), it stops working after a gui restart, so you may also have to do a full re-boot everytime the gui is restarted to get the thing working again. Apparently this restart problem is for all usb-dvb devices under Vix 2.4 and also openPLi.

 

[MarsArtis]

Hi stick,
thx for replying.
I'm wondering why the driver is not made available in the Plugin GUI.
Anyhow, I'll try your instructions, to be honest last week I did try to issue a opkg install command but that kernel module was not found.
Maybe they have put it recently.
Before installin the module I'm issueing a opkg update && opkg upgrade.
Let's see.

P.S.
how did you check the availability of the module in the feed?

 

[stick50jr]

I just used a867 instead of af9035 and the command did something

opkg install kernel-module-dvb-usb-a867

The fatal error can be ignored, its an openPLi/Vix feature!

... then I issued additional commands:

opkg files kernel-module-dvb-usb-a867
opkg depends kernel-module-dvb-usb-a867

but as I don't have the device, I didn't do anything else.

They haven't got around to creating a meta package that can be installed from the plugin gui... I guess there are plenty of devices that haven't been supported to this extent yet. Even the af9035 was not supported via the plugin gui in Vix 2.3. They have added a fair few in Vix 2.4 but not the a867. If you can confirm that the a867 is working okay, then Andyblac will probably add it in some time.

I suspect that usb-dvb devices have had a low priority in the Vu images, because they have all been unstable due to problems attributed to the closed Vu kernel drivers by the open developers. However, the elimination of usbtunerhelper has improved stability IMHO, just a bit inconvenient having to reboot whenever there has been a gui restart.

 

[MarsArtis]

mmm something went wrong:
at first after update and upgrde (but not rebooted) I issued_
root@vuduo:~# opkg install kernel-module-dvb-usb-a867
Installing kernel-module-dvb-usb-a867 (3.1.1-r16.8) to root...
Downloading http://enigma2.world-of-satellite.c...nel-module-dvb-usb-a867_3.1.1-r16.8_vuduo.ipk.
Configuring kernel-module-dvb-usb-a867.
FATAL: Error inserting dvb_usb_a867 (/lib/modules/3.1.1/kernel/drivers/media/dvb/dvb-usb/dvb-usb-a867.ko): Invalid module format

so tried to manually remove the previously manually installed via ftp
/etc/modutils/dvb-usb-a867
/lib/modules/3.1.1./kernel/drivers/media/dvb/dvb-usb/dvb-usb-a867.ko

resend the opkg install kernel-module-dvb-usb-a867
and got:
package kernel-module-dvb-usb-a867 (3.1.1-r16.8) installed in root is up to date.

????

Tried to reboot the box and now when issuing
mesg | grep dvb I don't get anything..... no line:
root@vuduo:~# mesg | grep dvb
root@vuduo:~#

 

[stick50jr]

opkg remove kernel-module-dvb-usb-a867

opkg install kernel-module-dvb-usb-a867

reboot

 

[MarsArtis]

that was exactly what I was doing.
And the DUO hanged on install process.
Since I'm at work I phoned my brother and made him switch off the receiver.
Let's see what happens

 

[MarsArtis]

Ok somethig strange happens.
I did the opkg remove and it went ok
then issued again the opkg install and It returned the following:
oot@vuduo:~# opkg install kernel-module-dvb-usb-a867
Installing kernel-module-dvb-usb-a867 (3.1.1-r16.8) to root...
Downloading http://enigma2.world-of-satellite.c...nel-module-dvb-usb-a867_3.1.1-r16.8_vuduo.ipk.
Configuring kernel-module-dvb-usb-a867.
FATAL: Error inserting dvb_usb_a867 (/lib/modules/3.1.1/kernel/drivers/media/dvb/dvb-usb/dvb-usb-a867.ko): Invalid module format
root@vuduo:~#

why? what doe it mean?
anyway checkhing the destination folders I found that both
/lib/modules/3.1.1/kernel/drivers/media/dvb/dvb-usb/dvb-usb-a867.ko)
and
/etc/modutils/dvb-usb-a867
were installed

root@vuduo:~# opkg files kernel-module-dvb-usb-a867
Package kernel-module-dvb-usb-a867 (3.1.1-r16.8) is installed on root and has the following files:
/etc/modutils/dvb-usb-a867
/lib/modules/3.1.1/kernel/drivers/media/dvb/dvb-usb/dvb-usb-a867.ko
root@vuduo:~# opkg depends kernel-module-dvb-usb-a867
kernel-module-dvb-usb-a867 depends on:

update-modules
kernel-3.1.1​

 

[MarsArtis]

mmm something is not going as it should:
mesg | grep dvb
dvb_bcm7335: module license 'Proprietary' taints kernel.
dvb_usb: version magic '2.6.18-7.4-dm500hd SMP mod_unload MIPS32_R1 32BIT gcc-4.4' should be '3.1.1 SMP mod_unload MIPS32_R1 32BIT '
dvb_usb: version magic '2.6.18-7.4-dm500hd SMP mod_unload MIPS32_R1 32BIT gcc-4.4' should be '3.1.1 SMP mod_unload MIPS32_R1 32BIT '
dvb_usb: version magic '2.6.18-7.4-dm500hd SMP mod_unload MIPS32_R1 32BIT gcc-4.4' should be '3.1.1 SMP mod_unload MIPS32_R1 32BIT '
dvb_usb: version magic '2.6.18-7.4-dm500hd SMP mod_unload MIPS32_R1 32BIT gcc-4.4' should be '3.1.1 SMP mod_unload MIPS32_R1 32BIT '

lsusb
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 07ca:a867 AVerMedia Technologies, Inc.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 058f:6366 Alcor Micro Corp.
Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 002: ID 13b1:0020 Linksys WUSB54GC 802.11g Adapter [ralink rt73]
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

lsmod
Module Size Used by
tun 16458 2
zd1211rw 55901 0
8192cu 542837 0
rtl8187 54063 0
rt73usb 24424 0
rt2800usb 13089 0
rt2800lib 44771 1 rt2800usb
rt2500usb 18185 0
rt2x00usb 10921 3 rt73usb,rt2800usb,rt2500usb
rt2x00lib 40442 5 rt73usb,rt2800usb,rt2800lib,rt2500usb,rt2x00usb
r8712u 169530 0
pl2303 12486 0
keyspan 32756 0
ipv6 348670 10
ftdi_sio 30425 0
dib8000 30230 0
dib9000 29991 0
mt2266 4051 0
tuner_xc2028 19906 0
dib3000mc 11212 0
mxl5007t 7531 0
xc5000 12405 0
s5h1411 8457 0
mt2060 4211 0
lgdt3305 14600 0
xc4000 19738 0
dibx000_common 6837 3 dib8000,dib9000,dib3000mc
carl9170 83694 0
belkin_sa 6809 0
usbserial 30919 4 pl2303,keyspan,ftdi_sio,belkin_sa
ath9k_htc 63975 0
mac80211 211445 7 zd1211rw,rtl8187,rt2800lib,rt2x00usb,rt2x00lib,carl9170,ath9k_htc
ath9k_common 1442 1 ath9k_htc
ath9k_hw 310668 2 ath9k_htc,ath9k_common
ath 16979 3 carl9170,ath9k_htc,ath9k_hw
brcmfb 1127 2
dvb_bcm7335 4932784 32 brcmfb
procmk 1397 1 dvb_bcm7335

I'm wondering if I did right when issued:
opkg update && opkg upgrade