0
deb2016

Clearfogpro : lost PCIe sata card after update

Recommended Posts

Hello,

 

I have just updated armbian on my clearfogpro and after the hard drive plugged on the PCIe sata card (2 slots) is no more recognized, it does not appear at all in logs.

 

It was working like a charm before.  I wonder what happened ?

 

Here is the output of 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)
02:00.0 Network controller: Qualcomm Atheros QCA986x/988x 802.11ac Wireless Network Adapter

I think the PCIe card is recognized (I have also a wifi card on the other PCI slot). I wonder why armbian does no more see the hard drive, this one is powered I can hear it.

 

It must be due to the u-boot version. Here is the listing of /boot directory

-rw-rw-r-- 1 root root     319 Jan 12 17:28 armbianEnv.txt
-rw-rw-r-- 1 root root     319 Jan 12 17:28 armbianEnv.txte
-rw-rw-r-- 1 root root    1624 Jan 27  2018 armbian_first_run.txt.template
-rw-rw-r-- 1 root root   38518 Jan 27  2018 boot.bmp
-rw-rw-r-- 1 root root    1532 Jan 27  2018 boot.cmd
-rw-rw-r-- 1 root root    4882 Jan 27  2018 boot-desktop.png
-rw-rw-r-- 1 root root    1604 Jan 27  2018 boot.scr
-rw-r--r-- 1 root root  123827 Nov 26 08:29 config-4.14.83-mvebu
lrwxrwxrwx 1 root root      17 Jan 12 17:21 dtb -> dtb-4.14.83-mvebu
drwxr-xr-x 2 root root    4096 Jan 12 17:20 dtb-4.14.83-mvebu
lrwxrwxrwx 1 root root      17 Mar 10  2018 dtb.old -> dtb-4.14.18-mvebu
-rw-r--r-- 1 root root 5073125 Jan 12 17:21 initrd.img-4.14.83-mvebu
-rw-r--r-- 1 root root 2179815 Nov 26 08:29 System.map-4.14.83-mvebu
lrwxrwxrwx 1 root root      21 Jan 12 17:21 uInitrd -> uInitrd-4.14.83-mvebu
-rw-r--r-- 1 root root 5073189 Jan 12 17:21 uInitrd-4.14.83-mvebu
-rwxr-xr-x 1 root root 5450232 Nov 26 08:29 vmlinuz-4.14.83-mvebu
lrwxrwxrwx 1 root root      21 Jan 12 17:21 zImage -> vmlinuz-4.14.83-mvebu

 

In the dtb directory, I see many *dtb files, one is for the clearfogpro, but in the logs I can see

 

[    0.000000] OF: fdt: Machine model: SolidRun Clearfog A1

 

Should not it say "Clearfogpro" ?

 

Edited by deb2016

Share this post


Link to post
Share on other sites

Hello,

 

I think the issue is that the wrong dtb file is loaded.

 

There are three files in the /boot/dtb directory

-rw-r--r-- 1 root root 18619 Jan 12 15:07 armada-388-clearfog-base.dtb
-rw-r--r-- 1 root root 20484 Jan 12 15:07 armada-388-clearfog.dtb
-rw-r--r-- 1 root root 20512 Jan 12 15:07 armada-388-clearfog-pro.dtb

 

The command "cat /proc/device-tree/modele returns "SolidRun Clearfog A1", which I guess corresponds to the "armada-388-clearfog.dtb" file.

 

There are no dtb files in /boot, so I guess the u-boot process takes the default one, "armada-388-clearfog.dtb"  ?

 

How can I set the dtb file ?

 

Thanks for your kind attention.

 

Regards

Share this post


Link to post
Share on other sites
16 hours ago, deb2016 said:

How can I set the dtb file ?

First, stop u-boot during startup with spacebar, and then check "printenv" to see what is the value of "fdtfile".

If it is the wrong DT file, you can change it by overwritting "fdtfile" in /boot/armbianEnv.txt ...

Share this post


Link to post
Share on other sites
On 1/12/2019 at 10:48 PM, deb2016 said:

I have just updated armbian on my clearfogpro and after the hard drive plugged on the PCIe sata card (2 slots) is no more recognized, it does not appear at all in logs.


Clearfog wasn't receiving any updates in last update beside upstream fixes. There were some adjustments to the mvebu-next kernel for Helios4 purposes by @gprovost https://github.com/armbian/build/commits/master/patch/kernel/mvebu-next I doubt they could be behind those troubles.

Share this post


Link to post
Share on other sites
On 1/15/2019 at 3:07 PM, martinayotte said:

First, stop u-boot during startup with spacebar, and then check "printenv" to see what is the value of "fdtfile".

If it is the wrong DT file, you can change it by overwritting "fdtfile" in /boot/armbianEnv.txt ...

 

Hi, thanks for your reply, I tried what you said and indeed I saw fdtfile=armada-388-clearfog.dtb.

I tried to correct within u-boot with "setenv fdtfile armada-388-clearfog-pro.dtb" and then complete the boot process,

but I still could not see the ASmedia SATA controller in dmesg or with lspci.

 

Also here is my /boot/armbianEnv.txt

verbosity=1
emmc_fix=off
eth1addr=00:50:43:25:fb:84
eth2addr=00:50:43:84:25:2f
eth3addr=00:50:43:0d:19:18
rootdev=UUID=495afdfb-5ff0-4e1a-9226-83ebf40fc2ec
rootfstype=ext4
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

you can see the weird characters in it, is it normal ?

Share this post


Link to post
Share on other sites

How can you set the ftdfile ?

 

I tried to put the line "ftdfile=armada-388-clearfog-pro.dtb" into the file "/boot/armbianEnv.txt", but it did not bring any improvements.

Share this post


Link to post
Share on other sites
14 minutes ago, deb2016 said:

How can you set the ftdfile ?

Be aware that "/boot/armbianEnv.txt" isn't yet loaded if you stop u-boot with <space>, it is loaded after, so doing "printenv" won't show the change yet.

Another workaround would be to copy "armada-388-clearfog-pro.dtb" into the other "armada-388-clearfog.dtb" file.

About the PCIe itself, I can't provide more detail since I don't own a ClearfogPro board ...

Share this post


Link to post
Share on other sites

I have now the correct fdtfile, I checked it with 'cat /proc/device-tree/model' which returns "SolidRun Clearfog Pro A1".

 

However, I still lack the PCIe sata controller, nothing happens when I plug a hard drive to the sata controller.

 

I doubt it is a hardware issue, it just happened when updating the system (apt-get ..)

 

In case I would like to reinstall, which is the appropriate armbian image ? next or default ?

 

My current image is "next"

Share this post


Link to post
Share on other sites
13 minutes ago, deb2016 said:

next or default ?

Personally, I would try NEXT, even if your current is already NEXT, because it maybe the fact that was an upgrade instead of fresh install.

BTW, did you look for any trace in "dmesg" that can give some clues ?

 

As I said, since I don't own a ClearfogPro, I can't help much more. Maybe some other will ...

Share this post


Link to post
Share on other sites

Hi,

 

Many thanks for your help.

 

Normally, I should see "SATA Controller" ... "ASMedia" in logs if it was detected.

 

I prefer to reinstall as it seems not easy to debug and too few people (at least for now) to help.

 

I will let you know if a fresh reinstall fixes the issue.

 

Regards

Share this post


Link to post
Share on other sites
0