dell_rbu gcc version conflict
Davis_Phillips at Dell.com
Davis_Phillips at Dell.com
Fri Sep 8 08:57:58 CDT 2006
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
More information about the Linux-PowerEdge
mailing list