Jump to content











Photo
- - - - -

Need Help With tftp32 and ghost


  • Please log in to reply
17 replies to this topic

#1 vtec-this

vtec-this
  • Members
  • 9 posts
  •  
    Canada

Posted 13 May 2010 - 09:52 PM

Need help bad.

OK So I downloaded tftp32 and I need it for imaging ~80 machines.

I have a ghost disk that I usually boot from USB. Instead I want to PXE boot them.

I setup TFTP and placed memdisk and menu.c32 and pxelinux.0 in the root folder. I also placed 5 floppy .img files in there.

Then I made a folder called pxelinux.cfg in the root directory. In this folder I have the file "default". No extension on the file.

here is what i have in it:


DEFAULT menu.c32
PROMPT 0
NOESCAPE 0
ALLOWOPTIONS 55
TIMEOUT 55555


MENU TITLE Visual Touch PXE Menu

# Ghost 1
LABEL Ghost 1
MENU Ghost 1
KERNEL memdisk
APPEND initrd=jeff.img

# Ghost 2
LABEL Ghost 2
MENU Ghost 2
KERNEL memdisk
APPEND initrd=jeff2.img

# Ghost 3
LABEL Ghost 3
MENU Ghost 3
KERNEL memdisk
APPEND initrd=jeff3.img

# Ghost 4
LABEL Ghost 4
MENU Ghost 4
KERNEL memdisk
APPEND initrd=jeff4.img

# Ghost 5
LABEL Ghost 5 IMZ
MENU Ghost 5
KERNEL memdisk
APPEND initrd=jeff5.img

# Diagnostic Tools
LABEL Diagnostic Tools
MENU Diagnostic Tools
KERNEL memdisk
APPEND initrd=DiagnosticTools.img

The reason I have 5 ghost disks listed is because each one assigns a different IP for using ghost. This way I can image 5 at a time on the same network. (same images I use when booting from floppy). I used a .img program to create the files from the disks and then formatted FLOPPY and copied one of them over just to make sure that it works ok. it does so the file is not corrupt or anything. Yes I have no other device giving out IPs this is just on a simple switch, not even a router.

So I boot up a client machine via PXE. It gets an IP from tftp32 fine and loads my gay menu fine. When I select an option off of the menu I get the following on the client screen:

Loadings jeff.img
Ready.

then there is around 9 lines of what I am assuming is hex code of some kind.

then

Ramdisk at 0xbfd580000, length 0x00168000
command line: initrd=jeff.img BOOT_IMG=memdisk
Disk is floppy 0, 1440 K. C/H/S = 80/2/18, EDD off
Total Size Needed = v2364 bytes, allocating 3k
Old DOS memory at 0x9e400 (map says 0x9f800) loading at 0x9d800
1588: 0xffff 15E801: 0x3c00 0xbed5
INT 13 08: Success, count =1, BPT = f000:74d9
old: int13 = f000ec59 int 15 =f000f859
new: int13 = 9d800008 int15 = 9d800376
Loading boot sector... booting...
Starting...


Then it just hangs. CRTL+ALT+DEL doesnt even restart it.

When I check the log in TFTP this is what it reads from beginning to end of attempt:

Rcvd DHCP Discover Msg for IP 0.0.0.0, Mac 00:24:1D:51:D9:30 [13/05 15:41:02.187]
DHCP: proposed address 192.168.2.10 [13/05 15:41:04.421]
Rcvd DHCP Discover Msg for IP 0.0.0.0, Mac 00:24:1D:51:D9:30 [13/05 15:41:04.484]
DHCP: proposed address 192.168.2.10 [13/05 15:41:05.984]
1440 Request 2 not processed [13/05 15:41:06.046]
1440 Request 2 not processed [13/05 15:41:06.109]
Rcvd DHCP Rqst Msg for IP 0.0.0.0, Mac 00:24:1D:51:D9:30 [13/05 15:41:08.531]
Previously allocated address 192.168.2.10 acked [13/05 15:41:10.421]
Connection received from 192.168.2.10 on port 2070 [13/05 15:41:10.421]
Read request for file <pxelinux.0>. Mode octet [13/05 15:41:10.421]
OACK: <tsize=13940,> [13/05 15:41:10.421]
Using local port 1473 [13/05 15:41:10.421]
1440 Request 2 not processed [13/05 15:41:10.484]
Peer returns ERROR <TFTP Aborted> -> aborting transfer [13/05 15:41:10.546]
Connection received from 192.168.2.10 on port 2071 [13/05 15:41:10.546]
Read request for file <pxelinux.0>. Mode octet [13/05 15:41:10.546]
Using local port 1474 [13/05 15:41:10.546]
<pxelinux.0>: sent 28 blks, 13940 bytes in 0 s. 0 blk resent [13/05 15:41:10.734]
Connection received from 192.168.2.10 on port 57089 [13/05 15:41:10.937]
Read request for file <pxelinux.cfg/00000000-0000-0000-0000-00241d51d930>. Mode octet [13/05 15:41:10.937]
File <pxelinux.cfg\00000000-0000-0000-0000-00241d51d930> : error 2 in system call CreateFile The system cannot find the file specified. [13/05 15:41:10.937]
Connection received from 192.168.2.10 on port 57090 [13/05 15:41:10.937]
Read request for file <pxelinux.cfg/01-00-24-1d-51-d9-30>. Mode octet [13/05 15:41:10.937]
File <pxelinux.cfg\01-00-24-1d-51-d9-30> : error 2 in system call CreateFile The system cannot find the file specified. [13/05 15:41:10.937]
Connection received from 192.168.2.10 on port 57091 [13/05 15:41:10.937]
Read request for file <pxelinux.cfg/C0A8020A>. Mode octet [13/05 15:41:10.937]
File <pxelinux.cfg\C0A8020A> : error 2 in system call CreateFile The system cannot find the file specified. [13/05 15:41:10.937]
Connection received from 192.168.2.10 on port 57092 [13/05 15:41:10.953]
Read request for file <pxelinux.cfg/C0A8020>. Mode octet [13/05 15:41:10.953]
File <pxelinux.cfg\C0A8020> : error 2 in system call CreateFile The system cannot find the file specified. [13/05 15:41:10.953]
Connection received from 192.168.2.10 on port 57093 [13/05 15:41:10.953]
Read request for file <pxelinux.cfg/C0A802>. Mode octet [13/05 15:41:10.953]
File <pxelinux.cfg\C0A802> : error 2 in system call CreateFile The system cannot find the file specified. [13/05 15:41:10.953]
Connection received from 192.168.2.10 on port 57094 [13/05 15:41:10.953]
Read request for file <pxelinux.cfg/C0A80>. Mode octet [13/05 15:41:10.953]
File <pxelinux.cfg\C0A80> : error 2 in system call CreateFile The system cannot find the file specified. [13/05 15:41:10.953]
Connection received from 192.168.2.10 on port 57095 [13/05 15:41:10.953]
Read request for file <pxelinux.cfg/C0A8>. Mode octet [13/05 15:41:10.953]
File <pxelinux.cfg\C0A8> : error 2 in system call CreateFile The system cannot find the file specified. [13/05 15:41:10.953]
Connection received from 192.168.2.10 on port 57096 [13/05 15:41:10.968]
Read request for file <pxelinux.cfg/C0A>. Mode octet [13/05 15:41:10.968]
File <pxelinux.cfg\C0A> : error 2 in system call CreateFile The system cannot find the file specified. [13/05 15:41:10.968]
Connection received from 192.168.2.10 on port 57097 [13/05 15:41:10.968]
Read request for file <pxelinux.cfg/C0>. Mode octet [13/05 15:41:10.968]
File <pxelinux.cfg\C0> : error 2 in system call CreateFile The system cannot find the file specified. [13/05 15:41:10.968]
Connection received from 192.168.2.10 on port 57098 [13/05 15:41:10.968]
Read request for file <pxelinux.cfg/C>. Mode octet [13/05 15:41:10.968]
File <pxelinux.cfg\C> : error 2 in system call CreateFile The system cannot find the file specified. [13/05 15:41:10.968]
Connection received from 192.168.2.10 on port 57099 [13/05 15:41:10.968]
Read request for file <pxelinux.cfg/default>. Mode octet [13/05 15:41:10.968]
OACK: <tsize=656,> [13/05 15:41:10.968]
Using local port 1485 [13/05 15:41:10.968]
<pxelinux.cfg\default>: sent 2 blks, 656 bytes in 1 s. 0 blk resent [13/05 15:41:11.046]
Connection received from 192.168.2.10 on port 57100 [13/05 15:41:11.046]
Read request for file <menu.c32>. Mode octet [13/05 15:41:11.046]
OACK: <tsize=33404,> [13/05 15:41:11.046]
Using local port 1486 [13/05 15:41:11.046]
<menu.c32>: sent 66 blks, 33404 bytes in 0 s. 0 blk resent [13/05 15:41:11.171]
Connection received from 192.168.2.10 on port 57101 [13/05 15:41:11.171]
Read request for file <pxelinux.cfg/default>. Mode octet [13/05 15:41:11.171]
OACK: <tsize=656,> [13/05 15:41:11.171]
Using local port 1487 [13/05 15:41:11.171]
<pxelinux.cfg\default>: sent 2 blks, 656 bytes in 0 s. 0 blk resent [13/05 15:41:11.296]
Connection received from 192.168.2.10 on port 57102 [13/05 15:42:11.671]
Read request for file <memdisk>. Mode octet [13/05 15:42:11.671]
OACK: <tsize=20056,> [13/05 15:42:11.671]
Using local port 1488 [13/05 15:42:11.671]
<memdisk>: sent 40 blks, 20056 bytes in 0 s. 0 blk resent [13/05 15:42:11.734]
Connection received from 192.168.2.10 on port 57103 [13/05 15:42:11.734]
Read request for file <jeff.img>. Mode octet [13/05 15:42:11.734]
OACK: <tsize=1474560,> [13/05 15:42:11.734]
Using local port 1489 [13/05 15:42:11.734]
<jeff.img>: sent 2881 blks, 1474560 bytes in 1 s. 0 blk resent [13/05 15:42:12.078]



Does anyone have the slightest idea what I am doing wrong? I figured maybe I dont have the files in the right directory so I included all the files in both directories just to be sure and still no dice.

Here are some screen shots of my TFTP setup:

Posted Image

Posted Image


any help you guys could provided would be most appreciated. I am terrible at this sort of thing and just spend a day trying to get this to work without luck.

thanks again, jeff

#2 Icecube

Icecube

    Gold Member

  • Team Reboot
  • 1063 posts
  •  
    Belgium

Posted 13 May 2010 - 10:20 PM

AFAI can tell from the MEMDISK output, your whole floppy image is transfered.

Try adding 'raw' to memdisk (using new Syslinux syntax):
# Ghost 1

LABEL Ghost 1

MENU LABEL Ghost 1

LINUX memdisk

INITRD jeff.img

APPEND raw
The old way:
# Ghost 1

LABEL Ghost 1

MENU LABEL Ghost 1

KERNEL memdisk

APPEND initrd=jeff.img raw


#3 vtec-this

vtec-this
  • Members
  • 9 posts
  •  
    Canada

Posted 13 May 2010 - 10:41 PM

when i cut and paste your code i get

MEMDISK: No ramdisk image specified!

right after it loads..just a syntax error?

#4 Sha0

Sha0

    WinVBlock Dev

  • Developer
  • 1682 posts
  • Location:reboot.pro Forums
  • Interests:Booting
  •  
    Canada

Posted 13 May 2010 - 10:51 PM

I would guess that you should use newer versions of both PXELINUX (pxelinux.0) and MEMDISK. Older MEMDISKs had some DOS bugs. Here's hoping that a MEMDISK from Syslinux 3.86 or newer should do the trick. Then you'd use Icecube's suggested syntax, too. Look for these newer files in the archive you download:
  • syslinux/core/pxelinux.0
  • syslinux/memdisk/memdisk


#5 vtec-this

vtec-this
  • Members
  • 9 posts
  •  
    Canada

Posted 14 May 2010 - 01:34 PM

well after i put in the newer files the old syntax works great. new syntax just gives same error.

for some reason I can network boot most machines great, but these damn little intel n270s dont seem to pick up the pxe. When I put network as the primary boot device it just says no system disk so its not picking it up. I am wondering if tftp32 maybe isnt compatible with these boards? Seems to boot every other intel device I hook up to it. The strange thing is there really isnt anything I can tell that should be changed in the atom bios. only thing I can find is "network" in the boot order. no "enable pxe" or other obvious setting that I can find..

So it works..., but it doesnt lol thanks though.

#6 vtec-this

vtec-this
  • Members
  • 9 posts
  •  
    Canada

Posted 14 May 2010 - 04:14 PM

does anyone have experience pxe booting atom 270? This is frustrating. is there a chance that the files I have are not compatible with booting an atom board? I though PXE booting was standardized by intel?

much to learn I still have /yodavoice

#7 Sha0

Sha0

    WinVBlock Dev

  • Developer
  • 1682 posts
  • Location:reboot.pro Forums
  • Interests:Booting
  •  
    Canada

Posted 14 May 2010 - 05:09 PM

Do you even see the units attempting to PXE boot? It doesn't seem like it.

#8 vtec-this

vtec-this
  • Members
  • 9 posts
  •  
    Canada

Posted 14 May 2010 - 05:19 PM

no it is strange the only thing i can find pxe related in the bios is selecting network from the boot list. Maybe I dont know the proper abbreviation of something network related (english is not my first lang) but the only setting i can tell is putting it first in the boot order. so i did it first second and third and ya it isnt looking it just boots straight to error, no dhcp attempt. Very strange Im gonna google some info maybe i can figure it out.

#9 Sha0

Sha0

    WinVBlock Dev

  • Developer
  • 1682 posts
  • Location:reboot.pro Forums
  • Interests:Booting
  •  
    Canada

Posted 14 May 2010 - 06:00 PM

If you do not see the PXE-boot attempt, you can rule out your TFTP software altogether for involvement... Unless these units have a lightning-fast PXE-boot which is invisible, which would be a stupid design decision as far as troubleshooting goes.

Some BIOSes have a tri-state for Network Card:
  • Disabled
  • Enabled
  • Enabled with PXE (or sometimes you see MBA or RPL)


#10 Icecube

Icecube

    Gold Member

  • Team Reboot
  • 1063 posts
  •  
    Belgium

Posted 15 May 2010 - 04:27 PM

well after i put in the newer files the old syntax works great. new syntax just gives same error.

Are you sure, you updated all files?

You need to replace at least:
  • pxelinux.0
  • menu.c32
  • memdisk
Also change:
DEFAULT menu.c32
To the new syntax:
UI menu.c32


#11 vtec-this

vtec-this
  • Members
  • 9 posts
  •  
    Canada

Posted 17 May 2010 - 05:44 PM

i am not sure if I did all 3 of the files or just 2 so i will try again today with your syntax and get back to you.

seems there is going to be more problems then i thought. Ive tried out the pxe booting to ghost on 10 different types of machines now. Seems anything with a cyrix setup (non intel) hangs right as the image is about to transfer. Ive had about 50% success rates using intel boards P4s, Duo Core, C2Duo,atom (both 300 and 270).

Wondering if maybe I need to update something else to make it compatible with different boards. Its pretty hit or miss right now.

#12 vtec-this

vtec-this
  • Members
  • 9 posts
  •  
    Canada

Posted 18 May 2010 - 03:08 PM

made sure to replace all 3. no change..

#13 Sha0

Sha0

    WinVBlock Dev

  • Developer
  • 1682 posts
  • Location:reboot.pro Forums
  • Interests:Booting
  •  
    Canada

Posted 18 May 2010 - 03:38 PM

Perhaps you'd like to throw these units in the garbage? :cheers: Maybe the vendor's web site has a spec. sheet including details for the NIC and whether or not it supports PXE?

#14 vtec-this

vtec-this
  • Members
  • 9 posts
  •  
    Canada

Posted 19 May 2010 - 09:41 PM

ok i got it partly figured out

after adding the UI menu.32 and making sure the overwrite the previous menu.c32 I am now able to boot the intel atom machines!!!!!!

thank you guys so much for the help you saved my dumb ass.

The cyrix based systems are still no dice though. Which is too bad because I have to deal with them all the time. They can boot the menu, but after selecting the image they just hang.

the log from the tftp32 server is:

Rcvd DHCP Discover Msg for IP 0.0.0.0, Mac 00:80:91:5A:4C:40 [19/05 15:20:57.765]
DHCP: proposed address 192.168.2.13 [19/05 15:20:59.437]
1440 Request 2 not processed [19/05 15:20:59.500]
Rcvd DHCP Rqst Msg for IP 0.0.0.0, Mac 00:80:91:5A:4C:40 [19/05 15:20:59.781]
Previously allocated address 192.168.2.13 acked [19/05 15:21:01.281]
Connection received from 192.168.2.13 on port 2070 [19/05 15:21:01.281]
Read request for file <pxelinux.0>. Mode octet [19/05 15:21:01.281]
OACK: <tsize=16794,> [19/05 15:21:01.281]
Using local port 1838 [19/05 15:21:01.281]
1440 Request 2 not processed [19/05 15:21:01.343]
Peer returns ERROR <TFTP Aborted> -> aborting transfer [19/05 15:21:01.406]
Connection received from 192.168.2.13 on port 2071 [19/05 15:21:01.406]
Read request for file <pxelinux.0>. Mode octet [19/05 15:21:01.406]
OACK: <blksize=1456,> [19/05 15:21:01.406]
Using local port 1839 [19/05 15:21:01.406]
<pxelinux.0>: sent 12 blks, 16794 bytes in 0 s. 0 blk resent [19/05 15:21:01.593]
Connection received from 192.168.2.13 on port 57089 [19/05 15:21:01.593]
Read request for file <pxelinux.cfg/ffffffff-ffff-ffff-ffff-ffffffffffff>. Mode octet [19/05 15:21:01.593]
File <pxelinux.cfg\ffffffff-ffff-ffff-ffff-ffffffffffff> : error 2 in system call CreateFile The system cannot find the file specified. [19/05 15:21:01.593]
Connection received from 192.168.2.13 on port 57090 [19/05 15:21:01.593]
Read request for file <pxelinux.cfg/01-00-80-91-5a-4c-40>. Mode octet [19/05 15:21:01.593]
File <pxelinux.cfg\01-00-80-91-5a-4c-40> : error 2 in system call CreateFile The system cannot find the file specified. [19/05 15:21:01.593]
Connection received from 192.168.2.13 on port 57091 [19/05 15:21:01.593]
Read request for file <pxelinux.cfg/C0A8020D>. Mode octet [19/05 15:21:01.593]
File <pxelinux.cfg\C0A8020D> : error 2 in system call CreateFile The system cannot find the file specified. [19/05 15:21:01.593]
Connection received from 192.168.2.13 on port 57092 [19/05 15:21:01.593]
Read request for file <pxelinux.cfg/C0A8020>. Mode octet [19/05 15:21:01.593]
File <pxelinux.cfg\C0A8020> : error 2 in system call CreateFile The system cannot find the file specified. [19/05 15:21:01.593]
Connection received from 192.168.2.13 on port 57093 [19/05 15:21:01.593]
Read request for file <pxelinux.cfg/C0A802>. Mode octet [19/05 15:21:01.593]
File <pxelinux.cfg\C0A802> : error 2 in system call CreateFile The system cannot find the file specified. [19/05 15:21:01.593]
Connection received from 192.168.2.13 on port 57094 [19/05 15:21:01.593]
Read request for file <pxelinux.cfg/C0A80>. Mode octet [19/05 15:21:01.593]
File <pxelinux.cfg\C0A80> : error 2 in system call CreateFile The system cannot find the file specified. [19/05 15:21:01.593]
Connection received from 192.168.2.13 on port 57095 [19/05 15:21:01.609]
Read request for file <pxelinux.cfg/C0A8>. Mode octet [19/05 15:21:01.609]
File <pxelinux.cfg\C0A8> : error 2 in system call CreateFile The system cannot find the file specified. [19/05 15:21:01.609]
Connection received from 192.168.2.13 on port 57096 [19/05 15:21:01.609]
Read request for file <pxelinux.cfg/C0A>. Mode octet [19/05 15:21:01.609]
File <pxelinux.cfg\C0A> : error 2 in system call CreateFile The system cannot find the file specified. [19/05 15:21:01.609]
Connection received from 192.168.2.13 on port 57097 [19/05 15:21:01.609]
Read request for file <pxelinux.cfg/C0>. Mode octet [19/05 15:21:01.609]
File <pxelinux.cfg\C0> : error 2 in system call CreateFile The system cannot find the file specified. [19/05 15:21:01.609]
Connection received from 192.168.2.13 on port 57098 [19/05 15:21:01.609]
Read request for file <pxelinux.cfg/C>. Mode octet [19/05 15:21:01.609]
File <pxelinux.cfg\C> : error 2 in system call CreateFile The system cannot find the file specified. [19/05 15:21:01.609]
Connection received from 192.168.2.13 on port 57099 [19/05 15:21:01.609]
Read request for file <pxelinux.cfg/default>. Mode octet [19/05 15:21:01.609]
OACK: <tsize=656,blksize=1408,> [19/05 15:21:01.609]
Using local port 1850 [19/05 15:21:01.609]
Warning : received duplicated request from 192.168.2.13:57099 [19/05 15:21:01.703]
<pxelinux.cfg\default>: sent 1 blk, 656 bytes in 0 s. 0 blk resent [19/05 15:21:01.718]
Connection received from 192.168.2.13 on port 57099 [19/05 15:21:01.953]
Connection received from 192.168.2.13 on port 57100 [19/05 15:21:01.953]
Warning : received duplicated request from 192.168.2.13:57100 [19/05 15:21:01.953]
Read request for file <menu.c32>. Mode octet [19/05 15:21:01.953]
OACK: <tsize=54964,blksize=1408,> [19/05 15:21:01.953]
Using local port 1852 [19/05 15:21:01.953]
Read request for file <pxelinux.cfg/default>. Mode octet [19/05 15:21:01.953]
OACK: <tsize=656,blksize=1408,> [19/05 15:21:01.953]
Using local port 1851 [19/05 15:21:01.953]
<menu.c32>: sent 40 blks, 54964 bytes in 1 s. 0 blk resent [19/05 15:21:02.015]
Connection received from 192.168.2.13 on port 57100 [19/05 15:21:02.203]
Connection received from 192.168.2.13 on port 57100 [19/05 15:21:02.203]
Connection received from 192.168.2.13 on port 57101 [19/05 15:21:02.203]
Warning : received duplicated request from 192.168.2.13:57101 [19/05 15:21:02.203]
Read request for file <menu.c32>. Mode octet [19/05 15:21:02.203]
OACK: <tsize=54964,blksize=1408,> [19/05 15:21:02.203]
Using local port 1853 [19/05 15:21:02.203]
Read request for file <menu.c32>. Mode octet [19/05 15:21:02.203]
OACK: <tsize=54964,blksize=1408,> [19/05 15:21:02.203]
Using local port 1854 [19/05 15:21:02.203]
Read request for file <pxelinux.cfg/default>. Mode octet [19/05 15:21:02.203]
OACK: <tsize=656,blksize=1408,> [19/05 15:21:02.203]
Using local port 1855 [19/05 15:21:02.203]
<pxelinux.cfg\default>: sent 1 blk, 656 bytes in 0 s. 0 blk resent [19/05 15:21:02.390]
Connection received from 192.168.2.13 on port 57101 [19/05 15:21:02.453]
Warning : received duplicated request from 192.168.2.13:57101 [19/05 15:21:02.453]
Read request for file <pxelinux.cfg/default>. Mode octet [19/05 15:21:02.453]
OACK: <tsize=656,blksize=1408,> [19/05 15:21:02.453]
Using local port 1856 [19/05 15:21:02.453]
Connection received from 192.168.2.13 on port 57101 [19/05 15:21:02.703]
Warning : received duplicated request from 192.168.2.13:57101 [19/05 15:21:02.703]
Read request for file <pxelinux.cfg/default>. Mode octet [19/05 15:21:02.703]
OACK: <tsize=656,blksize=1408,> [19/05 15:21:02.703]
Using local port 1857 [19/05 15:21:02.703]
Connection received from 192.168.2.13 on port 57101 [19/05 15:21:02.953]
Read request for file <pxelinux.cfg/default>. Mode octet [19/05 15:21:02.953]
OACK: <tsize=656,blksize=1408,> [19/05 15:21:02.953]
Using local port 1858 [19/05 15:21:02.953]
Connection received from 192.168.2.13 on port 57102 [19/05 15:21:04.281]
Read request for file <memdisk>. Mode octet [19/05 15:21:04.281]
OACK: <tsize=25340,blksize=1408,> [19/05 15:21:04.281]
Using local port 1859 [19/05 15:21:04.281]
<memdisk>: sent 18 blks, 25340 bytes in 0 s. 0 blk resent [19/05 15:21:04.343]
Connection received from 192.168.2.13 on port 57103 [19/05 15:21:04.343]
Read request for file <jeff.img>. Mode octet [19/05 15:21:04.343]
OACK: <tsize=1474560,blksize=1408,> [19/05 15:21:04.343]
Using local port 1860 [19/05 15:21:04.343]
Warning : received duplicated request from 192.168.2.13:57103 [19/05 15:21:04.453]
Connection received from 192.168.2.13 on port 57103 [19/05 15:21:04.703]
Read request for file <jeff.img>. Mode octet [19/05 15:21:04.703]
OACK: <tsize=1474560,blksize=1408,> [19/05 15:21:04.703]
Using local port 1861 [19/05 15:21:04.703]
<jeff.img>: sent 1048 blks, 1474560 bytes in 0 s. 0 blk resent [19/05 15:21:04.703]
TIMEOUT waiting for Ack block #0 [19/05 15:21:17.078]
TIMEOUT waiting for Ack block #0 [19/05 15:21:17.265]
TIMEOUT waiting for Ack block #0 [19/05 15:21:17.328]
TIMEOUT waiting for Ack block #0 [19/05 15:21:17.515]
TIMEOUT waiting for Ack block #0 [19/05 15:21:17.765]
TIMEOUT waiting for Ack block #0 [19/05 15:21:18.015]
TIMEOUT waiting for Ack block #0 [19/05 15:21:19.765]


thanks again for the help guys it really is greatly appreciated. If I cant I cant figure out this cyrix thing its not the end of the world the atom problem was the main concern

I just wanted to say though that this forums is awsome! lots of knowledge in here!

#15 Sha0

Sha0

    WinVBlock Dev

  • Developer
  • 1682 posts
  • Location:reboot.pro Forums
  • Interests:Booting
  •  
    Canada

Posted 20 May 2010 - 02:02 AM

Good day vtec-this,

You can try the attached debug-output MEMDISK. Add the pause option to your APPEND line, as in:
LABEL jeff

  KERNEL memdisk

  APPEND pause

  INITRD jeff.img
Please report what output you get after you press a key after MEMDISK says "press any key to boot...". You could possibly include the on-screen detail before you press the key to boot, but since it's a little more difficult to type all of it, worry about it later if the output after pressing a key doesn't reveal the problem's cause.

Attached Files



#16 vtec-this

vtec-this
  • Members
  • 9 posts
  •  
    Canada

Posted 20 May 2010 - 05:14 PM

I tried copy/paste your solution into my menu file but it gives an error saying that the menu is not specified when i try to pxeboot

best i could do was to make an option like this

# toshiba test
LABEL Ghost TOSHIBA TEST
MENU TOSHIBA TEST
KERNEL memdisk
APPEND pause
INITRD=jeff.img

then when i select this option it just says no image specified..

#17 Sha0

Sha0

    WinVBlock Dev

  • Developer
  • 1682 posts
  • Location:reboot.pro Forums
  • Interests:Booting
  •  
    Canada

Posted 20 May 2010 - 05:48 PM

# toshiba test
LABEL Ghost TOSHIBA TEST

LABEL lines must not have spaces.

MENU TOSHIBA TEST

I don't know that there's such a thing as MENU all by itself.

KERNEL memdisk
APPEND pause
INITRD=jeff.img

It seems that you should read syslinux/doc/menu.txt and correct your config-file syntax.

#18 Icecube

Icecube

    Gold Member

  • Team Reboot
  • 1063 posts
  •  
    Belgium

Posted 20 May 2010 - 05:59 PM

Use something like this (see also my first post on this topic, where I corrected your menu entry):
# toshiba test

LABEL Ghost_TOSHIBA_TEST

MENU LABEL TOSHIBA TEST

LINUX memdisk

INITRD jeff.img 

APPEND pause





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users