gtg498u

I know there has been an Igor account on the forums that has been trolling the forums, just want to make sure that the troll has not made any changes to the focal distribution, masquerading as the legit Igor. I was building from source, and noticed this debug note:

@Pali praise the LORD Jesus Christ! Got it working! Here are the specs: espressobin v7 Armbian running Ubuntu Focal 20.04 Linux kernel v5.8.6 Use the latest Flash image for ddr4 1GB 800_800 AR9380 chipset is recognized and stable. Thank you!!!!

Thank you @Pali I did as you said, no dice. I could get latest 5.8 with 2018 uboot to recognize the wifi card, I could not get 5.6 with your 2020.10-rc4 to recognize the card, it just stops at waiting for kernel...I'm going to try to build my custom kernel with my 5.8 and apply my patches...hopefully that's all I need!

Thank you so much @Pali and also thank you @Igor I thought your comments were amusing. so I’ve tried many different options so far (and by the way I am trying to get this to work on the espressobin, please ignore any comments about the other SBC that I am using I’m not running Armbian on that one). I’m having issues with the latest Armbian (5.6.y) and u-boot (2018) for marvel on the espressobin. Armbian loads up great. the issue is the Atheros Wi-Fi card with the AR 9380 chipset. With that in the mPCIe slot of the espressobin v7, I get the kernel hang I posted earlier. I saw on some forms that there was a patch for the kernel on marvel targets in which the millisecond delay for one of the routines for the aardvark PCI driver needed to be increased to 50ms as opposed to 1ms. I have successfully been able to get the espressobin v7 to boot Armbian and it works just fine with the Wi-Fi card using kernel 4.19 however when I use kernel 5.4 and up I get the kernel hang I posted earlier. the issue is always with the aardvark PCI driver. I suspect that the latest u-boot from Marvell doesn’t support kernel 5.4 and up. i was hoping it was just a slight modification of the kernel in aardvark PCI driver in the function: advk_pcie_rd_conf any other ideas?

Thanks for the reply Igor, I tried the latest already. Still doesn't work with ath9k wifi card. Is there an issues with the build script using: https://github.com/MarvellEmbeddedProcessors/u-boot-marvell.git, branch u-boot-2018.03-armada-18.12 This is the latest, that the u-boot build scripts pulls from. Is there a config file I can use to tell the u-boot build script to pull from the u-boot mainline (similar to how I can tell the kernel build script which kernel I want to build)? Perhaps I don't understand fully. TBH I'm just a practitioner. I specifically need 5.4-rc4 because I have an entire software stack that is married to that kernel (and for good reason). I have my set-up working (not armbian) on a different hardware SBC. So I'm trying to support this other board. It is crucial that I use 5.4-rc4 and Atheros AR9380 chipset (ath9k) wifi card.

Long story short: Espressobin v7 1GB Armbian (Ubuntu Bionic 18.04) Kernel Mainline 5.4-rc4 (with custom userpatch (compiles fine)) U-Boot 2018.03-devel-18.12.3-gc9aa92c-armbian (Feb 20 2019 - 09:45:04 +0100) Without my Atheros AR9380 chipset (ath9k) wifi card inserted into the mPCIe, boots fine into Ubuntu from SD. With Atheros AR9380 chipset (ath9k) wifi card inserted into mPCIe I get a kernel hang (see below), I'm assuming it's because I'm using: U-Boot 2018.03-devel-18.12.3-gc9aa92c-armbian (Feb 20 2019 - 09:45:04 +0100) But according to this: https://docs.armbian.com/Hardware_Marvell/, I should be using U-Boot v2019.04-rc4 However, Marvell U-Boot only goes to 2018.03-armada 18.12: https://github.com/MarvellEmbeddedProcessors/u-boot-marvell I read on other forums with similar ath9k kernel hangs, that the kernel should be matched with the u-boot...so, how do I get u-boot v2019.04-rc4 on my espressobin, if Marvell U-Boot github doesn't host it? Here is the kernel hang: