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-discuss/20110925/005473.html | 86 +++++++++++++++++++++++++++++ 1 file changed, 86 insertions(+) create mode 100644 zarb-ml/mageia-discuss/20110925/005473.html (limited to 'zarb-ml/mageia-discuss/20110925/005473.html') diff --git a/zarb-ml/mageia-discuss/20110925/005473.html b/zarb-ml/mageia-discuss/20110925/005473.html new file mode 100644 index 000000000..24afaf837 --- /dev/null +++ b/zarb-ml/mageia-discuss/20110925/005473.html @@ -0,0 +1,86 @@ + + + + [Mageia-discuss] Strange behavior after kernel update + + + + + + + + + +

[Mageia-discuss] Strange behavior after kernel update

+ TJ + andrewsfarm at gmail.com +
+ Sun Sep 25 03:39:22 CEST 2011 +

+
+ +
I'm using the 32-bit version of Mageia with a Sempron 3100+ processor, 
+Asus K8V-MX/S motherboard, 2GB DDR RAM, and an nVidia Geforce 6200 AGP 
+video card. I'm using the latest non-free video card driver amd I also 
+have the vendor's generic for-any-Linux version 4.1.2 of VirtualBox 
+installed.
+
+After updating the kernel earlier today, I attempted a reboot. The GUI 
+boot screen came up, and the progress dots showed progress, but it was 
+VERY slow. Not entirely unexpected because the new nVidia and VirtualBox 
+modules had to be installed, but this was far longer than I had ever 
+seen before. Normally I would have used the escape key to go to 
+"verbose" mode to see what was going on, but it didn't function, and the 
+message that I could do so didn't appear.
+
+The progress dots eventually showed progress all the way to the end, and 
+then it was "stuck" there. After about three minutes I used the reset 
+button to reboot, using the old kernel. That worked normally. I then 
+shut down and tried the new kernel again, with the same result as before.
+
+Another reset, but this time I booted into safe mode. This time the text 
+showed the nVidia and VirtualBox modules being installed, then went to a 
+command line. I issued a "halt" command and started again, once again 
+using the GUI bootscreen. This time, the "Press escape for verbose mode" 
+message showed up, and the boot proceeded completely normally. I haven't 
+tried everything yet, but so far it's working perfectly.
+
+I haven't the slightest idea of why this happened, but I thought 
+somebody should know.
+
+TJ
+
+
+ + + + +
+

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