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:
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:
but tells me that nothing was upgraded / removed nor installed.....????:
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:
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?
Question
cibomato 8
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:
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:
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:
but tells me that nothing was upgraded / removed nor installed.....????:
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:
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
Link to post
Share on other sites
13 answers to this question
Recommended Posts