trying to build the OMSA kernel modules
Tomas Pospisek's Mailing Lists
tpo2 at sourcepole.ch
Tue Jul 5 15:10:11 CDT 2005
On Tue, 5 Jul 2005, Pauli Borodulin wrote:
>>> tman_dell at trejan.com wrote:
>>>> The modules are built by Dell and you only get the module binary.
>
>> On Tue, 5 Jul 2005, Pauli Borodulin wrote:
>>> This is not true, at least not for OMSA 4.3 and 4.4. Part of the driver
>>> modules are distributed as source code, part in precompiled object files.
>>> [...]
>
> Tomas Pospisek's Mailing Lists wrote:
>> It looks like you are definitively making my day.... have you had any
>> success with 2.4 kernels? I seem to be unable to boot into 2.6 so far.
>
> I have not tried it with 2.4 kernels because we only run the newer 2.6 serie.
> Linux 2.6 has been working on our PE1850/2850 servers without problems for a
> half year now. It also has more decent drivers than the old 2.4. I'm not
> really that interested in figuring out how to get the OMSA modules compile
> with 2.4 kernel, but I can look into it if there's really no way for you to
> run 2.6.
No, that's fine, grepping through .config made me find the culprit.
2.6.12.2 running here ;-)!
> What kind of problems did you have with Linux 2.6? All you need is to install
> Debian package "module-init-tools" and then compile & install new 2.6 kernel.
> I can provide you a generic PowerEdge 1850 kernel config for 2.6.12.2. You
> can then add the extra drivers/features you need and just compile and
> install. Or, I can compile 2.6.12.2 kernel for you using our generic PE1850
> kernel config and also add the OMSA drivers to it -- I can then create a tar
> file of it and you just extract the file in the root directory and add entry
> to GRUB's menu.lst. You choose :-)
I'd be happy to get the OMSA drivers in whatever way you please - I'm
getting this when compiling them through DKS (hell, those scripts are
O-V-E-R-K-I-L-L):
# ./instsvcdrv start
Starting Systems Management Device Drivers:
Building dcdbas device driver using DKS:
make: Entering directory `/usr/src/linux-2.6.12.2'
CC [M] /opt/dell/srvadmin/hapi/drivers/x86/dks/build/dcdbas/dcddks.o
/opt/dell/srvadmin/hapi/drivers/x86/dks/build/dcdbas/dcddks.c: In function `esm_verify_area_write':
/opt/dell/srvadmin/hapi/drivers/x86/dks/build/dcdbas/dcddks.c:575: warning: `verify_area' is deprecated (declared at include/asm/uaccess.h:105)
/opt/dell/srvadmin/hapi/drivers/x86/dks/build/dcdbas/dcddks.c: In function `esm_verify_area':
/opt/dell/srvadmin/hapi/drivers/x86/dks/build/dcdbas/dcddks.c:592: warning: `verify_area' is deprecated (declared at include/asm/uaccess.h:105)
LD [M] /opt/dell/srvadmin/hapi/drivers/x86/dks/build/dcdbas/dcdbas.o
Building modules, stage 2.
MODPOST
*** Warning: "dcd_init"
[/opt/dell/srvadmin/hapi/drivers/x86/dks/build/dcdbas/dcdbas.ko] undefined!
*** Warning: "dcd_get_dev_name"
[/opt/dell/srvadmin/hapi/drivers/x86/dks/build/dcdbas/dcdbas.ko] undefined!
*** Warning: "dcd_dbg_level"
[/opt/dell/srvadmin/hapi/drivers/x86/dks/build/dcdbas/dcdbas.ko] undefined!
*** Warning: "esm_printk3"
[/opt/dell/srvadmin/hapi/drivers/x86/dks/build/dcdbas/dcdbas.ko] undefined!
*** Warning: "dcd_device_ioctl"
[/opt/dell/srvadmin/hapi/drivers/x86/dks/build/dcdbas/dcdbas.ko] undefined!
*** Warning: "dcd_do_shutdown_action"
[/opt/dell/srvadmin/hapi/drivers/x86/dks/build/dcdbas/dcdbas.ko] undefined!
*** Warning: "dcd_timer_process_data"
[/opt/dell/srvadmin/hapi/drivers/x86/dks/build/dcdbas/dcdbas.ko] undefined!
*** Warning: "dcd_unload"
[/opt/dell/srvadmin/hapi/drivers/x86/dks/build/dcdbas/dcdbas.ko] undefined!
*** Warning: "esm_printk4"
[/opt/dell/srvadmin/hapi/drivers/x86/dks/build/dcdbas/dcdbas.ko] undefined!
CC
/opt/dell/srvadmin/hapi/drivers/x86/dks/build/dcdbas/dcdbas.mod.o
LD [M] /opt/dell/srvadmin/hapi/drivers/x86/dks/build/dcdbas/dcdbas.ko
make: Leaving directory `/usr/src/linux-2.6.12.2'
rails-ha1:/opt/dell/srvadmin/hapi/bin# modprobe dcdbas
FATAL: Error inserting dcdbas
(/lib/modules/2.6.12.2-sourcepole14/misc/dcdbas.ko): Invalid module format
> PS. Did you read my email about my "Dell OMSA 4.4 on Debian Sarge"
> documentation? I really recommend using my init.d script for loading the
> kernel modules instead that instsvcdrv script.
Yes, I am right now. I have to figure out how to clean up my system here
from my own trials. I'll give you feedback ASAP.
Thanks heaps,
*t
--
-----------------------------------------------------------
Tomas Pospisek
http://sourcepole.com - Linux & Open Source Solutions
-----------------------------------------------------------
More information about the Linux-PowerEdge
mailing list