From owner-freebsd-proliant@FreeBSD.ORG Mon Jul 28 19:35:24 2008 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 383F7106566C for ; Mon, 28 Jul 2008 19:35:24 +0000 (UTC) (envelope-from mahlerrd@yahoo.com) Received: from web51011.mail.re2.yahoo.com (web51011.mail.re2.yahoo.com [206.190.39.154]) by mx1.freebsd.org (Postfix) with SMTP id CBF1B8FC16 for ; Mon, 28 Jul 2008 19:35:23 +0000 (UTC) (envelope-from mahlerrd@yahoo.com) Received: (qmail 95183 invoked by uid 60001); 28 Jul 2008 19:35:23 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Message-ID; b=1Y5QznfnHVKyUIAOzxZVIqzzPyQd4WfaFdlbke3xRBsWilpNHTPUUrSIO1AeRqd42tfq5KQ5Oz28KyMJPdmfOZoVJR55h4BTIErK1jaZXfi1NUzE/AaF7NWsPRuN1XGmLKLZCoXRc94vBEZLsEeZk7YUsezgZClp4bnABRc/ilc=; Received: from [74.43.179.2] by web51011.mail.re2.yahoo.com via HTTP; Mon, 28 Jul 2008 12:35:22 PDT X-Mailer: YahooMailWebService/0.7.218 Date: Mon, 28 Jul 2008 12:35:22 -0700 (PDT) From: Richard Mahlerwein To: freebsd-proliant@freebsd.org MIME-Version: 1.0 Message-ID: <282583.95073.qm@web51011.mail.re2.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: ML370 (G1), boot options X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mahlerrd@yahoo.com 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: Mon, 28 Jul 2008 19:35:24 -0000 Please ignore cruft at the end - I apparently forgot to finish deleting my = first draft of this message.=A0 Boy, do I hope it doesn't outright contradi= ct anything in my "real" message. :) Rich Mahlerwein mahlerrd@yahoo.com Mobile: 715-891-7420 --- On Mon, 7/28/08, Richard Mahlerwein wrote: From: Richard Mahlerwein Subject: ML370 (G1), boot options To: freebsd-proliant@freebsd.org Date: Monday, July 28, 2008, 3:21 PM Hi, all.=A0 I've searched the archives as best I can, and also consulted th= e Great Oracle of Google, but seem to be getting nowhere in a little projec= t I'm doing. I know it's not always good form to include more than one problem in a post= , so I apologize in advance, but since answering one of the three questions= may mean the other two no longer need an answer, I feel it's appropriate i= n this case. I recently retrieved a ML370 G1 off the to-be-recycled heap here at work.= =A0 It'll replace my aging 550 MHz PIII single-processor PC I've had presse= d into "server" duty for ages.=A0 The ML370 is in fine physical order and i= s a Dual PIII 866 with a Smart Array 3200 in it, 2x 36 GB drives and 4x 18 = GB.=A0 I have downloaded and used a SmartStart 5.5 CD to verify all seems w= ell and to reconfigure the RAID to my needs. Issue 1: During my first attempt at installing FreeBSD 7.0, I found I couldn't boot from the = CD.=A0 No problem, I thought, I'll just create the floppies and do a net in= stall from there - I was sure it was just a Old CD Drive + Burnt CD =3D no = booting. I created boot.flp and kern.flp figuring if I needed more floppies= out of the set I'll keep overwriting those two.=A0 (I'm slowly running out= of good floppies!) =A0 I wasn't paying that close of attention, but I real= ized about mid-way through the install the system never asked me for the ke= rnel floppy.=A0 I was a bit puzzled, but figured maybe the boot floppy saw = the CD and passed control to it... Q1: Does anyone know what likely happened there?=A0 I *DID* at least start = the boot from the floppy, I remember seeing that little piece, but afterwar= ds, it was magic...=A0 Will the boot floppy hand off to the CD if/when it s= ees it? Issue 2: The install went fine, the only real issue is in the obnoxiously loud and bothersome fan noise.=A0 Options don't seem to be in = the BIOS (?!?) but I found the FreeBSD Tools for ProLiant page (http://peop= le.freebsd.org/~jcagle/) and thought "Perfect!"=A0 I noticed it had images = for 4.x, 5.x and 6.2.=A0 No 7.0...=A0 Since I had 7.0 already installed, I = tried winging it and and installing the various pieces for 6.2 and doing ld= config and installing compat layers and whatnot, but I couldn't quite get i= t working.=A0=20 Q2: Does anyone have some reasonably easy to follow docs on making at least= hpasm work on 7.0?=A0 I've seen a few vague references to it working after= an upgrade from 6.x to 7, but docs are surprisingly sparse AFAICT. Issue 3: So I thought to install 6.3, which I guess will very likely work u= sing the 6.2 build of hpasm.=A0 I changed my boot disk to a 6.3 one, stuck = it in the floppy drive and booted, but the system happily and without quest= ion booted from the hard drives.=A0 Tonight I hope to find time to do a 6.3 CD + a 6.3 boot floppy = and see if I can get it up that way, but I'd love to find out what may be g= oing on with this.=A0 I don't think that will work, because I think it was = only booting from CD/Floppy *after* the hard drive boot failed.=A0 I don't = really want to delete the arrays so it will fail back over to floppy bootin= g, but at this point I'd try it if there's no easy way.=A0 But, I'm *positi= ve* there's an easier way...=20 Q3: How do you change the boot order to include the floppy disk?=A0=20 I would appreciate any help someone can give or pointers to other informati= on for me to try proceeding on my own. Many thanks, Rich I tried winging it and doing the 7.0 and addressing issues as they came up = (which involved a few hoops with compat_6x, _5x and ldconfig, I think), but= I never quite got it going.=A0 I'm thinking about starting over with 6.3, = which I believe I will have a much, much greater chance to get working. 7.0 was a bear to get on it, but only because it wouldn't recognize my burn= t CD as bootable.=A0 I realize now that I never got to kern.flp, though - b= oot.flp was all it took.=A0 I don't know if that's because magically my unb= ootable CD became bootable, or if the bootable floppy figured out there was= a CD there and used it. So I decided reinstalling from 6.3 wouldn't be an issue, except I=20 =A0=20 =A0 Rich Mahlerwein mahlerrd@yahoo.com Mobile: 715-891-7420 From owner-freebsd-proliant@FreeBSD.ORG Mon Jul 28 19:47:50 2008 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 A2E2D1065676 for ; Mon, 28 Jul 2008 19:47:50 +0000 (UTC) (envelope-from mahlerrd@yahoo.com) Received: from web51006.mail.re2.yahoo.com (web51006.mail.re2.yahoo.com [206.190.38.137]) by mx1.freebsd.org (Postfix) with SMTP id 3A9718FC1B for ; Mon, 28 Jul 2008 19:47:50 +0000 (UTC) (envelope-from mahlerrd@yahoo.com) Received: (qmail 44835 invoked by uid 60001); 28 Jul 2008 19:21:08 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Message-ID; b=Ba1WjQ9E1VCqqeAAv+iINevmAGpbJ5QWhO+NEhJ36ml1rj2HavpAtJ+NJiBfPn2fBDpIH4KrsyVFPJliEyzncB/NU5cLLrzLL2JTRXTylAWHbL/+e+HO+R6syr4G22eH9BKMDUk3rho7RmkyCPMtE+CCCd5nx+l6rXbCs4Jbnv4=; Received: from [74.43.179.2] by web51006.mail.re2.yahoo.com via HTTP; Mon, 28 Jul 2008 12:21:08 PDT X-Mailer: YahooMailWebService/0.7.218 Date: Mon, 28 Jul 2008 12:21:08 -0700 (PDT) From: Richard Mahlerwein To: freebsd-proliant@freebsd.org MIME-Version: 1.0 Message-ID: <475559.43160.qm@web51006.mail.re2.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: ML370 (G1), boot options X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mahlerrd@yahoo.com 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: Mon, 28 Jul 2008 19:47:50 -0000 Hi, all.=A0 I've searched the archives as best I can, and also consulted th= e Great Oracle of Google, but seem to be getting nowhere in a little projec= t I'm doing. I know it's not always good form to include more than one problem in a post= , so I apologize in advance, but since answering one of the three questions= may mean the other two no longer need an answer, I feel it's appropriate i= n this case. I recently retrieved a ML370 G1 off the to-be-recycled heap here at work.= =A0 It'll replace my aging 550 MHz PIII single-processor PC I've had presse= d into "server" duty for ages.=A0 The ML370 is in fine physical order and i= s a Dual PIII 866 with a Smart Array 3200 in it, 2x 36 GB drives and 4x 18 = GB.=A0 I have downloaded and used a SmartStart 5.5 CD to verify all seems w= ell and to reconfigure the RAID to my needs. Issue 1: During my first attempt at installing FreeBSD 7.0, I found I could= n't boot from the CD.=A0 No problem, I thought, I'll just create the floppi= es and do a net install from there - I was sure it was just a Old CD Drive = + Burnt CD =3D no booting. I created boot.flp and kern.flp figuring if I ne= eded more floppies out of the set I'll keep overwriting those two.=A0 (I'm = slowly running out of good floppies!) =A0 I wasn't paying that close of att= ention, but I realized about mid-way through the install the system never a= sked me for the kernel floppy.=A0 I was a bit puzzled, but figured maybe th= e boot floppy saw the CD and passed control to it... Q1: Does anyone know what likely happened there?=A0 I *DID* at least start = the boot from the floppy, I remember seeing that little piece, but afterwar= ds, it was magic...=A0 Will the boot floppy hand off to the CD if/when it s= ees it? Issue 2: The install went fine, the only real issue is in the obnoxiously l= oud and bothersome fan noise.=A0 Options don't seem to be in the BIOS (?!?)= but I found the FreeBSD Tools for ProLiant page (http://people.freebsd.org= /~jcagle/) and thought "Perfect!"=A0 I noticed it had images for 4.x, 5.x a= nd 6.2.=A0 No 7.0...=A0 Since I had 7.0 already installed, I tried winging = it and and installing the various pieces for 6.2 and doing ldconfig and ins= talling compat layers and whatnot, but I couldn't quite get it working.=A0= =20 Q2: Does anyone have some reasonably easy to follow docs on making at least= hpasm work on 7.0?=A0 I've seen a few vague references to it working after= an upgrade from 6.x to 7, but docs are surprisingly sparse AFAICT. Issue 3: So I thought to install 6.3, which I guess will very likely work u= sing the 6.2 build of hpasm.=A0 I changed my boot disk to a 6.3 one, stuck = it in the floppy drive and booted, but the system happily and without quest= ion booted from the hard drives.=A0 Tonight I hope to find time to do a 6.3= CD + a 6.3 boot floppy and see if I can get it up that way, but I'd love t= o find out what may be going on with this.=A0 I don't think that will work,= because I think it was only booting from CD/Floppy *after* the hard drive = boot failed.=A0 I don't really want to delete the arrays so it will fail ba= ck over to floppy booting, but at this point I'd try it if there's no easy = way.=A0 But, I'm *positive* there's an easier way...=20 Q3: How do you change the boot order to include the floppy disk?=A0=20 I would appreciate any help someone can give or pointers to other informati= on for me to try proceeding on my own. Many thanks, Rich I tried winging it and doing the 7.0 and addressing issues as they came up = (which involved a few hoops with compat_6x, _5x and ldconfig, I think), but= I never quite got it going.=A0 I'm thinking about starting over with 6.3, = which I believe I will have a much, much greater chance to get working. 7.0 was a bear to get on it, but only because it wouldn't recognize my burn= t CD as bootable.=A0 I realize now that I never got to kern.flp, though - b= oot.flp was all it took.=A0 I don't know if that's because magically my unb= ootable CD became bootable, or if the bootable floppy figured out there was= a CD there and used it. So I decided reinstalling from 6.3 wouldn't be an issue, except I=20 =A0=20 =A0 Rich Mahlerwein mahlerrd@yahoo.com Mobile: 715-891-7420 From owner-freebsd-proliant@FreeBSD.ORG Tue Jul 29 07:09:16 2008 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 04DF91065676 for ; Tue, 29 Jul 2008 07:09:16 +0000 (UTC) (envelope-from geoff.buckingham@thomsonreuters.com) Received: from VA3EHSOBE002.bigfish.com (outbound-va3.frontbridge.com [216.32.180.16]) by mx1.freebsd.org (Postfix) with ESMTP id A969C8FC1C for ; Tue, 29 Jul 2008 07:09:15 +0000 (UTC) (envelope-from geoff.buckingham@thomsonreuters.com) Received: from mail161-va3-R.bigfish.com (10.7.14.252) by VA3EHSOBE002.bigfish.com (10.7.40.22) with Microsoft SMTP Server id 8.1.240.5; Tue, 29 Jul 2008 06:54:10 +0000 Received: from mail161-va3 (localhost.localdomain [127.0.0.1]) by mail161-va3-R.bigfish.com (Postfix) with ESMTP id 4729A7903B7 for ; Tue, 29 Jul 2008 06:54:10 +0000 (UTC) X-BigFish: VPS-48(zzaf6W542N1a09M9370P8a5S936fQzz10d3izzz2ei6bh41i42k61h) X-Spam-TCS-SCL: 0:0 X-FB-SS: 5, Received: by mail161-va3 (MessageSwitch) id 1217314448288238_2075; Tue, 29 Jul 2008 06:54:08 +0000 (UCT) Received: from lonsmime02.rit.reuters.com (lonsmimeo.rit.reuters.com [192.165.213.23]) by mail161-va3.bigfish.com (Postfix) with ESMTP id 09F0B51005A for ; Tue, 29 Jul 2008 06:54:07 +0000 (UTC) Received: from eupig2 (unverified [129.1.30.40]) by lonsmime02.rit.reuters.com (Content Technologies SMTPRS 4.3.19) with ESMTP id ; Tue, 29 Jul 2008 06:54:08 +0000 Received: from dtcsmsxb01.emea.ime.reuters.com ([10.5.150.13]) by eupig2.dtc.lon.ime.reuters.com (PMDF V6.2-1x10 #31408) with ESMTP id <0K4R00B0V9U78E@eupig2.dtc.lon.ime.reuters.com>; Tue, 29 Jul 2008 06:54:07 +0000 (GMT) Received: from LONSMSXM04.emea.ime.reuters.com ([10.14.113.15]) by dtcsmsxb01.emea.ime.reuters.com with Microsoft SMTPSVC (6.0.3790.1830); Tue, 29 Jul 2008 07:54:07 +0100 Date: Tue, 29 Jul 2008 07:54:06 +0100 From: Geoff Buckingham In-Reply-To: <475559.43160.qm@web51006.mail.re2.yahoo.com> To: mahlerrd@yahoo.com, freebsd-proliant@freebsd.org Message-ID: <8753F8EA457BFF4A9707CADA143C8F68057BB904@LONSMSXM04.emea.ime.reuters.com> MIME-Version: 1.0 X-MIMEOLE: Produced By Microsoft Exchange V6.5 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Thread-Topic: ML370 (G1), boot options thread-index: Acjw6tn+kuHM0UqnTR2uKtdQFHFO7AAXHTMg Content-Class: urn:content-classes:message X-MS-Has-Attach: X-MS-TNEF-Correlator: References: <475559.43160.qm@web51006.mail.re2.yahoo.com> X-OriginalArrivalTime: 29 Jul 2008 06:54:07.0504 (UTC) FILETIME=[E57A7900:01C8F147] Cc: Subject: RE: ML370 (G1), boot options 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: Tue, 29 Jul 2008 07:09:16 -0000 The ML 370 (G1) most likely has the same lack of an interactive embedded BI= OS configuration utility as the DL360 G1 and earlier Compaq Proliants. You = configure boot order and the like form=20 Smart Start or an EISA tools partition you install from smart start.=20 -----Original Message----- From: owner-freebsd-proliant@freebsd.org [mailto:owner-freebsd-proliant@fre= ebsd.org] On Behalf Of Richard Mahlerwein Sent: 28 July 2008 20:21 To: freebsd-proliant@freebsd.org Subject: ML370 (G1), boot options Hi, all.=A0 I've searched the archives as best I can, and also consulted th= e Great Oracle of Google, but seem to be getting nowhere in a little projec= t I'm doing. I know it's not always good form to include more than one problem in a post= , so I apologize in advance, but since answering one of the three questions= may mean the other two no longer need an answer, I feel it's appropriate i= n this case. I recently retrieved a ML370 G1 off the to-be-recycled heap here at work.= =A0 It'll replace my aging 550 MHz PIII single-processor PC I've had presse= d into "server" duty for ages.=A0 The ML370 is in fine physical order and i= s a Dual PIII 866 with a Smart Array 3200 in it, 2x 36 GB drives and 4x 18 = GB.=A0 I have downloaded and used a SmartStart 5.5 CD to verify all seems w= ell and to reconfigure the RAID to my needs. Issue 1: During my first attempt at installing FreeBSD 7.0, I found I could= n't boot from the CD.=A0 No problem, I thought, I'll just create the floppi= es and do a net install from there - I was sure it was just a Old CD Drive = + Burnt CD =3D no booting. I created boot.flp and kern.flp figuring if I ne= eded more floppies out of the set I'll keep overwriting those two.=A0 (I'm = slowly running out of good floppies!) =A0 I wasn't paying that close of att= ention, but I realized about mid-way through the install the system never a= sked me for the kernel floppy.=A0 I was a bit puzzled, but figured maybe th= e boot floppy saw the CD and passed control to it... Q1: Does anyone know what likely happened there?=A0 I *DID* at least start = the boot from the floppy, I remember seeing that little piece, but afterwar= ds, it was magic...=A0 Will the boot floppy hand off to the CD if/when it s= ees it? Issue 2: The install went fine, the only real issue is in the obnoxiously l= oud and bothersome fan noise.=A0 Options don't seem to be in the BIOS (?!?)= but I found the FreeBSD Tools for ProLiant page (http://people.freebsd.org= /~jcagle/) and thought "Perfect!"=A0 I noticed it had images for 4.x, 5.x a= nd 6.2.=A0 No 7.0...=A0 Since I had 7.0 already installed, I tried winging = it and and installing the various pieces for 6.2 and doing ldconfig and ins= talling compat layers and whatnot, but I couldn't quite get it working.=A0= =20 Q2: Does anyone have some reasonably easy to follow docs on making at least= hpasm work on 7.0?=A0 I've seen a few vague references to it working after= an upgrade from 6.x to 7, but docs are surprisingly sparse AFAICT. Issue 3: So I thought to install 6.3, which I guess will very likely work u= sing the 6.2 build of hpasm.=A0 I changed my boot disk to a 6.3 one, stuck = it in the floppy drive and booted, but the system happily and without quest= ion booted from the hard drives.=A0 Tonight I hope to find time to do a 6.3= CD + a 6.3 boot floppy and see if I can get it up that way, but I'd love t= o find out what may be going on with this.=A0 I don't think that will work,= because I think it was only booting from CD/Floppy *after* the hard drive = boot failed.=A0 I don't really want to delete the arrays so it will fail ba= ck over to floppy booting, but at this point I'd try it if there's no easy = way.=A0 But, I'm *positive* there's an easier way...=20 Q3: How do you change the boot order to include the floppy disk?=A0=20 I would appreciate any help someone can give or pointers to other informati= on for me to try proceeding on my own. Many thanks, Rich I tried winging it and doing the 7.0 and addressing issues as they came up = (which involved a few hoops with compat_6x, _5x and ldconfig, I think), but= I never quite got it going.=A0 I'm thinking about starting over with 6.3, = which I believe I will have a much, much greater chance to get working. 7.0 was a bear to get on it, but only because it wouldn't recognize my burn= t CD as bootable.=A0 I realize now that I never got to kern.flp, though - b= oot.flp was all it took.=A0 I don't know if that's because magically my unb= ootable CD became bootable, or if the bootable floppy figured out there was= a CD there and used it. So I decided reinstalling from 6.3 wouldn't be an issue, except I=20 =A0=20 =A0 Rich Mahlerwein mahlerrd@yahoo.com Mobile: 715-891-7420 _______________________________________________ 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 Tue Jul 29 18:44:53 2008 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 B45B81065671 for ; Tue, 29 Jul 2008 18:44:53 +0000 (UTC) (envelope-from friedman@www1.emax.ca) Received: from www1.emax.ca (www1.emax.ca [69.13.248.199]) by mx1.freebsd.org (Postfix) with ESMTP id 799438FC17 for ; Tue, 29 Jul 2008 18:44:53 +0000 (UTC) (envelope-from friedman@www1.emax.ca) Received: from www1.emax.ca (www1.emax.ca [69.13.248.199]) by www1.emax.ca (8.12.11/8.12.9) with ESMTP id m6TIiqCY017768 for ; Tue, 29 Jul 2008 14:44:52 -0400 (EDT) (envelope-from friedman@www1.emax.ca) Received: (from friedman@localhost) by www1.emax.ca (8.12.11/8.12.9/Submit) id m6TIiqYw017767 for freebsd-proliant@freebsd.org; Tue, 29 Jul 2008 14:44:52 -0400 (EDT) (envelope-from friedman) Date: Tue, 29 Jul 2008 14:44:52 -0400 From: Barry Friedman To: freebsd-proliant@freebsd.org Message-ID: <20080729184452.GA14558@emax.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Scanned-By: MIMEDefang 2.42 Subject: Changing the console com port X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bfriedman@emax.ca 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: Tue, 29 Jul 2008 18:44:53 -0000 I am trying to get virtual serial boot console working with ilo standard on the DL380G4. First off, I can't see any way to get the ILO to reconfigure and use COM1 as the virtual port. Anders Nordby had posted a similar problem in Oct '07 (see http://lists.freebsd.org/pipermail/freebsd-proliant/2007-October/000302. html) in which he apparently was configuring the RBSU from the command line. Was this using ilo2 or advanced ilo? In any case, the alternative is to redirect the console to COM2 and reconfigure the boot parameters. The BSD handbook says to use this line in the kernel configuration file: device sio1 at isa? port IO_COM2 flags 0x10 irq 3 but config reports a syntax error on this line. Is the handbook in error? Do I need to set the flags for sio1 in the HINTS file? What is the correct way to change the com port? -- Barry Friedman Emax Computer Systems Inc., 480 Tweedsmuir Ave., Ottawa, Ont. Canada K1Z 5N9 From owner-freebsd-proliant@FreeBSD.ORG Wed Jul 30 01:52:52 2008 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 AE9EF1065677 for ; Wed, 30 Jul 2008 01:52:52 +0000 (UTC) (envelope-from jcagle@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.231]) by mx1.freebsd.org (Postfix) with ESMTP id 65B998FC14 for ; Wed, 30 Jul 2008 01:52:46 +0000 (UTC) (envelope-from jcagle@gmail.com) Received: by wr-out-0506.google.com with SMTP id c8so254631wra.27 for ; Tue, 29 Jul 2008 18:52:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=9Bvopj6S5yOBvFSclnXvQm5qNWotwZtyQrK39DYpJxM=; b=iPqEd/vCfPHZeVr54Qw+NNE/9jJtUCi1PmM9fpTJW1bY/TRTdlasdkgvpYWG342EiE e/YjLmrEI9v9fDskdReZjvWWH9F11tln7s9TQdOlBOIl7ce9gUlFBeDgMSp2IcDpcmO+ DxA6fq6XDl83iUVuI4AQUKDKj4LovBe8CzVj0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=vBvsBwlZMB2f3jqgcAfnznidq9rUhkStM+g0tsfQS1CrqwCE1p9glDuKWkPtgK1h5j gOcuaT80oDu8XOYIIYNQjOF2tZbTpVNNXloaSOUix1UAzsa+LOUa1vF7rV6lKOS1VbO8 imQsPtaFNWTTbVn+aVwQ1G+RRp0bS6qW9+aik= Received: by 10.90.98.13 with SMTP id v13mr10193109agb.86.1217381177331; Tue, 29 Jul 2008 18:26:17 -0700 (PDT) Received: by 10.90.52.2 with HTTP; Tue, 29 Jul 2008 18:26:17 -0700 (PDT) Message-ID: <6863f0c90807291826k55814fe2u837fb60493230c44@mail.gmail.com> Date: Tue, 29 Jul 2008 20:26:17 -0500 From: "John Cagle" To: bfriedman@emax.ca In-Reply-To: <20080729184452.GA14558@emax.ca> MIME-Version: 1.0 References: <20080729184452.GA14558@emax.ca> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-proliant@freebsd.org Subject: Re: Changing the console com port 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: Wed, 30 Jul 2008 01:52:52 -0000 Barry, You have to use the BIOS configuration utility to configure which COM port resources are used for the iLO Virtual Serial Port. (Also called RBSU - ROM Based Setup Utility.) That utility is either menu driven, or command line driven -- it has its own settings for that choice. I think the root of the problem Anders was having is that FreeBSD insists on using the ACPI tables to enable serial ports, instead of just "hardwiring" the COM1 and COM2 ports as serial consoles. Maybe if you disable ACPI you can do what Anders wanted to do. John On Tue, Jul 29, 2008 at 1:44 PM, Barry Friedman wrote: > > I am trying to get virtual serial boot console working with > ilo standard on the DL380G4. First off, I can't see any way to > get the ILO to reconfigure and use COM1 as the virtual port. > Anders Nordby had posted a similar problem in Oct '07 (see > http://lists.freebsd.org/pipermail/freebsd-proliant/2007-October/000302. > html) > in which he apparently was configuring the RBSU from the command > line. Was this using ilo2 or advanced ilo? > > In any case, the alternative is to redirect the console to COM2 and > reconfigure the boot parameters. The BSD handbook says to use this line > in the kernel configuration file: > > device sio1 at isa? port IO_COM2 flags 0x10 irq 3 > > but config reports a syntax error on this line. Is the handbook in > error? Do I need to set the flags for sio1 in the HINTS file? What is > the correct way to change the com port? > > -- > Barry Friedman > Emax Computer Systems Inc., > 480 Tweedsmuir Ave., > Ottawa, Ont. Canada K1Z 5N9 > _______________________________________________ > 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 Fri Aug 1 17:26:46 2008 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 D367F1065681 for ; Fri, 1 Aug 2008 17:26:46 +0000 (UTC) (envelope-from friedman@www1.emax.ca) Received: from www1.emax.ca (www1.emax.ca [69.13.248.199]) by mx1.freebsd.org (Postfix) with ESMTP id 9ECDC8FC20 for ; Fri, 1 Aug 2008 17:26:46 +0000 (UTC) (envelope-from friedman@www1.emax.ca) Received: from www1.emax.ca (www1.emax.ca [69.13.248.199]) by www1.emax.ca (8.12.11/8.12.9) with ESMTP id m71HQjJA035272; Fri, 1 Aug 2008 13:26:45 -0400 (EDT) (envelope-from friedman@www1.emax.ca) Received: (from friedman@localhost) by www1.emax.ca (8.12.11/8.12.9/Submit) id m71HQi8b035271; Fri, 1 Aug 2008 13:26:44 -0400 (EDT) (envelope-from friedman) Date: Fri, 1 Aug 2008 13:26:44 -0400 From: Barry Friedman To: John Cagle Message-ID: <20080801172644.GA28300@emax.ca> References: <20080729184452.GA14558@emax.ca> <6863f0c90807291826k55814fe2u837fb60493230c44@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6863f0c90807291826k55814fe2u837fb60493230c44@mail.gmail.com> User-Agent: Mutt/1.4.2.1i X-Scanned-By: MIMEDefang 2.42 Cc: bfriedman@emax.ca, freebsd-proliant@freebsd.org Subject: Re: Changing the console com port X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bfriedman@emax.ca 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: Fri, 01 Aug 2008 17:26:46 -0000 John, Thanks for this. I hadn't noticed the RBSU setup option F9 during boot and I see that this allows the change of serial port. In the end I was able to use the standard COM2 port by changing the sio1 flags in /boot/device.hints and this seems to work in freebsd 7 (also needed to remove the sio0 flags line and add a boot.config file). In examing the RBSU options, I noticed a thermal shutdown option which was enabled. Is there any chance of this triggering a reboot without leaving any ILO log messages? Barry You wrote: > You have to use the BIOS configuration utility to configure which COM port > resources are used for the iLO Virtual Serial Port. (Also called RBSU - ROM > Based Setup Utility.) That utility is either menu driven, or command line > driven -- it has its own settings for that choice. > > I think the root of the problem Anders was having is that FreeBSD insists on > using the ACPI tables to enable serial ports, instead of just "hardwiring" > the COM1 and COM2 ports as serial consoles. Maybe if you disable ACPI you > can do what Anders wanted to do. -- Barry Friedman Emax Computer Systems Inc., 480 Tweedsmuir Ave., Ottawa, Ont. Canada K1Z 5N9 bfriedman@emax.ca Phone: (613) 725-3198 Fax: 725-0298 From owner-freebsd-proliant@FreeBSD.ORG Fri Aug 1 17:53:20 2008 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 73B3D106564A for ; Fri, 1 Aug 2008 17:53:20 +0000 (UTC) (envelope-from jcagle@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.238]) by mx1.freebsd.org (Postfix) with ESMTP id 2A5268FC13 for ; Fri, 1 Aug 2008 17:53:20 +0000 (UTC) (envelope-from jcagle@gmail.com) Received: by wr-out-0506.google.com with SMTP id c8so1160549wra.27 for ; Fri, 01 Aug 2008 10:53:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=SYKC8f6JIOz4V4lGLEzKPUQPjTJDUAsONrkXkQ9TEME=; b=aG9eMeQ4jXiKUPVe+yERf+Dcx520ehJn4O2jcZfrc92lPJw1hmRLAusefgWu6+0VQ+ rQ1O26YSZpRGYDMrxamWDsKT0WBKEUUJNULJWMU7MvGdHCg4XEbcY+30Bv+8441oOSm4 oK+nTacUKFiP8dnbdcoyD/CL+bM/10TQMlX54= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=MRjKQKUrkxxPQuWSXswTSlL3tITUIhQZVWaZCgV6mFvaNQhRdrTlGR5XlvyVKvW9HV rCorXhHrNd0+SrGISj6ya3w72VRtZ3vivzO5KPlQZ73VaHFgPuf+R5obNplRKUYWodrF C7E2J2p5GQBs8IJ/EXi7SRdxGt77GWxhWN5Ds= Received: by 10.90.63.12 with SMTP id l12mr4734430aga.93.1217613199272; Fri, 01 Aug 2008 10:53:19 -0700 (PDT) Received: by 10.90.52.2 with HTTP; Fri, 1 Aug 2008 10:53:19 -0700 (PDT) Message-ID: <6863f0c90808011053n6f81c2eci5a6f1f48826a987c@mail.gmail.com> Date: Fri, 1 Aug 2008 12:53:19 -0500 From: "John Cagle" To: bfriedman@emax.ca In-Reply-To: <20080801172644.GA28300@emax.ca> MIME-Version: 1.0 References: <20080729184452.GA14558@emax.ca> <6863f0c90807291826k55814fe2u837fb60493230c44@mail.gmail.com> <20080801172644.GA28300@emax.ca> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-proliant@freebsd.org Subject: Re: Changing the console com port 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: Fri, 01 Aug 2008 17:53:20 -0000 I'm not sure about that particular option on that particular server, but it probably needs to have a health driver running in order to log it to the IML (integrated management log) which is viewable with iLO. If the server is based on iLO-2, then it should be logged to the IML without having to run a health driver. There is a different thermal shutdown feature of all ProLiants -- when the server/cpu reaches a "temp deadly" setting, the box will immediately shut down. This feature has saved many ProLiant servers during computer room cooling failures over weekends when no one was around... Other servers burned up during those events... John On Fri, Aug 1, 2008 at 12:26 PM, Barry Friedman wrote: > John, > > Thanks for this. I hadn't noticed the RBSU setup option F9 during boot > and I see that this allows the change of serial port. In the end I > was able to use the standard COM2 port by changing the sio1 flags in > /boot/device.hints and this seems to work in freebsd 7 (also needed to > remove the sio0 flags line and add a boot.config file). > > In examing the RBSU options, I noticed a thermal shutdown option which > was enabled. Is there any chance of this triggering a reboot without > leaving any ILO log messages? > > Barry > > > You wrote: > > You have to use the BIOS configuration utility to configure which COM > port > > resources are used for the iLO Virtual Serial Port. (Also called RBSU - > ROM > > Based Setup Utility.) That utility is either menu driven, or command > line > > driven -- it has its own settings for that choice. > > > > I think the root of the problem Anders was having is that FreeBSD insists > on > > using the ACPI tables to enable serial ports, instead of just > "hardwiring" > > the COM1 and COM2 ports as serial consoles. Maybe if you disable ACPI > you > > can do what Anders wanted to do. > > -- > Barry Friedman > Emax Computer Systems Inc., 480 Tweedsmuir Ave., Ottawa, Ont. Canada K1Z > 5N9 > bfriedman@emax.ca Phone: (613) 725-3198 Fax: 725-0298 > From owner-freebsd-proliant@FreeBSD.ORG Fri Aug 1 22:21:32 2008 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 8F019106568F for ; Fri, 1 Aug 2008 22:21:32 +0000 (UTC) (envelope-from friedman@www1.emax.ca) Received: from www1.emax.ca (www1.emax.ca [69.13.248.199]) by mx1.freebsd.org (Postfix) with ESMTP id 5A0648FC13 for ; Fri, 1 Aug 2008 22:21:31 +0000 (UTC) (envelope-from friedman@www1.emax.ca) Received: from www1.emax.ca (www1.emax.ca [69.13.248.199]) by www1.emax.ca (8.12.11/8.12.9) with ESMTP id m71MLU18044313; Fri, 1 Aug 2008 18:21:30 -0400 (EDT) (envelope-from friedman@www1.emax.ca) Received: (from friedman@localhost) by www1.emax.ca (8.12.11/8.12.9/Submit) id m71MLUTo044312; Fri, 1 Aug 2008 18:21:30 -0400 (EDT) (envelope-from friedman) Date: Fri, 1 Aug 2008 18:21:30 -0400 From: Barry Friedman To: John Cagle Message-ID: <20080801222130.GA43859@emax.ca> References: <20080729184452.GA14558@emax.ca> <6863f0c90807291826k55814fe2u837fb60493230c44@mail.gmail.com> <20080801172644.GA28300@emax.ca> <6863f0c90808011053n6f81c2eci5a6f1f48826a987c@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6863f0c90808011053n6f81c2eci5a6f1f48826a987c@mail.gmail.com> User-Agent: Mutt/1.4.2.1i X-Scanned-By: MIMEDefang 2.42 Cc: bfriedman@emax.ca, freebsd-proliant@freebsd.org Subject: Re: Changing the console com port X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bfriedman@emax.ca 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: Fri, 01 Aug 2008 22:21:32 -0000 You wrote: > I'm not sure about that particular option on that particular server, but it > probably needs to have a health driver running in order to log it to the IML > (integrated management log) which is viewable with iLO. If the server is > based on iLO-2, then it should be logged to the IML without having to run a > health driver. The DL380G4 box only has iLO standard and I presume that there is no health driver running. Now that I have the virtual console working I am faced with the problem that the iLO seems to time out the connection after about 30 min so there is still a difficulty in logging the reboot event which seems to be happening once every ~ 1-5 days. Is there any chance that we'll be seeing the utility software (hpasmd, hpacucli, hpadu) compiled for freebsd 7 any time soon? > There is a different thermal shutdown feature of all ProLiants -- when the > server/cpu reaches a "temp deadly" setting, the box will immediately shut > down. This feature has saved many ProLiant servers during computer room > cooling failures over weekends when no one was around... Other servers > burned up during those events... Thanks again, -- Barry Friedman Emax Computer Systems Inc., 480 Tweedsmuir Ave., Ottawa, Ont. Canada K1Z 5N9 bfriedman@emax.ca Phone: (613) 725-3198 Fax: 725-0298 From owner-freebsd-proliant@FreeBSD.ORG Fri Aug 1 22:45:04 2008 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 DA9CA1065675 for ; Fri, 1 Aug 2008 22:45:04 +0000 (UTC) (envelope-from jcagle@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.237]) by mx1.freebsd.org (Postfix) with ESMTP id 8C5BE8FC15 for ; Fri, 1 Aug 2008 22:45:04 +0000 (UTC) (envelope-from jcagle@gmail.com) Received: by wr-out-0506.google.com with SMTP id c8so1227807wra.27 for ; Fri, 01 Aug 2008 15:45:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=5rweGUx/P9wYCKnMFLcVn122nbfirKw/2y7ZxISSVyk=; b=XqhPkRwyVdDrQkYuENqean5Z8spvsaoDR/eTQ441fh5FHrfdbVX6wkPo1OzOEvv2SU 23IBpZV1UmKzEWKTISxEpPNcZoHu2WV1rshAuyMzXB6xSPDaBjazqA+21PhT7d73mcUN 7NAkbc21Ptb6E4HmyxDjZX0JfL+JjoswZgV5s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=J5ckRk6xS7VKXUfjokaHVsD+lLikipit+DwsTLySfRUqmMyPNlkkNkcQt0b+5xnMLK Loo88HqxdZ20vwNnU6NY7o5X/QsRbyw8evr72dgbfk3IvfPQi6k5FH48AefzpK+yzo/5 b8KTKEflBDVtipFVtLITAarxU3EqsAPQY1zao= Received: by 10.90.82.8 with SMTP id f8mr8733701agb.56.1217630703646; Fri, 01 Aug 2008 15:45:03 -0700 (PDT) Received: by 10.90.52.2 with HTTP; Fri, 1 Aug 2008 15:45:03 -0700 (PDT) Message-ID: <6863f0c90808011545j373e3d1bo18681cd53739bd05@mail.gmail.com> Date: Fri, 1 Aug 2008 17:45:03 -0500 From: "John Cagle" To: bfriedman@emax.ca In-Reply-To: <20080801222130.GA43859@emax.ca> MIME-Version: 1.0 References: <20080729184452.GA14558@emax.ca> <6863f0c90807291826k55814fe2u837fb60493230c44@mail.gmail.com> <20080801172644.GA28300@emax.ca> <6863f0c90808011053n6f81c2eci5a6f1f48826a987c@mail.gmail.com> <20080801222130.GA43859@emax.ca> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-proliant@freebsd.org Subject: Re: Changing the console com port 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: Fri, 01 Aug 2008 22:45:04 -0000 If you're using SSH to access the Virtual Serial Port of iLO, you should be able to set the Idle Connection Timeout to "Infinite" instead of 30 minutes. (This setting is available in the Web administration pages of iLO itself.) However, I don't think that VSP connections will ever time out, but I might be wrong. If the "Infinite" option is not available, then you should consider updating the iLO firmware. Also you probably should explore the other iLO settings -- perhaps there are some other things that you want to enable/disable. I don't know about the utility software... John On Fri, Aug 1, 2008 at 5:21 PM, Barry Friedman wrote: > You wrote: > > I'm not sure about that particular option on that particular server, but > it > > probably needs to have a health driver running in order to log it to the > IML > > (integrated management log) which is viewable with iLO. If the server is > > based on iLO-2, then it should be logged to the IML without having to run > a > > health driver. > > The DL380G4 box only has iLO standard and I presume that there is no > health driver running. Now that I have the virtual console working > I am faced with the problem that the iLO seems to time out the connection > after about 30 min so there is still a difficulty in logging the reboot > event > which seems to be happening once every ~ 1-5 days. > > Is there any chance that we'll be seeing the utility software (hpasmd, > hpacucli, hpadu) compiled for freebsd 7 any time soon? > > > There is a different thermal shutdown feature of all ProLiants -- when > the > > server/cpu reaches a "temp deadly" setting, the box will immediately shut > > down. This feature has saved many ProLiant servers during computer room > > cooling failures over weekends when no one was around... Other servers > > burned up during those events... > > Thanks again, > -- > Barry Friedman > Emax Computer Systems Inc., 480 Tweedsmuir Ave., Ottawa, Ont. Canada K1Z > 5N9 > bfriedman@emax.ca Phone: (613) 725-3198 Fax: 725-0298 >