Date: Wed, 23 Mar 2022 10:41:22 +0100 (CET) From: Ronald Klop <ronald-lists@klop.ws> To: Alexander Coers <alexander.coers@gmx.de> Cc: "freebsd-x11@freebsd.org" <freebsd-x11@FreeBSD.org> Subject: Re: Fixed virtual box driver (drm_v5.4.144_6), sort of Message-ID: <728905678.132.1648028482165@mailrelay> In-Reply-To: <50E4A7BF-A89A-4B66-9709-3AA247D52B83@gmx.de> References: <50E4A7BF-A89A-4B66-9709-3AA247D52B83@gmx.de>
next in thread | previous in thread | raw e-mail | index | archive | help
------=_Part_131_985937622.1648028482109 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable =20 Van: Alexander Coers <alexander.coers@gmx.de> Datum: zondag, 20 maart 2022 16:20 Aan: "freebsd-x11@freebsd.org" <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 <html><head></head><body> <p><strong>Van:</strong> Alexander Coers <alexander.coers@gmx.de><br = /> <strong>Datum:</strong> zondag, 20 maart 2022 16:20<br /> <strong>Aan:</strong> "freebsd-x11@freebsd.org" <freebsd-x11@F= reeBSD.org><br /> <strong>Onderwerp:</strong> Fixed virtual box driver (drm_v5.4.144_6), sort= of</p> <blockquote style=3D"padding-right: 0px; padding-left: 5px; margin-left: 5p= x; border-left: #000000 2px solid; margin-right: 0px"> <div class=3D"MessageRFC822Viewer" id=3D"P"> <div class=3D"TextPlainViewer" id=3D"P.P">Hi everyone,<br /> <br /> 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.<br /> 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:<br /> 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.<br /> Do you have an idea where I could look to fix this issue? Is there any more= documentation on how DRM works?<br /> Also, how should I provide the fix? Diff here in the list, or PR in Github?= <br /> <br /> Best,<br /> Alexander<br /> <br /> </div> <hr /></div> </blockquote> <br /> <br /> Hi,<br /> <br /> 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.<br /> See: https://www.freshports.org/emulators/virtualbox-ose/<br /> <br /> 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.= ;-)<br /> <br /> Regards,<br /> Ronald.<br /> </body></html> ------=_Part_131_985937622.1648028482109--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?728905678.132.1648028482165>