Hi guys, This may be a stupid question... I was trying to get a machine to boot with PXE. Everything supportive is setup, the DNS/DHCP works fine, TFTP is also handing over pxelinux.0 and config files correctly. The problem happens at: label xxx kernel memdisk initrd blabla My machine would report "cannot find kernel: memdisk". When doing a tcpdump, I found the machine actually is sending requests for "memdisk", "memdisk.c" memdisk.* to the tftp server - of coz, I don't have them. A bit more information, I am trying to boot a freebsd disk image within a VirtualBox virtual machine. Does anyone have ideas about what's going on here? Thanks a bunch! -Simon
CHEN Xu wrote:> The problem happens at: > > label xxx > kernel memdisk > initrd blabla > > My machine would report "cannot find kernel: memdisk". When doing a > tcpdump, I found the machine actually is sending requests for > "memdisk", "memdisk.c" memdisk.* to the tftp server - of coz, I don't > have them.OK, the problem as I read it, is that you haven't copied memdisk to your TFTP root.... Or it's permissions are denying access. Copy the file "memdisk" from the syslinux tar/package to your TFTP root, and then make sure it's permissions are allowing the TFTP server to read it (644 should do it). TB
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 CHEN Xu wrote:> My machine would report "cannot find kernel: memdisk". When doing a > tcpdump, I found the machine actually is sending requests for > "memdisk", "memdisk.c" memdisk.* to the tftp server - of coz, I don't > have them.memdisk is part of syslinux. After building you need to copy it to the tftp root directory. There are several other binaries as well such as menu.c32. Generally you don't need any of them if you just use a trivial config file and boot linux, but for your example you do. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIeZvlmOOfHg372QQRAuQ7AKDhoUWR8o6gObvhPvKZ6SnbxNoAuwCfbQ0H vNSLxdUVnlDguQ3obOWdPpk=lhS5 -----END PGP SIGNATURE-----