Why won't QNX4 boot w/o a keyboard?

Ususually our target product has a full-up user interface, however in some
systems we need to have our system boot “headless”, e.g. w/ no keyboard,
mouse, or monitor attached.

I have found that the system hangs during boot if no keyboard is attached.
Can’t I have the system use the keyboard if one is there, but not hang if
one is not there?

Regards,

Jay Marchetti
Pittsburgh Firmware

Jay Marchetti <marchetti@pittsburghfirmware.com> wrote:

Ususually our target product has a full-up user interface, however in some
systems we need to have our system boot “headless”, e.g. w/ no keyboard,
mouse, or monitor attached.

I have found that the system hangs during boot if no keyboard is attached.
Can’t I have the system use the keyboard if one is there, but not hang if
one is not there?

At what point is it hanging?

QNX shouldn’t care. In fact, I just booted the machine beside the
one I’m typeing on with the keyboard unplugged and it booted happily.
(Though, it was a PS/2 keyboard.) Is it a PS/2 keyboard, or an AT
keyboard?

But, likely, this is a BIOS problem, not a QNX issue – the BIOS is
looking for a keyboard well before it gets to the point of running
QNX.

If trying to collect information about how far something has gotten
in a boot sequence:

– leave the monitor attached :slight_smile:
– rebuild your boot image with the specific inclusion, as the first
entry, of sys/boot, and give it the -v option. That is, the start
of your build file should look like:

sys/boot
$ boot -v

– make sure the first line of your sysinit is “set -v” (without the
quotes) to have the sysinit echo every command before executing it.

But, I’ll bet it dies in the BIOS, before it starts loading the OS. I’ve
seen amusing messages like:

“keyboard failure detected. Hit any key to continue.”

Displayed when trying to boot systems without a keyboard.

-David

Its not an early BIOS failure, e.g. the machine goes through normal POST
stuff with no error messages, then the QNX loader runs w/o error messages
(still in text mode), then the screen is switched to graphics mode (it
normally boots into Photon) - but then: it just remains a black empty
graphics screen.

Now, I really don’t care that the screen is black since I won’t have
anything to display locally while headless anyway, but the machine’s network
capability is nill also. In a headless system I want to use Phindows for a
user interface occassionally - but nothing. Can’t even ping the QNX box.

I looked at the CMOS setup for BIOS keyboard settings. Alternatives are
“Present” and “Not present” though this makes no difference with or without
a keyboard plugged in. I have systems with AT and PS/2 keyboards - same
thing.

Any other ideas before I get into rebuilding QNX images?

Jay


David Gibbs <dagibbs@qnx.com> wrote in message
news:8m9tfs$n1e$2@inn.qnx.com

Jay Marchetti <> marchetti@pittsburghfirmware.com> > wrote:
Ususually our target product has a full-up user interface, however in
some
systems we need to have our system boot “headless”, e.g. w/ no keyboard,
mouse, or monitor attached.

I have found that the system hangs during boot if no keyboard is
attached.
Can’t I have the system use the keyboard if one is there, but not hang
if
one is not there?

At what point is it hanging?

QNX shouldn’t care. In fact, I just booted the machine beside the
one I’m typeing on with the keyboard unplugged and it booted happily.
(Though, it was a PS/2 keyboard.) Is it a PS/2 keyboard, or an AT
keyboard?

But, likely, this is a BIOS problem, not a QNX issue – the BIOS is
looking for a keyboard well before it gets to the point of running
QNX.

If trying to collect information about how far something has gotten
in a boot sequence:

– leave the monitor attached > :slight_smile:
– rebuild your boot image with the specific inclusion, as the first
entry, of sys/boot, and give it the -v option. That is, the start
of your build file should look like:

sys/boot
$ boot -v

– make sure the first line of your sysinit is “set -v” (without the
quotes) to have the sysinit echo every command before executing it.

But, I’ll bet it dies in the BIOS, before it starts loading the OS. I’ve
seen amusing messages like:

“keyboard failure detected. Hit any key to continue.”

Displayed when trying to boot systems without a keyboard.

-David

Strange, what if you don’t start Photon?

“Jay Marchetti” <marchetti@pittsburghfirmware.com> wrote in message
news:8ma0bm$otu$1@inn.qnx.com

Its not an early BIOS failure, e.g. the machine goes through normal POST
stuff with no error messages, then the QNX loader runs w/o error messages
(still in text mode), then the screen is switched to graphics mode (it
normally boots into Photon) - but then: it just remains a black empty
graphics screen.

Now, I really don’t care that the screen is black since I won’t have
anything to display locally while headless anyway, but the machine’s
network
capability is nill also. In a headless system I want to use Phindows for a
user interface occassionally - but nothing. Can’t even ping the QNX box.

I looked at the CMOS setup for BIOS keyboard settings. Alternatives are
“Present” and “Not present” though this makes no difference with or
without
a keyboard plugged in. I have systems with AT and PS/2 keyboards - same
thing.

Any other ideas before I get into rebuilding QNX images?

Jay


David Gibbs <> dagibbs@qnx.com> > wrote in message
news:8m9tfs$n1e$> 2@inn.qnx.com> …
Jay Marchetti <> marchetti@pittsburghfirmware.com> > wrote:
Ususually our target product has a full-up user interface, however in
some
systems we need to have our system boot “headless”, e.g. w/ no
keyboard,
mouse, or monitor attached.

I have found that the system hangs during boot if no keyboard is
attached.
Can’t I have the system use the keyboard if one is there, but not hang
if
one is not there?

At what point is it hanging?

QNX shouldn’t care. In fact, I just booted the machine beside the
one I’m typeing on with the keyboard unplugged and it booted happily.
(Though, it was a PS/2 keyboard.) Is it a PS/2 keyboard, or an AT
keyboard?

But, likely, this is a BIOS problem, not a QNX issue – the BIOS is
looking for a keyboard well before it gets to the point of running
QNX.

If trying to collect information about how far something has gotten
in a boot sequence:

– leave the monitor attached > :slight_smile:
– rebuild your boot image with the specific inclusion, as the first
entry, of sys/boot, and give it the -v option. That is, the start
of your build file should look like:

sys/boot
$ boot -v

– make sure the first line of your sysinit is “set -v” (without the
quotes) to have the sysinit echo every command before executing it.

But, I’ll bet it dies in the BIOS, before it starts loading the OS.
I’ve
seen amusing messages like:

“keyboard failure detected. Hit any key to continue.”

Displayed when trying to boot systems without a keyboard.

-David

Jay Marchetti <marchetti@pittsburghfirmware.com> wrote:

Its not an early BIOS failure, e.g. the machine goes through normal POST
stuff with no error messages, then the QNX loader runs w/o error messages
(still in text mode), then the screen is switched to graphics mode (it
normally boots into Photon) - but then: it just remains a black empty
graphics screen.

Now, I really don’t care that the screen is black since I won’t have
anything to display locally while headless anyway, but the machine’s network
capability is nill also. In a headless system I want to use Phindows for a
user interface occassionally - but nothing. Can’t even ping the QNX box.

Make your own copy of the ‘ph’ startup script…

Don’t start a graphics driver.

Don’t start an input driver.

Jay Marchetti <marchetti@pittsburghfirmware.com> wrote:

Its not an early BIOS failure, e.g. the machine goes through normal POST
stuff with no error messages, then the QNX loader runs w/o error messages
(still in text mode), then the screen is switched to graphics mode (it
normally boots into Photon) - but then: it just remains a black empty
graphics screen.

Ah, well that is a missing piece of useful information. I think of
“boot” as get the operating system up & running. After boot, you
can then do things like run a GUI.

It looks like the trapping of the keyboard input is causing
a problem. Do you need to run Photon at all?

Or, if you do, you might want to play around with not running
inputtrap/Input.

Now, I really don’t care that the screen is black since I won’t have
anything to display locally while headless anyway, but the machine’s network
capability is nill also. In a headless system I want to use Phindows for a
user interface occassionally - but nothing. Can’t even ping the QNX box.

I looked at the CMOS setup for BIOS keyboard settings. Alternatives are
“Present” and “Not present” though this makes no difference with or without
a keyboard plugged in. I have systems with AT and PS/2 keyboards - same
thing.

Any other ideas before I get into rebuilding QNX images?

Don’t run Photon, that is, don’t boot into Photon.

-David


Jay



David Gibbs <> dagibbs@qnx.com> > wrote in message
news:8m9tfs$n1e$> 2@inn.qnx.com> …
Jay Marchetti <> marchetti@pittsburghfirmware.com> > wrote:
Ususually our target product has a full-up user interface, however in
some
systems we need to have our system boot “headless”, e.g. w/ no keyboard,
mouse, or monitor attached.

I have found that the system hangs during boot if no keyboard is
attached.
Can’t I have the system use the keyboard if one is there, but not hang
if
one is not there?

At what point is it hanging?

QNX shouldn’t care. In fact, I just booted the machine beside the
one I’m typeing on with the keyboard unplugged and it booted happily.
(Though, it was a PS/2 keyboard.) Is it a PS/2 keyboard, or an AT
keyboard?

But, likely, this is a BIOS problem, not a QNX issue – the BIOS is
looking for a keyboard well before it gets to the point of running
QNX.

If trying to collect information about how far something has gotten
in a boot sequence:

– leave the monitor attached > :slight_smile:
– rebuild your boot image with the specific inclusion, as the first
entry, of sys/boot, and give it the -v option. That is, the start
of your build file should look like:

sys/boot
$ boot -v

– make sure the first line of your sysinit is “set -v” (without the
quotes) to have the sysinit echo every command before executing it.

But, I’ll bet it dies in the BIOS, before it starts loading the OS. I’ve
seen amusing messages like:

“keyboard failure detected. Hit any key to continue.”

Displayed when trying to boot systems without a keyboard.

-David

The problem is likely not with QNX, but with the BIOS.
I regularly use/install QNX in settings like this.
Look at the BIOS settings around things like “System keyboard”
or “Halt on:”.
Is it a PC you’re using or an SBC?

Jay Marchetti wrote:

Ususually our target product has a full-up user interface, however in some
systems we need to have our system boot “headless”, e.g. w/ no keyboard,
mouse, or monitor attached.

I have found that the system hangs during boot if no keyboard is attached.
Can’t I have the system use the keyboard if one is there, but not hang if
one is not there?

We have the same problem with our Ampro PC/104
machines. We found that setting the appropriate options
to Dev.ansi solved the problem i.e we could set up the
computer to boot without keyboard and monitor. However, if we did add a
keyboard and monitor to a computer that was configured for none it would
also hang.

Larry

“Jay Marchetti” <marchetti@pittsburghfirmware.com> wrote in message
news:8m9pr7$lul$1@inn.qnx.com

Ususually our target product has a full-up user interface, however in some
systems we need to have our system boot “headless”, e.g. w/ no keyboard,
mouse, or monitor attached.

I have found that the system hangs during boot if no keyboard is attached.
Can’t I have the system use the keyboard if one is there, but not hang if
one is not there?

Regards,

Jay Marchetti
Pittsburgh Firmware

Funny, we have no such problem with our Ampro CoreModule 4DX[ei]
boards. We boot QNX4 without a keyboard all the time. When I
hook up the keyboard to debug something, it just works.

I think this is a BIOS/chipset thing. We have the Ampro Award
r1.05 and r1.06 BIOS revs.

Previously, Lawrence R. Sweet wrote in qdn.public.qnx4:

We have the same problem with our Ampro PC/104
machines. We found that setting the appropriate options
to Dev.ansi solved the problem i.e we could set up the
computer to boot without keyboard and monitor. However, if we did add a
keyboard and monitor to a computer that was configured for none it would
also hang.

Larry

[…]