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/2013-April/024140.html | 86 +++++++++++++++++++++++++++++++ 1 file changed, 86 insertions(+) create mode 100644 zarb-ml/mageia-dev/2013-April/024140.html (limited to 'zarb-ml/mageia-dev/2013-April/024140.html') diff --git a/zarb-ml/mageia-dev/2013-April/024140.html b/zarb-ml/mageia-dev/2013-April/024140.html new file mode 100644 index 000000000..f2b764eb2 --- /dev/null +++ b/zarb-ml/mageia-dev/2013-April/024140.html @@ -0,0 +1,86 @@ + + + + [Mageia-dev] M3 beta - where to report problems? + + + + + + + + + +

[Mageia-dev] M3 beta - where to report problems?

+ Frank Griffin + ftg at roadrunner.com +
+ Thu Apr 4 18:12:55 CEST 2013 +

+
+ +
On 04/04/2013 10:59 AM, Anne Wilson wrote:
+> Not much progress.  My usual method of editing the kernel line to get
+> a level 3 boot doesn't work - same blank (but lit) screen.  Failsafe
+> appears to be doing better - at least I can see messages.  It reaches
+>
+> Reached target Multi-User
+> Reached target Graphical Interface
+>
+> and there it sticks.  Does that give any clue as to what is failing,
+> and what I need to do to rescue the system?
+>
+Boot a rescue disk and mount your root partition.  In 
+/etc/systemd/system you should see a symlink like:
+
+lrwxrwxrwx 1 root root   36 Mar 29 11:00 default.target -> 
+/lib/systemd/system/runlevel5.target
+
+Just remove this and re-symlink to /lib/systemd/system/runlevel3.target 
+and you should get a level 3 boot.
+
+ + + + + + + + + + + + + + +
+

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