Menu

PXE boot on Dell R620

Help
2013-06-25
2013-07-02
  • Pavel Gurkov

    Pavel Gurkov - 2013-06-25

    It just won`t work, though it works perfectly with Dell R410 servers. I think it has something to do with ethernet controller (Broadcom 5720 Base-T) as the boot hangs just after messages

    tg3 0000:01:00.0 eth0: Link is up at 1000 Mbps, full duplex
    tg3 0000:01:00.0 eth0: Flow control is on for TX and on for RX
    tg3 0000:01:00.0 eth0: EEE is disabled
    IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

    etc. Then it just waits for something, but does nothing.
    I've tried several Clonezillas, old, stable and unstable, based on Debian as well as based on Ubuntu, but had no luck at all, everything hangs at the same point. I've also tried to use kernel that we actually use in our environment.
    Some people suggested I should inject proper firmwares in initrd image, but 1) as I can see, some tg3 firmwares are already there (given latest Ubuntu-based versions); 2) I have no idea where to get them, as on official broadcom website there are just drivers built as kernel modules.
    Could anyone help me out?

     

    Last edit: Pavel Gurkov 2013-06-25
  • derMori

    derMori - 2013-06-27

    I've nearly the same Problem.

    [ 8.477373] r8169 0000:04:00.0 eth0: link down
    [ 8.478164] r8169 0000:04:00.0 eth0: link down
    [ 8.478985] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
    Begin: Running /scripts/live-premount ... Waiting for ethernet card(s) up... If it fail, maybe the ethernet card is not supported ky the kernel 3.8.0-19-generic?
    done.
    [ 10.348346] r8169 0000:04:00.0 eth0: link up
    [ 10.349250] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

    I run two different PXE Systems. A Windows 2008 WDS based one whitch works well and a openSUSE. Only the openSUSE caused this problem the Windows works wunderfull.

    I think the DHCP is the problem but I've no idea how to fix it.

     
  • derMori

    derMori - 2013-06-28

    I fixed it. The problem was caused by a misconfiguration of the DHCPv4 Server. With the following configuration it works.

    max-lease-time 7200;
    default-lease-time 600;
    allow booting;
    allow bootp;

    subnet 192.168.0.0 netmask 255.255.255.0 {
    pool {
    range 192.168.0.11 192.168.0.200;
    default-lease-time 180;
    max-lease-time 360;
    server-name "192.168.0.1";
    next-server 192.168.0.1;
    filename "pxelinux.0";
    }
    }

     
    • Pavel Gurkov

      Pavel Gurkov - 2013-07-02

      I`ve solved mine by adding "live-netdev=eth1 ethdevice=eth1 ethdevice-timeout=10" to kernel parameters. The thing is that Clonezilla was trying to get filesystem.squashfs using wrong NIC, and never switched to another one.

       

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.