52 replies to this topic

[goldeneye]

@ip_gr

 

I think you are more or less desparate to use USB WiFi and therefore keep pushing your argument as you are probably not willing to leave OpenPli... I concur with Eric that OpenPli can't be forced into applying new driver just because you desperately want to! Their statement is clear! As of 2013 the DMM boxes are no longer actively supported and it is purely out of their good spirit to keep on building for as long as possible.. You should be grateful for that alone! New drivers will not be incorporated (even before the official shutdown) since DMM has left the Open Source platform...

 

So again: Tough luck! The DMM boxes are becoming obsolete by themselves so stop whining and get yourself a brand new STB that is officially supported by OpenPli. You will have full support again, newer kernels and drivers that MIGHT solve your USB WiFi problem... As said: USB WiFI support for any Linux STB is never 100% the same as on PC's or laptops/tablets...

[malakudi]

@goldeneye: It's not a USB wifi, DM8000 has an internal PCI Atheros Wifi.

[Erik Slagter]

Nevertheless, if there ARE new drivers we can use, we are always willing to add them. But the dm8000 has been end-of-live for some time now and I doubt very much if DMM released new drivers in the meantime (if they still exist at all).

[goldeneye]

@Malakudi

You are right! I own a DMM8000 myself and have never ever used the build-in WLAN adapter because of its poor operation.. DM8000 is connected with cable directly to switch..

[malakudi]

Nevertheless, if there ARE new drivers we can use, we are always willing to add them. But the dm8000 has been end-of-live for some time now and I doubt very much if DMM released new drivers in the meantime (if they still exist at all).

 

The DMM images (Merlin3 etc) use a newer patchlevel of the kernel (68 instead of ours 60) and a different dmm patch. I mentioned them above. So the kernel is different. If this the only thing affecting the performance of the internal Atheros wifi is not known, unless we build our kernel with patchlevel 68 and DMM's new patch.

[athoik]

Here are some patch regarding ath9k added after 3.2.60

3.2.71 -> https://git.kernel.o...62fa0d9f64f49b3
3.2.67 -> https://git.kernel.o...944d29118c8d70c
3.2.67 -> https://git.kernel.o...34b0e154841710d

[ip_gr]

@ip_gr

 

I think you are more or less desparate to use USB WiFi and therefore keep pushing your argument as you are probably not willing to leave OpenPli... I concur with Eric that OpenPli can't be forced into applying new driver just because you desperately want to! Their statement is clear! As of 2013 the DMM boxes are no longer actively supported and it is purely out of their good spirit to keep on building for as long as possible.. You should be grateful for that alone! New drivers will not be incorporated (even before the official shutdown) since DMM has left the Open Source platform...

 

So again: Tough luck! The DMM boxes are becoming obsolete by themselves so stop whining and get yourself a brand new STB that is officially supported by OpenPli. You will have full support again, newer kernels and drivers that MIGHT solve your USB WiFi problem... As said: USB WiFI support for any Linux STB is never 100% the same as on PC's or laptops/tablets...

 

And I do not want to force somebody to do something at all! Sorry if somebody got that impression!

But the qutoted statement is a statement I can life with! Until now only malakudi dealt with the problem itself and that the problem occurs ONLY and EXCLUSIVLY in Pli/Pli-based  images. And he analyze it and came to an assumption because of the differences. All the other said that it is not a bug in Pli but the problem is caused by something else except Pli itself. And this is NOT true! That was my problem with all the discussion here.

Edited by ip_gr, 9 December 2015 - 14:13.

[ip_gr]

@malakudi @athoik yparxoun telika kapoio swstoi edw mesa!

Thank you both!

[malakudi]

We can try to build with patchlevel 68 and the newer patch revision from dmm. In linux-dreambox_3.2.bb

 

PATCHREV = "3c7230bc0819495db75407c365f4d1db70008044"

PATCHLEVEL = "68"

 

Now we have:

PATCHREV = "4e0356d04e89df800361b9252f990716f5523c6e"

PATCHLEVEL = "60"

[Erik Slagter]

We "maintain" the BSP for the DMM receiver ourselves. If someone comes up with a patch to "update"/modernise the kernel, I'll apply it.

[athoik]

Hi,

@ip_gr, I've send you a link to download image with newer kernel (patchlevel 68).

Please let us know if it solves your problem in order to send patch from inclusion.

[bsod]

Jumping in late into this thread, and it may not be the exact same issue, but when I first installed OpenPLI I could not get wifi to work either. The VU+ DUO2 just refused to see any wifi network SIDs, even though when in the same room my iPhone/iPAD and AppleTV could.

 

I decided to revert back to OpenATV to see if I could see the networks or not and bingo,  wifi was working fine. Went back to OpenPLI, no wifi.

 

In the end and in desperation I decided to try disabling any form of encryption. Bingo, with no security enabled I could see my WIFI SID and connect.  The AP I connect to is built into my DSL modem/router and was using WPA/PSK. I actually tried this with three disfferent brands of DSL modems, a Draytek Vigor 2900N, Billion 7400VDOX and a ASUS ACU68U, and the same results occurred. I even tried the various other encryption modes the modems supported, all to no avail, it seems the DUO2 can only see the wifi networks when there is no encryption set. 

 

Because I live in a faitly secluded area, running an "open" wifi network does not bother me too much, my nearest neighbour is about 2kms away and I only have wifi active when I need it, I leave it off when not needed.  I haven't gone back to see if this is still an issue with the later builds of OpenPLI so I will give that a shot tonight.

 

Just thought I would add in my 2c worth.

Craig

[bsod]

Just an update, after applying quite a large backlog of updates wifi with WPA/WPA2 with TKIP/AES encryption is now working. Noticed that part of the upgrade included new drivers for the wifi controller on the DUO2, so perhaps this addressed the issue I had.

Craig