From friedman at www1.emax.ca Tue Jul 8 17:50:31 2008 From: friedman at www1.emax.ca (Barry Friedman) Date: Tue Jul 8 17:50:38 2008 Subject: Server reboots at random :-( Message-ID: <20080708175026.GA36586@emax.ca> On Fri, Jun 20, 2008 at 3:50 AM, Ulf Zimmermann wrote: > On Thu, Jun 19, 2008 at 07:29:41AM +1000, Edwin Groothuis wrote: >> On Wed, Jun 18, 2008 at 12:29:00PM -0400, BarryFriedman@www1.emax.ca wrote: >> > Any ideas about how to troubleshoot this would be greatly appreciated. >> >> Start with enabling crash dumps to see if it is a kernel issue or >> a hardware issue: > > You might also want to setup virtual serial and enable console on serial. > Then you can use conserver to log anything and check after a reboot. > 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 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 the line : device sio1 at isa? port IO_COM2 flags 0x10 irq 3 to do this, 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 proceed? The reboot problem persists. The machine has gone as long as 27hrs before rebooting, average 18hrs. This is a system under no load. I have tried turning off the network interface to see if there was any external source of the problem to no avail. What kinds of hardware failure could cause this kind of behavior? Regards, -- 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 friedman at www1.emax.ca Tue Jul 8 18:08:48 2008 From: friedman at www1.emax.ca (Barry Friedman) Date: Tue Jul 8 18:08:54 2008 Subject: bge interface configuration caused throttling : Solved Message-ID: <20080708180846.GB36586@emax.ca> OS: FreeBSD 7.0-RELEASE-p2 Machine: HP Proliant DL380G4 Network adapter: HP NC7782 Gigabit Server Adapter Apparently the use of configuration directives : ifconfig_bge0="inet xx.xx.xx.xx netmask 255.255.240.0 media 100baseTX mediaopt full-duplex" caused incoming network traffic to be throttled to a trickle. When the media and mediaopt parameters were removed the interface worked perfectly. Is this gotcha a bug in the bge driver and if so how should it be reported? -- 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 rainer at ultra-secure.de Tue Jul 8 19:03:10 2008 From: rainer at ultra-secure.de (Rainer Duffner) Date: Tue Jul 8 19:03:16 2008 Subject: bge interface configuration caused throttling : Solved In-Reply-To: <20080708180846.GB36586@emax.ca> References: <20080708180846.GB36586@emax.ca> Message-ID: Am 08.07.2008 um 20:08 schrieb Barry Friedman: > OS: FreeBSD 7.0-RELEASE-p2 > Machine: HP Proliant DL380G4 > Network adapter: HP NC7782 Gigabit Server Adapter > > Apparently the use of configuration directives : > > ifconfig_bge0="inet xx.xx.xx.xx netmask 255.255.240.0 media > 100baseTX > mediaopt full-duplex" > > caused incoming network traffic to be throttled to a trickle. When > the media and mediaopt parameters were removed the interface worked > perfectly. Is this gotcha a bug in the bge driver and if so how > should it be reported? It's rather a question of what the switch on the other end of the cable was configured to. Some switches don't like auto-sense. Some like it, some prefer it. Some only like "Auto-Sensing" to Gigabit etc.pp. It's a funny game. I just try to keep everything to "auto", because I feel switch and interface-cards should be able to do what their vendors advertise: autosensing. Rainer From ba at oaomge.ru Wed Jul 9 07:03:50 2008 From: ba at oaomge.ru (Maxim N. Seregin) Date: Wed Jul 9 07:03:57 2008 Subject: Cant install FreeBSD 7.0 Release on HP Proliant DL 180 G5 Message-ID: <367070433.20080709104839@oaomge.ru> Hello, Freebsd-proliant. OS: FreeBSD 7.0 Release Machine: HP Proliant DL 180 G5 Question: can i install drivers for network cards (drivers for linux only i find) or i cant? Help me please. -- Best regards Max Seregin JSC "Mosgorenergo" ?.495-580-2066 ?.499-500-3511 ?.926-1000-764 From soren at klintrup.dk Wed Jul 9 08:35:40 2008 From: soren at klintrup.dk (=?UTF-8?B?U8O4cmVuIEtsaW50cnVw?=) Date: Wed Jul 9 08:35:55 2008 Subject: Cant install FreeBSD 7.0 Release on HP Proliant DL 180 G5 In-Reply-To: <367070433.20080709104839@oaomge.ru> References: <367070433.20080709104839@oaomge.ru> Message-ID: <487476B9.5040602@klintrup.dk> Maxim N. Seregin wrote: > Hello, Freebsd-proliant. > > OS: FreeBSD 7.0 Release > Machine: HP Proliant DL 180 G5 > Question: can i install drivers for network cards (drivers for linux > only i find) or i cant? Help me please. Drivers should be included in the default FreeBSD Installation (probably bge or bce), I havn't tried this on a DL180G5 (using DL3xx series) - but if you want more help, please attach the output of the following commands: * 'dmesg' ('/var/run/dmesg.boot' if the dmesg buffer is empty or filled with other data) * 'pciconf -l -v' * 'ifconfig -a' Regards, S?ren Klintrup From soren at klintrup.dk Wed Jul 9 08:40:40 2008 From: soren at klintrup.dk (=?UTF-8?B?U8O4cmVuIEtsaW50cnVw?=) Date: Wed Jul 9 08:40:46 2008 Subject: bge interface configuration caused throttling : Solved In-Reply-To: <20080708180846.GB36586@emax.ca> References: <20080708180846.GB36586@emax.ca> Message-ID: <48747564.1050204@klintrup.dk> Barry Friedman wrote: > OS: FreeBSD 7.0-RELEASE-p2 > Machine: HP Proliant DL380G4 > Network adapter: HP NC7782 Gigabit Server Adapter > > Apparently the use of configuration directives : > > ifconfig_bge0="inet xx.xx.xx.xx netmask 255.255.240.0 media 100baseTX > mediaopt full-duplex" > > caused incoming network traffic to be throttled to a trickle. When > the media and mediaopt parameters were removed the interface worked > perfectly. Is this gotcha a bug in the bge driver and if so how > should it be reported? This is by design in the 'autosense' specification. If both devices use autosense, they will negotiate a speed and use that (this does occasionally fail, but it's not something I see very often). If one device is configured to autosense, and the other is not - the autosense device will always fall back to half-duplex, if you want to force full-duplex operation, you have to force this on both ends of the cable. Regards, S?ren Klintrup From michael at lysov.ru Thu Jul 10 03:47:40 2008 From: michael at lysov.ru (Michael S Lysov) Date: Thu Jul 10 03:47:48 2008 Subject: Cant install FreeBSD 7.0 Release on HP Proliant DL 180 G5 In-Reply-To: <367070433.20080709104839@oaomge.ru> References: <367070433.20080709104839@oaomge.ru> Message-ID: <8b1c20dd0807092047w408d6d7cybe9a69ded404ac1d@mail.gmail.com> I think you have same problem as for my dl160 It have "Networking Integrated Broadcom 5722" NIC, wich is not supported by FreeBSD own driver. So you must simply add it into driver and recompile kernel. Patch for bge driver you can find here http://blog.lysov.ru/?p=20. 9 ???? 2008 ?. 12:48 ???????????? Maxim N. Seregin ???????: > Hello, Freebsd-proliant. > > OS: FreeBSD 7.0 Release > Machine: HP Proliant DL 180 G5 > Question: can i install drivers for network cards (drivers for linux > only i find) or i cant? Help me please. > > > > -- > Best regards Max Seregin > JSC "Mosgorenergo" > ?.495-580-2066 > ?.499-500-3511 > ?.926-1000-764 > > _______________________________________________ > 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 news.letter at zolnetwork.com Fri Jul 25 10:10:10 2008 From: news.letter at zolnetwork.com (Akira Norimaki) Date: Fri Jul 25 10:10:16 2008 Subject: SmartArray E200i (ML350) ''ciss0: ADAPTER HEARTBEAT FAILED'' Message-ID: <4889A3FD.8070008@zolnetwork.com> We have a problem with an installation of FreeBSD7 - ungraded from 6 to try to resolve the problem. - where in a random time period the RAID controller fail with the error "ciss0: ADAPTER HEARTBEAT FAILED". The system work but without disk operation. Bye, Akira Norimaki From matsuyama at qac.jp Fri Jul 25 13:08:00 2008 From: matsuyama at qac.jp (?? ??) Date: Fri Jul 25 13:08:36 2008 Subject: SmartArray E200i (ML350) ''ciss0: ADAPTER HEARTBEAT FAILED'' In-Reply-To: <4889A3FD.8070008@zolnetwork.com> Message-ID: We had the save problem with some DL360 G5 servers with SmartArray E200i, they were running 6.2-RELEASE. After upgrading to 7.0R three months ago, the problem hasn't reproduced so far, but I don't know if the problem was fixed because hang-ups occurred in ratio of one time in several months. Hang-ups also occur in the same DL360 G5s with CentOS 5.x. System diagnostic program in Smart Start CD reported no problems with them. Now I doubt of their System ROM version, so I will try to upgrade the System ROM and see what happens. -- Junichi Matsuyama > -----Original Message----- > From: owner-freebsd-proliant@freebsd.org > [mailto:owner-freebsd-proliant@freebsd.org]On Behalf Of Akira Norimaki > Sent: Friday, July 25, 2008 6:59 PM > To: freebsd-proliant@freebsd.org > Subject: SmartArray E200i (ML350) ''ciss0: ADAPTER HEARTBEAT FAILED'' > > > We have a problem with an installation of FreeBSD7 - ungraded from 6 to > try to resolve the problem. - where in a random time period the RAID > controller fail with the error "ciss0: ADAPTER HEARTBEAT FAILED". > > The system work but without disk operation. > > Bye, > Akira Norimaki > _______________________________________________ > 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 mahlerrd at yahoo.com Mon Jul 28 19:35:24 2008 From: mahlerrd at yahoo.com (Richard Mahlerwein) Date: Mon Jul 28 19:35:30 2008 Subject: ML370 (G1), boot options Message-ID: <282583.95073.qm@web51011.mail.re2.yahoo.com> Please ignore cruft at the end - I apparently forgot to finish deleting my first draft of this message.? Boy, do I hope it doesn't outright contradict 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.? I've searched the archives as best I can, and also consulted the Great Oracle of Google, but seem to be getting nowhere in a little project 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 in this case. I recently retrieved a ML370 G1 off the to-be-recycled heap here at work.? It'll replace my aging 550 MHz PIII single-processor PC I've had pressed into "server" duty for ages.? The ML370 is in fine physical order and is a Dual PIII 866 with a Smart Array 3200 in it, 2x 36 GB drives and 4x 18 GB.? I have downloaded and used a SmartStart 5.5 CD to verify all seems well 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.? No problem, I thought, I'll just create the floppies and do a net install from there - I was sure it was just a Old CD Drive + Burnt CD = 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.? (I'm slowly running out of good floppies!) ? I wasn't paying that close of attention, but I realized about mid-way through the install the system never asked me for the kernel floppy.? 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?? I *DID* at least start the boot from the floppy, I remember seeing that little piece, but afterwards, it was magic...? Will the boot floppy hand off to the CD if/when it sees it? Issue 2: The install went fine, the only real issue is in the obnoxiously loud and bothersome fan noise.? 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!"? I noticed it had images for 4.x, 5.x and 6.2.? No 7.0...? Since I had 7.0 already installed, I tried winging it and and installing the various pieces for 6.2 and doing ldconfig and installing compat layers and whatnot, but I couldn't quite get it working.? Q2: Does anyone have some reasonably easy to follow docs on making at least hpasm work on 7.0?? 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 using the 6.2 build of hpasm.? I changed my boot disk to a 6.3 one, stuck it in the floppy drive and booted, but the system happily and without question booted from the hard drives.? 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 going on with this.? I don't think that will work, because I think it was only booting from CD/Floppy *after* the hard drive boot failed.? I don't really want to delete the arrays so it will fail back over to floppy booting, but at this point I'd try it if there's no easy way.? But, I'm *positive* there's an easier way... Q3: How do you change the boot order to include the floppy disk?? I would appreciate any help someone can give or pointers to other information 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.? 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 burnt CD as bootable.? I realize now that I never got to kern.flp, though - boot.flp was all it took.? I don't know if that's because magically my unbootable 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 ? ? Rich Mahlerwein mahlerrd@yahoo.com Mobile: 715-891-7420 From mahlerrd at yahoo.com Mon Jul 28 19:47:50 2008 From: mahlerrd at yahoo.com (Richard Mahlerwein) Date: Mon Jul 28 19:47:56 2008 Subject: ML370 (G1), boot options Message-ID: <475559.43160.qm@web51006.mail.re2.yahoo.com> Hi, all.? I've searched the archives as best I can, and also consulted the Great Oracle of Google, but seem to be getting nowhere in a little project 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 in this case. I recently retrieved a ML370 G1 off the to-be-recycled heap here at work.? It'll replace my aging 550 MHz PIII single-processor PC I've had pressed into "server" duty for ages.? The ML370 is in fine physical order and is a Dual PIII 866 with a Smart Array 3200 in it, 2x 36 GB drives and 4x 18 GB.? I have downloaded and used a SmartStart 5.5 CD to verify all seems well 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.? No problem, I thought, I'll just create the floppies and do a net install from there - I was sure it was just a Old CD Drive + Burnt CD = 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.? (I'm slowly running out of good floppies!) ? I wasn't paying that close of attention, but I realized about mid-way through the install the system never asked me for the kernel floppy.? 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?? I *DID* at least start the boot from the floppy, I remember seeing that little piece, but afterwards, it was magic...? Will the boot floppy hand off to the CD if/when it sees it? Issue 2: The install went fine, the only real issue is in the obnoxiously loud and bothersome fan noise.? 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!"? I noticed it had images for 4.x, 5.x and 6.2.? No 7.0...? Since I had 7.0 already installed, I tried winging it and and installing the various pieces for 6.2 and doing ldconfig and installing compat layers and whatnot, but I couldn't quite get it working.? Q2: Does anyone have some reasonably easy to follow docs on making at least hpasm work on 7.0?? 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 using the 6.2 build of hpasm.? I changed my boot disk to a 6.3 one, stuck it in the floppy drive and booted, but the system happily and without question booted from the hard drives.? 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 going on with this.? I don't think that will work, because I think it was only booting from CD/Floppy *after* the hard drive boot failed.? I don't really want to delete the arrays so it will fail back over to floppy booting, but at this point I'd try it if there's no easy way.? But, I'm *positive* there's an easier way... Q3: How do you change the boot order to include the floppy disk?? I would appreciate any help someone can give or pointers to other information 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.? 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 burnt CD as bootable.? I realize now that I never got to kern.flp, though - boot.flp was all it took.? I don't know if that's because magically my unbootable 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 ? ? Rich Mahlerwein mahlerrd@yahoo.com Mobile: 715-891-7420 From Geoff.Buckingham at thomsonreuters.com Tue Jul 29 07:09:16 2008 From: Geoff.Buckingham at thomsonreuters.com (Geoff Buckingham) Date: Tue Jul 29 07:09:23 2008 Subject: ML370 (G1), boot options In-Reply-To: <475559.43160.qm@web51006.mail.re2.yahoo.com> References: <475559.43160.qm@web51006.mail.re2.yahoo.com> Message-ID: <8753F8EA457BFF4A9707CADA143C8F68057BB904@LONSMSXM04.emea.ime.reuters.com> The ML 370 (G1) most likely has the same lack of an interactive embedded BIOS configuration utility as the DL360 G1 and earlier Compaq Proliants. You configure boot order and the like form Smart Start or an EISA tools partition you install from smart start. -----Original Message----- From: owner-freebsd-proliant@freebsd.org [mailto:owner-freebsd-proliant@freebsd.org] On Behalf Of Richard Mahlerwein Sent: 28 July 2008 20:21 To: freebsd-proliant@freebsd.org Subject: ML370 (G1), boot options Hi, all.? I've searched the archives as best I can, and also consulted the Great Oracle of Google, but seem to be getting nowhere in a little project 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 in this case. I recently retrieved a ML370 G1 off the to-be-recycled heap here at work.? It'll replace my aging 550 MHz PIII single-processor PC I've had pressed into "server" duty for ages.? The ML370 is in fine physical order and is a Dual PIII 866 with a Smart Array 3200 in it, 2x 36 GB drives and 4x 18 GB.? I have downloaded and used a SmartStart 5.5 CD to verify all seems well 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.? No problem, I thought, I'll just create the floppies and do a net install from there - I was sure it was just a Old CD Drive + Burnt CD = 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.? (I'm slowly running out of good floppies!) ? I wasn't paying that close of attention, but I realized about mid-way through the install the system never asked me for the kernel floppy.? 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?? I *DID* at least start the boot from the floppy, I remember seeing that little piece, but afterwards, it was magic...? Will the boot floppy hand off to the CD if/when it sees it? Issue 2: The install went fine, the only real issue is in the obnoxiously loud and bothersome fan noise.? 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!"? I noticed it had images for 4.x, 5.x and 6.2.? No 7.0...? Since I had 7.0 already installed, I tried winging it and and installing the various pieces for 6.2 and doing ldconfig and installing compat layers and whatnot, but I couldn't quite get it working.? Q2: Does anyone have some reasonably easy to follow docs on making at least hpasm work on 7.0?? 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 using the 6.2 build of hpasm.? I changed my boot disk to a 6.3 one, stuck it in the floppy drive and booted, but the system happily and without question booted from the hard drives.? 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 going on with this.? I don't think that will work, because I think it was only booting from CD/Floppy *after* the hard drive boot failed.? I don't really want to delete the arrays so it will fail back over to floppy booting, but at this point I'd try it if there's no easy way.? But, I'm *positive* there's an easier way... Q3: How do you change the boot order to include the floppy disk?? I would appreciate any help someone can give or pointers to other information 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.? 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 burnt CD as bootable.? I realize now that I never got to kern.flp, though - boot.flp was all it took.? I don't know if that's because magically my unbootable 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 ? ? 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 friedman at www1.emax.ca Tue Jul 29 18:44:53 2008 From: friedman at www1.emax.ca (Barry Friedman) Date: Tue Jul 29 18:45:00 2008 Subject: Changing the console com port Message-ID: <20080729184452.GA14558@emax.ca> 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 jcagle at gmail.com Wed Jul 30 01:52:52 2008 From: jcagle at gmail.com (John Cagle) Date: Wed Jul 30 01:53:02 2008 Subject: Changing the console com port In-Reply-To: <20080729184452.GA14558@emax.ca> References: <20080729184452.GA14558@emax.ca> Message-ID: <6863f0c90807291826k55814fe2u837fb60493230c44@mail.gmail.com> 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 > " >