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
|
<!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=%3C4EE7F204.1070407%40mageia.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="010136.html">
<LINK REL="Next" HREF="010426.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=%3C4EE7F204.1070407%40mageia.org%3E"
TITLE="[Mageia-dev] RFC: Drop mkinitrd completely in favour of dracut.">anssi at mageia.org
</A><BR>
<I>Wed Dec 14 01:47:00 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="010136.html">[Mageia-dev] RFC: Drop mkinitrd completely in favour of dracut.
</A></li>
<LI>Next message: <A HREF="010426.html">[Mageia-dev] RFC: Drop mkinitrd completely in favour of dracut.
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#10401">[ date ]</a>
<a href="thread.html#10401">[ thread ]</a>
<a href="subject.html#10401">[ subject ]</a>
<a href="author.html#10401">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On 03.12.2011 16:39, Anssi Hannula wrote:
><i> On 03.12.2011 08:05, Thomas Backlund wrote:
</I>>><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>><i>
</I>><i> Does loading of radeon modesetting kernel driver without firmware break
</I>><i> the boot completely, or does it just make X.org server fail to start?
</I>
Does anyone know?
>>><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>
One possibility is to make dracut record the missing firmware files
somewhere, and then in %post or in filetrigger (for /lib/firmware) check
if missing firmware got installed, and in that case run
bootloader-config --action rebuild-initrds.
>><i> and what about nvidia* and fglrx, should they do the same ?
</I>><i>
</I>><i> Well, currently we always include the KMS drivers in initrd, and when
</I>><i> nvidia* or fglrx is enabled we simply add nokmsboot (mga/mdv specific)
</I>><i> kernel parameter to avoid initrd rebuild.
</I>><i>
</I>>><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>><i>
</I>><i> That would seem reasonable, it would just be a matter of
</I>><i> [ -x /usr/sbin/dkms_autoinstaller ] && \
</I>><i> /usr/sbin/dkms_autoinstaller start %kernelver || :
</I>><i> in kernel %post AFAICS...
</I>><i>
</I>
--
Anssi Hannula
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="010136.html">[Mageia-dev] RFC: Drop mkinitrd completely in favour of dracut.
</A></li>
<LI>Next message: <A HREF="010426.html">[Mageia-dev] RFC: Drop mkinitrd completely in favour of dracut.
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#10401">[ date ]</a>
<a href="thread.html#10401">[ thread ]</a>
<a href="subject.html#10401">[ subject ]</a>
<a href="author.html#10401">[ 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>
|
