Date: Tue, 6 Mar 2007 13:53:50 +0300 From: "Artem Kuchin" <matrix@itlegion.ru> To: "Tom Judge" <tom@tomjudge.com> Cc: stable@freebsd.org, Jack Vogel <jfvogel@gmail.com> Subject: Re: Boot prompt for Intel AMT Message-ID: <00b501c75fdd$bab195c0$0c00a8c0@Artem> References: <20070227205351.GA72597@ravenloft.kiev.ua> <20070305035945.GA71660@xor.obsecurity.org> <20070305132350.GB57253@comp.chem.msu.su> <200703051314.29902@aldan> <20070305191714.GF57253@comp.chem.msu.su> <20070305193022.GM10453@deviant.kiev.zoral.com.ua> <000b01c75f6b$594c23d0$0c00a8c0@Artem> <2a41acea0703051355n5148d19cp36bc425ecd054add@mail.gmail.com><008201c75fcc$21302940$0c00a8c0@Artem> <45ED35F2.9080505@tomjudge.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Artem Kuchin wrote: >>>> I hope some people will understand what i am talking about, because >>>> the technology, i think, is not very popular, but can come VERY handy. >>>> >>>> Intel AMT Serial over LAN (SOL, why is it called 'over LAN' if it is >>>> really >>>> 'OVER IP'?) allows to boot into BIOS of a remote machine >>>> and even, as seen in their demo, can be used to control MS DOS prompt. >>> >>> well because it isnt using IP, besides SOIP is uninspiring :) >> >> Wait.. how so? I was sure that the whose SOL (IPMI) protocal is running >> over >> IP and i can REMOTELY (e.g. from anoth planet with IP connection) access >> the machine in the data center. If i can do such thing, then it DOES run >> over IP >> eventually. Isn't it? >> >> Anyway, nobody said anothing about getting freebsd boot prompt over SOL. >> My guess, that this is THE MOST usefull usage of SOL for remote upgrades. >> I understand that this is not as simple as sending data to UART. THis is >> must >> be done explicitely in the boot loader, i thinks. But why no do it? >> > > We have a number of Dell PowerEdge 2950's that we boot using the built > in SOL, which does run over IP as we use it across a routed VPN backbone > (server in the data center, console in the office). We have found that > the IPMI serial port is connected to the system as COM2, which we select > in the bios configuration. We then set device.hints so that the freebsd > console is set to use the same port. We use the open source ipmitool to > access the ipmi controller, and serial port, on the system. Aha! This is something already. When our system boot it says: Mar 5 23:59:04 aaa kernel: sio0: configured irq 4 not in bitmap of probed irqs 0 Mar 5 23:59:04 aaa kernel: sio0: port may not be enabled Mar 5 23:59:04 aaa kernel: sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 Mar 5 23:59:04 aaa kernel: sio0: type 16550A Mar 5 23:59:04 aaa kernel: sio1: configured irq 3 not in bitmap of probed irqs 0 Mar 5 23:59:04 aaa kernel: sio1: port may not be enabled My guess is that sio0 is the real port and sio1 is the IPMI port of Intel AMT. But what does this message really say? What must i do to enable the port? The other question, do i need to include device ipmi in the kernel config? And how do i tell the boot loader to redirect its output to serial port? Sorry, working with freebsd for 10 years now but never touched this issue. -- Regads, Artem
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00b501c75fdd$bab195c0$0c00a8c0>