i tried the DHCP trick u mentioned using the following,
host ws246 {
hardware ethernet 00:01:03:e9:4e:88;
fixed-address 192.168.1.246;
if substring (option vendor-class-identifier, 0, 9) = "PXEClient" {
filename "/lts/2.6.16.1-ltsp-2/eb-5.4.2-3c90x.zpxe";
} else if substring (option vendor-class-identifier, 0, 9) = "Etherboot" {
filename "/lts/vmlinuz-2.6.16.1-ltsp-2 ";
#option vendor-encapsulated-options 3c:09:45:74:68:65:72:62:6f:6f:74:ff;
}
}
but i m getting "segemet does not fit in any memory" i think i have to do mknbi tagging, can someone help me in that.
I haven't tried flashing rom yet.
thanks
On 7/14/06, Anselm Martin Hoffmeister <[EMAIL PROTECTED]
> wrote:
Am Donnerstag, den 13.07.2006, 12:37 +0500 schrieb Metal Gear:
> hi all,
> i am trying to boot a workstation using PXE. I am facing a strange
> problem, follwoing is my dhcpd.conf
> ########################################################
> when i try to use only 'filename "/lts/2.6.16.1-ltsp-2/pxelinux.0";'
> only then thin client hangs on "uncompressing the linux...." and when
> i try to use 'filename "/lts/2.6.16.1-ltsp-2/eb-5.4.2-3c90x.zpxe' then
> thin client constantly emits debugging messages. In then end i have to
> use 'filename "/lts/2.6.16.1-ltsp-2/eb-5.4.2-3c90x.zpxe' and then
> restart my dhcp service at that point thin client is constatly
> emitting messages and does no load gnome. In the second step i
> uncomment the line 'filename "/lts/2.6.16.1-ltsp-2/pxelinux.0'
> eventually the thin client goes into gnome. I am using 3 com
> 3C905-TX-M card.
> Any help would be appreciated,
This sounds as if the PXE implementation on your 3com card is broken,
and will not execute "pxelinux". It will run Etherboot though, which in
turn is able to run pxelinux, weird enough.
My first advice is to get rid of the 3com boot loader on that 3c905 -
those boards iirc have a flash memory on it that can be reprogrammed
in-situ, with appropriate software (probably available from 3com). Get
Etherboot (in .zrom format) and burn it into that chip, which should you
get rid of that problem.
If that is not possible, a bit of DHCP magic should do the trick. Every
client software should send a "client identifier" string when requesting
an address. Find out what 3com and Etherboot send (ethereal is your
friend). Use the trick described in
http://www.ltsp.org/documentation/pxe.howto.html
and set that if-else-statement (about three screens worth of text down
that document) to refer to pxelinux.0 and the etherboot....zpxe file,
respectively.
Sorry I'm too lazy to write that down, time to get some sleep. Ask back
if you don't work all that out yourself.
Hth
Anselm
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
