Arch Linux

icbrainy

Member

From: England

Registered: 2015-02-09

Posts: 7

Initialising networking subsystem

Howdy folks,

I'm building a custom configuration from scratch and so far I have "all" the bog-standard filesystems in place and without errors or app/kernel panics.

What I'm trying to do now is get some basic "DHCP-only" networking functionality. "ip addr" and "ifconfig -a" only reports the loopback interface (without showing any actual IP addresses). I temporarily installed "lspci" and it's dependencies into the image for diagnostics and it has definetly found available NICs. I have tried it in a VMware player virtual machine and on an 7 year-old disused laptop. I did see subtle changes in listing when I tried with 2, 3 and 4 NICs in VMware just to ensure that I was not getting incorrect readings (with the NICs showing as type 200 devices).

Can anybody guide me (in simple terms and method where possible) in how to make the NICs accessible? I'm using dhcpcd since it's the easiest one to start.

My initrd file system (with "find|sort") is currently...

/bin	-> System
/dev	-> System/dev
/etc	-> System
/init	-> System/init
/lib	-> System
/proc	-> System/proc
/run	-> System/run
/sbin	-> System
/sys	-> System/sys
/System
/System/bash
/System/bin	-> .
/System/dev
/System/dhcpcd
/System/ifconfig
/System/init
/System/ip
/System/ld-linux.so.2
/System/lib	-> .
/System/libblkid.so.1
/System/libc.so.6
/System/libdl.so.2
/System/libmount.so.1
/System/libncursesw.so.5
/System/libpcre.so.3
/System/libprocps.so.3
/System/libpthread.so.0
/System/librt.so.1
/System/libselinux.so.1
/System/libtinfo.so.5
/System/libuuid.so.1
/System/mkdir
/System/mount
/System/mtab	-> proc/self/mounts
/System/proc
/System/run	-> tmp
/System/share	-> .
/System/sys
/System/tmp
/tmp	-> System/tmp
/usr	-> System
/var	-> System

-> : shortcut / symbolic link

...and my startup script...

#!/bin/bash --init-file
mount	proc -t proc -o nodev,noexec,nosuid,ro /proc
mount	sysfs -t sysfs -o nodev,noexec,nosuid,ro /sys
mount	udev -t devtmpfs -o noexec,nosuid,size=1m /dev
mkdir	/dev/pts
mount	devpts -t devpts -o noexec,nosuid,ro /dev/pts
mount	-o mode=0444,remount,ro /dev
mount	tmpfs -t tmpfs -o mode=0666,nodev,noexec,nosuid,size=1m /tmp
mount	-o mode=0555,remount,ro /
dhcpcd

Appreciate your help.

brebs

Member

Registered: 2007-04-03

Posts: 3,742

Re: Initialising networking subsystem

Could use udhcpc (provided by busybox) - see info linked in my sig.

tomk

Forum Fellow

From: Ireland

Registered: 2004-07-21

Posts: 9,839

Re: Initialising networking subsystem

I'm going to assume that "building a custom configuration from scratch" includes compiling your own kernel, in which case it seems you have neglected to compile the drivers for your NICs.

icbrainy

Member

From: England

Registered: 2015-02-09

Posts: 7

Re: Initialising networking subsystem

I'm going to assume that "building a custom configuration from scratch" includes compiling your own kernel, in which case it seems you have neglected to compile the drivers for your NICs.

No, I'm using the kernel that accompanies the 32-bit Arch Linux ISOs. What I'm doing is downloading the pre-made packages from the Arch Linux's Packages section.

Could use udhcpc (provided by busybox) - see info linked in my sig.

I'm getting "siocgifindex no such device". I tried busybox's "find" utility with "/sys/class/net" and only "/sys/class/net/lo" was returned; no mention of eth0 or similar.