Re: [Thinstation-general] Thinstation and gPXE
Brought to you by:
doncuppjr
|
From: Martin Z. <Mar...@t-...> - 2011-02-18 23:25:42
|
> The loop is stopped and no more cannot "load image" error message. > > It goes through and load up and get an ip address, give a > BOOTIF=01......, then > > SYSUUID= ffffff....... > > Then I get; > > TFTP prefix: > > Trying to load: pxelinux.cfg/default ok > > Could not find kernel image: vmlinuz > > Boot: > > Then cursor starts blinking and stops there. Does not go beyond the > "boot:" prompt > does not find it, cause it is not there... Two things I need to mention to you; The first is that what I find in the Thinstation\Thinstation-2.2\Thinstation-2.2\kernel folder is a *_vmlinuz-2.6.16.5_* that's not what you need. > > I copied and pasted this straight into my tftpdroot folder and it is > showing as vmlinuz-2.6.16.5 (i.e with the numbers) > you need a "vmlinuz" without these numbers. (But I do not think, removing the extension will do: you need the "vmlinuz", that thinstation creates for you. look in this folder after successful "./build": "thinstation-2.2.2f/boot-images/syslinux" There you find "vmlinuz" and "initrd". > The initrd that I found was initrd.devices in the boot-images intrd > folder (is that the correct one? > No, it must be "initrd" without ".devices" -> look at "Thinstation-2.2.2f/boot-images/syslinux". But it should be in "boot-images/intrd" folder as well. If not, your "./build"-command was not successful. You could also use TS-O-MATIC to create this files, if you can't get build to run. > Secondly, my DHCP user defined scope option 067 have the following > entries; > > (Option Name) 067 Boot file Name (Vendor) Standard (Value) > gpxelinux.0 (Class) gPXE > Should be "pxelinux.0" for class gPXE (that's the bootloader, that parses the config file (e.g. "default") in folder "pxelinux.cfg" thus realising a little boot-menu, if you wish). In the chainload-document they made gPXE boot a script instead) > (Option Name) 067 Boot file Name (Vendor) Standard (Value) > undionly.kpxe (Class) NONE > And gpxelinux.0 for NONE > I think that I have input some wrong settings in here. By the way, the > set up is correct as per the instructions from the chain how to > The chainload-instructions were written, before gpxelinux.0 (the mixture of the gPXE-module and the pxelinux.0-bootloader was created by it's authors), but you can use the module as well. > > Below is the output from the default text file > > default linux > > prompt 0 > > label linux > > kernel vmlinuz > > append ramdisk_blocksize=4096 initrd=initrd root=/dev/ram0 > ramdisk_size=524288 console=ttyS3 acpi=off > This way files are searched on tftp-server; "use "initrd=http://..../initrd.bin" for www-server |