RH 7.1, Reiserfs, Compaq Heath and Wellness Driver on ML530

RH 7.1, Reiserfs, Compaq Heath and Wellness Driver on ML530

Post by EtherNu » Tue, 22 Jan 2002 11:55:12



My situation:

I have a Compaq ML 530 Server.  I have Reiserfs as my file system type and
kernel 2.4.9-6.  I cannot get Compaq's Health and Wellness drivers to load.
I get a segfault when I try to load them.  I called Compaq's technical
support and they basically said that it would work if I ran the stock Kernel
(stock is 2.4.2-2)  but if I have changed my kernel or upgraded in any way
the driver wouldn't work.  So, I test their theory, and they were right.  On
the stock kernel for 7.1 they work fine.  Well Comapq, that's wonderful that
the drivers run like a chanp on stock kernels, BUUUUUT, no one in their
right mind would be running 2.4.2-2 on a production server with Reiserfs not
to mention the massive work to repair the VM since 7.1 came out.  According
to namesys.com, I shouldn't be running 2.4.9 and I need to be on 2.4.10-pre4
minimum.  So I'm looking at upgrading again.

Here's the error I get:

Jan 15 17:22:19 goku cpcpqhealth: /lib/modules/Compaq/cpcpqhealth: line 2:
548 Segmentation fault      /sbin/insmod -f $1
 >/dev/null 2>/dev/null
Jan 15 17:22:19 goku kernel: Dentry-cache hash table entries: 32768 (order:
6, 262144 bytes)
Jan 15 17:22:20 goku cpcpqhealth: /lib/modules/Compaq/cpcpqhealth: line 2:
549 Segmentation fault      /sbin/insmod -f $1
 >/dev/null 2>/dev/null
Jan 15 17:22:20 goku cpqhealth: Starting Compaq Health & Wellness succeeded
Jan 15 17:22:32 goku kernel: ------------[ cut here ]------------
Jan 15 17:22:32 goku kernel: kernel BUG at slab.c:1096!
Jan 15 17:22:32 goku kernel: invalid operand: 0000
Jan 15 17:22:32 goku kernel: CPU:    0
Jan 15 17:22:32 goku kernel: EIP:    0010:[kmem_cache_grow+38/576]    Not
tainted
Jan 15 17:22:32 goku kernel: EIP:    0010:[<c012ce86>]    Not tainted
Jan 15 17:22:32 goku kernel: EFLAGS: 00010296
Jan 15 17:22:32 goku kernel: eax: 0000001b   ebx: c1822490   ecx: 00000001
edx: 00001bf8
Jan 15 17:22:32 goku kernel: esi: c1822490   edi: 00000007   ebp: 00000007
esp: cf0d1e3c
Jan 15 17:22:33 goku kernel: ds: 0018   es: 0018   ss: 0018
Jan 15 17:22:33 goku kernel: Process insmod (pid: 548, stackpage=cf0d1000)
Jan 15 17:22:33 goku kernel: Stack: c0219126 00000448 c02d4144 00000203
c02d3fa4 00000000 c02d3f60 c02d3f60
Jan 15 17:22:33 goku kernel:        c02d4144 c1822490 00000202 c1822490
00000007 c012d23f c1822490 00000007
Jan 15 17:22:33 goku kernel:        c1004520 c013029f 000000d2 00000000
d0967000 00000000 00000000 cf0d1eb8
Jan 15 17:22:33 goku kernel: Call Trace: [copyrite+19974/24619] copyrite
[kernel] 0x4e06
Jan 15 17:22:33 goku kernel: Call Trace: [<c0219126>] copyrite [kernel]
0x4e06
Jan 15 17:22:33 goku kernel: [kmalloc+223/272] kmalloc [kernel] 0xdf
Jan 15 17:22:33 goku kernel: [<c012d23f>] kmalloc [kernel] 0xdf
Jan 15 17:22:33 goku kernel: [__alloc_pages+15/160] __alloc_pages [kernel]
0xf
Jan 15 17:22:33 goku kernel: [<c013029f>] __alloc_pages [kernel] 0xf
Jan 15 17:22:33 goku kernel:
[reiserfs:__insmod_reiserfs_S.bss_L6624+1059820/401337892] cromMalloc
[cpqrom] 0x10
Jan 15 17:22:33 goku kernel: [<d096884c>] cromMalloc [cpqrom] 0x10
Jan 15 17:22:33 goku xinetd: xinetd startup succeeded
Jan 15 17:22:33 goku kernel:
[reiserfs:__insmod_reiserfs_S.bss_L6624+1065401/401332311] init_crommemory
[cpqrom] 0x1d
Jan 15 17:22:33 goku kernel: [<d0969e19>] init_crommemory [cpqrom] 0x1d
Jan 15 17:22:33 goku kernel: [_wrapped_alloc_pages+102/608]
_wrapped_alloc_pages [kernel] 0x66
Jan 15 17:22:33 goku xinetd[716]: chargen disabled, removing
Jan 15 17:22:34 goku kernel: [<c0130096>] _wrapped_alloc_pages [kernel] 0x66
Jan 15 17:22:34 goku xinetd[716]: chargen disabled, removing
Jan 15 17:22:34 goku kernel:
[reiserfs:__insmod_reiserfs_S.bss_L6624+1060235/401337477] crominit [cpqrom]
0xb
Jan 15 17:22:34 goku kernel: [<d09689eb>] crominit [cpqrom] 0xb
Jan 15 17:22:34 goku kernel:
[reiserfs:__insmod_reiserfs_S.bss_L6624+1065675/401332037] CromUnLock
[cpqrom] 0x17
Jan 15 17:22:34 goku kernel: [<d0969f2b>] CromUnLock [cpqrom] 0x17
Jan 15 17:22:34 goku kernel: [sys_init_module+1333/1536] sys_init_module
[kernel] 0x535
Jan 15 17:22:34 goku kernel: [<c0118935>] sys_init_module [kernel] 0x535
Jan 15 17:22:34 goku kernel:
[reiserfs:__insmod_reiserfs_S.bss_L6624+1053696/401344016]
__insmod_cpqrom_O/lib/modules/2.4.9
-6/kernel/drivers/char/cpqrom.o_M3BD52A29_V132098 [cpqrom] 0x60
Jan 15 17:22:34 goku kernel: [system_call+51/56] system_call [kernel] 0x33
Jan 15 17:22:34 goku xinetd[716]: daytime disabled, removing
Jan 15 17:22:34 goku kernel: [<c0106f3b>] system_call [kernel] 0x33
Jan 15 17:22:34 goku xinetd[716]: daytime disabled, removing
Jan 15 17:22:34 goku kernel:
Jan 15 17:22:34 goku xinetd[716]: echo disabled, removing
Jan 15 17:22:34 goku kernel:
Jan 15 17:22:34 goku xinetd[716]: echo disabled, removing
Jan 15 17:22:34 goku kernel: Code: 0f 0b 59 5b f7 c7 00 10 00 00 0f 85 f1 01
00 00 a1 68 db 33
Jan 15 17:22:35 goku xinetd[716]: finger disabled, removing
Jan 15 17:22:35 goku kernel:  ------------[ cut here ]------------

My question to the community:

What is it about Compaq's drivers that make them kernel specific?  I can't
seem to understand why their drivers won't run on the newer 2.4.x kernels...
Has anyone out there dealt with this issue?  Any advice?

My Compaq Rant:
It is my personal opinion that Compaq should be more friendly to the
community... I asked them to give me source RPMS or the code to allow me to
recompile to fit my box but NOOOOO .  They wouldn't do that.  Instead they
said I could contract them for $200/hr to make it work on my kernel.  I that
didn't settle very well with me, but I don't have a choice.  I've always
liked Compaq, their servers, their support and still do.  This particular
issue has made me aware of Compaq's willingness to support their hardware on
linux.  Buyer beware.  If you're willing to stick with stock kernels and
never recompile or upgrade, Compaq is a wonderful choice.  If you're like
the rest of us that try to keep up with security/stabiliy issues and upgrade
our software when needed... don't buy compaq and expect their proprietary
drivers to work..

Thanks a bunch for any insight you all might have in my issue.
EtherNut

 
 
 

RH 7.1, Reiserfs, Compaq Heath and Wellness Driver on ML530

Post by Gavenda, Bar » Wed, 23 Jan 2002 02:20:31



> My situation:

> I have a Compaq ML 530 Server.  I have Reiserfs as my file system type and
> kernel 2.4.9-6.  I cannot get Compaq's Health and Wellness drivers to load.
> I get a segfault when I try to load them.  I called Compaq's technical
> support and they basically said that it would work if I ran the stock Kernel
> (stock is 2.4.2-2)  but if I have changed my kernel or upgraded in any way
> the driver wouldn't work.  So, I test their theory, and they were right.  On
> the stock kernel for 7.1 they work fine.  Well Comapq, that's wonderful that
> the drivers run like a chanp on stock kernels, BUUUUUT, no one in their
> right mind would be running 2.4.2-2 on a production server with Reiserfs not
> to mention the massive work to repair the VM since 7.1 came out.  According
> to namesys.com, I shouldn't be running 2.4.9 and I need to be on 2.4.10-pre4
> minimum.  So I'm looking at upgrading again.

> Here's the error I get:

> Jan 15 17:22:19 goku cpcpqhealth: /lib/modules/Compaq/cpcpqhealth: line 2:
> 548 Segmentation fault      /sbin/insmod -f $1
>  >/dev/null 2>/dev/null
> Jan 15 17:22:19 goku kernel: Dentry-cache hash table entries: 32768 (order:
> 6, 262144 bytes)
> Jan 15 17:22:20 goku cpcpqhealth: /lib/modules/Compaq/cpcpqhealth: line 2:
> 549 Segmentation fault      /sbin/insmod -f $1
>  >/dev/null 2>/dev/null
> Jan 15 17:22:20 goku cpqhealth: Starting Compaq Health & Wellness succeeded
> Jan 15 17:22:32 goku kernel: ------------[ cut here ]------------
> Jan 15 17:22:32 goku kernel: kernel BUG at slab.c:1096!
> Jan 15 17:22:32 goku kernel: invalid operand: 0000
> Jan 15 17:22:32 goku kernel: CPU:    0
> Jan 15 17:22:32 goku kernel: EIP:    0010:[kmem_cache_grow+38/576]    Not
> tainted
> Jan 15 17:22:32 goku kernel: EIP:    0010:[<c012ce86>]    Not tainted
> Jan 15 17:22:32 goku kernel: EFLAGS: 00010296
> Jan 15 17:22:32 goku kernel: eax: 0000001b   ebx: c1822490   ecx: 00000001
> edx: 00001bf8
> Jan 15 17:22:32 goku kernel: esi: c1822490   edi: 00000007   ebp: 00000007
> esp: cf0d1e3c
> Jan 15 17:22:33 goku kernel: ds: 0018   es: 0018   ss: 0018
> Jan 15 17:22:33 goku kernel: Process insmod (pid: 548, stackpage=cf0d1000)
> Jan 15 17:22:33 goku kernel: Stack: c0219126 00000448 c02d4144 00000203
> c02d3fa4 00000000 c02d3f60 c02d3f60
> Jan 15 17:22:33 goku kernel:        c02d4144 c1822490 00000202 c1822490
> 00000007 c012d23f c1822490 00000007
> Jan 15 17:22:33 goku kernel:        c1004520 c013029f 000000d2 00000000
> d0967000 00000000 00000000 cf0d1eb8
> Jan 15 17:22:33 goku kernel: Call Trace: [copyrite+19974/24619] copyrite
> [kernel] 0x4e06
> Jan 15 17:22:33 goku kernel: Call Trace: [<c0219126>] copyrite [kernel]
> 0x4e06
> Jan 15 17:22:33 goku kernel: [kmalloc+223/272] kmalloc [kernel] 0xdf
> Jan 15 17:22:33 goku kernel: [<c012d23f>] kmalloc [kernel] 0xdf
> Jan 15 17:22:33 goku kernel: [__alloc_pages+15/160] __alloc_pages [kernel]
> 0xf
> Jan 15 17:22:33 goku kernel: [<c013029f>] __alloc_pages [kernel] 0xf
> Jan 15 17:22:33 goku kernel:
> [reiserfs:__insmod_reiserfs_S.bss_L6624+1059820/401337892] cromMalloc
> [cpqrom] 0x10
> Jan 15 17:22:33 goku kernel: [<d096884c>] cromMalloc [cpqrom] 0x10
> Jan 15 17:22:33 goku xinetd: xinetd startup succeeded
> Jan 15 17:22:33 goku kernel:
> [reiserfs:__insmod_reiserfs_S.bss_L6624+1065401/401332311] init_crommemory
> [cpqrom] 0x1d
> Jan 15 17:22:33 goku kernel: [<d0969e19>] init_crommemory [cpqrom] 0x1d
> Jan 15 17:22:33 goku kernel: [_wrapped_alloc_pages+102/608]
> _wrapped_alloc_pages [kernel] 0x66
> Jan 15 17:22:33 goku xinetd[716]: chargen disabled, removing
> Jan 15 17:22:34 goku kernel: [<c0130096>] _wrapped_alloc_pages [kernel] 0x66
> Jan 15 17:22:34 goku xinetd[716]: chargen disabled, removing
> Jan 15 17:22:34 goku kernel:
> [reiserfs:__insmod_reiserfs_S.bss_L6624+1060235/401337477] crominit [cpqrom]
> 0xb
> Jan 15 17:22:34 goku kernel: [<d09689eb>] crominit [cpqrom] 0xb
> Jan 15 17:22:34 goku kernel:
> [reiserfs:__insmod_reiserfs_S.bss_L6624+1065675/401332037] CromUnLock
> [cpqrom] 0x17
> Jan 15 17:22:34 goku kernel: [<d0969f2b>] CromUnLock [cpqrom] 0x17
> Jan 15 17:22:34 goku kernel: [sys_init_module+1333/1536] sys_init_module
> [kernel] 0x535
> Jan 15 17:22:34 goku kernel: [<c0118935>] sys_init_module [kernel] 0x535
> Jan 15 17:22:34 goku kernel:
> [reiserfs:__insmod_reiserfs_S.bss_L6624+1053696/401344016]
> __insmod_cpqrom_O/lib/modules/2.4.9
> -6/kernel/drivers/char/cpqrom.o_M3BD52A29_V132098 [cpqrom] 0x60
> Jan 15 17:22:34 goku kernel: [system_call+51/56] system_call [kernel] 0x33
> Jan 15 17:22:34 goku xinetd[716]: daytime disabled, removing
> Jan 15 17:22:34 goku kernel: [<c0106f3b>] system_call [kernel] 0x33
> Jan 15 17:22:34 goku xinetd[716]: daytime disabled, removing
> Jan 15 17:22:34 goku kernel:
> Jan 15 17:22:34 goku xinetd[716]: echo disabled, removing
> Jan 15 17:22:34 goku kernel:
> Jan 15 17:22:34 goku xinetd[716]: echo disabled, removing
> Jan 15 17:22:34 goku kernel: Code: 0f 0b 59 5b f7 c7 00 10 00 00 0f 85 f1 01
> 00 00 a1 68 db 33
> Jan 15 17:22:35 goku xinetd[716]: finger disabled, removing
> Jan 15 17:22:35 goku kernel:  ------------[ cut here ]------------

> My question to the community:

> What is it about Compaq's drivers that make them kernel specific?  I can't
> seem to understand why their drivers won't run on the newer 2.4.x kernels...
> Has anyone out there dealt with this issue?  Any advice?

> My Compaq Rant:
> It is my personal opinion that Compaq should be more friendly to the
> community... I asked them to give me source RPMS or the code to allow me to
> recompile to fit my box but NOOOOO .  They wouldn't do that.  Instead they
> said I could contract them for $200/hr to make it work on my kernel.  I that
> didn't settle very well with me, but I don't have a choice.  I've always
> liked Compaq, their servers, their support and still do.  This particular
> issue has made me aware of Compaq's willingness to support their hardware on
> linux.  Buyer beware.  If you're willing to stick with stock kernels and
> never recompile or upgrade, Compaq is a wonderful choice.  If you're like
> the rest of us that try to keep up with security/stabiliy issues and upgrade
> our software when needed... don't buy compaq and expect their proprietary
> drivers to work..

> Thanks a bunch for any insight you all might have in my issue.
> EtherNut

Same deal here w/ my ML350's and RH 7.1.  I upgrade to 2.4.9-12 kernel
and lost cpqhealth and cpqrom.  Could not even removed them until I
completely rebuilt the Kernel from source.  Then tried the 2.3 version
of cpqhealth and It bombed as well, as it is designed for RH 7.2.
Tried manually adding the 2.3 cpqhealth to no avail (only runs on
2.4.7).  I got the same smart ass remarks from Compaq tech support,
saying I should not have upgraded and now I'm screwed, but I can pay
$200.00 to have someone tell me I'm screwed for an hour and I should
downgrade back to 2.4.2.
When you pay $$$ for a Compaq Proliant system that advertises it
supports an OS, it should support that OS and all upgrades to that OS.

 
 
 

RH 7.1, Reiserfs, Compaq Heath and Wellness Driver on ML530

Post by EtherNu » Wed, 23 Jan 2002 11:31:08


Yeah, that's pretty much BULL SH!T.  Compaq should atleast keep up with Red
Hat's updates to the OS version.kernel.  I'd be happy to run 2.4.9-12 if
their *would run on it.

If anyone has had any success please post!

Barry, thanks for your response!

EtherNut



Quote:> > My situation:

> > I have a Compaq ML 530 Server.  I have Reiserfs as my file system type
and
> > kernel 2.4.9-6.  I cannot get Compaq's Health and Wellness drivers to
load.
> > I get a segfault when I try to load them.  I called Compaq's technical
> > support and they basically said that it would work if I ran the stock
Kernel
> > (stock is 2.4.2-2)  but if I have changed my kernel or upgraded in any
way
> > the driver wouldn't work.  So, I test their theory, and they were right.
On
> > the stock kernel for 7.1 they work fine.  Well Comapq, that's wonderful
that
> > the drivers run like a chanp on stock kernels, BUUUUUT, no one in their
> > right mind would be running 2.4.2-2 on a production server with Reiserfs
not
> > to mention the massive work to repair the VM since 7.1 came out.
According
> > to namesys.com, I shouldn't be running 2.4.9 and I need to be on
2.4.10-pre4
> > minimum.  So I'm looking at upgrading again.

> > Here's the error I get:

> > Jan 15 17:22:19 goku cpcpqhealth: /lib/modules/Compaq/cpcpqhealth: line
2:
> > 548 Segmentation fault      /sbin/insmod -f $1
> >  >/dev/null 2>/dev/null
> > Jan 15 17:22:19 goku kernel: Dentry-cache hash table entries: 32768
(order:
> > 6, 262144 bytes)
> > Jan 15 17:22:20 goku cpcpqhealth: /lib/modules/Compaq/cpcpqhealth: line
2:
> > 549 Segmentation fault      /sbin/insmod -f $1
> >  >/dev/null 2>/dev/null
> > Jan 15 17:22:20 goku cpqhealth: Starting Compaq Health & Wellness
succeeded
> > Jan 15 17:22:32 goku kernel: ------------[ cut here ]------------
> > Jan 15 17:22:32 goku kernel: kernel BUG at slab.c:1096!
> > Jan 15 17:22:32 goku kernel: invalid operand: 0000
> > Jan 15 17:22:32 goku kernel: CPU:    0
> > Jan 15 17:22:32 goku kernel: EIP:    0010:[kmem_cache_grow+38/576]
Not
> > tainted
> > Jan 15 17:22:32 goku kernel: EIP:    0010:[<c012ce86>]    Not tainted
> > Jan 15 17:22:32 goku kernel: EFLAGS: 00010296
> > Jan 15 17:22:32 goku kernel: eax: 0000001b   ebx: c1822490   ecx:
00000001
> > edx: 00001bf8
> > Jan 15 17:22:32 goku kernel: esi: c1822490   edi: 00000007   ebp:
00000007
> > esp: cf0d1e3c
> > Jan 15 17:22:33 goku kernel: ds: 0018   es: 0018   ss: 0018
> > Jan 15 17:22:33 goku kernel: Process insmod (pid: 548,
stackpage=cf0d1000)
> > Jan 15 17:22:33 goku kernel: Stack: c0219126 00000448 c02d4144 00000203
> > c02d3fa4 00000000 c02d3f60 c02d3f60
> > Jan 15 17:22:33 goku kernel:        c02d4144 c1822490 00000202 c1822490
> > 00000007 c012d23f c1822490 00000007
> > Jan 15 17:22:33 goku kernel:        c1004520 c013029f 000000d2 00000000
> > d0967000 00000000 00000000 cf0d1eb8
> > Jan 15 17:22:33 goku kernel: Call Trace: [copyrite+19974/24619] copyrite
> > [kernel] 0x4e06
> > Jan 15 17:22:33 goku kernel: Call Trace: [<c0219126>] copyrite [kernel]
> > 0x4e06
> > Jan 15 17:22:33 goku kernel: [kmalloc+223/272] kmalloc [kernel] 0xdf
> > Jan 15 17:22:33 goku kernel: [<c012d23f>] kmalloc [kernel] 0xdf
> > Jan 15 17:22:33 goku kernel: [__alloc_pages+15/160] __alloc_pages
[kernel]
> > 0xf
> > Jan 15 17:22:33 goku kernel: [<c013029f>] __alloc_pages [kernel] 0xf
> > Jan 15 17:22:33 goku kernel:
> > [reiserfs:__insmod_reiserfs_S.bss_L6624+1059820/401337892] cromMalloc
> > [cpqrom] 0x10
> > Jan 15 17:22:33 goku kernel: [<d096884c>] cromMalloc [cpqrom] 0x10
> > Jan 15 17:22:33 goku xinetd: xinetd startup succeeded
> > Jan 15 17:22:33 goku kernel:
> > [reiserfs:__insmod_reiserfs_S.bss_L6624+1065401/401332311]
init_crommemory
> > [cpqrom] 0x1d
> > Jan 15 17:22:33 goku kernel: [<d0969e19>] init_crommemory [cpqrom] 0x1d
> > Jan 15 17:22:33 goku kernel: [_wrapped_alloc_pages+102/608]
> > _wrapped_alloc_pages [kernel] 0x66
> > Jan 15 17:22:33 goku xinetd[716]: chargen disabled, removing
> > Jan 15 17:22:34 goku kernel: [<c0130096>] _wrapped_alloc_pages [kernel]
0x66
> > Jan 15 17:22:34 goku xinetd[716]: chargen disabled, removing
> > Jan 15 17:22:34 goku kernel:
> > [reiserfs:__insmod_reiserfs_S.bss_L6624+1060235/401337477] crominit
[cpqrom]
> > 0xb
> > Jan 15 17:22:34 goku kernel: [<d09689eb>] crominit [cpqrom] 0xb
> > Jan 15 17:22:34 goku kernel:
> > [reiserfs:__insmod_reiserfs_S.bss_L6624+1065675/401332037] CromUnLock
> > [cpqrom] 0x17
> > Jan 15 17:22:34 goku kernel: [<d0969f2b>] CromUnLock [cpqrom] 0x17
> > Jan 15 17:22:34 goku kernel: [sys_init_module+1333/1536] sys_init_module
> > [kernel] 0x535
> > Jan 15 17:22:34 goku kernel: [<c0118935>] sys_init_module [kernel] 0x535
> > Jan 15 17:22:34 goku kernel:
> > [reiserfs:__insmod_reiserfs_S.bss_L6624+1053696/401344016]
> > __insmod_cpqrom_O/lib/modules/2.4.9
> > -6/kernel/drivers/char/cpqrom.o_M3BD52A29_V132098 [cpqrom] 0x60
> > Jan 15 17:22:34 goku kernel: [system_call+51/56] system_call [kernel]
0x33
> > Jan 15 17:22:34 goku xinetd[716]: daytime disabled, removing
> > Jan 15 17:22:34 goku kernel: [<c0106f3b>] system_call [kernel] 0x33
> > Jan 15 17:22:34 goku xinetd[716]: daytime disabled, removing
> > Jan 15 17:22:34 goku kernel:
> > Jan 15 17:22:34 goku xinetd[716]: echo disabled, removing
> > Jan 15 17:22:34 goku kernel:
> > Jan 15 17:22:34 goku xinetd[716]: echo disabled, removing
> > Jan 15 17:22:34 goku kernel: Code: 0f 0b 59 5b f7 c7 00 10 00 00 0f 85
f1 01
> > 00 00 a1 68 db 33
> > Jan 15 17:22:35 goku xinetd[716]: finger disabled, removing
> > Jan 15 17:22:35 goku kernel:  ------------[ cut here ]------------

> > My question to the community:

> > What is it about Compaq's drivers that make them kernel specific?  I
can't
> > seem to understand why their drivers won't run on the newer 2.4.x
kernels...
> > Has anyone out there dealt with this issue?  Any advice?

> > My Compaq Rant:
> > It is my personal opinion that Compaq should be more friendly to the
> > community... I asked them to give me source RPMS or the code to allow me
to
> > recompile to fit my box but NOOOOO .  They wouldn't do that.  Instead
they
> > said I could contract them for $200/hr to make it work on my kernel.  I
that
> > didn't settle very well with me, but I don't have a choice.  I've always
> > liked Compaq, their servers, their support and still do.  This
particular
> > issue has made me aware of Compaq's willingness to support their
hardware on
> > linux.  Buyer beware.  If you're willing to stick with stock kernels and
> > never recompile or upgrade, Compaq is a wonderful choice.  If you're
like
> > the rest of us that try to keep up with security/stabiliy issues and
upgrade
> > our software when needed... don't buy compaq and expect their
proprietary
> > drivers to work..

> > Thanks a bunch for any insight you all might have in my issue.
> > EtherNut

> Same deal here w/ my ML350's and RH 7.1.  I upgrade to 2.4.9-12 kernel
> and lost cpqhealth and cpqrom.  Could not even removed them until I
> completely rebuilt the Kernel from source.  Then tried the 2.3 version
> of cpqhealth and It bombed as well, as it is designed for RH 7.2.
> Tried manually adding the 2.3 cpqhealth to no avail (only runs on
> 2.4.7).  I got the same smart ass remarks from Compaq tech support,
> saying I should not have upgraded and now I'm screwed, but I can pay
> $200.00 to have someone tell me I'm screwed for an hour and I should
> downgrade back to 2.4.2.
> When you pay $$$ for a Compaq Proliant system that advertises it
> supports an OS, it should support that OS and all upgrades to that OS.

 
 
 

RH 7.1, Reiserfs, Compaq Heath and Wellness Driver on ML530

Post by Bjor » Sat, 16 Feb 2002 19:09:16


This is pure BS. This is like saying that they support NT4 as long as
you don't apply any servicepacks.

They do support updates to NT4 so why wouldn't they do the same if you
run Linux.

This is just another example of companies that say that they support Linux
to make it a media hype but they don't take any responsibilities for it in
the long run.

// Bjorn

"EtherNut" <jle...@yahoo.com> wrote in message <news:V5438.32878$Y17.2732443@e3500-atl2.usenetserver.com>...
> Yeah, that's pretty much BULL SH!T.  Compaq should atleast keep up with Red
> Hat's updates to the OS version.kernel.  I'd be happy to run 2.4.9-12 if
> their crap would run on it.

> If anyone has had any success please post!

> Barry, thanks for your response!

> EtherNut

> "Gavenda, Barry" <bgave...@classifiedventures.com> wrote in message
> news:126b1d86.0201210920.10089a09@posting.google.com...
> > "EtherNut" <jle...@yahoo.com> wrote in message
>  <news:XfL28.31295$Ee7.2595864@e3500-atl1.usenetserver.com>...
> > > My situation:

> > > I have a Compaq ML 530 Server.  I have Reiserfs as my file system type
>  and
> > > kernel 2.4.9-6.  I cannot get Compaq's Health and Wellness drivers to
>  load.
> > > I get a segfault when I try to load them.  I called Compaq's technical
> > > support and they basically said that it would work if I ran the stock
>  Kernel
> > > (stock is 2.4.2-2)  but if I have changed my kernel or upgraded in any
>  way
> > > the driver wouldn't work.  So, I test their theory, and they were right.
>  On
> > > the stock kernel for 7.1 they work fine.  Well Comapq, that's wonderful
>  that
> > > the drivers run like a chanp on stock kernels, BUUUUUT, no one in their
> > > right mind would be running 2.4.2-2 on a production server with Reiserfs
>  not
> > > to mention the massive work to repair the VM since 7.1 came out.
>  According
> > > to namesys.com, I shouldn't be running 2.4.9 and I need to be on
>  2.4.10-pre4
> > > minimum.  So I'm looking at upgrading again.

> > > Here's the error I get:

> > > Jan 15 17:22:19 goku cpcpqhealth: /lib/modules/Compaq/cpcpqhealth: line
>  2:
> > > 548 Segmentation fault      /sbin/insmod -f $1
> > >  >/dev/null 2>/dev/null
> > > Jan 15 17:22:19 goku kernel: Dentry-cache hash table entries: 32768
>  (order:
> > > 6, 262144 bytes)
> > > Jan 15 17:22:20 goku cpcpqhealth: /lib/modules/Compaq/cpcpqhealth: line
>  2:
> > > 549 Segmentation fault      /sbin/insmod -f $1
> > >  >/dev/null 2>/dev/null
> > > Jan 15 17:22:20 goku cpqhealth: Starting Compaq Health & Wellness
>  succeeded
> > > Jan 15 17:22:32 goku kernel: ------------[ cut here ]------------
> > > Jan 15 17:22:32 goku kernel: kernel BUG at slab.c:1096!
> > > Jan 15 17:22:32 goku kernel: invalid operand: 0000
> > > Jan 15 17:22:32 goku kernel: CPU:    0
> > > Jan 15 17:22:32 goku kernel: EIP:    0010:[kmem_cache_grow+38/576]
>  Not
> > > tainted
> > > Jan 15 17:22:32 goku kernel: EIP:    0010:[<c012ce86>]    Not tainted
> > > Jan 15 17:22:32 goku kernel: EFLAGS: 00010296
> > > Jan 15 17:22:32 goku kernel: eax: 0000001b   ebx: c1822490   ecx:
>  00000001
> > > edx: 00001bf8
> > > Jan 15 17:22:32 goku kernel: esi: c1822490   edi: 00000007   ebp:
>  00000007
> > > esp: cf0d1e3c
> > > Jan 15 17:22:33 goku kernel: ds: 0018   es: 0018   ss: 0018
> > > Jan 15 17:22:33 goku kernel: Process insmod (pid: 548,
>  stackpage=cf0d1000)
> > > Jan 15 17:22:33 goku kernel: Stack: c0219126 00000448 c02d4144 00000203
> > > c02d3fa4 00000000 c02d3f60 c02d3f60
> > > Jan 15 17:22:33 goku kernel:        c02d4144 c1822490 00000202 c1822490
> > > 00000007 c012d23f c1822490 00000007
> > > Jan 15 17:22:33 goku kernel:        c1004520 c013029f 000000d2 00000000
> > > d0967000 00000000 00000000 cf0d1eb8
> > > Jan 15 17:22:33 goku kernel: Call Trace: [copyrite+19974/24619] copyrite
> > > [kernel] 0x4e06
> > > Jan 15 17:22:33 goku kernel: Call Trace: [<c0219126>] copyrite [kernel]
> > > 0x4e06
> > > Jan 15 17:22:33 goku kernel: [kmalloc+223/272] kmalloc [kernel] 0xdf
> > > Jan 15 17:22:33 goku kernel: [<c012d23f>] kmalloc [kernel] 0xdf
> > > Jan 15 17:22:33 goku kernel: [__alloc_pages+15/160] __alloc_pages
>  [kernel]
> > > 0xf
> > > Jan 15 17:22:33 goku kernel: [<c013029f>] __alloc_pages [kernel] 0xf
> > > Jan 15 17:22:33 goku kernel:
> > > [reiserfs:__insmod_reiserfs_S.bss_L6624+1059820/401337892] cromMalloc
> > > [cpqrom] 0x10
> > > Jan 15 17:22:33 goku kernel: [<d096884c>] cromMalloc [cpqrom] 0x10
> > > Jan 15 17:22:33 goku xinetd: xinetd startup succeeded
> > > Jan 15 17:22:33 goku kernel:
> > > [reiserfs:__insmod_reiserfs_S.bss_L6624+1065401/401332311]
>  init_crommemory
> > > [cpqrom] 0x1d
> > > Jan 15 17:22:33 goku kernel: [<d0969e19>] init_crommemory [cpqrom] 0x1d
> > > Jan 15 17:22:33 goku kernel: [_wrapped_alloc_pages+102/608]
> > > _wrapped_alloc_pages [kernel] 0x66
> > > Jan 15 17:22:33 goku xinetd[716]: chargen disabled, removing
> > > Jan 15 17:22:34 goku kernel: [<c0130096>] _wrapped_alloc_pages [kernel]
>  0x66
> > > Jan 15 17:22:34 goku xinetd[716]: chargen disabled, removing
> > > Jan 15 17:22:34 goku kernel:
> > > [reiserfs:__insmod_reiserfs_S.bss_L6624+1060235/401337477] crominit
>  [cpqrom]
> > > 0xb
> > > Jan 15 17:22:34 goku kernel: [<d09689eb>] crominit [cpqrom] 0xb
> > > Jan 15 17:22:34 goku kernel:
> > > [reiserfs:__insmod_reiserfs_S.bss_L6624+1065675/401332037] CromUnLock
> > > [cpqrom] 0x17
> > > Jan 15 17:22:34 goku kernel: [<d0969f2b>] CromUnLock [cpqrom] 0x17
> > > Jan 15 17:22:34 goku kernel: [sys_init_module+1333/1536] sys_init_module
> > > [kernel] 0x535
> > > Jan 15 17:22:34 goku kernel: [<c0118935>] sys_init_module [kernel] 0x535
> > > Jan 15 17:22:34 goku kernel:
> > > [reiserfs:__insmod_reiserfs_S.bss_L6624+1053696/401344016]
> > > __insmod_cpqrom_O/lib/modules/2.4.9
> > > -6/kernel/drivers/char/cpqrom.o_M3BD52A29_V132098 [cpqrom] 0x60
> > > Jan 15 17:22:34 goku kernel: [system_call+51/56] system_call [kernel]
>  0x33
> > > Jan 15 17:22:34 goku xinetd[716]: daytime disabled, removing
> > > Jan 15 17:22:34 goku kernel: [<c0106f3b>] system_call [kernel] 0x33
> > > Jan 15 17:22:34 goku xinetd[716]: daytime disabled, removing
> > > Jan 15 17:22:34 goku kernel:
> > > Jan 15 17:22:34 goku xinetd[716]: echo disabled, removing
> > > Jan 15 17:22:34 goku kernel:
> > > Jan 15 17:22:34 goku xinetd[716]: echo disabled, removing
> > > Jan 15 17:22:34 goku kernel: Code: 0f 0b 59 5b f7 c7 00 10 00 00 0f 85
>  f1 01
> > > 00 00 a1 68 db 33
> > > Jan 15 17:22:35 goku xinetd[716]: finger disabled, removing
> > > Jan 15 17:22:35 goku kernel:  ------------[ cut here ]------------

> > > My question to the community:

> > > What is it about Compaq's drivers that make them kernel specific?  I
>  can't
> > > seem to understand why their drivers won't run on the newer 2.4.x
>  kernels...
> > > Has anyone out there dealt with this issue?  Any advice?

> > > My Compaq Rant:
> > > It is my personal opinion that Compaq should be more friendly to the
> > > community... I asked them to give me source RPMS or the code to allow me
>  to
> > > recompile to fit my box but NOOOOO .  They wouldn't do that.  Instead
>  they
> > > said I could contract them for $200/hr to make it work on my kernel.  I
>  that
> > > didn't settle very well with me, but I don't have a choice.  I've always
> > > liked Compaq, their servers, their support and still do.  This
>  particular
> > > issue has made me aware of Compaq's willingness to support their
>  hardware on
> > > linux.  Buyer beware.  If you're willing to stick with stock kernels and
> > > never recompile or upgrade, Compaq is a wonderful choice.  If you're
>  like
> > > the rest of us that try to keep up with security/stabiliy issues and
>  upgrade
> > > our software when needed... don't buy compaq and expect their
>  proprietary
> > > drivers to work..

> > > Thanks a bunch for any insight you all might have in my issue.
> > > EtherNut

> > Same deal here w/ my ML350's and RH 7.1.  I upgrade to 2.4.9-12 kernel
> > and lost cpqhealth and cpqrom.  Could not even removed them until I
> > completely rebuilt the Kernel from source.  Then tried the 2.3 version
> > of cpqhealth and It bombed as well, as it is designed for RH 7.2.
> > Tried manually adding the 2.3 cpqhealth to no avail (only runs on
> > 2.4.7).  I got the same smart ass remarks from Compaq tech support,
> > saying I should not have upgraded and now I'm screwed, but I can pay
> > $200.00 to have someone tell me I'm screwed for an hour and I should
> > downgrade back to 2.4.2.
> > When you pay $$$ for a Compaq Proliant system that advertises it
> > supports an OS, it should support that OS and all upgrades to that OS.

 
 
 

1. cpqimlview: Compaq Health & Wellness Drivers

Guys,

I'm wondering if anyone out there has the Compaq Health and Wellness
Drivers for Linux working on a Slackware box...

I've installed Slackware on a Compaq ML530 and would like to use their
wellness drivers, but am having a problem with one of the executables
that they provide.  Specifically, it's /sbin/imlbe.  I get a seg fault
when running this.

Does anyone know if I can obtain the source and compile it myself for
Slackware?

If anyone has had any luck with this, please let me know.

Thanks.

Sent via Deja.com
http://www.deja.com/

2. Xemacs and Linux

3. RH 7.1 Reiserfs on / mount point (2.4.8 kernel)

4. Question

5. transfer drivers from RH 7.1-> RH 6.2

6. Linux/Apache Guru Needed!($$)

7. Compaq Proliant 5500 keeps rebooting RH 7.1

8. Changing/appending to KDE icon path??

9. Installing RH 7.1 on Compaq Proliant 1500 with Disk Array Controller (RAID 5)

10. Adaptec 29160N w/ RH 7.1 on Compaq ML370

11. compaq alpha c++compiler & RH Linux 7.1

12. Installing RH 7.1 on Compaq Proliant 1500 with disk array (RAID 5)

13. What version of Solaris8 is supported on Compaq ML530 G2 server?