Thread: RE: [Etherboot-users] pxe boot ?
Brought to you by:
marty_connor,
stefanhajnoczi
Menu
▾
▴
etherboot-users
|
From: Timothy L. <tim...@al...> - 2005-09-19 12:31:20
|
> that I looked up on google that indicated that PXE will not=20 > accept boot images larger than 512KB ! this is an old machine=20 > with no possibility of getting the PXE upgraded to allow=20 > larger images. So i took a 500KB file and pointed that at the=20 As far as I know, no PXE implementation (maybe Etherboot's) allows you to go over a certain max size. You need to read: http://wiki.etherboot.org/pmwiki.php/Main/UsingPXE There is a link there to Marty's doc that he wrote some time ago on the subject that is required reading for anyone trying to figure out how to PXE boot. Tim ********************************************************************** This E-mail message (including attachments, if any) is intended for the use= of the individual or entity to which it is addressed and may contain infor= mation that is privileged, proprietary, confidential and exempt fromdisclos= ure. If you are not the intended recipient, you are notified thatany dissem= ination, distribution or copying of this communication is strictly prohibit= ed. If you have received this communication in error, please notify the sen= der and erase this E-mail message immediately.=20 Le present message electronique (y compris les pieces qui y sont annexees, = le cas echeant) s'addresse au destinataire indique et peut contenir des ren= seignements de caractere prive ou confidentiel. Si vous n'etes pas le desti= nataire de ce document, nous vous signalons qu'il est strictement interdit = de le diffuser, de le distribuer ou de le reproduire. Si ce message vous a = ete transmis par erreur, veuillez en informer l'expediteur et le supprimer= immediatement. |
|
From: Roy W. <roy...@ya...> - 2005-10-19 11:46:22
|
Hello, ok, in summary, I have tftpd32.exe running on a Windows XP box. DHCP is turned off on my router so that tftpd32 controls the DHCP for the PXEBOOT. I point the DHCP in tftp32d to provide pxelinux.0 to pxe clients, and this works in that, I pxelinux.0 is found and boots. The problem seems to be menu.c32 and getting memlinux to go for a new DOS image (or any other image). maybe. I'm using the default syslinux distribution for win32. end result, big failure. I've then used Cristian's great default script (note, pxelinux only talk in abstract terms, terrible documentation, no examples), so I've used Cristian's script to make my pxelinux.cfg folder. end result, failure. Cristian then gave me his menu.c32 and memlinux (as again, pxelinux provide *no* examples of this in Windows and these are not compiled for win32 in the win32 distribution. Surely a great way to cause people waste time for months is to release incomplete distributions for an environment that are fundamentally broken, which this is). end result, this failed also, with no difference between this attempt and previous attempt. Please, has someone got a working pxelinux boot system on windows xp with tftpd32.exe ? There is that page that describes how to setup tftpd32 that I was pointed to from this list but that only provides useful information up to the dhcp boot part. it does not help at all with pxelinux / default / menu.c32 / memlinux. i.e. it doesn't help to get a boot image to boot at all. please help ? somebody must have done this somewhere right ? Once I can get a simple DOS image booting across the network, I can then start to learn all the in's and out's of pxelinux, but without any basic working system, I can't do anything (oh, for useful documentation with examples ! I'll gladly write it myself for Win32 if you guys can help me to get this working). Thanks, Roy. > > pxelinux.cfg/default file > > > > <file> > > default menu.c32 > > prompt 0 > > timeout 0 > > > > menu title pxelinux boot menu > > > > label DOS > > menu label DOS > > kernel ::/memdisk > > append initrd=::/dosboot.img > > </file> > > > > > > > > Output from PXE Client : > > > > Found PXENV+ structure > > PXE API version is 0063 > > Old PXE API detected, using PXENV+ structure > > UNDI data segment at: 9880 > > UNDI data segment size: 5520 > > UNDI code segment at: 9DD2 > > UNDI code segment size: 1BD0 > > PXENV entry point found (we hope) at 9140:0092 > > My IP address seems to be 0A000032 10.0.0.50 > > ip=10.0.0.50:10.0.0.10:10.0.0.1:255.255.255.0 > > TFTP prefix: > > Trying to load: pxelinux.cfg/01-00-00-0e-b0-a0-70 > > Trying to load: pxelinux.cfg/0A000032 > > Trying to load: pxelinux.cfg/0A00003 > > Trying to load: pxelinux.cfg/0A0000 > > Trying to load: pxelinux.cfg/0A000 > > Trying to load: pxelinux.cfg/0A0 > > Trying to load: pxelinux.cfg/0A > > Trying to load: pxelinux.cfg/0 > > Trying to load: pxelinux.cfg/default > > Could not find kernel image: linux > > boot: ___________________________________________________________ To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com |
|
From: Marty C. <md...@et...> - 2005-10-19 15:04:27
|
On Oct 19, 2005, at 7:45 AM, Roy Wiseman wrote:
> Hello,
> ok, in summary, I have tftpd32.exe running on a
> Windows XP box. DHCP is turned off on my router so
> that tftpd32 controls the DHCP for the PXEBOOT. I
> point the DHCP in tftp32d to provide pxelinux.0 to pxe
> clients, and this works in that, I pxelinux.0 is found
> and boots.
I'm glad you got that far.
> The problem seems to be menu.c32 and getting memlinux
> to go for a new DOS image (or any other image). maybe.
Sounds like you should join the SYSLINUX mailing list and ask there.
I did a google search for:
tftpd32 pxe boot windows
And found a lot of links that looks interesting.
Here is one that seemed to have specific, practical, information.
http://pxes.sourceforge.net/howtos/ms_only_environment/
> ...
> Please, has someone got a working pxelinux boot system
> on windows xp with tftpd32.exe ? There is that page
> that describes how to setup tftpd32 that I was pointed
> to from this list but that only provides useful
> information up to the dhcp boot part. it does not help
> at all with pxelinux / default / menu.c32 / memlinux.
> i.e. it doesn't help to get a boot image to boot at
> all.
> please help ? somebody must have done this somewhere
> right ?
The SYSLINUX list is probably the first and best place for you to be
asking this kind of thing. If they say that Etherboot's PXE
implementation is somehow not working properly, then we could debug
things here, but so far, it looks PXELINUX specific.
> Once I can get a simple DOS image booting across the
> network, I can then start to learn all the in's and
> out's of pxelinux, but without any basic working
> system, I can't do anything (oh, for useful
> documentation with examples ! I'll gladly write it
> myself for Win32 if you guys can help me to get this
> working).
This seems like sound reasoning. One thing I would recommend is
trying to do this on a Linux system, which is much more well-
documented (and there are probably a lot more people who can help you
with it), then see if there is something different between the two
systems (tftpd vs. win32tftpd, dhcpd vs. the windows equivalent, etc.)
If you provide enough specific information for those of us who have a
windows machine around to duplicate your setup, some of us will be
willing to do this, I'm sure. (others may say they don't do windows,
but don't let that bother you :)
> Roy.
Thanks for writing. I encourage you to continue, and to rely on the
Etherboot and SYSLINUX mailing lists. I would be very interested in
getting a writeup when you get this working.
Marty
--
Try: http://rom-o-matic.net/ to make Etherboot images instantly.
Name: Marty Connor
US Mail: Entity Cyber, Inc.; P.O. Box 391827;
Cambridge, MA 02139; USA
Voice: (617) 491-6935; Fax: (617) 491-7046
Email: md...@et...
Web: http://www.etherboot.org/
|
|
From: Roy W. <roy...@ya...> - 2005-10-19 15:36:42
|
> Sounds like you should join the SYSLINUX mailing > list and ask there. I never knew it existed ! I'll get on there right away thanks ... :) > > I did a google search for: > > tftpd32 pxe boot windows > > And found a lot of links that looks interesting. > > Here is one that seemed to have specific, practical, > information. > > http://pxes.sourceforge.net/howtos/ms_only_environment/ I've seen this before, but it doesn't help past the dhcp ... it helps *nothing* to actually make pxelinux rrun <doh!> ... ok, only 6-12 months trying to get this working ... seems crazy as this is such useful technology, why o why do those syslinux people have to write unintelligible documentation as if they were unix guys ... oh, it's cos they is unix guys right ? ;o) ("before starting with pxelinux please read the 40 pages of syslinux documentation, then reference the manual of some other thing, then look at another 20 pages of some other intelligible documentation. once you have done that please continue with this document" and I'm not kidding here either, this is *exactly* what they do. I cannot think of a better way to dissaude people from using your technology. alternatively : "here is a useful 5 page document with example scripts to get you up and running in 15-20 minutes" ... wow, now that would really be something ...) ok, over to the syslinux user list with my questions. i'm a little scared of the answers i'll get ... :-s ___________________________________________________________ How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com |
|
From: Marty C. <md...@et...> - 2005-10-19 15:50:50
|
On Oct 19, 2005, at 11:36 AM, Roy Wiseman wrote:
> ...
> ok, over to the syslinux user list with my questions.
> i'm a little scared of the answers i'll get ... :-s
Well, the author of SYSLINUX is on the Etherboot list, and they're
quite helpful there.
In any case, please let us know how it goes. I'd really like to know
how you get this working, and add it to the wiki.
Thanks,
Marty
--
Try: http://rom-o-matic.net/ to make Etherboot images instantly.
Name: Marty Connor
US Mail: Entity Cyber, Inc.; P.O. Box 391827;
Cambridge, MA 02139; USA
Voice: (617) 491-6935; Fax: (617) 491-7046
Email: md...@et...
Web: http://www.etherboot.org/
|
|
From: Alexander H. <mai...@gm...> - 2005-10-19 16:20:51
|
> In any case, please let us know how it goes. I'd really like to know > how you get this working, and add it to the wiki. I will download tftp32.exe today and write a corresponding article. Alex |
|
From: Alexander H. <mai...@gm...> - 2005-10-19 17:51:04
|
> If so then great, I was going to write something but > if you are keen to do it then excellent. I'd gladly > show you what I've got, but basically, I get syslinux > (which is supposed to include pxelinux and memlinux) > and use tftpd32 (which we know is pxelinux compatible, > this is guarenteed), and pxelinux starts to boot, but > menu.x32 and memlinux are fatally broken and there are > no sample scripts for "default" to allow booting a DOS > or other image. for pxelinux booting on windows > environments, it's basically just a big mess. > > Let me know if you get it working, I'd appreciate it > so much, I really want this tech to work, and it's so > frustrating that it's all broken :o( pxelinux, memdisk and menu.c32 work great for me (using an ISC DHCP server and the tftp server by hpa). tftpd32 is the only new part for me. Alex |
|
From: Roy W. <roy...@ya...> - 2005-10-19 18:03:37
|
well, could you show me how please Alexander ? that's all I've really been after for these past few months. I don't care much what dhcp / tftp server i use, i just want it to work. any chance you could zip up what you have and let me have it also ? then i can see it working and then take apart things for a look to see how it all works ? All the best, Roy. --- Alexander Heinz <mai...@gm...> wrote: > > If so then great, I was going to write something > but > > if you are keen to do it then excellent. I'd > gladly > > show you what I've got, but basically, I get > syslinux > > (which is supposed to include pxelinux and > memlinux) > > and use tftpd32 (which we know is pxelinux > compatible, > > this is guarenteed), and pxelinux starts to boot, > but > > menu.x32 and memlinux are fatally broken and there > are > > no sample scripts for "default" to allow booting a > DOS > > or other image. for pxelinux booting on windows > > environments, it's basically just a big mess. > > > > Let me know if you get it working, I'd appreciate > it > > so much, I really want this tech to work, and it's > so > > frustrating that it's all broken :o( > > pxelinux, memdisk and menu.c32 work great for me > (using an ISC DHCP > server and the tftp server by hpa). tftpd32 is the > only new part for me. > > Alex > ___________________________________________________________ To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com |
|
From: Alexander H. <mai...@gm...> - 2005-10-20 10:17:28
|
hi! i am going to explain how to boot an image of a DOS floppy disk or the debian installer via the network extract http://perso.wanadoo.fr/philippe.jounin/download/tftpd32.280.zip extract http://www.kernel.org/pub/linux/utils/boot/syslinux/syslinux-3.11.zip create a directory (e.g. c:\tftproot) start tftpd32.exe modify the tftpd32 settings: - make c:\tftproot the base directory - make sure "PXE Compatibility" is selected create a valid DHCP server configuration (use pxelinux.0 as boot file) and save it. a sample DHCP configuration: IP pool starting address: 192.168.6.100 size of pool: 10 boot file: pxelinux.0 wins/dns server: 192.168.6.1 default router: 192.168.6.254 mask: 255.255.255.0 domain name: domain.invalid create an image of bootable DOS floppy disk (e.g. using winimage) and copy it to c:\tftproot\dos.ima copy these files from the syslinux package to c:\tftproot\: pxelinux.0 memdisk/memdisk com32/modules/chain.c32 com32/modules/menu.c32 create the sub-directory c:\tftproot\sarge\ copy http://ftp.egr.msu.edu/debian/dists/sarge/main/installer-i386/current/images/netboot/debian-installer/i386/linux to c:\tftproot\sarge\ copy http://ftp.egr.msu.edu/debian/dists/sarge/main/installer-i386/current/images/netboot/debian-installer/i386/initrd.gz to c:\tftproot\sarge\ create the sub-directory c:\tftproot\pxelinux.cfg\ (although there is an extension, it has to be a directory and not a file!) create a file called default ( c:\tftproot\pxelinux.cfg\default ) # start of the file default DEFAULT menu PROMPT 0 TIMEOUT 100 MENU TITLE a simple boot menu LABEL nextdev MENU LABEL next device (depends on BIOS settings) localboot 0 LABEL fd MENU LABEL floppy A: KERNEL chain.c32 append fd0 LABEL hda MENU LABEL Master Boot Record (MBR) of the 1st hard disk KERNEL chain.c32 append hd0 LABEL dos MENU LABEL Image of a DOS floppy disk KERNEL memdisk append initrd=dos.ima label debian MENU LABEL Debian Sarge Installer (Kernel 2.4) kernel sarge/linux append vga=normal initrd=sarge/initrd.gz ramdisk_size=9424 root=/dev/rd/0 devfs=mount,dall rw -- LABEL menu MENU HIDE KERNEL menu.c32 # end of the file default Cheers Alex |
|
From: Marty C. <md...@et...> - 2005-10-20 10:28:05
|
On Oct 20, 2005, at 6:17 AM, Alexander Heinz wrote: > hi! > i am going to explain how to boot an image of a DOS floppy disk or > the debian installer via the network Alex, Outstanding work! This is definitely something I would like to see on the Etherboot wiki. I'm going to install mediawiki on SourceForge now that they allow multiple MySQL databases, and then we can migrate all the existing wiki content over there. Many thanks for figuring this out, and I look forward to hearing how Roy fares in testing it. Marty > extract http://perso.wanadoo.fr/philippe.jounin/download/ > tftpd32.280.zip > extract http://www.kernel.org/pub/linux/utils/boot/syslinux/ > syslinux-3.11.zip > > create a directory (e.g. c:\tftproot) > > start tftpd32.exe > > modify the tftpd32 settings: > - make c:\tftproot the base directory > - make sure "PXE Compatibility" is selected > > create a valid DHCP server configuration (use pxelinux.0 as boot > file) and save it. > > a sample DHCP configuration: > IP pool starting address: 192.168.6.100 > size of pool: 10 > boot file: pxelinux.0 > wins/dns server: 192.168.6.1 > default router: 192.168.6.254 > mask: 255.255.255.0 > domain name: domain.invalid > > create an image of bootable DOS floppy disk (e.g. using winimage) > and copy it to c:\tftproot\dos.ima > > copy these files from the syslinux package to c:\tftproot\: > > pxelinux.0 > memdisk/memdisk > com32/modules/chain.c32 > com32/modules/menu.c32 > > create the sub-directory c:\tftproot\sarge\ > > copy http://ftp.egr.msu.edu/debian/dists/sarge/main/installer-i386/ > current/images/netboot/debian-installer/i386/linux to c:\tftproot > \sarge\ > > copy http://ftp.egr.msu.edu/debian/dists/sarge/main/installer-i386/ > current/images/netboot/debian-installer/i386/initrd.gz to c: > \tftproot\sarge\ > > create the sub-directory c:\tftproot\pxelinux.cfg\ (although there > is an extension, it has to be a directory and not a file!) > > create a file called default ( c:\tftproot\pxelinux.cfg\default ) > > # start of the file default > DEFAULT menu > PROMPT 0 > TIMEOUT 100 > MENU TITLE a simple boot menu > LABEL nextdev > MENU LABEL next device (depends on BIOS settings) > localboot 0 > LABEL fd > MENU LABEL floppy A: > KERNEL chain.c32 > append fd0 > LABEL hda > MENU LABEL Master Boot Record (MBR) of the 1st hard disk > KERNEL chain.c32 > append hd0 > LABEL dos > MENU LABEL Image of a DOS floppy disk > KERNEL memdisk > append initrd=dos.ima > label debian > MENU LABEL Debian Sarge Installer (Kernel 2.4) > kernel sarge/linux > append vga=normal initrd=sarge/initrd.gz ramdisk_size=9424 > root=/dev/rd/0 devfs=mount,dall rw -- > LABEL menu > MENU HIDE > KERNEL menu.c32 > # end of the file default > > Cheers > Alex > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Power Architecture Resource Center: Free content, downloads, > discussions, > and more. http://solutions.newsforge.com/ibmarch.tmpl > _______________________________________________ > Etherboot-users mailing list > Eth...@li... > https://lists.sourceforge.net/lists/listinfo/etherboot-users > |
|
From: Roy W. <roy...@ya...> - 2005-10-20 10:33:15
|
Hi Alex, > i am going to explain how to boot an image of a DOS > floppy disk or the > debian installer via the network Are you like psychic or something !? ;o) Reason I ask is that as well as the DOS boot, the next thing I wanted from this after DOS booting was a way to be able to start a Debian installation, so you've solved all my questions in this posting !!! :o) Thanks for everyone that answered my questions, all of it has been very helpful, and I'm very much looking forward to trying this tonight Alex, this looks like The Way. Now, I wonder if the PXELINUX guys can put your information below near the start of their document (at the moment their document says "please read 40 pages of unintelligable syslinux documentation before attempting to start pxelinux" which is guarenteed to put off 80-90% of people who want to do this. uh, call me weird, but ... I prefer Alex's description !!! ;o) ). Cheers, Roy. --- Alexander Heinz <mai...@gm...> wrote: > hi! > > i am going to explain how to boot an image of a DOS > floppy disk or the > debian installer via the network > > extract > http://perso.wanadoo.fr/philippe.jounin/download/tftpd32.280.zip > extract > http://www.kernel.org/pub/linux/utils/boot/syslinux/syslinux-3.11.zip > > create a directory (e.g. c:\tftproot) > > start tftpd32.exe > > modify the tftpd32 settings: > - make c:\tftproot the base directory > - make sure "PXE Compatibility" is selected > > create a valid DHCP server configuration (use > pxelinux.0 as boot file) > and save it. > > a sample DHCP configuration: > IP pool starting address: 192.168.6.100 > size of pool: 10 > boot file: pxelinux.0 > wins/dns server: 192.168.6.1 > default router: 192.168.6.254 > mask: 255.255.255.0 > domain name: domain.invalid > > create an image of bootable DOS floppy disk (e.g. > using winimage) and > copy it to c:\tftproot\dos.ima > > copy these files from the syslinux package to > c:\tftproot\: > > pxelinux.0 > memdisk/memdisk > com32/modules/chain.c32 > com32/modules/menu.c32 > > create the sub-directory c:\tftproot\sarge\ > > copy > http://ftp.egr.msu.edu/debian/dists/sarge/main/installer-i386/current/images/netboot/debian-installer/i386/linux > > to c:\tftproot\sarge\ > > copy > http://ftp.egr.msu.edu/debian/dists/sarge/main/installer-i386/current/images/netboot/debian-installer/i386/initrd.gz > > to c:\tftproot\sarge\ > > create the sub-directory c:\tftproot\pxelinux.cfg\ > (although there is > an extension, it has to be a directory and not a > file!) > > create a file called default ( > c:\tftproot\pxelinux.cfg\default ) > > # start of the file default > DEFAULT menu > PROMPT 0 > TIMEOUT 100 > MENU TITLE a simple boot menu > LABEL nextdev > MENU LABEL next device (depends on BIOS > settings) > localboot 0 > LABEL fd > MENU LABEL floppy A: > KERNEL chain.c32 > append fd0 > LABEL hda > MENU LABEL Master Boot Record (MBR) of the 1st > hard disk > KERNEL chain.c32 > append hd0 > LABEL dos > MENU LABEL Image of a DOS floppy disk > KERNEL memdisk > append initrd=dos.ima > label debian > MENU LABEL Debian Sarge Installer (Kernel 2.4) > kernel sarge/linux > append vga=normal initrd=sarge/initrd.gz > ramdisk_size=9424 > root=/dev/rd/0 devfs=mount,dall rw -- > LABEL menu > MENU HIDE > KERNEL menu.c32 > # end of the file default > > Cheers > Alex > ___________________________________________________________ To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com |
|
From: Carl K. <ca...@pe...> - 2005-10-25 20:38:05
|
Roy Wiseman wrote: > Hi Alex, > > >>i am going to explain how to boot an image of a DOS >>floppy disk or the >>debian installer via the network > > > Are you like psychic or something !? ;o) > Reason I ask is that as well as the DOS boot, the next > thing I wanted from this after DOS booting was a way > to be able to start a Debian installation, so you've Here is my version of the ubuntu version of pxe based install: https://wiki.ubuntu.com/Installation/LocalNet ^Carl K |
|
From: Alexander H. <mai...@gm...> - 2005-10-20 21:32:49
|
> Unfortunately, something seems wrong. I tried the > below *exactly* using hardware (a Fujitsu Stylistic LT > with an Intel PRO/100 NIC) and a VMware GSX Server 3.2 > virtual machine. > > As in my previous posting, DHCP works perfectly, but > everything stops at "Could not find kernel image: > linux" and then on a new line "boot:" with a prompt. > > Have you got any ideas ? If you have time to talk to > me online I am at roy...@ho... ... maybe you > could zip up the setup you have and email me that to > try the exact settings that you have ? > > Below is my dir listing : > > C:\tftproot>dir/s > Volume in drive C is SYSTEM > Volume Serial Number is 28EB-C452 > > Directory of C:\tftproot > > 20/10/2005 20:34 <DIR> . > 20/10/2005 20:34 <DIR> .. > 20/10/2005 20:34 <DIR> com32 > 20/10/2005 20:34 <DIR> memdisk > 20/10/2005 20:34 <DIR> sarge > 02/09/2005 20:16 13,148 pxelinux.0 > 20/10/2005 20:34 <DIR> pxelunux.cfg > 14/01/2005 21:18 118,784 tftpd32.exe > 20/10/2005 20:28 1,474,560 dos.ima > 20/10/2005 20:28 0 syslog.txt Here is the mistake. Just copy the mentioned files to c:\tftproot Do not copy the sub-directories (e.g. com32, memdisk) Alex |
|
From: Alexander H. <mai...@gm...> - 2005-10-20 22:16:56
|
> Directory of C:\tftproot\sarge > > 20/10/2005 20:34 <DIR> . > 20/10/2005 20:34 <DIR> .. > 20/10/2005 20:19 9,650,176 initrd.gz > 20/10/2005 20:34 816,260 linux.txt > 2 File(s) 10,466,436 bytes rename linux.txt to linux Cheers Alex P.S.: please CC the list |
|
From: Alexander H. <mai...@gm...> - 2005-10-21 11:43:21
|
> Some small part is missing from things somewhere I > guess. It's very very close I think, as I can now see > linux booting, but no menu's (so no option to boot > anything but the "linux" file and the debian linux > installer hangs with a kernel panic every time as you > can see, and can also test with the attached rar). chain.c32 and menu.c32 are missing in your tftproot. copy both files to c:\tftproot Cheers Alex |
|
From: Roy W. <roy...@ya...> - 2005-10-25 20:41:25
|
Hi,
--- Marty Connor <md...@et...> wrote:
>
> I look forward to seeing your output.
>
> Marty
>
Alexander Heinz was kind enough to help me out on my
PXE setup via Messenger and got it all working for me.
I have a couple of questions about this now that it's
working though :
- why do I always get the error "invalid keyword in
file" right after it's loading the "default" file ?? I
get this in every case, either booting hardware or
vmware images etc. Is there an invalid keyword ? or is
this a bug in the PXE ROM code itself or something
inherent in PXELINUX ?
- is there a simple way to get CD-ROM .ISO images to
boot with memdisk just like .IMA files ?
- I *cannot* get the Debian Sarge installer to work on
various hardware, or vmware images. The kernel panic
that described before happens in every case, and I
expect that anyone would get the same result if they
have the same setup as I now have with the directory
structure as below. If anyone has time to try it,
maybe they can see why the Sarge installer is not
working ?
I had been making a few mistakes in my configuration
that Alex fixed for me, but below is my
now-working-perfectly exact folder structure ...
Thanks and Regards,
Roy.
C:\tftproot>dir/s
Volume in drive D is DATA
Volume Serial Number is 9875-503A
Directory of C:\tftproot
24/10/2005 21:34 <DIR> .
24/10/2005 21:34 <DIR> ..
20/10/2005 20:16 698 default
02/09/2005 20:16 20,020 memdisk
24/10/2005 21:34 <DIR> sarge
02/09/2005 20:16 13,148 pxelinux.0
02/09/2005 20:17 3,592 chain.c32
02/09/2005 20:17 26,756 menu.c32
24/10/2005 21:35 <DIR> pxelinux.cfg
14/01/2005 21:18 118,784 tftpd32.exe
20/10/2005 20:28 1,474,560 dos.ima
7 File(s) 1,657,558 bytes
Directory of C:\tftproot\pxelinux.cfg
24/10/2005 21:35 <DIR> .
24/10/2005 21:35 <DIR> ..
20/10/2005 20:16 698 default
1 File(s) 698 bytes
Directory of C:\tftproot\sarge
24/10/2005 21:34 <DIR> .
24/10/2005 21:34 <DIR> ..
20/10/2005 20:34 816,260 linux
20/10/2005 20:19 9,650,176 initrd.gz
2 File(s) 10,466,436 bytes
Total Files Listed:
10 File(s) 12,124,692 bytes
8 Dir(s) 20,415,746,048 bytes free
___________________________________________________________
To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X