We have a linux system which currently boots from its internal hard disk, and are trying to convert it to boot from the network.
The ultimate aim is to mount the root partition over NFS; but I thought it better to go one step at a time. What I have done is: * created gPXE disk image using rom-o-matic and written to floppy * used wraplinux to create ELF file from same vmlinuz, initrd and kernel options as used by grub * configured bootp and tftp daemons suitably When the PC boots, it reads the floppy OK, gets its network address etc from bootp, fetches the ELF file OK but then hangs when trying to execute it. I.e. no further output to screen or serial console. Am I right to expect that gPXE should work with a stock kernel and initrd wrapped in this way? Any idea what might be wrong? Or how to investigate further? I've scoured the wiki and asked uncle Google but to no avail. Any help is welcome. Additional info: ELF file was built with this command: wraplinux --elf \ -p "ro root=/dev/VolGroup00/LogVol00 console=tty0 console=ttyS0,9600" \ --initrd=/boot/initrd-2.6.18-1.2798.fc6.img \ -o lin-kg10.nbi \ /boot/vmlinuz-2.6.18-1.2798.fc6 The gPXE version is 0.9.9 (1.0.0 did not work with bootp - reported as FS#75). I downloaded the tarball for 0.9.9 and built with debug enabled, to confirm that it is getting as far as trying to execute. Log from serial console is attached. -- Colin Hogben
gPXE 0.9.9 -- Open Source Boot Firmware -- http://etherboot.org Features: HTTP DNS TFTP AoE iSCSI COMBOOT Multiboot PXE bzImage ELF NBI PXEXT Press Ctrl-B for the gPXE command line... net0: 00:01:29:a4:19:46 on PCI02:00.0 (open) [Link:down, TX:0 TXE:0 RX:0 RXE:0] [Link status: Not connected (0x38086001)] Waiting for link-up on net0... ok DHCP (net0 00:01:29:a4:19:46)XFER 0x1c068 opening (SOCK_DGRAM,AF_INET) socket DHCP 0x1c054 entering discovery state .DHCP 0x1c054 DHCPDISCOVER DHCP 0x1c054 BOOTP from 145.239.198.49:67 (0.0.0.0) for 145.239.198.115 .DHCP 0x1c054 DHCPDISCOVER DHCP 0x1c054 BOOTP from 145.239.198.49:67 (0.0.0.0) for 145.239.198.115 ..DHCP 0x1c054 entering request state DHCP 0x1c054 DHCPREQUEST to 0.0.0.0:67 for 145.239.198.115 DHCP 0x1c054 BOOTP from 145.239.198.49:67 (0.0.0.0) for 145.239.198.115 ok net0: 145.239.198.115/255.255.254.0 gw 145.239.198.3 Booting from filename "/jetlinks/ss/tftpboot/lin-kg10.nbi" XFER 0x1c128 opening tftp URI tftp://145.239.198.49//jetlinks/ss/tftpboot/lin-kg10.nbi.TFTP 0x1c454 requesting "/jetlinks/ss/tftpboot/lin-kg10.nbi" XFER 0x1c46c opening (SOCK_DGRAM,AF_INET) socket TFTP 0x1c454 requesting "/jetlinks/ss/tftpboot/lin-kg10.nbi" .TFTP 0x1c454 requesting "/jetlinks/ss/tftpboot/lin-kg10.nbi" TFTP 0x1c454 using remote port 38268 TFTP 0x1c454 blksize=1432 TFTP 0x1c454 tsize=4118396 Downloader 0x1c114 extending to 4118396 bytes .TFTP 0x1c454 finished with status 0 (No error (0x00000000)) IMAGE 0x1c054 at [7fad6000,7fec377c) registered as lin-kg10.nbi IMAGE 0x1c054 trying type Multiboot IMAGE 0x1c054 could not load as Multiboot: Not an executable image (0x2e838001) IMAGE 0x1c054 trying type script IMAGE 0x1c054 could not load as script: Not an executable image (0x2e028001) IMAGE 0x1c054 trying type COM32 IMAGE 0x1c054 could not load as COM32: Not an executable image (0x2e888001) IMAGE 0x1c054 trying type COMBOOT IMAGE 0x1c054 could not load as COMBOOT: Not an executable image (0x2e878001) IMAGE 0x1c054 trying type bzImage bzImage 0x1c054 missing 55AA signature IMAGE 0x1c054 could not load as bzImage: Not an executable image (0x2e818001) IMAGE 0x1c054 trying type ELF ELF 0x1c054 loading segment [a0,265c) to [10000,125bc,125bc) ELF 0x1c054 found physical entry point at 12018 ELF 0x1c054 loading segment [2660,26a1) to [1ffb0,1fff1,1fff1) ELF 0x1c054 loading segment [26b0,3ed632) to [100000,4eaf82,4eaf82) . ok ELF 0x1c054 starting execution at 12018
_______________________________________________ gPXE mailing list [email protected] http://etherboot.org/mailman/listinfo/gpxe
