Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some PCIe cards may not be detected on certain OSes #115

Open
miczyg1 opened this issue Aug 27, 2018 · 69 comments
Open

Some PCIe cards may not be detected on certain OSes #115

miczyg1 opened this issue Aug 27, 2018 · 69 comments
Assignees
Labels

Comments

@miczyg1
Copy link
Member

@miczyg1 miczyg1 commented Aug 27, 2018

mPCIe extension cards often require correct kernel modules/drivers and/or firmware blobs. If the card is not detected, be sure to check whether all needed modules and drivers are present on the system.

Also have a look at the mPCIe capabilities and connection to mPCIe ports on apu boards:
https://github.com/pcengines/apu2-documentation/blob/master/docs/APU_mPCIe_capabilities.md
Certain cards may require USB signals or SIM cards signals connected to the port. Be sure to match the mPCIe card requirements with correct mPCIe port to enable all features of the module.

@nicklowe
Copy link

@nicklowe nicklowe commented Aug 27, 2018

Thanks for adding this. There may be other related issues, however. I don't think this covers:

http://pcengines.info/forums/?page=post&id=DB3EE6E0-9ABA-4E0D-9960-9A995DD20B91&fid=DF5ACB70-99C4-4C61-AFA6-4C0E0DB05B2A

http://pcengines.info/forums/?page=post&id=68A48B1E-5F35-40BB-B4B9-10C362A92F3B&fid=DC038CE7-688B-4FD7-A449-014010E444D1

I suspect this is occurring because of a coreboot interoperability issue.

Could the suggestion from QCA be followed up if it is not on the radar currently?

"QCA had helped to look at the problem and found that the incompatible motherboard’s CPU-PCIe-TX signal came out 150ms after PCIe-reset, unlike common Intel motherboards in the market, which had the CPU-PCIe-TX signal out in about 30ms after PCIe-reset. QCA believed that the timing of the CPU-PCIe-TX signal can be altered through BIOS."

https://bugzilla.kernel.org/show_bug.cgi?id=84821#c48

@miczyg1
Copy link
Member Author

@miczyg1 miczyg1 commented Aug 27, 2018

@nicklowe thank You for Your feedback. We simply do not possess all possible hardware to test, but now we can consider equiping our apus with those modules to fix the problem, thanks to Your input.

We will try to reproduce and investigate the issue with currently owned Compex mPCIe modules for now. Of course we would gladly continue the thread and publish the information and status of our effort on PC Engines forum.

@pietrushnic FYI.

@miczyg1 miczyg1 self-assigned this Aug 27, 2018
@pietrushnic
Copy link
Member

@pietrushnic pietrushnic commented Aug 27, 2018

@nicklowe thanks for contribution. We should publish the hardware matrix that we testing and think about investing in above Compex modules.

@gilfrade
Copy link

@gilfrade gilfrade commented Sep 5, 2018

I'm trying to use a wireless card WLE1216V5-20 7A (source) and its detection is a little tricky and bios related. Maybe related to what @nicklowe described.

For example, with bios version v4.0.7 (came by default) the card is only detected with a second soft reboot. Multiple hard reboots does not allow the card to be detected.

With bios version v4.0.11 legacy and later the card is only detected if at bios F10 is pressed and "setup" is selected, it does not matter if new bios settings are saved or not.

Any thoughts? Is this a SeaBios related issue or Coreboot?

By the way download links for v4.0.9 and v4.0.10 are broken from https://pcengines.github.io/#mr-14

@miczyg1
Copy link
Member Author

@miczyg1 miczyg1 commented Sep 5, 2018

@gilfrade thank You for Your feedback. Have a look at CHANGELOG we have added some quirk for mPCIe2 port since v4.0.11. It may be influencing the card detection. Could You try v4.0.10 whether it behaves the same as v4.0.7? Also what slot do You use when connecting the card?

It seems like the older release links expired on pcengines site. I would have to ask person responsible for hosting what happened. For now You may download them here:

I would appreciate if You could check it.

@gilfrade
Copy link

@gilfrade gilfrade commented Sep 6, 2018

@miczyg1 thank you for your quick response. I made another round of tests that i included on the anexed file WLE1216V5-20_APU2.zip

The tests where made using APU2 with the card on slot2, all methods fail on slot1. Changing the bios option of forcing mpcie2 clock quirk when available with no change in results. Also tried changing bios options to match the defaults on v4.0.7 but made no difference.

@pietrushnic
Copy link
Member

@pietrushnic pietrushnic commented Sep 8, 2018

@gilfrade we are a little bit busy with osfc2018 we will take care of that in coming release. Unfortunately, we don't have that card, so probably will rely on WLE{200NX,600VX,900VX} and see if we can improve the situation for all. Please be patient this may take time till v4.8.0.5 or further version. Meanwhile, I have nothing else to offer then using old legacy versions.

@gilfrade
Copy link

@gilfrade gilfrade commented Sep 10, 2018

@pietrushnic i have the following cards WLE{200NX,600VX,900VX,216V5-20,650V5-18}

The cards WLE{200NX,600VX,900VX} have been working great with no issues regarding compatibility with mainboard.
The card WLE{650V5-18} have not been fully tested but it is detected and runs normally.
The card WLE{216V5-20} is the only with detection issues, when detected i have not encountered any issues running it.

The tests were made with APU2C2, but i also have APU3A2. I am available to help you test bios build changes.

@gilfrade
Copy link

@gilfrade gilfrade commented Oct 8, 2018

Any news about this issue? I can help testing.

@pietrushnic
Copy link
Member

@pietrushnic pietrushnic commented Oct 9, 2018

@miczyg1 can we provide debug version of v4.8.0.5, @gilfrade any chance you can use pce-fw-builder to build firmware by yourself?

@gilfrade
Copy link

@gilfrade gilfrade commented Oct 11, 2018

@pietrushnic Yes, i can do that.

@pietrushnic
Copy link
Member

@pietrushnic pietrushnic commented Oct 29, 2018

@gilfrade any luck with building and testing version with verbose logging? Best would be spew level 8 since it is most verbose.

@gilfrade
Copy link

@gilfrade gilfrade commented Nov 2, 2018

@pietrushnic Sorry i was waiting for @miczyg1 answer before proceding. Anyway i tried using pce-fw-builder but it stops when it tries to run "docker run" with error.

./build.sh release v4.8.0.5 apu2
or
./build.sh dev-build `pwd`/release/coreboot apu2

after cloning and downloading docker image it stops at

/bin/bash: /home/coreboot/scripts/pce-fw-builder.sh: Permission denied

I'm using Fedora 28 Workstation. What steps can i use to debug the docker error?

Update: It was a conflict with selinux. Making "sudo setenforce 0" temporary allows the process to continue.

@miczyg1
Copy link
Member Author

@miczyg1 miczyg1 commented Nov 5, 2018

@gilfrade have You successfully built the firmware using pce-fw-builder? Any news about WLE{216V5-20}?

@miczyg1
Copy link
Member Author

@miczyg1 miczyg1 commented Nov 9, 2018

@gilfrade I have produced debug binary for You:

apu2_v4.8.0.5_debug

This has to be rather PCI initialization problem. I have tried before to figure something out with external PCI devices on apu based on firmware log, but coreboot does not care for non-static PCI devices and does not enable them in early phases (although it does for ethernet controllers). They are later enabled by either SeaBIOS or kernel itself.

Try it and please send me the logs. You may also try to pass amd_iommu=off to kernel cmdline to see if it helps on v4.8.0.3 and later versions.

@miczyg1
Copy link
Member Author

@miczyg1 miczyg1 commented Nov 28, 2018

@gilfrade any results?

@gilfrade
Copy link

@gilfrade gilfrade commented Nov 30, 2018

@miczyg1 sorry for the delay, i was waiting for the flash recovery adapter just in case of failure. Here is the bios output with WLE{216V5-20}:

apu2_v4.8.0.5_debug.log

In sum, it did not detect the radio card even with amd_iommu=off. Can you produce a debug bios of v4.0.7? This is the only one that detects the board on a reboot after first boot, maybe we can identify differences.

@miczyg1
Copy link
Member Author

@miczyg1 miczyg1 commented Nov 30, 2018

@gilfrade thank You, of course we can try 4.0.7. From the log I can see that coreboot and SeaBIOS both detect a child device on the bridge (PCI 4:0.0) and assign resources, io, memory etc. The PCI ID is 168c:002a which matches the Qualcomm Atheros AR928X. The only thing that bothers me is:

PCI IRQ: Found device 0:02.04 using PIN D
PCI Devfn (0x14) not found in pirq_data table
PCI IRQ: Found device 0:02.05 using PIN A
PCI Devfn (0x15) not found in pirq_data table

I will try to do something about it. For now lets try these two binaries:

Also would You mind sending me also a dmesg output for 4.0.7 both working and not working + 4.8.0.6 working (if hopefully will work) and not working cases?

apu2_v4.8.0.6_debug
apu2_v4.0.7_debug

v4.0.7 may have problems with iPXE, however if You have dhcp server set up properly, it may work. v4.0.7 version is a little bit archaic and support very old build procedure, not maintained anymore, so it may not work exactly the same way as release binary.

Also be aware to not flash the SPI recovery dongle. After booting OS, remove the dongle, before flashing.

@gilfrade
Copy link

@gilfrade gilfrade commented Nov 30, 2018

@miczyg1 forgot to mention that i also have a WLE{200NX} in the board mpcie1, this radio has been working properly with every bios version tested. WLE{216V5-20} is in mpcie2.

apu2_v4.0.7_debug.log
apu2_v4.8.0.6_debug.log

In sum, in v4.0.7 WLE{216V5-20} is detected on reboot right after first boot although in this debug version fails to load ath10k firmware.
In v4.8.0.6 it is not detected.

@gilfrade
Copy link

@gilfrade gilfrade commented Nov 30, 2018

@miczyg1 here is dmesg of stable v4.0.7 and v4.8.0.6_debug

dmesg_v4.0.7.log
dmesg_v4.8.0.6_debug.log

@nicklowe
Copy link

@nicklowe nicklowe commented Jan 4, 2019

Any update on this?

@miczyg1
Copy link
Member Author

@miczyg1 miczyg1 commented Jan 9, 2019

@gilfrade @nicklowe in the logs I can see that the WLE216V5-20 is not detected by coreboot and/or SeaBIOS at all (except 4.0.7 after reboot) and thus PCIe bridge is not being enabled, resources are not assigned etc. This is a firmware problem. I will think what we can do to solve the problem (probably will send some binaries to You for testing). We do not have this particular WiFi card (we only have WLE200NX which works well), so it might be difficult or just take much time to find the root cause.

@nicklowe
Copy link

@nicklowe nicklowe commented Jan 9, 2019

Hi Michał,

Understood, thanks so much for your efforts here!

As a gift with no obligation or expectations of success on my behalf and purely to try and help out, I have ordered and paid for a WLE1216V5-20 card from compexshop.com to be delivered in your name to the 3mdeb office.

Regards,

Nick

@gilfrade
Copy link

@gilfrade gilfrade commented Jan 9, 2019

@miczyg1 i'm available to help with testing, send me some binaries whenever you need.

@miczyg1
Copy link
Member Author

@miczyg1 miczyg1 commented Jan 10, 2019

Hi Nick,

I bow before Your kindness and generosity. We will put in the best effort to achieve positive results with the WLE1216V5-20.

Best regards,
Michał

@nicklowe
Copy link

@nicklowe nicklowe commented Jan 14, 2019

Hi Michal,

Please can you let me know if you received the card today? The tracking says it should have been delivered. I just want to check that it has arrived safely! :-)

Cheers,

Nick

@miczyg1
Copy link
Member Author

@miczyg1 miczyg1 commented Jan 14, 2019

Hi Nick,

Yes, I have receive the card today. It arrived safely and is already connected for testing. Really appreciate that.

Regards,
Michał

@ouafnico
Copy link

@ouafnico ouafnico commented May 11, 2019

Hi everyone

I've search a day to explain why my wle200nx was not broadcasting any SSID, while the wle600vx on the same APU2C4 was working.

Both cards are installed in the same time.

I was using coreboot 4.9.0.2, and tried 4.9.0.5. Same problem.
After downgrading to 4.0.25 it works !

@miczyg1
Copy link
Member Author

@miczyg1 miczyg1 commented May 13, 2019

Hi @ouafnico ,

  1. Have possibly used the module on apu3/4?
  2. Is the WLE200NX detected in lspci?
  3. Have You tried amd_iommu=off in v4.9.0.x? Like here: pcengines/coreboot#206
drduh added a commit to drduh/PC-Engines-APU-Router-Guide that referenced this issue May 23, 2019
@riptidewave93
Copy link

@riptidewave93 riptidewave93 commented Mar 27, 2020

Sorry to revive an old issue, but I just found this thread after dealing with issues getting my WLE1216V5-20 to be seen on my APU2C4. I am curious @miczyg1, does the PE_RST circuit stay the same in the APU2D4 and APU2E4? I would really love to have a board that can run both the WLE1216V5-20 and WLE1216V2-20, and since the APU2 series is the only one with PCIe wired up to both mPCIe slots, it seems to be the only option for these cards.

@miczyg1
Copy link
Member Author

@miczyg1 miczyg1 commented Mar 28, 2020

@riptidewave93 have a look at https://github.com/pcengines/coreboot/blob/release/CHANGELOG.md#v41105---2020-03-27

In the upcoming few days we will release v4.11.0.5 that implements additional PCIe reset logic using GPIOs (PE_RSTx signals) on apu2. As far as I have tested it doesn't cause regression in PCIe modules detection in the default testing configuration in our office, but I have been unable to test with WLE1216* modules (due to covid-19 I am limiting visits to the office and did not switch the modules to check it yet, working remotely now most of the time). I have high expectations about this change and also hope to get this module working as it should. I will post an update here when I will have an opportunity to test WLE1216 on apu2.

As for the PE_RST circuit, there have been some changes since revision D as you may compare on the schematics between APU2C* vs APU2D* and APU2E*:

There is an additional resistor in the mPCIe2 slot reset circuit since revision D.

@riptidewave93
Copy link

@riptidewave93 riptidewave93 commented Mar 28, 2020

Hello @miczyg1,

Thank you very much for the update. If you have a build of v4.11.0.5 laying around, id love to help test it quick! As for the PE_RST circuit changes in the APU2D and newer, do you believe this will have any impact on the stability of the WLE1216* modules? I guess I am asking, is it worth replacing my APU2C4 with an APU2E4 if I want to use the WLE1216* modules? (given if the latest patches help get the cards working correctly)

EDIT: So I got a build of v4.11.0.5 going using pce-fw-builder, but sadly my WLE1216* modules are still undetected by OpenWrt. Guess I will wait and see how your testing goes. For all I know, I compiled it incorrectly; or so I hope. 🤞

@riptidewave93
Copy link

@riptidewave93 riptidewave93 commented Apr 3, 2020

Hello,

I see v4.11.0.5 is out, so I decided to test a few of the wireless modules I have laying around with this latest build. Below you can find the results of my testing. Note the below is from my APU2C4 board.

V4.11.0.4

Wireless Module mPCIe 1 mPCIe 2
WLE200NX ✔️ ✔️
WLE600VX ✔️ ✔️
WLE900VX ✔️ ✔️
WLE1216V5-20

V4.11.0.5

Wireless Module mPCIe 1 mPCIe 2
WLE200NX ✔️
WLE600VX ✔️
WLE900VX ✔️
WLE1216V5-20
@miczyg1
Copy link
Member Author

@miczyg1 miczyg1 commented Apr 3, 2020

@riptidewave93 thank you for your results. It seems like we broke mPCIe2 slot. I am looking into it now.

id love to help test it quick! I hope your words are still relevant. I see you have all modules at hand so I would like to "take an advantage" of that :) I will produce another binary with a small change to PCIe clocks, so maybe it could help.

@riptidewave93
Copy link

@riptidewave93 riptidewave93 commented Apr 3, 2020

@miczyg1 Sure thing, feel free to share anything you would like me to test. :)

@riptidewave93
Copy link

@riptidewave93 riptidewave93 commented Apr 3, 2020

@miczyg1 Results are below:

Test BIOS

Wireless Module mPCIe 1 mPCIe 2
WLE200NX ✔️
WLE600VX ✔️
WLE900VX ✔️
WLE1216V5-20

Note I am testing by seeing if the cards show up in lspci. I am testing using OpenWRT.

@miczyg1
Copy link
Member Author

@miczyg1 miczyg1 commented Apr 3, 2020

@riptidewave93
Copy link

@riptidewave93 riptidewave93 commented Apr 3, 2020

@miczyg1

Test BIOS 2

Wireless Module mPCIe 1 mPCIe 2
WLE200NX ✔️
WLE600VX ✔️
WLE900VX ✔️
WLE1216V5-20
@miczyg1
Copy link
Member Author

@miczyg1 miczyg1 commented Apr 3, 2020

@riptidewave93
Copy link

@riptidewave93 riptidewave93 commented Apr 3, 2020

@miczyg1 Looks better to me 😄. Feel free to "at" me if you need anymore testing done.

Test BIOS 3

Wireless Module mPCIe 1 mPCIe 2
WLE200NX ✔️ ✔️
WLE600VX ✔️ ✔️
WLE900VX ✔️ ✔️
WLE1216V5-20
@riptidewave93
Copy link

@riptidewave93 riptidewave93 commented Apr 24, 2020

As an additional followup @miczyg1, the last test firmware above, while works, also shows severe performance degradation on the intel NICs. Specifically, I was seeing only 350Mb/s across each port until I rolled back to 4.11.0.4

@syoder89
Copy link

@syoder89 syoder89 commented Apr 28, 2020

@riptidewave93 I've found a way to get both the WLE1216V5-20 and WLE1216V2-20 working simultaneously with the APU2e and it doesn't involve the bios. Instead it requires a little minor surgery. This isn't for the inexperienced but these boards aren't expensive. Disclaimer: I assume no responsibility if you destroy your board.

TLDR: To mimick the reset circuit from the mPCIe2 slot I desoldered and removed the SOT-23 diode D14 from the top side of the board and jumpered pin 1 to pin 3 via 0 ohm 0603 resistor (0603 / 0804 or bodge wire).

With the APU2e and stock bios I have had success (detection and function) with all my Compex cards in mPCIe2 (J13). I've tested the 200, 600, 650, 900 and both 1216v2 and v5 cards in the second slot.
In slot mPCIe1 (J14) I could get every card to work except the 1216 which would never be detected.

Looking at the schematic and board revisions I keyed in on the one major difference between the slots which is the reset circuit. In the 2d/2e the working mPCIe2 slot diode D2 is not stuffed and bypassed via R366. The non-working slot has D14 stuffed.

This diode acts as a diode logic OR gate allowing either the general PE_RST# or GPIO PE3_RST# to reset the slot. But being a diode it has a potential issue. The BAS40-06 has a forward voltage of about 380 mV at 1 mA.

The result is that the reset line on slot 1 will be at about 0.38V (perhaps less) while either of the reset lines are held low. This should be fine unless the mPCIe card also implements its own sort of diode logic which I suspect is happening with the WLE1216 and the card is not being reset.

The APU3c went through a similar respin to allow a no stuff option on the reset logic diodes.

You will lose the ability to reset the slot via GPIO but in my case it doesn't matter if it can't be reset at all.

@miczyg1
Copy link
Member Author

@miczyg1 miczyg1 commented Apr 29, 2020

@syoder89 thank you for such deep investigation of the problem. I was also planning to experiment with those diodes, but you were faster :) In the v4.11.0.5 I have added a reset logic using the GPIOs for the mPCIe slots, however it did more harm than good for apu2 (probably due to those diodes). So we did a fallback to the previous state (no GPIO reset at all) in order to get it working again in v4.11.0.6.

@michaelsteinmann maybe could you test this discovery in your lab?

@syoder89
Copy link

@syoder89 syoder89 commented Apr 29, 2020

I just tested v4.11.0.6 with my modified apu2e board and still had no problems with resets. Both of my WLE1216 cards continue to be detected and the network performance loss that I saw with v4.11.0.5 is gone. Iperf3 at the apu2 was showing about 350-400 Mbps in v4.11.0.5 but now it's back to 940 Mbps with this new version.

D14 diode removal / bypass

Wireless Module mPCIe 1 mPCIe 2
WLE200NX  ✔️  ✔️
WLE650V5-25  ✔️  ✔️
WLE900VX  ✔️  ✔️
WLE1216V5-20   ✔️  ✔️
WLE1216V2-20   ✔️  ✔️
@pietrushnic
Copy link
Member

@pietrushnic pietrushnic commented Apr 29, 2020

@syoder89 this looks really great, I wonder what @michaelsteinmann would say about that, maybe it can be incorporated into apu2f or g series?

@syoder89
Copy link

@syoder89 syoder89 commented Apr 29, 2020

I'm sure they'll want to validate the change as well and likely will offer it in a future respin. Pascal mentioned that they could send modified boards in the future. They're always very responsive.

The whole GPIO reset was a great tool for those horribly buggy Qualcomm 3G and LTE radios but it just doesn't work with some cards which I would consider non-compliant.

@michaelsteinmann
Copy link

@michaelsteinmann michaelsteinmann commented Apr 29, 2020

@riptidewave93
Copy link

@riptidewave93 riptidewave93 commented Apr 29, 2020

Guess it's time to save up for a future release APU2 board 😄

EDIT: Looking at the APU2C schematics, it seems it is missing the bypass resistor so I will have to remove both diodes, but hey it's worth it to have a board that works with all PCI-E cards then!

EDIT2: Thank you so much for digging into this @syoder89, I was able to review the schematics and fix up both slots on my APU2C4 (pics below for those who are curious on what it looks like).

IMG_20200429_175216
IMG_20200429_175238

@anonymous-one
Copy link

@anonymous-one anonymous-one commented May 3, 2020

Just a note for those looking at a solution / willing to spend some $$ for it...

I run an APU2D4 with 2 MikroTik adapters:

R11e-5HacD x 1
R11e-2HPnD x 1

And have zero issues running OpenWRT git latest.

I have not pushed an uptime of over 2 weeks as I tinker quite a bit but running the latest APU2 firmware / bios (as well as one previous, Feb 2020 release) I have zero issues.

root@OPENWRT-PRIMARY:~# lspci
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 16h (Models 30h-3fh) Processor Root Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Mullins IOMMU
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 16h (Models 30h-3fh) Host Bridge
00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 16h Processor Functions 5:1
00:02.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 16h Processor Functions 5:1
00:02.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 16h Processor Functions 5:1
00:02.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 16h Processor Functions 5:1
00:02.5 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 16h Processor Functions 5:1
00:08.0 Encryption controller: Advanced Micro Devices, Inc. [AMD] Kabini/Mullins PSP-Platform Security Processor
00:10.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller (rev 11)
00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 40)
00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 39)
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 42)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 11)
00:14.7 SD Host controller: Advanced Micro Devices, Inc. [AMD] FCH SD Flash Controller (rev 01)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 16h (Models 30h-3fh) Processor Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 16h (Models 30h-3fh) Processor Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 16h (Models 30h-3fh) Processor Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 16h (Models 30h-3fh) Processor Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 16h (Models 30h-3fh) Processor Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 16h (Models 30h-3fh) Processor Function 5
01:00.0 Network controller: Qualcomm Atheros QCA986x/988x 802.11ac Wireless Network Adapter
02:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
03:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
04:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
05:00.0 Network controller: Qualcomm Atheros AR958x 802.11abgn Wireless Network Adapter (rev 01)
root@OPENWRT-PRIMARY:~# uptime

EDIT : I also run my APU2D2 using the performance governor so its clocked at 1GHZ 24/7. Gets a bit warm but stability is not an issue.

EDIT 2 : I also power my APU2D2 using a quality MeanWell 12V 5A power adapter (IRM-60-12ST)... Mainly because it was there from my previous AP and I like 1 power supply to power both my switch and the APU2 that's there now.

@buletti
Copy link

@buletti buletti commented May 10, 2020

For the soldering noobs: When we can we expect a board revision that works for wave 2 WIFI devices?

@pstratem
Copy link

@pstratem pstratem commented Jul 16, 2020

I've done the same mod as @riptidewave93 and it worked. Presumably the diode just needs to be replaced by an actual OR gate.

@CmdrMoozy
Copy link

@CmdrMoozy CmdrMoozy commented Mar 27, 2021

I have an apu2c4 (BIOS version v4.13.0.3) with the WLE1216V5-20 card. Initially it was undetected by Linux at all, but after applying the soldering mod it is detected and mostly works.

However, I still have some problems with it. I'm trying to use it as an AP with hostapd, and while it seems to mostly work, it seems a bit "flaky". E.g., ~10% of packets are lost, ping is pretty consistently 4ms or so but then every Nth packet suddenly gets poor latency. I've done some work to rule out "normal" issues like, signal strength, sharing channels with other networks, proper Linux regulatory domain configuration, firmware loading, etc... I'm left wondering if this could be a hardware issue?

Has anyone else experienced similar issues using this card (or a similar) card?

@inteliboy
Copy link

@inteliboy inteliboy commented Apr 19, 2021

Has there been any development in getting WLE1216V2-20 and WLE1216V5-20 cards to work without the soldering mod?

I have just ordered an APU2E4 and was looking to put both of those cards in there but I do not feel comfortable taking the D14 diode out due to warranty.

@miczyg1
Copy link
Member Author

@miczyg1 miczyg1 commented Apr 19, 2021

Question to @michaelsteinmann ^

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet