From nobody Wed Mar 23 09:41:22 2022 X-Original-To: freebsd-x11@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 C210C1A305FF for ; Wed, 23 Mar 2022 09:41:31 +0000 (UTC) (envelope-from SRS0=4Fcw=UC=klop.ws=ronald-lists@realworks.nl) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.24]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4KNjzZ5rMKz4r8h for ; Wed, 23 Mar 2022 09:41:30 +0000 (UTC) (envelope-from SRS0=4Fcw=UC=klop.ws=ronald-lists@realworks.nl) Date: Wed, 23 Mar 2022 10:41:22 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1648028482; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=7PoeW0Q48ImU4M514UFn3zl+UPAwIFRLSzzXJvgkb/U=; b=QYGWLOHT7Lot+qX2zmsy2inHH4M/C38aK4zIEKpBk15Qr/hIeig217sQt8PXYnAsMtcvu0 LG1X3A0JX1KwIn1F3PayrMvPnlNOsS+7JsyxI37f5QZWtMPoWX2FIct03ELynhqfPkdxhw msjQVbf0lKjX3WMEyqm9OPjgopkRn4KHos3zUYuus1eDS/XJuPDZUVTt1ayvMvZXmo+T67 V1uc7nVJLC4LV40QLfqLdlWF+rtFYfDfVrB6oiCytpJ36CHP/PmgION2bfBu0yFmnWK31P BhOkYl+sDwzMEwNsICxHFrZI2cesqdPxSF/gHKH95WTAolOaAsRCoXzTtoAMSw== From: Ronald Klop To: Alexander Coers Cc: "freebsd-x11@freebsd.org" Message-ID: <728905678.132.1648028482165@mailrelay> In-Reply-To: <50E4A7BF-A89A-4B66-9709-3AA247D52B83@gmx.de> References: <50E4A7BF-A89A-4B66-9709-3AA247D52B83@gmx.de> Subject: Re: Fixed virtual box driver (drm_v5.4.144_6), sort of List-Id: X11 List-Archive: https://lists.freebsd.org/archives/freebsd-x11 List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-x11@freebsd.org X-BeenThere: freebsd-x11@freebsd.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_131_985937622.1648028482109" X-Mailer: Realworks (601.302.c1954fd) Importance: Normal X-Priority: 3 (Normal) X-Rspamd-Queue-Id: 4KNjzZ5rMKz4r8h X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=klop.ws header.s=rw2 header.b=QYGWLOHT; dmarc=pass (policy=quarantine) header.from=klop.ws; spf=pass (mx1.freebsd.org: domain of "SRS0=4Fcw=UC=klop.ws=ronald-lists@realworks.nl" designates 194.109.157.24 as permitted sender) smtp.mailfrom="SRS0=4Fcw=UC=klop.ws=ronald-lists@realworks.nl" X-Spamd-Result: default: False [-3.17 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; FORGED_SENDER(0.30)[ronald-lists@klop.ws,SRS0=4Fcw=UC=klop.ws=ronald-lists@realworks.nl]; R_DKIM_ALLOW(-0.20)[klop.ws:s=rw2]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:194.109.157.0/24]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; RWL_MAILSPIKE_EXCELLENT(0.00)[194.109.157.24:from]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[klop.ws:+]; RCPT_COUNT_TWO(0.00)[2]; HAS_X_PRIO_THREE(0.00)[3]; NEURAL_HAM_SHORT(-0.97)[-0.968]; DMARC_POLICY_ALLOW(-0.50)[klop.ws,quarantine]; MLMMJ_DEST(0.00)[freebsd-x11]; FREEMAIL_TO(0.00)[gmx.de]; RCVD_COUNT_ZERO(0.00)[0]; MIME_TRACE(0.00)[0:+,1:+,2:~]; MID_RHS_NOT_FQDN(0.50)[]; ASN(0.00)[asn:3265, ipnet:194.109.0.0/16, country:NL]; FROM_NEQ_ENVFROM(0.00)[ronald-lists@klop.ws,SRS0=4Fcw=UC=klop.ws=ronald-lists@realworks.nl] X-ThisMailContainsUnwantedMimeParts: N ------=_Part_131_985937622.1648028482109 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable =20 Van: Alexander Coers Datum: zondag, 20 maart 2022 16:20 Aan: "freebsd-x11@freebsd.org" Onderwerp: Fixed virtual box driver (drm_v5.4.144_6), sort of >=20 > Hi everyone, >=20 > Since I wanted to know how all things are working out between FreeBSD, DR= M and Linux, I skimmed through the source and tested a lot with FBSD13 runn= ing in Virtual Box 6.x on FBSD13 host. Now I fixed the Makefiles and found = the issue for the kernel panic which happens directly after loading the vbo= x DRM driver. > Within X11 everything looks now okay, multiple monitors as well as differ= ent resolutions work, but in the console there is still a bug making it unu= sable: > You can=E2=80=99t see any output, the console is frozen. If you force the= repaint of the virtual machine window (moving other windows around or open= the =E2=80=9Eabout dialog=E2=80=9C of Virtual Box), the output is drawn. S= o console works, but the framebuffer output seems to have issues. > Do you have an idea where I could look to fix this issue? Is there any mo= re documentation on how DRM works? > Also, how should I provide the fix? Diff here in the list, or PR in Githu= b? >=20 > Best, > Alexander >=20 > =20 >=20 >=20 >=20 Hi, This sounds very promising. I think you can ask the maintainer of VirtualBo= x how to proceed with this: vbox@FreeBSD.org. Or is the driver not in the V= irtualBox source. See: https://www.freshports.org/emulators/virtualbox-ose/ A possibility is to create a PR in https://bugs.freebsd.org/bugzilla/, but = I'm not authoritative in development of the virtualbox software on FreeBSD.= ;-) Regards, Ronald. =20 ------=_Part_131_985937622.1648028482109 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable  

Van: Alexander Coers <alexander.coers@gmx.de>
Datum: zondag, 20 maart 2022 16:20
Aan: "freebsd-x11@freebsd.org" <freebsd-x11@F= reeBSD.org>
Onderwerp: Fixed virtual box driver (drm_v5.4.144_6), sort= of

Hi everyone,

Since I wanted to know how all things are working out between FreeBSD, DRM = and Linux, I skimmed through the source and tested a lot with FBSD13 runnin= g in Virtual Box 6.x on FBSD13 host. Now I fixed the Makefiles and found th= e issue for the kernel panic which happens directly after loading the vbox = DRM driver.
Within X11 everything looks now okay, multiple monitors as well as differen= t resolutions work, but in the console there is still a bug making it unusa= ble:
You can=E2=80=99t see any output, the console is frozen. If you force the r= epaint of the virtual machine window (moving other windows around or open t= he =E2=80=9Eabout dialog=E2=80=9C of Virtual Box), the output is drawn. So = console works, but the framebuffer output seems to have issues.
Do you have an idea where I could look to fix this issue? Is there any more= documentation on how DRM works?
Also, how should I provide the fix? Diff here in the list, or PR in Github?=

Best,
 Alexander

 


Hi,

This sounds very promising. I think you can ask the maintainer of VirtualBo= x how to proceed with this: vbox@FreeBSD.org. Or is the driver not in the V= irtualBox source.
See: https://www.freshports.org/emulators/virtualbox-ose/

A possibility is to create a PR in https://bugs.freebsd.org/bugzilla/, but = I'm not authoritative in development of the virtualbox software on FreeBSD.= ;-)

Regards,
Ronald.
  ------=_Part_131_985937622.1648028482109--