Jump to content

SOLVED - Clearfog Pro PCI-e card only detected in slot 2 in Armbian

Technicavolous

By Technicavolous
in Marvell mvebu

 Share

Recommended Posts

Technicavolous

Technicavolous

Posted
Posted

EDIT: only the card in what I'm calling slot two is detected by lspci. 

wifi card near SoM -

 

at boot

PCI-e 0: Detected No Link.
PCI-e 2 (IF 1 - bus 0) Root Complex Interface, Detected Link X1, GEN 1.1

...

once booted

root@clearfogpro:~# lspci
00:02.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04)

 

wifi card in slot nearer edge of board -

 

at boot
PCI-e 1 (IF 0 - bus 0) Root Complex Interface, Detected Link X1, GEN 1.1
PCI-e 1: Detected No Link.

...

once booted
00:02.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04)
01:00.0 Network controller: Qualcomm Atheros QCA986x/988x 802.11ac Wireless Network Adapter

 

This wifi card -

https://www.amazon.com/gp/product/B011SI4544/ref=oh_aui_detailpage_o05_s00?ie=UTF8&psc=1

 

Here is the full log of both boots

  Reveal hidden contents

 

Kind of funny as I didn't think of trying the other slot because I 'wanted' to put it in the middle of the board for simplicity of running the antenna wires ... I'll figure out a new antenna layout, glad the thing gets seen in Armbian!

 

I removed network-manager from 5.38 stretch next 4.14.14 so I have to do this manually. Not finding the card was kind of breathtaking as it was suggested to use this chipset. Thought I might pass this on if anyone else is having detection problems.

 

EDIT: only slot 2 gets identified with lspci

I know I've read somewhere something about 'serdes' as you will see in the u-boot messages but I just can't figure out what I'm looking for. 

 

I also have a 4 port Marvell SATA card that will only detect in the 2nd PCI-e slot. (mPCI-e?) Anyway, only the card in the slot farthest from the SoM gets reported by lspci but they both show when u-boot detects them.

 

I have no clue where to look for this answer - any pointers?

 

Here is the full boot output with my SATA card in slot 0 and the wifi card in slot 2

 

  Reveal hidden contents

 

I can't give armbianmonitor -u as I don't have any networking set up yet.

Technicavolous

Technicavolous

Posted
  • Author
Posted

First thing I did ... took a really close up picture all looks good but doused it with board cleaner. Hit the contacts on the card for good measure.

 

The thing that kills me is u-boot finds them both -

U-Boot 2013.01-gf906e3d-dirty (Dec 01 2016 - 23:19:59) Marvell version: 2015_T1.
0p11

Board: A38x-Customer-Board-1
SoC:   MV88F6828 Rev A0
       running 2 CPUs
CPU:   ARM Cortex A9 MPCore (Rev 1) LE
       CPU 0
       CPU    @ 1600 [MHz]
       L2     @ 800 [MHz]
       TClock @ 250 [MHz]
       DDR3    @ 800 [MHz]
       DDR3 32 Bit Width,FastPath Memory Access, DLB Enabled, ECC Disabled
DRAM:  1 GiB
MMC:   mv_sdh: 0
sdhci_transfer_data: Error detected in status(0x408000)!
PCI-e 1 (IF 0 - bus 0) Root Complex Interface, Detected Link X1, GEN 1.1
PCI-e 2 (IF 1 - bus 1) Root Complex Interface, Detected Link X1, GEN 2.0
USB2.0 0: Host Mode
USB3.0 0: Host Mode
USB3.0 1: Host Mode

Map:   Code:                    0x3fed4000:0x3ff980cc
       BSS:                     0x3ffefd5c
       Stack:                   0x3f9c3f20
       Heap:                    0x3f9c4000:0x3fed4000
       U-Boot Environment:      0x000f0000:0x00100000 (MMC)
...

Armbian (lspci) finds whichever one is in the outside slot.

Technicavolous

Technicavolous

Posted
  • Author
Posted

dmsg output

  Reveal hidden contents

 

The entire screencap of both boots in spoiler in above post as well.

 

 

zador.blood.stained

zador.blood.stained

Posted
Posted
  On 2/20/2018 at 7:45 PM, Technicavolous said:

The entire screencap of both boots in spoiler in above post as well.

Expand  

That doesn't include dmesg, that's why I asked for it.

 

  On 2/20/2018 at 7:45 PM, Technicavolous said:

dmsg output

Expand  

Hm, I see firmware loading issues for an ath10k card, and since I see cfg80211 lines I'm assuming that the second card is detected correctly.

I would try adding missing firmware files first.

Is it a dual radio card?

 

Technicavolous

Technicavolous

Posted
  • Author
Posted

BUT it finds it fine on the outside slot. Also find my SATA controller on the outside slot. Neither are found by Armbian on the inside slot but both are reported by u-boot in either slot. Both show up in u-boot regardless of slot, slot near the SoM never shows anything in Armbian.

 

SerDes?? I read somewhere that the slot has to be configured but it was oooolllldddd ...

zador.blood.stained

zador.blood.stained

Posted
Posted

It's just confusing without seeing "lspci -t -nn" to map what is connected to what.

I remember having PCIe detection issues in the past, but I don't remember on which kernel.

 

Can you try booting a mainline (next) image from a USB flash to check if it detects both devices?

 

  On 2/20/2018 at 8:06 PM, Technicavolous said:

SerDes?? I read somewhere that the slot has to be configured but it was oooolllldddd ...

Expand  

It is configured before the u-boot proper, so if PCIe cards are detected by u-boot it's safe to assume that SERDES configuration is correct.

Technicavolous

Technicavolous

Posted
  • Author
Posted

I have the clearfog pro with emmc ... I've never been able to boot from usb, but I've done well with tftp and ext4load.

 

I have a tftp server on my xu4 with quite a few files there. 

 

I did 

apt-get install armbian-firmware and it said it was the latest. (default kernel ... have no networking on next kernel)

apat-get install armbian-firmware-full basically says it won't do it because firmware is gone.

  Reveal hidden contents

 

I'll try again to boot from a usb stick, but so far I've failed at that.

Technicavolous

Technicavolous

Posted
  • Author
Posted

I was unable to boot mainline (next) from usb but I'm getting really quick at imaging the eMMC ;] loaded a fresh copy of 5.38 stretch next

 

lspci -t -nn output

root@clearfogpro:~# lspci -t -nn
-[0000:00]---02.0-[01]----00.0

 

lspci output

root@clearfogpro:~# lspci
00:02.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04)
01:00.0 Network controller: Qualcomm Atheros QCA986x/988x 802.11ac Wireless Network Adapter

 

 

dmesg output

  Reveal hidden contents

 

Seems same. 4.14.14 or 4.4.115 same behavior.

 

If u-boot didn't show both I'd think it was hardware. But it clearly shows both cards regardless of which slot they are in. Armbian only sees the outside slot, either card.

Technicavolous

Technicavolous

Posted
  • Author
Posted

I know what to do to test ... but I have to leave for work :\

 

install next 4.14.114

I have to learn the manual networking. I'm hoping Count Doku config here will work for me.

update / upgrade

then switch to nightly and see if the card is detected

?

 

install the clearfog debian image

see if the card is detected ?

(update / upgrade fails with repository errors though)

 

whatever else any of you instruct me to do.

 

it will be a day or two before I'm back at the terminal :((

 

Heisath

Heisath

Posted
Posted

Funny thing is, I actually also have a SATA Card (but only 2 Port) running in one PCIe and the WLE600VX (small brother of your 900) in the other. 
And I checked and both are running in both slots (cross checked)....

I am currently using Armbian 5.41 (newest I think)
(ARMBIAN 9 (stretch)  Debian GNU/Linux 9 (stretch) 4.14.18-mvebu)

 

I also suggest to update your system and check again. And if you compile your own kernel, *do not* check the pcie option as this breaks the ath10k pci driver.... 
I am unsure why and will make a seperate post for that problem....

 

Attached my output from lspci and dmesg 

 

dmesg part of pci and ath10k 

[   11.199812] pci 0000:00:03.0: enabling device (0140 -> 0142)
[   11.205508] ath10k_pci 0000:02:00.0: enabling device (0140 -> 0142)
[   11.212012] ath10k_pci 0000:02:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[   11.332699] libphy: mv88e6xxx SMI: probed
[   11.336757] DSA: switch 0 0 parsed
[   11.340204] DSA: tree 0 parsed
[   11.464359] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:02:00.0.bin failed with error -2
[   11.475104] ath10k_pci 0000:02:00.0: Falling back to user helper
[   11.528208] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/cal-pci-0000:02:00.0.bin failed with error -2
[   11.538610] ath10k_pci 0000:02:00.0: Falling back to user helper
[   11.553353] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/firmware-6.bin failed with error -2
[   11.564121] ath10k_pci 0000:02:00.0: Falling back to user helper
[   11.585703] ath10k_pci 0000:02:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043222ff sub 0000:0000
[   11.594968] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs 0 testmode 0
[   11.603714] ath10k_pci 0000:02:00.0: firmware ver 10.2.4.70.54 api 5 features no-p2p,raw-mode,mfp crc32 9d340dd9
[   11.643836] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/board-2.bin failed with error -2
[   11.654320] ath10k_pci 0000:02:00.0: Falling back to user helper
[   11.670826] ath10k_pci 0000:02:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
[   12.154010] Marvell 88E1540 mv88e6xxx-0:00: attached PHY driver [Marvell 88E1540] (mii_bus:phy_addr=mv88e6xxx-0:00, irq=POLL)
[   12.361859] Marvell 88E1540 mv88e6xxx-0:01: attached PHY driver [Marvell 88E1540] (mii_bus:phy_addr=mv88e6xxx-0:01, irq=POLL)
[   12.496977] Marvell 88E1540 mv88e6xxx-0:02: attached PHY driver [Marvell 88E1540] (mii_bus:phy_addr=mv88e6xxx-0:02, irq=POLL)
[   12.586213] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[   12.631796] Marvell 88E1540 mv88e6xxx-0:03: attached PHY driver [Marvell 88E1540] (mii_bus:phy_addr=mv88e6xxx-0:03, irq=POLL)
[   12.742057] Marvell 88E1540 mv88e6xxx-0:04: attached PHY driver [Marvell 88E1540] (mii_bus:phy_addr=mv88e6xxx-0:04, irq=POLL)
[   12.760583] Generic PHY fixed-0:03: attached PHY driver [Generic PHY] (mii_bus:phy_addr=fixed-0:03, irq=POLL)
[   12.879496] ath10k_pci 0000:02:00.0: htt-ver 2.1 wmi-op 5 htt-op 2 cal otp max-sta 128 raw 0 hwcrypto 1
[   13.010060] ath: EEPROM regdomain: 0x0
[   13.010064] ath: EEPROM indicates default country code should be used
[   13.010066] ath: doing EEPROM country->regdmn map search
[   13.010069] ath: country maps to regdmn code: 0x3a
[   13.010071] ath: Country alpha2 being used: US
[   13.010073] ath: Regpair used: 0x3a
[   13.024541] ath10k_pci 0000:02:00.0 wlp2s0: renamed from wlan0

 

lspci 

00:02.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04)
00:03.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04)
01:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01)
02:00.0 Network controller: Qualcomm Atheros QCA986x/988x 802.11ac Wireless Network Adapter

 

Picture of my assembly: https://jannis.imserv.org/nextcloud/index.php/s/Ydp8JMqJCbGzdBK

 

 

Technicavolous

Technicavolous

Posted
  • Author
Posted

I have never compiled anything more than simple c programs I wrote myself ... it's something I think I'd better set up and do. For now, all of my 'desktops' are Odroid ARM boards. I will get an x86 system to set up per the Armbian build instructions.

 

For now, I'm using what I can download from the download page which is currently  Armbian_5.38_Clearfogpro_Debian_stretch_next_4.14.14. network manager is broken on that one so I haven't been able to do any updates on it. I've been able to update default 4.4.112 to 115 but it has the same problems.

 

I installed the Solid-Run 20171001 Debian Stretch but it fails at apt-get update so I don't trust it, but their lspci also shows only the card in the outside slot. Its running 4.9.45.

 

I'm praying at this moment it is a difference in kernel or something because if it's hardware I just don't trust Solid-Run to replace it with any speed, it took me months to get this board ...

 

I'm really bummed, I find posts all over Armbian and Solid-Run forums that others have had problems running two cards at the same time, most posts have gone unanswered. I can usually get past anything but this one has me stopped. The entire project fails if both cards won't function.

 

EDIT:

Also I noted my card is a pcie 1.1 card, there have been issues

https://forum.solid-run.com/hardware-f33/pcie-1-1-cards-not-detected-t3332.html

but seem to have been solved. For the heck of it I ordered a mpcie 2.0 card, 2 port only but for $20 it's a good answer anyway ...

 

 

Heisath

Heisath

Posted
Posted

I just checked the dmesg postet by Techni and it seems like the firmware for the card ist just not available: 

[    6.379978] pci 0000:00:02.0: enabling device (0140 -> 0142)
[    6.379999] ath10k_pci 0000:01:00.0: enabling device (0140 -> 0142)
[    6.380248] ath10k_pci 0000:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 r
eset_mode 0
[    6.674749] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/pre-cal-
pci-0000:01:00.0.bin failed with error -2
[    6.674756] ath10k_pci 0000:01:00.0: Falling back to user helper
[    6.953983] mvneta f1070000.ethernet eth0: could not find the PHY
[    6.953990] mvneta f1070000.ethernet eth0: cannot probe MDIO bus
[    7.004533] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/cal-pci-
0000:01:00.0.bin failed with error -2
[    7.004539] ath10k_pci 0000:01:00.0: Falling back to user helper
[    7.006015] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA988X/
hw2.0/firmware-6.bin failed with error -2
[    7.006021] ath10k_pci 0000:01:00.0: Falling back to user helper
[    7.008097] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA988X/
hw2.0/firmware-5.bin failed with error -2
[    7.008101] ath10k_pci 0000:01:00.0: Falling back to user helper
[    7.010003] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA988X/
hw2.0/firmware-4.bin failed with error -2
[    7.010007] ath10k_pci 0000:01:00.0: Falling back to user helper
[    7.012238] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA988X/
hw2.0/firmware-3.bin failed with error -2
[    7.012243] ath10k_pci 0000:01:00.0: Falling back to user helper
[    7.014410] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA988X/
hw2.0/firmware-2.bin failed with error -2
[    7.014414] ath10k_pci 0000:01:00.0: Falling back to user helper
[    7.016102] ath10k_pci 0000:01:00.0: Failed to find firmware-N.bin (N between
 2 and 6) from ath10k/QCA988X/hw2.0: -11
[    7.016106] ath10k_pci 0000:01:00.0: could not fetch firmware files (-11)
[    7.016111] ath10k_pci 0000:01:00.0: could not probe fw (-11)
[    7.239162] systemd-journald[295]: Received request to flush runtime journal
from PID 1

 

Is it possible that the ath10k is (why ever) not integrated?

 

@Technicavolous can you check with ls or so if there are any files in /lib/firmware/ath10k/QCA988X/hw2.0 ?

 

At my clearfog it looks like this: 

root@clearfogpro:~# ls /lib/firmware/ath10k/QCA988X/hw2.0
board.bin  firmware-4.bin  firmware-5.bin

 

 

Here it also says that there are some problems with the WLE900VX not getting detected: 
https://wireless.wiki.kernel.org/en/users/drivers/ath10k#supported_devices

 

 

Heisath

Heisath

Posted
Posted

Excuse this double post / push.

 

But I think I found your problem Techni and a simple solution.

 

I built a new armbian image using newest kernel and debian and made sure to check the ath10k pci driver option.

 

Then burned it to my sd card and booted my clearfog -> voila same error as yours in dmesg. And no firmware files in /lib/firmware/ath10k!

 

A simple apt install firmware-atheros got me the firmware and after a reboot the card is detected and available in ifconfig.

 

So just try it using lan and install the atheros firmware.

 

I will also provide my testimage (login: root and 1234) in case you have no network connectivity.

(Upload will take some time, will update this with link when its done...)

EDIT: couldnt get a running image resized from my 64GB SD Card in time. Will try again if you need it...

 

Greetings,

count-doku

 

1
Technicavolous

Technicavolous

Posted
  • Author
Posted

@count-doku THAT seems like what I've been thinking! Zador had told me to update the firmware and I *thought* I had but obviously had failed. I have installed the Solidrun Debian and have the same results.

 

I will be back at my lab late tonight and I will let you know! Thanks for offering the image, but I need to learn how to handle all of this myself. But the firmware makes sense. 

 

Thanks!!
 

Technicavolous

Technicavolous

Posted
  • Author
Posted

@zador.blood.stained it will be a little bit before I can compile ... but it is high on my list to build an Armbian build system and learn it. 

Would that be possible to do using the automated build system noted here, and would it be better to learn that than make my own build system?

 

@count-doku No matter what configuration I use, neither my SATA card nor my wifi card are usable in the inside slot, both are usable in the outside slot. I had Armbian-Config recognizing the wifi card in the outside slot but not the inside slot. I'm beginning to believe it's hardware but u-boot reporting the card still has me doubting.

 

I would very much like to try an image that works for you if we can figure out how to get it to me...

 

I've installed so many images I've confused myself. Tonight I'm going to make a truth chart and post all the dmesg outputs. All I can say is behavior has been identical in every case.

zador.blood.stained

zador.blood.stained

Posted
Posted (edited)

@Technicavolous

I just looked at your dmesg log from this post

  On 2/20/2018 at 7:45 PM, Technicavolous said:

[    0.000000] Machine model: SolidRun Clearfog Base A1

Expand  

 

Did you flash the u-boot binary for the Base model to your eMMC? Or looking at your earlier posts you must have flashed the non-Armbian (unpatched) u-boot blob. Looks like this results in loading Clearfog Base DT even when using the Clearfog Pro image.

Now that you have OS running from eMMC you should be able to flash a new u-boot image to /dev/mmcblk0boot0 using dd (you'll need to unlock it by running "echo 0 > /sys/block/mmcblk0boot0/force_ro" from a root command prompt or "echo 0 | sudo tee /sys/block/mmcblk0boot0/force_ro" from a non-root command prompt).

Please unpack a .deb package from here and use the u-boot.mmc blob from it. You should be able to confirm the flashing by checking the u-boot build date printed during early boot in the serial console.

Edited by zador.blood.stained
boot0 partition should be unlocked first
zador.blood.stained

zador.blood.stained

Posted
Posted
  On 2/24/2018 at 10:59 AM, count-doku said:

The image is a fresh build and just apt updated and firmware-atheros installed.

You might need to re expand the partition though, if you want to use it for production...

Expand  

This won't help if this image is loaded by a wrong u-boot version (that was flashed to eMMC previously) unless you force load a proper DT file.

Igor

Igor

Posted
Posted

There is some problem with a legacy kernel. With ath10 card it crashes. Checking mainline ...
 

  Reveal hidden contents

 

After switching to 4.14.18 from apt.armbian.com, everything is fine, wlan works. After installing full firmware package: apt install armbian-firmware-full

http://ix.io/OJw


Serial console log:
 

  Reveal hidden contents
 


Compex VL600 running as AP, my notebook client few meters away, Intel AC7260
 

  Reveal hidden contents

 

Changed to the other mPCI port, everything is normal, performance unchanged, properly recognized:
 

  Reveal hidden contents

 

Technicavolous

Technicavolous

Posted
  • Author
Posted
  On 2/24/2018 at 9:12 AM, zador.blood.stained said:

Or looking at your earlier posts you must have flashed the non-Armbian (unpatched) u-boot blob. Looks like this results in loading Clearfog Base DT even when using the Clearfog Pro image.

Expand  

This is the entirety of the problem.  Wrong u-boot, wrong DTB. I still can't get kwboot or the script to initiate a boot but since I had already a semi-working u-boot I wrote the correct one and it was immediately able to see usb where I never had before.

 

I'm going to start from scratch but lspci got a hoot from me when I saw this -

root@clearfogpro:~#lspci
00:02.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04)
00:03.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04)
01:00.0 Network controller: Qualcomm Atheros QCA986x/988x 802.11ac Wireless Network Adapter
02:00.0 SATA controller: Marvell Technology Group Ltd. Device 9215 (rev 11)
root@clearfogpro:~# 

 

I'll correct my page on installing from tftp to emphasize the right files. I'd be miles ahead had I got the u-boot correct in the first place. 

Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept