Your message dated Tue, 18 May 2021 18:32:44 +0000
with message-id <e1lj4wk-0002bn...@respighi.debian.org>
and subject line unblock xserver-xorg-video-geode
has caused the Debian Bug report #988714,
regarding unblock: xserver-xorg-video-geode/2.11.20-6
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
988714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: unblock
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Please unblock package xserver-xorg-video-geode
This is a small documentation fix.
It patches the upstream README to add information about what cdmline option is
needed to be able to use this legacy X driver on a Linux kernel newer than 3.xx
without having to disable vesafb. This has been a long-standing issue and was
finally resolved via info provided by the Debian kernel maintainers. The bug
was reassigned to this package and fix as shown in the debdiff.
The package still builds with what's in Unstable and runs as before on Testing.
debdiff attached.
Thanks!
unblock xserver-xorg-video-geode/2.11.20-6
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmCjzB4ACgkQrh+Cd8S0
17byiQ/9GvJUzR/mc4nTzKgTr9YhgsG8Tro6rkmfkgr/lQ0kA2vZAYyQUfzqgLP7
3n6KIKSouTs+w/bomoATMR72oNRzw3fvZgzl6VXLmONHOf8XtoN0CC2u224Evx6+
Gnu7pW+fHGYXahbP+/kotPNqYg8EkWYBE9oTf7BhjWvcP4+AgV1En2g8ZF2KKRff
l3G4mnVp6BWl/OeBxZj/2mWRApx5BsWj0CgE5Gmn10qjIx5crxxsSlS0FIamVbFp
SkXo7toLY2XQVPKfNZV4tUkTL+dyGTmhsf9e8FHvu74/73xtM1FKQEPmnCr/pIVS
H3d88xnEwm1zffodWj0v1H4klgiaYHxD9d3586vDE2THlUneXvi9euAe6YJWmjhh
Q5aUpEsrb0xRxXKYwxnbG8cbM4qYg2PE+h9qv5dqjDuQbaqplpCioWhbMsadXcor
wUSIQZlMln2OW/OZZf1PdjxcnuurXzd/KUsn+4vKEUcbh/5mqOnxjQq/Fwh0yrZr
su59lz9tBI6Lr4adxewfZls+DQm5aO+/wES12dEV8xz103ZshItCcxyYvqS+6R6t
BiWZ7KT06AFdmSLKK9xH5e4b7oaLkMoIqYJvqDUseds6WWq6SlrOUyYUHNerqpk1
G7zR0bUBNd6n47bKEp6fesHYBQh2YCUH2Mk5oKmULCq27mFVk1E=
=Pc5U
-----END PGP SIGNATURE-----
diff -Nru xserver-xorg-video-geode-2.11.20/debian/changelog
xserver-xorg-video-geode-2.11.20/debian/changelog
--- xserver-xorg-video-geode-2.11.20/debian/changelog 2021-01-03
17:11:43.000000000 +0200
+++ xserver-xorg-video-geode-2.11.20/debian/changelog 2021-05-17
21:58:21.000000000 +0300
@@ -1,3 +1,18 @@
+xserver-xorg-video-geode (2.11.20-6) unstable; urgency=medium
+
+ * Merged patch from Git (Closes: #822112):
+ 03_Mention-iomem-relaxed.patch
+
+ Fixes a long-standing issue that prevents this legacy X driver from booting
+ with stock Linux kernels version 4 or newer. Merely adding a cmdline option
+ makes vesafb and legacy X drivers like this one coexist peacefully again.
+
+ This short patch to the upstream README mentions iomem=relaxed as the fix.
+
+ Thanks to Ben Hutchings for figuring this one out.
+
+ -- Martin-Éric Racine <martin-eric.rac...@iki.fi> Mon, 17 May 2021 21:58:21
+0300
+
xserver-xorg-video-geode (2.11.20-5) unstable; urgency=medium
* [watch]
diff -Nru
xserver-xorg-video-geode-2.11.20/debian/patches/03_Mention-iomem-relaxed.patch
xserver-xorg-video-geode-2.11.20/debian/patches/03_Mention-iomem-relaxed.patch
---
xserver-xorg-video-geode-2.11.20/debian/patches/03_Mention-iomem-relaxed.patch
1970-01-01 02:00:00.000000000 +0200
+++
xserver-xorg-video-geode-2.11.20/debian/patches/03_Mention-iomem-relaxed.patch
2021-05-17 21:55:02.000000000 +0300
@@ -0,0 +1,37 @@
+From ae82f4b2746eb24295389f184bc18a9cb6c8f31c Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Martin-=C3=89ric=20Racine?= <martin-eric.rac...@iki.fi>
+Date: Mon, 17 May 2021 21:50:23 +0300
+Subject: [PATCH] Mention iomem=relaxed in the README FAQ for Linux 4.x+
+ requirements
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+Thanks to Ben Hutchings for pointing out that vesafb and legacy X
+drivers can peacefully coexist if iomem=relaxed gets added to the
+Linux kernel cmdline options.
+
+Signed-off-by: Martin-Éric Racine <martin-eric.rac...@iki.fi>
+---
+ README | 5 ++++-
+ 1 file changed, 4 insertions(+), 1 deletion(-)
+
+diff --git a/README b/README
+index e3ec6ee..111f9a6 100644
+--- a/README
++++ b/README
+@@ -94,7 +94,10 @@ A: Since kernel 4.x Linux has strong memory protection. If
the kernel is
+
+ GRUB_GFXPAYLOAD_LINUX=text
+
+- Once this option has been added and the GRUB configuration refreshed,
++ Alternately, adding iomem=relaxed to GRUB_CMDLINE_LINUX_DEFAULT will
++ allow the video memory to be accessed by vesafb and the GEODE driver.
++
++ Once either option has been added and the GRUB configuration refreshed,
+ the GEODE driver will launch on recent kernels as previously.
+
+ Q: Why doesn't the GEODE driver work at WXGA (wide screen) resolutions?
+--
+2.20.1
+
diff -Nru xserver-xorg-video-geode-2.11.20/debian/patches/series
xserver-xorg-video-geode-2.11.20/debian/patches/series
--- xserver-xorg-video-geode-2.11.20/debian/patches/series 2020-12-15
20:27:27.000000000 +0200
+++ xserver-xorg-video-geode-2.11.20/debian/patches/series 2021-05-17
21:57:57.000000000 +0300
@@ -1,2 +1,3 @@
01_fno-common.patch
02_Updated-the-README.patch
+03_Mention-iomem-relaxed.patch
--- End Message ---
--- Begin Message ---
Unblocked.
--- End Message ---
