If I run
dmesg | grep e1000e
there are 8 references when booting from the USB stick, but there none when booting from the hard drive.
What do you see right after the kernel modules start loading?
(From a VirtualBox instance):
[ 4.215447] procd: - init -
[ 4.227741] kmodloader: loading kernel modules from /etc/modules.d/*
[ 4.229368] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
[ 4.230156] e1000: Copyright (c) 1999-2006 Intel Corporation.
[ 4.705308] e1000 0000:00:03.0 eth0: (PCI:33MHz:32-bit) 08:00:27:64:f7:2d
[ 4.706036] e1000 0000:00:03.0 eth0: Intel(R) PRO/1000 Network Connection
[ 5.164459] e1000 0000:00:08.0 eth1: (PCI:33MHz:32-bit) 08:00:27:4e:63:3b
[ 5.165223] e1000 0000:00:08.0 eth1: Intel(R) PRO/1000 Network Connection
[ 5.167781] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.4.0-k
[ 5.168378] igb: Copyright (c) 2007-2014 Intel Corporation.
[ 5.169555] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 5.171038] i2c /dev entries driver
[ 5.174916] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[ 5.175573] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
What does lsmod show?
Does ls /etc/modules.d/ show the e1000e driver? What about 35-e1000?
procd: - init -
is followed immediately by
random: crng init done
and that is the last entry in dmesg
lsmod shows nothing but there are 34 entries in /etc/modules.d including the two you mentioned.
You've got some significant problems then. What is mounted on / (the output of mount would be helpful).
mount shows
/dev/root on / type ext4 (rw,noatime,data=ordered)
proc on /proc type proc (rw,nosuid,nodev,noexec,noatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,noatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime)
/dev/sda1 on /boot type ext4 (rw,noatime,block_validity,delalloc,barrier,user_xa
/dev/sda1 on /boot type ext4 (rw,noatime,block_validity,delalloc,barrier,user_xa
tmpfs on /dev type tmpfs (rw,nosuid,relatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,mode=600,ptmxmode=000)
debugfs on /sys/kernel/debug type debugfs (rw,noatime)
It looks like I've screwed up something big time so I guess it's time to think about reinstalling both OpenWrt and Arch Linux, but I'm not sure of the best way to do that. Installing OpenWrt is straightforward but re-adding Arch might be tricky...
I found the problem... I was using the wrong vmlinuz.
Sorted now.
1 Like
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.