tom_i

Members
  • Content count

    24
  • Joined

  • Last visited

About tom_i

  • Rank
    Member

Recent Profile Visitors

251 profile views
  1. My problem with no boot with SSD and HDD I've solved with renaming rootdev root and bootargs root with /dev/sdb1 Of course, I've updated U-Boot from Armbian
  2. I think there is no possiblity like this, because it hasn't ATX power supply Anyway, I'm shutting it down via sudo halt and it unmount drives and turn off HDD, but when I'm listening it carefully HDD make some low noise. So maybe EspressoBin can't turn HDD completely off.
  3. Ahaa, so I should use these: setenv initrd_addr 0x1100000 setenv image_name boot/Image setenv load_script 'if test -e mmc 0:1 boot/boot.scr; then echo \"... booting from SD\";setenv boot_interface mmc;else echo \"... booting from USB/SATA\";usb start;setenv boot_interface usb;fi;if test -e \$boot_interface 0:1 boot/boot.scr;then ext4load \$boot_interface 0:1 0x00800000 boot/boot.scr; source; fi' setenv bootcmd 'run get_images; run set_bootargs; run load_script;booti \$kernel_addr \$ramfs_addr \$fdt_addr' But configure it for using SSD. So it should look like this: setenv boot_interface scsi setenv rootdev "/dev/sda1" setenv root root=/dev/sda1 rw setenv initrd_addr 0x1100000 setenv image_name boot/Image setenv load_script 'if test -e mmc 0:1 boot/boot.scr; then echo \"... booting from SD\";setenv boot_interface mmc;else echo \"... booting from USB/SATA\";usb start;setenv boot_interface usb;fi;if test -e \$boot_interface 0:1 boot/boot.scr;then ext4load \$boot_interface 0:1 0x00800000 boot/boot.scr; source; fi' setenv bootcmd 'run get_images; run set_bootargs; run load_script;booti \$kernel_addr \$ramfs_addr \$fdt_addr' And what about this parameters? setenv bootcmd 'scsi scan; scsi dev 0; ext4load scsi 0:1 $kernel_addr $image_name;ext4load scsi 0:1 $initrd_addr $initrd_image; ext4load scsi 0:1 $fdt_addr $fdt_name;setenv bootargs $console root=$rootdev rw rootwait; booti $kernel_addr $initrd_addr $fdt_addr' Something should be there too right?
  4. Yes of course, there are right UUIDs for SSD / and for HDD which is currently commented. Actual situation when both are connected: (initramfs) blkid /dev/sdb1: UUID="0f9d4af6-98bf-4e76-bf12-3f85f706f468" TYPE="ext4" PARTUUID="669c2e15-01" /dev/sda1: UUID="5d577507-8c81-4be3-ba3d-5776baf857d1" TYPE="ext4" PARTUUID="aa448862-01" From /etc/fstab: root@espressobin:~# cat /etc/fstab # <file system> <mount point> <type> <options> <dump> <pass> tmpfs /tmp tmpfs defaults,nosuid 0 0 /var/swap none swap sw 0 0 #UUID=05f654b5-c16f-49ed-86c1-6474b04e92da /media/mmcboot ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro,x-gvfs-hide 0 1 #/media/mmcboot/boot /boot none bind 0 0 UUID=0f9d4af6-98bf-4e76-bf12-3f85f706f468 / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro,x-gvfs-hide 0 1 #UUID=5d577507-8c81-4be3-ba3d-5776baf857d1 /media/multimedia ext4 auto,rw,user 0 1 As you can see, that SSD is configured to mount to "/" but it doesn't :-/ armbianEnv.tct: root@espressobin:~# cat /boot/armbianEnv.txt verbosity=1 emmc_fix=off ... rootdev=UUID=0f9d4af6-98bf-4e76-bf12-3f85f706f468 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u
  5. Setup "rootdev" for using UUID doesn't help. But I think, that u-boot is ok. It boots to armbian, but after Armbian checks disks it changes names. So HDD is /dev/sda1 and SSD is /dev/sdb1.
  6. Oh.. ok thank you, I'll try it today... Anyway you meant my u-boot isn't in a good shape? Should I remove some stuff from there?
  7. Loading, please wait... starting version 238 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.31.1 [/sbin/fsck.ext4 (1) -- /dev/sda1] fsck.ext4 -a -C0 /dev/sda1 /dev/sda1: recovering journal /dev/sda1: clean, 31481/61054976 files, 208644350/244190390 blocks done. [ 8.717541] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... mount: No such file or directory mount: invalid option -- done. mount: No such file or directory run-init: opening console: No such file or directory Target filesystem doesn't have requested /sbin/init. run-init: opening console: No such file or directory run-init: opening console: No such file or directory run-init: opening console: No such file or directory run-init: opening console: No such file or directory run-init: opening console: No such file or directory No init found. Try passing init= bootarg. (initramfs)
  8. @Igor - I used to use SD card for running EspressoBin, but it was slow, so I decided to buy SSD and use HDD for "home" data. I've used "nand-sata-install" to copy data from SD card to SSD. @umiddelb - "/boot/armbianEnv.txt" had that UUID saved, with it no boot if the normal HDD is connected. And then I've tried to setup "root=UUID=0f9d4af6-12cd-3e33-b234-3385f706f468", "saveenv" but that parameter isn't saved There is still "root=root=/dev/sda1"
  9. Hi all, so I've bought this SATA miniPCI card for to have 2 or more HDD (SSD) together, like some NAS or so. Booting with SSD works just when I connect SSD to SATA connector on my EspressoBin. If I connect it to miniPCI card, it doesn't boot from u-boot. So if I connect SSD to SATA connector on EspressoBin, it boots, but problem is when I connect HDD to the miniPCI slot. Booting is ok till Armbian decided that /dev/sda1 is HDD and /dev/sdb1 is SSD which is wrong. Is there any hack for u-boot to change booting option from that miniPCI card? My actual ENV from u-boot: Marvell>> printenv baudrate=115200 boot=interface scsi boot_interface=scsi bootargs=console=ttyMV0,115200 earlycon=ar3700_uart,0xd0012000 root=/dev/sda1 rw rootwait bootcmd=scsi scan; scsi dev 0; ext4load scsi 0:1 $kernel_addr $image_name;ext4load scsi 0:1 $initrd_addr $initrd_image; ext4load scsi 0:1 $fdt_addr $fdt_name_a;ext4load scsi 0:1 $fdt_addr $fdt_name_b;setenv bootargs $console root=$rootdev rw rootwait; booti $kernel_addr $initrd_addr $fdt_addr bootdelay=2 console=console=ttyMV0,115200 earlycon=ar3700_uart,0xd0012000 eth1addr=00:51:82:11:22:01 eth2addr=00:51:82:11:22:02 eth3addr=00:51:82:11:22:03 ethact=neta@30000 ethaddr=F0:AD:XX:XX:XX:XX ethprime=eth0 fdt_addr=0x4f00000 fdt_high=0xffffffffffffffff fdt_name=boot/dtb/marvell/armada-3720-community.dtb fdt_name_a=boot/dtb/marvell/armada-3720-community.dtb fdt_name_b=boot/dtb/marvell/armada-3720-espressobin.dtb fdtcontroladdr=7f7182d8 gatewayip=10.4.50.254 get_images=tftpboot $kernel_addr $image_name; tftpboot $fdt_addr $fdt_name; run get_ramfs get_ramfs=if test "${ramfs_name}" != "-"; then setenv ramfs_addr 0x8000000; tftpboot $ramfs_addr $ramfs_name; else setenv ramfs_addr -;fi hostname=marvell image_name=boot/Image initrd_addr=0x1100000 initrd_image=boot/uInitrd initrd_size=0x2000000 ipaddr=0.0.0.0 kernel_addr=0x5000000 loadaddr=0x5000000 netdev=eth0 netmask=255.255.255.0 ramfs_addr=0x8000000 ramfs_name=- root=root=/dev/sda1 rw rootdev=/dev/sda1 rootfstype=ext4 rootpath=/srv/nfs/ serverip=0.0.0.0 set_bootargs=setenv bootargs $console $root ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:none nfsroot=$serverip:$rootpath $extra_params stderr=serial@12000 stdin=serial@12000 stdout=serial@12000 verbosity=1 Environment size: 1772/65532 bytes
  10. Looking forward to rebuild your systems @ebin-dev
  11. Works gr8 now, EspressoBin 2GB is on 1200MHz up, down on 300MHz. I've switched to Debian Testing and seems it works without problem Thx @ebin-dev & @umiddelb
  12. Argh.. you mean to set some setenv right? Because that flash remove all the environments. I was stupid yesterday evening. I should know it :-/ Ok thx, I'll do it today.
  13. @ebin-dev ok, I've burned Debian image to my testing SD card, run `bubt flash-image-2g-1200_750_boot_sd_and_usb.bin spi usb` command, that shows me success. Then I turn it off and put that SDHC card to slot and turn on. Unfortunately it shows me this: Marvell>> SVC_REV:0 NOTICE: Booting Trusted Firmware NOTICE: BL1: v1.3(release):devel-17.08.1:627667b NOTICE: BL1: Built : 14:40:39, Oct 4 2NOTICE: BL2: v1.3(release):devel-17.08.1:627667b NOTICE: BL2: Built : 14:40:39, Oct 4 2017 NNOTICE: BL31: v1.3(release):devel-17.08.1:627667b NOTICE: BL31: U-Boot 2017.03-armada-17.10.1-g440395a (Sep 25 2017 - 15:43:51 +0200) Model: Marvell Armada 3720 Community Board ESPRESSOBin CPU @ 1200 [MHz] L2 @ 800 [MHz] TClock @ 200 [MHz] DDR @ 750 [MHz] DRAM: 2 GiB U-Boot DT blob at : 000000007f7182d8 Comphy-0: USB3 5 Gbps Comphy-1: PEX0 2.5 Gbps Comphy-2: SATA0 6 Gbps SATA link 0 timeout. AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl SATA mode flags: ncq led only pmp fbss pio slum part sxs PCIE-0: Link down MMC: sdhci@d0000: 0 SF: Detected w25q32dw with page size 256 Bytes, erase size 4 KiB, total 4 MiB *** Warning - bad CRC, using default environment Net: eth0: neta@30000 [PRIME] Hit any key to stop autoboot: 0 *** ERROR: `serverip' not set *** ERROR: `serverip' not set Bad Linux ARM64 Image magic! I've tried to boot it from USB3.0 too, but same error appears.
  14. @ebin-dev do you have some newer images? Or am I using last one?
  15. OK, so today my EspressoBin shutdown its WIFI connection. So I had to investigate it, but no luck. https://pastebin.com/eWiWGuEt I've tried to rmmod/modprobe all necesary modules for marvell wifi "mwifiiex, mwifiex_pcie, cfg80211" 00:00.0 Ethernet controller: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac Wireless But no wlan0 in ifconfig After boot too. Looks that this wifi minipci card is broken. Any idea how to check, that it's ok? Thank you very much.