• Content Count

  • Joined

  • Last visited

About deb2016

  • Rank
    Advanced Member

Recent Profile Visitors

686 profile views
  1. Hello, There are many leds on the clearfogpro that I would like to switch off. But /sys/class/leds only has "mmc0::". Is there a way to access other leds ? namely those of the ethernet ports ? Regards deb2016
  2. Wonderful, I had stopped working on this, lacking of hints, I wonder what was the issue. Thanks for pointing this to me. Regards
  3. 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 ?
  4. 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
  5. 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
  6. I have just tried the oldest armbian next, still same issue.
  7. 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.
  8. 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.
  9. 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 ?
  10. 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.
  11. 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 ?
  12. 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
  13. 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"
  14. 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.
  15. 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 ?