1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-discuss] Mageia 2 Experiences
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Mageia%202%20%20Experiences&In-Reply-To=%3C4F9941AC.2080607%40roadrunner.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="007133.html">
<LINK REL="Next" HREF="007136.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-discuss] Mageia 2 Experiences</H1>
<B>Frank Griffin</B>
<A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Mageia%202%20%20Experiences&In-Reply-To=%3C4F9941AC.2080607%40roadrunner.com%3E"
TITLE="[Mageia-discuss] Mageia 2 Experiences">ftg at roadrunner.com
</A><BR>
<I>Thu Apr 26 14:38:04 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="007133.html">[Mageia-discuss] Mageia 2 Experiences
</A></li>
<LI>Next message: <A HREF="007136.html">[Mageia-discuss] Mageia 2 Experiences
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#7135">[ date ]</a>
<a href="thread.html#7135">[ thread ]</a>
<a href="subject.html#7135">[ subject ]</a>
<a href="author.html#7135">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On 04/26/2012 07:50 AM, imnotpc wrote:
><i> On 04/25/2012 10:32 PM, Frank Griffin wrote:
</I>>><i> If you boot a rescue CD, mount the root partition, change the
</I>>><i> runlevel in /etc/inittab to 3 rather than 5, and reboot, do you get
</I>>><i> to a login prompt with no problem ?
</I>><i>
</I>><i> No, it locks up with a blank screen. The last line I could read before
</I>><i> it went blank was "Starting speech dispatcher..."
</I>><i>
</I>><i> If I boot using safe mode the system doesn't lock, but doesn't give me
</I>><i> a command prompt either. The last message is "Failed to issue method
</I>><i> call: Transaction is destructive."
</I>
OK, there may be several issues in play here.
Cauldron currently starts plymouth on tty1 to display boot messages, and
I think the design relies on a Display Manager (GDM, KDM) signalling
plymouth to exit, so if you boot to runlevel 3 (where no DM is staretd,
plymouth currently hangs around on tty1, and it looks like it's hung.
However, if you do ALT-F2 (or 3, 4, etc), switching to an available tty
that isn't running X should start getty there and give you a login prompt.
What I'm trying to determine is whether your line-mode tty video works
without X in the picture.
If you could read "Starting speech dispatcher", then your tty was
working, and the blank screen was probably the result of starting X.
Maybe with systemd now, there is a different way of setting the
runlevel. Try booting in safe mode, doing ALT-F2, logging in as root,
and running XFdrake. Then uncheck the box which says start graphical
mode at boot, and try again.
The "Transaction is destructive" thing is a known open bug.
>><i> If your NICs worked under mga1, NM is most likely the culprit.
</I>>><i>
</I>><i>
</I>><i> I install over the network so the wired NIC is working during
</I>><i> installation. The wireless NICs work as well but they usually need
</I>><i> firmware installed first. I'll take a look at this once I can reliably
</I>><i> get that far. Thanks for the help.
</I>><i>
</I>
If the wired NIC works during installation, then it doesn't need
firmware, and there's no reason it shouldn't work in the new system.
It's common for wireless to take a few reboots, since the install
doesn't detect wireless and install everything it should. Instead, when
you run drakconnect to add the wireless interface, it kicks urpmi to
install wireless-tools and some other packages. It also detects your
wireless NIC, and modifies boot files to load the appropriate kernel
driver (if it recognizes it).
So it's not unusual for the initial attempt at adding wlan0 to show only
"Use a windows driver with ndiswrapper" until you reboot and the kernel
recognizes the device. Then using drakconnect should show your actual
device.
I haven't used any NICs that require firmware not included with the
install, so I don't know how automatic that is.
Once you get to the point of defining eth0 or wlan0 and not having it
come up, you can do the checks for NM.
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="007133.html">[Mageia-discuss] Mageia 2 Experiences
</A></li>
<LI>Next message: <A HREF="007136.html">[Mageia-discuss] Mageia 2 Experiences
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#7135">[ date ]</a>
<a href="thread.html#7135">[ thread ]</a>
<a href="subject.html#7135">[ subject ]</a>
<a href="author.html#7135">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-discuss">More information about the Mageia-discuss
mailing list</a><br>
</body></html>
|
