diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-July/006829.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-July/006829.html | 145 |
1 files changed, 145 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-July/006829.html b/zarb-ml/mageia-dev/2011-July/006829.html new file mode 100644 index 000000000..6e95d1149 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-July/006829.html @@ -0,0 +1,145 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] kernel 3.0 is a big mistake in cauldron + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20kernel%203.0%20is%20a%20big%20mistake%20in%20cauldron&In-Reply-To=%3C1310913446.36015.YahooMailNeo%40web161713.mail.bf1.yahoo.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="006825.html"> + <LINK REL="Next" HREF="006838.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] kernel 3.0 is a big mistake in cauldron</H1> + <B>Radu-Cristian FOTESCU</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20kernel%203.0%20is%20a%20big%20mistake%20in%20cauldron&In-Reply-To=%3C1310913446.36015.YahooMailNeo%40web161713.mail.bf1.yahoo.com%3E" + TITLE="[Mageia-dev] kernel 3.0 is a big mistake in cauldron">beranger5ca at yahoo.ca + </A><BR> + <I>Sun Jul 17 16:37:26 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="006825.html">[Mageia-dev] kernel 3.0 is a big mistake in cauldron +</A></li> + <LI>Next message: <A HREF="006838.html">[Mageia-dev] kernel 3.0 is a big mistake in cauldron +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6829">[ date ]</a> + <a href="thread.html#6829">[ thread ]</a> + <a href="subject.html#6829">[ subject ]</a> + <a href="author.html#6829">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE> +><i>and both i586 and x86_64 kernels were tested on a i7-860 workstation and +</I>><i>on a Acer TravelMate 5720  laptop before submitting to the buildsystem... +</I> + +tmb, for the Wi-Fi issue, I identified the culprit. + +With the 2.6.38 kernel, dkms-broadcom-wl was useless (Broadcom STA + +is a hybrid driver, including a binary blob from upstream, but in Mageia + +dkms-broadcom-wl is not like Ubuntu's broadcom-wl, it still asks for +firmware, which is stupid, as STA is redistributable; eventually, I had to use + +fw-cutter and to populate /lib/firmware/b43 with *.fw, so that BCM4311 rev.1 +works w/o dkms-broadcom-wl!). + +With the 3.0.0 kernel, dkms-broadcom-wl tries to build a module after booting, +but it doesn't work at all (I haven't checked what it does, whether it has the binary + +blob or not, if it logs messages, etc.), and it blocks b43. + +Uninstalling dkms-broadcom-wl still didn't fix the issue, but again, I have not investigated +-- maybe there are some remnants or smth that impedes b43. + +Still, with the 3.0.0 kernel, my TravelMate 5310 fails to shutdown or reboot, when told +so kdeinit4 takes 100% CPU and the system becomes unresponsive. Back to 2.6.38, +everything is smooth again. + +Experimenting with various packages and their breakages is one thing, but the Linux +kernel is my personal enemy, I hate the too many changes between one release and + +the next one, it's practically impossible to design & run any relevant regression tests. + +If I were in charge with any distro's policy, I would be particularly conservative +when comes to the kernel (e.g. slackware-current is still on 2.6.38.7) + +><i>There is no forcing... +</I>><i>the old kernel is still installed so you can use it if you need. +</I> +><i> +</I>><i>And if you dont like automatic kernel upgrades, uninstall kernel-*-latest +</I> + +I did so, but w/o kernel-*-latest I suppose I won't get any kernel update at all?! +This is not what I intended... + + +><i>its always good to know my work is appreciated... +</I> + +Your work in patching and packing and so on is one thing, and the policy of +when the kernel goes and where it goes and what kind of kernel-*-latest + +metapackages exist is a different thing. I still believe that, even in cauldron, +there should be 2 distinct kernel "branches", not a unique kernel-*-latest path. +(Maybe I'm influenced by the conservative way Slackware is approaching the kernels.) +(Or maybe I'm just getting old.) + +R-C aka beranger + +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="006825.html">[Mageia-dev] kernel 3.0 is a big mistake in cauldron +</A></li> + <LI>Next message: <A HREF="006838.html">[Mageia-dev] kernel 3.0 is a big mistake in cauldron +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6829">[ date ]</a> + <a href="thread.html#6829">[ thread ]</a> + <a href="subject.html#6829">[ subject ]</a> + <a href="author.html#6829">[ 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> |