>>> On 05 May 2007 at 04:40, in message <[EMAIL PROTECTED]>,
Steve
Shockley <[EMAIL PROTECTED]> wrote:
> Raimo Niskanen wrote:
>> Sorry, I can't make it work. For a DL140 G3 (or rather now a DL145
G3).
>>
>> I remember seing something like that on a DL380, though.
>>
>> telnet gives a weird prom
Raimo Niskanen wrote:
Sorry, I can't make it work. For a DL140 G3 (or rather now a DL145 G3).
I remember seing something like that on a DL380, though.
telnet gives a weird prompt /./ that has no help and only
responds with command errors. There is also a HTTP server running
at the address. But
Hello Raimo,
Wednesday, May 2, 2007, 9:52:40 AM, you wrote:
RN> Sorry, I can't make it work. For a DL140 G3 (or rather now a DL145 G3).
RN> I remember seing something like that on a DL380, though.
RN> telnet gives a weird prompt /./ that has no help and only
RN> responds with command errors. T
Sorry, I can't make it work. For a DL140 G3 (or rather now a DL145 G3).
I remember seing something like that on a DL380, though.
telnet gives a weird prompt /./ that has no help and only
responds with command errors. There is also a HTTP server running
at the address. But not ssh.
On Sat, Apr
Darth Lists wrote:
Honestly, it blows big-time compared to a
real serial console since it has a more or less useless scroll-back
buffer.
You can ssh in to the ILO IP address and get console redirection. You
can even redirect the serial console to the ILO ssh after POST if you want.
No. Basic 80x25 console redirection is free. You only need to pay
for the graphical interface bit. Honestly, it blows big-time
compared to a real serial console since it has a more or less useless
scroll-back buffer. I have only ever used the iLO console for the
initial installation pro
Thank you everybody for your valuable answers.
Could you give me some pointers on how to use "the
redirected console via iLO (ESC+Q)". HP documentation is
a mess. All they want is to sell me a license for some
Windoze application for remote management.
Do I need a license for LO 100i something?
A
> So what is the best way to deal with this? Disabling both axe and
> uberry, or disabling usb (I do not want to do that). For axe
> it loops failing something like
> axe0: read PHY failed
> axe0: read PHY failed
> axe0: read PHY failed
> axe0: read PHY failed
> axe0:
On Thu, Apr 26, 2007 at 12:53:16PM +0200, Reyk Floeter wrote:
> hi!
>
> On Thu, Apr 26, 2007 at 12:23:58PM +0200, Raimo Niskanen wrote:
> > I have a HP ProLiant DL140 G3 coming in soon, that I really would
> > like to run OpenBSD 4.1 on. Its predecessor runs OpenBSD (sparc).
> > If I do not succee
On Thu, Apr 26, 2007 at 12:23:58PM +0200, Raimo Niskanen wrote:
> Hi all!
>
> I have a HP ProLiant DL140 G3 coming in soon, that I really would
> like to run OpenBSD 4.1 on. Its predecessor runs OpenBSD (sparc).
> If I do not succeed it will wind up running SLES 10 and that is
> a pity.
>
> I hav
the attach as axe is mostly random, it sometimes attaches as axe(4)
and sometimes as uberry(4) in my DL145 G3...
uberry0 at uhub2 port 2
uberry0: ServerEngines SE USB Device, rev 1.10/0.01, addr 2
uberry0: Charging enabled
And this is caused by a stupid bug in both axe and uberry. Thanks for
po
hi!
On Thu, Apr 26, 2007 at 12:23:58PM +0200, Raimo Niskanen wrote:
> I have a HP ProLiant DL140 G3 coming in soon, that I really would
> like to run OpenBSD 4.1 on. Its predecessor runs OpenBSD (sparc).
> If I do not succeed it will wind up running SLES 10 and that is
> a pity.
>
> I have used a
Hi all!
I have a HP ProLiant DL140 G3 coming in soon, that I really would
like to run OpenBSD 4.1 on. Its predecessor runs OpenBSD (sparc).
If I do not succeed it will wind up running SLES 10 and that is
a pity.
I have used a snapshot of OpenBSD amd64 from April 24.
HP ProLiant DL 140 G2 works l
13 matches
Mail list logo
