From nobody Wed Aug 18 14:53:15 2021 X-Original-To: freebsd-xen@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 80F74174A200 for ; Wed, 18 Aug 2021 14:53:18 +0000 (UTC) (envelope-from gerd.hafenbrack@gmail.com) Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4GqW9V2xVzz4bMW for ; Wed, 18 Aug 2021 14:53:18 +0000 (UTC) (envelope-from gerd.hafenbrack@gmail.com) Received: by mail-ed1-x529.google.com with SMTP id r19so3532055eds.13 for ; Wed, 18 Aug 2021 07:53:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=evb4HJA5EyvZYv7OTtdjK1ei86LxCqNawQC/FFIzqmo=; b=oTZRxoDXxO5hSpUZqc3OZlPhZHYVZODPm7+jQcPIVYxve5PEMbfaOC0F8UnlWkJ22o OX8XSf8nwvIuvgJ2YTpc6NZe3MpC2H5lbD7lG5vKAlWnh41vGL13he9pSH6n8zuk9j4a bnPe5DLodiwOXdHRa3qKqS1M4DBnLat/6uWaniLD3ZHFw6XNVBcf1qj+V+H1aErK3kDi 1/l0cNyspLBsTr6Im3INHp6X7FEf6eJ4Vw5SHNiXv8Fd7VQ1yG1bxoypC2xu2MbjQFsD ZM3egduY/XAXtjyOF1fFFicWO5dpYkf17EDyf0wJm0gPaSAL1mKMzI5/ibEgecB4bMR4 WmUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=evb4HJA5EyvZYv7OTtdjK1ei86LxCqNawQC/FFIzqmo=; b=X90bDelMm9j4yCIkiPSV4WI0Y+asMfBgquWTqAHTvkUfN17uWAILni9dXqKax4bmOP qxgmXI7vc0EVOYjlGm/pGvSosKl4XIK6ycPxKyXq0EmfmKoJ5dE9Jgfe9i/WZg5TB05t MOMl0Zdp5QAzb/ZalBxa9/X+8CrWH6Heb7HNQlWlk4x3Z0XECXEYLctbii7FegTcM0qO c74X54xDB4RJgG8MwFkDlchG8axioVvh3Ev9BtrnULsvymwTkIjzyFJdhKfIXqIhNdfg JJpfk/n1gUbPE3ncHID7oPVnBO3DcR4KHJSLURpcbdCYPtvRW/lf9tv8KEw9udZGTYau 4N0g== X-Gm-Message-State: AOAM531sMh3qLoKphbZTtDk2U+79FOAYlwTpLDfJhVKLM72oup3gxyfF GPYQt8i8oKusQl6nePeWlJ0QNGFJKqk= X-Google-Smtp-Source: ABdhPJzI9fYveuk3TgWvaoEl0G7RRtoOwacpTvvMjj52LzFgD3Z8CQuFWLszUz0RtZ1AdQz5FHYhRA== X-Received: by 2002:a05:6402:19a:: with SMTP id r26mr10444593edv.230.1629298397328; Wed, 18 Aug 2021 07:53:17 -0700 (PDT) Received: from ?IPv6:2a02:8070:e198:fc00:95ca:dbd4:f6e2:b742? ([2a02:8070:e198:fc00:95ca:dbd4:f6e2:b742]) by smtp.gmail.com with ESMTPSA id kv4sm2188033ejc.35.2021.08.18.07.53.16 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 18 Aug 2021 07:53:16 -0700 (PDT) Subject: Re: another xen-kernel UEFI story To: "Lizbeth Mutterhunt, Ph.D" Cc: freebsd-xen@freebsd.org References: <3839452.BRNeRiNLvY@freebsd_current> <9cf13949-3436-ce43-9884-d7a028c940fb@gmail.com> <2659512.iL6vRArjjl@freebsd_current> <4DAB0DB2-E18D-4024-B80B-FCA2D2F51A45@gmail.com> From: Gerd Hafenbrack Message-ID: Date: Wed, 18 Aug 2021 16:53:15 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-xen List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-xen@freebsd.org X-BeenThere: freebsd-xen@freebsd.org MIME-Version: 1.0 In-Reply-To: <4DAB0DB2-E18D-4024-B80B-FCA2D2F51A45@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4GqW9V2xVzz4bMW X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N As all my desktop computer have a RS-232 port, I can't help further. cu, Gerd On 2021-08-18 16:03, Lizbeth Mutterhunt, Ph.D wrote: > Ok, the RS-232 cable arrived yestereday to connect it with my ASUS board shouldn’t 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, > Lizbeth > > P.S.: Clover can boot XEN, but not FreeBSD!? > > > > > > >> Op 13 aug. 2021, om 14:49 heeft Gerd Hafenbrack het volgende geschreven: >> >> Hello lizbeth, >> >> 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_PRO.pdf >> >> cu, >> Gerd >> >> On 2021-08-13 13:36, lizbethmutterhunt@gmail.com wrote: >>> Op Thursday, 12 August 2021 18:56:29 CEST schreef u: >>>> Hello, >>>> >>>> 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. >>>> >>>> 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 = ^O; dsusp = ^Y; eof = ^D; eol = ; >>> eol2 = ; erase = ^?; erase2 = ^H; intr = ^C; kill = ^U; >>> lnext = ^V; min = 1; quit = ^\; reprint = ^R; start = ^Q; >>> status = ^T; stop = ^S; susp = ^Z; time = 0; werase = ^W; >>> cu soon, >>> lizbeth >>> thx for help, >>> lizbeth >>>> >>>> On 2021-08-12 18:45, Roger Pau Monné 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é het >>>>>>> volgende geschreven: >>>>>>> >>>>>>> Adding the freebsd-xen mailing list again. >>>>>>> >>>>>>> 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 >>>>>>>> >>>>>>>> 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 >>>>>>>> >>>>>>>> wrote: >>>>>>>>>>>> could someone pleas check this link: >>>>>>>> https://forums.freebsd.org/threads/xen-kernel-doesnt-start-at-all.8155 >>>>>>>> >>>>>>>>>>>> 6/ >>>>>>>>>>>> >>>>>>>>>>>> does anyone has another idea then duplicating CURRENT and RELEASE >>>>>>>> >>>>>>>> via >>>>>>>> >>>>>>>>>>>> Virtualbox or qemu? >>>>>>>>>>>> >>>>>>>>>>>> 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], >>>>>>>> >>>>>>>> [data], >>>>>>>> >>>>>>>>>>>> [syms] and the preconfig but afterwards there's just the >>>>>>>> >>>>>>>> reset-button >>>>>>>> >>>>>>>>>>>> option, because XEN doesn't boot. >>>>>>>>>>>> >>>>>>>>>>>> any help appreciated! >>>>>>>>>>> >>>>>>>>>>> Hello, >>>>>>>>>> >>>>>>>>>> hello royger! >>>>>>>> >>>>>>>> hija! >>>>>> >>>>>> Hello Roger! >>>>>> >>>>>>>>>>> There are a couple of things to look at, first of all, do you have a >>>>>>>>>>> serial console attached to the box? >>>>>>>>>> >>>>>>>>>> I guess so, because there are two possibilities to start from via >>>>>>>> >>>>>>>> primary >>>>>>>> >>>>>>>>>> and secodary console! >>>>>>>>> >>>>>>>>> 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: >>>>>>>>> >>>>>>>>> https://www.computerhope.com/jargon/s/serial-console.htm >>>>>>>>> https://tldp.org/HOWTO/Remote-Serial-Console-HOWTO/intro-why.html >>>>>>>> >>>>>>>> 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! >>>>>>> >>>>>>> I 'm afraid I'm a bit lost here, so your computer does have some kind >>>>>>> of serial port? >>>>>> >>>>>> 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) >>>>>> >>>>>> Yup! >>>>>> >>>>>>> the re0 network interface stops working. >>>>>> >>>>>> Yes, at the dhclient allocations it stops immediately with no output or >>>>>> debugger info at all. Also the keyboard was disabled and I couldn’t >>>>>> 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. >>>>> >>>>> 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. >>>>> >>>>> The handbook contains a good section about how to get it working: >>>>> >>>>> https://docs.freebsd.org/en/books/handbook/serialcomms/#serialconsole-setu >>>>> p >>>>> >>>>> 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. >>>>> >>>>> Note that you should be able to get the output of both the FreeBSD >>>>> loader and kernel on the serial console. >>>>> >>>>> Regards, Roger. >