[Voyage-linux] PXE boot problem with 0.9-rc2: no IP address configured when no ethdevice kernel parameter

Teco Boot (spam-protected)
Thu Jan 10 02:54:27 HKT 2013


Hi,

I tested the 0.9-rc2 with PXE. I face a problem when using same kernel parameters as I used before, I did not use the ethdevice=eth0.

I copied the 0.9-rc2 files to my PXE server and adjusted PXE config for it. I use Alix6. I have problems with NFS mount. The IP address was released from the NIC, between DHCP&TFTP and mounting NFS. Probably the card was reset by the kernel. But no new IP address is configured after kernel init.

Console logging, slightly cleaned up for readability:

640 KB Base Memory
261120 KB Extended Memory

01F0 Master 044A CF 4GB                                  
Phys C/H/S 7785/16/63 Log C/H/S 973/128/63

Intel UNDI, PXE-2.1 (build 083)
Copyright (C) 1997,1998,1999  Intel Corporation
VIA Rhine III Management Adapter v2.44 (2007/09/17)

CLIENT MAC ADDR: 00 0D B9 21 08 20  
CLIENT IP: 10.1.1.47  MASK: 255.255.255.0  DHCP IP: 10.1.1.1                   
                                                                               
PXELINUX 3.71 Debian-2008-09-06  Copyright (C) 1994-2008 H. Peter Anvin
Voyage Linux PXE boot 
1: Voyage 0.7.0 - 2.6.32 
2: Voyage 0.7.5 - 2.6.38 
3: Voyage 0.8.0 - 3.0.0 - default 
4: Voyage 0.9-rc2 3.6.9 
boot: 4
Loading vmlinuz-3.6.9-voyage................................
Loading initrd.img-3.6.9-voyage-live.................................................................................................ready.
(skipped)
[    0.000000] Kernel command line: initrd=initrd.img-3.6.9-voyage-live boot=live netboot=nfs nfsroot=10.1.1.1:/home/voyage-0.9-rc2 livgetty noautologin console=ttyS0,9600n8
(skipped)
[    2.001833] via_rhine: v1.10-LK1.5.0 2010-10-09 Written by Donald Becker
(skipped)
[    3.599207] via-rhine 0000:00:09.0: eth0: VIA Rhine III (Management Adapter) at 0xe0000000, 00:0d:b9:21:08:20, IRQ 10
[    3.727013] via-rhine 0000:00:09.0: eth0: MII PHY found at address 1, status 0x786d advertising 01e1 Link c5e1
(skipped)
[    5.537914] via-rhine 0000:00:0a.0: eth1: VIA Rhine III (Management Adapter) at 0xe0040000, 00:0d:b9:21:08:21, IRQ 11
[    5.665744] via-rhine 0000:00:0a.0: eth1: MII PHY found at address 1, status 0x7849 advertising 05e1 Link 0000
(skipped)
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... 
Waiting for ethernet card(s) up... If this fails, maybe the ethernet card is not supported by the kernel 3.6.9-voyage?
Looking for a connected Ethernet interface ... eth0 ? eth1 ?
Connected eth0 found
Using timeout of 15 seconds for network configuration.
Begin: Trying netboot from 10.1.1.1:/home/voyage-0.9-rc2 ... 
Begin: Trying nfsmount -o nolock -o ro  10.1.1.1:/home/voyage-0.9-rc2 /live/image ... 
connect: Network is unreachable
connect: Network is unreachable
NFS over TCP not available from 10.1.1.1
connect: Network is unreachable
connect: Network is unreachable
NFS over TCP not available from 10.1.1.1
connect: Network is unreachable
(skipped)

      .''`.  
     : :'  : 
     `. `'`  
       `-      This Debian Live image failed to boot.
0m  BOOT FAILED!
  Please file a bug against the 'live-boot' package or email the Debian
  Live mailing list at <debian-live at lists.debian.org>, making sure to note the
  exact version, name and distribution of the image you were attempting to boot.

  The file /boot.log contains some debugging information but booting with the
  debug command-line parameter will greatly increase its verbosity which is
  extremely useful when diagnosing issues.

  live-boot will now start a shell. The error message was:

    Unable to find a live file system on the network


BusyBox v1.20.2 (Debian 1:1.20.0-7) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off
(initramfs) 


No IP addres is configured:

(initramfs) ifconfig
eth0      Link encap:Ethernet  HWaddr 00:0D:B9:21:08:20  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:14 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1227 (1.1 KiB)  TX bytes:0 (0.0 B)
          
eth1      Link encap:Ethernet  HWaddr 00:0D:B9:21:08:21  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)



I can configure an IP address and mount by hand:

(initramfs) ifconfig eth0 10.1.1.47
(initramfs)  ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:0D:B9:21:08:20  
          inet addr:10.1.1.47  Bcast:10.255.255.255  Mask:255.0.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1014 (1014.0 B)  TX bytes:0 (0.0 B)

(initramfs) nfsmount -o nolock -o ro  10.1.1.1:/home/voyage-0.9-rc2 /live/image
(initramfs) mount
rootfs on / type rootfs (rw)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=31091,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620)
tmpfs on /run type tmpfs (rw,nosuid,relatime,size=51040k,mode=755)
10.1.1.1:/home/voyage-0.9-rc2 on /live/image type nfs (ro,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,nolock,proto=tcp,port=2049,timeo=7,retrans=3,sec=sys,local_lock=all,addr=10.1.1.1)
(initramfs) 



With 0.8.0 there is no problem. 
I fixed issue for 0.9-rc2 with the ethdevice parameter, but then I loose some flexibility. 

[    0.000000] Kernel command line: initrd=initrd.img-3.6.9-voyage-live boot=live netboot=nfs ethdevice=eth0 nfsroot=10.1.1.1:/home/voyage-0.9-rc2 livgetty noautologin console=ttyS0,9600n8
(skipped)
Waiting for ethernet card(s) up... 
If this fails, maybe the ethernet card is not supported by the kernel 3.6.9-voyage?
Looking for a connected Ethernet interface ... eth0 ? eth1 ?
Connected eth0 found
Using timeout of 15 seconds for network configuration.
IP-Config: eth0 hardware address 00:0d:b9:21:08:20 mtu 1500 DHCP RARP
IP-Config: eth0 complete (dhcp from 10.1.1.1):
 address: 10.1.1.47        broadcast: 10.1.1.255       netmask: 255.255.255.0   
 gateway: 0.0.0.0          dns0     : 0.0.0.0          dns1   : 0.0.0.0         
 domain : example.org                                                     
 rootserver: 10.1.1.1 rootpath: 
 filename  : pxelinux.0
Creating /etc/resolv.conf
Begin: Trying netboot from 10.1.1.1:/home/voyage-0.9-rc2 ... 
Begin: Trying nfsmount -o nolock -o ro  10.1.1.1:/home/voyage-0.9-rc2 /live/image ... done.
Begin: Running /scripts/live-realpremount ... done.
Begin: Mounting "/live/image/live/filesystem.squashfs" on "//filesystem.squashfs" via "/dev/loop0" ... done.
mount: mounting /overlay on /root/live/overlay failed: No such file or directory
Warning: Unable to move or bind /overlay to /root/live/overlay
done.
Begin: Configuring fstab ... done.
Begin: Preconfiguring networking ... done.



Maybe just file this issue as known issue? 
Try to find out what goes wrong?
I browsed thru the /lib/live/boot/ scripts, run by /lib/live/boot. There is something wrong getting the IP address with DHCP. In netbase.sh, bottom, it seams dhcp is disabled. Idea's why?



Thanks,
Teco





More information about the Voyage-linux mailing list