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(0x0000), > ServerWorks(0x1166), rev 1.00 > port 1 powered > port 2 addr 2: full speed, power 100 mA, unconfigured, SE USB > Device(0x0000), ServerEngines(0x0000), 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
