deb2016 Posted January 12, 2019 Share Posted January 12, 2019 (edited) 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 January 12, 2019 by deb2016 Link to comment Share on other sites More sharing options...
deb2016 Posted January 13, 2019 Author Share Posted January 13, 2019 No hints ? Link to comment Share on other sites More sharing options...
deb2016 Posted January 14, 2019 Author Share Posted January 14, 2019 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 Link to comment Share on other sites More sharing options...
martinayotte Posted January 15, 2019 Share Posted January 15, 2019 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 ... Link to comment Share on other sites More sharing options...
Igor Posted January 15, 2019 Share Posted January 15, 2019 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. Link to comment Share on other sites More sharing options...
deb2016 Posted January 16, 2019 Author Share Posted January 16, 2019 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 ? Link to comment Share on other sites More sharing options...
martinayotte Posted January 17, 2019 Share Posted January 17, 2019 16 hours ago, deb2016 said: you can see the weird characters in it, is it normal ? No ! It seems to be filesystem corruption ... Link to comment Share on other sites More sharing options...
deb2016 Posted January 18, 2019 Author Share Posted January 18, 2019 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. Link to comment Share on other sites More sharing options...
martinayotte Posted January 18, 2019 Share Posted January 18, 2019 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 ... Link to comment Share on other sites More sharing options...
deb2016 Posted January 18, 2019 Author Share Posted January 18, 2019 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" Link to comment Share on other sites More sharing options...
martinayotte Posted January 18, 2019 Share Posted January 18, 2019 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 ... Link to comment Share on other sites More sharing options...
deb2016 Posted January 19, 2019 Author Share Posted January 19, 2019 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 Link to comment Share on other sites More sharing options...
deb2016 Posted January 22, 2019 Author Share Posted January 22, 2019 Hi, I made a full reinstall on the SD card to begin with (avoiding the M2. sata card). It seems the armbian installation (NEXT) does not set the right fdtfile. But I can fix this on next reboot and I check that /proc/device-tree/model returns "clearfogpro A1". Even once having the right model, I still face the same issue : I have two PCIe cards (wifi and sata controller) which used to work well. The wifi one is still recognized but I cannot see the sata controller with lspci. The point is that if I remove the wifi card, the sata controller gets recognized on both slots. If I plug only the wifi card it gets also recognized, but only one one slot (the nearest most one to the SoM). That is quite strange. I do not think it is a hardware issue as both cards can be recognized by armbian at least in some configurations. Also, the u-boot process detects a link on both PCIe slots when both cards are plugged. I noticed that I have to flash one u-boot file (uboot.sata) to make the booting process work if I want to use the M2. sata card as root filesystem. Is it possible that the installation process flashes the wrong uboot file on the SD card ? As far as I see, uboot files do not depend on the hardware name itself, they depend on whether it is SD, MMC or SATA. Do you have any suggestions ? Link to comment Share on other sites More sharing options...
Igor Posted January 22, 2019 Share Posted January 22, 2019 Started with 5.59 Debian Stretch, updated to most recent, attached sfp, ath10 card and 4x marvell SATA. Everything looks fine: http://ix.io/1yXM U-boot: Spoiler Detected Device ID 6828 High speed PHY - Version: 2.0 Init Customer board board SerDes lanes topology details: | Lane # | Speed| Type | ------------------------------| | 0 | 3 | SATA0 | | 1 | 0 | SGMII1 | | 2 | 5 | PCIe1 | | 3 | 5 | USB3 HOST1 | | 4 | 5 | PCIe2 | | 5 | 0 | SGMII2 | ------------------------------- PCIe, Idx 2: detected no link High speed PHY - Ended Successfully DDR3 Training Sequence - Ver TIP-1.39.0 DDR3 Training Sequence - Switching XBAR Window to FastPath Window DDR3 Training Sequence - Ended Successfully BootROM: Image checksum verification PASSED __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) | |_ \___/ |____/ \___/ \___/ \__| ** LOADER ** U-Boot 2013.01 (Aug 22 2018 - 14:06:29) 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 *** Warning - bad CRC, using default environment PCI-e 1 (IF 0 - bus 0) Root Complex Interface, Detected Link X1, GEN 2.0 PCI-e 2 (IF 1 - bus 1) Root Complex Interface, Detected Link X1, GEN 1.1 USB2.0 0: Host Mode USB3.0 0: Host Mode USB3.0 1: Host Mode Map: Code: 0x3fed6000:0x3ff98098 BSS: 0x3ffefd54 Stack: 0x3f9c5f20 Heap: 0x3f9c6000:0x3fed6000 U-Boot Environment: 0x000f0000:0x00100000 (MMC) Board configuration detected: Net: | port | Interface | PHY address | |--------|-----------|--------------| | egiga0 | RGMII | 0x00 | | egiga1 | SGMII | In-Band | | egiga2 | SGMII | In-Band | egiga0 [PRIME], egiga1, egiga2 Hit any key to stop autoboot: 0 Trying to boot from MMC 1604 bytes read in 13 ms (120.1 KiB/s) ## Executing script at 03000000 Boot script loaded from mmc 221 bytes read in 11 ms (19.5 KiB/s) 20484 bytes read in 37 ms (540 KiB/s) 4712014 bytes read in 265 ms (17 MiB/s) 5457936 bytes read in 309 ms (16.8 MiB/s) ## Loading init Ramdisk from Legacy Image at 02880000 ... Image Name: uInitrd Created: 2019-01-22 16:29:01 UTC Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 4711950 Bytes = 4.5 MiB Load Address: 00000000 Entry Point: 00000000 ## Flattened Device Tree blob at 02040000 Booting using the fdt blob at 0x02040000 Using Device Tree in place at 02040000, end 02048003 Skipping Device Tree update ('fdt_skip_update' = yes) Limit DDR size at 3GB due to power of 2 requirement of Address decoding Starting kernel ... Uncompressing Linux... done, booting the kernel. Loading, please wait... Link to comment Share on other sites More sharing options...
deb2016 Posted January 28, 2019 Author Share Posted January 28, 2019 on - Version: 1.0.0 Detected Device ID 6828 High speed PHY - Version: 2.0 Init Customer board board SerDes lanes topology details: | Lane # | Speed| Type | ------------------------------| | 0 | 3 | SATA0 | | 1 | 0 | SGMII1 | | 2 | 5 | PCIe1 | | 3 | 5 | USB3 HOST1 | | 4 | 5 | PCIe2 | | 5 | 0 | SGMII2 | ------------------------------- PCIe, Idx 2: detected no link High speed PHY - Ended Successfully DDR3 Training Sequence - Ver TIP-1.39.0 DDR3 Training Sequence - Switching XBAR Window to FastPath Window DDR3 Training Sequence - Ended Successfully BootROM: Image checksum verification PASSED __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) | |_ \___/ |____/ \___/ \___/ \__| ** LOADER ** U-Boot 2013.01 (Oct 26 2018 - 16:58:49) 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 *** Warning - bad CRC, using default environment PCI-e 1 (IF 0 - bus 0) Root Complex Interface, Detected Link X1, GEN 2.0 PCI-e 2 (IF 1 - bus 1) Root Complex Interface, Detected Link X1, GEN 1.1 USB2.0 0: Host Mode USB3.0 0: Host Mode USB3.0 1: Host Mode Map: Code: 0x3fed6000:0x3ff98098 BSS: 0x3ffefd54 Stack: 0x3f9c5f20 Heap: 0x3f9c6000:0x3fed6000 U-Boot Environment: 0x000f0000:0x00100000 (MMC) Board configuration detected: Net: | port | Interface | PHY address | |--------|-----------|--------------| | egiga0 | RGMII | 0x00 | | egiga1 | SGMII | In-Band | | egiga2 | SGMII | In-Band | egiga0 [PRIME], egiga1, egiga2 Hit any key to stop autoboot: 0 Marvell>> Marvell>> Marvell>> Marvell>> Marvell>> Marvell>> boot Trying to boot from MMC 1979 bytes read in 15 ms (127.9 KiB/s) ## Executing script at 03000000 Boot script loaded from mmc 257 bytes read in 12 ms (20.5 KiB/s) 20512 bytes read in 36 ms (555.7 KiB/s) 4712239 bytes read in 259 ms (17.4 MiB/s) 5457936 bytes read in 299 ms (17.4 MiB/s) ## Loading init Ramdisk from Legacy Image at 02880000 ... Image Name: uInitrd Created: 2019-01-28 21:40:43 UTC Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 4712175 Bytes = 4.5 MiB Load Address: 00000000 Entry Point: 00000000 ## Flattened Device Tree blob at 02040000 Booting using the fdt blob at 0x02040000 Using Device Tree in place at 02040000, end 0204801f Skipping Device Tree update ('fdt_skip_update' = yes) Limit DDR size at 3GB due to power of 2 requirement of Address decoding Starting kernel ... Hello, here is above the boot process, after a fresh install. (debian stretch next) Still the same issue : 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 cannot see the sata controller. The strange point is that, if I remove the network controller (nearest PCIE to som), the sata controller gets recognized and I can see it with lspci. So is like my clearfogpro was able to handle only one PCIe at a time. Link to comment Share on other sites More sharing options...
Igor Posted January 29, 2019 Share Posted January 29, 2019 7 hours ago, deb2016 said: So is like my clearfogpro was able to handle only one PCIe at a time. Strange issue. Topology, which could be related to this, looks alright. I can only suspect some hardware defects. Have you tried some Solidrun stock builds? Link to comment Share on other sites More sharing options...
deb2016 Posted January 29, 2019 Author Share Posted January 29, 2019 Hi, Thanks for your reply, I will try the solidrun image. Another point I noticed is that the temperature reported by armbian is very rapidly 70°C (without running anything), but in the clearfogpro specifications I read that it works from 0 to 70°C. Is it a normal temperature ? Link to comment Share on other sites More sharing options...
deb2016 Posted February 1, 2019 Author Share Posted February 1, 2019 Hi again, I made further tests. I recall I have a clearfogpro which runs armbian next latest, the issue is that I cannot make both mPCIe cards recognized (there is one wifi card and one sata controller). There is also a M2 ssd card, but it is not used at present, the system is installed on a sd card. I checked at each time with /proc/device-tree/model that I have the clearfog pro. If I plug the sata controller alone on the left slot (the one on the left hand side when you faces all ethernet ports), it is recognized (lspci shows it and attached hard drives are mountable) If, in addition, I plug the wifi card on the right slot, nothing is recognized at all, not even the sata controller (left slot) which was recognized before. Then, if I switch : I plug alone the sata controller ont the right slot, it is then recognized as earlier. When I plug the wifi card on the remaining slot (left one), the sata controller is no more recognized but I can see the wifi card : iwconfig finds it but I do not know if it works well. At last, when I plug the wifi card alone on either left or right slot, it gets recognized. I do not know how to interpret these tests. Both cards are recognized well when they are plugged alone. Trouble arises when I plug a second one. Link to comment Share on other sites More sharing options...
Heisath Posted February 2, 2019 Share Posted February 2, 2019 Hey, which SATA and WiFi Cards are you using exactly? What driver are you using for the wifi card (if it needed to be installed additionally?) I remember that I had a similiar issue, a while back, which was caused by the wifi card... After trying a different one it was solved. Maybe just some combination of cards does not work. Btw. your uboot seems to correctly detect the link: On 1/28/2019 at 11:17 PM, deb2016 said: [...] PCI-e 1 (IF 0 - bus 0) Root Complex Interface, Detected Link X1, GEN 2.0 PCI-e 2 (IF 1 - bus 1) Root Complex Interface, Detected Link X1, GEN 1.1 USB2.0 0: Host Mode USB3.0 0: Host Mode USB3.0 1: Host Mode [...] Will try later with mine (currently only one inserted) and edit this post with the results. EDIT: I am using a Qualcomm Atheros Wifi Card, the Compex WLE600VXhttp://www.compex.com.sg/product/wle600vx/ (inserted in the slot next to the som / cpu) and a cheap Delock 95233 mPCIe to SATA adapter https://www.delock.com/produkte/G_95233/merkmale.html Running current armbian next for clearfogpro. (fresh update, also updated uboot) Both are working fine - and the uboot detections looks very similiar to yours. Most interesting in the beginning, where it first prints "PCIe, Idx 2: detected no link" followed by "PCI-e 2 (IF 1 - bus 1) Root Complex Interface, Detected Link X1, GEN 1.1" a few lines later. This looks exactly the same as in your boot up. I attached the uboot, linux boot up and lspci output. Spoiler BootROM - 1.73 Booting from AHCI Probing HBA- 0 port 0 SATA device found General initialization - Version: 1.0.0 Detected Device ID 6828 High speed PHY - Version: 2.0 Init Customer board board SerDes lanes topology details: | Lane # | Speed| Type | ------------------------------| | 0 | 3 | SATA0 | | 1 | 0 | SGMII1 | | 2 | 5 | PCIe1 | | 3 | 5 | USB3 HOST1 | | 4 | 5 | PCIe2 | | 5 | 0 | SGMII2 | ------------------------------- :** Link is Gen1, check the EP capability PCIe, Idx 1: Link upgraded to Gen2 based on client cpabilities PCIe, Idx 2: detected no link High speed PHY - Ended Successfully DDR3 Training Sequence - Ver TIP-1.39.0 DDR3 Training Sequence - Switching XBAR Window to FastPath Window DDR3 Training Sequence - Ended Successfully BootROM: Image checksum verification PASSED __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) | |_ \___/ |____/ \___/ \___/ \__| ** LOADER ** U-Boot 2013.01 (Jan 28 2019 - 10:56:52) 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 Card did not respond to voltage select! MMC init failed Using default environment PCI-e 1 (IF 0 - bus 0) Root Complex Interface, Detected Link X1, GEN 2.0 PCI-e 2 (IF 1 - bus 1) Root Complex Interface, Detected Link X1, GEN 1.1 USB2.0 0: Host Mode USB3.0 0: Host Mode USB3.0 1: Host Mode Map: Code: 0x3fed8000:0x3ff97950 BSS: 0x3ffef4f4 Stack: 0x3f9c7f20 Heap: 0x3f9c8000:0x3fed8000 U-Boot Environment: 0x000f0000:0x00100000 Board configuration detected: Net: | port | Interface | PHY address | |--------|-----------|--------------| | egiga0 | RGMII | 0x00 | | egiga1 | SGMII | In-Band | | egiga2 | SGMII | In-Band | egiga0 [PRIME], egiga1, egiga2 Hit any key to stop autoboot: 0 Marvell>> Marvell>> boot Trying to boot from SATA AHCI init for unit0 Target spinup took 0 ms. SATA link 1 timeout. Error: SCSI Controller(s) 1B4B:9215 1B4B:9235 not found scanning bus for devices... Device 0: (0:0) Vendor: ATA Prod.: LITEON LST-32S9G Rev: ZS21 Type: Hard Disk Capacity: 30533.8 MB = 29.8 GB (62533296 x 512) Found 1 device(s). 1604 bytes read in 48 ms (32.2 KiB/s) ## Executing script at 03000000 Boot script loaded from scsi 221 bytes read in 41 ms (4.9 KiB/s) 20484 bytes read in 127 ms (157.2 KiB/s) 4702873 bytes read in 157 ms (28.6 MiB/s) 5458304 bytes read in 190 ms (27.4 MiB/s) ## Loading init Ramdisk from Legacy Image at 02880000 ... Image Name: uInitrd Created: 2019-01-31 12:40:17 UTC Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 4702809 Bytes = 4.5 MiB Load Address: 00000000 Entry Point: 00000000 ## Flattened Device Tree blob at 02040000 Booting using the fdt blob at 0x02040000 Using Device Tree in place at 02040000, end 02048003 Skipping Device Tree update ('fdt_skip_update' = yes) Limit DDR size at 3GB due to power of 2 requirement of Address decoding Starting kernel ... Uncompressing Linux... done, booting the kernel. [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.14.96-mvebu (root@armbian.com) (gcc version 7.2.1 20171011 (Linaro GCC 7.2-2017.11)) #32 SMP Tue Jan 29 06:24:23 CET 2019 [ 0.000000] CPU: ARMv7 Processor [414fc091] revision 1 (ARMv7), cr=50c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] OF: fdt: Machine model: SolidRun Clearfog A1 [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] cma: Reserved 16 MiB at 0x3f000000 [ 0.000000] random: get_random_bytes called from start_kernel+0x87/0x354 with crng_init=0 [ 0.000000] percpu: Embedded 16 pages/cpu @ef6c6000 s33868 r8192 d23476 u65536 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 260416 [ 0.000000] Kernel command line: console=ttyS0,115200 root=UUID=c4b74654-b71b-44c9-9303-e7f9ca15211d rootwait rootfstype=ext4 ubootdev=scsi scandelay loglevel=7 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u [ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes) [ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] allocated 1048576 bytes of page_ext [ 0.000000] Memory: 1006472K/1048576K available (6144K kernel code, 325K rwdata, 1760K rodata, 1024K init, 242K bss, 25720K reserved, 16384K cma-reserved, 245760K highmem) [ 0.000000] Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB) [ 0.000000] vmalloc : 0xf0800000 - 0xff800000 ( 240 MB) [ 0.000000] lowmem : 0xc0000000 - 0xf0000000 ( 768 MB) [ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) [ 0.000000] modules : 0xbf800000 - 0xbfe00000 ( 6 MB) [ 0.000000] .text : 0xc0008000 - 0xc0700000 (7136 kB) [ 0.000000] .init : 0xc0900000 - 0xc0a00000 (1024 kB) [ 0.000000] .data : 0xc0a00000 - 0xc0a517b8 ( 326 kB) [ 0.000000] .bss : 0xc0a59de0 - 0xc0a96958 ( 243 kB) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1 [ 0.000000] Hierarchical RCU implementation. [ 0.000000] RCU event tracing is enabled. [ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2. [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2 [ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16 [ 0.000000] L2C-310 enabling early BRESP for Cortex-A9 [ 0.000000] L2C-310 full line of zeros enabled for Cortex-A9 [ 0.000000] L2C-310 D prefetch enabled, offset 1 lines [ 0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled [ 0.000000] L2C-310 Coherent cache controller enabled, 16 ways, 1024 kB [ 0.000000] L2C-310 Coherent: CACHE_ID 0x410054c9, AUX_CTRL 0x56070001 [ 0.000000] Switching to timer-based delay loop, resolution 40ns [ 0.000002] sched_clock: 32 bits at 25MHz, resolution 40ns, wraps every 85899345900ns [ 0.000009] clocksource: armada_370_xp_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 76450417870 ns [ 0.000198] Console: colour dummy device 80x30 [ 0.000212] Calibrating delay loop (skipped), value calculated using timer frequency.. 50.00 BogoMIPS (lpj=100000) [ 0.000218] pid_max: default: 32768 minimum: 301 [ 0.000346] Security Framework initialized [ 0.000352] AppArmor: AppArmor disabled by boot time parameter [ 0.000384] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.000389] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.000709] CPU: Testing write buffer coherency: ok [ 0.000720] CPU0: Spectre v2: using BPIALL workaround [ 0.000834] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.000954] Setting up static identity map for 0x100000 - 0x100054 [ 0.001032] mvebu-soc-id: MVEBU SoC ID=0x6828, Rev=0x4 [ 0.001115] mvebu-pmsu: Initializing Power Management Service Unit [ 0.001163] Hierarchical SRCU implementation. [ 0.001349] smp: Bringing up secondary CPUs ... [ 0.001474] Booting CPU 1 [ 0.001610] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 [ 0.001612] CPU1: Spectre v2: using BPIALL workaround [ 0.001656] smp: Brought up 1 node, 2 CPUs [ 0.001660] SMP: Total of 2 processors activated (100.00 BogoMIPS). [ 0.001663] CPU: All CPU(s) started in SVC mode. [ 0.002145] devtmpfs: initialized [ 0.003976] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4 [ 0.004053] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns [ 0.004060] futex hash table entries: 512 (order: 3, 32768 bytes) [ 0.004484] xor: measuring software checksum speed [ 0.043882] arm4regs : 2534.000 MB/sec [ 0.083881] 8regs : 1947.000 MB/sec [ 0.123881] 32regs : 1805.000 MB/sec [ 0.163880] neon : 1842.000 MB/sec [ 0.163883] xor: using function: arm4regs (2534.000 MB/sec) [ 0.163889] pinctrl core: initialized pinctrl subsystem [ 0.164196] NET: Registered protocol family 16 [ 0.165073] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.165498] cpuidle: using governor ladder [ 0.165607] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers. [ 0.165611] hw-breakpoint: maximum watchpoint size is 4 bytes. [ 0.165731] mvebu-pmsu: CPU hotplug support is currently broken on Armada 38x: disabling [ 0.165738] mvebu-pmsu: CPU idle is currently broken on Armada 38x: disabling [ 0.240055] raid6: int32x1 gen() 262 MB/s [ 0.307959] raid6: int32x1 xor() 267 MB/s [ 0.375906] raid6: int32x2 gen() 351 MB/s [ 0.443939] raid6: int32x2 xor() 325 MB/s [ 0.512033] raid6: int32x4 gen() 393 MB/s [ 0.579963] raid6: int32x4 xor() 323 MB/s [ 0.647885] raid6: int32x8 gen() 422 MB/s [ 0.715949] raid6: int32x8 xor() 322 MB/s [ 0.783896] raid6: neonx1 gen() 1212 MB/s [ 0.851893] raid6: neonx1 xor() 1150 MB/s [ 0.919907] raid6: neonx2 gen() 1296 MB/s [ 0.987893] raid6: neonx2 xor() 1347 MB/s [ 1.055925] raid6: neonx4 gen() 1350 MB/s [ 1.123889] raid6: neonx4 xor() 1377 MB/s [ 1.191885] raid6: neonx8 gen() 1073 MB/s [ 1.259886] raid6: neonx8 xor() 1041 MB/s [ 1.259889] raid6: using algorithm neonx4 gen() 1350 MB/s [ 1.259892] raid6: .... xor() 1377 MB/s, rmw enabled [ 1.259895] raid6: using neon recovery algorithm [ 1.260154] vgaarb: loaded [ 1.260297] SCSI subsystem initialized [ 1.260429] usbcore: registered new interface driver usbfs [ 1.260447] usbcore: registered new interface driver hub [ 1.260468] usbcore: registered new device driver usb [ 1.260844] clocksource: Switched to clocksource armada_370_xp_clocksource [ 1.260919] VFS: Disk quotas dquot_6.6.0 [ 1.260952] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 1.261009] FS-Cache: Loaded [ 1.263402] NET: Registered protocol family 2 [ 1.263639] TCP established hash table entries: 8192 (order: 3, 32768 bytes) [ 1.263680] TCP bind hash table entries: 8192 (order: 4, 65536 bytes) [ 1.263742] TCP: Hash tables configured (established 8192 bind 8192) [ 1.263789] UDP hash table entries: 512 (order: 2, 16384 bytes) [ 1.263812] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes) [ 1.263901] NET: Registered protocol family 1 [ 1.264045] RPC: Registered named UNIX socket transport module. [ 1.264050] RPC: Registered udp transport module. [ 1.264053] RPC: Registered tcp transport module. [ 1.264056] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 1.264141] Unpacking initramfs... [ 1.399575] Freeing initrd memory: 4596K [ 1.399842] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available [ 1.400290] audit: initializing netlink subsys (disabled) [ 1.400398] audit: type=2000 audit(1.396:1): state=initialized audit_enabled=0 res=1 [ 1.400554] workingset: timestamp_bits=14 max_order=18 bucket_order=4 [ 1.403154] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 1.403374] FS-Cache: Netfs 'nfs' registered for caching [ 1.403545] NFS: Registering the id_resolver key type [ 1.403556] Key type id_resolver registered [ 1.403559] Key type id_legacy registered [ 1.403566] nfs4filelayout_init: NFSv4 File Layout Driver Registering... [ 1.403645] fuse init (API version 7.26) [ 1.403902] aufs 4.14-20171218 [ 1.406042] bounce: pool size: 64 pages [ 1.406071] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249) [ 1.406118] io scheduler noop registered [ 1.406122] io scheduler deadline registered [ 1.406201] io scheduler cfq registered (default) [ 1.406205] io scheduler mq-deadline registered [ 1.406208] io scheduler kyber registered [ 1.406267] io scheduler bfq registered [ 1.406897] armada-38x-pinctrl f1018000.pinctrl: registered pinctrl driver [ 1.408191] mv_xor f1060800.xor: Marvell shared XOR driver [ 1.445311] mv_xor f1060800.xor: Marvell XOR (Descriptor Mode): ( xor cpy intr ) [ 1.445406] mv_xor f1060900.xor: Marvell shared XOR driver [ 1.473308] mv_xor f1060900.xor: Marvell XOR (Descriptor Mode): ( xor cpy intr ) [ 1.487530] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 1.488366] console [ttyS0] disabled [ 1.508431] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 22, base_baud = 15625000) is a 16550A [ 2.359372] console [ttyS0] enabled [ 2.383305] f1012100.serial: ttyS1 at MMIO 0xf1012100 (irq = 23, base_baud = 15625000) is a 16550A [ 2.394871] loop: module loaded [ 2.398398] ahci-mvebu f10a8000.sata: AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl platform mode [ 2.407476] ahci-mvebu f10a8000.sata: flags: 64bit ncq sntf led only pmp fbs pio slum part sxs [ 2.416697] scsi host0: ahci-mvebu [ 2.420260] scsi host1: ahci-mvebu [ 2.423763] ata1: SATA max UDMA/133 mmio [mem 0xf10a8000-0xf10a9fff] port 0x100 irq 44 [ 2.431706] ata2: SATA max UDMA/133 mmio [mem 0xf10a8000-0xf10a9fff] port 0x180 irq 44 [ 2.439769] ahci-mvebu f10e0000.sata: AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl platform mode [ 2.448849] ahci-mvebu f10e0000.sata: flags: 64bit ncq sntf led only pmp fbs pio slum part sxs [ 2.458081] scsi host2: ahci-mvebu [ 2.461634] scsi host3: ahci-mvebu [ 2.465119] ata3: SATA max UDMA/133 mmio [mem 0xf10e0000-0xf10e1fff] port 0x100 irq 45 [ 2.473060] ata4: SATA max UDMA/133 mmio [mem 0xf10e0000-0xf10e1fff] port 0x180 irq 45 [ 2.481703] libphy: Fixed MDIO Bus: probed [ 2.486063] libphy: orion_mdio_bus: probed [ 2.493039] mvneta_bm f10c8000.bm: Buffer Manager for network controller enabled [ 2.501837] mvneta f1070000.ethernet eth0: Using device tree mac address 00:50:43:25:fb:84 [ 2.511063] mvneta f1030000.ethernet eth1: Using device tree mac address 00:50:43:84:25:2f [ 2.520276] mvneta f1034000.ethernet eth2: Using device tree mac address 00:50:43:0d:19:18 [ 2.528732] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 2.535279] ehci-pci: EHCI PCI platform driver [ 2.539758] ehci-orion: EHCI orion driver [ 2.543855] orion-ehci f1058000.usb: EHCI Host Controller [ 2.549278] orion-ehci f1058000.usb: new USB bus registered, assigned bus number 1 [ 2.556942] orion-ehci f1058000.usb: irq 40, io mem 0xf1058000 [ 2.580847] orion-ehci f1058000.usb: USB 2.0 started, EHCI 1.00 [ 2.586876] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 2.593687] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.600929] usb usb1: Product: EHCI Host Controller [ 2.605820] usb usb1: Manufacturer: Linux 4.14.96-mvebu ehci_hcd [ 2.611843] usb usb1: SerialNumber: f1058000.usb [ 2.616686] hub 1-0:1.0: USB hub found [ 2.620466] hub 1-0:1.0: 1 port detected [ 2.624781] xhci-hcd f10f0000.usb3: xHCI Host Controller [ 2.630125] xhci-hcd f10f0000.usb3: new USB bus registered, assigned bus number 2 [ 2.637745] xhci-hcd f10f0000.usb3: hcc params 0x0a000990 hci version 0x100 quirks 0x0000000000010010 [ 2.647015] xhci-hcd f10f0000.usb3: irq 47, io mem 0xf10f0000 [ 2.652859] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 [ 2.659667] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.666909] usb usb2: Product: xHCI Host Controller [ 2.671799] usb usb2: Manufacturer: Linux 4.14.96-mvebu xhci-hcd [ 2.677820] usb usb2: SerialNumber: f10f0000.usb3 [ 2.682722] hub 2-0:1.0: USB hub found [ 2.686503] hub 2-0:1.0: 1 port detected [ 2.690571] xhci-hcd f10f0000.usb3: xHCI Host Controller [ 2.695920] xhci-hcd f10f0000.usb3: new USB bus registered, assigned bus number 3 [ 2.703436] xhci-hcd f10f0000.usb3: Host supports USB 3.0 SuperSpeed [ 2.709929] usb usb3: We don't know the algorithms for LPM for this host, disabling LPM. [ 2.718113] usb usb3: New USB device found, idVendor=1d6b, idProduct=0003 [ 2.724924] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.732165] usb usb3: Product: xHCI Host Controller [ 2.737056] usb usb3: Manufacturer: Linux 4.14.96-mvebu xhci-hcd [ 2.743077] usb usb3: SerialNumber: f10f0000.usb3 [ 2.747978] hub 3-0:1.0: USB hub found [ 2.751759] hub 3-0:1.0: 1 port detected [ 2.755721] ata2: SATA link down (SStatus 0 SControl 300) [ 2.755894] xhci-hcd f10f8000.usb3: xHCI Host Controller [ 2.766472] xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 4 [ 2.774096] xhci-hcd f10f8000.usb3: hcc params 0x0a000990 hci version 0x100 quirks 0x0000000000010010 [ 2.783360] xhci-hcd f10f8000.usb3: irq 48, io mem 0xf10f8000 [ 2.789198] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002 [ 2.796014] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.801067] ata4: SATA link down (SStatus 0 SControl 300) [ 2.803255] usb usb4: Product: xHCI Host Controller [ 2.808682] ata3: SATA link down (SStatus 0 SControl 300) [ 2.813553] usb usb4: Manufacturer: Linux 4.14.96-mvebu xhci-hcd [ 2.824982] usb usb4: SerialNumber: f10f8000.usb3 [ 2.829878] hub 4-0:1.0: USB hub found [ 2.833658] hub 4-0:1.0: 1 port detected [ 2.837718] xhci-hcd f10f8000.usb3: xHCI Host Controller [ 2.843055] xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 5 [ 2.850570] xhci-hcd f10f8000.usb3: Host supports USB 3.0 SuperSpeed [ 2.857071] usb usb5: We don't know the algorithms for LPM for this host, disabling LPM. [ 2.865241] usb usb5: New USB device found, idVendor=1d6b, idProduct=0003 [ 2.872048] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.879290] usb usb5: Product: xHCI Host Controller [ 2.884179] usb usb5: Manufacturer: Linux 4.14.96-mvebu xhci-hcd [ 2.890201] usb usb5: SerialNumber: f10f8000.usb3 [ 2.895083] hub 5-0:1.0: USB hub found [ 2.898862] hub 5-0:1.0: 1 port detected [ 2.903029] usbcore: registered new interface driver usb-storage [ 2.909153] mousedev: PS/2 mouse device common for all mice [ 2.915206] armada38x-rtc f10a3800.rtc: rtc core: registered f10a3800.rtc as rtc0 [ 2.922813] i2c /dev entries driver [ 2.924850] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 2.926591] pca953x 0-0020: 0-0020 supply vcc not found, using dummy regulator [ 2.939789] ata1.00: ATA-9: LITEON LST-32S9G-11 SATA 32GB, ZS2110B, max UDMA/133 [ 2.942108] GPIO line 496 (pcie1.0-clkreq) hogged as input [ 2.947207] ata1.00: 62533296 sectors, multi 1: LBA48 NCQ (depth 31/32) [ 2.959604] ata1.00: configured for UDMA/133 [ 2.959619] GPIO line 499 (pcie1.0-w-disable) hogged as output/low [ 2.964103] scsi 0:0:0:0: Direct-Access ATA LITEON LST-32S9G 10B PQ: 0 ANSI: 5 [ 2.970274] GPIO line 501 (usb3-current-limit) hogged as input [ 2.978561] sd 0:0:0:0: [sda] 62533296 512-byte logical blocks: (32.0 GB/29.8 GiB) [ 2.984314] GPIO line 502 (usb3-power) hogged as output/high [ 2.991659] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 2.997575] GPIO line 507 (m.2 devslp) hogged as output/low [ 3.002685] sd 0:0:0:0: [sda] Write Protect is off [ 3.008411] GPIO line 500 (pcie2.0-clkreq) hogged as input [ 3.013101] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 3.018800] GPIO line 503 (pcie2.0-w-disable) hogged as output/low [ 3.033812] sda: sda1 [ 3.036584] sd 0:0:0:0: [sda] Attached SCSI removable disk [ 3.046793] (NULL device *): hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info(). [ 3.059242] orion_wdt: Initial timeout 171 sec, nowayout [ 3.064845] device-mapper: ioctl: 4.37.0-ioctl (2017-09-20) initialised: dm-devel@redhat.com [ 3.073598] cpu cpu1: opp_list_debug_create_link: Failed to create link [ 3.080236] cpu cpu1: _add_opp_dev: Failed to register opp debugfs (-12) [ 3.087077] sdhci: Secure Digital Host Controller Interface driver [ 3.093286] sdhci: Copyright(c) Pierre Ossman [ 3.097928] sdhci-pxav3 f10d8000.sdhci: Got CD GPIO [ 3.151001] mmc0: SDHCI controller on f10d8000.sdhci [f10d8000.sdhci] using ADMA [ 3.158587] sdhci-pltfm: SDHCI platform and OF driver helper [ 3.164464] ledtrig-cpu: registered to indicate activity on CPUs [ 3.170516] hidraw: raw HID events driver (C) Jiri Kosina [ 3.176012] usbcore: registered new interface driver usbhid [ 3.181605] usbhid: USB HID core driver [ 3.186937] ipip: IPv4 and MPLS over IPv4 tunneling driver [ 3.192631] Initializing XFRM netlink socket [ 3.197339] NET: Registered protocol family 10 [ 3.213361] Segment Routing with IPv6 [ 3.217086] NET: Registered protocol family 17 [ 3.221563] NET: Registered protocol family 15 [ 3.226037] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this. [ 3.239046] 8021q: 802.1Q VLAN Support v1.8 [ 3.243257] Key type dns_resolver registered [ 3.247643] ThumbEE CPU extension supported. [ 3.251929] Registering SWP/SWPB emulation handler [ 3.257009] registered taskstats version 1 [ 3.262515] zswap: default zpool zbud not available [ 3.267423] zswap: pool creation failed [ 3.275466] Btrfs loaded, crc32c=crc32c-generic [ 3.284978] Key type encrypted registered [ 3.290017] mvebu-pcie soc:pcie: /soc/pcie/pcie@2,0: reset gpio is active low [ 3.308890] mvebu-pcie soc:pcie: /soc/pcie/pcie@3,0: reset gpio is active low [ 3.317226] pcie1.0: reset completed in 0us [ 3.321613] pcie2.0: reset completed in 0us [ 3.325891] mvebu-pcie soc:pcie: PCI host bridge to bus 0000:00 [ 3.331833] pci_bus 0000:00: root bus resource [io 0x1000-0xfffff] [ 3.338117] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xe7ffffff] [ 3.345011] pci_bus 0000:00: root bus resource [bus 00-ff] [ 3.350694] PCI: bus0: Fast back to back transfers disabled [ 3.356286] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring [ 3.364312] pci 0000:00:03.0: bridge configuration invalid ([bus 00-00]), reconfiguring [ 3.372549] PCI: bus1: Fast back to back transfers disabled [ 3.378368] PCI: bus2: Fast back to back transfers disabled [ 3.383974] pci 0000:00:02.0: BAR 8: assigned [mem 0xe0000000-0xe00fffff] [ 3.390782] pci 0000:00:03.0: BAR 8: assigned [mem 0xe0200000-0xe04fffff] [ 3.397589] pci 0000:00:02.0: BAR 7: assigned [io 0x10000-0x10fff] [ 3.403875] pci 0000:01:00.0: BAR 6: assigned [mem 0xe0000000-0xe000ffff pref] [ 3.411120] pci 0000:01:00.0: BAR 5: assigned [mem 0xe0010000-0xe00101ff] [ 3.417929] pci 0000:01:00.0: BAR 4: assigned [io 0x10000-0x1001f] [ 3.424214] pci 0000:01:00.0: BAR 0: assigned [io 0x10020-0x10027] [ 3.430499] pci 0000:01:00.0: BAR 2: assigned [io 0x10028-0x1002f] [ 3.436785] pci 0000:01:00.0: BAR 1: assigned [io 0x10030-0x10033] [ 3.443069] pci 0000:01:00.0: BAR 3: assigned [io 0x10034-0x10037] [ 3.449355] pci 0000:00:02.0: PCI bridge to [bus 01] [ 3.454332] pci 0000:00:02.0: bridge window [io 0x10000-0x10fff] [ 3.460616] pci 0000:00:02.0: bridge window [mem 0xe0000000-0xe00fffff] [ 3.467424] pci 0000:02:00.0: BAR 0: assigned [mem 0xe0200000-0xe03fffff 64bit] [ 3.474759] pci 0000:02:00.0: BAR 6: assigned [mem 0xe0400000-0xe040ffff pref] [ 3.482000] pci 0000:00:03.0: PCI bridge to [bus 02] [ 3.486979] pci 0000:00:03.0: bridge window [mem 0xe0200000-0xe04fffff] [ 3.493927] pci 0000:00:02.0: enabling device (0140 -> 0143) [ 3.499614] ahci 0000:01:00.0: enabling device (0140 -> 0143) [ 3.505451] ahci 0000:01:00.0: SSS flag set, parallel bus scan disabled [ 3.512109] ahci 0000:01:00.0: AHCI 0001.0200 32 slots 2 ports 6 Gbps 0x3 impl SATA mode [ 3.520223] ahci 0000:01:00.0: flags: 64bit ncq sntf stag led clo pmp pio slum part ccc sxs [ 3.529241] scsi host4: ahci [ 3.532264] scsi host5: ahci [ 3.535227] ata5: SATA max UDMA/133 abar m512@0xe0010000 port 0xe0010100 irq 54 [ 3.542568] ata6: SATA max UDMA/133 abar m512@0xe0010000 port 0xe0010180 irq 54 [ 3.550433] input: gpio-keys as /devices/platform/gpio-keys/input/input0 [ 4.037097] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 4.045788] ata5.00: ATA-10: ST4000DM004-2CV104, 0001, max UDMA/133 [ 4.052074] ata5.00: 7814037168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA [ 4.059509] random: fast init done [ 4.065255] ata5.00: configured for UDMA/133 [ 4.069920] scsi 4:0:0:0: Direct-Access ATA ST4000DM004-2CV1 0001 PQ: 0 ANSI: 5 [ 4.078530] sd 4:0:0:0: [sdb] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB) [ 4.078549] sd 4:0:0:0: Attached scsi generic sg1 type 0 [ 4.086313] sd 4:0:0:0: [sdb] 4096-byte physical blocks [ 4.100875] sd 4:0:0:0: [sdb] Write Protect is off [ 4.105767] sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 4.175736] sdb: sdb1 [ 4.178810] sd 4:0:0:0: [sdb] Attached SCSI disk [ 4.573100] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 4.581739] ata6.00: ATA-10: ST4000DM004-2CV104, 0001, max UDMA/133 [ 4.588025] ata6.00: 7814037168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA [ 4.597756] ata6.00: configured for UDMA/133 [ 4.602360] scsi 5:0:0:0: Direct-Access ATA ST4000DM004-2CV1 0001 PQ: 0 ANSI: 5 [ 4.610950] sd 5:0:0:0: [sdc] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB) [ 4.610969] sd 5:0:0:0: Attached scsi generic sg2 type 0 [ 4.618731] sd 5:0:0:0: [sdc] 4096-byte physical blocks [ 4.632872] sd 5:0:0:0: [sdc] Write Protect is off [ 4.637757] sd 5:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 4.708413] sdc: sdc1 [ 4.711453] sd 5:0:0:0: [sdc] Attached SCSI disk [ 4.717008] Freeing unused kernel memory: 1024K Loading, please wait... starting version 232 [ 4.754494] random: systemd-udevd: uninitialized urandom read (16 bytes read) [ 4.757927] random: udevadm: uninitialized urandom read (16 bytes read) [ 4.762063] random: systemd-udevd: uninitialized urandom read (16 bytes read) [ 4.943365] libphy: SFP I2C Bus: probed [ 4.959914] mvneta f1034000.ethernet eth2: Link is Down [ 4.986015] mv88e6085 f1072004.mdio-mii:04: switch 0x1760 detected: Marvell 88E6176, revision 1 [ 5.221781] libphy: mv88e6xxx SMI: probed [ 5.225849] DSA: switch 0 0 parsed [ 5.229273] DSA: tree 0 parsed [ 6.478234] Marvell 88E1540 mv88e6xxx-0:00: attached PHY driver [Marvell 88E1540] (mii_bus:phy_addr=mv88e6xxx-0:00, irq=POLL) [ 6.580042] Marvell 88E1540 mv88e6xxx-0:01: attached PHY driver [Marvell 88E1540] (mii_bus:phy_addr=mv88e6xxx-0:01, irq=POLL) [ 6.675575] Marvell 88E1540 mv88e6xxx-0:02: attached PHY driver [Marvell 88E1540] (mii_bus:phy_addr=mv88e6xxx-0:02, irq=POLL) [ 6.776783] Marvell 88E1540 mv88e6xxx-0:03: attached PHY driver [Marvell 88E1540] (mii_bus:phy_addr=mv88e6xxx-0:03, irq=POLL) [ 6.878075] Marvell 88E1540 mv88e6xxx-0:04: attached PHY driver [Marvell 88E1540] (mii_bus:phy_addr=mv88e6xxx-0:04, irq=POLL) [ 6.902275] Generic PHY fixed-0:01: attached PHY driver [Generic PHY] (mii_bus:phy_addr=fixed-0:01, irq=POLL) Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Will now check root file system ... fsck from util-linux 2.29.2 [/sbin/fsck.ext4 (1) -- /dev/sda1] fsck.ext4 -a -C0 /dev/sda1 /dev/sda1: clean, 118605/1804992 files, 1520978/7791488 blocks done. [ 7.288686] EXT4-fs (sda1): mounted filesystem with writeback data mode. Opts: (null) done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... done. [ 7.463798] systemd[1]: System time before build time, advancing clock. [ 7.477366] ip_tables: (C) 2000-2006 Netfilter Core Team [ 7.492980] systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN) [ 7.514965] systemd[1]: Detected architecture arm. Welcome to Debian GNU/Linux 9 (stretch)! [ 7.535353] systemd[1]: Set hostname to <clearfogpro>. [ 7.733192] systemd[1]: NetworkManager-wait-online.service: Cannot add dependency job, ignoring: Unit NetworkManager-wait-online.service is masked. [ 7.751367] systemd[1]: NetworkManager.service: Cannot add dependency job, ignoring: Unit NetworkManager.service is masked. [ 7.762953] systemd[1]: ModemManager.service: Cannot add dependency job, ignoring: Unit ModemManager.service is masked. [ 7.773862] systemd[1]: strongswan.service: Cannot add dependency job, ignoring: Unit strongswan.service is masked. [ 7.784594] systemd[1]: netfilter-persistent.service: Cannot add dependency job, ignoring: Unit netfilter-persistent.service is masked. [ 7.801989] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. [ OK ] Set up automount Arbitrary Executab…rmats File System Automount Point. [ 7.832578] systemd[1]: Listening on fsck to fsckd communication Socket. [ OK ] Listening on fsck to fsckd communication Socket. [ OK ] Listening on udev Kernel Socket. [ OK ] Reached target Remote File Systems. [ OK ] Listening on Journal Socket. [ OK ] Started Dispatch Password Requests to Console Directory Watch. [ OK ] Listening on Journal Audit Socket. [ OK ] Created slice System Slice. Starting Remount Root and Kernel File Systems... Mounting POSIX Message Queue File System... [ 7.980626] EXT4-fs (sda1): re-mounted. Opts: commit=600,errors=remount-ro [ OK ] Created slice system-serial\x2dgetty.slice. [ OK ] Started Forward Password Requests to Wall Directory Watch. [ OK ] Created slice User and Session Slice. [ OK ] Reached target Slices. Starting Nameserver information manager... [ OK ] Listening on /dev/initctl Compatibility Named Pipe. [ OK ] Reached target Paths. [ OK ] Listening on Journal Socket (/dev/log). Starting Set the console keyboard layout... Mounting Debug File System... [ OK ] Created slice system-openvpn.slice. Starting Load Kernel Modules... [ OK ] Reached target Encrypted Volumes. Starting Restore / save the current clock... [ OK ] Listening on Syslog Socket. Starting Journal Service... [ OK ] Listening on udev Control Socket. [ OK ] Created slice system-systemd\x2dfsck.slice. Starting Create list of required st…ce nodes for the current kernel... [ OK ] Mounted Debug File System. [ OK ] Mounted POSIX Message Queue File System. [ OK ] Started Remount Root and Kernel File Systems. [ OK ] Started Set the console keyboard layout. [ OK ] Started Load Kernel Modules. [ OK ] Started Restore / save the current clock. [ OK ] Started Create list of required sta…vice nodes for the current kernel. [ OK ] Started Nameserver information manager. [ OK ] Started Journal Service. Starting Create Static Device Nodes in /dev... Starting Apply Kernel Variables... Mounting FUSE Control File System... Starting Load/Save Random Seed... Starting udev Coldplug all Devices... Starting Flush Journal to Persistent Storage... Activating swap /var/swap... [ OK ] Mounted FUSE Control File System. [ OK ] Started Create Static Device Nodes in /dev. [ OK ] Started Apply Kernel Variables. [ OK ] Started Load/Save Random Seed. [ 8.633289] systemd-journald[238]: Received request to flush runtime journal from PID 1 Starting udev Kernel Device Manager... [ OK ] Reached target Local File Systems (Pre). Mounting /tmp... [ OK ] Started Flush Journal to Persistent Storage. [ OK ] Mounted /tmp. [ OK ] Started udev Kernel Device Manager. [ 8.889529] Adding 2047996k swap on /var/swap. Priority:-2 extents:18 across:2981884k SSFS [ OK ] Activated swap /var/swap. [ OK ] Reached target Swap. [ OK ] Started udev Coldplug all Devices. [ OK ] Found device /dev/ttyS0. [ 9.155457] marvell-cesa f1090000.crypto: CESA device successfully registered [ OK ] Found device /sys/subsystem/net/devices/eth0. [ 9.330070] pci 0000:00:03.0: enabling device (0140 -> 0142) [ 9.335791] ath10k_pci 0000:02:00.0: enabling device (0140 -> 0142) [ 9.342375] ath10k_pci 0000:02:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [ OK ] Found device ST4000DM004-2CV104 1. [ OK ] Found device ST4000DM004-2CV104 1. Starting File System Check on /dev/sdc1... Starting File System Check on /dev/sdb1... [ OK ] Started File System Check Daemon to report status. [ 9.704898] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:02:00.0.bin failed with error -2 [ 9.715658] ath10k_pci 0000:02:00.0: Falling back to user helper [ 9.798047] random: crng init done [ 9.801481] random: 7 urandom warning(s) missed due to ratelimiting [ 9.870332] br0: port 1(eth0) entered blocking state [ 9.875332] br0: port 1(eth0) entered disabled state [ 9.880446] device eth0 entered promiscuous mode [ 10.029488] mvneta f1070000.ethernet eth0: PHY [f1072004.mdio-mii:00] driver [Marvell 88E1510] [ OK ] Started File System Check on /dev/sdc1. [ 10.052976] mvneta f1070000.ethernet eth0: configuring for phy/rgmii-id link mode [ 10.067184] br0: port 2(lan1) entered blocking state [ 10.072194] br0: port 2(lan1) entered disabled state [ 10.088419] device lan1 entered promiscuous mode [ 10.093066] device eth1 entered promiscuous mode [ 10.198014] br0: port 3(lan2) entered blocking state [ 10.203024] br0: port 3(lan2) entered disabled state [ 10.238085] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/cal-pci-0000:02:00.0.bin failed with error -2 [ 10.248485] ath10k_pci 0000:02:00.0: Falling back to user helper [ 10.259629] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/firmware-6.bin failed with error -2 [ 10.270391] ath10k_pci 0000:02:00.0: Falling back to user helper [ 10.284037] device lan2 entered promiscuous mode [ OK 10.298093] ath10k_pci 0000:02:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043222ff sub 0000:0000 m] Listening on [ 10.308267] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs 0 testmode 0 Load/Save RF Kil[ 10.308915] ath10k_pci 0000:02:00.0: firmware ver 10.2.4.70.54 api 5 features no-p2p,raw-mode,mfp crc32 9d340dd9 l Switch Status /dev/rfkill Watch. Mounting /mnt/hd-secondary... [ 10.351652] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/board-2.bin failed with error -2 [ 10.362140] ath10k_pci 0000:02:00.0: Falling back to user helper [ 10.388948] ath10k_pci 0000:02:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08 [ 10.399733] br0: port 4(lan3) entered blocking state [ 10.404723] br0: port 4(lan3) entered disabled state [ 10.428584] device lan3 entered promiscuous mode [ 10.590093] br0: port 5(lan4) entered blocking state [ 10.595084] br0: port 5(lan4) entered disabled state [ 10.626143] device lan4 entered promiscuous mode [ 10.673675] br0: port 6(lan5) entered blocking state [ 10.678669] br0: port 6(lan5) entered disabled state [ 10.708601] device lan5 entered promiscuous mode [ 10.757577] br0: port 7(lan6) entered blocking state [ 10.762589] br0: port 7(lan6) entered disabled state [ 10.774691] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null) [ OK ] Mounted /mnt/hd-secondary. [ 10.792317] device lan6 entered promiscuous mode [ 10.826422] br0: port 1(eth0) entered blocking state [ 10.831415] br0: port 1(eth0) entered forwarding state [ 10.836625] IPv6: ADDRCONF(NETDEV_UP): br0: link is not ready [ OK ] Started File System Check on /dev/sdb1.) Mounting /mnt/hd-primary... [ 10.908957] br0: port 1(eth0) entered disabled state [ 11.325608] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) [ OK ] Mounted /mnt/hd-primary. [ OK ] Reached target Local File Systems. [ 11.364582] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) Starting Armbian ZRAM config... Starting Raise network interfaces... Starting Set console font and keymap... [ OK ] Started ifup for eth0. Starting Create Volatile Files and Directories... Starting Enable support for additional executable binary formats... [ OK ] Started Set console font and keymap. Mounting Arbitrary Executable File Formats File System... [ OK ] Started Create Volatile Files and Directories. [ OK ] Mounted Arbitrary Executable File Formats File System. [ OK ] Started Enable support for additional executable binary formats. [ OK ] Started Entropy daemon using the HAVEGE algorithm. Starting Update UTMP about System Boot/Shutdown... [ OK ] Reached target System Time Synchronized. [ 11.614467] ip6_tables: (C) 2000-2006 Netfilter Core Team [ 11.620245] 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 [ OK ] Started Update UTMP about System Boot/Shutdown. [ 11.723048] ath10k_pci 0000:02:00.0 wlp2s0: renamed from wlan0 Starting Load/Save RF Kill Switch Status... [ 11.785057] zram: Added device: zram0 [ OK ] Started Load/Save RF Kill Switch Status. [ 11.799178] zram: Added device: zram1 [ 11.807851] zram: Added device: zram2 [ 11.814568] zram: Added device: zram3 [ 11.877093] zram1: detected capacity change from 0 to 263290880 [ 11.926079] Adding 257116k swap on /dev/zram1. Priority:5 extents:1 across:257116k SSFS [ 11.945116] zram2: detected capacity change from 0 to 263290880 [ 11.987528] Adding 257116k swap on /dev/zram2. Priority:5 extents:1 across:257116k SSFS [ 12.097003] zram0: detected capacity change from 0 to 52428800 [ OK ] Started Armbian ZRAM config. Starting Armbian memory supported logging... [ 12.345102] EXT4-fs (zram0): mounted filesystem without journal. Opts: discard [ 12.681896] mvneta f1030000.ethernet eth1: configuring for fixed/sgmii link mode [ 12.689406] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready [ 12.696013] mvneta f1030000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off [ 12.708255] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [ 14.405334] mvneta f1070000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx [ 14.413514] br0: port 1(eth0) entered blocking state [ 14.418535] br0: port 1(eth0) entered forwarding state [ 14.423950] IPv6: ADDRCONF(NETDEV_CHANGE): br0: link becomes ready [ 14.444242] mv88e6085 f1072004.mdio-mii:04 lan1: Link is Down [ OK ] Started Raise network interfaces. [ OK ] Reached target Network. [ OK ] Reached target Network is Online. [ OK ] Started Armbian memory supported logging. [ OK ] Reached target System Initialization. Starting Armbian hardware optimization... [ 14.924811] mv88e6085 f1072004.mdio-mii:04 lan2: Link is Down [ OK ] Started Run certbot twice daily. [ OK ] Started Daily Cleanup of Temporary Directories. [ OK ] Listening on D-Bus System Message Bus Socket. [ OK ] Reached target Sockets. Starting Armbian hardware monitoring... [ OK ] Started Daily apt download activities. [ OK ] Started Daily apt upgrade and clean activities. [ OK ] Started Clean PHP session files every 30 mins. [ 15.052026] mv88e6085 f1072004.mdio-mii:04 lan3: Link is Down [ OK ] Reached target Timers. [ OK ] Started Armbian hardware optimization. [ OK ] Started Armbian hardware monitoring. [ OK ] Reached target Basic System. Starting OpenVPN connection to server... Starting LSB: Update dynamic domain name service entries... [ OK ] Started Regular background program processing daemon. [ 15.181109] mv88e6085 f1072004.mdio-mii:04 lan4: Link is Down Starting OpenBSD Secure Shell server... [ OK ] Started Self Monitoring and Reporting Technology (SMART) Daemon. Starting OpenVPN service... Starting Login Service... Starting System Logging Service... Starting LSB: Start/Stop WIDE DHCPv6 client... [ 15.292922] br0: port 7(lan6) entered blocking state Starting control[ 15.298086] br0: port 7(lan6) entered forwarding state s configuration [ 15.305886] tun: Universal TUN/TAP device driver, 1.6 of serial ports.[ 15.308313] mv88e6085 f1072004.mdio-mii:04 lan6: Link is Up - 1Gbps/Full - flow control off .. [ 15.334234] mv88e6085 f1072004.mdio-mii:04 lan5: Link is Down Starting LSB: Start/stop sysstat's sadc... Starting LSB: disk temperature monitoring daemon... Starting LSB: minidlna server... Starting LSB: pptpd... [ OK ] Started D-Bus System Message Bus. Starting LSB: network connection manager... Starting dnsmasq - A lightweight DHCP and caching DNS server... Starting MariaDB 10.1.37 database server... [ OK ] Started Unattended Upgrades Shutdown. Starting Restore /etc/resolv.conf i…fore the ppp link was shut down... Starting Samba NMB Daemon... Starting /etc/rc.local Compatibility... Starting LSB: Starts LIRC daemon.... Starting LSB: Load kernel modules needed to enable cpufreq scaling... Starting LSB: Start NTP daemon... Starting controls configuration of serial ports... [ OK ] Started System Logging Service. [ OK ] Started OpenVPN connection to server. [ OK ] Started OpenVPN service. [ OK ] Started LSB: pptpd. [ OK ] Started LSB: network connection manager. [ OK ] Started Restore /etc/resolv.conf if…before the ppp link was shut down. [ OK ] Started /etc/rc.local Compatibility. [ OK ] Started OpenBSD Secure Shell server. [ OK ] Started LSB: Start/Stop WIDE DHCPv6 client. [ OK ] Started controls configuration of serial ports. [ OK ] Started LSB: Start/stop sysstat's sadc. [ OK ] Started LSB: disk temperature monitoring daemon. [ OK ] Started Samba NMB Daemon. [ OK ] Started LSB: Starts LIRC daemon.. [ OK ] Started LSB: Start NTP daemon. [ OK ] Started controls configuration of serial ports. [ OK ] Started Login Service. Starting Samba SMB Daemon... [ OK ] Created slice system-getty.slice. Starting Permit User Sessions... [ OK ] Started LSB: Load kernel modules needed to enable cpufreq scaling. [ OK ] Started Permit User Sessions. [ OK ] Started Serial Getty on ttyS0. [ OK ] Started Getty on tty1. [ OK ] Reached target Login Prompts. Starting LSB: set CPUFreq kernel parameters... [ OK ] Started LSB: set CPUFreq kernel parameters. Starting LSB: Set sysfs variables from /etc/sysfs.conf... [ OK ] Started LSB: Update dynamic domain name service entries. [ OK ] Started LSB: Set sysfs variables from /etc/sysfs.conf. [ OK ] Started dnsmasq - A lightweight DHCP and caching DNS server. [ OK ] Reached target Host and Network Name Lookups. Starting LSB: Starts ProFTPD daemon... Starting LSB: powerful, efficient, …d scalable Mail Transport Agent... Starting The Apache HTTP Server... [ OK ] Started LSB: minidlna server. [ OK ] Started LSB: powerful, efficient, and scalable Mail Transport Agent. [ 17.603441] nr_pdflush_threads exported in /proc is scheduled for removal [ OK ] Started LSB: Starts ProFTPD daemon. [ OK ] Started Samba SMB Daemon. [ OK ] Started The Apache HTTP Server. [ OK ] Started MariaDB 10.1.37 database server. [ OK ] Reached target Multi-User System. [ OK ] Reached target Graphical Interface. Starting Update UTMP about System Runlevel Changes... [ OK ] Started Update UTMP about System Runlevel Changes. Debian GNU/Linux 9 clearfogpro ttyS0 clearfogpro login: root Password: Last login: Sat Feb 2 10:07:21 CET 2019 on ttyS0 ____ _ __ ____ / ___| | ___ __ _ _ __ / _| ___ __ _ | _ \ _ __ ___ | | | |/ _ \/ _` | '__| |_ / _ \ / _` | | |_) | '__/ _ \ | |___| | __/ (_| | | | _| (_) | (_| | | __/| | | (_) | \____|_|\___|\__,_|_| |_| \___/ \__, | |_| |_| \___/ |___/ Welcome to ARMBIAN 5.73 stable Debian GNU/Linux 9 (stretch) 4.14.96-mvebu 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 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 Greetings, count-doku Link to comment Share on other sites More sharing options...
deb2016 Posted February 3, 2019 Author Share Posted February 3, 2019 Hi, Thanks for your reply. I made further tests without the wifi card, with two sata controller, the one that I already had and a new one (listed on the armbian clearfogpro page, the one with four sata ports). When I plug both sata controller (one on each PCIe slot), none of them are detected, whatever the order. I checked again, I use the correct model (/proc/device-tree/model). I begin to believe it is a hardware defect, something that does not show up in logs, what else could it be if everything works well for you with the same configuration (?) I believe I have no other alternative than buy another clearfogpro and another PCIe wifi card. I will try again with the new sata controller and the new wifi card. If I have the same trouble, I'll buy another clearfogpro, what else can I do ? I wonder. So strange, it was working perfectly well before upgrading armbian. Link to comment Share on other sites More sharing options...
Heisath Posted February 3, 2019 Share Posted February 3, 2019 Did you try going back to the old armbian version? You could use git to checkout some old commit and build your own image from there. But Igor can possibly describe this better. Might also take the old 5.59 Version from the archive:https://dl.armbian.com/clearfogpro/archive/ Armbian_5.59_Clearfogpro_Debian_stretch_next_4.14.66.7z from 22.08.2018 If everything is working again when using 5.59 we could go from there and check what changed (if anything). If it is not working in the old version I'd say some of your hardware is broken. Maybe try to return / exchange the clearfogpro. Link to comment Share on other sites More sharing options...
deb2016 Posted February 3, 2019 Author Share Posted February 3, 2019 I have just tried the oldest armbian next, still same issue. Link to comment Share on other sites More sharing options...
deb2016 Posted February 12, 2019 Author Share Posted February 12, 2019 Hello, I bought another clearfogpro, thinking hardware was broken. I also bought a mPCIe wifi card and sata controller following the ones which are listed on the clearfogpro armbian page. I cannot believe it : I still face the very same issue : the wifi card is correctly detected but not the sata controller. At least, I am sure now that it is not a hardware issue (all is new). I will keep testing. When installing the system on the SD card, I always notice that the device-tree model is not clearfogpro, as if the installation process was not detecting well the right hardware. In this case, is there a specific process to reinstall for the correct hardware (uboot , initrd) ? Thanks for your attention Regards Link to comment Share on other sites More sharing options...
deb2016 Posted February 19, 2019 Author Share Posted February 19, 2019 On 1/29/2019 at 7:07 AM, Igor said: Strange issue. Topology, which could be related to this, looks alright. I can only suspect some hardware defects. Have you tried some Solidrun stock builds? Hi, I have tried with the latest Solidrun stock build : I first installed their uboot for sata on the M2. SSD card : dd if=file.kwb of=/dev/sda bs=512 seek=1 Then, I installed the system : dd if=solidrun_image.img of=/dev/sda bs=4M I switched the boot order to sata and powered on. At the end of the installation, I can indeed see both PCIe cards with lspci, but the strange part is that nothing happens if I plug a hard drive on the sata controller : no device appears and no activity in logs. But the hardware does react when I plug the hard drive : leds of the sata controller lights up (and light down when I unplug) So, this is a slight improvement with solidrun stock image. All the hardware is brand new, so it is very unlikely to be a hardware defect. Could it be related to insufficient power ? I will try again with another power adapter. I remember that you have tried on our side with our clearfogpro, could you give me details about how you proceeded exactly ? Regards Link to comment Share on other sites More sharing options...
martinayotte Posted February 19, 2019 Share Posted February 19, 2019 2 hours ago, deb2016 said: I first installed their uboot for sata on the M2. SSD card : dd if=file.kwb of=/dev/sda bs=512 seek=1 Then, I installed the system : dd if=solidrun_image.img of=/dev/sda bs=4M Those steps are not logical since the second "dd" will overwrite the first one ... Link to comment Share on other sites More sharing options...
deb2016 Posted February 19, 2019 Author Share Posted February 19, 2019 Hi, Thanks for your reply. If I perform the "dd"'s in the other order, will the second one (u-boot) still damage the solidrun image ? Link to comment Share on other sites More sharing options...
Heisath Posted July 18, 2019 Share Posted July 18, 2019 @Igor This is not a problem on deb2016 side. This is a general problem. You posted some armbian-monitor link above, of your setup: On 1/22/2019 at 5:34 PM, Igor said: Started with 5.59 Debian Stretch, updated to most recent, attached sfp, ath10 card and 4x marvell SATA. Everything looks fine: http://ix.io/1yXM Did you read the results? Because if you check your 'lspci' output, you would realise that your 4x marvell sata card is not detected in linux: ### 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 So this is the same problem @deb2016 is facing. In my opinion this is a big problem (maybe even with the drivers for 88se9215 (which is probably your sata card)) and we should try to fix this together with current work on mvebu. See also github issue. https://github.com/armbian/build/issues/1426 1 Link to comment Share on other sites More sharing options...
Heisath Posted July 31, 2019 Share Posted July 31, 2019 @deb2016 just to wind up on this issue. This is somehow fixed in the new Armbian 5.91 (default). See the download page or armbian docs for more info. Link to comment Share on other sites More sharing options...
deb2016 Posted August 1, 2019 Author Share Posted August 1, 2019 Wonderful, I had stopped working on this, lacking of hints, I wonder what was the issue. Thanks for pointing this to me. Regards Link to comment Share on other sites More sharing options...
Recommended Posts