Thank you. I try to understand: the dwmac-intel module will make both my ec1000s nic and ax200 wireless work? They share the same underlying "problem"?
When i installed this minipc with win10 i noticed it took a LOT of extra intel drivers (aprox 500mbyte of drivers for windows) to make it all work. A lot of extra intel devices in device manager, most of which i'm not certain what they do. And most are by default not recognised by win10, they all need extra drivers and firmware. I was surprised (in a positive way) that i was able to boot LE at all on this minipc, with all these unknown intel devices . Are all modern intel based minipc's like this, or is it just this one? I'm more used to older hardware.
Support of Intel AX200 WiFi card
-
fred_35 -
January 29, 2020 at 9:34 AM -
Thread is Resolved
-
-
I have AX201 and it works fine in LE. I would assume AX200 should work too.
-
dipswitch Sorry regarding AX200 I only looked for firmware errors and there are none.
The good news: in LE 13 the AX200 is working fine:
CodeOct 15 16:48:26.567299 DigitalEngine kernel: Intel(R) Wireless WiFi driver for Linux Oct 15 16:48:26.567357 DigitalEngine kernel: iwlwifi 0000:01:00.0: enabling device (0000 -> 0002) Oct 15 16:48:26.567546 DigitalEngine kernel: iwlwifi 0000:01:00.0: Detected crf-id 0x3617, cnv-id 0x100530 wfpm id 0x80000000 Oct 15 16:48:26.567707 DigitalEngine kernel: iwlwifi 0000:01:00.0: PCI dev 2723/0084, rev=0x340, rfid=0x10a100 Oct 15 16:48:26.567843 DigitalEngine kernel: iwlwifi 0000:01:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz
But in LE12:
Code
Display MoreOct 15 15:13:45.214986 DigitalEngine kernel: Intel(R) Wireless WiFi driver for Linux Oct 15 15:13:45.215076 DigitalEngine kernel: iwlwifi 0000:01:00.0: enabling device (0000 -> 0002) Oct 15 15:13:45.248306 DigitalEngine kernel: iwlwifi 0000:01:00.0: CSR_RESET = 0x10 Oct 15 15:13:45.248659 DigitalEngine kernel: iwlwifi 0000:01:00.0: Host monitor block 0x0 vector 0x0 Oct 15 15:13:45.248880 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 0]: 0x3f7f0430 Oct 15 15:13:45.249117 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 1]: 0x3f7f8c30 Oct 15 15:13:45.249359 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 2]: 0x3f7f0830 Oct 15 15:13:45.249597 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 3]: 0x3f7f0830 Oct 15 15:13:45.249806 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 4]: 0x3f7f8030 Oct 15 15:13:45.250380 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 5]: 0x3f7f8830 Oct 15 15:13:45.254206 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 6]: 0x3f7f0c30 Oct 15 15:13:45.254376 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 7]: 0x3f7f8430 Oct 15 15:13:45.254532 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 8]: 0x3f7f0c30 Oct 15 15:13:45.254672 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 9]: 0x3f7f8c30 Oct 15 15:13:45.254814 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 10]: 0x3f7f8c30 Oct 15 15:13:45.254950 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 11]: 0x3f7f0030 Oct 15 15:13:45.255141 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 12]: 0x3f7f0030 Oct 15 15:13:45.255294 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 13]: 0x3f7f8830 Oct 15 15:13:45.255429 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 14]: 0x3f7f8030 Oct 15 15:13:45.255563 DigitalEngine kernel: iwlwifi 0000:01:00.0: Host monitor block 0x0 vector 0x1 Oct 15 15:13:45.255693 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 0]: 0x044466c2 Oct 15 15:13:45.255833 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 1]: 0x044466c2 Oct 15 15:13:45.255972 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 2]: 0x044466c2 Oct 15 15:13:45.256106 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 3]: 0x044466c2 Oct 15 15:13:45.256240 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 4]: 0x044466c2 Oct 15 15:13:45.256384 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 5]: 0x044466c2 Oct 15 15:13:45.256522 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 6]: 0x044466c2 Oct 15 15:13:45.256657 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 7]: 0x044466c2 Oct 15 15:13:45.269425 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 8]: 0x044466c2 Oct 15 15:13:45.269968 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 9]: 0x044466c2 Oct 15 15:13:45.270626 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 10]: 0x044466c2 Oct 15 15:13:45.272983 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 11]: 0x044466c2 Oct 15 15:13:45.273652 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 12]: 0x044466c2 Oct 15 15:13:45.274056 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 13]: 0x044466c2 Oct 15 15:13:45.274206 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 14]: 0x044466c2 Oct 15 15:13:45.274350 DigitalEngine kernel: iwlwifi 0000:01:00.0: Host monitor block 0x0 vector 0x6 Oct 15 15:13:45.274586 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 0]: 0xf00c4471 Oct 15 15:13:45.274744 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 1]: 0xb00c4471 Oct 15 15:13:45.274878 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 2]: 0xb00c4471 Oct 15 15:13:45.275267 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 3]: 0xf00c4471 Oct 15 15:13:45.275398 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 4]: 0xb00c4471 Oct 15 15:13:45.275524 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 5]: 0xe00c4471 Oct 15 15:13:45.275644 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 6]: 0xe00c4471 Oct 15 15:13:45.275761 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 7]: 0xa00c4471 Oct 15 15:13:45.275877 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 8]: 0xe00c4471 Oct 15 15:13:45.275994 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 9]: 0xb00c4471 Oct 15 15:13:45.276109 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 10]: 0xf00c4471 Oct 15 15:13:45.276227 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 11]: 0xb00c4471 Oct 15 15:13:45.276341 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 12]: 0xe00c4471 Oct 15 15:13:45.276457 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 13]: 0xa00c4471 Oct 15 15:13:45.276571 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 14]: 0xe00c4471 Oct 15 15:13:45.276690 DigitalEngine kernel: iwlwifi 0000:01:00.0: Host monitor block 0x22 vector 0x0 Oct 15 15:13:45.276806 DigitalEngine kernel: iwlwifi 0000:01:00.0: value [iter 0]: 0x00000000 Oct 15 15:13:45.276919 DigitalEngine kernel: iwlwifi: probe of 0000:01:00.0 failed with error -110
Error -110 can be caused by power on issue, you can try this fix. The file name is /storage/.config/modprobe.d/iwlwifi.conf in LE.
-
I booted the same nightly as yesterday and indeed, it seems the wireless ax200 card is detected. But as soon as i make it connect, LE crashes, the libreelec bootscreen reappears and after a while the gui shows.
I hope i was able to pull the corresponding logs: https://paste.libreelec.tv/magnetic-krill.log
-edit: i rebooted the minipc and it now is able to connect to wirelesss. Don't know why the pc crashed at first try. Will test this some more.
-
i rebooted the minipc and it now is able to connect to wirelesss. Don't know why the pc crashed at first try.
I hope your firmware is up-to-date.
-
I hope your firmware is up-to-date.
I have no idea? How can i tell? This was while running the most recent nightly build.
-
I have no idea? How can i tell?
If BIOS/EFI and all Windows drivers are up-to-date, then your firmware, used by LE, is up-to-date, too.
Maybe that step is needed to get reliable results.
-
If BIOS/EFI and all Windows drivers are up-to-date, then your firmware, used by LE, is up-to-date, too.
Maybe that step is needed to get reliable results.
I misunderstood, i thought you meant the firmware for the ax200 card. The efi is on it's latest version, as are all windows drivers.
-
In the latest nightly, the ax200 seems to work pretty good. For those who may need it: the bluetooth part of the card isn't working. LE doesn't detect a bluetooth adapter. This doesnt affect me, since i don't use bluetooth devices. But for those who do please be aware that this maybe needs fixing.
-
When looking at upward-salmon.log you posted in other thread bluetooth seem to be working fine.
-
When looking at upward-salmon.log you posted in other thread bluetooth seem to be working fine.
That's strange, i'm not suring what i'm doing wrong. I have to admit, i didn't give it a lot of attention.
-
Yes, looks like the behavior is not stable.
It may depend on cold or warm boot. Or even on reboot which OS was booted before.
You can test if disabling "Fast Boot" in EFI firmware (when available and enabled) may improve behavior.
-