I had similar problems with my initial program loader IPL, which is
outputting the
Hit Esc for .altboot…D
(but mine always output the D before hanging)
How I got around it was to do two things:
- I slowed down the RAM speed setting in my BIOS (!) from 60ns to 70ns.
- My boot script did not use compression - ie don’t use +compress in your
“virtual(x86,bios)” line (syntax approximate)
Doing those two things allowed my boot script to run about 60% of the time
instead of 0% of the time previously…
I’d still like to get to the bottom of this, and am in discussions with the
ST PC104plus computer manufacturer, MSC.
You might like to try what I found, to see if it makes any difference. I’ve
also heard mention in other postings that the floppy or floppy drive may be
bad, but that didn’t seem to be my problem.
My theory goes something like this:
The IPL loads the .boot file into RAM, and the . after “Hit Esc for
…altboot” indicate progress in this way, so my guess is the IPL can’t
continue due to some I/O problem with the file system (floppy or HDD boot)
and/or RAM. The root cause may be BIOS-dependant or hardware-dependant, at
this point I am not sure. Since the IPL program from QNX is sparsely
instrumented (I’m using secondary loader ipl-diskpc2-flop), it is difficult
to see what it chokes on. (see
http://qdn.qnx.com/support/bok/solution.qnx?10389 for more info on x86 ipl
variants)
Anyone else have anything to add?
Good luck,
Tony Nordstrom
“Cipriano Patrik” <patrik.cipriano@unaxis.com> wrote in message
news:acv7bj$n70$1@inn.qnx.com…
Hallo,
I have a small problem booting my Image made with mkifs.
I have two CF Cards. One with 128MB (Sandisk) one with 64MB (Mitsubishi).
I use the same procedure on both to initialize them but only the Sandisk
starts the startup script.
The Mitsubishi card stops after :
Boot Partition 1 ? 1
Hit Esc for .Altboot
…
It does not start the startup script.
Strange is that on the Sandisk there is no “Boot Partition 1?1” line.
But the startup script is started without problems.
- I make the Partition type 79 with fdisk. And I mark it “Bootable”.
- mount /dev/hd1t79 /fs/sandisk
- dinit -hf gsm.ifs /dev/hd1t79
- chkfsys -Vu /fs/sandisk
I think the problem is the bootloader. But who knows.
PS: I use QNX RTP 6.1 on a x86 platform
Best Regards
Patrik Cipriano