Jump to content











Photo

comboot, netboot & Tiny PXE Server 1.0.0.11


  • Please log in to reply
14 replies to this topic

#1 reboot12

reboot12

    Frequent Member

  • Advanced user
  • 215 posts
  • Interests:WinXP, Debian, OpenWrt, gPXE, iPXE, BIOS, Coreboot
  •  
    European Union

Posted 02 July 2015 - 01:50 PM

Hi. Always use Tiny PXE Server 1.0.0.11 with gPXE, iPXE, RIS, Boot-PROM (Dirk Köppen).

Now I need use old NIC PCMCIA or ISA 3com 3c509B TPO EtherLink III. I try NIC ISA with Netboot or Comboot with this floopy image 3c509.floppy
 
but after boot from FDD have only:
Searching for server...
and in Tiny log:
15:30:13 DHCPd:incoming packet from : .00.60.08.76.D8.A2
or
DHCPd:unrecognised bootp packet
Probably 3c509.floppy is image comboot because display info:
Loading .COM image from floppy


#2 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1936 posts
  • Location:Nantes - France
  •  
    France

Posted 02 July 2015 - 02:00 PM

double post?

 

Hi Reboot12,

 

Get latest version 1.0.0.19.

It might be that this solves your issue.

 

If not, add rfc951=1 under [dhcp] in config.ini as it could be that this old card only support bootp.

 

Regards,

Erwan



#3 reboot12

reboot12

    Frequent Member

  • Advanced user
  • 215 posts
  • Interests:WinXP, Debian, OpenWrt, gPXE, iPXE, BIOS, Coreboot
  •  
    European Union

Posted 02 July 2015 - 03:56 PM

I try 1.0.0.19 and rfc951=1 but still not work :-(

#4 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1936 posts
  • Location:Nantes - France
  •  
    France

Posted 02 July 2015 - 04:57 PM

I try 1.0.0.19 and rfc951=1 but still not work :-(

 

 

copy paste the TPS logs with latest version and rfc951=1 in config.ini.

 

and also describe your setup (screenshot of TPS windows).



#5 reboot12

reboot12

    Frequent Member

  • Advanced user
  • 215 posts
  • Interests:WinXP, Debian, OpenWrt, gPXE, iPXE, BIOS, Coreboot
  •  
    European Union

Posted 02 July 2015 - 05:19 PM

19:13:46 ROOT=C:\PXE\
19:13:46 DHCPd:67 started...
19:13:46 TFPTd started...
19:13:46 HTTPd started...
6997950m.png

Incoming packet log is only in 1.0.0.11 version TPS. On 1.0.0.19 any usefull log data
Loading .COM image from floppy................

BOOT/TFTP/NFS bootstrap loader   ESC for menu

Searching for adapter...3C5x9 board on ISA at 0x0300 - 10baseT
Ethernet address: 00:60:08:76:D8:A2

Searching for server...
No Server found.

boot> help

help               this list
ip <addr>          set my IP addr
server <addr>      set TFTP server IP addr
netmask <addr>     set network mask
hostname <name>    set hostname
kernel <file>      set boot filename
rootfs ip:/fs      set root filesystem
swapfs ip:/fs      set swap filesystem
swapsize <nblks>   set swap size
swapopts <options> swap mount options
rootopts <options> root mount options
linuxcmd <cmds>    pass cmds to linux
diskboot           boot from disk
autoboot           continue
trans <on:off>     turn transceiver on:off


#6 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1936 posts
  • Location:Nantes - France
  •  
    France

Posted 02 July 2015 - 05:26 PM

to be sure I understand, you are booting your device with a floppy?

is it because your network card does not have a pxe/bootp stack?

 

on that floppy there is a netboot or comboot bootstrap?

if so, TPS will not be useful for now as netboot/comboot is not pxe/bootp.

hence the message : DHCPd:unrecognised bootp packet .

 

you need a floppy disk with a bootp/pxe bootstrap.



#7 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1936 posts
  • Location:Nantes - France
  •  
    France

Posted 02 July 2015 - 05:35 PM

reading here : ftp://ftp.ulb.ac.be/pub/resulb/PC/3COMEtherDisk/HELP/readme.txt, you should be able to perform bootp (which is supported by TPS 1.0.0.19 with rfc951=1) : "A boot ROM for the EtherLink III ISA product family is available from your

network supplier. The 3C5-TriROM supports Netware boot, RPL, and BootP
network boot protocols."

 

files here in case you want to have a look : ftp://ftp.ulb.ac.be/pub/resulb/PC/3COMEtherDisk/ .



#8 reboot12

reboot12

    Frequent Member

  • Advanced user
  • 215 posts
  • Interests:WinXP, Debian, OpenWrt, gPXE, iPXE, BIOS, Coreboot
  •  
    European Union

Posted 02 July 2015 - 06:33 PM

I found this tutorial about Netboot PXE Booting a Laptop. I built a floppy disk using a packet driver for 3com 509B TPO and still not boot.
My floopy boot info on screen:
Netboot V0.9.8, Copyright (C) 1995-2003 G. Kuhlmann
BIOS options: none

Packet driver for a 3c509, version 11.2
Portions Copyright 1992, Crynwr Software
Packet driver skeleton copyright 1988-93, Crynwr Software.
This program is freely copyable; source must be available; NO WARRANTY.
See the file COPYING.DOC for details; send FAX to +1-315-268-9201 for a copy.

Packet driver interrupt is 0x62 (98)
Interrupt number 0xA (10)
I/O port 0x300 (768)
Using Twisted Pair (10BaseT) transceiver
ID port 0x110 (272)
My Ethernet address is 00:60:08:76:D8:A2

Found packet driver at int 62, irq 0A


BOOTP: Sending request (press ESC to abort): .........
Bootrom error: PXE-41
Network boot failed
On website of Netboot writes that supports PXE:

Netboot is open source software licensed by the GNU GPL, and contains all necessary tools including a PXE compliant bootrom.


BOOT-PROM by Dirk also use BOOTP protocol and working OK with Tiny PXE Server, need only set boot file to bpmenu:
6989747.gif

#9 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1936 posts
  • Location:Nantes - France
  •  
    France

Posted 02 July 2015 - 07:34 PM

I need to see what TinyPXE Server 1.0.0.19 (with rfc951=1) displays when you client displays this :

 

BOOTP: Sending request (press ESC to abort): .........
Bootrom error: PXE-41
Network boot failed



#10 reboot12

reboot12

    Frequent Member

  • Advanced user
  • 215 posts
  • Interests:WinXP, Debian, OpenWrt, gPXE, iPXE, BIOS, Coreboot
  •  
    European Union

Posted 02 July 2015 - 07:50 PM

21:45:59 ROOT=C:\PXE\
21:45:59 DHCPd:67 started...
21:45:59 TFPTd started...
21:45:59 HTTPd started...
21:49:06 DHCPd:REQUEST received, MAC:00-60-08-76-D8-A2, XID:662E0200
21:49:06 DHCPd:BOOTP REQUEST
21:49:07 DHCPd:ACK sent, IP:192.168.20.4, XID:662E0200


#11 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1936 posts
  • Location:Nantes - France
  •  
    France

Posted 02 July 2015 - 08:06 PM

21:45:59 ROOT=C:\PXE\
21:45:59 DHCPd:67 started...
21:45:59 TFPTd started...
21:45:59 HTTPd started...
21:49:06 DHCPd:REQUEST received, MAC:00-60-08-76-D8-A2, XID:662E0200
21:49:06 DHCPd:BOOTP REQUEST
21:49:07 DHCPd:ACK sent, IP:192.168.20.4, XID:662E0200

 

well this is looks good : 

-a request was sent

-this was seen as a bootp request (thanks to the rfc951=1)

-TinyPXE Server sent a ACK answer

 

Sequence complete : at this stage, you client should boot what ever bootstrapper you specified (pxelinux, ipxe, etc).



#12 reboot12

reboot12

    Frequent Member

  • Advanced user
  • 215 posts
  • Interests:WinXP, Debian, OpenWrt, gPXE, iPXE, BIOS, Coreboot
  •  
    European Union

Posted 02 July 2015 - 10:07 PM

I test Netboot + PCI RTL8139 NIC + Tiny PXE Server:
  • TPS 1.0.0.11 - unrecognised bootp packet
  • TPS 1.0.0.19 with rfc951=1 - Netboot 0.9.8 working OK :-)
22:37:27 DHCPd:REQUEST received, MAC:00-80-48-14-8F-B6, XID:3B010300
22:37:27 DHCPd:BOOTP REQUEST
22:37:28 DHCPd:ACK sent, IP:192.168.20.4, XID:3B010300
22:37:28 TFTPd:DoReadFile:pxelinux.0 B:1432 T:16794
Probably something wrong with the packet driver 3com NIC ISA

#13 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1936 posts
  • Location:Nantes - France
  •  
    France

Posted 03 July 2015 - 07:32 AM

I test Netboot + PCI RTL8139 NIC + Tiny PXE Server:

  • TPS 1.0.0.11 - unrecognised bootp packet
  • TPS 1.0.0.19 with rfc951=1 - Netboot 0.9.8 working OK :-)
22:37:27 DHCPd:REQUEST received, MAC:00-80-48-14-8F-B6, XID:3B010300
22:37:27 DHCPd:BOOTP REQUEST
22:37:28 DHCPd:ACK sent, IP:192.168.20.4, XID:3B010300
22:37:28 TFTPd:DoReadFile:pxelinux.0 B:1432 T:16794
Probably something wrong with the packet driver 3com NIC ISA

 

 

Ok so it works then? Good :)

 

FYI, related discussion here (Tiny Pxe Server and BootP) : http://reboot.pro/to...cating-dnsmasq/ .



#14 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1936 posts
  • Location:Nantes - France
  •  
    France

Posted 04 July 2015 - 11:07 AM

Note that if netboot does not work for you 3c509 card, you may try to build a floppy with gpxe or ipxe.

You may get better results/drivers than the old netboot.

 

ipxe : https://rom-o-matic.eu/(choose advanced)

gpxe : http://rom-o-matic.n...ib/rom-o-matic/



#15 reboot12

reboot12

    Frequent Member

  • Advanced user
  • 215 posts
  • Interests:WinXP, Debian, OpenWrt, gPXE, iPXE, BIOS, Coreboot
  •  
    European Union

Posted 04 July 2015 - 01:46 PM

Yes, I know about this for a long time. I want to use Netboot with old PCMCIA 16-bit card because gPXE/iPXE not support PCMCIA. From this tutorial - PXE Booting a Laptop shows that Netboot support PCMCIA NETGEAR FA410TX. I try build Netboot for other 16-bit PCMCIA 3com 3CCFE574BT and test it in my ThinkPad X61 but probably need also DOS services for PCMCIA slot and not working :-(. I found this PC Card drivers for DOS - ThinkPad but I don't know how use this to build Netboot. Maybe in old laptops no need PCMCIA services and Netboot working OK.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users