From: Jan Beulich <jbeulich@suse.com>
To: Dylanger Daly <dylangerdaly@protonmail.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Andrew Cooper <Andrew.Cooper3@citrix.com>
Subject: Re: Ryzen 6000 (Mobile)
Date: Wed, 20 Jul 2022 10:11:44 +0200 [thread overview]
Message-ID: <b3e00f33-527e-e29c-87fb-0773344aa1f6@suse.com> (raw)
In-Reply-To: <pDQL7BhwlO49buWymLE-VFEZJim7qNeMmAeThZgHF9qzcbNbQ6ZoSXktgD14I_HYpsdxqfCugrNoJ227u5DLCWEEXk_h9c7bf4iKdgoQbQ8=@protonmail.com>
On 20.07.2022 02:33, Dylanger Daly wrote:
>> I'd focus on the booting issues first. And I guess you can take a video
>> of that (assuming that a single screenshot likely isn't going to be
>> enough), possibly with "vga=keep" in place (albeit that introduces
>> extra slowness)?
>>
>> There's also the option of using an EHCI debug port for the serial
>> console, but this requires (a) a special cable and (b) the system
>> designers not having inserted any hubs between the controller andthe connector.
>
> Do you know if it's possible to have `console=vga vga=keep` and specify a secondary monitor? This would be very useful if I could have Xen log via a secondary monitor,
No, if anything it could be the other way around. Xen wants to use the
(sole) VGAish thing in the system; Dom0 kernel and Dom0 userspace (X)
may be happy to use any secondary (non-VGA) graphics card. On EFI it
might in principle be possible, but that would require (perhaps quite
a bit of) work in Xen.
Jan
next prev parent reply other threads:[~2022-07-20 8:12 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 23:04 Ryzen 6000 (Mobile) Dylanger Daly
2022-07-19 6:29 ` Jan Beulich
2022-07-19 6:47 ` Dylanger Daly
2022-07-19 6:58 ` Jan Beulich
2022-07-19 6:50 ` Dylanger Daly
2022-07-19 9:34 ` Andrew Cooper
2022-07-20 0:33 ` Dylanger Daly
2022-07-20 8:11 ` Jan Beulich [this message]
2022-07-20 8:13 ` Jan Beulich
2022-08-15 11:07 ` Dylanger Daly
2022-08-15 11:30 ` Jan Beulich
2022-08-15 11:50 ` Dylanger Daly
2022-08-15 11:55 ` Jan Beulich
2022-08-15 12:03 ` Andrew Cooper
2022-08-15 15:39 ` Dylanger Daly
2022-08-15 16:19 ` Jan Beulich
2022-08-15 16:54 ` Dylanger Daly
2022-08-16 6:17 ` Jan Beulich
2022-08-16 8:34 ` Dylanger Daly
2022-08-16 8:59 ` Jan Beulich
2022-08-16 9:19 ` Dylanger Daly
2022-08-16 9:30 ` Jan Beulich
2022-08-16 11:22 ` Jan Beulich
2022-08-24 18:15 ` Dylanger Daly
2022-08-25 8:35 ` Jan Beulich
2022-08-25 11:10 ` Dylanger Daly
2022-08-25 14:55 ` Jan Beulich
2022-08-29 15:26 ` Dylanger Daly
2022-09-06 10:52 ` Jan Beulich
2022-09-06 11:45 ` Dylanger Daly
2022-08-31 22:12 ` Dylanger Daly
2022-09-06 10:50 ` Jan Beulich
2022-09-03 15:59 ` Dylanger Daly
2022-09-05 20:44 ` Dylanger Daly
[not found] ` <6JMvOsjmpWkAsnm6AXzNsjtj5_jy5vG_vG_PwTyDzX0z1buoX89r5UEpSGKf-H7CTBtg9gNlq4Icy7Q9OIDjfrxp2AqNMXbyKTCD0y_d0Hc=@protonmail.com>
2022-09-06 11:51 ` Jan Beulich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b3e00f33-527e-e29c-87fb-0773344aa1f6@suse.com \
--to=jbeulich@suse.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=dylangerdaly@protonmail.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.