Find the answer to your Linux question:
Results 1 to 3 of 3
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1

    kernel 2.6.31 not detecting ethernet device

    I'm creating a kernel image using kernel version 2.6.31 for sbc8641d board. When I boot the kernel on target, it throughs the error saying IP-Config: device 'eth0' not found. what is the reason? How can I debug this? In my .dtb image I have specified 'gianfar' as the driver to load. But it does not seem to be calling this.

  2. #2
    hello and welcome!

    what is the hardware exactly? post the output of the lspci command. in particular, you'd be interested in this:
    lspci|egrep -i 'net|eth'
    from there, you should be able to get the vendor/product IDs and then look up the support for the device in the kernel documentation.

    if you believe your device is already supported and you know the name of the driver, you can try to manually load it, e.g.:
    modprobe gianfar
    check the output of dmesg.

  3. #3
    Here is the target output:

    => bootm 1000000 - 1600000
    ## Booting image at 01000000 ...
    Image Name: Linux-
    Image Type: PowerPC Linux Kernel Image (gzip compressed)
    Data Size: 1987200 Bytes = 1.9 MB
    Load Address: 00000000
    Entry Point: 00000000
    Verifying Checksum ... OK
    Uncompressing Kernel Image ... OK
    Booting using flat device tree at 0x1600000
    -> early_init_devtree(c1600000)
    search "chosen", depth: 0, uname:
    search "chosen", depth: 1, uname: cpus
    search "chosen", depth: 2, uname: PowerPC,8641@0
    search "chosen", depth: 1, uname: memory
    search "chosen", depth: 1, uname: soc8641@f8000000
    search "chosen", depth: 2, uname: mdio@24520
    search "chosen", depth: 3, uname: ethernet-phy@1f
    search "chosen", depth: 3, uname: ethernet-phy@0
    search "chosen", depth: 3, uname: ethernet-phy@1
    search "chosen", depth: 3, uname: ethernet-phy@2
    search "chosen", depth: 2, uname: ethernet@24000
    search "chosen", depth: 2, uname: ethernet@25000
    search "chosen", depth: 2, uname: ethernet@26000
    search "chosen", depth: 2, uname: ethernet@27000
    search "chosen", depth: 2, uname: serial@4500
    search "chosen", depth: 2, uname: serial@4600
    search "chosen", depth: 2, uname: pic@40000
    search "chosen", depth: 1, uname: chosen
    Looking for initrd properties...
    initrd_start=0x0 initrd_end=0x0
    Command line is: console=ttyS0,115200 mem=512M ip= 5.255.0:sbc8641d:eth0:off rw root=/dev/nfs nfsroot=
    dt_root_size_cells = 1
    dt_root_addr_cells = 1
    memory scan node memory, reg size 8, data: 0 20000000 2 1,
    - 0 , 20000000
    memory limit = 0x20000000
    Phys. mem: 20000000
    -> move_device_tree
    <- move_device_tree
    Scanning CPUs ...
    boot cpu: logical 0 physical 0
    <- early_init_devtree()
    Using SBC8641D machine description
    Total memory = 512MB; using 1024kB for hash table (at cff00000)
    Linux version (TCS@localhost) (gcc version 4.5.4 (Buildroot 2012.11.1) ) #5 SMP PREEMPT Fri Mar 22 00:27:16 IST 2013
    -> unflatten_device_tree()
    size is f14, allocating...
    unflattening dffff0e8...
    fixed up name for ->
    fixed up name for cpus -> cpus
    fixed up name for PowerPC,8641@0 -> PowerPC,8641
    fixed up name for memory -> memory
    fixed up name for soc8641@f8000000 -> soc8641
    fixed up name for mdio@24520 -> mdio
    fixed up name for ethernet-phy@1f -> ethernet-phy
    fixed up name for ethernet-phy@0 -> ethernet-phy
    fixed up name for ethernet-phy@1 -> ethernet-phy
    fixed up name for ethernet-phy@2 -> ethernet-phy
    fixed up name for ethernet@24000 -> ethernet
    fixed up name for ethernet@25000 -> ethernet
    fixed up name for ethernet@26000 -> ethernet
    fixed up name for ethernet@27000 -> ethernet
    fixed up name for serial@4500 -> serial
    fixed up name for serial@4600 -> serial
    fixed up name for pic@40000 -> pic
    <- unflatten_device_tree()
    CPU maps initialized for 1 thread per core
    console [udbg0] enabled
    setup_arch: bootmem
    SBC8641 board from Wind River
    arch: exit
    Zone PFN ranges:
    DMA 0x00000000 -> 0x00020000
    Normal 0x00020000 -> 0x00020000
    Movable zone start PFN for each node
    early_node_map[1] active PFN ranges
    0: 0x00000000 -> 0x00020000
    Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048
    Kernel command line: console=ttyS0,115200 mem=512M ip= 5.255.0:sbc8641d:eth0:off rw root=/dev/nfs nfsroot=
    PID hash table entries: 2048 (order: 11, 8192 bytes)
    Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
    Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
    Memory: 514176k/524288k available (3820k kernel code, 9704k reserved, 128k data, 106k bss, 184k init)
    Kernel virtual memory layout:
    * 0xffffe000..0xfffff000 : fixmap
    * 0xfdffe000..0xfe000000 : early ioremap
    * 0xe1000000..0xfdffe000 : vmalloc & ioremap
    mpic: Setting up MPIC " MPIC " version 1.2 at f8040000, max 2 CPUs
    mpic: ISU size: 256, shift: 8, mask: ff
    mpic: Initializing for 256 sources
    clocksource: timebase mult[2800000] shift[22] registered
    Console: colour dummy device 80x25
    Security Framework initialized
    Mount-cache hash table entries: 512
    Brought up 1 CPUs
    NET: Registered protocol family 16

    rstcr compatible register does not exist!
    PCI: Probing PCI hardware
    bio: create slab <bio-0> at 0
    NET: Registered protocol family 2
    IP route cache hash table entries: 16384 (order: 4, 65536 bytes)
    TCP established hash table entries: 65536 (order: 7, 524288 bytes)
    TCP bind hash table entries: 65536 (order: 7, 786432 bytes)
    TCP: Hash tables configured (established 65536 bind 65536)
    TCP reno registered
    NET: Registered protocol family 1
    VFS: Disk quotas dquot_6.5.2
    Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
    msgmni has been set to 1005
    alg: No test for stdrng (krng)
    io scheduler noop registered
    io scheduler anticipatory registered
    io scheduler deadline registered
    io scheduler cfq registered (default)
    Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
    serial8250.0: ttyS0 at MMIO 0xf8004500 (irq = 42) is a 16550A
    console handover: boot [udbg0] -> real [ttyS0]
    serial8250.0: ttyS1 at MMIO 0xf8004600 (irq = 2 is a 16550A
    brd: module loaded
    Fixed MDIO Bus: probed
    console [netcon0] enabled
    netconsole: network logging started
    mice: PS/2 mouse device common for all mice
    i2c /dev entries driver
    md: linear personality registered for level -1
    md: raid0 personality registered for level 0
    md: raid1 personality registered for level 1
    md: raid10 personality registered for level 10
    md: multipath personality registered for level -4
    md: faulty personality registered for level -5
    device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised:
    TCP cubic registered
    NET: Registered protocol family 17
    RPC: Registered udp transport module.
    RPC: Registered tcp transport module.
    IP-Config: Device `eth0' not found.
    md: Waiting for all devices to be available before autodetect
    md: If you don't use raid, use raid=noautodetect
    md: Autodetecting RAID arrays.
    md: Scanned 0 and added 0 devices.
    md: autorun ...
    md: ... autorun DONE.
    Looking up port of RPC 100003/2 on
    rpcbind: server not responding, timed out
    Root-NFS: Unable to get nfsd port number from server, using default
    Looking up port of RPC 100005/1 on
    rpcbind: server not responding, timed out
    Root-NFS: Unable to get mountd port number from server, using default
    Root-NFS: Server returned error -5 while mounting /opt/nfsRootfs
    VFS: Unable to mount root fs via NFS, trying floppy.
    VFS: Cannot open root device "nfs" or unknown-block(2,0)
    Please append a correct "root=" boot option; here are the available partitions:
    Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
    Rebooting in 180 seconds..

    Why it is not detecting 'eth0' device?

    Target is Wind River sbc8641d board. I am passing the information of driver through DTB file.

  4. $spacer_open

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts