Mediatek MT7986 / Banana Pi BPI-R3 Wifi not working #702
Comments
|
maybe you miss eeprom-data? daniel added it like me in the devicetree and with the firmware-files from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/mediatek probe works for me (creates 2 wifi-interfaces seen by "ip a"). |
|
Hello Frank, |
|
I have just tried with https://downloads.openwrt.org/snapshots/targets/mediatek/filogic/openwrt-mediatek-filogic-bananapi_bpi-r3-sdcard.img.gz, I didn't do anything else. It's worth mentioning that I'm running directly from the SD card, and it's a v1.1 board. I guess the eeprom-data you are talking about is https://github.com/openwrt/openwrt/blob/master/target/linux/mediatek/dts/mt7986a-bananapi-bpi-r3.dts#L424, @frank-w? The thing is that in https://openwrt.org/toh/sinovoip/bananapi_bpi-r3 there is a link to https://asciinema.org/a/518024 where it can be seen working just fine. And in openwrt/openwrt@a96382c it says WiFi was working. The eeprom-data in the HEAD of openwrt is still the same one that was added in openwrt/openwrt@a96382c, it has never changed. |
|
Yes it's the portion i mean for eeprom-data. What kind of powersupply do you have (12v xA)? Are the sfp slots equipped (one/both) any other power consumers like m2 or mpcie card? I guess it can be a current problem... |
|
I was using a 12v x 2A power supply, it came with the board. But just to test, I have just tried with a 12v x 3.33A one, same problem. |
|
Now its a bit clearer. Just to say it's not a power supply issue. Have 2 power supplies from sinovoip and tested both, no difference. I just tested the board on a laboratory power supply with 12v@10a with no difference so there is no issue with that. Also not with the sd card. What drives me crazy is the fact that with first board the wifi worked with the image from sinovoip and got broken as i installed the snapshot. But on 2. board it never worked. |
|
here a complete log booting from spi-nand with todays snapshot r20784-ec8fb542ec. perhaps we miss something. Edit I put the extracted device tree with the eeprom-data at the end of the log. |
|
Is this supposed to be the same as https://github.com/openwrt/openwrt/blob/ec8fb542ec3e4f584444a97de5ac05dbc2a9cde5/target/linux/mediatek/dts/mt7986a-bananapi-bpi-r3.dts#L424 ? Edit: never mind, endianess... |
|
it is the same as https://github.com/openwrt/openwrt/blob/master/target/linux/mediatek/dts/mt7986a-bananapi-bpi-r3.dts#L424 |
|
From Sinovoip mac80211 image |
|
Hello ppl, I have to tell you now, i noticed it 5min ago. I tested a bit beside the work and suddenly the wireless tab in the config appeared. |
|
The log from menu: |
|
Power cycle and away. Then removed the antennas and reattached like yesterday nothing. After i plugged out debug console and did a power cycle it is back. |
|
you removed debug-console and then wifi works?? have you connected gnd/rx/tx to the board? |
|
Hello frank, just tested it again and yeah i plug out debug console, make a power cycle and there it is. Wifi working. there is a problem with console thats why with wifi on the console went crazy. |
|
i guess your adapter brings gnd to your board and shortens anything needed for wifi to be precise all 3 have to be connected, but something there is strange...maybe try another adapter? is your host-system and the r3 connected to same power-source? afaik it is UART0 yes |
|
sure all 3, you need an reference... ;) Here is another log, its the same position debug console stops working... and then wifi starts.... edit Oh sry should have checked the other log first. its not the same position. So at this point it's no longer a software problem and matters sinovoip. Good we found the problem. Should i close the thread or do you let it open for updates from sinovoip? |
|
I can reproduce what @eckinga says with both these adapters With both the mt76 driver and the proprietary Mediatek driver. So... yeah, not a mt76 issue. |
|
i do not have this issue with cp210x no stop of serial output and wifi is recognized using linux 6.0.0-rc6...so there is something strange with your boards |
|
@frank-w is your board a v1.1? |
no, v1.0..so maybe something has changed here between those versions |
|
Would be nice to see full schematic and pcb layout for both v1.0 and v1.1 to see what was changed. |
|
Have you reported it to sinovoip? I see no (public) Thread in forum. Changes i know for v1.1 are adding hole for 2230 nvme, moving bootswitches together, add common usb2 and a sata power connector. Reset bug schold be still there in 1.1 (when card in m2 slot) |
|
yes i reported to them, due national day in china i guess respond will take a while... |
|
I tried the snapshot from today (flashed on an SD card) and it seems to work well, just a note when I had the serial connected it wasn't working, not sure if it has anything to do with it. |
|
Bpi responds here: https://forum.banana-pi.org/t/bpi-r3-hw-issues/14027/2 I wonder why it affects v1.1 with cp21x2 and not v1.0. I have no profilic adapter as they are reported as buggy on other boards (e.g. bpi-r2). Can only test with ch340,but this seems not affected |
Bpi says "When powered on, if the uart tx is pulled high, it will cause this". I see you did a "modprobe mt7915e", way after powering it on. It doesn't happen to you, with the v1.0, even during boot? |
|
simon says there are no differences regarding this between v1.0 and v1.1 and only PL2303 is affected, shematics look same too added mt7915e module to /etc/modules-load.d/wifi.conf and see no issues with my cp210x. no broken serial output and wifi is initialized without problem (using my 6.1-rc tree, but basicly same patches as daniel used for openwrt) ch340,cp2102,FT4232 reported to be not affected based on simons answer but it is still unclear to me why it affects wifi...in any case it does not affect wifi (uart tx pulled up to 3v3/even 5v or down to 0v) |
|
I can confirm as well. |
|
FYI from a quick look at the schematic I think that the problem is that UART0_TXD is also a strap pin. When attaching a serial adapter it will have its own pull (up) resistor, countering the built-in pull-down strap (RB8). This causes the second "A-Die" which I think are the RF frontend ICs to switch its crystal mode selection from crystal mode to "buffer mode". Most likely this causes the wifi firmware to fail to power up the second frontend. The good thing is that this is not a fatal problem, it can be fixed by either decreasing RB6 to make for a stronger pull-down (probably something like 820Ohms -> ~4mA) or getting a serial adapter with a much higher pull-up (like 47kOhms). This stops the serial adapter's pull-up from overpowering the strapping resistor. |
|
I understand the UART problem I am reading about here but for my case I am not using a UART device. I boot the device with a clean openwrt build and wifi is not present. When I boot the device with the sdcard image found within the bpi-r3 forums I see wlan devices. Is there something within the build configuration I am missing to activate the wireless interfaces? Edit: I solved this by looking at a few boot log differences. It appears as though the default BPI R3 config file does not have the kernel modules for the wifi chip enabled. I believe what I marked as yes were the 7915 and 7915e kmods within the config. |
did you checked that it not been disabled in |
|
have now same error on new system (debian bullseye) with newest firmware-files and kernel 6.1.0 also if not connected uart (cp2102)...maybe it is firmware-issue? edit: used card i used on my v1.0-board, and it is not working too...so it looks like a problem on v1.1 board |
|
Linux 6.2-rc6 works for me with a FT2232H serial console attached. |
|
thanks for report...i tried the usb2uart i used on v1.0 and this works here...very strange...both are cp21xx...i try to find a difference. not-working one is a very small adapter with micro-usb jack, working one is larger with usb-A plug. need to find out, how i can get more information this one is working: this is the small one not working: so usb-id is same, but first (working) seems to be a cp2104 and second cp2102 |
|
If this is caused by the serial adapter fighting with the strapping it might not even be down to the USB-Serial chip, but any external pull-ups/pull-downs/buffers on the USB-Serial board. OT but could you have a quick look at https://lore.kernel.org/linux-mediatek/SN1KPR.7R1MV34Z4HRM3@brun.one/T/#u? Have you encountered anything like it? |
|
ch340G seems not working too: |
@lorenz you mean decreasing RB8,right? RB6 is not connected and a pullup to 3v3 |
|
Yeah, I meant RB8. |
|
Hey, I am having rhis exact issue with ASUS RT-AX59U and I am not using any serial adapter. My device has the waranty seal intact. |
I came accross the same problem today. I could solve it by reinstalling the following packages trough luci (The webinterface):
|
|
I had same Problem with CH340 and Board I don't know but i think it must be ver 1.1 |
|
I confirm as well CH340 with V1.1 has the same issues - wifi won't initialize: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Someone opened a case in openwrt for this issue but i think its firmware related problem and better here.
The text was updated successfully, but these errors were encountered: