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
121
122
123
124
125
126
127
128
129
130
131
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Can't win - or, best of both worlds . . .!
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Can%27t%20win%20-%20or%2C%20best%20of%20both%20worlds%20.%20.%20.%21&In-Reply-To=%3C50B12249.9040902%40roadrunner.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="020201.html">
<LINK REL="Next" HREF="020230.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Can't win - or, best of both worlds . . .!</H1>
<B>Frank Griffin</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Can%27t%20win%20-%20or%2C%20best%20of%20both%20worlds%20.%20.%20.%21&In-Reply-To=%3C50B12249.9040902%40roadrunner.com%3E"
TITLE="[Mageia-dev] Can't win - or, best of both worlds . . .!">ftg at roadrunner.com
</A><BR>
<I>Sat Nov 24 20:38:49 CET 2012</I>
<P><UL>
<LI>Previous message: <A HREF="020201.html">[Mageia-dev] Can't win - or, best of both worlds . . .!
</A></li>
<LI>Next message: <A HREF="020230.html">[Mageia-dev] Can't win - or, best of both worlds . . .!
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#20226">[ date ]</a>
<a href="thread.html#20226">[ thread ]</a>
<a href="subject.html#20226">[ subject ]</a>
<a href="author.html#20226">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On 11/24/2012 02:37 AM, Anne Wilson wrote:
><i> On 24/11/2012 05:36, Frank Griffin wrote:
</I>>><i> I haven't tested since, because this was the straw on the camel's back
</I>>><i> that finally got me to pull enough teeth to find out that NM won't work
</I>>><i> in KDE without manual intervention. Once I got NM to work, I never went
</I>>><i> back.
</I>><i> For those of us still struggling to get wireless to work, can you give
</I>><i> more details, please? Sorry if you have done so somewhere else and I
</I>><i> missed it.
</I>><i>
</I>As I understand it, NM needs to parse ifcfg files to an internal format
before it can work correctly with wireless. I suspect there's a way to
do this with the NM CLI, but unless you speak NM well (I don't), it
isn't really obvious.
It's easy in GNOME, as GNOME appears to detect that it needs to be done
and does it silently. So if you have GNOME installed, just log in to
it, activate the interface from the dropdown at the top right, and log
out again.
Otherwise, from KDE, you define the interface with drakconnect (MCC),
selecting to allow NM to control it. Then install
plasma-applet-networkmanager (which is not installed by default for KDE
because NM is not supposed to be the default for wireless yet). John
Balcaen has posted that you don't need to add it to the panel (you can
invoke it directly in some way I didn't follow), but before I read that
I just used the panel toolbox widget "Add Widgets" option, search on
network", double-clicked to place it
on the panel, and invoked it from there. Just tell it to connect the
wireless, and the parse should be done automatically.
IIRC, John also posted that knetworkmanager (invoked through KDE system
settings) should do as well, but I'm not sure whether the
plasma-applet-networkmanager package was still required in that case.
Something has probably changed since I did this, since my recollection
is that the plasma applet showed a choice of interface controllers with
NM selected by default, and that did the required parse. In current
cauldron, both the applet and knetworkmanager give me the same display,
and neither mentions NM, so maybe both the panel icon and the system
settings option are executing the same thing, and the plasma package was
being used under the covers.
I'm a recent refugee to KDE from GNOME3, so there's a lot I don't find
intuitive.
There are two questions for which I don't have answers.
Once you've caused the parse to be done, you should be good to go for
wireless on subsequent reboots for that SSID. I'm not sure whether it
needs to be redone if you switch SSIDs, but the errors you get from NM
if the parse *hasn't* been done refer to errors in an "ifcfg-rh" which
appears to be independent of SSID. So maybe it's a one-time thing, or
maybe it's a one-time-per-SSID thing.
The other question is what happens for DEs other than GNOME and KDE. No
clue there.
You can find more details in bug#2160 and bug#8169.
I'm still not sure exactly what happens when. I just followed John's
suggestion to install plasma-applet-networkmanager, and then bumbled
around until I noticed it working. Apart from having to install the
applet and invoke *something* (either the applet or knetworkmanager), it
all works by magic. Just not by as much magic as it does in GNOME.
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="020201.html">[Mageia-dev] Can't win - or, best of both worlds . . .!
</A></li>
<LI>Next message: <A HREF="020230.html">[Mageia-dev] Can't win - or, best of both worlds . . .!
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#20226">[ date ]</a>
<a href="thread.html#20226">[ thread ]</a>
<a href="subject.html#20226">[ subject ]</a>
<a href="author.html#20226">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>
|
