[S905X] Unknown WLAN chip

**mmpp** · June 13, 2017 at 10:03 AM

Module loads, but wlan0 interface cannot be brought up.

dmesg : GVMN

lsmod:

Code

Module                  Size  Used by
8021q                  18879  0
8189es               1149103  0
cfg80211              365310  1 8189es
mceusb                 10291  0
rc_core                22607  1 mceusb
wifi_dummy               806  0
mali                  198408  5
amlvideodri            11602  0
videobuf_res            5402  1 amlvideodri
videobuf_core          16491  2 amlvideodri,videobuf_res
videodev              148509  1 amlvideodri
media                  21539  1 videodev
fbcon                  37495  0
bitblit                 4484  1 fbcon
softcursor              1184  1 bitblit
font                    7287  1 fbcon

Display More

Some more testing:

Code

akaso:~ # ifconfig
eth0      Link encap:Ethernet  HWaddr D0:76:58:07:32:D8
          inet addr:192.168.1.46  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:271 errors:0 dropped:0 overruns:0 frame:0
          TX packets:254 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:45164 (44.1 KiB)  TX bytes:92687 (90.5 KiB)
          Interrupt:40

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:4096  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

akaso:~ # ifconfig wlan0
wlan0     Link encap:Ethernet  HWaddr 00:E0:4C:42:54:EF
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

akaso:~ # ifconfig wlan0 up
ifconfig: ioctl 0x8914 failed: Operation not permitted

Display More

Just tell me what you want me to test. Linux command line knowledge is present, but maybe a bit dated

**kszaq** · June 13, 2017 at 10:45 AM

Thank you for checking. I don't think there's anything more to test.

jeg535s · June 30, 2017 at 2:03 PM

I am clueless when it comes to this stuff. Nevertheless I insist on trying to help.

I was at [ROM] Beelink Mini MX3 II / M8S II TVStock Nexus ROM (Android TV) *

and I see a request for 9082C drivers, to which Magendanz seems to be in possesion of.

Here is the link: Qualcomm QCA9377 chipset

^*I^{hope it's OK to post a screenshot from another blog.}

**kszaq** · June 30, 2017 at 2:38 PM

Adding a pre-built module to Android ROM is easier because "all" you do is modify existing ROM where the module already works. I tried adding the pre-built kernel module to LE builds but it crashes the system. Without driver source code we can do nothing.

jeg535s · July 1, 2017 at 12:15 AM

Quote from kszaq

Adding a pre-built module to Android ROM is easier because "all" you do is modify existing ROM where the module already works. I tried adding the pre-built kernel module to LE builds but it crashes the system. Without driver source code we can do nothing.

Oh Okay....I understand.

Tyler Durden · July 16, 2017 at 3:30 PM

Quote from kszaq

Adding a pre-built module to Android ROM is easier because "all" you do is modify existing ROM where the module already works. I tried adding the pre-built kernel module to LE builds but it crashes the system. Without driver source code we can do nothing.

Does this help?

Mini M8S Pro T95N T95X Android 6.0 S905X WIFI SCI 9082C - FreakTab.com

Tyler Durden · July 16, 2017 at 3:42 PM

Or this. Apparently this is the 9082C drivers.

MEGA

**kszaq** · July 16, 2017 at 5:26 PM

Tyler Durden This is not the driver source code.

Tyler Durden · July 16, 2017 at 11:24 PM

Sorry. Where would I find that?

Tyler Durden · July 16, 2017 at 11:25 PM

Product Finder Results | Wi-Fi Alliance

**kszaq** · July 16, 2017 at 11:34 PM

If I could answer that question, this thread would have been solved long time ago.

**chewitt** · July 17, 2017 at 7:33 AM Official Post

We know who creates the chip. They don't respond to emails in English or Chinese. Neither Amlogic or Rockchip (where we have direct contacts) have any record of an authorised hardware manufacturer using the chip (else they would require accreditation and would have driver sources in their code archives). I'm sure sources will leak eventually, but until that happens we are out of luck.

KissIt · July 19, 2017 at 1:04 AM

Have you tried writing Xiaomi or someone else in China who understands Eastcoast English?

Tyler Durden · July 19, 2017 at 2:23 PM

Quote from chewitt

We know who creates the chip. They don't respond to emails in English or Chinese. Neither Amlogic or Rockchip (where we have direct contacts) have any record of an authorised hardware manufacturer using the chip (else they would require accreditation and would have driver sources in their code archives). I'm sure sources will leak eventually, but until that happens we are out of luck.

Who creates the chip?

**chewitt** · July 20, 2017 at 11:55 AM Official Post

Suzhou SmartChip Semiconductor Co.,Ltd FCC ID Applications (2AKCE) - the phone diverts to voicemail and both voice/email messages left (in Mandarin by a native speaker) are not answered. Via third-parties we've been offered the driver in binary form for any Android kernel version we care to ask for, but nobody has sources, which is what we need. I can assure people we've been quite creative on trying to reach them - but so far no results.

**kszaq** · September 6, 2017 at 9:27 AM

Now some bad news: I e-mailed VideoStrong - as the chip is used in their Mecool M8S Pro+ - requesting the driver and they informed me that 9082 chip supplier doesn't give them driver source code and refuses to share pre-built driver object file (9082xs.o) that could help us building the driver for LibreELEC.

Now that I have one device with that chip I tried using the pre-built driver but it crashes on NULL pointer dereference - something that can't be fixed without source code.

frequenzy · September 6, 2017 at 9:35 AM

Quote from kszaq

Now some bad news: I e-mailed VideoStrong - as the chip is used in their Mecool M8S Pro+ - requesting the driver and they informed me that 9082 chip supplier doesn't give them driver source code and refuses to share pre-built driver object file (9082xs.o) that could help us building the driver for LibreELEC.

Now that I have one device with that chip I tried using the pre-built driver but it crashes on NULL pointer dereference - something that can't be fixed without source code.

**wrxtasy** · September 6, 2017 at 12:28 PM

Plug a EDIMAX EW-7811Un - RTL8188CUS Chipset - USB WiFi dongle in and it will work out of the box. That 2.4GHz N Band one is $8

[S905X] Unknown WLAN chip

Similar Threads

Create remote.conf from scratch

S905X WLAN chip