OpenMP detection crashes for MP version 1.4
| Project: | JNode Core |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | admin |
| Status: | closed |
Jump to:
Description
The OpenMP detection causes the system to crash during detection of a system that uses MP version 1.4.
- Login to post comments
The 0.2 release crashed
The 0.2 release crashed similarly when the bios was set to MP 1.1.
Dual Pentium III on a VIA board.
(And those I _could_ boot on, did not recognize the netcard
--
Thorbjørn Ravn Andersen "...plus...Tubular Bells!"
netcard ?
What's the model of your netcard ? have you verify in supported hardware list that your netcard is supported ?
CVS version
OpenMP detection was fixed after the 0.2 release. You might want to give it a try with the latest cvs version of the sources.
The model is yet unsupported
The model is yet unsupported - my point was just that I do not have a machine where I can run JNode with network.
Sometime ago I was looking for a packet driver to run in the XP DOS box, and fell over http://www.emboot.com/products_UniversalPacketDriver.htm which claims to utilize the PXE UNDI transport layer. If a similar JNode driver could be written it would mean that any PXE-capable computer would have network support if booted via PXE. That would be nice
--
Thorbjørn Ravn Andersen "...plus...Tubular Bells!"
Thorbjørn, why don't you
Thorbjørn, why don't you submit a feature request issue on a driver for your netcard?
The PXE looks to me like a way of downloading an image from a server to a client pc. This is not a direct JNode matter.
Martin
The point here was that
The point here was that booting via PXE apparently configures the netcard to be in a generic state which could be used with a single driver instead of having a driver per netcard model.
Regarding the network driver - the machine I would use for JNode is the dual processor one, which currently crashes. I will come back to the issue when I have tested that the CVS version can boot.
--
Thorbjørn Ravn Andersen "...plus...Tubular Bells!"
Netcard generic state
If i remember my networking courses, Generic state is good to made some basis actions on netcard like replace serial debugging, load a boot image, etc but not for more complex tasks. These other tasks need a more specific driver for each type of card because netcards have different implementations of receive/transmit actions.
Fabien L.
#1
I think I've fixed it in the HEAD branch.
Please verify and report any problems.
#2