Jump to content

First run stuck with ssh key generation / Cubietruck RTC bug


Vadim Kovzunov

Recommended Posts

Very much I hope that the problem will be solved. Good distribution kit. Convenient.

If it helps with elimination of a mistake that: my problem is shown not only when updating but also new installation of the last kernel. All that I spoke on the problem was at new installation of the last image and kernel

Link to comment
Share on other sites

Solution(s) - pick one:

 

- Edit /etc/init.d/armhwinfo and add this:

# fix for eth0 no brought up
if [ "$(hwclock -r)" == "" ]; then 
echo -e "[\e[0;32m ok \x1B[0m] Fixing RTC and reloading eth0"
date -s "2015-01-01 10:00:00"
hwclock -w
ifup eth0
fi

- Replace it with this content

 

- Wait for new image release (4.3)

 

 

Please try if you run into problems after this fix. 

Link to comment
Share on other sites

And a little more universal solution:

# fix for eth0 no brought up
if [ "$(hwclock -r)" == "" ]; then
echo -e "[\e[0;32m ok \x1B[0m] Fixing RTC and reloading eth0"
date -s "2015-01-01 10:00:00"
hwclock -w
service networking restart
fi
Link to comment
Share on other sites

It works in Trusty too. (there is some time delay but it works)

Jessie startup procedure is different and it resolves into different error. I'll try but it won't be this quick as for Wheezy. 

 

Rather stick to Wheezy, yes.

 

... I would rather see this is solved on kernel level.

Link to comment
Share on other sites

Ah, sorry...

 

Wheezy with kernel 4.1.6 does work.

 

... when you use Igor's patch:

 

# fix for eth0 no brought up

if [ "$(hwclock -r)" == "" ]; then
echo -e "[\e[0;32m ok \x1B[0m] Fixing RTC and reloading eth0"
date -s "2015-01-01 10:00:00"
hwclock -w
service networking restart

fi

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines