Forum Topic - Mysterious Boot Error Messages with Qnx Neutrino:
   
Mysterious Boot Error Messages with Qnx Neutrino  
Hi,

I have a problem with new x86-Computers running Neutrino 6.3.2. In each 
boot process, the following screen text appears:
///////////////////////////////////////////////////////////////

( ... BIOS messages ... )
Press F1-F4 to select drive or select partition 1? 1
Hit Esc for .altboot...........................................
..............Unable to allocate resource: Invalid argument
Unable to allocate resource: Invalid argument
Unable to allocate resource: Invalid argument
Unable to allocate resource: Invalid argument
Unable to allocate resource: Invalid argument
Unable to allocate resource: Invalid argument
Unable to allocate resource: Invalid argument
Unable to allocate resource: Invalid argument
Unable to allocate resource: Invalid argument
Unable to allocate resource: Invalid argument
( ... no more output displayed for some Minutes ... )
Press the spae bar to input boot options or D to disable DMA
( ... startup continues showing normal messages ... )
//////////////////////////////////////////////////////////////

The same was already showing when I installed Neutrino from the CD. As 
far as I understand the help in User's Guide Chapter "Controlling how 
Neutrino starts", something within the OS boot loader (Second stage boot 
loader) causes the message "Unable to allocat ..."

In the BIOS, the Option "PNP OS" is already turned off.

Can someone give advice?

Michael Haas
Re: Mysterious Boot Error Messages with Qnx Neutrino  
Michael Dr. Haas wrote:
> Hi,
>
> I have a problem with new x86-Computers running Neutrino 6.3.2. In each 
> boot process, the following screen text appears:
> ///////////////////////////////////////////////////////////////
>
> ( ... BIOS messages ... )
> Press F1-F4 to select drive or select partition 1? 1
> Hit Esc for .altboot...........................................
> ..............Unable to allocate resource: Invalid argument
> Unable to allocate resource: Invalid argument
> Unable to allocate resource: Invalid argument
> Unable to allocate resource: Invalid argument
> Unable to allocate resource: Invalid argument
> Unable to allocate resource: Invalid argument
> Unable to allocate resource: Invalid argument
> Unable to allocate resource: Invalid argument
> Unable to allocate resource: Invalid argument
> Unable to allocate resource: Invalid argument
> ( ... no more output displayed for some Minutes ... )
> Press the spae bar to input boot options or D to disable DMA
> ( ... startup continues showing normal messages ... )
> //////////////////////////////////////////////////////////////
>
> The same was already showing when I installed Neutrino from the CD. As 
> far as I understand the help in User's Guide Chapter "Controlling how 
> Neutrino starts", something within the OS boot loader (Second stage boot 
> loader) causes the message "Unable to allocat ..."
>
> In the BIOS, the Option "PNP OS" is already turned off.
>
> Can someone give advice?
>   
This issue has come up in the past, but it was some time ago (around the 
time of the last release) and
the issues had to do with the system allocation of data into the 
internal (kernel) resource manager for
use by other programs. 

* It might be a problem of a program called seedres that is used to seed 
the system resources at
system start time.  The problem might actually be caused due to the fact 
that you have turned PnP
off since on x86

* The PCI manager pulls stuff out of the resource database to reserve it 
for PCI use and then pushes
it back in as shared PCI resources.  I don't know if it uses any PnP 
information, but the main developer
for that monitors this forum and will likely chime in.

Not a lot of help unfortunately.
 Thomas

Re: Mysterious Boot Error Messages with Qnx Neutrino  
Thank you for your reply. The error message I quoted initially also appeared with BIOS option "PnP OS" turned on. 

Could one start seedres later in /etc/sysinit or rc.d, or MUST it be included in the diskboot image? 

Since the system seems to run normal after the startup finally reaches the Photon login windows, I suspect there is more
 likely a timing problem of QNX components than a device fault. 

M. H.