hpacucli problem

View: New views
4 Messages — Rating Filter:   Alert me  

hpacucli problem

by Dávid Fazekaš :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

could you please take a look at this?
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/128288
It's opened a half of year and stefan doesn't care about that and
doesn't response to my emails.
thx

--
Dávid Fazekaš
Network technologies s.r.o.
Vodárenská 25, 040 01 Košice
Tel: 0911 497 937



__________ Informacia od ESET Smart Security, verzia databazy 3805 (20090127) __________

Tuto spravu preveril ESET Smart Security.

http://www.eset.sk


_______________________________________________
freebsd-proliant@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-proliant
To unsubscribe, send any mail to "freebsd-proliant-unsubscribe@..."

Re: hpacucli problem

by kama-4 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


On Wed, 28 Jan 2009, [windows-1252] Dávid Fazeka? wrote:

> could you please take a look at this?
> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/128288
> It's opened a half of year and stefan doesn't care about that and
> doesn't response to my emails.
> thx

You must manually use ldconfig to add that library.

# ldconfig -32 -m /usr/local/lib/compaq/hpacucli

But even when you do, it will not work, since it will not find the
controller. At least not with P800. On FreeBSD x86 it will find the
controller and work correctly, at least with the old SA 6400.

AFAIK, that port should be consider broken for amd64.

/Bjorn

---

# uname -rsp
FreeBSD 7.1-PRERELEASE amd64
# hpacucli controller all show
In AddChild:0x838b180
In AddChild child doesnot exists:0x838b180
Iam inside findDevce
The device enumerated now is 0x838b180
In Reenumerate Childern Eoption is 1
...
Operation Call: OperationDiscoverNonFibreHBA
zzz freebsd Bus = 14, devfn = 0, dev = 0, fn = 0
freebsd, Looking for bus 14, device 0, function 0
ioctl: Inappropriate ioctl for device
zzz freebsd Bus = 6, devfn = 0, dev = 0, fn = 0
freebsd, Looking for bus 6, device 0, function 0
ioctl: Inappropriate ioctl for device
Wed Jan 28 09:17:25 2009
Operation Call: OperationDiscoverInternalArrayControllers
zzz freebsd Bus = 14, devfn = 0, dev = 0, fn = 0
freebsd, Looking for bus 14, device 0, function 0
ioctl: Inappropriate ioctl for device
zzz freebsd Bus = 6, devfn = 0, dev = 0, fn = 0
freebsd, Looking for bus 6, device 0, function 0
ioctl: Inappropriate ioctl for device
Wed Jan 28 09:17:25 2009
Operation Call: OperationDiscoverChildren
The device enumerated now is 0x838b180
In Reenumerate Childern Eoption is 2
In Enumerate Child nodes
Wed Jan 28 09:17:25 2009
Operation Call: OperationSystemPostProcess
Pchild in GenerateXML:0x8385d80
Pchild in GenerateXML:0x0

Error: No controllers detected.

Wed Jan 28 09:17:25 2009
Operation Call: OperationReleaseConfigurationMutex
Wed Jan 28 09:17:25 2009
<Operation>
Wed Jan 28 09:17:25 2009
    <Name>OperationReleaseConfigurationMutex</Name>
Wed Jan 28 09:17:25 2009
    <Target>ModRoot137888128-System137933184</Target>
Wed Jan 28 09:17:25 2009
</Operation>
_______________________________________________
freebsd-proliant@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-proliant
To unsubscribe, send any mail to "freebsd-proliant-unsubscribe@..."

Re: hpacucli problem

by Florian Smeets :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On 28.01.2009 10:28 Uhr, kama wrote:

> On Wed, 28 Jan 2009, [windows-1252] Dávid Fazeka? wrote:
>
>> could you please take a look at this?
>> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/128288
>> It's opened a half of year and stefan doesn't care about that and
>> doesn't response to my emails.
>> thx
>
> You must manually use ldconfig to add that library.
>
> # ldconfig -32 -m /usr/local/lib/compaq/hpacucli
>
> But even when you do, it will not work, since it will not find the
> controller. At least not with P800. On FreeBSD x86 it will find the
> controller and work correctly, at least with the old SA 6400.

I had the same experience with 7.1-RELEASE/amd64 on DL380G5/DL360G5 with
P400/P400i, the controller was not found by hpacucli.

Cheers,
Florian
_______________________________________________
freebsd-proliant@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-proliant
To unsubscribe, send any mail to "freebsd-proliant-unsubscribe@..."

Re: hpacucli problem

by Stefan Walter-5 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

kama, 28.01.09, 10:28h CET:

> On Wed, 28 Jan 2009, [windows-1252] Dávid Fazeka? wrote:
>
> > could you please take a look at this?
> > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/128288
> > It's opened a half of year and stefan doesn't care about that and
> > doesn't response to my emails.

It seems I have to correct this a bit:

- The PR has been submitted three months ago. That's not half a year, at
  least not over here.
- Since noone else got involved, I assigned this PR to me one month ago to
  track its state.
- There hasn't been any response by the maintainer since then.
- You (David) submitted a followup to the PR on Sunday (3 days ago) which
  contained no information other than that you are seeing the same
  problem on a 7.1 system.
- You (David) sent *one* e-mail to me *last night/this morning* basically
  just asking for this problem to be fixed.

I strongly encourage you (David) to think again about what you expect from
people who work on this voluntarily without contributing anything to fix
the problem yourself.

> You must manually use ldconfig to add that library.
>
> # ldconfig -32 -m /usr/local/lib/compaq/hpacucli

I have committed a patch this morning which does this.

> But even when you do, it will not work, since it will not find the
> controller. At least not with P800. On FreeBSD x86 it will find the
> controller and work correctly, at least with the old SA 6400.

Oleg Gawriloff (the PR's originator) reported it doesn't work for him,
either, so maybe it really is a general problem on amd64.

> AFAIK, that port should be consider broken for amd64.

If this is a problem on amd64 in general it should be, yes. Can more
people confirm that it doesn't work, or is somebody able to use this
software on amd64?

Regards,
Stefan


attachment0 (664 bytes) Download Attachment