cibomato

  • Content Count

    45
  • Joined

  • Last visited

Reputation Activity

  1. Like
    cibomato reacted to Igor in Touch display for cubietruck?   
    It works on mainline. Not sure for legacy.
  2. Like
    cibomato reacted to Igor in Touch display for cubietruck?   
    I have two touchscreen displays in the lab. Both works with Cubietruck in plug and play fashion. Check download page for details: https://www.armbian.com/cubietruck/ Similar will also work and there are many others, but for some you might need to do some R&D/tinkering.
  3. Like
    cibomato got a reaction from Igor in update not working   
    Hi Igor,
     
    thanks for your answer. Upgrade to Xenial didn't work either but now I've set up a whole new system image.
     
    Cheers,
    Jochen
  4. Like
    cibomato reacted to Igor in Problem with new update script   
    If you still have a running system, than you don't need to use that procedure but directly:
    apt-get install linux-image-next-sunxi linux-headers-next-sunxi linux-firmware-image-next-sunxi apt-get install linux-trusty-root-cubietruck apt-get install linux-u-boot-next-cubietruck
  5. Like
    cibomato got a reaction from Igor in new? boot problem   
    Thanks Igor!
  6. Like
    cibomato reacted to Igor in new? boot problem   
    http://apt.armbian.com/pool/main/l/
     
    Get the one for your board.
     
    NEXT in name is for mainline kernel 4.x.
  7. Like
    cibomato got a reaction from wildcat_paris in Kernel update procedure has been changed   
    Yes, it solves the problem. Didn't expect it to be so easy ... 
    Thank you!!!
  8. Like
    cibomato got a reaction from Igor in Kernel update procedure has been changed   
    Yes, it solves the problem. Didn't expect it to be so easy ... 
    Thank you!!!
  9. Like
    cibomato reacted in change commit setting when using hdd?   
    For a normal HDD the defaults are fine. For a SSD it's recommended to add "noatime" and "commit=600" mount options. The "discard" is not recommended, and fstrim should be used instead.
  10. Like
    cibomato got a reaction from jtaparicio in cubietruck hangs at boot with debian-3.8-wheezy-4.0.4   
    GOT IT !!!
      It was the f***ed-up rtc indeed! Let me explain:   I simplified my experiment from above:   - installed debian-3.8-wheezy-3.4.107 --> ok (eth0 is ok, ping heise.de works) - survives reboot / halt and power-on / halt and dis-/reconnect power --> everything ok   Then upgrade to kernel 4.0.5 as described in your faq and then: - reboot    --> System boots till login screen (!!!) but eth0 isn't set up! No ping possible! dmesg | grep rtc 2085-06-25 (NOT ok) date Fr 20. Mai 13:37:52 CET 1949 (NOT ok)
    hwclock --show hwclock: The Hardware Clock registers contain values that are either invalid (e.g. 50th day of month) or beyond the range we can handle (e.g. Year 2095).
      So, all date/time and clocks are wrong! Now I've set the correct date manually: date -s "25 JUN 2015 21:00:10" date ok!
     
    But hwclock / rtc is still going wrong:
    hwclock --show (NOT ok)
     
    So, I've now set hwclock to system date via:
    hwclock --systohc --localtime And voilà:
    hwclock --show  --> ok (!)   reboot --> eth0 comes up !!!! ping ok! date --> ok hwclock --show --> ok   halt and power on date : ok ping ok   halt power dis-reconmnect --> ok   Then I removed sdcard, copied debian-4.0-wheezy-4.1 on it, put it back in and reset   And.................. Tatataaaaaaa, it doesn't complain about rtc, it recognizes eth0 and boots normally!   Repeated that with new installation of  debian 3.9-jessie-4.0.5, also works like a charm!     I'm happy!   Hope, that this is helpful for you other guys, too!!!
  11. Like
    cibomato got a reaction from Igor in cubietruck hangs at boot with debian-3.8-wheezy-4.0.4   
    GOT IT !!!
      It was the f***ed-up rtc indeed! Let me explain:   I simplified my experiment from above:   - installed debian-3.8-wheezy-3.4.107 --> ok (eth0 is ok, ping heise.de works) - survives reboot / halt and power-on / halt and dis-/reconnect power --> everything ok   Then upgrade to kernel 4.0.5 as described in your faq and then: - reboot    --> System boots till login screen (!!!) but eth0 isn't set up! No ping possible! dmesg | grep rtc 2085-06-25 (NOT ok) date Fr 20. Mai 13:37:52 CET 1949 (NOT ok)
    hwclock --show hwclock: The Hardware Clock registers contain values that are either invalid (e.g. 50th day of month) or beyond the range we can handle (e.g. Year 2095).
      So, all date/time and clocks are wrong! Now I've set the correct date manually: date -s "25 JUN 2015 21:00:10" date ok!
     
    But hwclock / rtc is still going wrong:
    hwclock --show (NOT ok)
     
    So, I've now set hwclock to system date via:
    hwclock --systohc --localtime And voilà:
    hwclock --show  --> ok (!)   reboot --> eth0 comes up !!!! ping ok! date --> ok hwclock --show --> ok   halt and power on date : ok ping ok   halt power dis-reconmnect --> ok   Then I removed sdcard, copied debian-4.0-wheezy-4.1 on it, put it back in and reset   And.................. Tatataaaaaaa, it doesn't complain about rtc, it recognizes eth0 and boots normally!   Repeated that with new installation of  debian 3.9-jessie-4.0.5, also works like a charm!     I'm happy!   Hope, that this is helpful for you other guys, too!!!