[Eisfair_dev] [e1,e2] LPRng 1.17.2 (Status 'testing') verfügbar

[Thomas Bork]

Am 18.08.2012 14:26, schrieb Marcus Roeckrath:

> Bei meinem Linux-Desktop-PC (2.6) sieht das bei gleichem SCSI-Adapter so
> aus:
>
> mptscsih               36392  0
> mptbase                46432  1 mptscsih
> scsi_mod              130432  7
> usb_storage,sg,st,sr_mod,aic7xxx,mptscsih,sd_mod
>
> mptscsih und mptctl sind in der SCSI-Liste des Kernelpaketes nicht erfasst.

In unserem 2.6.32.59 ist mptbase lediglich ein _Basis_-Treiber (daher 
der Name Bratkartoffel - äh mpt_base_):

referencetest # modinfo mptbase
filename: 
/lib/modules/2.6.32-eisfair-1-SMP/kernel/drivers/message/fusion/mptbase.ko
version:        3.04.12
license:        GPL
description:    Fusion MPT base driver
author:         LSI Corporation
srcversion:     EBAAED85FA70499814502FF
depends:
vermagic:       2.6.32-eisfair-1-SMP SMP mod_unload 486
parm:           mpt_msi_enable_spi: Enable MSI Support for SPI 
controllers (default=0) (int)
parm:           mpt_msi_enable_fc: Enable MSI Support for FC 
controllers (default=0) (int)
parm:           mpt_msi_enable_sas: Enable MSI Support for SAS 
controllers (default=0) (int)
parm:           mpt_channel_mapping: Mapping id's to channels 
(default=0) (int)
parm:           mpt_debug_level: debug level - refer to mptdebug.h 
- (default=0)
parm:           mpt_fwfault_debug:Enable detection of Firmware fault and 
halt Firmware on fault - (default=0)


Im Gegensatz dazu mptsas, bei dem man gepflegt sieht, welche Hardware 
wirklich davon angesteuert wird:

referencetest # modinfo mptsas
filename: 
/lib/modules/2.6.32-eisfair-1-SMP/kernel/drivers/message/fusion/mptsas.ko
version:        3.04.12
license:        GPL
description:    Fusion MPT SAS Host driver
author:         LSI Corporation
srcversion:     668BC49223A8EDDBB919393
alias:          pci:v00001000d00000062sv*sd*bc*sc*i*
alias:          pci:v00001000d00000058sv*sd*bc*sc*i*
alias:          pci:v00001000d00000056sv*sd*bc*sc*i*
alias:          pci:v00001000d00000054sv*sd*bc*sc*i*
alias:          pci:v00001000d00000050sv*sd*bc*sc*i*
depends:        mptscsih,scsi_mod,mptbase,scsi_transport_sas
vermagic:       2.6.32-eisfair-1-SMP SMP mod_unload 486
parm:           mpt_pt_clear: Clear persistency table: enable=1 
(default=MPTSCSIH_PT_CLEAR=0) (int)
parm:           max_lun: max lun, default=16895  (int)


Bleibt das Problem zu lösen, dass der Treiber im 2.4er Kernel einfach 
mptbase hiess. Unklar ist, auf welchen der 3 Treiber (mptspi, mptfc oder 
mptsas) der dann umgesetzt werden muss :(

referencetest # modinfo mptspi
filename: 
/lib/modules/2.6.32-eisfair-1-SMP/kernel/drivers/message/fusion/mptspi.ko
version:        3.04.12
license:        GPL
description:    Fusion MPT SPI Host driver
author:         LSI Corporation
srcversion:     A3FC34AB2316FDF2D4E5496
alias:          pci:v00001000d00000040sv*sd*bc*sc*i*
alias:          pci:v0000117Cd00000030sv*sd*bc*sc*i*
alias:          pci:v00001000d00000030sv*sd*bc*sc*i*
depends:        mptscsih,scsi_mod,mptbase,scsi_transport_spi
vermagic:       2.6.32-eisfair-1-SMP SMP mod_unload 486
parm:           mpt_saf_te: Force enabling SEP Processor: enable=1 
(default=MPTSCSIH_SAF_TE=0) (int)

referencetest # modinfo mptfc
filename: 
/lib/modules/2.6.32-eisfair-1-SMP/kernel/drivers/message/fusion/mptfc.ko
version:        3.04.12
license:        GPL
description:    Fusion MPT FC Host driver
author:         LSI Corporation
srcversion:     92E350C096B75A9714B8B0E
alias:          pci:v00001657d00000646sv*sd*bc*sc*i*
alias:          pci:v00001000d00000646sv*sd*bc*sc*i*
alias:          pci:v00001000d00000640sv*sd*bc*sc*i*
alias:          pci:v00001000d00000642sv*sd*bc*sc*i*
alias:          pci:v00001000d00000626sv*sd*bc*sc*i*
alias:          pci:v00001000d00000628sv*sd*bc*sc*i*
alias:          pci:v00001000d00000622sv*sd*bc*sc*i*
alias:          pci:v00001000d00000624sv*sd*bc*sc*i*
alias:          pci:v00001000d00000621sv*sd*bc*sc*i*
depends:        mptscsih,scsi_transport_fc,scsi_mod,mptbase
vermagic:       2.6.32-eisfair-1-SMP SMP mod_unload 486
parm:           mptfc_dev_loss_tmo: Initial time the driver programs the 
  transport to wait for an rport to  return following a device loss 
event.  Default=60. (int)
parm:           max_lun: max lun, default=16895  (int)

-- 
der tom
[eisfair-team]