IP-Config: No network devices available.

From: Shaun Jackman
Date: Tue Jul 18 2006 - 14:16:54 EST

I've compiled the smc91x driver into my kernel (CONFIG_SMC91X=y), but
the boot process complains `IP-Config: No network devices available.'
I tried using the netdev kernel parameter to start the smc91x driver
(netdev=1,0x300,eth0 and ether=1,0x300,eth0), but I don't see any
output on the console from the smc91x driver. The driver doesn't
appear to be starting. How do I start the smc91x driver? I'm compiling
linux. for ARM nommu (Atmel AT91).


Linux version (sjackman@xxxxxxxxxxxxxxxxxxxxx) (gcc
version 4.2.0 20060629 (experimental)) #28 Tue Jul 18 12:07:39 MDT
CPU: Atmel-AT91M40xxx [14080044]
Machine: ATMEL EB01
Memory management: Non-Paged(unused/noMMU)
CPU0: D no cache
Built 1 zonelists
Kernel command line: root=/dev/ram initrd=0x15a0000,64K keepinitrd
ether=1,0x300,eth0 ip=dhcp
PID hash table entries: 16 (order: 4, 256 bytes)
Dentry cache hash table entries: 256 (order: -2, 1024 bytes)
Inode-cache hash table entries: 128 (order: -3, 512 bytes)
Memory: 1MB = 1MB total
Memory: 912KB available (858K code, 79K data, 4K init)
Mount-cache hash table entries: 512
NET: Registered protocol family 16
DCC: JTAG1 Serial emulation driver driver $Revision: 1.1 $
ttyJ0 at MMIO 0x12345678 (irq = 0) is a DCC
io scheduler noop registered
NET: Registered protocol family 2
IP route cache hash table entries: 16 (order: -6, 64 bytes)
TCP established hash table entries: 64 (order: -4, 256 bytes)
TCP bind hash table entries: 64 (order: -4, 256 bytes)
TCP: Hash tables configured (established 64 bind 64)
TCP reno registered
TCP bic registered
NET: Registered protocol family 17
IP-Config: No network devices available.
Freeing init memory: 4K
BINFMT_FLAT: Loading file: /init
Mapping is 1038000, Entry point is 44, data_start is 80
Load /init: TEXT=1038040-1038080 DATA=1038084-10380c4 BSS=10380c4-10380d4
Hello, world!
Kernel panic - not syncing: Attempted to kill init!
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/