[K12OSN] Compaq Deskpro not PXE booting

Bert Rolston bert.rolston at clear.net.nz
Mon Mar 1 19:37:09 UTC 2004


Hi Joe,

There are two forms of ROMPAQ, remote and floppy. 

The remote version has to run from a server or another machine via
serial cable. The floppy version will do exactly that, run from a
floppy.

It seems like you got the F10 setup and Diagnostics disks, so that's a
plus. This usually resides from a special partition on the HDD, but can
run from floppy.

HTH

Cheers,
Bert

On Sat, 2004-02-21 at 05:45, Joe Guenther wrote:
> Just to wrap up the solution to the Compaq Deskpro 4000S Small Form
> Factor... with onboard Netelligent NIC.
> 
> I downloaded the ROM paq, but do not have the special software necessary to
> do the remote ROM update, null modem cable etc.  DUMB system if you ask me.
> The latest ROMpaq also addresses the PXE boot issue, but who know if it
> would have fixed it .... didn't get to try it.
> 
> SO THEREFORE, I disabled the onboard NIC in the setup - had to do this via
> diskette as I had  removed the Hdd (makes for nice quiet machine later).  I
> then installed a 3Com905c, ran setup again to confirm that it was recognized
> and the boot order included the NIC (I had tried another RTL NIC but it was
> not included in the boot order.  Now that I got that, I included that MAC
> address in the dhcpd.conf and viola! we have a wonderful thin client.... a
> P233 with 32Mb of RAM that works great.  I get 1024x768 video on it.  What
> more could you ask from a machine that was destined for the recycler!
> 
> I wish I could report a solution to the Netitelligent NIC, but I did not
> have to tools to deal with it.... so I resignated and installed a real NIC
> 
> joe
> 
> -----Original Message-----
> From: k12osn-admin at redhat.com [mailto:k12osn-admin at redhat.com]On Behalf
> Of jessemcdonnell at comcast.net
> Sent: Thursday, February 19, 2004 9:02 AM
> To: k12osn at redhat.com
> Cc: Joe Guenther; k12osn at redhat.com
> Subject: RE: [K12OSN] Compaq Deskpro not PXE booting
> 
> 
> Joe,
> 
> Try changing the server settings and leave the onboard nic. Your problem is
> most likely caused by the implementation of PXE booting in Intel Landesk
> 0.99 and will persist even if you swap out the nic. My Intel motherboard had
> an onboard Intel eepro100 nic and it couldn't boot without making those
> changes. I think you'll find you have to change these settings no matter
> what nic you use.
> 
> Good luck and let us know how you make out.
> 
> Jesse
> 
> > Jesse,
> >
> > That was a great link ... that is what makes this list so phenomenal!!  So
> > now the question is, ... do I just disable the onboard NIC and throw in a
> > standard 3com905c ... certainly more simple.  But hey thanks for the
> > incredible tip.
> >
> > joe
> >
> > -----Original Message-----
> > From: k12osn-admin at redhat.com [mailto:k12osn-admin at redhat.com]On Behalf
> > Of Jesse McDonnell
> > Sent: Wednesday, February 18, 2004 5:06 PM
> > To: k12osn at redhat.com
> > Subject: Re: [K12OSN] Compaq Deskpro not PXE booting
> >
> >
> > On Wed, 18 Feb 2004 14:19:16 -0700
> > "Joe Guenther" <jguenther at chinooksedge.ab.ca> wrote:
> >
> > > I have an older Pentium 233MXX Compaq Deskpro with an on board
> Netlligent
> > > NIC.  It will not PXE boot.  A bit newer PIII600 Compaq Deskpro with
> > onboard
> > > Intel will work.  SO I know that my server is functional.
> > >
> > > Here is the non-functioning boot Dialogue
> > >
> > > BOOTP
> > > DHCP...
> > > PXE-EA1: No PXE server found, using standard boot file
> > > IP ADDR: 192.168.0.6 (so DHCP is working as per the DHCP.conf
> > configuration)
> > > TFTP.....
> > > PXE-E32: TFTP open timeout
> > >
> > > LSA-M99: Exiting LANDesk Service Agent
> > >
> > >
> > > DHCP is working or it would not get the 192.168.0.6 address
> > > PXE does work on the other compaq
> > >
> > > So where do I point this little monster to get his boot file?
> > >
> >
> > Joe,
> >
> > I had an identical problem when setting up an Intel cn430tx board with
> > onboard nic and Landesk Service Agent 0.99. Landesk Service Agent 0.99 is
> > known to be buggy. The solution that worked for me is outlined at
> > http://syslinux.zytor.com/hardware.php#network.
> >
> > Briefly, disable path MTU discovery on the boot server by changing the
> > content of /proc/sys/net/ipv4/ip_no_pmtu_disc from 0 to 1.
> > To do this. as root, run echo 1 > /proc/sys/net/ipv4/ip_no_pmtu_disc  from
> > the command line. If you ever reboot your server you will have to rerun
> this
> > command.
> >
> > Disable the blksize TFTP option on your TFTP server by adding -r blksize
> to
> > the server_args in /etc/xinetd.d/tftp
> > The line in my system is:
> >
> > server_args	=  -r blksize -s /tftpboot/
> >
> > You'll have to restart tftp for the changes to take effect.: /sbin/service
> > xinetd restart should take of that.
> >
> > This works for me...hope it does for you.
> >
> > Good luck!
> >
> > Jesse McDonnell
> >
> >
> >
> > _______________________________________________
> > K12OSN mailing list
> > K12OSN at redhat.com
> > https://www.redhat.com/mailman/listinfo/k12osn
> > For more info see <http://www.k12os.org>
> >
> >
> > _______________________________________________
> > K12OSN mailing list
> > K12OSN at redhat.com
> > https://www.redhat.com/mailman/listinfo/k12osn
> > For more info see <http://www.k12os.org>
> 
> 
> _______________________________________________
> K12OSN mailing list
> K12OSN at redhat.com
> https://www.redhat.com/mailman/listinfo/k12osn
> For more info see <http://www.k12os.org>
> 
> 
> _______________________________________________
> K12OSN mailing list
> K12OSN at redhat.com
> https://www.redhat.com/mailman/listinfo/k12osn
> For more info see <http://www.k12os.org>
-- 
==================================
Bert Rolston Computer Support Ltd.
Mobile - 027 264 0851
================================== 
Specialising in system support
alternative solutions and
Linux operating system
==================================





More information about the K12OSN mailing list