dell_rbu gcc version conflict

Tom Haddon tom at greenleaftech.net
Fri Sep 8 09:40:12 CDT 2006


Hi Davis,

Thanks! Can you explain how to rebuild dell_rbu? I'd rather not force
the dell_rbu module into the kernel if it's giving me these error
messages (that's what insmod -f is doing, correct), but I'm not sure
what's involved in rebuilding dell_rbu.

gcc -v gives:

Using built-in specs.
Target: i386-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --enable-shared --enable-threads=posix
--enable-checking=release --with-system-zlib --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-libgcj-multifile
--enable-languages=c,c++,objc,obj-c++,java,fortran,ada
--enable-java-awt=gtk --disable-dssi
--with-java-home=/usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/jre
--with-cpu=generic --host=i386-redhat-linux
Thread model: posix
gcc version 4.1.0 20060512 (Red Hat 4.1.0-17)

Thanks, Tom

On Fri, 2006-09-08 at 08:57 -0500, Davis_Phillips at Dell.com wrote:
> I have seen this error a bunch recently. Check the output of gcc -v. You
> can usually resolve the issue by rebuilding dell_rbu with the GCC
> version that the krnel was built against. Relink gcc essentially.
> Alternatively, a insmod -f on the dell_rbu module should work as well. 
> 
> -----Original Message-----
> From: linux-poweredge-bounces at dell.com
> [mailto:linux-poweredge-bounces at dell.com] On Behalf Of Tom Haddon
> Sent: Friday, September 08, 2006 3:49 AM
> To: linux-poweredge-Lists
> Subject: dell_rbu gcc version conflict
> 
> Hi Folks,
> 
> I'm trying to install OMI-SrvAdmin-Dell-Web-LX-50_A00.tar.gz on an FC3
> box running 2.6.12-1.1381_FC3smp. When I try to startup the services, I
> get the following:
> 
> ./srvadmin-services.sh start
> Starting mptctl:
> Waiting for mptctl driver registration to complete:
>                                                            [  OK  ]
> 
> Starting Systems Management Device Drivers:
> Building dell_rbu using DKS:                               [  OK  ]
> Starting dell_rbu:                                         [FAILED]
> dell_rbu device driver load failed for kernel 2.6.12-1.1381_FC3smp.
> See /var/log/dell_rbu.log for output from modprobe.
> Starting ipmi driver:                                      [FAILED]
> Starting Systems Management Device Drivers:
> Building dell_rbu using DKS:                               [  OK  ]
> Starting dell_rbu:                                         [FAILED]
> dell_rbu device driver load failed for kernel 2.6.12-1.1381_FC3smp.
> See /var/log/dell_rbu.log for output from modprobe.
> Starting ipmi driver:                                      [FAILED]
> Starting DSM SA Shared Services:                           [  OK  ]
> 
> Starting DSM SA Connection Service:                        [  OK  ]
> 
> Looking in /var/log/dell_rbu.log, I see:
> 
> FATAL: Error inserting dell_rbu
> (/lib/modules/2.6.12-1.1381_FC3smp/kernel/drivers/firmware/dell_rbu.ko):
> Invalid module format
> FATAL: Error inserting dell_rbu
> (/lib/modules/2.6.12-1.1381_FC3smp/kernel/drivers/firmware/dell_rbu.ko):
> Invalid module format
> 
> and in dmesg, I see:
> 
> 
> dell_rbu: version magic '2.6.12-1.1381_FC3smp SMP 686 REGPARM 4KSTACKS
> gcc-4.1' should be '2.6.12-1.1381_FC3smp SMP 686 REGPARM 4KSTACKS
> gcc-3.4'
> 
> I've seen this gcc error before, but that was when I was using version
> 4.5 - and previously my fix had been to upgrade to OMSA 5.0. Can anyone
> suggest another avenue of attack?
> 
> Thanks, Tom
> --
> Tom Haddon <tom at greenleaftech.net>
> 
> _______________________________________________
> Linux-PowerEdge mailing list
> Linux-PowerEdge at dell.com
> http://lists.us.dell.com/mailman/listinfo/linux-poweredge
> Please read the FAQ at http://lists.us.dell.com/faq
-- 
Tom Haddon <tom at greenleaftech.net>



More information about the Linux-PowerEdge mailing list