Following up my own post (after some more noodling with the system
in question) I wrote:
I’m working with the 4.25 diskset, and a 4.25A boot floppy.
The boot floppy seems to have no trouble seeing the full drive (I’m
making the entire drive one large QNX partition) but after the
apparently successful installation completes and I reboot, I get a
message saying the partition is too large for the drive when the
system gets to the second loader.
I believe that I’m not getting the verson of Fsys.eide that I need
onto the drive.
I managed to get the same version of Fsys.eide onto the hard drive.
I doesn’t help: when the system gets to the second loader it still
complains about the partition not fitting on the drive.
A quick rundown of the H/W and S/W I’m working with:
- ASUS P3V4X motherboard with 64MB RAM.
- Quantum LM10.2 10.2GB hard drive, with shielded 80-pin ribbon.
- QNX 4.25 installation diskset with v4.25A boot floppy. (Fsys.eide
with >8.4GB HD support.)
With the above settings and gear, the installation seems to proceed
normally, with one exception. Early in the install after executing
Fsys.eide, the system pauses and begins to print out the following
Waiting for /dev/hd0 to initialize.
This is repeated nine times, and then the installation continues.
[Note: While this message is not printed, there is also a noticeable
delay if I boot from the install boot floppy and manually run
Fsys.eide before I get a console message indicating that the HD
has been recognized.]
Since this system will be dedicated to QNX, I instruct fdisk to create
a single partition on the drive that uses all of the available space.
[Note: I have seen messages that indicate that the requirement is
that the entire boot file be below the 1024 cyliner range because
of a BIOS limitation. With the size of the 4.25 OS, this should
not be a problem, but does this limitation mean that I cannot
successfully create a single QNX partition larger than 8.2GB?]
The installation seems to complete successfully. Before rebooting I am
able to list and run commands from /hd.
After taking out the last floppy and rebooting, the system restarts
and seems to have no difficulty with the primary loader. It gets to
the secondary loader and prints:
and then after a delay, it prints the following to the console:
Path=0 - EIDE
target=0 lun=0 Direct-Access(0) - QUANTUM FIREBALL Rev:
mount -p: cannot mount partition 77 (04dh) on /dev/hd0:
error No space left on device
disk /dev/hd0 has 16514064 sectors
partition (63…20065185) does not fit within disk
If I reboot from the installation boot floppy and run fdisk on
/dev/hd0, QNX’s fdisk reports the following:
Start cylinder: 0
End cylinder: 1248
255 heads/63 sectors-per-track/1249 heads
Why does the loader report that /dev/hd0 has 16514064 sectors
when fdisk reports 20065185?
I’ve confirmed that the version of /bin/Fsys.eide that appears on
/dev/hd0 is the one from the v4.25A boot floppy. I’ve also tried
changing the drive parameters:
HD Type from “Auto” to “User Defined”
HD Translation to “match partition table”
and I’ve tried disabling UDMA in the BIOS. So far nothing has changed
the behaviour on bootup.
I know that others have had trouble with larger drives. In fact, from
some earlier postings I had saved, the 10GB drives seemed to be more
trouble than drives in the 20 and 30GB range.
Can someone point me in the right direction so that I can get the
system booting (and then try configuring all of the other new
hardware in the system!)?
Thanks in advance.