diff options
| author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
|---|---|---|
| committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
| commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
| tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/attachments/20121124/7ce98fd7/attachment.html | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-master.tar archives-master.tar.gz archives-master.tar.bz2 archives-master.tar.xz archives-master.zip | |
Diffstat (limited to 'zarb-ml/mageia-dev/attachments/20121124/7ce98fd7/attachment.html')
| -rw-r--r-- | zarb-ml/mageia-dev/attachments/20121124/7ce98fd7/attachment.html | 40 |
1 files changed, 40 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/attachments/20121124/7ce98fd7/attachment.html b/zarb-ml/mageia-dev/attachments/20121124/7ce98fd7/attachment.html new file mode 100644 index 000000000..d59848824 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121124/7ce98fd7/attachment.html @@ -0,0 +1,40 @@ +<p dir="ltr">Le 24 nov. 2012 16:39, "Frank Griffin" <<a href="mailto:ftg@roadrunner.com">ftg@roadrunner.com</a>> a écrit :<br> +><br> +> On 11/24/2012 02:37 AM, Anne Wilson wrote:<br> +>><br> +>> On 24/11/2012 05:36, Frank Griffin wrote:<br> +>>><br> +>>> I haven't tested since, because this was the straw on the camel's back<br> +>>> that finally got me to pull enough teeth to find out that NM won't work<br> +>>> in KDE without manual intervention. Once I got NM to work, I never went<br> +>>> back.<br> +>><br> +>> For those of us still struggling to get wireless to work, can you give<br> +>> more details, please? Sorry if you have done so somewhere else and I<br> +>> missed it.<br> +>><br> +> 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.</p> + +<p dir="ltr">It's only happening if you choose to not change the default networkmanager configuration aka using the ifcfg plugin which means read only support for ifcfg files. I'm personally using instead the keyfile plugin (the upstream default).<br> + +><br> +> 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.<br> +</p> +<p dir="ltr">> 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<br> + +> on the panel, and invoked it from there. Just tell it to connect the wireless, and the parse should be done automatically.<br> +><br> +> 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. </p> +<p dir="ltr">knetworkmanager is just the name of the source rpm and the original binary which is long dead...So currently it's just a virtual package pulling the plasma applet package. </p> +<p dir="ltr">> 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.<br> +</p> +<p dir="ltr">They're the same thing indeed. <br> +> I'm a recent refugee to KDE from GNOME3, so there's a lot I don't find intuitive.<br> +><br> +> There are two questions for which I don't have answers.<br> +><br> +> 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.<br> + +></p> +<p dir="ltr">Suggest here: drop all ifcfg configuration files and switch to keyfile plugin. <br> +</p> |