Hi, do you know of a reason why I can't seem to load the kernel from the redhat 8.0 pxeboot using pxelinux? Same everything but with the kernels from 7.2 and 7.3 work fine. More details: - dhcp fine - loads pxelinux.0 fine - is able to get the pxelinux.cfg/<my config> - starts to get the kernel image vmlinuz... - stops after receiving only a few blocks over tftp (system hangs) - next step would be to transfer the initrd but it doesn't get here Thanks, Mike --------------------- Mike Bethune, SCSA, SCNA, LCP, LCA Senior UNIX Engineer Fusepoint Managed Services Inc. 2323 - 595 Burrard Street P.O. Box 49336, Vancouver, BC, V7X 1L4 T. 604.687-7757 x303 F. 604.687.7761 Email:mike.bethune at fusepoint.com Web : www.fusepoint.com
Hello ! Could we have a look at your pxelinux.cfg/<my config> file ? Or what's the name of your kernel ? I have had some problems while loading kernel named 'kernel.img' (with isolinux) When i renamed it to 'bzImage' and changed isolinux.cfg, it worked. Maybe it's something like that... sylvain ___________________________________________________________________ Haut D?bit: Modem offert soit 150,92 euros rembours?s sur le Pack eXtense de Wanadoo ! Profitez du Haut D?bit ? partir de 30 euros/mois : http://www.ifrance.com/_reloc/w
> Hello ! > > Could we have a look at your pxelinux.cfg/<my config> file ?It's the same config file I use to successfully pxe boot the same machine using redhat's prebuilt pxeboot kernels in 7.2 or 7.3, the only difference being the names of the kernel and the initrd image: default linux serial 0,9600n8 label linux kernel vmlinuz-8.0 append initrd=initrd.img-8.0 lang= devfs=nomount nofb ramdisk_size=9216 console=ttyS0,9600 ks=nfs:10.210.1.11:/kickstart/ks.cfg ksdevice=eth0 I don't understand why this won't work when the only difference is the kernel, and I've verified this same kernel boots fine on a floppy. For some reason it won't load it over tftp. I didn't try renaming it but that didn't strike me as being an issue since "vmlinuz-7.3" is ok. Thanks, Mike
> > I don't understand why this won't work when the only > difference is the kernel, and I've verified this same kernel > boots fine on a floppy. > > For some reason it won't load it over tftp. I didn't try > renaming it but that didn't strike me as being an issue since > "vmlinuz-7.3" is ok. > > > > What does your tftpd logs look like when you run tftpd with -v -v -v? >The tftp logs look as they do for a successful boot (only it stops at the kernel): Oct 21 15:28:05 x in.tftpd[9044]: [ID 810593 daemon.notice] RRQ from 10.240.1.210 filename pxelinux.0 Oct 21 15:28:05 x in.tftpd[9044]: [ID 142274 daemon.warning] tftp: client does not accept options Oct 21 15:28:05 x in.tftpd[9045]: [ID 810593 daemon.notice] RRQ from 10.240.1.210 filename pxelinux.0 Oct 21 15:28:05 x in.tftpd[9046]: [ID 810593 daemon.notice] RRQ from 10.240.1.210 filename pxelinux.cfg/0AF001D2 Oct 21 15:28:07 x in.tftpd[9047]: [ID 810593 daemon.notice] RRQ from 10.240.1.210 filename vmlinuz-8.0 This is as far as it gets though, only a few blocks of the kernel before crapping out: TFTP Read "vmlinuz-8.0" (octet) UDP D=57218 S=61995 LEN=23 TFTP Ack block 0 TFTP Data block 1 (512 bytes) TFTP Data block 1 (512 bytes) TFTP Data block 1 (512 bytes) TFTP Data block 1 (512 bytes) TFTP Data block 1 (512 bytes) TFTP Data block 1 (512 bytes) The console on the server trying to load it spews this: . I ~[ c. I ~[ c. I ~[ c. I ~[ c. I ~[ c. I ~[ c. I ~[ c. I ~[ c. I ~[ c. I ~[ c. I ~[ c. I ~[ c. I ~[ c. I ~[ c. I ~[ c. I ~[ c. I ~[ c. I ~[ c. I ~[ c. I ~[ c. I ~[ c. I ~[ c. I ~[ c. I ~[ c. etc. Thanks, Mike