Problems with 6.1.0 installation on ServerWorks LE

[No crossposting at all? Grrr. Also posted to <comp.os.qnx>, slightly
different subject.]

Peter E. Fry wrote:

Anybody try this? I just did, for the heck of it. No go. ASUS
CUR-DLS, or more precisely the Gateway 6400 OEM version of the board.
If I had to take a wild guess I’d say the PCI scanner’s choking on the
second PCI bus, which happens to be where the LSI 53c1010-33 sits. […]

OK, getting serious: Starting with F6 (verbose) and F10 (partition
install), message is:

Starting pci-bios
Range check failed (IO) - Dev 211 - Vend 1166 - Class 1018a
Addr ffa0 - Size 10

…and ncr8 finds nothing. Problem is, device 211 is the IDE controller
(according to the data at http://www.yourvote.com/pci/), and it works
– it mounts the CD. Then again, it ends with a “cannot locate
finstall” or some such (dang it – didn’t write that down, and swapping
boxes is a giant PITA).
So… Exactly what’s the failure here…? A quick search of
<comp.os.qnx> pulled up a few mentions, but no specifics or fixes. A
search on <www.qnx.com> came up empty.
I did accidentally drop through the boot with no options selected, and
received (a message similar to) “no qnx 6.1 partition to mount”.
I don’t recall having such difficulties with an IDE HDD. I would
expect a listing of available HDDs during startup, but I could just be
high. Would it be profitable to drop to a prompt and dig a bit? I have
to swap external peripherals – I have little space and one set handy,
and the bloody thing takes forever to boot (2.5GB RAM, SCSI), so I don’t
care to plug it up again tonight.
BIOS is AMI 0AAWGP20 (latest on Gateway’s site), SCSI BIOS is 4.17.00,
by the way.

Peter E. Fry

“Peter E. Fry” wrote:
[…]

…and ncr8 finds nothing. […]

I assume ncr8 would post a console message, especially in verbose
mode. What’s the chance that the driver misses the 53c1010-33, as it
has a unique PCI dev ID?

Peter E. Fry

Hi Peter,

Just checked the code, and support for the 53c1010-33/66 were just added
in the code. The update will hopefully make the next release.

Erick.


Peter E. Fry <pfry@swbell.net> wrote:

“Peter E. Fry” wrote:
[…]
…and ncr8 finds nothing. […]

I assume ncr8 would post a console message, especially in verbose
mode. What’s the chance that the driver misses the 53c1010-33, as it
has a unique PCI dev ID?

Peter E. Fry

Hi Peter,

My mistake, the 1010 is not supported at this time. Please ignore my last post.

Erick.


Hardware Support Account <hw@qnx.com> wrote:

Hi Peter,

Just checked the code, and support for the 53c1010-33/66 were just added
in the code. The update will hopefully make the next release.

Erick.



Peter E. Fry <> pfry@swbell.net> > wrote:
“Peter E. Fry” wrote:
[…]
…and ncr8 finds nothing. […]

I assume ncr8 would post a console message, especially in verbose
mode. What’s the chance that the driver misses the 53c1010-33, as it
has a unique PCI dev ID?

Peter E. Fry

Hardware Support Account wrote:

Hi Peter,

My mistake, the 1010 is not supported at this time. Please ignore my last post.

Awww… Crud. Might want to pull it from the page:
http://qdn.qnx.com/support/hardware/platform/filesystem.html.
Back to the old Athlon and the “disappearing CD drive”…

Peter E. Fry

Hi Peter,

Thanks for letting me know about the website, I have now updated it.

Erick.


Peter E. Fry <pfry@swbell.net> wrote:

Hardware Support Account wrote:

Hi Peter,

My mistake, the 1010 is not supported at this time. Please ignore my last post.

Awww… Crud. Might want to pull it from the page:
http://qdn.qnx.com/support/hardware/platform/filesystem.html> .
Back to the old Athlon and the “disappearing CD drive”…

Peter E. Fry