/dev/fc Qlogic 2300 card problem
807559Dec 1 2005 — edited Mar 9 2006I have just installed a Qlogic PCI 2300 card in two sun machines, one is a V480 and one is a V440. The V480 is fine and the card can be seen from the /dev/fc directory, the other box is where the problem is, there is no /dev/fc that has been created for the card plus on the install i get the following error
Installing QLogic QLA2300 driver as <QLA2300>
## Installing part 1 of 1.
/kernel/drv/q3ip_v9
/kernel/drv/qla2300_v9
[ verifying class <none> ]
## Executing postinstall script.
("pci1077,9") already in use as a driver or alias.
Installation of <QLA2300> was successful.
The thing is if i type modinfo|grep FC i get the following
27 123df4e 548a0 239 1 qla2300 (QLogic FC Driver v4.13.01)
61 13f08d4 6888 - 1 fctl (Sun FC Transport Library v1.14)
201 781c0000 c628 150 1 fcp (Sun FCP Pseudo Driver v1.25)
and when i run prtconf -v i get the following
fibre-channel, instance #1
System software properties:
name='hba0-max-frame-length' type=int items=1
value=00000800
name='hba0-execution-throttle' type=int items=1
value=00000010
name='hba0-login-retry-count' type=int items=1
value=00000008
name='hba0-enable-adapter-hard-loop-ID' type=int items=1
value=00000000
name='hba0-adapter-hard-loop-ID' type=int items=1
value=00000000
name='hba0-enable-LIP-reset' type=int items=1
value=00000000
name='hba0-enable-LIP-full-login' type=int items=1
value=00000001
name='hba0-enable-target-reset' type=int items=1
value=00000000
name='hba0-reset-delay' type=int items=1
value=00000005
name='hba0-port-down-retry-count' type=int items=1
value=00000008
name='hba0-maximum-luns-per-target' type=int items=1
value=00000008
name='hba0-connection-options' type=int items=1
value=00000002
name='hba0-fc-tape' type=int items=1
value=00000001
name='hba0-fc-data-rate' type=int items=1
value=00000002
name='hba0-pci-latency-timer' type=int items=1
value=00000040
name='hba0-pci-x-max-memory-read-byte-count' type=int items=1
value=00000000
name='hba0-link-down-error' type=int items=1
value=00000001
name='hba0-link-down-timeout' type=int items=1
value=0000003c
name='hba0-persistent-binding-configuration' type=int items=1
value=00000000
name='hba0-fast-error-reporting' type=int items=1
value=00000000
name='hba0-extended-logging' type=int items=1
value=00000000
name='hba0-queue-full-retry-count' type=int items=1
value=00000010
name='hba0-queue-full-retry-delay' type=int items=1
value=00000002
name='hba0-security-protocols' type=int items=1
value=00000000
Driver properties:
name='pm-components' type=string items=3 dev=none
value='NAME=qla2300(1)' + '0=Device D3 State' + '3=Device D0 State'
name='scsi-selection-timeout' type=int items=1 dev=(239,0)
value=000000fa
name='scsi-options' type=int items=1 dev=(239,0)
value=00107ff8
name='scsi-watchdog-tick' type=int items=1 dev=(239,0)
value=0000000a
name='scsi-tag-age-limit' type=int items=1 dev=(239,0)
value=00000002
name='scsi-reset-delay' type=int items=1 dev=(239,0)
value=00000bb8
sd, instance #46 (driver not attached)
System properties:
name='lun' type=int items=1
value=00000000
name='target' type=int items=1
value=00000000
name='class_prop' type=string items=1
value='atapi'
name='class' type=string items=1
value='scsi'
sd, instance #47
System properties:
name='lun' type=int items=1
value=00000000
name='target' type=int items=1
value=00000001
name='class_prop' type=string items=1
value='atapi'
name='class' type=string items=1
value='scsi'
Driver properties:
name='pm-hardware-state' type=string items=1 dev=none
value='needs-suspend-resume'
name='ddi-failfast-supported' type=boolean dev=none
name='ddi-kernel-ioctl' type=boolean dev=none
Hardware properties:
name='devid' type=string items=1
value='id1,sd@w4849544143484920373330313033353630303030'
name='inquiry-revision-id' type=string items=1
value='0000'
name='inquiry-product-id' type=string items=1
value='DF600F'
name='inquiry-vendor-id' type=string items=1
value='HITACHI'
name='inquiry-device-type' type=int items=1
value=00000000
sd, instance #48 (driver not attached)
System properties:
name='lun' type=int items=1
value=00000000
name='target' type=int items=1
value=00000002
name='class_prop' type=string items=1
value='atapi'
name='class' type=string items=1
value='scsi'
sd, instance #49 (driver not attached)
System properties:
name='lun' type=int items=1
value=00000000
name='target' type=int items=1
value=00000003
name='class_prop' type=string items=1
value='atapi'
name='class' type=string items=1
value='scsi'
sd, instance #50 (driver not attached)
System properties:
name='lun' type=int items=1
value=00000000
name='target' type=int items=1
value=00000004
name='class' type=string items=1
value='scsi'
sd, instance #51 (driver not attached)
System properties:
name='lun' type=int items=1
value=00000000
name='target' type=int items=1
value=00000005
name='class' type=string items=1
value='scsi'
sd, instance #52 (driver not attached)
System properties:
name='lun' type=int items=1
value=00000000
name='target' type=int items=1
value=00000006
name='class' type=string items=1
value='scsi'
sd, instance #53 (driver not attached)
System properties:
name='lun' type=int items=1
value=00000000
name='target' type=int items=1
value=00000008
name='class' type=string items=1
value='scsi'
sd, instance #54 (driver not attached)
System properties:
name='lun' type=int items=1
value=00000000
name='target' type=int items=1
value=00000009
name='class' type=string items=1
value='scsi'
sd, instance #55 (driver not attached)
System properties:
name='lun' type=int items=1
value=00000000
name='target' type=int items=1
value=0000000a
name='class' type=string items=1
value='scsi'
sd, instance #56 (driver not attached)
I am at the stage of pulling my hair out :) any ideas why no /dev/fc is being created ?
Cheers,
Mike