On Mon, 2021-05-17 at 20:01 +0200, Ben Hutchings wrote: > Control: tag -1 wontfix > > On Wed, 2021-05-12 at 06:16 +0300, Martin-Éric Racine wrote: > > This still applies to current kernels. > > > > The problem seems to be that kernels after version 3 implement a > > memory protection scheme that prevents the framebuffer from being > > accessed by both vesafb and X drivers. The Geode X driver does that. > > Then this is not a kernel bug. The change was intentional and > documented in the NEWS file along with the option to revert it: > > - On most architectures, the /dev/mem device can no longer be used to > access devices that also have a kernel driver. This breaks dosemu > and some old user-space graphics drivers. To allow this, set the > kernel parameter: iomem=relaxed
That said, this was originally reported before that change was made, so possibly there are two different issues here. Let us know if the kernel parameter change doesn't allow the X driver to work again. Ben. -- Ben Hutchings Never attribute to conspiracy what can adequately be explained by stupidity.
signature.asc
Description: This is a digitally signed message part
