Re: [Thinstation-general] Thinstation and gPXE

[Kobra y. <kob...@ho...>]

Hi Martin,

 

Progress.

 

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

 

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  

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)

The initrd that I found was initrd.devices in the boot-images intrd folder
(is that the correct one?

 

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

(Option Name) 067 Boot file Name (Vendor) Standard  (Value) undionly.kpxe
(Class) 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

 

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

 

Thanking you for all your assistance.

 

Regards

  

Alex

 

 

From: Martin Zwerschke [mailto:Mar...@t-...] 
Sent: 18 February 2011 17:34
To: thi...@li...
Subject: Re: [Thinstation-general] Thinstation and gPXE

 





I have downloaded and extracted Syslinux-4.03.zip to my C drive from
http://www.kernel.org/pub/linux/utils/boot/syslinux/


extract "gpxelinux.0" and put it in the tftp-root directory (I use TFTPD32,
by the way: http://tftpd32.jounin.net). gpxelinux.0  contains both (gPXE and
the pxelinux.0). This way your PXE-clients can afterwards boot from http
(faster!!)  instead of tftp. gPXE-clients can do that natively.

also create a "pxelinux.cfg"-folder inside your tpft-root-directory.

put the (plain text) file "default" into this .cfg-folder. it should contain
at least:

default linux
prompt 0

label linux
 kernel vmlinuz
 append ramdisk_blocksize=4096 initrd=initrd root=/dev/ram1
ramdisk_size=1000000 console=ttyS3 debug=off splash=silent vga=791

or something like that.

Now your clients (PXE-clients as well as gPXE-clients, if you have done the
chaining-trick) should try to load "vmlinuz" and "initrd" from  the
tftp-server's root.
Because I want my clients to get these files not from tftp but from http
(Windows IIS-Server, a Web-Server), i modified the "default"-file:

default linux
prompt 0

label linux
 kernel http://192.168.2.1/vmlinuz.xtp
 append ramdisk_blocksize=4096 initrd=http://192.168.2.1/initrd.bin
root=/dev/ram1 ramdisk_size=1000000 console=ttyS3 debug=off splash=silent
vga=791

I gave these files the extensions ".xtp" and ".bin", because of the
http-server's MIME-types. (It must be "binary/octet-stream"), when I copied
them to IIS-"wwwroot"-directory.

gPXE-clients also can get the "pxelinux.0" from the http-server, if you
configure the boot-server option in your DHCP-Server.




What do I do next? Am I right in assuming that by my http-server, you mean
the 2003 Terminal Server (in my case)?

no, i ment the IIS-Web server (WWW)-server (an apache could do the same
thing).




Also you said "This way both types of client can receive vmlinuz / initrd
from my http-server".Where will I find the vmlinuz/initrd and where do I
install this? i.e does it go into the tftproot folder?

They are part of the SYSLINUX-package, but are also created by TS-O-MATIC or
by the thinstation build-environment (Folder boot-images/PXE)

put them to your "wwwroot" or tftp-root folder (preferable wwwroot of
http-server)


Martin