From nobody Wed Mar 23 15:42:41 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 ED37711D3FCF for ; Wed, 23 Mar 2022 15:42:43 +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 4KNt0M0Ms0z4xqK for ; Wed, 23 Mar 2022 15:42:42 +0000 (UTC) (envelope-from SRS0=4Fcw=UC=klop.ws=ronald-lists@realworks.nl) Date: Wed, 23 Mar 2022 16:42:41 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1648050161; 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=jwUGoKXnu3hb6gaU06wlT8gjHrtdi4nsYGMzOMe1yQY=; b=nk4gOT7giCKRt+5DiO1Hzo6R03ZkMnS2g2xiWQaf3mWqTdEh4h+XcfbZLMYEt7jXtAa3bv lQ6dnaK4lriaI0FiEqqy/iCsNzcxCZNcGmKHNYxaEIE7/bCungpsEFJ6tuXoC7WsIP64zN QY8ddsCXlXGjWeJk9hA9wVcEMQj3BcTBtR+uHSXxPBoi3Hr5Pmjtz0Y4anXHsS/2Yc4K+3 fAceX1v7VHCS6c5Yzn10kEKNjTa/IZV6jztdUb7esCerGOhrop9OnzOjC/ijr31YZe4McY tc+BfxjhMg3vOb5g4D5dadkBuxd07UZrAbH4v/H9rEmGme13sH6xqQ1SuPOAVw== From: Ronald Klop To: Alexander Coers Cc: "freebsd-x11@freebsd.org" Message-ID: <1270986992.107.1648050161092@mailrelay> In-Reply-To: <6ADD603F-E8ED-4883-9E09-DD5FDEDBBB77@gmx.de> References: <50E4A7BF-A89A-4B66-9709-3AA247D52B83@gmx.de> <728905678.132.1648028482165@mailrelay> <6ADD603F-E8ED-4883-9E09-DD5FDEDBBB77@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_106_1303158156.1648050161083" X-Mailer: Realworks (602.305.04a0cad) Importance: Normal X-Priority: 3 (Normal) X-Rspamd-Queue-Id: 4KNt0M0Ms0z4xqK X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=klop.ws header.s=rw2 header.b=nk4gOT7g; 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.20 / 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)[-1.000]; 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(-1.00)[-0.996]; 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_106_1303158156.1648050161083 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable =20 Van: Alexander Coers Datum: woensdag, 23 maart 2022 14:39 Aan: Ronald Klop CC: "freebsd-x11@freebsd.org" Onderwerp: Re: Fixed virtual box driver (drm_v5.4.144_6), sort of >=20 >=20 > > Am 23.03.2022 um 10:41 schrieb Ronald Klop : > > > > 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 > > > > 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 ru= nning in Virtual Box 6.x on FBSD13 host. Now I fixed the Makefiles and foun= d the issue for the kernel panic which happens directly after loading the v= box DRM driver. > > Within X11 everything looks now okay, multiple monitors as well as diff= erent resolutions work, but in the console there is still a bug making it u= nusable: > > You can=E2=80=99t see any output, the console is frozen. If you force t= he repaint of the virtual machine window (moving other windows around or op= en the =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 Git= hub? > > > > Best, > > Alexander > > > > =20 > > > > > > Hi, > > > > This sounds very promising. I think you can ask the maintainer of Virtu= alBox how to proceed with this: vbox@FreeBSD.org. Or is the driver not in t= he VirtualBox 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 Free= BSD. ;-) > > > > Regards, > > Ronald. > > =20 >=20 > Hi Ronald, >=20 > the driver source is part of the drm-fbsd-kmod repo and the driver behave= s always the same on different host systems, like Windows, Linux or FreeBSD= . So I think the console issue needs to be fixed somewhere in the drm sourc= e, but I have no clue about the inner workings, so any hint or help would b= e appreciated. >=20 > Best, > Alexander >=20 >=20 >=20 > =20 >=20 >=20 >=20 Hi, Sorry, I don't have knowledge about the inner workings of X. So I hope some= body else answers that question. But if you post your patch somewhere I'm willing to test it. Regards, Ronald. =20 ------=_Part_106_1303158156.1648050161083 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable  

Van: Alexander Coers <alexander.coers@gmx.de>
Datum: woensdag, 23 maart 2022 14:39
Aan: Ronald Klop <ronald-lists@klop.ws>
CC: "freebsd-x11@freebsd.org" <freebsd-x11@Fr= eeBSD.org>
Onderwerp: Re: Fixed virtual box driver (drm_v5.4.144_6), = sort of


> Am 23.03.2022 um 10:41 schrieb Ronald Klop <ronald-lists@klop.ws>= ;:
>
> Van: Alexander Coers <alexander.coers@gmx.de>
> Datum: zondag, 20 maart 2022 16:20
> Aan: "freebsd-x11@freebsd.org" <freebsd-x11@FreeBSD.org&g= t;
> 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 r= unning in Virtual Box 6.x on FBSD13 host. Now I fixed the Makefiles and fou= nd the 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 dif= ferent resolutions work, but in the console there is still a bug making it = unusable:
> 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 o= pen the =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 Gi= thub?
>
> Best,
>  Alexander
>
>  
>
>
> Hi,
>
> This sounds very promising. I think you can ask the maintainer of Virt= ualBox how to proceed with this: vbox@FreeBSD.org. Or is the driver not in = the VirtualBox 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 authoritati= ve in development of the virtualbox software on FreeBSD. ;-)
>
> Regards,
> Ronald.
>  

Hi Ronald,

the driver source is part of the drm-fbsd-kmod repo and the driver behaves = always the same on different host systems, like Windows, Linux or FreeBSD. = So I think the console issue needs to be fixed somewhere in the drm source,= but I have no clue about the inner workings, so any hint or help would be = appreciated.

Best,
 Alexander



 


Hi,

Sorry, I don't have knowledge about the inner workings of X. So I hope some= body else answers that question.
But if you post your patch somewhere I'm willing to test it.

Regards,
Ronald.
  ------=_Part_106_1303158156.1648050161083--