Hi,
I've bought two of these AOC-SAS2LP-MV8 hba cards. It connects 16 hot swap bays. When I add a drive in one of the bays i can't see the drive with "parted -l". Has ClearOS no drivers for these hba cards? When i check supported operating system RHEL is supported. What should i do next? Is it possible to install these drivers?
AOC-SAS2LP-MV8
I've bought two of these AOC-SAS2LP-MV8 hba cards. It connects 16 hot swap bays. When I add a drive in one of the bays i can't see the drive with "parted -l". Has ClearOS no drivers for these hba cards? When i check supported operating system RHEL is supported. What should i do next? Is it possible to install these drivers?
AOC-SAS2LP-MV8
In Hardware
Share this post:
Responses (21)
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
Hi Tim,
I know that kmod packages *should* work across kernels but Marcel can't install my package and I can. If you do an "rpm -qR" it does not show any package dependencies, just a list similar to Marcel's failed dependency list which seems to point to the kernel hence trying to either upgrade the kernel or compile at his kernel level.
On your system you do have multiple kernel/kernel-devel versions and it stays that way once you heve kernel-devel installed, but you will find that the older kernel-devel packages are not in the repos and so are uninstallable. This means the first time you want kernel-devel you must reboot to the latest kernel to have them match *unless* there is a new kernel in updates-testing. In that case you will only find the kernel-devel package for the kernel which is in updates-testing. This is what I mean by "less than ideal".
kernel-headers (and possibly firmware) upgrade each time a new kernel is installed so the earlier packages get removed and again are uninstallable. It also suffers the updates-testing issue.
I still need to remember if it is the headers or devel package I need but I never seem to retain the info in my memory. You've mentioned it often enough. I think there is a lot of overlap between them (but I need to test this statement). If I can just use devel that is great because, as you see, old versions do not get deleted on a kernel update. -
Accepted Answer
Hi Nick no that's the point of kmod RPMs, they are ABI compatible (or should be!) so in theory you can compile against any 2.6.32-x version and install it on a system running a similarly ABI compatible running kernel
It's more sane to keep your running kernel and kernel-devel in step
I know there is a timing issue with the early arrival of kernel-devel into the repo's but TBH I leave auto-upgrades off and manage it that way via yum (i.e. keep the matching kernel-devel version for my running kernel)
On my system here I have matching multiple kernel/kernel-devel versions...?
[root@leonardo ~]# rpm -qa | grep kernel | sort
dracut-kernel-004-336.el6_5.2.noarch
kernel-2.6.32-431.17.1.v6.x86_64
kernel-2.6.32-431.20.3.v6.x86_64
kernel-2.6.32-431.23.3.v6.x86_64
kernel-devel-2.6.32-431.17.1.v6.x86_64
kernel-devel-2.6.32-431.20.3.v6.x86_64
kernel-devel-2.6.32-431.23.3.v6.x86_64
kernel-firmware-2.6.32-431.23.3.v6.noarch
kernel-headers-2.6.32-431.23.3.v6.x86_64
kernel-ml-3.13.2-1.clearos.x86_64
-
Accepted Answer
I think the issue may be a bit deeper and there is a continuing repo issue. I think, Marcel, you are running ClearOS Pro? Its kernel updates run behind ClearOS Community, but as soon as a new kernel-devel comes along it gets pushed into the repo's. At that point you can no longer get the header/devel packages relating to your running kernel which I think is [strike]pants[/strike] less than ideal for a high availability system. It also happens on the Community edition but with a smaller time lag. In the Community edition you can generakky get round it by installing the new kernel from clearos-test when this happens. Then you have to reboot (did anyone mention linux as a high-availability system?). This is why I block automatic kernel updates and control them manually.
Tim's suggestion will probably work for the compilation but then the installation may fail again. -
Accepted Answer
You only need kernel-devel to compile kmod RPMs, kernel-headers are rarely required and do not have to be the latest version.
In your case you have version kernel-devel-2.6.32-431.23.3.v6.x86_64, so specify that on the rpmbuild line. The reason you have an error is because you are specifying 'uname -r' which is actually a different version (i.e the kernel you are running is slightly older)
It's no problem you can either reboot... or specify it directly
rpmbuild --rebuild --define "kversion 2.6.32-431.23.3.v6.x86_64" --define 'dist .mydist' --define 'packager myname' mvsas-kmod-0.8.16-1.el6.elrepo.src.rpm
-
Accepted Answer
what is going on...
I have the latest kernel:
Package kernel-2.6.32-358.23.2.v6.x86_64 already installed and latest version
I have the kernel-headers installed:
Package kernel-headers-2.6.32-358.23.2.v6.x86_64 already installed and latest version
and the latest kernel-devel:
Package kernel-devel-2.6.32-431.23.3.v6.x86_64 already installed and latest version
I don't get it.., why can you install it and I'm not...
Edit: and this system is installed this evening. -
Accepted Answer
I've no idea what causes those errors:
You could try updating to the latest kernel and, perhaps, installing kernel-headers and/or kernel-devel and see what happens.[root@server x86_64]# rpm -ivh kmod-mvsas-0.8.16-1.clearos6.njh.x86_64.rpm
Preparing... ########################################### [100%]
1:kmod-mvsas ########################################### [100%]
Working. This may take some time ...
Done. -
Accepted Answer
When installing your rpm I have this error:
[root@voyager tmp]# rpm -ivh kmod-mvsas-0.8.16-1.clearos6.njh.x86_64.rpm
error: Failed dependencies:
kernel(sas_alloc_slow_task) = 0x081280cb is needed by kmod-mvsas-0.8.16-1.clearos6.njh.x86_64
kernel(sas_domain_attach_transport) = 0xb287d015 is needed by kmod-mvsas-0.8.16-1.clearos6.njh.x86_64
kernel(sas_drain_work) = 0x9b608720 is needed by kmod-mvsas-0.8.16-1.clearos6.njh.x86_64
kernel(sas_free_task) = 0x0f87c3e0 is needed by kmod-mvsas-0.8.16-1.clearos6.njh.x86_64
kernel(sas_get_local_phy) = 0xa25d23d5 is needed by kmod-mvsas-0.8.16-1.clearos6.njh.x86_64
kernel(sas_phy_reset) = 0xc012e9a8 is needed by kmod-mvsas-0.8.16-1.clearos6.njh.x86_64
kernel(sas_register_ha) = 0x37247c1a is needed by kmod-mvsas-0.8.16-1.clearos6.njh.x86_64
kernel(sas_ssp_task_response) = 0x827df083 is needed by kmod-mvsas-0.8.16-1.clearos6.njh.x86_64
kernel(sas_unregister_ha) = 0x219825f8 is needed by kmod-mvsas-0.8.16-1.clearos6.njh.x86_64
This is caused by not having the latest kernel devel / headers? If so how do i install this? Is it available in the ClearOS repos? -
Accepted Answer
-
Accepted Answer
I'm not sure what you mean by wrong key. It looks like you don't have the kernel-headers (or perhaps kernel-devel) installed. Because of the way kernel update work with the repos (badly), you'll need to update your kernel to the latest (including rebooting) before you can install the latest headers. Alternatively I quickly built it after I posted yesterday and it is now here here if you want it. -
Accepted Answer
I checked with "modinfo mvsas" and the driver is loaded. I have the same output as you. However ClearOS doesn't see the card.
Edit: I'm not sure which driver to use
I tried to build from source but i have a issue with the key:
[marcel@voyager tmp]$ rpmbuild --rebuild --define "kversion `uname -r`" --define 'packager Marcel van Leeuwen' mvsas-kmod-0.8.16-1.el6.elrepo.src.rpm
Installing mvsas-kmod-0.8.16-1.el6.elrepo.src.rpm
warning: InstallSourcePackage at: psm.c:244: Header V4 DSA/SHA1 Signature, key ID baadae52: NOKEY
warning: user phil does not exist - using root
warning: group phil does not exist - using root
warning: user phil does not exist - using root
warning: group phil does not exist - using root
warning: user phil does not exist - using root
warning: group phil does not exist - using root
warning: user phil does not exist - using root
warning: group phil does not exist - using root
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.TJNmTF
+ umask 022
+ cd /home/marcel/rpmbuild/BUILD
+ LANG=C
+ export LANG
+ unset DISPLAY
+ cd /home/marcel/rpmbuild/BUILD
+ rm -rf mvsas-0.8.16
+ /usr/bin/bzip2 -dc /home/marcel/rpmbuild/SOURCES/mvsas-0.8.16.tar.bz2
+ /bin/tar -xf -
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd mvsas-0.8.16
+ /bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ echo 'override mvsas * weak-updates/mvsas'
+ exit 0
Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.IuYYSt
+ umask 022
+ cd /home/marcel/rpmbuild/BUILD
+ cd mvsas-0.8.16
+ LANG=C
+ export LANG
+ unset DISPLAY
+ KSRC=/usr/src/kernels/2.6.32-358.23.2.v6.x86_64
+ /usr/bin/make -C /usr/src/kernels/2.6.32-358.23.2.v6.x86_64 -j8 modules M=/home/marcel/rpmbuild/BUILD/mvsas-0.8.16
make: *** /usr/src/kernels/2.6.32-358.23.2.v6.x86_64: No such file or directory. Stop.
error: Bad exit status from /var/tmp/rpm-tmp.IuYYSt (%build)
RPM build errors:
InstallSourcePackage at: psm.c:244: Header V4 DSA/SHA1 Signature, key ID baadae52: NOKEY
user phil does not exist - using root
group phil does not exist - using root
user phil does not exist - using root
group phil does not exist - using root
user phil does not exist - using root
group phil does not exist - using root
user phil does not exist - using root
group phil does not exist - using root
Bad exit status from /var/tmp/rpm-tmp.IuYYSt (%build)
Is it possible to override the key? -
Accepted Answer
mvsas-kmod or any of the other Elrepo mirrors. Note that when compiling kmod NIC drivers I use a command like:
It would not compile without defining the "kversion". This driver could be the same.rpmbuild --rebuild --define "kversion `uname -r`" --define 'packager Nick Howitt' igb-kmod-5.2.5-1.el6.elrepo.src.rpm
HTH,
Nick
[edit]
FWIW the module mvsas.ko is included in the kernel:
Any reason for needing the kmod one? Is it compatible with more devices?[root@server ~]# modinfo mvsas
filename: /lib/modules/2.6.32-431.23.3.v6.x86_64/kernel/drivers/scsi/mvsas/mvsas.ko
license: GPL
version: 0.8.2
description: Marvell 88SE6440 SAS/SATA controller driver
author: Jeff Garzik <jgarzik@pobox.com>
srcversion: F63DF838ABC694D6903E4A6
alias: pci:v00009005d00000450sv*sd*bc*sc*i*
alias: pci:v000017D3d00001320sv*sd*bc*sc*i*
alias: pci:v000017D3d00001300sv*sd*bc*sc*i*
alias: pci:v000011ABd00009180sv*sd*bc*sc*i*
alias: pci:v000011ABd00009480sv*sd*bc*sc*i*
alias: pci:v000011ABd00006485sv*sd*bc*sc*i*
alias: pci:v000011ABd00006440sv*sd*bc*sc*i*
alias: pci:v000011ABd00006440sv*sd00006480bc*sc*i*
alias: pci:v000011ABd00006340sv*sd*bc*sc*i*
alias: pci:v000011ABd00006320sv*sd*bc*sc*i*
depends: libsas,scsi_transport_sas
vermagic: 2.6.32-431.23.3.v6.x86_64 SMP mod_unload modversions
[/edit] -
Accepted Answer
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »