cibomato

  • Content Count

    45
  • Joined

  • Last visited

Posts posted by cibomato

  1. Hi Igor,

     

    aaaargh, I've already checked this page before but was too fast and didn't see the touch display.

    Sorry for inconvenience and many thanks for your answer and hint!!!

    Just ordered the 7" display ;-)

    Can I use the mainline or do I have to use the legacy image for it?

     

    Best regards,

    Jochen

  2. Hi all,

     

    I'd like to use a touch display together with my cubietruck. 

    Research shows displays for all other boards but not for cubietruck :-(

    Isn't there any touch display out there which works with cubietruck?

    Do I really have to change system to raspberry or something else?

     

    Thanks for your help and best regards,

    cibomato

  3. Hi,

     

    haven't touched my system for quite a long time, now I'm running into problems while trying to uprade system:

     

    Err http://apt.armbian.com trusty/main armhf Packages
      404  Not Found
    ...

    W: Failed to fetch http://apt.armbian.com/dists/trusty/main/binary-armhf/Packages: 404  Not Found
    W: Failed to fetch http://nginx.org/packages/mainline/ubuntu/dists/trusty/nginx/binary-armhf/Packages: 404  Not Found [IP: 95.211.80.227 80]
    E: Some index files failed to download. They have been ignored, or old ones used instead.
    E: Couldn't rebuild package cache

     

    aptitude upgrade
    The following packages will be upgraded:
      linux-trusty-root-next-cubietruck
    1 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
    Need to get 363 kB of archives. After unpacking 0 B will be used.
    Do you want to continue? [Y/n/?]
    WARNING: untrusted versions of the following packages will be installed!

    Untrusted packages could compromise your system's security.
    You should only proceed with the installation if you are certain that
    this is what you want to do.

      linux-trusty-root-next-cubietruck

    Do you want to ignore this warning and proceed anyway?
    To continue, enter "Yes"; to abort, enter "No": Yes
    Err http://apt.armbian.com/ trusty/main linux-trusty-root-next-cubietruck armhf 5.23
      404  Not Found
    0% [Working]E: Failed to fetch http://apt.armbian.com/pool/main/l/linux-trusty-root-next-cubietruck/linux-trusty-root-next-cubietruck_5.23_armhf.deb: 404  Not Found
     

     

    Any idea?

     

    Thanks in advance and best regards,

    Jochen

  4. apt-get update && apt-get upgrade
    

    ran through smoothly and yesterday some other packages where updated successfully (...libc...), so I assume that the package base shouldn't be corrupted. Otherwise this wouldn't have worked?

    But running:

    root@seafile:/# wget -qO - http://upgrade.armbian.com | bash
    Image Name:
    Created:      Tue Oct 20 12:03:57 2015
    Image Type:   ARM Linux Script (uncompressed)
    Data Size:    1753 Bytes = 1.71 kB = 0.00 MB
    Load Address: 00000000
    Entry Point:  00000000
    Contents:
       Image 0: 1745 Bytes = 1.70 kB = 0.00 MB
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    Calculating upgrade... Done
    0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
    
    
    All done. Check boot scripts and reboot for changes to take effect!
    
    
    Visit: forum.armbian.com in case of troubles or just for fun 
    
    
    root@seafile:/#

    results in no kernel update, although I'm still on 4.1.6.

     

    Which log could I check / do you need to further investigate?

     

    With "install them manually" do you mean the steps described in 'how to unbrick the system'? So just download and dpkg -x these files? 

     

    Thanks and best regards,

    Jochen

  5. [sOLVED]

     

    Ok, don't know, what have caused the problem but after 

    - installing 4.2-image on sd

    - doing sata-install on fresh hdd

    - booting from sd with old hdd

    system comes up! :)

     

    Seems to be f***ed-up somehow (iptables and some other complain, I have to look into it...) but it's up & running again.

     

    Although: Seems that system still was on kernel 4.1.6, although I did the update-stuff with new update-script. Have to try this again.

     

  6. Igor, could you please tell me where to download the 4.3 image for trusty-next-cubietruck (Ionly found the single files but that doesn't seem to work)?

    [Edit]: Ok, guessed the right download-link ;-)

     

    Background:

    - installed latest 4.5 image on sd

    - did sata-install on fresh hdd

    - tried to boot with newsd+old hdd (with all my data on it)

     

    -> didn't work because during boot process e.g iptables complains about wrong kernel

     

    Thanks and best regards,

    Jochen

  7. Hi Igor,

     

    while trying to reproduce/fixing my boot problem, I stumbled across some weird things regarding your new update script.

     

    I've put a complete new image on sd-card only (Armbian_4.5_Cubietruck_Ubuntu_trusty_4.2.3) which works fine, boots and reboots.

    Then I've tried to use your update script which I called via:

    wget -q -O - http://upgrade.armbian.com | bash
    

    with the letter O and a blank between the minus and http, is this correct?

     

    First strange thing I noticed is, that it starts but doesn't run through completely. It ends with this output:

    a1.jpg

     

    Don't think that this should be the normal behaviour!? And remember that this wasn't the case when I tried this some time ago. What could have happened?

     

    Second strange thing is, that when I call it again, it runs through completely, removes the old kerne-stuff:

     

    a2.jpg

     

    but tells me that nothing was upgraded / removed nor installed.....????:

     

    a3.jpg

     

    Could this be because everything was already up to date? But then it either shouldn't remove 'old' kernel or should populate /boot again with the latest stuff!?

     

    Looking in /boot, all the new stuff is missing:

     

    a4.jpg

     

    So no wonder that it doesn't boot anymore.

     

    Does this make any sense to you? Can you imagine what has happened and whether this is a common thing or something went wrong just at my side?

    [Edit:] There's another user that reports similar problem: http://forum.armbian.com/index.php/topic/211-kernel-update-procedure-has-been-changed/?p=2173

     

    Thanks in advance and best regards,

    Jochen

  8. Hi Igor,

     

    instead of installing a whole new system in parallel, I'd first like to try your 'unbrick-mechanism' as described under Documentation.

    I'm just wondering whether I'll need only the 4 files you mention in 'How to unbrick the sytem' or in addition the headers and especially the u-boot, as you mention here: http://forum.armbian.com/index.php/topic/211-kernel-update-procedure-has-been-changed/ ?

    If I'd need also the u-boot, could you please tell me the URL to it, since I couldn't locate it.

     

    Thanks and best regards,

    Jochen

  9. Thanks Igor!

     

    I'll try to setup whole new working system on a new sd card, do the sata install to a new hdd and then try to use the new sd card with my existing hdd. Maybe that'll do it.

    BTW, it wasn't 4.1 but 4.3, I've upgraded from but nevertheless it's strange.

  10. Yes, boot is on sd, everything else on hdd. Survived some reboots before.

     

    I upgraded from ubuntu trusty 4.1 image / vanilla kernel. Was it the 4.2 kernel?

     

    I used 

    wget -q -O - http://upgrade.armbian.com | bash

    to upgrade to the 4.5 image (did this already some weeks before in order to update to the 4.1 image.)

    Is this the right procedure, to run this again? Or should I have just use apt-get upgrade?

     

    Seems that it didn't do anything, but i'm not sure. So after that I ran

    apt-get update && apt-get upgrade

    Also didn't seem to do much (maybe beause I have automatic upgrades activated?).

     

    So I decided to try to reboot in order to see whether it'll come up with a new kernel but oops,... doesn't boot any more.

  11. Hi,

     

    after trying to upgrade to new image 4.5 (don't know whether this was successful...) and reboot, my cubietruck get's stucked:

    boot.jpg

     

    What could have happened? Is this the same problem, some others describe here or totally different?

    Seems like it doesn't find 'a boot file'!? What does this mean? Bootloader is on sd, root etc. on hdd. 

     

    Thanks and best regards,

    Jochen

  12. Hey man, keep cool!

     

    Or did you pay thousands of dollars for an 24*7 5hr-response-time platinum support? Then go ahead.

     

    Think, we are all appreciating the very great work, Igor is doing here! And since we're not paying for it (I have spent via paypal, have you?), we will just have to wait, until things are ready.

     

    No harm meant!

     

    cibomato