diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-December/010136.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-December/010136.html | 126 |
1 files changed, 126 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-December/010136.html b/zarb-ml/mageia-dev/2011-December/010136.html new file mode 100644 index 000000000..db96b54b9 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-December/010136.html @@ -0,0 +1,126 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] RFC: Drop mkinitrd completely in favour of dracut. + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20RFC%3A%20Drop%20mkinitrd%20completely%20in%20favour%20of%20dracut.&In-Reply-To=%3C4EDA34A9.9030007%40mageia.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="010204.html"> + <LINK REL="Next" HREF="010401.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] RFC: Drop mkinitrd completely in favour of dracut.</H1> + <B>Anssi Hannula</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20RFC%3A%20Drop%20mkinitrd%20completely%20in%20favour%20of%20dracut.&In-Reply-To=%3C4EDA34A9.9030007%40mageia.org%3E" + TITLE="[Mageia-dev] RFC: Drop mkinitrd completely in favour of dracut.">anssi at mageia.org + </A><BR> + <I>Sat Dec 3 15:39:37 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="010204.html">[Mageia-dev] RFC: Drop mkinitrd completely in favour of dracut. +</A></li> + <LI>Next message: <A HREF="010401.html">[Mageia-dev] RFC: Drop mkinitrd completely in favour of dracut. +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#10136">[ date ]</a> + <a href="thread.html#10136">[ thread ]</a> + <a href="subject.html#10136">[ subject ]</a> + <a href="author.html#10136">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 03.12.2011 08:05, Thomas Backlund wrote: +><i> Anssi Hannula skrev 3.12.2011 01:06: +</I>>><i> On 03.12.2011 00:18, Thomas Backlund wrote: +</I>>>><i> Anssi Hannula skrev 2.12.2011 23:17: +</I>>>>><i> +</I>>>>><i> Patch attached. I guess this would remain as a Mageia specific patch as +</I>>>>><i> the wanted behavior is dependant on how the distribution handles driver +</I>>>>><i> switching etc... +</I>>>><i> +</I>>>><i> Speaking of driver switching... +</I>>>><i> +</I>>>><i> Is it possible to detect missing radeon firmware in initrd in early +</I>>>><i> boot, and then switch to loading radeon with modeset=0 ? +</I>>><i> +</I>>><i> Seems doable (if a bit hacky), but unfortunately new radeon cards (at +</I>>><i> least cayman/northern islands) do not work without KMS at all (while +</I>>><i> slightly older cards like Evergreen mostly work but without any kind of +</I>>><i> 2d/3d acceleration). +</I>>><i> +</I>><i> +</I>><i> Yeah, I started thinking about those too after my post... +</I>><i> +</I>>><i> This also means that X server will fail to start since it doesn't +</I>>><i> fallback to autodetection (and therefore vesa) when the card is +</I>>><i> explicitely listed in xorg.conf. +</I>>><i> +</I>>><i> Not quite sure what is the best way forward. +</I>>><i> +</I>><i> +</I>><i> Hm, so we would need a split in detection for nonkms capable cards +</I>><i> and the rest... +</I>><i> +</I>><i> or take the easy way out and boot everyone on vesa until radeon firmware +</I>><i> is available... +</I> +Does loading of radeon modesetting kernel driver without firmware break +the boot completely, or does it just make X.org server fail to start? + +>><i> BTW, shouldn't we regenerate initrds when installing radeon-firmware for +</I>>><i> the first time? +</I>>><i> +</I>><i> +</I>><i> Yeah, I've been thinking the same, but haven't gotten around to doing it +</I>><i> yet. +</I>><i> +</I>><i> and what about nvidia* and fglrx, should they do the same ? +</I> +Well, currently we always include the KMS drivers in initrd, and when +nvidia* or fglrx is enabled we simply add nokmsboot (mga/mdv specific) +kernel parameter to avoid initrd rebuild. + +><i> and for a dkms related issue, I've also been thinking we whould +</I>><i> trigger dkms rebuild on kernel install to save time on next bootup. +</I> +That would seem reasonable, it would just be a matter of +[ -x /usr/sbin/dkms_autoinstaller ] && \ + /usr/sbin/dkms_autoinstaller start %kernelver || : +in kernel %post AFAICS... + +-- +Anssi Hannula +</PRE> + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="010204.html">[Mageia-dev] RFC: Drop mkinitrd completely in favour of dracut. +</A></li> + <LI>Next message: <A HREF="010401.html">[Mageia-dev] RFC: Drop mkinitrd completely in favour of dracut. +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#10136">[ date ]</a> + <a href="thread.html#10136">[ thread ]</a> + <a href="subject.html#10136">[ subject ]</a> + <a href="author.html#10136">[ 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> |