pxe boot: BTX halted

2005-01-24 Thread Norbert Koch
Hello,
I am desperately trying to get pxe boot running.

The client machine is a PentiumMMX/166MHz which successfully
boots FreeBSD from hard disk. It is connected to the server
machine's second ethernet card xl0 (3com).
I can boot the client with etherboot from a floppy withoudt problems,
but usually have no floppy connected to the machine.

When I run ethereal on the server machine I see successful
dhcp and tftp requests. No obvious problems.

The client machine comes up with Intel UNDI PXE-2.0 (build 074).

PXEBOOT usually crashes with int 6 or int d.
CS:EIP points to nothing: ff ff ff ff ...
The final message is: 'BTX halted'.

Any idea?

Thank you,

Norbert Koch
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: pxe boot: BTX halted

2005-01-24 Thread Jan Branbergen
Hello,
 I am desperately trying to get pxe boot running.
 
 The client machine is a PentiumMMX/166MHz which successfully
 boots FreeBSD from hard disk. It is connected to the server
 machine's second ethernet card xl0 (3com).
 I can boot the client with etherboot from a floppy withoudt
 problems,
 but usually have no floppy connected to the machine.
 
 When I run ethereal on the server machine I see successful
 dhcp and tftp requests. No obvious problems.
 
 The client machine comes up with Intel UNDI PXE-2.0 (build 074).
 
 PXEBOOT usually crashes with int 6 or int d.
 CS:EIP points to nothing: ff ff ff ff ...
 The final message is: 'BTX halted'.
 
 Any idea?

you could try to update the PXE firmware for your card. i have encountered some 
problems with older PXE cards ( go to manufacturers website ). 

furthermore, please post ( your / the relevant portion of )  dhcpd.conf 

regards,

Jan___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: PXE boot / BTX Halted [solved]

2004-12-31 Thread Jason Taylor
I'm trying to set up a few diskless workstations using some old 
hardware.  I've tried four different boxes for clients ranging from a 
P-133 to a P-200.  I did use the same Realtek 8139 based NIC in all 4 
boxes, but I don't think that's the problem.  They all get to the 
point where they grab pxeboot via tftp and then a message
snip
I'm using the instructions from 
http://www.onlamp.com/pub/a/bsd/2004/09/09/diskless_server.html and 
http://www.onlamp.com/pub/a/bsd/2004/09/30/diskless_clients.html
snip
All pointers, hints, RTFMs, etc. will be greatly appreciated.

An update with with info I hope is more useful.
I found an eepro100 card and updated the Intel Boot Agent to version 
4.1.16.  Using this card gets me a little further.  Taking out the 4th 
stuff per the ONLamp instructions, yields a dump and BTX Halted right 
after:

pxe_open: gateway ip: 192.168.1.254
/boot/kernel/kernel text=0x5021c8 data=0x7cc10+0x4fe30 
syms=[0x4+0x5a690+0x4+0x6f5d8]

Leaving it in, it happens right after the Beastie menu timer finishes 
counting down.  In both cases I get the exact same (register?) values. 
And here they are:

int=0006  err=  efl=00010002  eip=c0650b2f
eax=  ebx=c0a9a006  ecx=0005  edx=c0a9a009
esi=c0a9a000  edi=0005  ebp=c0c21bd0  esp=c0c21bd0
cs=0008   ds=0010  es=0010  fs=0010   qs=0010  ss=0010
es:eip=0f 44 d0 89 d0 5d c3 8d-76 00 8d bc 22 00 00 00
   00 55 89 e5 83 ec 08 8b-45 08 8b 50 04 89 54 24
ss:esp=f0 1b c2 c0 db 05 65 c0-00 a0 a9 c0 00 a0 a9 c0
   05 00 00 00 a3 5d 8e c0-00 e0 c1 00 00 00 00 00
BTX Halted
I tried a 2nd box with the same card and got the same results.
What am I doing wrong?  Are there any BIOS settings I should be 
checking?  Is my equipment simply too antiquated or not supported?  Are 
there any other debugging steps I can take?

I found the solution in the last handful of messages in this thread 
http://groups-beta.google.com/group/fa.freebsd.stable/browse_thread/thread/158bf491d67001b2/08bc3c981811414a

The problem was I'd set CPUTYPE=p3 when rebuilding world and the i586s 
I'd been trying for clients did not like that.  It seems obvious in hind 
site.

Everything is working wonderfully with the Intel NIC, but BTX still dies 
when I try with the RTL8139/Etherboot combo. :-s
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: PXE boot / BTX Halted

2004-12-30 Thread Jason Taylor
Jason Taylor wrote:
I'm trying to set up a few diskless workstations using some old 
hardware.  I've tried four different boxes for clients ranging from a 
P-133 to a P-200.  I did use the same Realtek 8139 based NIC in all 4 
boxes, but I don't think that's the problem.  They all get to the point 
where they grab pxeboot via tftp and then a message
snip
I'm using the instructions from 
http://www.onlamp.com/pub/a/bsd/2004/09/09/diskless_server.html and 
http://www.onlamp.com/pub/a/bsd/2004/09/30/diskless_clients.html
snip
All pointers, hints, RTFMs, etc. will be greatly appreciated.
An update with with info I hope is more useful.
I found an eepro100 card and updated the Intel Boot Agent to version 
4.1.16.  Using this card gets me a little further.  Taking out the 4th 
stuff per the ONLamp instructions, yields a dump and BTX Halted right after:

pxe_open: gateway ip: 192.168.1.254
/boot/kernel/kernel text=0x5021c8 data=0x7cc10+0x4fe30 
syms=[0x4+0x5a690+0x4+0x6f5d8]

Leaving it in, it happens right after the Beastie menu timer finishes 
counting down.  In both cases I get the exact same (register?) values. 
And here they are:

int=0006  err=  efl=00010002  eip=c0650b2f
eax=  ebx=c0a9a006  ecx=0005  edx=c0a9a009
esi=c0a9a000  edi=0005  ebp=c0c21bd0  esp=c0c21bd0
cs=0008   ds=0010  es=0010  fs=0010   qs=0010  ss=0010
es:eip=0f 44 d0 89 d0 5d c3 8d-76 00 8d bc 22 00 00 00
   00 55 89 e5 83 ec 08 8b-45 08 8b 50 04 89 54 24
ss:esp=f0 1b c2 c0 db 05 65 c0-00 a0 a9 c0 00 a0 a9 c0
   05 00 00 00 a3 5d 8e c0-00 e0 c1 00 00 00 00 00
BTX Halted
I tried a 2nd box with the same card and got the same results.
What am I doing wrong?  Are there any BIOS settings I should be 
checking?  Is my equipment simply too antiquated or not supported?  Are 
there any other debugging steps I can take?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]