Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 23 Mar 2022 14:39:13 +0100
From:      Alexander Coers <alexander.coers@gmx.de>
To:        Ronald Klop <ronald-lists@klop.ws>
Cc:        "freebsd-x11@freebsd.org" <freebsd-x11@FreeBSD.org>
Subject:   Re: Fixed virtual box driver (drm_v5.4.144_6), sort of
Message-ID:  <6ADD603F-E8ED-4883-9E09-DD5FDEDBBB77@gmx.de>
In-Reply-To: <728905678.132.1648028482165@mailrelay>
References:  <50E4A7BF-A89A-4B66-9709-3AA247D52B83@gmx.de> <728905678.132.1648028482165@mailrelay>

next in thread | previous in thread | raw e-mail | index | archive | help

> Am 23.03.2022 um 10:41 schrieb Ronald Klop <ronald-lists@klop.ws>:
>=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, =
DRM and Linux, I skimmed through the source and tested a lot with FBSD13 =
running 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 vbox DRM driver.
> Within X11 everything looks now okay, multiple monitors as well as =
different 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 open 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 =
Github?
>=20
> Best,
>  Alexander
>=20
> =20
>=20
>=20
> Hi,
>=20
> This sounds very promising. I think you can ask the maintainer of =
VirtualBox 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/
>=20
> 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. ;-)
>=20
> Regards,
> Ronald.
> =20

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







Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6ADD603F-E8ED-4883-9E09-DD5FDEDBBB77>