From owner-freebsd-proliant@FreeBSD.ORG Thu Mar 22 14:33:56 2012 Return-Path: Delivered-To: freebsd-proliant@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 81FBB1065670 for ; Thu, 22 Mar 2012 14:33:56 +0000 (UTC) (envelope-from MCVenner@Copar.com) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id 5C6938FC1C for ; Thu, 22 Mar 2012 14:33:56 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1SAj5P-0000UT-QM for freebsd-proliant@freebsd.org; Thu, 22 Mar 2012 07:33:55 -0700 Date: Thu, 22 Mar 2012 07:33:55 -0700 (PDT) From: MCVenner To: freebsd-proliant@freebsd.org Message-ID: <1332426835810-5586073.post@n5.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Keyboard Curiosity X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion of FreeBSD on HP ProLiant server platforms." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2012 14:33:56 -0000 I have an HP ProLiant ML110 G6 Server on which I've installed and configured FreeBSD v7.4-RELEASE. Though the computer auto-boots uneventfully, I have never been able to interact with the boot loader as no keyboard action is, while it's resident, recognized. I have tried a number of different keyboards (101-key, 102-key, 104-key; PS/2, USB; with and without interface adapters) without result. I find that if I attempt, continuously while booting, to toggle (for example) the CapsLock key that there is a period during the boot process where the associated CapsLock LED ceases toggling in response. The period begins at the moment the boot manager's boot-slice selection is satisfied (either via user action or timeout). The period ends midway through the loading of the kernel; perhaps as early as status message ... kernel: kbd2 at ukbd0 but, certainly, no later than status message ... kernel: sc09: at flags 0x100 on isa0 though it's difficult to discern as they go by quickly. Any suggestions as to how this might be resolved would be appreciated. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Keyboard-Curiosity-tp5586073p5586073.html Sent from the freebsd-proliant mailing list archive at Nabble.com. From owner-freebsd-proliant@FreeBSD.ORG Thu Mar 22 14:49:32 2012 Return-Path: Delivered-To: freebsd-proliant@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1AC38106566B for ; Thu, 22 Mar 2012 14:49:32 +0000 (UTC) (envelope-from mladen.lazarevic@hp.com) Received: from g1t0026.austin.hp.com (g1t0026.austin.hp.com [15.216.28.33]) by mx1.freebsd.org (Postfix) with ESMTP id D5B0F8FC19 for ; Thu, 22 Mar 2012 14:49:31 +0000 (UTC) Received: from G9W0369G.americas.hpqcorp.net (g9w0369g.houston.hp.com [16.216.193.232]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by g1t0026.austin.hp.com (Postfix) with ESMTPS id D7746C677; Thu, 22 Mar 2012 14:49:24 +0000 (UTC) Received: from G9W0366G.americas.hpqcorp.net (16.216.193.230) by G9W0369G.americas.hpqcorp.net (16.216.193.232) with Microsoft SMTP Server (TLS) id 14.1.289.1; Thu, 22 Mar 2012 14:48:19 +0000 Received: from G9W0723.americas.hpqcorp.net ([169.254.3.9]) by G9W0366G.americas.hpqcorp.net ([16.216.193.230]) with mapi id 14.01.0289.001; Thu, 22 Mar 2012 14:48:19 +0000 From: "Lazarevic Komac, Mladen" To: MCVenner Thread-Topic: Keyboard Curiosity Thread-Index: AQHNCDkYM4eYifyMcUCiosJhXhPQlpZ2Yw0w Date: Thu, 22 Mar 2012 14:48:18 +0000 Message-ID: <967B1D6B76D0F34092FDD44E3B14D6155A9C83E9@G9W0723.americas.hpqcorp.net> References: <1332426835810-5586073.post@n5.nabble.com> In-Reply-To: <1332426835810-5586073.post@n5.nabble.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [16.216.12.11] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-proliant@freebsd.org" Subject: RE: Keyboard Curiosity X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion of FreeBSD on HP ProLiant server platforms." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2012 14:49:32 -0000 Try to log into server via ILO port / web gui or via telnet/ then to use iL= O to get on server when it is booting ... User guide for iLO 2 you can find on location: http://bizsupport1.austin.hp= .com/bc/docs/support/SupportManual/c02845760/c02845760.pdf (Page 95 of 224) Text-based remote console overview iLO and its predecessors support a true text-based remote console. Video in= formation is obtained from the server and the contents of the video memory are sent to the manage= ment processor, compressed, encrypted, and forwarded to the management client application. = iLO uses a screen-frame buffer, which detects changes in text information, encrypts th= e changes, and sends the characters (including screen positioning information) to text-based cli= ent applications. This method provides compatibility with standard text-based clients, good perfor= mance, and simplicity. However, you cannot display non-ASCII or graphical information, and screen = positioning information (displayed characters) might be sent out of order. The Remote Console uses Virtual KVM and does not provide a true text-based = console. iLO 2 uses the video adapter DVO port to access video memory directly. This method sig= nificantly increases iLO 2 performance. However, the digital video stream does not contain usefu= l text data. Data obtained from the DVO port represents graphical data (non-character-based),= and is not comprehensible ASCII or text data. This video data cannot be rendered by a = text-based client application such as Telnet or SSH. Text-based console during POST The standard iLO 2 text-based remote console remains available on iLO 2 unt= il the operating system POST is complete. iLO 2 standard firmware continues to use the virtualized = serial-port functionality of the management processor. On the iLO 2 firmware, the virtual serial port= was renamed Remote Serial Console. iLO 2 uses the Remote Serial Console to access a pre-operat= ing system, text-based iLO 2 Remote Console 95 remote console. The iLO 2 Remote Serial Console applet appears as a text-ba= sed console, but the information is rendered using graphical video data. iLO 2 displays this inf= ormation through the remote console applet while in the server pre-operating system state, enabl= ing a non-licensed iLO 2 to observe and interact with the server during POST activities. For an iLO 2 blade (and an iLO blade running Linux in a graphical format), = enter getty() on the server's serial port, and then use iLO 2 Remote Serial Console or iLO V= irtual Serial Port (CLP command start /system1/oemhp_vsp1) to view a login session to the Linux ope= rating system through the serial port. A non-licensed iLO 2 cannot use Remote Console access after the server comp= letes POST and begins to load the operating system. To use Remote Console and iLO Text Con= sole after POST, you must have an iLO 2 Advanced or iLO 2 Advanced for BladeSystem. BR. Mladen ... -----Original Message----- From: owner-freebsd-proliant@freebsd.org [mailto:owner-freebsd-proliant@fre= ebsd.org] On Behalf Of MCVenner Sent: 22. marec 2012 15:34 To: freebsd-proliant@freebsd.org Subject: Keyboard Curiosity I have an HP ProLiant ML110 G6 Server on which I've installed and configure= d FreeBSD v7.4-RELEASE. Though the computer auto-boots uneventfully, I have never been able to inte= ract with the boot loader as no keyboard action is, while it's resident, re= cognized. I have tried a number of different keyboards (101-key, 102-key, 104-key; PS= /2, USB; with and without interface adapters) without result. I find that if I attempt, continuously while booting, to toggle (for example) the CapsLock key that there is a period during the boot process wh= ere the associated CapsLock LED ceases toggling in response. The period begins at the moment the boot manager's boot-slice selection is = satisfied (either via user action or timeout). The period ends midway through the loading of the kernel; perhaps as early= as status message ... kernel: kbd2 at ukbd0 but, certainly, no later than status message ... kernel: sc09: at flags 0x100 on isa0 though it's d= ifficult to discern as they go by quickly. Any suggestions as to how this might be resolved would be appreciated. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Keyboard= -Curiosity-tp5586073p5586073.html Sent from the freebsd-proliant mailing list archive at Nabble.com. _______________________________________________ freebsd-proliant@freebsd.org mailing list http://lists.freebsd.org/mailman/= listinfo/freebsd-proliant To unsubscribe, send any mail to "freebsd-proliant-unsubscribe@freebsd.org" From owner-freebsd-proliant@FreeBSD.ORG Thu Mar 22 18:05:05 2012 Return-Path: Delivered-To: freebsd-proliant@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 957D01065670 for ; Thu, 22 Mar 2012 18:05:05 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: from mail.ultra-secure.de (mail.ultra-secure.de [78.47.114.122]) by mx1.freebsd.org (Postfix) with ESMTP id C9E9E8FC1C for ; Thu, 22 Mar 2012 18:05:04 +0000 (UTC) Received: (qmail 80791 invoked by uid 89); 22 Mar 2012 17:02:43 -0000 Received: by simscan 1.4.0 ppid: 80786, pid: 80788, t: 0.0419s scanners: attach: 1.4.0 clamav: 0.97.3/m:54/d:14685 Received: from unknown (HELO suse2.iptech.internal) (rainer@ultra-secure.de@212.71.117.70) by mail.ultra-secure.de with ESMTPA; 22 Mar 2012 17:02:43 -0000 Date: Thu, 22 Mar 2012 19:02:44 +0100 From: Rainer Duffner To: freebsd-proliant@freebsd.org Message-ID: <20120322190244.51faf4f2@suse2.iptech.internal> In-Reply-To: References: X-Mailer: Claws Mail 3.7.10 (GTK+ 2.22.1; x86_64-unknown-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: ProLiant DL380 G7 X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion of FreeBSD on HP ProLiant server platforms." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2012 18:05:05 -0000 Am Wed, 31 Aug 2011 20:22:23 +0400 schrieb Andrej Zverev : > Hello guys. > > Does someone has success with installing FreeBSD 8.2 or 9.0BETA via > iLO? All my attempts failed. > cd0: Removable CD-ROM SCSI-0 device > cd0: 40.000MB/s transfers > cd0: cd present [310822 x 2048 x bytes records] > Mounting from cd9660:/dev/iso9660/FREEBSD_INSTALL failed with error > 19. > > and after I'm always inside mountroot which don't show any devices > except da0 which is raid controller. Hi, we installed 8.2 on an internal USB stick (via a 2nd, external USB stick...) It couldn't boot afterwards, but we added kern.cam.boot_delay=25000 to /boot/loader.conf (set kern.cam.boot_delay=25000 on loader prompt on first boot). 10000 or 15000 delay was not enough sometimes. I tried to boot 9.0 via virtual CD but did not succeed. Hopefully, it will boot once upgraded to 9.0 .... The incentive to boot this system as seldom as possible is certainly there. Rainer From owner-freebsd-proliant@FreeBSD.ORG Thu Mar 22 18:16:44 2012 Return-Path: Delivered-To: freebsd-proliant@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 38E09106566C for ; Thu, 22 Mar 2012 18:16:44 +0000 (UTC) (envelope-from MCVenner@Copar.com) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id 10DBD8FC0A for ; Thu, 22 Mar 2012 18:16:43 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1SAmZ0-0003nm-US for freebsd-proliant@freebsd.org; Thu, 22 Mar 2012 11:16:42 -0700 Date: Thu, 22 Mar 2012 11:16:42 -0700 (PDT) From: MCVenner To: freebsd-proliant@freebsd.org Message-ID: <1332440202914-5587436.post@n5.nabble.com> In-Reply-To: <967B1D6B76D0F34092FDD44E3B14D6155A9C83E9@G9W0723.americas.hpqcorp.net> References: <1332426835810-5586073.post@n5.nabble.com> <967B1D6B76D0F34092FDD44E3B14D6155A9C83E9@G9W0723.americas.hpqcorp.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: RE: Keyboard Curiosity X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion of FreeBSD on HP ProLiant server platforms." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2012 18:16:44 -0000 While I was aware of the existence of the management port, I'd regarded it a daunting distraction (ref. "IPMI", "BMC", "ILO", and a 224-page manual to explain it all). Your suggestion inspired me to revisit the thing, if only for a brief while. At least the enabling and disabling of my keyboard (the original problem) is repeatable. A constant background pinging of my computer's management port showed it to go on and off network for no apparent reason. During the periods it was active, an HTML client afforded nothing more than a "settings" interface and a Telnet client never yielded anything more than a "/./->" prompt (though for what I do not know). The only thing that seemed remotely consistent was that the interface would go down a soon as the kernel began loading. If there is truly light at the end of this tunnel then, I'm afraid, I just cannot see it right now. Thanks, though, for replying. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Keyboard-Curiosity-tp5586073p5587436.html Sent from the freebsd-proliant mailing list archive at Nabble.com. From owner-freebsd-proliant@FreeBSD.ORG Thu Mar 22 20:35:21 2012 Return-Path: Delivered-To: freebsd-proliant@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3CFB2106564A for ; Thu, 22 Mar 2012 20:35:21 +0000 (UTC) (envelope-from info@oems.ch) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id 0E0548FC17 for ; Thu, 22 Mar 2012 20:35:20 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1SAoj9-0001bR-R2 for freebsd-proliant@freebsd.org; Thu, 22 Mar 2012 13:35:19 -0700 Date: Thu, 22 Mar 2012 13:35:19 -0700 (PDT) From: salster420 To: freebsd-proliant@freebsd.org Message-ID: <456C255154B846479966A0DAC9490AC6@OEMSPC01> In-Reply-To: <1332426835810-5586073.post@n5.nabble.com> References: <1332426835810-5586073.post@n5.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Keyboard Curiosity X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion of FreeBSD on HP ProLiant server platforms." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2012 20:35:21 -0000 ----- Original Message ----- From: MCVenner [via FreeBSD] To: salster420 Sent: Thursday, March 22, 2012 3:33 PM Subject: Keyboard Curiosity I have an HP ProLiant ML110 G6 Server on which I've installed and configured FreeBSD v7.4-RELEASE. Though the computer auto-boots uneventfully, I have never been able to interact with the boot loader as no keyboard action is, while it's resident, recognized. I have tried a number of different keyboards (101-key, 102-key, 104-key; PS/2, USB; with and without interface adapters) without result. I find that if I attempt, continuously while booting, to toggle (for example) the CapsLock key that there is a period during the boot process where the associated CapsLock LED ceases toggling in response. The period begins at the moment the boot manager's boot-slice selection is satisfied (either via user action or timeout). The period ends midway through the loading of the kernel; perhaps as early as status message ... kernel: kbd2 at ukbd0 but, certainly, no later than status message ... kernel: sc09: at flags 0x100 on isa0 though it's difficult to discern as they go by quickly. Any suggestions as to how this might be resolved would be appreciated. If you reply to this email, your message will be added to the discussion below: http://freebsd.1045724.n5.nabble.com/Keyboard-Curiosity-tp5586073p5586073.html To start a new topic under freebsd-proliant, email ml-node+s1045724n4251986h59@n5.nabble.com To unsubscribe from freebsd-proliant, click here. NAML Greetings, I had some issuses with this and found out that with this system is was a little buggy, Until,after making the RAID volume with the E200i controller, you needed for the system to finish with building the volume. After it seemed to install FreeBSD and Work correctly. You have to let this system stay on for about 4 hours and then reboot and check the status of the RAID controller, ADU Report 1. if the battery is charged 2. Most important the RAID is done building. or else it really makes this crazy stuff [DeviceStatusSmart Array E200 in slot 4 The cache is temporarily disabled Logical Drive 1 Background parity initialization is currently queued or in progress on this logical drive. If background parity initialization is queued, it will start when I/O is performed on the drive. When background parity initialization completes, the performance of the logical drive will improve.] WOuld boot with not keyboard at worse, not instal all the packages. 3. you need to update the SYSTEM BIOS / and BMC as well as the controller BIOS. Let me know more about the HW details from the HP Survey. then I can check it with the two Testing Proliant ML110's I have here in the Lab. ----- Salster420 Ticino FreeBSD Advocacy -- View this message in context: http://freebsd.1045724.n5.nabble.com/Keyboard-Curiosity-tp5586073p5587731.html Sent from the freebsd-proliant mailing list archive at Nabble.com.