nxtv2.0

With your kernel and dtb and lib/modules the ethernet led lights up IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready The distro uses ethernet by: ifconfig eth0 down ifconfig eth0 add 192.168.1.30 up route add default gw 192.168.1.1 echo nameserver 192.168.1.1 >> /etc/resolv.conf What could be wrong?

I tried: 1) montjoie's using make defconfig,then make zImage ,dtbs 2) megous same way as above 3) armbian kernel and every dtbs for plus2E or plus None worked,all same issue as above.

Could this issue be a problem in the distro and the kernel? How do i troubleshoot this? And when compiling kernel , how do i configure it? Do i use defconfig ?

I am using kernel 4.9 built from https://github.com/megous/linux and tried DTB plus/plus2E in a custom distro ,But the ethernet isn't working. ifconfig: SIOCGIFFLAGS: No such device ifconfig: SIOCSIFADDR: No such device route: SIOCADDRT: Network is unreachable What could be the reason?

Can you please post where can i find a dtb for the Plus 2E with gigabit ethernet working and USB fully working(+ USB OTG) and if there isn't how do i modify existing dtb files for Plus 2E to support gigabit ethernet.

The kernel used to boot in 2.7s but when i reinstalled armbian on the eMMC again it now boots in almost 6s, how do i know what delays the kernel like that and what changed.i needed to reinstall as i had masked an important module and SSH wasn't connecting.

What is udev?

I am running from the internel eMMC

I will be using this server to stream cameras in an rov and need to have it on very quick from cold boot. Is there a way to start a binary quicker than that and also what is taking systemd so long to run my serivce? Thanks in advance.

Using my custom service: [Unit] Description=virtualhere After=system.slice DefaultDependencies=no [Service] ExecStart=/root/vhusbdarm Is there a way to make it faster , it takes about 20 secs for the client to see the server after power on. Update: What stuff runs before system.slice that makes it take time to boot?

Running virtualhere server as soon as kernel boots ~ 2.7s To decrease wait time before server is ready

How do i start a service right after the kernel using systemd?

Ok here is a list after i removed a few: 1.669s networking.service 770ms systemd-logind.service 749ms systemd-udev-trigger.service 699ms rc-local.service 589ms systemd-user-sessions.service 569ms loadcpufreq.service 509ms systemd-setup-dgram-qlen.service 499ms systemd-modules-load.service 489ms kbd.service 479ms console-setup.service 409ms keymap.service 409ms systemd-random-seed.service 399ms systemd-remount-fs.service 389ms kmod-static-nodes.service 369ms systemd-tmpfiles-setup-dev.service 319ms cpufrequtils.service 299ms systemd-sysctl.service 281ms rsyslog.service 243ms dev-mqueue.mount 219ms systemd-tmpfiles-setup.service 202ms sys-kernel-debug.mount 150ms sys-fs-fuse-connections.mount 149ms systemd-rfkill@rfkill0.service 119ms udev-finish.service 119ms systemd-update-utmp.service 113ms systemd-update-utmp-runlevel.service 79ms sysfsutils.service 78ms user@0.service 57ms lirc.service 53ms systemd-udevd.service 10ms tmp.mount what services do i not need and are there other ways to reduce boot time.

Thank you will try it and report what services take alot of time to boot.

Hi, I'm using the orange pi plus 2e with armbian server installed on eMMC via the built-in script,as the title says i want ways to reduce boot times. I only need ethernet and usb since i will be using it as a "virtualhere" server. Thanks, linux super noob. regards.