Good point indeed!
I actually forgot to make the partition bootable the last few times I used
However, trying again (making the partition bootable) didn’t get me any
I included the technical stuff just in case the info would help, the only
really relevant thing is that I’m using compact flash memory as a hard disk.
Here’s a link with a lot more info on the subject (thanks Frank):
Anyway, I finalty got it working, this is how:
- Removed all partitions from CF
- Added FAT partition in win2000 (Kingston 128MB: CHS = 15:255:63)
- Back to QNX: into fdisk: Removed partition
- Added partition: Type 77 (QNX), start/end cylinders at default values
- Rebooted QNX
- Mounted everything:
(mount -e /dev/hd1 , mount /dev/hd1 /fs/hd1 , mount -t qnx4 /dev/hd1t77
- dinit -h /dev/hd1t77
- cp test.ifs /fs/hd1t77/.boot
Please note that I’m not sure everything is essential here, just to make it
By the way, every time starting fdisk in msdos/qnx, a different CHS was
reported until it finally seemed to ‘stabilize’ at CHS = 15:255:63
This is not the CHS reported in the pc bios.
“nntp.qnx.com” <firstname.lastname@example.org> escribió en el mensaje
“Joost de Folter” <> email@example.com> > wrote in message
news:cvku7u$r02$> firstname.lastname@example.org> …
I tried using fdisk (creating a QNX 77 partition manually) / using
(using the comon hd/pc type), all had the same effect:
When booting, the CF is not recognised as bootable device at all.
If I might ask a really dumb question. I’ve had zero experience with the
devices you are using but I just have to ask: Did you tell fdisk to make
that partition bootable (in addition to having it write the Loader)?
When comparing pc bios info with qnx, the format does read differently
at the bottom of my mail).
The only way that got me up to the point where I was (where the device
boot, but crashed), is by removing all partitions (like you in fact
suggested Evan), and then using the dinit comand:
dinit -h /dev/hd1 (on the RAW partition; in QNX my CF is detected (in an
reader) as a hard disk.)
Could the boot image be the problem?
I tried various, also the new disc on chip build file, but removed the
d.o.c. driver in the startup.
I have a CF type: Kingston 128MB CF (NAND type) (not their latest Elite
block size: 512
block size: 128
“Evan Hillas” <> email@example.com> > escribió en el mensaje
news:cvkabd$ckj$> firstname.lastname@example.org> …
Igor Kovalenko wrote:
2) There’s two ways to set up a bootable disk in QNX6 - the ‘old’ way
using fdisk utility and ‘new’ way using dloader utility.
Are you sure? I can’t test such ideas but reading the docs for dloader
only puts a bootblock on a disc. As far as I can tell it’s the same
bootblock files, namely /boot/sys/ipl-diskpc*, that fdisk also uses.
I have had much trouble in understanding the real cause of CF booting
my best guess so far is simply a mis-match between BIOS’s view of the
geometry while the bootblocks’ are using it until /.boot is loaded vs
devb-eide’s view of the geometry when fdisk is used to specify where
partitions are located.
There is good chance that all CF card’s that are configured
“partitionless” will boot just fine.