Patrick

Members
  • Content count

    29
  • Joined

  • Last visited

About Patrick

  • Rank
    Member

Recent Profile Visitors

389 profile views
  1. Thanks ebin-dev, That worked (but you already knew that) kr., Patrick
  2. Hi, I had a little time and flashed the new firmware: espressobin-bootloader-cpu-1000-ddr3-2cs-1g-atf-ga3306ab-uboot-gaee49fc-20180129-REL.bin Set the environment settings again as found here: https://github.com/armbian/build/commit/e8868352324f5ee9567f2d06a0110c8f123a0384 Burned an image (Armbian_5.38_Espressobin_Debian_stretch_next_4.14.14.img) with Etcher. Sadly enough booting the ESPRESSObin doesn't complete Are the environment settings wrong? 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: Waiting for root file system ... Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. done. Gave up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/mmcblk0p1 does not exist. Dropping to a shell! kr., Patrick
  3. I know, But I never used the serial connection with my macbook connected to a power supply
  4. Read the NOTES here: https://www.armbian.com/espressobin/ Verzonden vanaf mijn iPhone met Tapatalk
  5. Sorry, the 5 day's up-time isn't the record. I changed this governor setting 5 days ago and had no kernel panic anymore.
  6. I changed the settings in /etc/init.d/cpufrequtils and /etc/default/cpufrequtils
  7. I had the firmware 1200/750 running but almost every day I had a kernel panic. I switched over to 1000/800 and had kernel panics every hour or so. Then I changed the governor from " ondemand" to "conservative" and now I have an up-time of 5 days kr., Patrick
  8. Changed ondemand governor to conservative, it's more stable for now. Verzonden vanaf mijn iPhone met Tapatalk
  9. Should this make the ESPRESSObin a bit more stable (les kernel panics)? For now this thing is hardly useable for personal use with OMV4 installed (with Docker and Plex).
  10. Sometimes I've got this kind of errors and the system doesn't respond anymore: Message from syslogd@localhost at Jan 12 17:42:02 ... kernel:[39637.813868] Call trace: Message from syslogd@localhost at Jan 12 17:42:02 ... kernel:[39637.822536] Call trace: After a few minutes (approx. 10 or so), the system is running normal again. kr. Patrick
  11. I'm back to 1200_750 MHz and the crashes are gone. So the 1000_800 MHz doesn't work for at this moment. kr., Patrick
  12. When I connect to the console when the ESPRESSObin has crashed, I only get an empty window. For me it's only possible to see the console when my macbook is connected (and the cosole open) on a running ESPRESSObin.
  13. Hi, Sometimes my ESPRESSObin crashes (I think). I need to "hard reset" the ESPRESSObin and afterwards it runs normal again. Is there a way, a log file or so, to find the cause of the crash? kr., Patrick
  14. I flashed the u-boot with "flash-image-1g-1000_800_boot_sd_and_usb.bin" and burned a new image on the sd-card. Now the scaling works for me also. # cat /proc/version Linux version 4.4.107-mvebu64 (root@xeon) (gcc version 6.4.1 20171012 (Linaro GCC 6.4-2017.11) ) #7 SMP PREEMPT Sat Dec 30 14:02:18 CET 2017 # cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 CPUs which need to have their frequency coordinated by software: 0 1 maximum transition latency: 50.0 us. hardware limits: 200 MHz - 1000 MHz available frequency steps: 200 MHz, 250 MHz, 500 MHz, 1000 MHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 250 MHz and 1000 MHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1000 MHz (asserted by call to hardware). cpufreq stats: 200 MHz:0.11%, 250 MHz:47.38%, 500 MHz:0.46%, 1000 MHz:52.06% (10841) analyzing CPU 1: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 CPUs which need to have their frequency coordinated by software: 0 1 maximum transition latency: 50.0 us. hardware limits: 200 MHz - 1000 MHz available frequency steps: 200 MHz, 250 MHz, 500 MHz, 1000 MHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 250 MHz and 1000 MHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1000 MHz (asserted by call to hardware). cpufreq stats: 200 MHz:0.11%, 250 MHz:47.38%, 500 MHz:0.46%, 1000 MHz:52.06% (10841)
  15. Thanks ebin-dev, My cpufrequtils are: ENABLE=true MIN_SPEED=200000 MAX_SPEED=1200000 GOVERNOR=ondemand The scaling doesn't work for me. In the passed I tested with the 1000MHz u-boot but got a lot of kernel-panics. Now, a few weeks or more later, I'll flash my u-boot again to 1000MHz. See what's happen. kr., Patrick