aprayoga

Members
  • Content Count

    25
  • Joined

  • Last visited

About aprayoga

  • Rank
    Member

Profile Information

  • Gender
    Male
  • Location
    Singapore

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I don't think you need to modify the Makefile, you can set LOCALVERSION environment variable before compiling. You could try something like this when you invoke the make LOCALVERSION=-sunxi64 make modules Here is how Armbian compile the kernel: https://github.com/armbian/build/blob/master/lib/compilation.sh#L367-L371
  2. A few months ago I enabled some USB-Serial converter driver on the kernel and test it. I used an USB hub then hotplug several USB-Serial (PL2303, FT232, FT2232, CH340G, CH341A, CP2101, CP2102), all detected correctly. According to your log, it seems something wrong with the USB Host controller driver, could you try with other USB device? maybe USB Flash drive
  3. Between middle-to end of November 2019, Armbian change the version and branch naming. Version from something like 5.91 become something like 19.11.x, if i'm not mistaken Year.Month, like Ubuntu versioning. Then the branch name, DEFAULT become LEGACY NEXT become CURRENT To upgrade to new version, use armbian-config. sudo apt-get update sudo apt-get -y upgrade sudo armbian-config Select System > Other, to switch to other kernel Confirm the action And after some process, you will be presented by list of kernels Select linux-image-current-mvebu. The system will install the new kernel and automatically reboot. Confirm the kernel installed correctly and Armbian changed to new branch CURRENT by executing, uname -a grep "BRANCH" /etc/armbian-release
  4. Good to hear you got it working. I tried the instructions first on my system and did not encounter such error. Could you share your u-boot version? I test on fresh Armbian_19.11.3_Helios4_buster_current_4.19.84.img 1. I don't encounter such error when accessing the system from Windows using PuTTY or thru serial console UPDATE: i tried to SSH from my Ubuntu machine (got id_ID locale), indeed there are perl warning regarding locale but armbian-config is still usable to generate the locale, no need to manually edit file. After the locale generated by armbian-config, no more perl locale warning. 2. Confirmed 3. Confirmed. cat: /sys/devices/system/cpu/cpufreq/policy0/scaling_available_frequencies: No such file or directory cat: /sys/devices/system/cpu/cpufreq/policy0/scaling_available_governors: No such file or directory /usr/lib/armbian-config/jobs.sh: line 1075: Error: Expected at least 5 tokens for --menu, have 4. Use --help to list options. / 1000: syntax error in expression (error token is ": Expected at least 5 tokens for --menu, have 4. Use --help to list options. / 1000") The path is not exist, even though the driver is compiled. I will need to investigate further. --- I also tried using fresh Armbian 5.91 then upgraded to Armbian 19.11.3, but strangely i don't see the System - CPU menu. 4. As mentioned on @sirleon link, apparently Buster make use nftables by default and on our kernel is not enabled. You could try to switch to iptables-legacy version. CONFIG_NF_TABLES=m CONFIG_NF_TABLES_SET=m # CONFIG_NF_TABLES_INET is not set # CONFIG_NF_TABLES_NETDEV is not set # CONFIG_NF_TABLES_IPV4 is not set # CONFIG_NF_TABLES_ARP is not set # CONFIG_NF_TABLES_IPV6 is not set # CONFIG_NF_TABLES_BRIDGE is not set meanwhile, i will try to enable those modules and test. @Igor, could you take a look whether armbian-config issues also occur on other board?
  5. Hi @sirleon, the tutorial is intended for moving the rootfs to USB thumb drive and due to spi_workaround it does not work with SATA seamlessly but you almost there.. I suggest to move the rootfs to drive that connected to SATA0 (most likely /dev/sda), because there is known issue that u-boot failed to recognized SATA device other than on SATA0. To boot from SATA you need to: 1. Move the rootfs with sata-nand-install while spi_workaround is disabled, and reboot. The system will boot from SD card. 2. Unmount /boot and copy over boot files from /media/mmcboot/boot to /boot umount /boot cp -rf /media/mmcboot/boot/* /boot/ 3. Edit /etc/fstab and remove/comment 2 lines that have mount point to /media/mmcboot and /boot. 4. Reboot the system and cancel u-boot auto boot. 5. Run following commands on u-boot prompt to add sata boot and reboot setenv boot_targets "usb0 scsi0 mmc0 pxe dhcp" setenv bootcmd_scsi0 'devnum=0; run scsi_boot' saveenv You could reorder the boot order on boot_targets variable. On above command, it would tried to boot from USB and if failed try SATA/SCSI and so on.
  6. @jimbolaya, I know it's quite late, ch341 driver would be included on next release. Refer to commit 14a0a54. @smith69085, we have updated the wiki page how to use the GPIO for button. You can take a look on https://wiki.kobol.io/gpio/#use-gpio-with-device-tree-overlay But currently the base dtb (armada-388-helios4.dtb) on Armbian 5.91 is still not compiled with overlay support. You can download the attached dtb, rename and replace the dtb on your system. lk4.14_armada-388-helios4.dtb is for Armbian Default (Stretch, Linux Kernel 4.14) sudo cp lk4.14_armada-388-helios4.dtb /boot/dtb/armada-388-helios4.dtb lk4.19_armada-388-helios4.dtb is for Armbian Next (Buster, Linux Kernel 4.19) sudo cp lk4.19_armada-388-helios4.dtb /boot/dtb/armada-388-helios4.dtb
  7. @Mangix have you check the wiki, https://wiki.kobol.io/cesa/ ? There are plenty of informations over there, for example the benchmark result and what kind of cipher can be hardware accelerated.
  8. I still confused with your configuration, you said you setup sdb & sdc as mirror but from the armbian log on first post, it's RAID level 5 with member sdb, sdc, &sdd Please run the following commands to make boot process more verbose sudo sed -i 's/verbosity=1/verbosity=7/g' /boot/armbianEnv.txt echo "extraargs=no_console_suspend ignore_loglevel" | sudo tee -a /boot/armbianEnv.txt sudo sed -i 's/exit 0/dmesg -n 8\nexit 0/g' /etc/rc.local sudo reboot and please capture serial console from very beginning of u-boot. Oh, with the configuration that has problem.
  9. Hi, Just wanted to make sure, do you see something like in screenshot below?
  10. Hi, We haven't started to work on 5.2 but maybe you can try the patch by Gontran Baerts for ArchLinux https://github.com/gbcreation/linux-helios4/blob/master/92-mvebu-gpio-remove-hardcoded-timer-assignment.patch
  11. Hi, currently booting directly to SATA1 is not supported. It was supported using Marvell U-boot 2013.01. If your intention is to boot without SD Card, you can boot from SPI NOR flash. The U-Boot on SPI NOR flash then would search boot.scr on following order USB SATA1 SD Card
  12. Hi, you're right, the driver is not included, you'd need to compile the driver by yourself if you need ASAP. I don't see any technical reason not to include the driver. After i test, I will enable it on Armbian kernel
  13. @MarcC it is possible to write U-Boot directly to SATA disk but currently no U-Boot image for SATA available. and AFAIK, the procedure a bit different but more similar like PC. Write U-Boot SPL to disk boot sector then put u-boot.bin into FAT formatted 1st partition. We are still experimenting with this, can not say when it would be ready.
  14. Yes, you can boot from SATA disk but currently limited only from SATA1 port. Take a look on following log: U-Boot SPL 2018.11-00008-g8f200a3d28 (Jul 03 2019 - 08:01:15 +0800) High speed PHY - Version: 2.0 Detected Device ID 6828 board SerDes lanes topology details: | Lane # | Speed | Type | -------------------------------- | 0 | 6 | SATA0 | | 1 | 5 | USB3 HOST0 | | 2 | 6 | SATA1 | | 3 | 6 | SATA3 | | 4 | 6 | SATA2 | | 5 | 5 | USB3 HOST1 | -------------------------------- High speed PHY - Ended Successfully mv_ddr: mv_ddr-armada-17.10.4 DDR3 Training Sequence - Switching XBAR Window to FastPath Window DDR Training Sequence - Start scrubbing DDR3 Training Sequence - End scrubbing mv_ddr: completed successfully Trying to boot from SPI U-Boot 2018.11-00008-g8f200a3d28 (Jul 03 2019 - 08:01:15 +0800) SoC: MV88F6828-A0 at 1600 MHz DRAM: 2 GiB (800 MHz, 32-bit, ECC enabled) MMC: mv_sdh: 0 Loading Environment from SPI Flash... SF: Detected w25q32bv with page size 256 Bytes, erase size 4 KiB, total 4 MiB OK Model: Helios4 Board: Helios4 SCSI: MVEBU SATA INIT Target spinup took 0 ms. Target spinup took 0 ms. AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl SATA mode flags: 64bit ncq led only pmp fbss pio slum part sxs Net: Warning: ethernet@70000 (eth1) using random MAC address - ee:e0:5b:09:22:72 eth1: ethernet@70000 Hit any key to stop autoboot: 0 starting USB... USB0: MVEBU XHCI INIT controller @ 0xf10f4000 Register 2000120 NbrPorts 2 Starting the controller USB XHCI 1.00 USB1: MVEBU XHCI INIT controller @ 0xf10fc000 Register 2000120 NbrPorts 2 Starting the controller USB XHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 1 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Device 0: device type unknown ... is now current device scanning bus for devices... Device 0: (0:0) Vendor: ATA Prod.: TOSHIBA MK5065GS Rev: GJ00 Type: Hard Disk Capacity: 476940.0 MB = 465.7 GB (976773168 x 512) Device 0: (0:1) Vendor: ATA Prod.: TOSHIBA MK5065GS Rev: GJ00 Type: Hard Disk Capacity: 476940.0 MB = 465.7 GB (976773168 x 512) Device 0: (1:0) Vendor: ATA Prod.: STEC MACH8 SSD Rev: 1031 Type: Hard Disk Capacity: 57241.8 MB = 55.9 GB (117231408 x 512) Device 0: (1:1) Vendor: ATA Prod.: STEC MACH8 SSD Rev: 1031 Type: Hard Disk Capacity: 57241.8 MB = 55.9 GB (117231408 x 512) Found 4 device(s). Device 0: (0:0) Vendor: ATA Prod.: TOSHIBA MK5065GS Rev: GJ00 Type: Hard Disk Capacity: 476940.0 MB = 465.7 GB (976773168 x 512) ... is now current device Scanning scsi 0:1... Found U-Boot script /boot/boot.scr 2948 bytes read in 88 ms (32.2 KiB/s) ## Executing script at 03000000 Boot script loaded from scsi 199 bytes read in 54 ms (2.9 KiB/s) 18933 bytes read in 167 ms (110.4 KiB/s) 5408781 bytes read in 223 ms (23.1 MiB/s) 5590368 bytes read in 218 ms (24.5 MiB/s) ## Loading init Ramdisk from Legacy Image at 02880000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 5408717 Bytes = 5.2 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 02040000 Booting using the fdt blob at 0x2040000 Loading Ramdisk to 0fad7000, end 0ffff7cd ... OK reserving fdt memory region: addr=2040000 size=6a000 Loading Device Tree to 0fa6a000, end 0fad6fff ... OK Starting kernel ... Uncompressing Linux... done, booting the kernel. Helios4 boot from SPI with rootfs located on scsi 0:1 To access the SATA disk, you have to use scsi command instead of sata command
  15. Hi, yes, you can see the boot process from serial. you can follow the instruction in our wiki. After the serial terminal ready, you can press the reset button to see the boot process since very beginning. You should see something like: U-Boot SPL 2018.11-armbian (Jan 20 2019 - 20:02:45 -0800) High speed PHY - Version: 2.0 Detected Device ID 6828 board SerDes lanes topology details: | Lane # | Speed | Type | -------------------------------- | 0 | 6 | SATA0 | | 1 | 5 | USB3 HOST0 | | 2 | 6 | SATA1 | | 3 | 6 | SATA3 | | 4 | 6 | SATA2 | | 5 | 5 | USB3 HOST1 | -------------------------------- High speed PHY - Ended Successfully mv_ddr: mv_ddr-armada-17.10.4 DDR3 Training Sequence - Switching XBAR Window to FastPath Window DDR Training Sequence - Start scrubbing DDR3 Training Sequence - End scrubbing mv_ddr: completed successfully Trying to boot from MMC1 U-Boot 2018.11-armbian (Jan 20 2019 - 20:02:45 -0800) SoC: MV88F6828-A0 at 1600 MHz DRAM: 2 GiB (800 MHz, 32-bit, ECC enabled) MMC: mv_sdh: 0 Loading Environment from MMC... *** Warning - bad CRC, using default environment Model: Helios4 Board: Helios4 SCSI: MVEBU SATA INIT Target spinup took 0 ms. SATA link 1 timeout. AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl SATA mode flags: 64bit ncq led only pmp fbss pio slum part sxs Net: Warning: ethernet@70000 (eth1) using random MAC address - 52:fc:90:b3:be:70 eth1: ethernet@70000 Hit any key to stop autoboot: 3 2 1 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 1979 bytes read in 104 ms (18.6 KiB/s) ## Executing script at 03000000 Boot script loaded from mmc 220 bytes read in 86 ms (2 KiB/s) 19717 bytes read in 353 ms (53.7 KiB/s) 4714605 bytes read in 852 ms (5.3 MiB/s) 5460016 bytes read in 1037 ms (5 MiB/s) ## Loading init Ramdisk from Legacy Image at 02880000 ... Image Name: uInitrd Created: 2019-02-07 11:42:01 UTC Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 4714541 Bytes = 4.5 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 02040000 Booting using the fdt blob at 0x2040000 Using Device Tree in place at 02040000, end 02047d04 Starting kernel ... But i think you won't see that screen. LED8 near power inlet indicate the input voltage, if it's blink (nothing fancy here, just LED connected to 12V 3.3V) then it's a hardware problem. most probably the power adapter. Do you have a voltmeter? Could you measure the voltage on these pin to determine whether it's power adapter or on-board regulator failure.