Heimdall

Members
  • Content Count

    12
  • Joined

  • Last visited

  1. Nope, old install (but it was next before) so there is no upgrade 4.18 -> 4.19? I have Stretch mainline.. but its 4.18 kernel So should I switch kernel to linux-image-next-meson64=5.71?
  2. Have same problem still with 4.18.8-odroidc2 aka Armbian 5.70 .. have to run lsusb -v few times to get USB drive up.. :-/
  3. That´s for long discussion, but computer (some intel nuc like) for 130€ will be in the end better for me (if I count spent hours with problems) then Odroid for 100€ But when I was buying Odroid at release, I was hoping for great support, but actually, Hardkernel doesnt care too much about C2. It suprise me that about XU4/MC1/HC1/HC2 they care much more And I want just headless server. I am not talking about some ARM for Kodi, because that is also not so well developed.. so for headleass.. do I want too much? Interesting, for me it was not working on clean NEXT installation. With default (3.16) kernel it works well.. with clean installation also system is stable now and not crashing every 12 hours
  4. Nope, reboot was first what I was trying.. mkey, back to 3.16 and I will write to my forehead "ARM boards are not worth it.. x86 ftw" (but I am glad what you and whole Armbian team doing, but support from ARM producers is shitty unfortunately).
  5. And any ideas about USB problems in following post?
  6. Heh, this kind of commits should be in repo asap
  7. I just installed clean image (its not a big deal, since data are on external USB disc), but I am not able now to get disk even detected in system (its not even blinking), but this was working correctly on 3.16 kernel.. any ideas? I created logs where I can see, that USB hub is detected, but when I put USB disk on, nothing (in dmesg or messages) - http://ix.io/1jSw Not even keyboard + mouse which I have in powered USB hub is loaded.. not a single line in dmesg after connection (tested all 4 ports). Don´t know if this can be named as "They are getting to that state, where we could just forget about old legacy kernels." :-)
  8. I found option to upgrade kernel from armbian-config, but after upgrade to next kernel, after reboot is just green screen on HDMI and nothing else.. going to try clean next installation..
  9. Is there any howto for upgrade? My use case is just using few docker images (5 running). OS is running on eMMC card and data are on USB disk.
  10. It stuck again. Here is the graphs from nmon - https://imgur.com/a/K7T4N3 Nothing special to see actually (all looks normal to me..). Will try to find out if I can go back with kernel or firmware.
  11. It freeze again, I tried to plug monitor to see something.. but no output at all :-/ going to set up nmon
  12. Hi guys, After some time I get enough brave to do apt upgrade on my Odroid C2 (after month or two).. I updated following packages: Start-Date: 2018-08-07 11:09:56 Commandline: apt upgrade Install: html2text:arm64 (1.3.2a-18, automatic), debconf-utils:arm64 (1.5.56+deb8u1, automatic) Upgrade: ncurses-term:arm64 (5.9+20140913-1+deb8u2, 5.9+20140913-1+deb8u3), libtinfo5:arm64 (5.9+20140913-1+deb8u2, 5.9+20140913-1+deb8u3), linux-dtb-odroidc2:arm64 (5.40, 5.54), libncurses5:arm64 (5.9+20140913-1+deb8u2, 5.9+20140913-1+deb8u3), libncursesw5:arm64 (5.9+20140913-1+deb8u2, 5.9+20140913-1+deb8u3), ncurses-bin:arm64 (5.9+20140913-1+deb8u2, 5.9+20140913-1+deb8u3), base-files:arm64 (8+deb8u10, 8+deb8u11), patch:arm64 (2.7.5-1, 2.7.5-1+deb8u1), libldap-2.4-2:arm64 (2.4.40+dfsg-1+deb8u3, 2.4.40+dfsg-1+deb8u4), linux-image-odroidc2:arm64 (5.40, 5.54), armbian-config:arm64 (5.40, 5.54), linux-u-boot-odroidc2-default:arm64 (5.40, 5.49), docker-ce:arm64 (18.05.0~ce~2.1.rc1-0~debian, 18.06.0~ce~2.1.rc1-0~debian), armbian-tools-jessie:arm64 (5.40, 5.44), tzdata:arm64 (2018d-0+deb8u1, 2018e-0+deb8u1), armbian-firmware:arm64 (5.40, 5.45), ncurses-base:arm64 (5.9+20140913-1+deb8u2, 5.9+20140913-1+deb8u3) End-Date: 2018-08-07 11:10:45 After upgrade I am having freeze almost every 12 hours - not able to connect to the odroid via SSH (running headless) and I have to replug power (I am using official power adapter from Odroid via jack). Here is link to logs etc. any ideas what it could be? I will try to set up nmon or zabbix to monitor health of mem / cpu before crash.