Gentoo On Orange Pi 3 LTS not Network

[denn0n]

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: Select all

* Clock skew detected 

and

Code: Select all

ERROR: netmount needs service(s) net

after that I do login normal and do

Code: Select all

ifconfig 

and only shows Io

if i do

Code: Select all

ifconfig -a

it shows eth0 to

how i do should work on that problem ?

Thank You All !

[NeddySeagoon]

denn0n,

Code: Select all

* 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: Select all

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.

[denn0n]

denn0n,

Code: Select all

* 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: Select all

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.