I have worked with QNX 6.1 version for some time, installed into Win98
operating system. It worked fine but there was a display driver problem that
is known to be fixed in the new QNX 6.2 version. So I now de-installed QNX
6.1 and installed the 6.2 version from the ISO-image. Installation worked
fine, but QNX now doesn’t boot anymore.
While trying to boot, the screen shows:
…
Detected EIDE. Scanning for devices.
/.diskroot file for root not found on any filesystem
Unable to locate fs-pkg
after this the boot process hangs.
I tried every available harddrive (C, D, E, F) for installation, with
different memory amounts for the file system (between 1000MB and 2000MB).
Neither the harddrive boots nor the BootDisc. It is always stoping at that
point described above.
There was already a similar news-message posted on 12.9.2002, but there
seemed to be no answer to that problem at that time. What can I do? Can
anybody help me?
/.diskroot file for root not found on any filesystem
This says it all.
If you’ve done the QNX supported, conventional install,
this shouldn’t happen
(so re-installing after all evidences erased is recommended;
tinkering further makes matter worse for beginners)
but to “fix” it:
boot from CDROM, and check for /fs/hd0-dos*-root.qfs/.diskboot .
If the file isn’t there, make a blank one.
If /fs/hd0-dos*-root.qfs/ isn’t there, …um, reinstall.
Recovery is dangerous unless you know what you’re really doing.
I’ve been not using FAT install for some time so maybe missing something.
Hmmm… And please don’t cross post. Kabe said it all and the same thing in
other words you can read at qdn.public.installation. Is it convenient?
Regards,
ed1k.
Nnamdi Kohn <nnamdi.kohn@tu-bs.de> wrote in message
news:b0s6tn$1r6$1@inn.qnx.com…
Hello,
I have worked with QNX 6.1 version for some time, installed into Win98
operating system. It worked fine but there was a display driver problem
that
is known to be fixed in the new QNX 6.2 version. So I now de-installed QNX
6.1 and installed the 6.2 version from the ISO-image. Installation worked
fine, but QNX now doesn’t boot anymore.
While trying to boot, the screen shows:
…
Detected EIDE. Scanning for devices.
/.diskroot file for root not found on any filesystem
Unable to locate fs-pkg
after this the boot process hangs.
I tried every available harddrive (C, D, E, F) for installation, with
different memory amounts for the file system (between 1000MB and 2000MB).
Neither the harddrive boots nor the BootDisc. It is always stoping at that
point described above.
There was already a similar news-message posted on 12.9.2002, but there
seemed to be no answer to that problem at that time. What can I do? Can
anybody help me?
I tried everything now but I didn’t manage to get QNX 6.2 running:
Adding the file /.diskroot helped to get rid of the error “/.diskroot file
for root not found on any filesystem”. But there was still the error “Unable
to locate fs-pkg”.
After this I decided to de-install QNX 6.2 from the Win98-Filesystem, delete
some files and create a primary partition (with partitionmagic) to install
QNX there (bootmenu from the CD). It shows the same error. QNX does not
boot.
Do you have some other suggestions what the problem could be?
/.diskroot file for root not found on any filesystem
This says it all.
If you’ve done the QNX supported, conventional install,
this shouldn’t happen
(so re-installing after all evidences erased is recommended;
tinkering further makes matter worse for beginners)
but to “fix” it:
boot from CDROM, and check for /fs/hd0-dos*-root.qfs/.diskboot .
If the file isn’t there, make a blank one.
If /fs/hd0-dos*-root.qfs/ isn’t there, …um, reinstall.
Recovery is dangerous unless you know what you’re really doing.
I’ve been not using FAT install for some time so maybe missing something.
Adding the file /.diskroot helped to get rid of the error “/.diskroot file
for root not found on any filesystem”. But there was still the error “Unable
to locate fs-pkg”.
As I said it’s not recommended to just “touch .diskroot” and hope it fixed.
(At least devb-eide seems to be running properly tho)
This time qnxbase.qfs seems corrupt, but this shouldn’t happen on
proper installation. Very Very Sick.
You should have ignored some errors or using some whacky configuration.
How’s the diagnostics from verbose boot? (Space-F6 during boot)
You still haven’t told us your machine configuration yet.
Tell what hardwares you use (everything) and how it’s connected,
in every detail. Oh, all BIOS setup should be consulted too.
I now completely removed EVERYTHING from my harddisk, configured two primary
partitions with partitionmagic and installed QNX 6.2 NC from the CD on the
first (bootable) harddisk partition. That should be the cleanest possible to
do.
How’s the diagnostics from verbose boot? (Space-F6 during boot)
I can’t write so fast as I read the errors (is there a possibility to log
the errors?), it often states ASC_MEDIA_NOT_PRESENT and also UDMA CRC error
…
I have tried to find the UDMA settings in the BIOS, but there is no
adjustment possible (I do not even know if it would help anything).
At the end there is always:
…
Starting with safe mode
Unmounting /fs/hd0-qnx4-qnxbase.qfs
Remounting /fs/hd0-qnx4/boot/fs/qnxbase.qfs as /pkgs/base
Remounting complete
Starting /proc/boot/devc-con -n4
Unable to locate fs-pkg
You still haven’t told us your machine configuration yet.
Tell what hardwares you use (everything) and how it’s connected,
in every detail. Oh, all BIOS setup should be consulted too.
1,4 GHz Athlon with K7T266 Pro motherboard (VIA VT8366 and VIA VT8233
chipset), 768 MB DDR RAM, …
what more is important?
What I don’t understand is, how come that QNX 6.1 runs properly while QNX
6.2 doesn’t even start on the same machine with the same BIOS and hardware
configuration.
Try to press (fast enough) Esc key during boot up to boot .alt OS image.
Alternative image should not use UDMA EIDE mode. Seems you have problems
with EIDE controller and UDMA mode, or QNX doesn’t properly support it…
QNX 6.1 probably was unable to force UDMA mode on your hardware, that’s why
it worked
I now completely removed EVERYTHING from my harddisk, configured two
primary
partitions with partitionmagic and installed QNX 6.2 NC from the CD on the
first (bootable) harddisk partition. That should be the cleanest possible
to
do.
How’s the diagnostics from verbose boot? (Space-F6 during boot)
I can’t write so fast as I read the errors (is there a possibility to log
the errors?), it often states ASC_MEDIA_NOT_PRESENT and also UDMA CRC
error
…
I have tried to find the UDMA settings in the BIOS, but there is no
adjustment possible (I do not even know if it would help anything).
At the end there is always:
…
Starting with safe mode
Unmounting /fs/hd0-qnx4-qnxbase.qfs
Remounting /fs/hd0-qnx4/boot/fs/qnxbase.qfs as /pkgs/base
Remounting complete
Starting /proc/boot/devc-con -n4
Unable to locate fs-pkg
You still haven’t told us your machine configuration yet.
Tell what hardwares you use (everything) and how it’s connected,
in every detail. Oh, all BIOS setup should be consulted too.
1,4 GHz Athlon with K7T266 Pro motherboard (VIA VT8366 and VIA VT8233
chipset), 768 MB DDR RAM, …
what more is important?
What I don’t understand is, how come that QNX 6.1 runs properly while QNX
6.2 doesn’t even start on the same machine with the same BIOS and hardware
configuration.
Remounting /fs/hd0-qnx4/boot/fs/qnxbase.qfs as /pkgs/base
Remounting complete
Starting /proc/boot/devc-con -n4
Unable to locate fs-pkg
devc-con should be from /pkgs/base/qnx/os/*/x86/sbin/devc-con.
/pkgs/base isn’t mounted properly. Very Very Sick.
You may want to “chkfsys qnxbase.qfs” just in case –
if problems reported, the CD-R wasn’t burnt properly.
(No gurantee for correctness if no problems reported tho)
1,4 GHz Athlon with K7T266 Pro motherboard (VIA VT8366 and VIA VT8233
chipset), 768 MB DDR RAM, …
what more is important?
Don’t shun info only because you think it unimportant.
(Below is the general list; it may not apply to you)
spec/brand of the HDD?
How many are hooked up?
spec/brand of CDROM drive?
How are those cabled to the motherboard?
Using any add-on IDE card? (FastTrack etc)
Is master/slave configured properly?
“It works on Linux/Windoze!” doesn’t justify.
Sure the IDE cable isn’t defect?
Cooling? (IDE will be flaky on overheat)
Onboard peripherals (some readers will sacrifice time to lookup ASUS site,
but majority won’t; and nobody will know soldering options)
“pci -vvv” may help from 6.1 boot.
How’s the memory cards inserted? (you can’t have 768MB by single DDR)
Is installation conformant to the MB’s manual?
with EIDE controller and UDMA mode, or QNX doesn’t properly support it…
QNX 6.1 probably was unable to force UDMA mode on your hardware, that’s why
it worked >
Maybe. Maybe not.
As it could read /.diskroot from qnxbase.qfs (/pkgs/base),
the data transfer seems to be working.
Or only failing on multisector transfers??
Try to press (fast enough) Esc key during boot up to boot .alt OS image.
Alternative image should not use UDMA EIDE mode. Seems you have problems
with EIDE controller and UDMA mode, or QNX doesn’t properly support it…
QNX 6.1 probably was unable to force UDMA mode on your hardware, that’s
why
it worked >
Best regards.
Eduard.
Nnamdi Kohn <> nnamdi.kohn@tu-bs.de> > wrote in message
news:b163su$4lc$> 1@inn.qnx.com> …
I now completely removed EVERYTHING from my harddisk, configured two
primary
partitions with partitionmagic and installed QNX 6.2 NC from the CD on
the
first (bootable) harddisk partition. That should be the cleanest
possible
to
do.
How’s the diagnostics from verbose boot? (Space-F6 during boot)
I can’t write so fast as I read the errors (is there a possibility to
log
the errors?), it often states ASC_MEDIA_NOT_PRESENT and also UDMA CRC
error
…
I have tried to find the UDMA settings in the BIOS, but there is no
adjustment possible (I do not even know if it would help anything).
At the end there is always:
…
Starting with safe mode
Unmounting /fs/hd0-qnx4-qnxbase.qfs
Remounting /fs/hd0-qnx4/boot/fs/qnxbase.qfs as /pkgs/base
Remounting complete
Starting /proc/boot/devc-con -n4
Unable to locate fs-pkg
You still haven’t told us your machine configuration yet.
Tell what hardwares you use (everything) and how it’s connected,
in every detail. Oh, all BIOS setup should be consulted too.
1,4 GHz Athlon with K7T266 Pro motherboard (VIA VT8366 and VIA VT8233
chipset), 768 MB DDR RAM, …
what more is important?
What I don’t understand is, how come that QNX 6.1 runs properly while
QNX
6.2 doesn’t even start on the same machine with the same BIOS and
hardware
configuration.
Try to press (fast enough) Esc key during boot up to boot .alt OS image.
Alternative image should not use UDMA EIDE mode. Seems you have problems
with EIDE controller and UDMA mode, or QNX doesn’t properly support
it…
QNX 6.1 probably was unable to force UDMA mode on your hardware, that’s
why
it worked >
Best regards.
Eduard.
Nnamdi Kohn <> nnamdi.kohn@tu-bs.de> > wrote in message
news:b163su$4lc$> 1@inn.qnx.com> …
I now completely removed EVERYTHING from my harddisk, configured two
primary
partitions with partitionmagic and installed QNX 6.2 NC from the CD on
the
first (bootable) harddisk partition. That should be the cleanest
possible
to
do.
How’s the diagnostics from verbose boot? (Space-F6 during boot)
I can’t write so fast as I read the errors (is there a possibility to
log
the errors?), it often states ASC_MEDIA_NOT_PRESENT and also UDMA CRC
error
…
I have tried to find the UDMA settings in the BIOS, but there is no
adjustment possible (I do not even know if it would help anything).
At the end there is always:
…
Starting with safe mode
Unmounting /fs/hd0-qnx4-qnxbase.qfs
Remounting /fs/hd0-qnx4/boot/fs/qnxbase.qfs as /pkgs/base
Remounting complete
Starting /proc/boot/devc-con -n4
Unable to locate fs-pkg
You still haven’t told us your machine configuration yet.
Tell what hardwares you use (everything) and how it’s connected,
in every detail. Oh, all BIOS setup should be consulted too.
1,4 GHz Athlon with K7T266 Pro motherboard (VIA VT8366 and VIA VT8233
chipset), 768 MB DDR RAM, …
what more is important?
What I don’t understand is, how come that QNX 6.1 runs properly while
QNX
6.2 doesn’t even start on the same machine with the same BIOS and
hardware
configuration.
It forces devb-eide not to use dma modes, i.e. system will use PIO mode for
disk operations. It’s slowly and require CPU intervension for
reading/writing hard disk, but it should reliable work. You should decide if
it answers your requirements. I’m unaware of another limitations.
Can I configure QNX 6.2 to boot .alt OS image automatically?
Try to press (fast enough) Esc key during boot up to boot .alt OS image.
Alternative image should not use UDMA EIDE mode. Seems you have problems
with EIDE controller and UDMA mode, or QNX doesn’t properly support
it…
QNX 6.1 probably was unable to force UDMA mode on your hardware, that’s
why
it worked >
Best regards.
Eduard.
Nnamdi Kohn <> nnamdi.kohn@tu-bs.de> > wrote in message
news:b163su$4lc$> 1@inn.qnx.com> …
I now completely removed EVERYTHING from my harddisk, configured two
primary
partitions with partitionmagic and installed QNX 6.2 NC from the CD on
the
first (bootable) harddisk partition. That should be the cleanest
possible
to
do.
How’s the diagnostics from verbose boot? (Space-F6 during boot)
I can’t write so fast as I read the errors (is there a possibility to
log
the errors?), it often states ASC_MEDIA_NOT_PRESENT and also UDMA CRC
error
…
I have tried to find the UDMA settings in the BIOS, but there is no
adjustment possible (I do not even know if it would help anything).
At the end there is always:
…
Starting with safe mode
Unmounting /fs/hd0-qnx4-qnxbase.qfs
Remounting /fs/hd0-qnx4/boot/fs/qnxbase.qfs as /pkgs/base
Remounting complete
Starting /proc/boot/devc-con -n4
Unable to locate fs-pkg
You still haven’t told us your machine configuration yet.
Tell what hardwares you use (everything) and how it’s connected,
in every detail. Oh, all BIOS setup should be consulted too.
1,4 GHz Athlon with K7T266 Pro motherboard (VIA VT8366 and VIA VT8233
chipset), 768 MB DDR RAM, …
what more is important?
What I don’t understand is, how come that QNX 6.1 runs properly while
QNX
6.2 doesn’t even start on the same machine with the same BIOS and
hardware
configuration.
