diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-November/009710.html')
-rw-r--r-- | zarb-ml/mageia-dev/2011-November/009710.html | 170 |
1 files changed, 170 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-November/009710.html b/zarb-ml/mageia-dev/2011-November/009710.html new file mode 100644 index 000000000..fbbdc3b63 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-November/009710.html @@ -0,0 +1,170 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Drakx-net or NetworkManager for Mageia 2 + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Drakx-net%20or%20NetworkManager%20for%20Mageia%202&In-Reply-To=%3C4294824.mgnD843gok%40hatmehyt-cauldron.lan.littleboboy.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="009703.html"> + <LINK REL="Next" HREF="009717.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Drakx-net or NetworkManager for Mageia 2</H1> + <B>Balcaen John</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Drakx-net%20or%20NetworkManager%20for%20Mageia%202&In-Reply-To=%3C4294824.mgnD843gok%40hatmehyt-cauldron.lan.littleboboy.net%3E" + TITLE="[Mageia-dev] Drakx-net or NetworkManager for Mageia 2">mikala at mageia.org + </A><BR> + <I>Tue Nov 22 00:01:50 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="009703.html">[Mageia-dev] Drakx-net or NetworkManager for Mageia 2 +</A></li> + <LI>Next message: <A HREF="009717.html">[Mageia-dev] Drakx-net or NetworkManager for Mageia 2 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#9710">[ date ]</a> + <a href="thread.html#9710">[ thread ]</a> + <a href="subject.html#9710">[ subject ]</a> + <a href="author.html#9710">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le lundi 21 novembre 2011 16:50:35 Frank Griffin a écrit : +[...] +><i> +</I>><i> Sorry, I transposed - should have been 865. +</I> +So here the problems here seems to happend when using the *specific* mdv plugin +on mageia 1 & not with the native plugin (keyfile). + +><i> +</I>><i> > Bug 2416 was submitted when nm 0.9 (well beta) was not patched to +</I>><i> > support our sysvinit script, we'll still waiting for an answer of the +</I>><i> > initial report. +</I>><i> +</I>><i> If you look at comment #6 in this bug, you'll see that this is another +</I>><i> case of the same bug reported with NM in several other distros +</I>><i> ("disconnected for local ... (reason=3)). I'm not sure what that would +</I>><i> have to do with sysvinit script support. +</I>This bug report is against nm not respecting the NM_CONTROLLED=no cf comment +#1 +We can expect problem when 2 system are trying to interfere with the same +hardware. + + +><i> +</I>><i> > So 2160 is the only bug remaining here but i think it's probably the +</I>><i> > same bug aka it was reported when nm was not supporting sysvinit +</I>><i> +</I>><i> Please explain about nm not supporting sysvinit, or point me to the +</I>><i> relevant bug report. 2160 documented a case where the kernel reports a +</I>><i> "no link beat detected" a second or so before reporting "link beat +</I>><i> detected", and apparently NM sees the first and aborts trying to bring +</I>><i> up the interface. In the bug, I called this aggressive timeout, but it +</I>><i> may just be that NM is misinterpreting the events it sees. +</I>The bug was reported the 2011-07-15 while nm was updated to the beta 0.9 the +2011-06-14 by dmorgan. +The support for ifcfg files (aka respect the NM_CONTROLLED=no and what i was +wrongly calling support in sysvinit) was added by blino on 2011-07-31 by +patching the redhat plugin. +><i>From the log you did past in comment #1 we can see that NM & sysvinit are +</I>trying to put on the same interface. +You never explicity wrote that you have in your nm to control your wifi +interface from what you write & since i can see ifplug running i can expect +that you were using by default sysvinit script & not nm. +So we 're still in the situation « nm is not reading correctly the ifcfg file & +do not respect the NM_CONTROLLED=no solution. +Your solution was to removed nm from your system to ensure that only ifcfg are +used & that nm does not try to bring up your interface. +Regarding your comment #9 it seems their is a bug in the rhplugin & it should +be reported & assigned to blino (since he's the one to code this +functionnality). +Please note that i don't deny there's a problem eventually but if indeed it's +not working correctly with nm explicity with ifcfg- disable (aka only a lo +interface & no etho/wan/whatelse) using the native keyfile plugin (& not the +rh-plugin) we should report it upstream. + +[...] +><i> +</I>><i> I'll be doing a fresh install on the laptop experiencing the problem in +</I>><i> the next couple of days, and I'll check to see whether the problem(s) +</I>><i> still occur(s). Since no one ever posted to the bug report that it +</I>><i> might be fixed, I've simply been removing the package whenever it gets +</I>><i> reinstalled or on fresh installs. +</I>><i> +</I>><i> I'll wait to do the test to say this for sure, but IIRC I would +</I>><i> occasionally not notice that some urpmi --auto-update had reinstalled NM +</I>><i> until the wireless stopped coming up, and this was well after seeing +</I>><i> your posts about blino's patch. +</I>Then if nm does not respect the NM_CONTROLLED=no (using the rhkeyfile plugin) +then it should be reported & assigned to blino. + +[...] +><i> > Well there's a lot of packages without maintainer ... +</I>><i> +</I>><i> Well, if we're considering doing something that has the potential of +</I>><i> breaking peoples' systems, it would make sense (at least to me) to tread +</I>><i> carefully unless we have someone on hand that can deal with the +</I>><i> problems, no ? +</I>Here our bug triager team looks directly @ the commits to find someone which +might be able to help on that +(because if we're looking @ <A HREF="http://pkgsubmit.mageia.org/data/unmaintained.txt">http://pkgsubmit.mageia.org/data/unmaintained.txt</A> +there's a lot of problematic packages without maintainer like at least grub :p +) + + +Regards, +-- +Balcaen John +Jabber-id: <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mikala at jabber.littleboboy.net</A> +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="009703.html">[Mageia-dev] Drakx-net or NetworkManager for Mageia 2 +</A></li> + <LI>Next message: <A HREF="009717.html">[Mageia-dev] Drakx-net or NetworkManager for Mageia 2 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#9710">[ date ]</a> + <a href="thread.html#9710">[ thread ]</a> + <a href="subject.html#9710">[ subject ]</a> + <a href="author.html#9710">[ 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> |