Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
Not eligible to see or edit group visibility for this bug.
View Bug Activity | Format For Printing | XML | Clone This Bug
First try to install Dell openmanage on Gentoo Reproducible: Always Steps to Reproduce: 1. 2. 3. I would like to thank Pauli Borodulin <pauli.borodulin@uta.fi> for installing omsa on Debian. It is a good start.
Created an attachment (id=73353) [details] ebuild to install omsa
Created an attachment (id=73354) [details] env settings Put this file in files/4.5
Created an attachment (id=73355) [details] Script to build the necessary drivers Put this file in files/4.5
Created an attachment (id=73356) [details] conf.d file for startup script Put this file in files/4.5
Created an attachment (id=73357) [details] patch for compiling driver on kernel 2.6.14
Created an attachment (id=73358) [details] script for starting the daemons
Created an attachment (id=73359) [details] script for loading drivers at startup
Created an attachment (id=73360) [details] Settings file
Created an attachment (id=73361) [details] patch to get the drivers compiled on gentoo
I have tested this ebuild on a dell PE 2850 and PE 1850 and it works there. It gives some warnings when installing the package, but they can be ignored. I'm pretty sure there are still some bugs in it, but it's a start. # emerge info Portage 2.0.51.22-r3 (default-linux/x86/2005.0, gcc-3.3.6, glibc-2.3.5-r2, 2.6.14-gentoo-r2 i686) ================================================================= System uname: 2.6.14-gentoo-r2 i686 Intel(R) Xeon(TM) CPU 3.60GHz Gentoo Base System version 1.6.13 dev-lang/python: 2.3.5, 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.20 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=pentium4 -mmmx -msse -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share /config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=pentium4 -mmmx -msse -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="ftp://pandemonium.tiscali.de/pub/gentoo/ ftp://ftp.snt.utwente.nl/pub/os/linux/gentoo http://linux.rz.ruhr-uni- bochum.de/download/gentoo-mirror/" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/root/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 extensions mmx ncurses nptl pam ssl userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS I have tested it only on a 32-bit server because I don't have a 64-bit at my disposal.
Don't forget to run emerge --config =omsa-4.5 after the installation, otherwise it won't run. You can build the drivers with: #/opt/dell/srvadmin/hapi/bin/builddriver.sh /usr/src/linux
(From update of attachment 73357 [details]) Put this file in files/4.5
The ebuild unpack and compile process work fine, however during ebuild install, the ebuild is having problems making Symbolic Links. >>> Install omsa-4.5 into /var/tmp/portage/omsa-4.5/image/ category app-admin ln: creating symbolic link `/var/tmp/portage/omsa-4.5/image//usr/bin/omconfig' to `/opt/dell/srvadmin/oma/bin/omconfig.sh': No such file or directory ln: creating symbolic link `/var/tmp/portage/omsa-4.5/image//usr/bin/omreport' to `/opt/dell/srvadmin/oma/bin/omreport.sh': No such file or directory ln: creating symbolic link `/var/tmp/portage/omsa-4.5/image//usr/bin/omhelp' to `/opt/dell/srvadmin/oma/bin/omhelp.sh': No such file or directory ln: creating symbolic link `/var/tmp/portage/omsa-4.5/image//usr/bin/omexec' to `/opt/dell/srvadmin/oma/bin/omexec.sh': No such file or directory ln: creating symbolic link `/var/tmp/portage/omsa-4.5/image//usr/bin/omdiag' to `/opt/dell/srvadmin/oldiags/bin/omdiag.sh': No such file or directory install: cannot stat `dcddks-2.6.14.patch': No such file or directory man: prepallstrip: strip: i686-pc-linux-gnu-strip --strip-unneeded strip: i686-pc-linux-gnu-strip --strip-unneeded opt/dell/srvadmin/sm/libdcsif32.so.1.2.0.787 opt/dell/srvadmin/sm/libval.so.1.2.0.787 opt/dell/srvadmin/sm/dellvl/libenclvil.so.1.2.0.787 opt/dell/srvadmin/sm/dellvl/libnrsvil.so.1.2.0.787 opt/dell/srvadmin/sm/dellvl/libafavil.so.1.2.0.787 opt/dell/srvadmin/sm/dellvl/libafavil.so.1.2.0.787 will contain runtime text relocations Text relocations require a lot of extra work to be preformed by the dynamic linker which will cause serious performance impact on IA-32 and might not function properly on other architectures hppa for example. If you are a programmer please take a closer look at this package and
excellent job creating this ebuild. Will you be maintaining it? Any desire to get it into the real portage tree? As long as the license is listed properly and users are required to manually download the dell omsa tarballs, I dont see a problem. If you need any help, let me know. I am going to experiment with this ebuild on a few dozen servers next week.
I would like to begin testing this ebuild for both 32/64bit systems It's not obvious what the file names for the attachments are to be when I save them. I am using Firefox 1.5 to view this bug, it doesn't suggest a name for the files other than attachment.cgi The file contents don't seem to have the respective filenames either.
Ok, I realized that if I click on Edit next to each attachment, it will show me the filename. So I've reassembled it all in /usr/local/portage/app-admin/omsa on a 32bit and 64bit machine Installed, and can start /etc/init.d/dellomsa-drivers start /etc/init.d/dellomsa-daemons start on the 32bit machine can't build drivers on the 64bit machine
I am coming up short on downloading the compat-libstdc++ version listed here. Anyone?
Nevermind, I was able to use Firefox to fetch it, but wget failed.
> > can't build drivers on the 64bit machine > The next version of omsa has drivers included in the standard linux kernel and should work for 64 bit. I think it has already been released somewhat. I'd like to get an ebuild for it. The older versions were never really supported for anything but 32 bit.
First of all, thanks for all the effort here; we had a hard drive go down in our mail server, and omreport was able to identify the failed drive. omconfig was able to rebuild it, but it still shows as 'degraded'. Here's where I hit a snag, omdiag isn't working. It spits back this error: cd /opt/dell/srvadmin/oldiags/bin ./omdiag storage -? omdiag Executes component diagnostics. The available command(s) are: Command Description Exception in thread "DiagnosticEngine" java.lang.UnsatisfiedLinkError: initialize at com.dell.diagnostic.obj.diagcontroller.DiagnosticController.initialize(Native Method) at com.dell.diagnostic.vendor.diagcontroller.DiagControllerDiagnosticVendor.<init>(DiagControllerDiagnosticVendor.java:129) at com.dell.diagnostic.engine.DiagnosticEngine.run(DiagnosticEngine.java:290) at java.lang.Thread.run(Unknown Source) Any ideas?
Tried to follow this track and came across the following... 1 - omsa-4.5-hapi.patch needed to be in files/4.5 as well. 2 - to get around Manifest and Digest problems - add the flag
Tried to follow this track and came across the following... 1 - omsa-4.5-hapi.patch needed to be in files/4.5 as well. 2 - to get around Manifest and Digest problems - add the flag ¨digest¨ to your FEATURES flag in /etc/make.conf. After the install - remove it. (Security) 3 - There is a bunch of "chown"-ing to do, whilst installing - change your "portage" user in /etc/passwd to be user/group 0:0 - change back afterwards. (ie - run portage as root) This allows everything to be installed without any errors - except the errors the ebuild tells you to ignore :-) This may not be the correct way to install - but it worked for me.
(In reply to comment #21) Compiling Driver Changed the format of /opt/dell/srvadmin/hapi/bin/builddriver.sh from DOS to UNIXC using "crlf" Recompiled kernel to enable... Processor type and features -> [*] Use register arguments (EXPERIMENTAL) (CONFIG_REGPARM=y) To build the Kernel modules... emerge fixdos crlf /opt/dell/srvadmin/hapi/bin/builddriver.sh sh /opt/dell/srvadmin/hapi/bin/builddriver.sh /usr/src/linux (rude comment - who put dos type files in???) Is there a HowTo on using omsa tools anywhere? I de-flowered my 1850 with Gentoo.
Sometime back, I found this (documentation): http://support.dell.com/support/edocs/software/svradmin/2.3/ Haven't been able to get the web server to start, and still haven't found a way to troubleshoot the error I get when trying to run omdiag. But the rest of the tools seem to work.
heloo... how to i install the struture of files and directorys this ebuild?? Marcelo
Just wanted to mention that version 5.0 has been released: http://linux.dell.com/blog/2006/06/15/#1545 It says all kernel drivers are no open source among other things. Not sure what needs to be done to adapt an ebuild to work with the newer version.
It's a shame there is no way to edit your post, and of course that I didn't reread my last one well enough. I meant "now open source" and not "no open source".
/usr/local/portage/app-admin/omsa/: total 28 drwxr-xr-x 3 root root 128 Aug 24 14:07 . drwxr-xr-x 3 root root 72 Aug 24 12:46 .. -rw-r--r-- 1 root root 3815 Aug 24 14:09 Manifest drwxr-xr-x 3 root root 104 Aug 24 14:07 files -rw-r--r-- 1 root root 24050 Aug 24 12:44 omsa-4.5.ebuild /usr/local/portage/app-admin/omsa/files: total 4 drwxr-xr-x 3 root root 104 Aug 24 14:07 . drwxr-xr-x 3 root root 128 Aug 24 14:07 .. drwxr-xr-x 2 root root 296 Aug 24 14:11 4.5 -rw-r--r-- 1 root root 632 Aug 24 14:07 digest-omsa-4.5 /usr/local/portage/app-admin/omsa/files/4.5: total 36 drwxr-xr-x 2 root root 296 Aug 24 14:11 . drwxr-xr-x 3 root root 104 Aug 24 14:07 .. -rw-r--r-- 1 root root 241 Aug 24 13:12 80openmanage -rw-r--r-- 1 root root 3870 Aug 24 14:11 builddriver.sh -rw-r--r-- 1 root root 179 Aug 24 13:14 confd-dellomsa-daemons -rw-r--r-- 1 root root 576 Aug 24 14:09 dcddks-2.6.14.patch -rw-r--r-- 1 root root 3782 Aug 24 14:07 dellomsa-daemons -rw-r--r-- 1 root root 4407 Aug 24 14:06 dellomsa-drivers -rw-r--r-- 1 root root 5515 Aug 24 13:58 omsa-4.5-hapi.patch
hi! I have a problem with starting omsa-driver on on power ege 1400sc. the instaltion from ebuild was succes, but when I try to start it become: # /etc/init.d/dellomsa-drivers start * driver modules unavailable for 2.6.14 what is wrong? missing module or something else? thank U!
Hi there! I'm watching this bug for while. Are there any hot news about OMSA and gentoo implementation? What about OMSA Version 5.0?
> * driver modules unavailable for 2.6.14 Any resolution on this? I just need to check if my RAID array is still redundant, but `omreport stroage controller` says "No Controllers Found" I controllers.(Dell 6950).
If you're going to use this, you need to modify it to reflect new packages and URL paths. Here's what mine looks like: #LIBSTDC="296-2.96-132.fc4" LIBSTDC="296-2.96-140" EXEVERSION="5.3.0.4531" SRC_PACK="OMI-SrvAdmin-Dell-Web-LX-${SRC_BASE}.tar.gz" SRC_PACK_LIBSTDC="compat-libstdc++-${LIBSTDC}.i386.rpm" SRC_URI="ftp://ftp.dell.com/sysman/${SRC_PACK} ftp://rpmfind.net/linux/0/fedora/development/i386/os/Packages/${SRC_PACK_LIBSTDC}" #SRC_URI="ftp://ftp.dell.com/sysman/${SRC_PACK} ftp://rpmfind.net/linux/0/fedora/core/4/i386/os/Fedora/RPMS/${SRC_PACK_LIBSTDC}"
The 2nd part of the source URI has changed again and is now ftp://fr2.rpmfind.net/linux/fedora/development/i386/os/Packages/ so the whole line becomes: SRC_URI="ftp://ftp.dell.com/sysman/${SRC_PACK} ftp://fr2.rpmfind.net/linux/fedora/development/i386/os/Packages/${SRC_PACK_LIBSTDC}"
