In order to discover the reason of the problem of my previous
message, we tried to run a kernel based on boot-nobios but on
a standard PC card and using netboot.
We created two kernels where the only change was using
boot-nobios instead of boot.
The kernel generated with normal boot always works fine, the
one generated with boot-nobios hangs at the initialization
without any diagnostic.
We tried the same couple of tests changing the other options
for boot or boot-nobios and we were never able to have the
second one working.
So we are going to go back with boot in the activity project and
to develop some bios stubs in order to finally have QNX working.
I would like to a have a clarification of this question.
Does some new version of boot-nobios exist ?
Thanks,
Enrico
–
| Enrico Bendinelli | Prisma Engineering srl |
| enricob@prisma-eng.it | Via Petrocchi 4 20127 MILANO ITALY |
| http://www.prisma-eng.it | Tel. +39 02 26113507 Fax. 26113597 |
Enrico Bendinelli <enricob@prisma-eng.it> wrote:
: In order to discover the reason of the problem of my previous
: message, we tried to run a kernel based on boot-nobios but on
: a standard PC card and using netboot.
: We created two kernels where the only change was using
: boot-nobios instead of boot.
: The kernel generated with normal boot always works fine, the
: one generated with boot-nobios hangs at the initialization
: without any diagnostic.
boot-nobios assumes a system without a bios that has custom IPL
(Initial Program Loader) that has configured the board and
switched to protected mode. This is not the case on a regular
desktop computer.
The regular bios boot option places some code at the beginning
of the image (called a preboot) which gathers bios information,
populates the startup information structures, switches the processor
to protected mode and copies the image to it’s predefined location
in RAM. It then jump to the entry point in startup. By contrast,
boot-nobios does nothing assuming all the above has been handled
by the IPL.
It might be helpful if you layed out exactly what it is you are
trying to accomplish (target hardware, booting method, etc …).
\
John
I was not able to find any documentation about boot-nobios but
a brief reference within Photon Help environment, that reports
the same options for both boot and boot-nobios.
Please let know about a document that where I can find more
details about this issue.
John Wall wrote:
Enrico Bendinelli <> enricob@prisma-eng.it> > wrote:
: In order to discover the reason of the problem of my previous
: message, we tried to run a kernel based on boot-nobios but on
: a standard PC card and using netboot.
: We created two kernels where the only change was using
: boot-nobios instead of boot.
: The kernel generated with normal boot always works fine, the
: one generated with boot-nobios hangs at the initialization
: without any diagnostic.
boot-nobios assumes a system without a bios that has custom IPL
(Initial Program Loader) that has configured the board and
switched to protected mode. This is not the case on a regular
desktop computer.
The regular bios boot option places some code at the beginning
of the image (called a preboot) which gathers bios information,
populates the startup information structures, switches the processor
to protected mode and copies the image to it’s predefined location
in RAM. It then jump to the entry point in startup. By contrast,
boot-nobios does nothing assuming all the above has been handled
by the IPL.
It might be helpful if you layed out exactly what it is you are
trying to accomplish (target hardware, booting method, etc …).
–
John
–
| Enrico Bendinelli | Prisma Engineering srl |
| enricob@prisma-eng.it | Via Petrocchi 4 20127 MILANO ITALY |
| http://www.prisma-eng.it | Tel. +39 02 26113507 Fax. 26113597 |