Date: Wed, 18 Aug 2021 16:03:34 +0200 From: "Lizbeth Mutterhunt, Ph.D" <lizbethmutterhunt@gmail.com> To: Gerd Hafenbrack <gerd.hafenbrack@gmail.com>, Roger Pau Monn? <royger@freebsd.org> Cc: freebsd-xen@freebsd.org Subject: Re: another xen-kernel UEFI story Message-ID: <4DAB0DB2-E18D-4024-B80B-FCA2D2F51A45@gmail.com> In-Reply-To: <f02a63b1-0b48-55ce-7f98-9486216e8ecf@gmail.com> References: <3839452.BRNeRiNLvY@freebsd_current> <YRVQHmzo5c7Tq3Dn@Air-de-Roger> <9cf13949-3436-ce43-9884-d7a028c940fb@gmail.com> <2659512.iL6vRArjjl@freebsd_current> <f02a63b1-0b48-55ce-7f98-9486216e8ecf@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ok, the RS-232 cable arrived yestereday to connect it with my ASUS board = shouldn=E2=80=99t be the problem, but how to connect on the other side = of a 7 year old Dell Notebook with FreeBSD 14 CURRENT running? I guess I = need a USB -> RS232 adapter there, or? And the Raspi would need = something like this, too? Greetz,=20 Lizbeth P.S.: Clover can boot XEN, but not FreeBSD!? > Op 13 aug. 2021, om 14:49 heeft Gerd Hafenbrack = <gerd.hafenbrack@gmail.com> het volgende geschreven: >=20 > Hello lizbeth, >=20 > there should be no USB involved at all. > Just connect the cable of the RS-232 port slot bracket module onto the = connector labeled "COM1" on the mainboard. See "10. Serial port = connectors (10-1 pin COM1)" in "Chapter 2" on page 2-27 in the P8H77-M = PRO user manual E8626. > = https://dlcdnets.asus.com/pub/ASUS/mb/LGA1155/P8H77-M_PRO/E8626_P8H77-M_PR= O.pdf >=20 > cu, > Gerd >=20 > On 2021-08-13 13:36, lizbethmutterhunt@gmail.com wrote: >> Op Thursday, 12 August 2021 18:56:29 CEST schreef u: >>> Hello, >>>=20 >>> The ASUS P8H77M-Pro has an internal serial connector onboard. = Lizbeth >>> should get a DB9 male slot bracket with 10 pin internal connector = and a >>> null modem cable. >>>=20 >>> Regards, Gerd >> ok guys, i decided to get some connectors for the rs-232 via usb on = both sides >> and also thought on the cable connect in between. this should take = 2-3 days, >> serial console should be able to /proc the very early preboot. when = ready, I >> will report immidiately. look at this output: >> grep uart /var/run/dmesg.boot >> uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on = acpi0 >> uart0: console (115200,n,8,1) >> uart0: fast interrupt >> uart0: PPS capture mode: DCD >> uart: uart0 already exists; skipping it >> pcib0: allocated type 4 (0x2f8-0x2f8) for rid 0 of uart1 >> uart1 failed to probe at port 0x2f8 irq 3 on isa0 >> pcib0: allocated type 4 (0x3e9-0x3e9) for rid 0 of uart2 >> uart2 failed to probe at port 0x3e9 irq 4 on isa0 >> and this I entered up to now: >> sudo stty -a -f /dev/ttyv1 >> speed 9600 baud; 90 rows; 320 columns; >> lflags: -icanon -isig -iexten -echo -echoe -echok -echoke -echonl >> -echoctl -echoprt -altwerase -noflsh -tostop -flusho -pendin >> -nokerninfo -extproc >> iflags: -istrip -icrnl -inlcr -igncr ixon ixoff -ixany -imaxbel = -ignbrk >> -brkint -inpck -ignpar -parmrk >> oflags: -opost onlcr -ocrnl tab0 -onocr -onlret >> cflags: cread cs8 -parenb -parodd hupcl clocal -cstopb -crtscts = -dsrflow >> -dtrflow -mdmbuf rtsdtr >> cchars: discard =3D ^O; dsusp =3D ^Y; eof =3D ^D; eol =3D <undef>; >> eol2 =3D <undef>; erase =3D ^?; erase2 =3D ^H; intr =3D ^C; kill = =3D ^U; >> lnext =3D ^V; min =3D 1; quit =3D ^\; reprint =3D ^R; start =3D = ^Q; >> status =3D ^T; stop =3D ^S; susp =3D ^Z; time =3D 0; werase =3D = ^W; >> cu soon, >> lizbeth >> thx for help, >> lizbeth >>>=20 >>> On 2021-08-12 18:45, Roger Pau Monn=C3=A9 wrote: >>>> On Thu, Aug 12, 2021 at 03:52:55PM +0200, Lizbeth Mutterhunt, Ph.D = wrote: >>>>>> Op 12 aug. 2021, om 09:01 heeft Roger Pau Monn=C3=A9 = <royger@freebsd.org> het >>>>>> volgende geschreven: >>>>>>=20 >>>>>> Adding the freebsd-xen mailing list again. >>>>>>=20 >>>>>> On Wed, Aug 11, 2021 at 12:48:55AM +0200, Lizbeth Mutterhunt, = Ph.D >> wrote: >>>>>>> Op Tuesday, 10 August 2021 15:32:45 CEST schreef u: >>>>>>>> On Tue, Aug 10, 2021 at 02:41:34PM +0200, = lizbethmutterhunt@gmail.com >>>>>>>=20 >>>>>>> wrote: >>>>>>>>> Op Tuesday, 10 August 2021 09:38:58 CEST schreef u: >>>>>>>>>> On Mon, Aug 09, 2021 at 05:23:27PM +0200, >>>>>>>>>> lizbethmutterhunt@gmail.com >>>>>>>=20 >>>>>>> wrote: >>>>>>>>>>> could someone pleas check this link: >>>>>>> = https://forums.freebsd.org/threads/xen-kernel-doesnt-start-at-all.8155 >>>>>>>=20 >>>>>>>>>>> 6/ >>>>>>>>>>>=20 >>>>>>>>>>> does anyone has another idea then duplicating CURRENT and = RELEASE >>>>>>>=20 >>>>>>> via >>>>>>>=20 >>>>>>>>>>> Virtualbox or qemu? >>>>>>>>>>>=20 >>>>>>>>>>> XEN simply doesn't boot after setting xen_kernel on in >>>>>>>>>>> /boot/loader.conf, >>>>>>>>>>> we tried different ways but none worked. It's loading = [text], >>>>>>>=20 >>>>>>> [data], >>>>>>>=20 >>>>>>>>>>> [syms] and the preconfig but afterwards there's just the >>>>>>>=20 >>>>>>> reset-button >>>>>>>=20 >>>>>>>>>>> option, because XEN doesn't boot. >>>>>>>>>>>=20 >>>>>>>>>>> any help appreciated! >>>>>>>>>>=20 >>>>>>>>>> Hello, >>>>>>>>>=20 >>>>>>>>> hello royger! >>>>>>>=20 >>>>>>> hija! >>>>>=20 >>>>> Hello Roger! >>>>>=20 >>>>>>>>>> There are a couple of things to look at, first of all, do you = have a >>>>>>>>>> serial console attached to the box? >>>>>>>>>=20 >>>>>>>>> I guess so, because there are two possibilities to start from = via >>>>>>>=20 >>>>>>> primary >>>>>>>=20 >>>>>>>>> and secodary console! >>>>>>>>=20 >>>>>>>> The serial console is a port (usually a RS-232) on your box = that you >>>>>>>> attach a cable to and connect to another computer, so you can = get >>>>>>>> early text debug output: >>>>>>>>=20 >>>>>>>> https://www.computerhope.com/jargon/s/serial-console.htm >>>>>>>> = https://tldp.org/HOWTO/Remote-Serial-Console-HOWTO/intro-why.html >>>>>>>=20 >>>>>>> Basically I know the RS-232 "live" in the 80s, and I was = soldering a >>>>>>> earth- >>>>>>> cable to connect two PCs without any swith via a deviate of = Midnight >>>>>>> Commander. So first thought, enable serial port in bios; = computer >>>>>>> crashing >>>>>>> at >>>>>>> xen and crashes when allocating the re0. so disabled again! >>>>>>=20 >>>>>> I 'm afraid I'm a bit lost here, so your computer does have some = kind >>>>>> of serial port? >>>>>=20 >>>>> No, no RS-232 output of course but a parallel and serial console = in the >>>>> BIOS! I activated the serial port and got in troubles with = booting; >>>>> beasties logo has been disabled, so no boot menu to unset the = xen_xernel >>>>> at boot prompt. XEN never booted anyway.>> >>>>>> Do you mean that when you enable the serial port in BIOS (I = assume a >>>>>> Serial Over LAN) >>>>>=20 >>>>> Yup! >>>>>=20 >>>>>> the re0 network interface stops working. >>>>>=20 >>>>> Yes, at the dhclient allocations it stops immediately with no = output or >>>>> debugger info at all. Also the keyboard was disabled and I = couldn=E2=80=99t >>>>> press CTRL+C for avoiding DHCPREQUEST.> >>>> I think it would be better to get Xen out of the picture here, and >>>> initially focus on getting a serial console working with plain >>>> FreeBSD. >>>>=20 >>>> Once you have that it should be trivial to attempt to boot >>>> Xen and get the output on the serial, but first you need to have it >>>> working properly with plain FreeBSD. >>>>=20 >>>> The handbook contains a good section about how to get it working: >>>>=20 >>>> = https://docs.freebsd.org/en/books/handbook/serialcomms/#serialconsole-setu= >>>> p >>>>=20 >>>> But it seems like you will need some help from your hardware vendor = in >>>> order to figure out how to enable Serial Over LAN properly on the >>>> firmware. >>>>=20 >>>> Note that you should be able to get the output of both the FreeBSD >>>> loader and kernel on the serial console. >>>>=20 >>>> Regards, Roger.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4DAB0DB2-E18D-4024-B80B-FCA2D2F51A45>