6.2.1 on HP ML350 G3

bridged with qdn.public.qnxrtp.installation
Post Reply
Johannes

6.2.1 on HP ML350 G3

Post by Johannes » Sat Oct 11, 2003 12:40 am

Has anyone try 6.2.1 on HP ML350 G3 with single processor? I tried it but
looks like 6.2.1 does not recognize the SCSI drive and Ethernet Adaptor.

Is this machine supported? or do I miss any driver?

Thanks

Chris McKillop

Re: 6.2.1 on HP ML350 G3

Post by Chris McKillop » Sat Oct 11, 2003 2:29 am

Johannes <Jsukamtoh@infolink.co.id> wrote:
Has anyone try 6.2.1 on HP ML350 G3 with single processor? I tried it but
looks like 6.2.1 does not recognize the SCSI drive and Ethernet Adaptor.

Is this machine supported? or do I miss any driver?
What are the makes/models of those devices?

chris

--
Chris McKillop <cdm@qnx.com> "The faster I go, the behinder I get."
Software Engineer, QSSL -- Lewis Carroll --
http://qnx.wox.org/

Johannes

Re: 6.2.1 on HP ML350 G3

Post by Johannes » Sat Oct 11, 2003 8:25 am

It's a Hewlette Packard Proliant Intel-based server computer (it used to be
Compaq Proliant ML350 Generation 3 Server). Its CPU is Xeon, with Adaptec
SCSI AIC-7899W and 72GB harddisk. It's dual processor capability, but
currently we have only one processor installed. 2GByte of RAM.

If I tried to install 6.2.1 from CD, it shows the following error:
aha8_chim_ini: Unable to verify hardware
aha8_init: Unable to initialize CHIM

So I disable the onboard SCSI and plug in an Adaptec SCSI Card 29160 Ultra
160 SCSI Controller, which is specified as one of the supported SCSI Card in
QNX website. But when I try to install 6.2.1 from CD, it shows the
following:
Could not get drive info for /dev/hd0

"Chris McKillop" <cdm@qnx.com> wrote in message
news:bm7pun$b1f$1@nntp.qnx.com...
Johannes <Jsukamtoh@infolink.co.id> wrote:
Has anyone try 6.2.1 on HP ML350 G3 with single processor? I tried it
but
looks like 6.2.1 does not recognize the SCSI drive and Ethernet Adaptor.

Is this machine supported? or do I miss any driver?


What are the makes/models of those devices?

chris

--
Chris McKillop <cdm@qnx.com> "The faster I go, the behinder I get."
Software Engineer, QSSL -- Lewis Carroll --
http://qnx.wox.org/

Johannes

Re: 6.2.1 on HP ML350 G3

Post by Johannes » Wed Oct 15, 2003 11:14 pm

Hi Chris, any idea what is the meaning of the following errors?
aha8_chim_ini: Unable to verify hardware
aha8_init: Unable to initialize CHIM

I am still trying to install 6.2.1A in this machine and I hope QSSL could
give me a solution. I have tried the same SCSI and harddisk on Dell Optiplex
L60 and it works, but why is it not working on HP Proliant ML350?

"Chris McKillop" <cdm@qnx.com> wrote in message
news:bm7pun$b1f$1@nntp.qnx.com...
Johannes <Jsukamtoh@infolink.co.id> wrote:
Has anyone try 6.2.1 on HP ML350 G3 with single processor? I tried it
but
looks like 6.2.1 does not recognize the SCSI drive and Ethernet Adaptor.

Is this machine supported? or do I miss any driver?


What are the makes/models of those devices?

chris

--
Chris McKillop <cdm@qnx.com> "The faster I go, the behinder I get."
Software Engineer, QSSL -- Lewis Carroll --
http://qnx.wox.org/

Igor Kovalenko

Re: 6.2.1 on HP ML350 G3

Post by Igor Kovalenko » Thu Oct 16, 2003 2:47 am

The aha8 (Adaptec) driver in QNX6 is designed to use CHIM (common hardware
interface module) that is a binary platform-independent code supplied by
Adaptec. This message probably means that the version of CHIM they currently
have does not know how to deal with your card.

Or it could be simpler - HP might have changed vendor and device ids to make
it look like HP. Or this particular device is not sold by Adaptec at all and
manufactured as OEM part specifically for HP (I know Adaptec did that for
Dell), in which case the device/vendor id would also be HP-specific I guess.
Either way, it is possible that Adaptec's CHIM does not work with OEM parts,
because they are supposed to be supported by vendors.

"Johannes" <Jsukamtoh@infolink.co.id> wrote in message
news:bmkjdc$4or$1@inn.qnx.com...
Hi Chris, any idea what is the meaning of the following errors?
aha8_chim_ini: Unable to verify hardware
aha8_init: Unable to initialize CHIM

I am still trying to install 6.2.1A in this machine and I hope QSSL could
give me a solution. I have tried the same SCSI and harddisk on Dell
Optiplex
L60 and it works, but why is it not working on HP Proliant ML350?

"Chris McKillop" <cdm@qnx.com> wrote in message
news:bm7pun$b1f$1@nntp.qnx.com...
Johannes <Jsukamtoh@infolink.co.id> wrote:
Has anyone try 6.2.1 on HP ML350 G3 with single processor? I tried it
but
looks like 6.2.1 does not recognize the SCSI drive and Ethernet
Adaptor.

Is this machine supported? or do I miss any driver?


What are the makes/models of those devices?

chris

--
Chris McKillop <cdm@qnx.com> "The faster I go, the behinder I
get."
Software Engineer, QSSL -- Lewis Carroll --
http://qnx.wox.org/



Johannes

Re: 6.2.1 on HP ML350 G3

Post by Johannes » Thu Oct 16, 2003 3:36 am

Thanks Igor.

Instead of using the integrated SCSI, I plug in an Adaptec 29160 SCSI card
with its harddisk. It doesn't work in ML350 but it works on Dell. Any idea
why? I have to use ML350 now because my customer has purchased that machine.

"Igor Kovalenko" <kovalenko@attbi.com> wrote in message
news:bmkvuc$ch8$1@inn.qnx.com...
The aha8 (Adaptec) driver in QNX6 is designed to use CHIM (common hardware
interface module) that is a binary platform-independent code supplied by
Adaptec. This message probably means that the version of CHIM they
currently
have does not know how to deal with your card.

Or it could be simpler - HP might have changed vendor and device ids to
make
it look like HP. Or this particular device is not sold by Adaptec at all
and
manufactured as OEM part specifically for HP (I know Adaptec did that for
Dell), in which case the device/vendor id would also be HP-specific I
guess.
Either way, it is possible that Adaptec's CHIM does not work with OEM
parts,
because they are supposed to be supported by vendors.

"Johannes" <Jsukamtoh@infolink.co.id> wrote in message
news:bmkjdc$4or$1@inn.qnx.com...
Hi Chris, any idea what is the meaning of the following errors?
aha8_chim_ini: Unable to verify hardware
aha8_init: Unable to initialize CHIM

I am still trying to install 6.2.1A in this machine and I hope QSSL
could
give me a solution. I have tried the same SCSI and harddisk on Dell
Optiplex
L60 and it works, but why is it not working on HP Proliant ML350?

"Chris McKillop" <cdm@qnx.com> wrote in message
news:bm7pun$b1f$1@nntp.qnx.com...
Johannes <Jsukamtoh@infolink.co.id> wrote:
Has anyone try 6.2.1 on HP ML350 G3 with single processor? I tried
it
but
looks like 6.2.1 does not recognize the SCSI drive and Ethernet
Adaptor.

Is this machine supported? or do I miss any driver?


What are the makes/models of those devices?

chris

--
Chris McKillop <cdm@qnx.com> "The faster I go, the behinder I
get."
Software Engineer, QSSL -- Lewis Carroll --
http://qnx.wox.org/





Igor Kovalenko

Re: 6.2.1 on HP ML350 G3

Post by Igor Kovalenko » Thu Oct 16, 2003 5:37 am

That is unusual. I have 29160 controller in my own system and it works just
fine... OTOH, I have had experience with certain RAID controllers working in
one system but not in another (even under Windows).

Can you post output of pci -v?

Make sure you have the internal SCSI controller disabled in the BIOS Setup.
The enumerator can get confused or it may have a bug. Then make sure that
when you boot your system the SCSI BIOS (residing on the 29160) gets to
run - I have seen weird BIOSes that disalow loading BIOS extensions by
default. Finally, try to boot from the installation CD using 'safe mode'
(minimum of drivers) and then start the driver from command line manually.

-- igor

"Johannes" <Jsukamtoh@infolink.co.id> wrote in message
news:bml2pq$ea6$1@inn.qnx.com...
Thanks Igor.

Instead of using the integrated SCSI, I plug in an Adaptec 29160 SCSI card
with its harddisk. It doesn't work in ML350 but it works on Dell. Any idea
why? I have to use ML350 now because my customer has purchased that
machine.

"Igor Kovalenko" <kovalenko@attbi.com> wrote in message
news:bmkvuc$ch8$1@inn.qnx.com...
The aha8 (Adaptec) driver in QNX6 is designed to use CHIM (common
hardware
interface module) that is a binary platform-independent code supplied by
Adaptec. This message probably means that the version of CHIM they
currently
have does not know how to deal with your card.

Or it could be simpler - HP might have changed vendor and device ids to
make
it look like HP. Or this particular device is not sold by Adaptec at all
and
manufactured as OEM part specifically for HP (I know Adaptec did that
for
Dell), in which case the device/vendor id would also be HP-specific I
guess.
Either way, it is possible that Adaptec's CHIM does not work with OEM
parts,
because they are supposed to be supported by vendors.

"Johannes" <Jsukamtoh@infolink.co.id> wrote in message
news:bmkjdc$4or$1@inn.qnx.com...
Hi Chris, any idea what is the meaning of the following errors?
aha8_chim_ini: Unable to verify hardware
aha8_init: Unable to initialize CHIM

I am still trying to install 6.2.1A in this machine and I hope QSSL
could
give me a solution. I have tried the same SCSI and harddisk on Dell
Optiplex
L60 and it works, but why is it not working on HP Proliant ML350?

"Chris McKillop" <cdm@qnx.com> wrote in message
news:bm7pun$b1f$1@nntp.qnx.com...
Johannes <Jsukamtoh@infolink.co.id> wrote:
Has anyone try 6.2.1 on HP ML350 G3 with single processor? I tried
it
but
looks like 6.2.1 does not recognize the SCSI drive and Ethernet
Adaptor.

Is this machine supported? or do I miss any driver?


What are the makes/models of those devices?

chris

--
Chris McKillop <cdm@qnx.com> "The faster I go, the behinder I
get."
Software Engineer, QSSL -- Lewis Carroll --
http://qnx.wox.org/







Johannes

Re: 6.2.1 on HP ML350 G3

Post by Johannes » Thu Oct 16, 2003 2:28 pm

Here is the output for the SCSI card from pci -vvv

Class = Mass Storage (SCSI)
Vendor ID = 9005h, Adaptec
Device ID = 80h, AIC-7892A Ultra160/m PCI SCSI Controller
PCI index = 0h
Class Codes = 010000h
Revision ID = 2h
Bus number = 0
Device number = 1
Function num = 0
Status Reg = 2b0h
Command Reg = 57h
I/O space access enabled
Memory space access enabled
Bus Master enabled
Special Cycle operations ignored
Memory Write and Invalidate enabled
Palette Snooping disabled
Parity Checking disabled
Data/Address stepping enabled
SERR# driver disabled
Fast back-to-back transactions to different agents disabled
Header type = 0h Single-function
BIST = 80h Selftest OK
Latency Timer = 40h
Cache Line Size= 10h un-cacheable
PCI IO Address = 2400h length 256 enabled
PCI Mem Address = f7ef0000h 64bit length 4096 enabled
Subsystem Vendor ID = 9005h
Subsystem ID = e2a0h
Max Lat = 25ns
Min Gnt = 40ns
PCI Int Pin = INT A
Interrupt line = 3
Capabilities Pointer = dch
Capability ID = 1h
Capabilities = 2h - 0h
Device Dependent Registers:
0x40: 02 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xD0: 00 00 00 00 00 00 00 00 00 00 00 00 01 00 02 00
0xE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Everything looks OK to me and I think it recognizes the card, but not sure
why it can't initialize it.

"Igor Kovalenko" <kovalenko@attbi.com> wrote in message
news:bml9tc$ii7$1@inn.qnx.com...
That is unusual. I have 29160 controller in my own system and it works
just
fine... OTOH, I have had experience with certain RAID controllers working
in
one system but not in another (even under Windows).

Can you post output of pci -v?

Make sure you have the internal SCSI controller disabled in the BIOS
Setup.
The enumerator can get confused or it may have a bug. Then make sure that
when you boot your system the SCSI BIOS (residing on the 29160) gets to
run - I have seen weird BIOSes that disalow loading BIOS extensions by
default. Finally, try to boot from the installation CD using 'safe mode'
(minimum of drivers) and then start the driver from command line manually.

-- igor

"Johannes" <Jsukamtoh@infolink.co.id> wrote in message
news:bml2pq$ea6$1@inn.qnx.com...
Thanks Igor.

Instead of using the integrated SCSI, I plug in an Adaptec 29160 SCSI
card
with its harddisk. It doesn't work in ML350 but it works on Dell. Any
idea
why? I have to use ML350 now because my customer has purchased that
machine.

"Igor Kovalenko" <kovalenko@attbi.com> wrote in message
news:bmkvuc$ch8$1@inn.qnx.com...
The aha8 (Adaptec) driver in QNX6 is designed to use CHIM (common
hardware
interface module) that is a binary platform-independent code supplied
by
Adaptec. This message probably means that the version of CHIM they
currently
have does not know how to deal with your card.

Or it could be simpler - HP might have changed vendor and device ids
to
make
it look like HP. Or this particular device is not sold by Adaptec at
all
and
manufactured as OEM part specifically for HP (I know Adaptec did that
for
Dell), in which case the device/vendor id would also be HP-specific I
guess.
Either way, it is possible that Adaptec's CHIM does not work with OEM
parts,
because they are supposed to be supported by vendors.

"Johannes" <Jsukamtoh@infolink.co.id> wrote in message
news:bmkjdc$4or$1@inn.qnx.com...
Hi Chris, any idea what is the meaning of the following errors?
aha8_chim_ini: Unable to verify hardware
aha8_init: Unable to initialize CHIM

I am still trying to install 6.2.1A in this machine and I hope QSSL
could
give me a solution. I have tried the same SCSI and harddisk on Dell
Optiplex
L60 and it works, but why is it not working on HP Proliant ML350?

"Chris McKillop" <cdm@qnx.com> wrote in message
news:bm7pun$b1f$1@nntp.qnx.com...
Johannes <Jsukamtoh@infolink.co.id> wrote:
Has anyone try 6.2.1 on HP ML350 G3 with single processor? I
tried
it
but
looks like 6.2.1 does not recognize the SCSI drive and Ethernet
Adaptor.

Is this machine supported? or do I miss any driver?


What are the makes/models of those devices?

chris

--
Chris McKillop <cdm@qnx.com> "The faster I go, the behinder
I
get."
Software Engineer, QSSL -- Lewis Carroll --
http://qnx.wox.org/









Guest

Re: 6.2.1 on HP ML350 G3

Post by Guest » Thu Oct 16, 2003 6:17 pm

kovalenko@attbi.com sed in <bml9tc$ii7$1@inn.qnx.com>:
Make sure you have the internal SCSI controller disabled in the BIOS Setup.
The enumerator can get confused or it may have a bug. Then make sure that
when you boot your system the SCSI BIOS (residing on the 29160) gets to
run - I have seen weird BIOSes that disalow loading BIOS extensions by
Some motherboards can only handle PCI Bus Mastering on particular slots
so changing slots may have some effect
(although very unlikely on a $$$ server class machine...)

Oh, and if the PCI slot was beyond a PCI bridge, it may
cause some problem if QNX didn't recognize the bridge, IIRC.

Does that card work on Windoze? They should at least support that.
--
kabe

Johannes

Re: 6.2.1 on HP ML350 G3

Post by Johannes » Fri Oct 17, 2003 12:55 am

The same hardware works well with Windows and Linux.

Talking about the bridge, the pci -vvv shows the followings. Do they mean
something to you? Device Id is unknown to QNX. Is that the culprit?

PCI version = 2.10

Class = Bridge (Host/PCI)
Vendor ID = 1166h, Reliance Computer Corp./ServerWorks
Device ID = 14h, Unknown Unknown
PCI index = 0h
Class Codes = 060000h
Revision ID = 32h
Bus number = 0
Device number = 0
Function num = 0
Status Reg = 0h
Command Reg = 0h
Header type = 0h Multi-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 10h un-cacheable
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = NC
Interrupt line = 0

Class = Bridge (Host/PCI)
Vendor ID = 1166h, Reliance Computer Corp./ServerWorks
Device ID = 14h, Unknown Unknown
PCI index = 1h
Class Codes = 060000h
Revision ID = 0h
Bus number = 0
Device number = 0
Function num = 1
Status Reg = 0h
Command Reg = 0h
Header type = 0h Multi-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 10h un-cacheable
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = NC
Interrupt line = 0

Class = Bridge (Host/PCI)
Vendor ID = 1166h, Reliance Computer Corp./ServerWorks
Device ID = 14h, Unknown Unknown
PCI index = 2h
Class Codes = 060000h
Revision ID = 0h
Bus number = 0
Device number = 0
Function num = 2
Status Reg = 0h
Command Reg = 0h
Header type = 0h Multi-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 10h un-cacheable
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = NC
Interrupt line = 0




<kabe@sra-tohoku.co.jp> wrote in message news:bmmmdr$j62$1@inn.qnx.com...
kovalenko@attbi.com sed in <bml9tc$ii7$1@inn.qnx.com>:

Make sure you have the internal SCSI controller disabled in the BIOS
Setup.
The enumerator can get confused or it may have a bug. Then make sure
that
when you boot your system the SCSI BIOS (residing on the 29160) gets to
run - I have seen weird BIOSes that disalow loading BIOS extensions by

Some motherboards can only handle PCI Bus Mastering on particular slots
so changing slots may have some effect
(although very unlikely on a $$$ server class machine...)

Oh, and if the PCI slot was beyond a PCI bridge, it may
cause some problem if QNX didn't recognize the bridge, IIRC.

Does that card work on Windoze? They should at least support that.
--
kabe

Igor Kovalenko

Re: 6.2.1 on HP ML350 G3

Post by Igor Kovalenko » Fri Oct 17, 2003 3:30 am

QNX initializes Host-PCI bridges based on the class, not device id. So it
probably does not matter. OTOH, I would not be too surprized if they don't
initialize it quite right. They have a bug with non-transparent bridges,
could have another one...

I never had a ServerWorks chipset, so no experience with it. You should
pursue this through official support channel, not here. You know the drill,
talk to your sales rep, talk to support@qnx.com or talk to your TAM if you
have one...

-- igor

"Johannes" <Jsukamtoh@infolink.co.id> wrote in message
news:bmndn7$5bs$1@inn.qnx.com...
The same hardware works well with Windows and Linux.

Talking about the bridge, the pci -vvv shows the followings. Do they mean
something to you? Device Id is unknown to QNX. Is that the culprit?

PCI version = 2.10

Class = Bridge (Host/PCI)
Vendor ID = 1166h, Reliance Computer Corp./ServerWorks
Device ID = 14h, Unknown Unknown
PCI index = 0h
Class Codes = 060000h
Revision ID = 32h
Bus number = 0
Device number = 0
Function num = 0
Status Reg = 0h
Command Reg = 0h
Header type = 0h Multi-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 10h un-cacheable
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = NC
Interrupt line = 0

Class = Bridge (Host/PCI)
Vendor ID = 1166h, Reliance Computer Corp./ServerWorks
Device ID = 14h, Unknown Unknown
PCI index = 1h
Class Codes = 060000h
Revision ID = 0h
Bus number = 0
Device number = 0
Function num = 1
Status Reg = 0h
Command Reg = 0h
Header type = 0h Multi-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 10h un-cacheable
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = NC
Interrupt line = 0

Class = Bridge (Host/PCI)
Vendor ID = 1166h, Reliance Computer Corp./ServerWorks
Device ID = 14h, Unknown Unknown
PCI index = 2h
Class Codes = 060000h
Revision ID = 0h
Bus number = 0
Device number = 0
Function num = 2
Status Reg = 0h
Command Reg = 0h
Header type = 0h Multi-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 10h un-cacheable
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = NC
Interrupt line = 0




kabe@sra-tohoku.co.jp> wrote in message news:bmmmdr$j62$1@inn.qnx.com...
kovalenko@attbi.com sed in <bml9tc$ii7$1@inn.qnx.com>:

Make sure you have the internal SCSI controller disabled in the BIOS
Setup.
The enumerator can get confused or it may have a bug. Then make sure
that
when you boot your system the SCSI BIOS (residing on the 29160) gets
to
run - I have seen weird BIOSes that disalow loading BIOS extensions
by

Some motherboards can only handle PCI Bus Mastering on particular slots
so changing slots may have some effect
(although very unlikely on a $$$ server class machine...)

Oh, and if the PCI slot was beyond a PCI bridge, it may
cause some problem if QNX didn't recognize the bridge, IIRC.

Does that card work on Windoze? They should at least support that.
--
kabe

Post Reply

Return to “qdn.public.qnxrtp.installation”