QNX4 boot problem

QNX Newsgroups (Archives) qdn.public.qnx4
1

We have a QNX box that runs a customers process and has started to fail. In
the boot sequence, it says:
- Failed to allocate memory for DEVICE structures
Dq.ser bailing out
QNX system errno <2>
Starting VGA graphics driver…
Starting QNX Windows Server on node 1
QNX :/home/berkley:1$ QNX Windows v4.20B
VGA Grafx v1.03
screen name:
pointer device 0: ‘mouse’ ps2 [rel:mouse] //1/dev/mouse
/usr/lib/windows/apps/Wterm/Dev.ein: Unable to add new devices.

and some otehr stuff about failed to add devices. I have never used QNX
before and am not really certain where to start looking for what has failed.
Can somebody point me in the right direction?

Wayne

2

Wayne Scott <wayne.scott@serra.com> wrote:

We have a QNX box that runs a customers process and has started to fail. In
the boot sequence, it says:
Error> - Failed to allocate memory for DEVICE structures

None of (our) messages say anything like .

Dq.ser bailing out

Dq.ser is a custom serial driver not written by QSSL, but by a
third party.

QNX system errno <2

Errno 2 is no such file or directory – but not sure, again,
what that message is about either – probably custom generated
from your boot sequence.

Starting VGA graphics driver…
Starting QNX Windows Server on node 1
QNX :/home/berkley:1$ QNX Windows v4.20B
VGA Grafx v1.03
screen name:
pointer device 0: ‘mouse’ ps2 [rel:mouse] //1/dev/mouse
/usr/lib/windows/apps/Wterm/Dev.ein: Unable to add new devices.

Dev.ein?

Is that a typo from the transcription, or was that what was actually
printed?

Dev.win is the executable.

and some otehr stuff about failed to add devices. I have never used QNX
before and am not really certain where to start looking for what has failed.
Can somebody point me in the right direction?

First direction – who did you buy this from? They might have an idea
of what the custom startup is.

Do you have any documentation printed by QNX/QSSL? A QNX user’s guide
or QNX system administration guide would be helpful.

First thing I’d try: do you see a message that says “hit escape for
alternate OS” during the boot sequence?

Try doing this.

QNX boots from one of two OS images, and then runs a system initialization
script – the default image is /.boot, and it runs one of a set of choices
(depending what is available), if you hit escape, it will run /.altboot,
and this traditionally is a minimal (recovery oriented) image, and it
will run a different (again, usually minimal) set of system init scripts.

That may get you to the point you can look at the system and try a few
things – but without a fair bit of familiarity, this could be a real
pain to debug. (Especially as final install systems are often highly
customized.)

My first couple of GUESSES are a Dev failure, maybe a memory problem
of some sort, maybe something else.

-David

QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.

3

David Gibbs wrote:

Wayne Scott <> wayne.scott@serra.com> > wrote:

We have a QNX box that runs a customers process and has started to fail. In
the boot sequence, it says:
Error> - Failed to allocate memory for DEVICE structures


None of (our) messages say anything like .


Dq.ser bailing out


Dq.ser is a custom serial driver not written by QSSL, but by a
third party.

In particular, it’s for a Digiboard. If you have a such a card with an
external box, make sure it is plugged in to the card. If it’s an oldor
version, plugging or unplugging with the power on may have damaged it.

If the card and/or external box are damaged (lightning, etc.) then you
will get this message.

Richard

QNX system errno <2


Errno 2 is no such file or directory – but not sure, again,
what that message is about either – probably custom generated
from your boot sequence.


Starting VGA graphics driver…
Starting QNX Windows Server on node 1
QNX :/home/berkley:1$ QNX Windows v4.20B
VGA Grafx v1.03
screen name:
pointer device 0: ‘mouse’ ps2 [rel:mouse] //1/dev/mouse
/usr/lib/windows/apps/Wterm/Dev.ein: Unable to add new devices.


Dev.ein?

Is that a typo from the transcription, or was that what was actually
printed?

Dev.win is the executable.


and some otehr stuff about failed to add devices. I have never used QNX
before and am not really certain where to start looking for what has failed.
Can somebody point me in the right direction?


First direction – who did you buy this from? They might have an idea
of what the custom startup is.

Do you have any documentation printed by QNX/QSSL? A QNX user’s guide
or QNX system administration guide would be helpful.

First thing I’d try: do you see a message that says “hit escape for
alternate OS” during the boot sequence?

Try doing this.

QNX boots from one of two OS images, and then runs a system initialization
script – the default image is /.boot, and it runs one of a set of choices
(depending what is available), if you hit escape, it will run /.altboot,
and this traditionally is a minimal (recovery oriented) image, and it
will run a different (again, usually minimal) set of system init scripts.

That may get you to the point you can look at the system and try a few
things – but without a fair bit of familiarity, this could be a real
pain to debug. (Especially as final install systems are often highly
customized.)

My first couple of GUESSES are a Dev failure, maybe a memory problem
of some sort, maybe something else.

-David

4

Richard Kramer wrote:

David Gibbs wrote:
Wayne Scott <> wayne.scott@serra.com> > wrote:

We have a QNX box that runs a customers process and has started to fail.
In
the boot sequence, it says:
Error> - Failed to allocate memory for DEVICE structures


None of (our) messages say anything like .


Dq.ser bailing out


Dq.ser is a custom serial driver not written by QSSL, but by a
third party.

In particular, it’s for a Digiboard. If you have a such a card with an
external box, make sure it is plugged in to the card. If it’s an oldor
version, plugging or unplugging with the power on may have damaged it.

If the card and/or external box are damaged (lightning, etc.) then you
will get this message.

If it is a Digiboard then double check the dip switches and/or jumper
settings. It has been our experience with a quad serial digiboard that
the dip switch settings can be inadvertently changed when mishandled.

Richard


QNX system errno <2


Errno 2 is no such file or directory – but not sure, again,
what that message is about either – probably custom generated
from your boot sequence.


Starting VGA graphics driver…
Starting QNX Windows Server on node 1
QNX :/home/berkley:1$ QNX Windows v4.20B
VGA Grafx v1.03
screen name:
pointer device 0: ‘mouse’ ps2 [rel:mouse] //1/dev/mouse
/usr/lib/windows/apps/Wterm/Dev.ein: Unable to add new devices.


Dev.ein?

Is that a typo from the transcription, or was that what was actually
printed?

Dev.win is the executable.


and some otehr stuff about failed to add devices. I have never used QNX
before and am not really certain where to start looking for what has
failed.
Can somebody point me in the right direction?


First direction – who did you buy this from? They might have an idea
of what the custom startup is.

Do you have any documentation printed by QNX/QSSL? A QNX user’s guide
or QNX system administration guide would be helpful.

First thing I’d try: do you see a message that says “hit escape for
alternate OS” during the boot sequence?

Try doing this.

QNX boots from one of two OS images, and then runs a system initialization
script – the default image is /.boot, and it runs one of a set of choices
(depending what is available), if you hit escape, it will run /.altboot,
and this traditionally is a minimal (recovery oriented) image, and it
will run a different (again, usually minimal) set of system init scripts.

That may get you to the point you can look at the system and try a few
things – but without a fair bit of familiarity, this could be a real
pain to debug. (Especially as final install systems are often highly
customized.)

My first couple of GUESSES are a Dev failure, maybe a memory problem
of some sort, maybe something else.

-David