View previous topic :: View next topic |
Author |
Message |
denn0n Tux's lil' helper
Joined: 24 May 2020 Posts: 87
|
Posted: Fri Nov 04, 2022 10:28 pm Post subject: Gentoo On Orange Pi 3 LTS not Network |
|
|
Hi I'm trying to install stage3 arm64 on a Orange Pi 3 LTS.
till now I have get to boot it but alert me two different things
Code: |
* Clock skew detected |
and
Code: |
ERROR: netmount needs service(s) net |
after that I do login normal and do
and only shows Io
if i do
it shows eth0 to
how i do should work on that problem ?
Thank You All ! |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54615 Location: 56N 3W
|
Posted: Fri Nov 04, 2022 10:56 pm Post subject: |
|
|
denn0n,
Code: | * Clock skew detected | means the boot process has detected your real time clock has gone backwards. Maybe you don't have one?
If your system is not fitted with a battery backed real time clock, rewove hwclock for the default runlevel and replace it with swclock.
This keeps your system time monotonic. It does not keep your time correct.
Code: | ERROR: netmount needs service(s) net | tells that your network didn't start. That's eth0.
eth0 is there but its not started.
Make a symlink in /etc/init.d/ that links net.eth0 to net.lo. Now add net.eth0 to the default runlevel.
You should install one of the ntp daemons and start it in the default runlevel too.
That will synchronise your system time to network time.
System time going backwards confuses make and security certificates that have a not valid until and not valid after window.
When your clock is incorrect, you will get warning about invalid security certificates. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
denn0n Tux's lil' helper
Joined: 24 May 2020 Posts: 87
|
Posted: Sat Nov 05, 2022 12:02 am Post subject: Thank You ! |
|
|
NeddySeagoon wrote: | denn0n,
Code: | * Clock skew detected | means the boot process has detected your real time clock has gone backwards. Maybe you don't have one?
If your system is not fitted with a battery backed real time clock, rewove hwclock for the default runlevel and replace it with swclock.
This keeps your system time monotonic. It does not keep your time correct.
Code: | ERROR: netmount needs service(s) net | tells that your network didn't start. That's eth0.
eth0 is there but its not started.
Make a symlink in /etc/init.d/ that links net.eth0 to net.lo. Now add net.eth0 to the default runlevel.
You should install one of the ntp daemons and start it in the default runlevel too.
That will synchronise your system time to network time.
System time going backwards confuses make and security certificates that have a not valid until and not valid after window.
When your clock is incorrect, you will get warning about invalid security certificates. |
|
|
Back to top |
|
|
|