I downloaded QNX 6.2 and have it installed on a small machine that
I also am attempting to run FreeBSD 4.6.2 on. This is all in
regards to my Ph.D. research on multiplatform software development.
I have done:
FreeBSD installed to the first IDE disk and installing the FreeBSD
bootloader
QNX 6.2 installed to the second IDE disk, putting the boot in the
QNX partition (option F3 from the installation).
I’ve decided to use GRUB to multiboot (I’ve already had failed
attempts using the multi boot from FreeBSD and from QNX). I can
boot FreeBSD without any issues from GRUB.
When I attempt to multiboot QNX from GRUB, I get the following
…altboot…S
followed by a hung system. I know the installation is still
good because I can boot from the CDROM without any issues.
Any thoughts/suggestions on why the QNX boot hangs. And after
the QNX installation, I no logner have an active partition to
boot from - on either disk. Is booting to DOS and making one
active the only solution??
I’ve decided to use GRUB to multiboot (I’ve already had failed
attempts using the multi boot from FreeBSD and from QNX). I can
QNX isn’t MultiBoot compliant.
But on the installation, it tells you you can install their multiboot
loader.
When I attempt to multiboot QNX from GRUB, I get the following
.altboot…S
Post the menu.lst . You seem to be doing some weird.
I don’t yet have a menu.lst, I’ve been using GRUB interactively
from a floppy until I felt confident enough to install it on the
actual 1st EIDE drive.
‘S’ seems to say that the /.boot wasn’t a valid boot file.
try “cp /fs/cd0/boot/fs/qnxbase.ifs /fs/hd1-qnx4/.boot” from CDROM boot.
No such luck. Same result.
Tried qnxbasedma.ifs, with the same result - .altboot…S
Tried qnxbasesmp.ifs (even though its NOT an SMP machine) I
got the following:
F1 FreeBSD
F5 Drive 1
Default: F5
Press F1-F4 to select drive or select partition 1? 1
Hit Esc for .altboot…S
Which appears to be the FreeBSD multiboot manager (?).
This occurred because somehow because CDROM was empty,
and C drive was used to boot prior to floppy.
A reboot after the hang lead back to GRUB on the floppy
and it failed the same way as the other options
The interesting thing to note is that when I boot with the install
CDROM, I then chose boot from hard disk (F1) and it boots correctly
from the 2nd hard disk
‘S’ seems to say that the /.boot wasn’t a valid boot file.
try “cp /fs/cd0/boot/fs/qnxbase.ifs /fs/hd1-qnx4/.boot” from CDROM boot.
No such luck. Same result.
Then the bootloader isn’t even seeing the qnx partition.
I guess I can do something if onsite, but it seems beyond solving you alone;
if you don’t have GRUB/pc-booting guru there,
don’t try to be smart and install QNX on the first HDD.
(FreeBSD should be able to boot from 2nd)
‘S’ seems to say that the /.boot wasn’t a valid boot file.
try “cp /fs/cd0/boot/fs/qnxbase.ifs /fs/hd1-qnx4/.boot” from CDROM boot.
No such luck. Same result.
Then the bootloader isn’t even seeing the qnx partition.
I guess I can do something if onsite, but it seems beyond solving you alone;
if you don’t have GRUB/pc-booting guru there,
don’t try to be smart and install QNX on the first HDD.
(FreeBSD should be able to boot from 2nd)
Thanks for all your help. Moving it to the first drive was my
next option…
I’ve decided to use GRUB to multiboot (I’ve already had failed
attempts using the multi boot from FreeBSD and from QNX). I can
QNX isn’t MultiBoot compliant.
But on the installation, it tells you you can install their multiboot
loader.
QNX6.2 isn’t MultiBoot compliant. But I think that Grub MultiBoot support
is on the list for a future 6.2 update/patch. Ask your sales rep.
You just change your build files from
[virtual=x86,bios +compress]
to
Just put drive translation in GRUB (fake second HDD as first)
I’ve been booting QNX (two installations, one on first HDD and other on
second, with W2K and NetBSD without issues. Using any of XOSL or QNX boot
loader)
I downloaded QNX 6.2 and have it installed on a small machine that
I also am attempting to run FreeBSD 4.6.2 on. This is all in
regards to my Ph.D. research on multiplatform software development.
I have done:
FreeBSD installed to the first IDE disk and installing the FreeBSD
bootloader
QNX 6.2 installed to the second IDE disk, putting the boot in the
QNX partition (option F3 from the installation).
I’ve decided to use GRUB to multiboot (I’ve already had failed
attempts using the multi boot from FreeBSD and from QNX). I can
boot FreeBSD without any issues from GRUB.
When I attempt to multiboot QNX from GRUB, I get the following
.altboot…S
followed by a hung system. I know the installation is still
good because I can boot from the CDROM without any issues.
Any thoughts/suggestions on why the QNX boot hangs. And after
the QNX installation, I no logner have an active partition to
boot from - on either disk. Is booting to DOS and making one
active the only solution??
Just put drive translation in GRUB (fake second HDD as first)
I’ve been booting QNX (two installations, one on first HDD and other on
second, with W2K and NetBSD without issues. Using any of XOSL or QNX boot
loader)
“Akhilesh Mritunjai” <~mritun~@REMOVETHISBIT.me.iitb.ac.in.ANDTHISLASTBIT
wrote in message news:ao6ovh$f39$> 1@inn.qnx.com> …
Just put drive translation in GRUB (fake second HDD as first)
I’ve been booting QNX (two installations, one on first HDD and other on
second, with W2K and NetBSD without issues. Using any of XOSL or QNX boot
loader)
Just put drive translation in GRUB (fake second HDD as first)
I’ve been booting QNX (two installations, one on first HDD and other on
second, with W2K and NetBSD without issues. Using any of XOSL or QNX boot
loader)
I’ve decided to use GRUB to multiboot (I’ve already had failed
attempts using the multi boot from FreeBSD and from QNX). I can
QNX isn’t MultiBoot compliant.
But on the installation, it tells you you can install their multiboot
loader.
QNX6.2 isn’t MultiBoot compliant. But I think that Grub MultiBoot support
is on the list for a future 6.2 update/patch. Ask your sales rep.
You just change your build files from
[virtual=x86,bios +compress]
to
| and reality”