matteobp

Members
  • Content count

    46
  • Joined

  • Last visited

About matteobp

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male
  • Location
    ITALY

Recent Profile Visitors

379 profile views
  1. matteobp

    Rock64 nightly image

    Yesterday I downloaded the latest "Debian desktop" image (it should be 5.42) linked here https://www.armbian.com/rock64/ but I'm still having the error reported below. I have never been able to run a version of Armbian on my Rock 64 (1GB version) . I'm currently using Armbian (Debian) on an Orange Pi+ without any problem. What's the problem? Can someone help me please? Welcome to minicom 2.7.1 OPTIONS: I18n Compiled on Aug 13 2017, 15:25:34. Port /dev/ttyUSB0, 20:57:55 Press CTRL-A Z for help on special keys DDR version 1.06 20170424 In LPDDR3 786MHz Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=32 Size=1024MB ddrconfig:1 OUT U-Boot SPL 2017.09-g5a90a9a (Jan 12 2018 - 11:06:01) setup_ddr_param 1 booted from SPI flash Trying to boot from SPI NOTICE: BL31: v1.3(release):f947c7e NOTICE: BL31: Built : 11:06:00, Jan 12 2018 NOTICE: BL31:Rockchip release version: v1.3 U-Boot 2017.09-g5a90a9a (Jan 12 2018 - 11:06:15 +0000), Build: jenkins-linux-build-rock-64-177 Model: Pine64 Rock64 DRAM: 1022 MiB MMC: rksdmmc@ff520000: 0, rksdmmc@ff500000: 1 *** Warning - bad CRC, using default environment In: serial@ff130000 Out: serial@ff130000 Err: serial@ff130000 Model: Pine64 Rock64 misc_init_r cpuid=55524b503039303038000000000d2b11 serial=ea6ec868699cad5 Net: eth0: ethernet@ff540000 Hit any key to stop autoboot: 0 Card did not respond to voltage select! mmc_init: -95, time 9 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 2960 bytes read in 27 ms (106.4 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 112 bytes read in 21 ms (4.9 KiB/s) "Synchronous Abort" handler, esr 0x96000210 ELR: 3ff77944 LR: 3ff75eb0 x0 : 000000003df2e9b0 x1 : 0000000044000000 x2 : 0000000000000070 x3 : 0000000000000000 x4 : 0000000000000070 x5 : 000000000000000e x6 : 0000000000000000 x7 : 0000000000000000 x8 : 0000000000000000 x9 : 0000000000000008 x10: 000000003df2e9c0 x11: 000000003df13b70 x12: 0000000000000000 x13: 0000000000000200 x14: 000000003df04bfc x15: 00000000ffffffff x16: 0000000060df18a6 x17: 0000000070a12210 x18: 000000003df0ce08 x19: 0000000000000000 x20: 0000000000000070 x21: 0000000044000000 x22: 000000003df2e9b0 x23: 000000003ffa0118 x24: 0000000000000000 x25: 0000000000000000 x26: 000000000000000a x27: 0000000000000001 x28: 0000000000000000 x29: 000000003df02b10 Resetting CPU ... DDR version 1.06 20170424 In SRX LPDDR3 786MHz Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=32 Size=1024MB ddrconfig:1 OUT U-Boot SPL 2017.09-g5a90a9a (Jan 12 2018 - 11:06:01) setup_ddr_param 1 booted from SPI flash Trying to boot from SPI NOTICE: BL31: v1.3(release):f947c7e NOTICE: BL31: Built : 11:06:00, Jan 12 2018 NOTICE: BL31:Rockchip release version: v1.3 U-Boot 2017.09-g5a90a9a (Jan 12 2018 - 11:06:15 +0000), Build: jenkins-linux-build-rock-64-177 Model: Pine64 Rock64 DRAM: 1022 MiB MMC: rksdmmc@ff520000: 0, rksdmmc@ff500000: 1 *** Warning - bad CRC, using default environment In: serial@ff130000 Out: serial@ff130000 Err: serial@ff130000 Model: Pine64 Rock64 misc_init_r cpuid=55524b503039303038000000000d2b11 serial=ea6ec868699cad5 normal boot Net: eth0: ethernet@ff540000 Hit any key to stop autoboot: 0 Card did not respond to voltage select! mmc_init: -95, time 9 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 2960 bytes read in 28 ms (102.5 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 112 bytes read in 22 ms (4.9 KiB/s) "Synchronous Abort" handler, esr 0x96000210 ELR: 3ff77944 LR: 3ff75eb0 x0 : 000000003df2e9d0 x1 : 0000000044000000 x2 : 0000000000000070 x3 : 0000000000000000 x4 : 0000000000000070 x5 : 000000000000000e x6 : 0000000000000000 x7 : 0000000000000000 x8 : 0000000000000000 x9 : 0000000000000008 x10: 000000003df2e9e0 x11: 000000003df13b70 x12: 0000000000000000 x13: 0000000000000200 x14: 000000003df04bfc x15: 00000000ffffffff x16: 0000000060df18a6 x17: 0000000070a12210 x18: 000000003df0ce08 x19: 0000000000000000 x20: 0000000000000070 x21: 0000000044000000 x22: 000000003df2e9d0 x23: 000000003ffa0118 x24: 0000000000000000 x25: 0000000000000000 x26: 000000000000000a x27: 0000000000000001 x28: 0000000000000000 x29: 000000003df02b10 Resetting CPU ...
  2. matteobp

    Rock64 nightly image

    No. With the latest version of 0.6.x (I tried with 0.6.13) it works. So both ayufan 0.5.15 e 0.6.1x works, at least the debian jessie and debian stretch images. But I was never able to boot the armbian. Here you can find the output log taken via console. Thanks
  3. matteobp

    Rock64 nightly image

    No one can help me? Why does the armbian image work for some people and doesn't work for other people like me? Thanks.
  4. matteobp

    Rock64 nightly image

    Hi. The "usb to serial ttl bridge adapter" arrived yesterday, and I tried the 20/11/2017 armbian Rock64 image. This is the output of the console and it loops on " x0 : ... x2 : ... ... x28: ... Resetting CPU ... " I hope that this can help. Thanks.
  5. matteobp

    Rock64 nightly image

    I think in my case the problem is not the writing: 2 writes with Etcher on Linux and 2 writes with Etcher on Windows with verification on. Moreover, when I write the ayufan image v. 0.5.15 the board works, while I have the same problem with 0.6.x . I think there is something missing/wrong with my board. Is there something like "a firmware" to be updated? AFAIK, the image contains everything I need. Thanks
  6. matteobp

    Rock64 nightly image

    No change. I used Etcher on Windows to write the SD card: it doesn't start; all leds on, no hdmi output. I think I have to wait for the "usb to serial ttl bridge adapter" (already ordered) and check via serial console what is happening.
  7. matteobp

    Rock64 nightly image

    Ok, perfect. I'll try and let you know. Thanks very much Matteo
  8. matteobp

    Rock64 nightly image

    How can I write an image on SD card with Linux? For my current Armbian on Orange Pi Plus I have always used dd, or dc3dd if I want to see the progress. For rock64, other tools are suggested, like Etcher and PINE64 Installer (based on Etcher). I tried dd, Etcher and PINE64 Installer, without success. By the way, Etcher and PINE64 Installer have an options for verifying. Can you suggest me another way to burn the rock64 armbian image on SD Card? If needed, I have also Windows system. Thanks Matteo
  9. matteobp

    Rock64 nightly image

    Hi. I've download the image built on 21/11, but it doesn't still work. I checked also the sha256 code to be sure that the image is not corrupted. Very strange. Did you burn the SD with Etcher? I think I have to try with Serial Console, but I have no usb to serial ttl bridge adapter. I want to buy a "CH340g usb to serial ttl bridge adapter". In this post https://forum.pine64.org/showthread.php?tid=5029 the connection is done with a Pinebook, but I think I can use any PC/notebook, isn't it. Thanks for support. Matteo
  10. matteobp

    Rock64 image for server only. Why?

    Hi. I'm currently using the armbian image (Debian Jessie) on an Orange Pi Plus board as NAS, and I bought the Rock64 one because it should have better performance in copying to and from NAS (the current average for the Orange Pi Plus is about 28-30MB/s), although so far the performance are lower than Orange Pi Plus, but it is another story. I want to use the Armbian also on Rock64, and the only available image is the server one (https://dl.armbian.com/rock64/Ubuntu_xenial_default_nightly.7z), but I was not able to use it I have already created this post Can you help me? Sorry for duplication post. Thanks in advance. Matteo
  11. matteobp

    Rock64 nightly image

    Hi all. I have a Rock64 board with 1GB RAM. I downloaded this image https://dl.armbian.com/rock64/Ubuntu_xenial_default_nightly.7z and I wrote it on the SD card (Samsung EVO 16GB) using both Etcher and dd command. But when I power the board, all 3 leds light up and remains on, nothing else happens. I have the same behaviour with the 0.6.0 stretch-minimal image downloaded here https://github.com/ayufan-rock64/linux-build/releases The only images that works are the 0.5.10 downloaded here https://github.com/ayufan-rock64/linux-build/releases/tag/0.5.10 What's wrong? I can exclude problems with power supply (I bought the one they suggested on their site, 5V 3A) and with SD card because I have no problem with 0.5.10 image. I tested both xenial-mate and stretch-minimal (with the XFCE4 desktop environment installed later) images without problems. Thanks in advance. Matteo
  12. matteobp

    BananaPi Network performance problem

    Removed. There are other two packages that seems to refers to mainline. This is the output of dpkg -l | grep next ii linux-firmware-image-next-sunxi 5.26 armhf Linux kernel firmware, version 4.9.10-sunxi ii linux-jessie-root-next-bananapi 5.25 armhf Armbian tweaks for jessie on bananapi (next branch) Are they ok? If I remove "linux-firmware-image-next-sunxi", can I install "linux-firmware-image-sun7i_5.27_armhf.deb"? I had error during previous installation of this package. Thanks
  13. matteobp

    BananaPi Network performance problem

    Perfect, it worked. Now the average Helios LanTest result are these ones. Legacy kernel without changes in /etc/sysctl.conf and /etc/sysfs.conf (CPU frequency set to 1104 Mhz) Legacy kernel with the changes reported in the first post in /etc/sysctl.conf and /etc/sysfs.conf (CPU frequency set to 1104 Mhz) Considering that I started with an image based on the mainline kernel, now that I went back to legacy kernel installing these 3 debs files linux-headers-sun7i_5.27_armhf.deb linux-image-sun7i_5.27_armhf.deb linux-u-boot-bananapipro_5.27_armhf.deb is there something else I have to do? I'm asking this because after apt update I have this list of upgradable packages. linux-dtb-next-sunxi/jessie 5.26 armhf [upgradable from: 5.26] linux-headers-next-sunxi/jessie 5.26 armhf [upgradable from: 5.26] linux-image-next-sunxi/jessie 5.26 armhf [upgradable from: 5.26] tzdata/stable-updates 2017a-0+deb8u1 all [upgradable from: 2016j-0+deb8u1] I dont' want to imagine what happens with an apt upgrade Thanks very much for the support.
  14. matteobp

    BananaPi Network performance problem

    This is the output of the command dpkg -i *.deb Selecting previously unselected package linux-firmware-image-sun7i. (Reading database ... 142813 files and directories currently installed.) Preparing to unpack linux-firmware-image-sun7i_5.27_armhf.deb ... Unpacking linux-firmware-image-sun7i (5.27) ... dpkg: error processing archive linux-firmware-image-sun7i_5.27_armhf.deb (--install): trying to overwrite '/lib/firmware/ap6210/nvram_ap6210.txt', which is also in package armbian-firmware 5.25 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Selecting previously unselected package linux-headers-sun7i. Preparing to unpack linux-headers-sun7i_5.27_armhf.deb ... Unpacking linux-headers-sun7i (5.27) ... Selecting previously unselected package linux-image-sun7i. Preparing to unpack linux-image-sun7i_5.27_armhf.deb ... Unpacking linux-image-sun7i (5.27) ... Selecting previously unselected package linux-u-boot-bananapipro-default. dpkg: regarding linux-u-boot-bananapipro_5.27_armhf.deb containing linux-u-boot-bananapipro-default: linux-u-boot-bananapipro-next conflicts with armbian-u-boot linux-u-boot-bananapipro-default provides armbian-u-boot and is to be installed. dpkg: error processing archive linux-u-boot-bananapipro_5.27_armhf.deb (--install): conflicting packages - not installing linux-u-boot-bananapipro-default Setting up linux-headers-sun7i (5.27) ... Compiling headers - please wait ... Setting up linux-image-sun7i (5.27) ... update-initramfs: Generating /boot/initrd.img-3.4.113-sun7i update-initramfs: Converting to u-boot format Errors were encountered while processing: linux-firmware-image-sun7i_5.27_armhf.deb linux-u-boot-bananapipro_5.27_armhf.deb Thanks for support Matteo
  15. matteobp

    BananaPi Network performance problem

    Hi. I did a last try. I downloaded the latest Banana Pi+ Server images "Legacy 3.4.113" and "Mainline 4.9.7", burnt them onto SD card, installed only samba and samba-common, and ran the Helios Lan Test. Here the resutl with "Legacy 3.4.113" and here the result with "Mainline 4.9.7" I didn't apply any changes, so the problem is with Mainline kernel itself. Am I the only one with this problem? Please help me. Thanks Matteo P.S. I tried this wget -q -O - http://upgrade.armbian.com | bash but after that the BananaPi didn't boot anymore. I had to restore the image taken before this try. Then I compiled the legacy kernel by myself (on a VirtualBox VM with ubuntu 16.04 server) and installed all these 4 debs files linux-firmware-image-sun7i_5.27_armhf.deb linux-headers-sun7i_5.27_armhf.deb linux-image-sun7i_5.27_armhf.deb linux-u-boot-bananapipro_5.27_armhf.deb with dpkg -i *.deb but I had an error during installation and also in this case the BananaPi didn't boot anymore and I had to restore the image. Which is the correct way to switch to legacy kernel in my situation?