Can you please take a look on this topic . There is as you know mainline kernel support for Khadas VIM in version 4.12. Today I tested (instruction from Martin Blumenstingl) WiFi and as soon as i try to connect to box there is call trace.
The Heiner Kallweit wrote that actually this could be a problem with “android” firmware which i use. Do there exist any other firmware then one i linked in first post in that Amlogic Mailing list?
Easy definition of call trace is the kernel panic/ kernel crash which prints stack/call trace message which could be seen with dmesg or if connected over serial console directly in that session. So actually forum post should be kernel panic and the panic/oops message says something like [stack: ; Call trace; etc…]
And here on Mainline Kernel there is kernel panic when enabling WiFi on Khadas VIM Pro. This was also reported by Martin Blumenstingl replay in Amlogic Mailinglist .
@Gouwa that commit which you point does it enable WiFI on Pro version with AP6255, because only reference I found is for non Pro version with AP6212 . Can you confirm that WiFi is relay working with the Pro version?
probably correct nvram for Pro version would be: /usr/lib/firmware/brcm/brcmfmac43455-sdio.txt and firmware /lib/firmware/brcm/fw_bcm43455c0_ag.bin from .
Or is the AP6255 firmware/nvram somewhere else defined?
They are for ArchLinuxArm and I will post them in that topic (actually I’ll update page on github, but post replay that page is updated)
How ever i also tried it on Ubuntu Server image you provide but i cannot login to device over SSH, ping out works through.
Do you have instruction how to setup WiFi on your Ubuntu Server image released yesterday?
This link  have some Notes with instruction I used:
Did you also tried WiFI without having Ethernet cable connected. As you can see in that Note from me, even after I add new default route I can’t ssh into device. Nor even ping gateway. Ping 184.108.40.206 work however apt-get update not, but resolve works. Quite weird stuff.
PS: To download over 380MB for network-manager on Server and then use it’s cli is not an option here, sure for tests but otherwise an no go.
Hello khadas team,
I want to understand why I have this problem :
my wifi access point is using channel 13, which is fully legal where I live (FR).
my khadas vim pro (using ubuntu xenial + kernel 412rc6 patched by numbqq) is not able to see my network but can see others using channel <=11