lebeno

Members
  • Content Count

    5
  • Joined

  • Last visited

  1. Booting my A20-OLinuXino-MICRO with the Armbian_5.20_Micro_Debian_jessie_4.7.3.7z (freshly downloaded) image from SD card hangs with these last log lines: [ 17.564273] cpufreq: cpufreq_online: CPU0: Running at unlisted freq: 384000 KHz [ 17.599267] cpufreq: cpufreq_online: CPU0: Unlisted initial frequency changed to: 528000 KHz At the start of the boot, there are also some bad looking error messages from U-Boot: Failed to set core voltage! Can't set CPU frequency Trying to boot from MMC1 U-Boot 2016.09-armbian (Sep 15 2016 - 05:13:34 +0200) Allwinner Technology CPU: Allwinner A20 (SUN7I) Model: Olimex A20-Olinuxino Micro I2C: ready DRAM: 1 GiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 *** Warning - bad CRC, using default environment Could this be a hardware problem? Do I have to do some manual initialization? Is this fixable? I have attached the full boot log to this post. The board is powered by a 12V 2A power supply. SD Card: Samsung EVO 64GB. A20-OLinuXino-MICRO_boot_hangs.txt
  2. I keep my Lime2 updated with apt-get update/apt-get upgrade, but it does not upgrade the u-boot, that is still an old version: U-Boot SPL 2015.07-armbian-sun7i (Oct 11 2015 - 17:17:10) DRAM: 1024 MiB CPU: 912000000Hz, AXI/AHB/APB: 3/2/2 Because the network speed is not that fast, I suspect this could be solved with a more recent u-boot. How do I update the Lime2 bootloader to a recent u-boot without re-downloading an image and re-installing all my software and data? It looks like there is already a recent u-boot.bin file on the system... # ls -l /usr/lib/nand-sata-install/a20/bootloader/linux/ -rwxr-xr-x 1 root root 152 May 23 22:35 linux.ini -rw-r--r-- 1 root root 309228 May 23 22:35 u-boot.bin ...but what steps are needed to make the Lime 2 use the new bootloader?
  3. @tkaiser Added that to my post under EDIT 2016-04-01, extra info. This is the smart output: # smartctl -a /dev/sda | grep 199 199 UDMA_CRC_Error_Count 0x003e 099 099 000 Old_age Always - 18
  4. I have been experiencing the same problem: freezing almost every day or every week. Running Debian Jessie Vanilla with SSD. I have even upgraded my power supply to a full ATX (PC) power supply, and LiPo battery, but still freezing. I checked the power demand with a digital multimeter in MIN/MAX mode and the current never went above 500mA. I doubt this is a power issue, and if it is, it is on the board, not the external power supply. I also see a lot of ATA errors in /var/log/syslog: [ 753.731120] ata1.00: exception Emask 0x0 SAct 0x600 SErr 0x0 action 0x0 [ 753.731144] ata1.00: irq_stat 0x40000000 [ 753.731161] ata1.00: failed command: READ FPDMA QUEUED [ 753.731184] ata1.00: cmd 60/08:48:20:cf:f4/00:00:24:00:00/40 tag 9 ncq 4096 in res 41/04:08:20:cf:f4/00:00:24:00:00/00 Emask 0x401 (device error) <F> [ 753.731196] ata1.00: status: { DRDY ERR } [ 753.731203] ata1.00: error: { ABRT } [ 753.731212] ata1.00: failed command: READ FPDMA QUEUED [ 753.731232] ata1.00: cmd 60/08:50:28:1e:c0/00:00:24:00:00/40 tag 10 ncq 4096 in res 41/04:00:20:cf:f4/00:00:24:00:00/40 Emask 0x1 (device error) [ 753.731242] ata1.00: status: { DRDY ERR } [ 753.731249] ata1.00: error: { ABRT } [ 753.731552] ata1.00: supports DRM functions and may not be fully accessible [ 753.732143] ata1.00: supports DRM functions and may not be fully accessible [ 753.732397] ata1.00: configured for UDMA/133 [ 753.732500] sd 0:0:0:0: [sda] tag#10 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 [ 753.732519] sd 0:0:0:0: [sda] tag#10 Sense Key : 0x5 [current] [descriptor] [ 753.732532] sd 0:0:0:0: [sda] tag#10 ASC=0x21 ASCQ=0x4 [ 753.732552] sd 0:0:0:0: [sda] tag#10 CDB: opcode=0x28 28 00 24 c0 1e 28 00 00 08 00 [ 753.732563] blk_update_request: I/O error, dev sda, sector 616570408 [ 753.732615] ata1: EH complete Do any of you see ATA erros in syslog? I do not know if this is related to the freezing problem. I have tried other SATA cable, but same result. Today, I was monitoring /var/log/syslog and I saw litteraly multiple pages of logs dumping on the HDMI screen because of a crash. I was able to take a picture of the last screen, see http://imgur.com/37ZXssp. EDIT 2016-04-01, extra info: I am running ARMBIAN Debian GNU/Linux 8 (jessie) 4.4.1-sunxi rootfs on uSD card, SSD only holds extra data in ext4 I have changed the governor to performance and no problems yet. No SATA errors in syslog, no craches.