LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)
-   -   PXE boot slack 14.1 (https://www.linuxquestions.org/questions/linux-networking-3/pxe-boot-slack-14-1-a-4175495028/)

SAJM 02-15-2014 10:39 AM
PXE boot slack 14.1
 
Here is what I have.
An XP laptop running tftpd32.
A 5G USB stick with slackware 14.1 ISO loaded and the usb-and-pxe-installers directory.
Another laptop I'm trying to load linux into.

I can connect to the laptop, allocate an ip address and download pxelinux.0

The boot prompt comes up, but what do I load there? Nothing runs. I did run etherboot.img and something loaded the screen flashed and the laptop rebooted.

My F: drive is as follows:

F:\>dir
Volume in drive F is USBSLACK
Volume Serial Number is D44D-DB0A

Directory of F:\

10/02/2014 13:47 64 slackware-14.1-source-dvd.iso.md5
10/02/2014 13:47 222,243 slackware-14.1-source-dvd.iso.txt
10/02/2014 16:06 3,485,065,216 slackware-14.1-source-dvd.iso
10/02/2014 13:47 198 slackware-14.1-source-dvd.iso.asc
14/02/2014 23:50 15,697 usbimg2disk.sh
15/02/2014 16:00 <DIR> etherboot
14/02/2014 23:54 882 pxelinux.cfg_default
14/02/2014 23:56 31,203 README_PXE.TXT
14/02/2014 23:56 9,197 README_USB.TXT
14/02/2014 23:54 51,340,288 usbboot.img
06/02/2014 13:19 11,816 pxelinux.0
10 File(s) 3,536,696,804 bytes
1 Dir(s) 462,077,952 bytes free


Directory of F:\etherboot

15/02/2014 16:00 <DIR> .
15/02/2014 16:00 <DIR> ..
14/02/2014 23:54 433 dhcpd.conf
14/02/2014 23:55 440 dnsmasq.conf
14/02/2014 23:55 1,474,560 etherboot.img
14/02/2014 23:55 3,087 etherboot_img.build
14/02/2014 23:55 1,474,560 etherboot_pcmcia.img
14/02/2014 23:54 4,567 ETHERBOOT_README.TXT
14/02/2014 23:55 2,498 populate_tftpboot.sh
14/02/2014 23:55 2,667 populate_tftpboot_symlinks.sh
14/02/2014 23:54 36,064 RAWRITE.EXE
14/02/2014 23:54 2,138 RAWRITE12.DOC
14/02/2014 23:54 13,052 RAWRITE12.EXE
14/02/2014 23:56 36,064 RAWRITE13.EXE
14/02/2014 23:54 6,170 RAWRITENT.DOC
14/02/2014 23:54 24,576 RAWRITENT.EXE
14/02/2014 23:55 588 rc.dhcpd
14/02/2014 23:55 547 rc.tftpd
16 File(s) 3,082,011 bytes
2 Dir(s) 462,077,952 bytes free


I find the online help rather contradictory with one site saying load this and another saying load that. I'm sure they are all right but my depth of knowledge cannot understand all the scripts described. I thought some script would run, unpack the ISO file and it would all work like I was installing from a CD. Seems I'm wrong.

Thanks

jefro 02-15-2014 02:43 PM
Not exactly sure what you are seeing. What does ls or other command line tools show?


http://diddy.boot-land.net/pxe/files/tftpd32.htm shows most of the options needed. Be sure to test the transfer size for best number.
I have only sent over data from the tftp folder. Haven't used mounted usb's.



There are a few hundred tutorials on pxe subject. All are different by the way. A slightly different way is to use gpxe/ipxe so that one might use internet to get data or local source other than tftp. Tftp is connectionless and could fail on bad connections.

This link has most of the tips. http://docs.slackware.com/slackware:pxe_install
http://docs.slackware.com/slackware:install

Both suggest you can use the dvd to boot a client.

SAJM 02-15-2014 03:17 PM
Quote:
Originally Posted by jefro (Post 5118323)
Not exactly sure what you are seeing. What does ls or other command line tools show?


http://diddy.boot-land.net/pxe/files/tftpd32.htm shows most of the options needed. Be sure to test the transfer size for best number.
I have only sent over data from the tftp folder. Haven't used mounted usb's.



There are a few hundred tutorials on pxe subject. All are different by the way. A slightly different way is to use gpxe/ipxe so that one might use internet to get data or local source other than tftp. Tftp is connectionless and could fail on bad connections.

This link has most of the tips. http://docs.slackware.com/slackware:pxe_install
http://docs.slackware.com/slackware:install

Both suggest you can use the dvd to boot a client.
After loading PXElinux.0 I get the following

......
Trying to load: pxelinux.cfg/default
Could not find kernel image: linux
boot:

Now if I load huge.s it starts loading then the laptop just locks up and i have to remove the batteries to restart.

The file you suggested odin1440.img loads, but my monitor just displays crazy colourful patterns. I have to power off to recover.

jefro 02-15-2014 07:12 PM
Maybe this??? https://www.linuxquestions.org/quest...oading-555403/

allend 02-15-2014 07:41 PM
Do not bother with trying to use XP and tftpd32. Instead, boot that computer from your USB stick and run pxesetup.
http://www.linuxquestions.org/questi...1/#post4967100

SAJM 02-16-2014 05:21 AM
Quote:
Originally Posted by allend (Post 5118441)
Do not bother with trying to use XP and tftpd32. Instead, boot that computer from your USB stick and run pxesetup.
http://www.linuxquestions.org/questi...1/#post4967100

Sadly my old laptop won't boot from a USB stick :-(

allend 02-16-2014 06:09 AM
I meant that you could boot the Slackware install media on your computer running XP and use pxesetup to make that a PXE server. This would all be run without affecting your XP install.

SAJM 02-16-2014 08:20 AM
Quote:
Originally Posted by allend (Post 5118612)
I meant that you could boot the Slackware install media on your computer running XP and use pxesetup to make that a PXE server. This would all be run without affecting your XP install.
I have the laptop connected to the XP TFTP server and it is assigned an ip address. The problem is what do I enter at the boot: prompt to start the install. Nothing I seem to try works. The laptop hangs up, does nothing or displays crazy colours on the screen and then reboots.

SAJM 02-16-2014 09:44 AM
Quote:
Originally Posted by SAJM (Post 5118676)
I have the laptop connected to the XP TFTP server and it is assigned an ip address. The problem is what do I enter at the boot: prompt to start the install. Nothing I seem to try works. The laptop hangs up, does nothing or displays crazy colours on the screen and then reboots.
Amongst the many discussions on PXE booting there seem to be 2 common threads. One is to boot huge.s and the other is vlinuz.

Booting huge.s loads on my laptop but gets to a stage where it wants me to "Insert root floppy and press ENTER" This is suprising because I understood linux has not been bootable from a floppy for years.

I simply cannot find the file vmlinuz on the slackware ftp site.

etherboot.img seems logical to me but that has display issues on my laptop, although it does load as I mentioned earlier.

I seem to be going round and round the same thing and must be missing the obvious.

SAJM 02-17-2014 09:51 AM
Quote:
Originally Posted by SAJM (Post 5118698)
Amongst the many discussions on PXE booting there seem to be 2 common threads. One is to boot huge.s and the other is vlinuz.

Booting huge.s loads on my laptop but gets to a stage where it wants me to "Insert root floppy and press ENTER" This is suprising because I understood linux has not been bootable from a floppy for years.

I simply cannot find the file vmlinuz on the slackware ftp site.

etherboot.img seems logical to me but that has display issues on my laptop, although it does load as I mentioned earlier.

I seem to be going round and round the same thing and must be missing the obvious.
I tried to load hugesmp.s and the same thing happened as with huge.s. The file downloaded from tftpd32, unpacked and loaded onto the laptop. again it asked for the root floppy (remember this laptop has no floppy) If I ignored the floppy and pressed enter anyway the laptop just locked up and required a power restart.

allend 02-17-2014 07:09 PM
I suspect that you are not loading the initrd image with the kernel image. On my PXE boot setup on Slackware I have this in the directory containing the files to be accessed by PXE.
Code:
bash-4.2$ tree /var/ftpd
/var/ftpd
|-- README.TXT
|-- VERSIONS.TXT
|-- f2.txt
|-- initrd.img
|-- kernels
|  |-- huge.s
|  |  |-- System.map.gz
|  |  |-- bzImage
|  |  `-- config
|  |-- hugesmp.s
|  |  |-- System.map.gz
|  |  |-- bzImage
|  |  `-- config
|  `-- memtest
|      |-- README
|      `-- memtest
|-- message.txt
|-- pxelinux.0
`-- pxelinux.cfg
    `-- default
The content of pxelinux.cfg/default is
Code:
default hugesmp.s
prompt 1
timeout 1200
display message.txt
F1 message.txt
F2 f2.txt
label huge.s
  kernel kernels/huge.s/bzImage
  append initrd=initrd.img load_ramdisk=1 prompt_ramdisk=0 rw printk.time=0 SLACK_KERNEL=huge.s
label hugesmp.s
  kernel kernels/hugesmp.s/bzImage
  append initrd=initrd.img load_ramdisk=1 prompt_ramdisk=0 rw printk.time=0 SLACK_KERNEL=hugesmp.s
label speakup.s
  kernel kernels/hugesmp.s/bzImage
  append initrd=initrd.img load_ramdisk=1 prompt_ramdisk=0 rw printk.time=0 SLACK_KERNEL=hugesmp.s
label memtest
  kernel kernels/memtest/memtest
Note the append lines to create the ramdisk including the Slackware installer image.

SAJM 02-17-2014 07:39 PM
Quote:
Originally Posted by allend (Post 5119628)
I suspect that you are not loading the initrd image with the kernel image. On my PXE boot setup on Slackware I have this in the directory containing the files to be accessed by PXE.
Code:
bash-4.2$ tree /var/ftpd
/var/ftpd
|-- README.TXT
|-- VERSIONS.TXT
|-- f2.txt
|-- initrd.img
|-- kernels
|  |-- huge.s
|  |  |-- System.map.gz
|  |  |-- bzImage
|  |  `-- config
|  |-- hugesmp.s
|  |  |-- System.map.gz
|  |  |-- bzImage
|  |  `-- config
|  `-- memtest
|      |-- README
|      `-- memtest
|-- message.txt
|-- pxelinux.0
`-- pxelinux.cfg
    `-- default
The content of pxelinux.cfg/default is
Code:
default hugesmp.s
prompt 1
timeout 1200
display message.txt
F1 message.txt
F2 f2.txt
label huge.s
  kernel kernels/huge.s/bzImage
  append initrd=initrd.img load_ramdisk=1 prompt_ramdisk=0 rw printk.time=0 SLACK_KERNEL=huge.s
label hugesmp.s
  kernel kernels/hugesmp.s/bzImage
  append initrd=initrd.img load_ramdisk=1 prompt_ramdisk=0 rw printk.time=0 SLACK_KERNEL=hugesmp.s
label speakup.s
  kernel kernels/hugesmp.s/bzImage
  append initrd=initrd.img load_ramdisk=1 prompt_ramdisk=0 rw printk.time=0 SLACK_KERNEL=hugesmp.s
label memtest
  kernel kernels/memtest/memtest
Note the append lines to create the ramdisk including the Slackware installer image.
Thanks

I have that script and several others quoted by numerous help pages on the subject. They have different names but all contain the same script. It does not load. The only file I can get across via tftp is pxelinux.0 which gives me a boot: prompt!

The more I read up on the subject the more confused I get. My PXE boot tree which I downloaded from a Slackware 14.1 mirror (and is displayed on an earlier post) looks nothing like yours. It seemed logical to me to download the PXE/USB and ethernet boot directory, after all that's what I'm trying to do, is this wrong?

allend 02-18-2014 05:22 AM
From README_PXE.TXT in the usb-and-pxe-installers directory of the Slackware install media. (Originally written for Slackware 13.37 but has not changed)
Quote:
The tftp directory structure:

As you can see in the DHCP section, the DHCP server has been configured
to offer any interested PXE client (i.e. your computers network card) the
file "/slackware-13.37/pxelinux.0" - this file contains the bootable code
that first downloads and starts a Linux kernel, and then downloads and
extracts the root filesystem containing the setup program and everything
else that we need. This filename "/slackware-13.37/pxelinux.0" indicates
a pathname relative to the root of the TFTP server. The PXE client will
use the tftp protocol to fetch this bootloader. So this is what we do:
create this directory "slackware-13.37" and copy the required files into it.
First, the pxelinux bootloader itself:

mkdir /tftpboot/slackware-13.37
mkdir /tftpboot/slackware-13.37/pxelinux.cfg
cp /usr/share/syslinux/pxelinux.0 /tftpboot/slackware-13.37/

Also, we need the files from the Slackware CDROM that show the
informative messages in the beginning. Assuming your local copy of the
Slackware release can be found in "/mirror/slackware/slackware-13.37"
(change paths in the below commands if your location is different) :

cp /mirror/slackware/slackware-13.37/isolinux/message.txt /tftpboot/slackware-13.37/
cp /mirror/slackware/slackware-13.37/isolinux/f2.txt /tftpboot/slackware-13.37/

Very important: we need the initial ramdisk image (initrd.img) and the pxelinux configuration file that contains the instructions for the PXE clients:

cp /mirror/slackware/slackware-13.37/isolinux/initrd.img /tftpboot/slackware-13.37/
cp /mirror/slackware/slackware-13.37/usb-and-pxe-installers/pxelinux.cfg_default /tftpboot/slackware-13.37/pxelinux.cfg/default

And lastly, we need all the kernels that the Slackware installer lets you
choose from:

cp -a /mirror/slackware/slackware-13.37/kernels /tftpboot/slackware-13.37/
Your PXE boot tree is not working and does not match with mine (built from the above instructions). Might be worth a try. ;-)

SAJM 02-18-2014 06:01 AM
Quote:
Originally Posted by allend (Post 5119913)
From README_PXE.TXT in the usb-and-pxe-installers directory of the Slackware install media. (Originally written for Slackware 13.37 but has not changed)

Your PXE boot tree is not working and does not match with mine (built from the above instructions). Might be worth a try. ;-)
I have done as you suggested but do not understand the following:

cp /mirror/slackware/slackware-13.37/isolinux/initrd.img /tftpboot/slackware-13.37/
cp /mirror/slackware/slackware-13.37/usb-and-pxe-installers/pxelinux.cfg_default /tftpboot/slackware-13.37/pxelinux.cfg/default

has the file "pxelinux.cfg_default" been renamed "default"

allend 02-18-2014 06:15 AM
Quote:
cp /mirror/slackware/slackware-13.37/isolinux/initrd.img /tftpboot/slackware-13.37/
Notice the trailing forward slash at the end of the command. It copies the "initrd.img" file into the top of the PXE boot tree.
Quote:
cp /mirror/slackware/slackware-13.37/usb-and-pxe-installers/pxelinux.cfg_default /tftpboot/slackware-13.37/pxelinux.cfg/default
That command copies the "pxelinux.cfg_default" file into the pxelinux.cfg subdirectory of the PXE boot tree and renames it to "default".

The output of the tree command in post#11 is your friend.

SAJM 02-18-2014 06:27 AM
Quote:
Originally Posted by SAJM (Post 5119933)
I have done as you suggested but do not understand the following:

cp /mirror/slackware/slackware-13.37/isolinux/initrd.img /tftpboot/slackware-13.37/
cp /mirror/slackware/slackware-13.37/usb-and-pxe-installers/pxelinux.cfg_default /tftpboot/slackware-13.37/pxelinux.cfg/default

has the file "pxelinux.cfg_default" been renamed "default"
Assuming that is the case here is what I get on the PC expecting slackware

PXELINUX 2.10 2004-06-18 copyright (C) 1994-2004 H. Peter Anvin
UNDI data segment at: 00099C20
UNDI data segment size:3850
UNDI data segment at: 0009D470
UNDI data segment size:2790
PXE entry point found (we hope) at 9D47:00FA
My ip address seems to be C0A801C8 192.168.1.200
ip=192.168.1.200:192.168.1.1:192.168.1.3:255.255.255.0
TFTP prefix
Trying to load: prelinux.cfg/01-00-06-5b-d7-0d-f9
Trying to load: prelinux.cfg/C0A801C8
Trying to load: prelinux.cfg/C0A801
Trying to load: prelinux.cfg/C0A80
Trying to load: prelinux.cfg/C0A8
Trying to load: prelinux.cfg/C0A
Trying to load: prelinux.cfg/C0
Trying to load: prelinux.cfg/C
Trying to load: prelinux.cfg/default
could not find kernel image: linux
Boot:

Where is linux? I have also pointed TFTPD32 to /prelinux.cfg/default and the file does not even get across to the other PC awaiting slackware

The TFTPD32 log is as follows:

RRcvd DHCP Discover Msg for IP 0.0.0.0, Mac 00:06:5B:D7:0D:F9 [18/02 12:25:15.828]
DHCP: proposed address 192.168.1.200 [18/02 12:25:16.718]
Rcvd DHCP Rqst Msg for IP 0.0.0.0, Mac 00:06:5B:D7:0D:F9 [18/02 12:25:17.906]
Previously allocated address 192.168.1.200 acked [18/02 12:25:17.906]
Connection received from 192.168.1.200 on port 2070 [18/02 12:25:17.953]
Read request for file <default>. Mode octet [18/02 12:25:17.953]
OACK: <tsize=905,> [18/02 12:25:17.953]
Using local port 17600 [18/02 12:25:17.953]
Peer returns ERROR <TFTP Aborted> -> aborting transfer [18/02 12:25:17.953]
Connection received from 192.168.1.200 on port 2071 [18/02 12:25:17.953]
Read request for file <default>. Mode octet [18/02 12:25:17.968]
Using local port 17601 [18/02 12:25:17.968]
<default>: sent 2 blks, 905 bytes in 0 s. 0 blk resent [18/02 12:25:17.968]

The
PC just sits displaying it's allocated ip address

allend 02-18-2014 06:35 AM
Quote:
Trying to load: prelinux.cfg/default
Is there a typo in your subdirectory name? Seems to be looking for 'prelinux.cfg' rather than 'pxelinux.cfg'.

SAJM 02-18-2014 06:47 AM
Error

allend 02-18-2014 06:50 AM
See post #17

SAJM 02-18-2014 07:11 AM
Quote:
Originally Posted by allend (Post 5119952)
Is there a typo in your subdirectory name? Seems to be looking for 'prelinux.cfg' rather than 'pxelinux.cfg'.
Yes the directory was incorrect but it did not change anything. The only file I can get across to my PC is pxelinux.0.

If at the boot: prompt I enter any script I get: Invalid or corrupt kernel image.

If I enter a Kernel image at boot: the PC either locks up or displays crazy colours on the screen.

SAJM 02-18-2014 07:24 AM
Quote:
Originally Posted by SAJM (Post 5119990)
Yes the directory was incorrect but it did not change anything. The only file I can get across to my PC is pxelinux.0.

If at the boot: prompt I enter any script I get: Invalid or corrupt kernel image.

If I enter a Kernel image at boot: the PC either locks up or displays crazy colours on the screen.
At boot: I tried to load several other kernels and they all stop loading and expect me to insert a floppy, which of course the PC does not have.

allend 02-18-2014 07:27 AM
Are you getting further into the boot process than in post#16?

What does the TFTPD32 log show?

What boot prompt?

Could the target PC require additional kernel parameters?

SAJM 02-18-2014 08:25 AM
Quote:
Originally Posted by allend (Post 5119999)
Are you getting further into the boot process than in post#16?
No unless I load huge.s then I'm asked to inset a floppy

Quote:
Originally Posted by allend (Post 5119999)
What does the TFTPD32 log show?
Rcvd DHCP Discover Msg for IP 0.0.0.0, Mac 00:06:5B:D7:0D:F9 [18/02 14:24:51.031]
DHCP: proposed address 192.168.1.200 [18/02 14:24:51.906]
Rcvd DHCP Rqst Msg for IP 0.0.0.0, Mac 00:06:5B:D7:0D:F9 [18/02 14:24:53.125]
Previously allocated address 192.168.1.200 acked [18/02 14:24:53.125]
Connection received from 192.168.1.200 on port 2070 [18/02 14:24:53.187]
Read request for file <pxelinux.0>. Mode octet [18/02 14:24:53.187]
Using local port 27128 [18/02 14:24:53.203]
<pxelinux.0>: sent 24 blks, 11816 bytes in 0 s. 0 blk resent [18/02 14:24:53.203]
Connection received from 192.168.1.200 on port 57089 [18/02 14:24:53.265]
Read request for file <pxelinux.cfg/01-00-06-5b-d7-0d-f9>. Mode octet [18/02 14:24:53.281]
File <pxelinux.cfg\01-00-06-5b-d7-0d-f9> : error 3 in system call CreateFile The system cannot find the path specified. [18/02 14:24:53.281]
Connection received from 192.168.1.200 on port 57090 [18/02 14:24:53.281]
Read request for file <pxelinux.cfg/C0A801C8>. Mode octet [18/02 14:24:53.281]
File <pxelinux.cfg\C0A801C8> : error 3 in system call CreateFile The system cannot find the path specified. [18/02 14:24:53.281]
Connection received from 192.168.1.200 on port 57091 [18/02 14:24:53.281]
Read request for file <pxelinux.cfg/C0A801C>. Mode octet [18/02 14:24:53.296]
File <pxelinux.cfg\C0A801C> : error 3 in system call CreateFile The system cannot find the path specified. [18/02 14:24:53.296]
Connection received from 192.168.1.200 on port 57092 [18/02 14:24:53.296]
Read request for file <pxelinux.cfg/C0A801>. Mode octet [18/02 14:24:53.296]
File <pxelinux.cfg\C0A801> : error 3 in system call CreateFile The system cannot find the path specified. [18/02 14:24:53.296]
Connection received from 192.168.1.200 on port 57093 [18/02 14:24:53.296]
Read request for file <pxelinux.cfg/C0A80>. Mode octet [18/02 14:24:53.312]
File <pxelinux.cfg\C0A80> : error 3 in system call CreateFile The system cannot find the path specified. [18/02 14:24:53.312]
Connection received from 192.168.1.200 on port 57094 [18/02 14:24:53.312]
Read request for file <pxelinux.cfg/C0A8>. Mode octet [18/02 14:24:53.312]
File <pxelinux.cfg\C0A8> : error 3 in system call CreateFile The system cannot find the path specified. [18/02 14:24:53.312]
Connection received from 192.168.1.200 on port 57095 [18/02 14:24:53.312]
Read request for file <pxelinux.cfg/C0A>. Mode octet [18/02 14:24:53.328]
File <pxelinux.cfg\C0A> : error 3 in system call CreateFile The system cannot find the path specified. [18/02 14:24:53.328]
Connection received from 192.168.1.200 on port 57096 [18/02 14:24:53.328]
Read request for file <pxelinux.cfg/C0>. Mode octet [18/02 14:24:53.328]
File <pxelinux.cfg\C0> : error 3 in system call CreateFile The system cannot find the path specified. [18/02 14:24:53.328]
Connection received from 192.168.1.200 on port 57097 [18/02 14:24:53.328]
Read request for file <pxelinux.cfg/C>. Mode octet [18/02 14:24:53.343]
File <pxelinux.cfg\C> : error 3 in system call CreateFile The system cannot find the path specified. [18/02 14:24:53.343]
Connection received from 192.168.1.200 on port 57098 [18/02 14:24:53.343]
Read request for file <pxelinux.cfg/default>. Mode octet [18/02 14:24:53.343]
File <pxelinux.cfg\default> : error 3 in system call CreateFile The system cannot find the path specified. [18/02 14:24:53.343]
Connection received from 192.168.1.200 on port 57099 [18/02 14:24:53.343]
Read request for file <linux>. Mode octet [18/02 14:24:53.343]
File <linux> : error 2 in system call CreateFile The system cannot find the file specified. [18/02 14:24:53.343]
Connection received from 192.168.1.200 on port 57100 [18/02 14:24:53.343]
Read request for file <linux.cbt>. Mode octet [18/02 14:24:53.359]
File <linux.cbt> : error 2 in system call CreateFile The system cannot find the file specified. [18/02 14:24:53.359]
Connection received from 192.168.1.200 on port 57101 [18/02 14:24:53.359]
Read request for file <linux.0>. Mode octet [18/02 14:24:53.359]
File <linux.0> : error 2 in system call CreateFile The system cannot find the file specified. [18/02 14:24:53.359]
Connection received from 192.168.1.200 on port 57102 [18/02 14:24:53.359]
Read request for file <linux.com>. Mode octet [18/02 14:24:53.375]
File <linux.com> : error 2 in system call CreateFile The system cannot find the file specified. [18/02 14:24:53.375]
Connection received from 192.168.1.200 on port 57103 [18/02 14:24:53.375]
Read request for file <linux.c32>. Mode octet [18/02 14:24:53.375]
File <linux.c32> : error 2 in system call CreateFile The system cannot find the file specified. [18/02 14:24:53.375]


Quote:
Originally Posted by allend (Post 5119999)
What boot prompt?
The boot prompt in #16:
Could not find kernel image: linux
boot:

Quote:
Originally Posted by allend (Post 5119999)
Could the target PC require additional kernel parameters?
I suspect there may be a few display parameters required but no mention is made of them in any of the sites and forums I have visited. In the past I've always got away with the default.

SAJM 02-18-2014 10:17 AM
Suddenly it almost worked. I have no idea what I did!!

Anyway here is what I have

I can boot (run) the PC with memtest. It tells me I have a Pentium III 866Mhz mobile with 255M RAM. It all passes OK

loading huge.s or hugesmp.s brings up the following error which locks up the PC

Call Trace:
[<cla8cf65>] dump_stack+0x16/0x18
[<cla86659>] panic+0x82/0x166
[<cla78ad8>] kernel_init+0x148/0x150
[<cla95377>] ret_from_kernel_thread+0x1b/0x28
[<cla78990>] ? rest_init+0x70/0x70

And then the PC locks up.

SAJM 02-18-2014 11:14 AM
[QUOTE=SAJM;5120131]Suddenly it almost worked. I have no idea what I did!!

/QUOTE]


Here is the tftpd32 log. There are still a few download errors

TIMEOUT waiting for Ack block #50175 [18/02 17:05:21.515]
Rcvd DHCP Discover Msg for IP 0.0.0.0, Mac 00:06:5B:D7:0D:F9 [18/02 17:05:29.437]
DHCP: proposed address 192.168.1.200 [18/02 17:05:30.406]
Rcvd DHCP Rqst Msg for IP 0.0.0.0, Mac 00:06:5B:D7:0D:F9 [18/02 17:05:33.500]
Previously allocated address 192.168.1.200 acked [18/02 17:05:33.500]
Connection received from 192.168.1.200 on port 2070 [18/02 17:05:33.546]
Read request for file <pxelinux.0>. Mode octet [18/02 17:05:33.546]
Using local port 35103 [18/02 17:05:33.546]
<pxelinux.0>: sent 24 blks, 11816 bytes in 0 s. 0 blk resent [18/02 17:05:33.562]
Connection received from 192.168.1.200 on port 57089 [18/02 17:05:33.640]
Read request for file <pxelinux.cfg/01-00-06-5b-d7-0d-f9>. Mode octet [18/02 17:05:33.640]
File <pxelinux.cfg\01-00-06-5b-d7-0d-f9> : error 2 in system call CreateFile The system cannot find the file specified. [18/02 17:05:33.640]
Connection received from 192.168.1.200 on port 57090 [18/02 17:05:33.640]
Read request for file <pxelinux.cfg/C0A801C8>. Mode octet [18/02 17:05:33.656]
File <pxelinux.cfg\C0A801C8> : error 2 in system call CreateFile The system cannot find the file specified. [18/02 17:05:33.656]
Connection received from 192.168.1.200 on port 57091 [18/02 17:05:33.656]
Read request for file <pxelinux.cfg/C0A801C>. Mode octet [18/02 17:05:33.656]
File <pxelinux.cfg\C0A801C> : error 2 in system call CreateFile The system cannot find the file specified. [18/02 17:05:33.656]
Connection received from 192.168.1.200 on port 57092 [18/02 17:05:33.671]
Read request for file <pxelinux.cfg/C0A801>. Mode octet [18/02 17:05:33.671]
File <pxelinux.cfg\C0A801> : error 2 in system call CreateFile The system cannot find the file specified. [18/02 17:05:33.671]
Connection received from 192.168.1.200 on port 57093 [18/02 17:05:33.671]
Read request for file <pxelinux.cfg/C0A80>. Mode octet [18/02 17:05:33.671]
File <pxelinux.cfg\C0A80> : error 2 in system call CreateFile The system cannot find the file specified. [18/02 17:05:33.671]
Connection received from 192.168.1.200 on port 57094 [18/02 17:05:33.687]
Read request for file <pxelinux.cfg/C0A8>. Mode octet [18/02 17:05:33.687]
File <pxelinux.cfg\C0A8> : error 2 in system call CreateFile The system cannot find the file specified. [18/02 17:05:33.687]
Connection received from 192.168.1.200 on port 57095 [18/02 17:05:33.687]
Read request for file <pxelinux.cfg/C0A>. Mode octet [18/02 17:05:33.687]
File <pxelinux.cfg\C0A> : error 2 in system call CreateFile The system cannot find the file specified. [18/02 17:05:33.687]
Connection received from 192.168.1.200 on port 57096 [18/02 17:05:33.703]
Read request for file <pxelinux.cfg/C0>. Mode octet [18/02 17:05:33.703]
File <pxelinux.cfg\C0> : error 2 in system call CreateFile The system cannot find the file specified. [18/02 17:05:33.703]
Connection received from 192.168.1.200 on port 57097 [18/02 17:05:33.703]
Read request for file <pxelinux.cfg/C>. Mode octet [18/02 17:05:33.703]
File <pxelinux.cfg\C> : error 2 in system call CreateFile The system cannot find the file specified. [18/02 17:05:33.703]
Connection received from 192.168.1.200 on port 57098 [18/02 17:05:33.718]
Read request for file <pxelinux.cfg/default>. Mode octet [18/02 17:05:33.718]
OACK: <tsize=905,> [18/02 17:05:33.718]
Using local port 35115 [18/02 17:05:33.718]
<pxelinux.cfg\default>: sent 2 blks, 905 bytes in 0 s. 0 blk resent [18/02 17:05:33.718]
Connection received from 192.168.1.200 on port 57099 [18/02 17:05:33.718]
Read request for file <message.txt>. Mode octet [18/02 17:05:33.718]
OACK: <tsize=873,> [18/02 17:05:33.718]
Using local port 35116 [18/02 17:05:33.718]
<message.txt>: sent 2 blks, 873 bytes in 0 s. 0 blk resent [18/02 17:05:33.734]
Connection received from 192.168.1.200 on port 57100 [18/02 17:05:49.062]
Read request for file <kernels/huge.s/bzImage>. Mode octet [18/02 17:05:49.062]
OACK: <tsize=5995104,> [18/02 17:05:49.062]
Using local port 35126 [18/02 17:05:49.062]
<kernels\huge.s\bzImage>: sent 11710 blks, 5995104 bytes in 5 s. 0 blk resent [18/02 17:05:54.468]
Connection received from 192.168.1.200 on port 57101 [18/02 17:05:54.468]
Read request for file <initrd.img>. Mode octet [18/02 17:05:54.484]
OACK: <tsize=30423684,> [18/02 17:05:54.484]
Using local port 35129 [18/02 17:05:54.484]
Ack block 28957 ignored (received twice) [18/02 17:06:08.171]
<initrd.img>: sent 59422 blks, 30423684 bytes in 27 s. 0 blk resent [18/02 17:06:21.812]

allend 02-18-2014 06:09 PM
This looks very close. Files are being requested and transferred.
Quote:
Connection received from 192.168.1.200 on port 57098 [18/02 17:05:33.718]
Read request for file <pxelinux.cfg/default>. Mode octet [18/02 17:05:33.718]
OACK: <tsize=905,> [18/02 17:05:33.718]
Using local port 35115 [18/02 17:05:33.718]
<pxelinux.cfg\default>: sent 2 blks, 905 bytes in 0 s. 0 blk resent [18/02 17:05:33.718]
Connection received from 192.168.1.200 on port 57099 [18/02 17:05:33.718]
Read request for file <message.txt>. Mode octet [18/02 17:05:33.718]
OACK: <tsize=873,> [18/02 17:05:33.718]
Using local port 35116 [18/02 17:05:33.718]
<message.txt>: sent 2 blks, 873 bytes in 0 s. 0 blk resent [18/02 17:05:33.734]
Connection received from 192.168.1.200 on port 57100 [18/02 17:05:49.062]
Read request for file <kernels/huge.s/bzImage>. Mode octet [18/02 17:05:49.062]
OACK: <tsize=5995104,> [18/02 17:05:49.062]
Using local port 35126 [18/02 17:05:49.062]
<kernels\huge.s\bzImage>: sent 11710 blks, 5995104 bytes in 5 s. 0 blk resent [18/02 17:05:54.468]
Connection received from 192.168.1.200 on port 57101 [18/02 17:05:54.468]
Read request for file <initrd.img>. Mode octet [18/02 17:05:54.484]
OACK: <tsize=30423684,> [18/02 17:05:54.484]
Using local port 35129 [18/02 17:05:54.484]
Ack block 28957 ignored (received twice) [18/02 17:06:08.171]
<initrd.img>: sent 59422 blks, 30423684 bytes in 27 s. 0 blk resent [18/02 17:06:21.812]
But why is the target PC requesting the huge.s kernel image rather than the hugesmp.s kernel image as is the default in the file pxelinux.cfg/default?
Also, there is nothing in the listing showing the transfer of the file f2.txt.

allend 02-18-2014 08:06 PM
This seems to be a problem.
Quote:
<initrd.img>: sent 59422 blks, 30423684 bytes in 27 s. 0 blk resent [18/02 17:06:21.812]
According to the FILELIST.TXT
Code:
-rw-r--r--  1 root root  38026282 2013-11-01 01:20 ./isolinux/initrd.img
Note the difference in file sizes.
Is the initrd.img file correct in your PXE boot tree?

SAJM 02-19-2014 10:41 AM
Quote:
Originally Posted by allend (Post 5120532)
This seems to be a problem.

According to the FILELIST.TXT
Code:
-rw-r--r--  1 root root  38026282 2013-11-01 01:20 ./isolinux/initrd.img
Note the difference in file sizes.
Is the initrd.img file correct in your PXE boot tree?
B I N G O That was it!!!

Thanks so very much for your help Allend

Best regards

Steve


All times are GMT -5. The time now is 11:15 PM.