Re: : : HP ProLiant DL140 G3 problems
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 machine 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. Ah, maybe, I seem to recall the DL 1xx servers didn't have all the management features The DL1xx are not traditional HP Proliant machines. The onboard remote management card is not a standard HP/Compaq Remote Insight Board, but a generic IPMI management card. GTG
Re: : : HP ProLiant DL140 G3 problems
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 machine 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. Ah, maybe, I seem to recall the DL 1xx servers didn't have all the management features.
Re: : : HP ProLiant DL140 G3 problems
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 machine gives a weird prompt /./ that has no help and only RN responds with command errors. There is also a HTTP server running RN at the address. But not ssh. RN On Sat, Apr 28, 2007 at 10:46:45PM -0400, Steve Shockley wrote: 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. I believe you need at least iLO Select license to activate ssh and ssl, and DL100/DL300 are coming by default with just iLO Standard. BTW, why don't you call HP and ask them these questions? -- Best regards, Borismailto:[EMAIL PROTECTED]
Re: : HP ProLiant DL140 G3 problems
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 process and the occasional visit to the ddb prompt when 3.7 crashed. That said, when I installed OpenBSD on my machines here, I needed to netboot them since the cd and floppy redirection thing was not working too well. It's better than nothing, that's for sure, but I would take a serial console over that any day of the week. Cheers, /Jason On Apr 27, 2007, at 6:02 AM, Raimo Niskanen wrote: 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? And what is (ESC+Q)? 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 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 like a charm with OpenBSD 4.0. The problems: i have seen similar problems on the DL145 G3 with OpenBSD 4.0 and OpenBSD 4.1. 1) something with keyboard interrupts. When booting with a PS2 or USB keyboard attached BIOS, CDBOOT and boot(8) works fine, but the kernel gets no keyboard. using boot boot cd0a:/4.1/amd64/bsd.rd -c gives an UKC promt but does not respond to keystrokes. First changing the console using boot set tty com0 and then boot boot cd0a:/4.1/amd64/bsd.rd -c gives a serial console that is usable. The dmsg is attached ukc works fine for me but the final system keyboard doesn't work. the redirected console via iLO (ESC+Q) works without problems, i didn't try the serial console. 2) something with internal USB devices. The axe(4) driver mistakes something in the server for an USB network card and fails to configure it. Therefore the disabling of the axe device in the following dmsg output. I can live without an axe device so this is not a big problem. it is not an axe device, it is some internal serverworks virtual stuff (and i don't need it). the interesting thing is that it reports an empty device and vendor id (see last line) which is not handled correctly in the usb stack: Controller /dev/usb2: addr 1: full speed, self powered, config 1, OHCI root hub(0x), ServerWorks(0x1166), rev 1.00 port 1 powered port 2 addr 2: full speed, power 100 mA, unconfigured, SE USB Device(0x), ServerEngines(0x), rev 0.01 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 At the end of the dmsg there is something concerning keyboard interrupts. What can I do about it? we need to fix this ;) reyk -- / Raimo Niskanen, Erlang/OTP, Ericsson AB
Re: : HP ProLiant DL140 G3 problems
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? And what is (ESC+Q)? 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 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 like a charm with OpenBSD 4.0. The problems: i have seen similar problems on the DL145 G3 with OpenBSD 4.0 and OpenBSD 4.1. 1) something with keyboard interrupts. When booting with a PS2 or USB keyboard attached BIOS, CDBOOT and boot(8) works fine, but the kernel gets no keyboard. using boot boot cd0a:/4.1/amd64/bsd.rd -c gives an UKC promt but does not respond to keystrokes. First changing the console using boot set tty com0 and then boot boot cd0a:/4.1/amd64/bsd.rd -c gives a serial console that is usable. The dmsg is attached ukc works fine for me but the final system keyboard doesn't work. the redirected console via iLO (ESC+Q) works without problems, i didn't try the serial console. 2) something with internal USB devices. The axe(4) driver mistakes something in the server for an USB network card and fails to configure it. Therefore the disabling of the axe device in the following dmsg output. I can live without an axe device so this is not a big problem. it is not an axe device, it is some internal serverworks virtual stuff (and i don't need it). the interesting thing is that it reports an empty device and vendor id (see last line) which is not handled correctly in the usb stack: Controller /dev/usb2: addr 1: full speed, self powered, config 1, OHCI root hub(0x), ServerWorks(0x1166), rev 1.00 port 1 powered port 2 addr 2: full speed, power 100 mA, unconfigured, SE USB Device(0x), ServerEngines(0x), rev 0.01 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 At the end of the dmsg there is something concerning keyboard interrupts. What can I do about it? we need to fix this ;) reyk -- / Raimo Niskanen, Erlang/OTP, Ericsson AB
HP ProLiant DL140 G3 problems
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 like a charm with OpenBSD 4.0. The problems: 1) something with keyboard interrupts. When booting with a PS2 or USB keyboard attached BIOS, CDBOOT and boot(8) works fine, but the kernel gets no keyboard. using boot boot cd0a:/4.1/amd64/bsd.rd -c gives an UKC promt but does not respond to keystrokes. First changing the console using boot set tty com0 and then boot boot cd0a:/4.1/amd64/bsd.rd -c gives a serial console that is usable. The dmsg is attached 2) something with internal USB devices. The axe(4) driver mistakes something in the server for an USB network card and fails to configure it. Therefore the disabling of the axe device in the following dmsg output. I can live without an axe device so this is not a big problem. At the end of the dmsg there is something concerning keyboard interrupts. What can I do about it? -- / Raimo Niskanen, Erlang/OTP, Ericsson AB [demime 1.01d removed an attachment of type application/octet-stream]
Re: HP ProLiant DL140 G3 problems
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 snapshot of OpenBSD amd64 from April 24. HP ProLiant DL 140 G2 works like a charm with OpenBSD 4.0. The problems: i have seen similar problems on the DL145 G3 with OpenBSD 4.0 and OpenBSD 4.1. 1) something with keyboard interrupts. When booting with a PS2 or USB keyboard attached BIOS, CDBOOT and boot(8) works fine, but the kernel gets no keyboard. using boot boot cd0a:/4.1/amd64/bsd.rd -c gives an UKC promt but does not respond to keystrokes. First changing the console using boot set tty com0 and then boot boot cd0a:/4.1/amd64/bsd.rd -c gives a serial console that is usable. The dmsg is attached ukc works fine for me but the final system keyboard doesn't work. the redirected console via iLO (ESC+Q) works without problems, i didn't try the serial console. 2) something with internal USB devices. The axe(4) driver mistakes something in the server for an USB network card and fails to configure it. Therefore the disabling of the axe device in the following dmsg output. I can live without an axe device so this is not a big problem. it is not an axe device, it is some internal serverworks virtual stuff (and i don't need it). the interesting thing is that it reports an empty device and vendor id (see last line) which is not handled correctly in the usb stack: Controller /dev/usb2: addr 1: full speed, self powered, config 1, OHCI root hub(0x), ServerWorks(0x1166), rev 1.00 port 1 powered port 2 addr 2: full speed, power 100 mA, unconfigured, SE USB Device(0x), ServerEngines(0x), rev 0.01 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 At the end of the dmsg there is something concerning keyboard interrupts. What can I do about it? we need to fix this ;) reyk
Re: HP ProLiant DL140 G3 problems
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 pointing this out, I'll fix this later today. Miod
Re: HP ProLiant DL140 G3 problems
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 have used a snapshot of OpenBSD amd64 from April 24. HP ProLiant DL 140 G2 works like a charm with OpenBSD 4.0. The problems: 1) something with keyboard interrupts. When booting with a PS2 or USB keyboard attached BIOS, CDBOOT and boot(8) works fine, but the kernel gets no keyboard. using boot boot cd0a:/4.1/amd64/bsd.rd -c gives an UKC promt but does not respond to keystrokes. First changing the console using boot set tty com0 and then boot boot cd0a:/4.1/amd64/bsd.rd -c gives a serial console that is usable. The dmsg is attached 2) something with internal USB devices. The axe(4) driver mistakes something in the server for an USB network card and fails to configure it. Therefore the disabling of the axe device in the following dmsg output. I can live without an axe device so this is not a big problem. At the end of the dmsg there is something concerning keyboard interrupts. What can I do about it? -- / Raimo Niskanen, Erlang/OTP, Ericsson AB [demime 1.01d removed an attachment of type application/octet-stream] And here comes the dmsg: OpenBSD/amd64 CDBOOT 1.08 boot boot cd0a:/4.1/amd64/bsd.rd -c booting cd0a:/4.1/amd64/bsd.rd: 2186912+443055+2277312+0+331664 [80+224880+13881 8]=0x958f94 entry point at 0x1001e0 [7205c766, 3404, 24448b12, 9880aCopyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2007 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 4.1-current (RAMDISK_CD) #1091: Tue Apr 24 04:34:18 MDT 2007 [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/RAMDISK_CD real mem = 2146086912 (2095788K) avail mem = 1835941888 (1792912K) using 22937 buffers containing 214814720 bytes (209780K) of memory User Kernel Config UKC help command argsdescription add dev add a device base 8|10|16 base on large numbers changedevno|dev change devices disable attr val|devno|dev disable devices enableattr val|devno|dev enable devices exit leave UKC find devno|dev find devices help this message list list configuration lines [count] number of lines before more quit leave UKC show [attr [val]]show attributes (or devices with an attribute) timezone [mins [dst]]set timezone/dst verbose toggle verbose booting ? this message UKC find axe 127 axe* at uhub*|uhub* port -1 configuration -1 interface -1 vendor -1 product -1 release -1 flags 0x0 UKC disable axe 127 axe* disabled UKC quit Continuing... mainbus0 (root) acpi at mainbus0 not configured cpu0 at mainbus0: (uniprocessor) cpu0: Intel(R) Xeon(R) CPU 5110 @ 1.60GHz, 1596.15 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CF LUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,TM2,CX16,xTPR ,NXE,LONG cpu0: 4MB 64b/line 16-way L2 cache pci0 at mainbus0 bus 0: configuration mode 1 pchb0 at pci0 dev 0 function 0 Intel 5000X Host rev 0x13 ppb0 at pci0 dev 2 function 0 Intel 5000 PCIE rev 0x13 pci1 at ppb0 bus 1 ppb1 at pci1 dev 0 function 0 Intel 6321ESB PCIE rev 0x01 pci2 at ppb1 bus 2 ppb2 at pci2 dev 0 function 0 Intel 6321ESB PCIE rev 0x01 pci3 at ppb2 bus 3 ppb3 at pci1 dev 0 function 3 Intel 6321ESB PCIE-PCIX rev 0x01 pci4 at ppb3 bus 5 ppb4 at pci0 dev 3 function 0 Intel 5000 PCIE rev 0x13 pci5 at ppb4 bus 6 ppb5 at pci0 dev 4 function 0 Intel 5000X PCIE rev 0x13 pci6 at ppb5 bus 8 ppb6 at pci0 dev 5 function 0 Intel 5000 PCIE rev 0x13 pci7 at ppb6 bus 9 ppb7 at pci0 dev 6 function 0 Intel 5000 PCIE rev 0x13 pci8 at ppb7 bus 10 ppb8 at pci0 dev 7 function 0 Intel 5000 PCIE rev 0x13 pci9 at ppb8 bus 11 pchb1 at pci0 dev 16 function 0 Intel 5000 Error Reporting rev 0x13 pchb2 at pci0 dev 16 function 1 Intel 5000 Error Reporting rev 0x13 pchb3 at pci0 dev 16 function 2 Intel 5000 Error Reporting rev 0x13 pchb4 at pci0 dev 17 function 0 Intel 5000 Reserved rev 0x13 pchb5 at pci0 dev 19 function 0 Intel 5000 Reserved rev 0x13 pchb6 at pci0 dev 21 function 0 Intel 5000 FBD rev 0x13 pchb7 at pci0 dev 22 function 0 Intel 5000 FBD rev 0x13 ppb9 at pci0 dev 28 function 0 Intel 6321ESB PCIE rev 0x09 pci10 at ppb9 bus 14 bge0 at pci10 dev 0 function 0 Broadcom BCM5721 rev 0x11, BCM5750 B1 (0x4101): irq 11, address 00:18:fe:28:de:62 brgphy0 at bge0 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0 ppb10 at pci0 dev 28 function 1 Intel 6321ESB PCIE rev 0x09 pci11 at ppb10 bus 15 bge1 at pci11 dev
Re: : HP ProLiant DL140 G3 problems
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 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 like a charm with OpenBSD 4.0. The problems: i have seen similar problems on the DL145 G3 with OpenBSD 4.0 and OpenBSD 4.1. 1) something with keyboard interrupts. When booting with a PS2 or USB keyboard attached BIOS, CDBOOT and boot(8) works fine, but the kernel gets no keyboard. using boot boot cd0a:/4.1/amd64/bsd.rd -c gives an UKC promt but does not respond to keystrokes. First changing the console using boot set tty com0 and then boot boot cd0a:/4.1/amd64/bsd.rd -c gives a serial console that is usable. The dmsg is attached ukc works fine for me but the final system keyboard doesn't work. the redirected console via iLO (ESC+Q) works without problems, i didn't try the serial console. 2) something with internal USB devices. The axe(4) driver mistakes something in the server for an USB network card and fails to configure it. Therefore the disabling of the axe device in the following dmsg output. I can live without an axe device so this is not a big problem. it is not an axe device, it is some internal serverworks virtual stuff (and i don't need it). the interesting thing is that it reports an empty device and vendor id (see last line) which is not handled correctly in the usb stack: Controller /dev/usb2: addr 1: full speed, self powered, config 1, OHCI root hub(0x), ServerWorks(0x1166), rev 1.00 port 1 powered port 2 addr 2: full speed, power 100 mA, unconfigured, SE USB Device(0x), ServerEngines(0x), rev 0.01 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 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: read PHY failed until the kernel panics out of memory. At the end of the dmsg there is something concerning keyboard interrupts. What can I do about it? we need to fix this ;) Is there no kernel configuration that can be tweaked to make it limp. I can use always serial console but it is not that appealing. reyk -- / Raimo Niskanen, Erlang/OTP, Ericsson AB
Re: : HP ProLiant DL140 G3 problems
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: read PHY failed until the kernel panics out of memory. http://www.archivesat.com/OpenBSD_Miscellaneous_topics/thread2719139.htm
