Hi there,
we try to build up diskless clients by pushing a bootimage over a DHCP
and perform an etherboot over PXE. Our networkcards are 3Com 3C905-TX.
Everything works fine so far, but when the client is setting up PCI,
booting stalls with no output. Even if the verbose mode is on, the
client would not talk back anything.
Has anyone similar problems - or better: a solution about that problem?
Hi Sergej,
Not sure off the top of my head, let me see what I can find out.
E.
Sergej Pioch <sergej.pioch@uni-freiburg.de> wrote:
Hi there,
we try to build up diskless clients by pushing a bootimage over a DHCP
and perform an etherboot over PXE. Our networkcards are 3Com 3C905-TX.
Everything works fine so far, but when the client is setting up PCI,
booting stalls with no output. Even if the verbose mode is on, the
client would not talk back anything.Has anyone similar problems - or better: a solution about that problem?
So, far we have been unable to get ANY Intel PXE boot client
to be able to remote boot QNX. Apparently there are some BIOS
calls made the QNX PCI program that cause some reentrancy
issues in the PXE code.
We have specifically had this problem with a RealTek ethernet
card using a PXE boot rom and with an Intel based NIC as well.
However, for the 3Com 3C905, we have a solution that DOES work.
Change over to BOOTP/DHCP rather than PXE mode. We have been
using this method to remote boot QNX successfully off of our
Linux DHCP server for quite some time now.
Michael Burkey (mailto:Michael.Burkey@Nexwarecorp.com)
Nexware Corp. (http://www.nexwarecorp.com)
Software Engineer
865.546.9998 x201
“Sergej Pioch” <sergej.pioch@uni-freiburg.de> wrote in message news:3BB48D66.EC1EE762@uni-freiburg.de…
Hi there,
we try to build up diskless clients by pushing a bootimage over a DHCP
and perform an etherboot over PXE. Our networkcards are 3Com 3C905-TX.
Everything works fine so far, but when the client is setting up PCI,
booting stalls with no output. Even if the verbose mode is on, the
client would not talk back anything.Has anyone similar problems - or better: a solution about that problem?
Hi Michael,
I found out that we have not been able to boot with PXE as it
takes up too much of the lower memory and the boot image will
not fit.
Sorry.
Erick.
Michael D. Burkey <michael.burkey@nexwarecorp.com> wrote:
So, far we have been unable to get ANY Intel PXE boot client
to be able to remote boot QNX. Apparently there are some BIOS
calls made the QNX PCI program that cause some reentrancy
issues in the PXE code.We have specifically had this problem with a RealTek ethernet
card using a PXE boot rom and with an Intel based NIC as well.However, for the 3Com 3C905, we have a solution that DOES work.
Change over to BOOTP/DHCP rather than PXE mode. We have been
using this method to remote boot QNX successfully off of our
Linux DHCP server for quite some time now.As far as the PXE goes, until/unless QNX comes out with a
version of PCI that accesses the pci configuration via a “bare
metal” interface rather than through the BIOS, I don’t personally
see a lot of hope. If I am incorrect in this assumption, I hope
someone lets me know – we have a bunch of other network cards
that we would love to be able to use!
Michael Burkey (mailto:> Michael.Burkey@Nexwarecorp.com> )
Nexware Corp. (> http://www.nexwarecorp.com> )
Software Engineer
865.546.9998 x201
“Sergej Pioch” <> sergej.pioch@uni-freiburg.de> > wrote in message news:> 3BB48D66.EC1EE762@uni-freiburg.de> …
Hi there,we try to build up diskless clients by pushing a bootimage over a DHCP
and perform an etherboot over PXE. Our networkcards are 3Com 3C905-TX.
Everything works fine so far, but when the client is setting up PCI,
booting stalls with no output. Even if the verbose mode is on, the
client would not talk back anything.Has anyone similar problems - or better: a solution about that problem?