From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/20110501/004335.html | 85 +++++++++++++++++++++++++++++++++ 1 file changed, 85 insertions(+) create mode 100644 zarb-ml/mageia-dev/20110501/004335.html (limited to 'zarb-ml/mageia-dev/20110501/004335.html') diff --git a/zarb-ml/mageia-dev/20110501/004335.html b/zarb-ml/mageia-dev/20110501/004335.html new file mode 100644 index 000000000..4749cba05 --- /dev/null +++ b/zarb-ml/mageia-dev/20110501/004335.html @@ -0,0 +1,85 @@ + + + + [Mageia-dev] RFT: kernel-2.6.38.5-0.rc1.1.mga1 on 32bit installs + + + + + + + + + +

[Mageia-dev] RFT: kernel-2.6.38.5-0.rc1.1.mga1 on 32bit installs

+ Thomas Backlund + tmb at mageia.org +
+ Sun May 1 17:52:28 CEST 2011 +

+
+ +
Hi,
+
+anyone that have had to add a "vmalloc=" on the kernel command line on a
+32bit install (atleast some users of nvidia proprietary drivers), can
+you try to remove the "vmalloc=" part and reboot...
+
+Does it still work after the reboot ?
+
+And for all 32bit users that haven't had to add the vmalloc line, do you
+see any problems with the kernel-2.6.38.5-0.rc1.1.mga1 (something
+stopped working since the 2.6.38.4 kernel) ?
+
+if you see any problem, does it go away if you add 
+
+vmalloc=128M
+
+to the kernel command line and reboot?
+
+The reason for theese questions it that we have raised default vmalloc
+to 192M in order to solve issues like
+https://bugs.mageia.org/show_bug.cgi?id=904
+and would like to know before we release Mageia 1 (or RC actually) if it
+breaks something.
+
+--
+Thomas
+
+
+
+ + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1