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
128
129
130
131
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Module config chaos [was Re: ANN: kernel-3.1-rc9 landing...]
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Module%20config%20chaos%20%5Bwas%20Re%3A%20ANN%3A%20kernel-3.1-rc9%0A%20landing...%5D&In-Reply-To=%3C20111006175540.7bcfb690%40werewolf.home%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="008649.html">
<LINK REL="Next" HREF="008677.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Module config chaos [was Re: ANN: kernel-3.1-rc9 landing...]</H1>
<B>JA Magallon</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Module%20config%20chaos%20%5Bwas%20Re%3A%20ANN%3A%20kernel-3.1-rc9%0A%20landing...%5D&In-Reply-To=%3C20111006175540.7bcfb690%40werewolf.home%3E"
TITLE="[Mageia-dev] Module config chaos [was Re: ANN: kernel-3.1-rc9 landing...]">jamagallon at ono.com
</A><BR>
<I>Thu Oct 6 17:55:40 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="008649.html">[Mageia-dev] ANN: kernel-3.1-rc9 landing...
</A></li>
<LI>Next message: <A HREF="008677.html">[Mageia-dev] ANN: kernel-3.1-rc9 landing...
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#8656">[ date ]</a>
<a href="thread.html#8656">[ thread ]</a>
<a href="subject.html#8656">[ subject ]</a>
<a href="author.html#8656">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Thu, 06 Oct 2011 02:58:38 +0300
Thomas Backlund <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">tmb at mageia.org</A>> wrote:
><i>
</I>><i> Hi,
</I>><i>
</I>><i> Just a small headsup...
</I>><i>
</I>><i> I've just submitted core kernel-3.1.0-0.rc9.1.mga2 to the buildsystem so
</I>><i> it will probably start showing up on the mirrors in ~ 4 - 8 hours.
</I>><i>
</I>><i> Have fun...
</I>
I had ;)...
Works fine in most of boxes, but I have a 'little' problem with others.
They have IDE disks, and 3.1 kernel insists on driving them with IDE driver
(pata_acpi) instead of SATA emulation (ata_piix). So those boxes
which booted/mounted root via UUID survived and at least booted, using
hda as root. But others where I had drives named by device /sed/sda1, did
not even boot.
For the moment I could try to change the boot to LABEL or UUID, but I think this
is a bug, or at least a change wrt previous kernels.
I don't know if it is a problem with in-kernel detection or with the generation
of initrds, as new module-init-tools make initrd scripts complain about:
direwolf:~# bootloader-config --action rebuild-initrds
WARNING: "include /lib/module-init-tools/modprobe.compat" is deprecated, please use /etc/modprobe.d
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
Some of this I think can be corrected:
/lib/module-init-tools/modprobe.compat -> /etc/modprobe.d/compat.conf
(btw, is it still needed ? it was for migration from 2.4 to 2.6 and we are at 3.1 :-O )
/etc/modules <==== I think it is unused !
/etc/modprobe.preload -> deprectated for /etc/modprobe.preload.d
/etc/modprobe.conf -> /etc/modprobe.d/modprobe.conf
or split in /etc/modprobe.d/[scsi-host.conf, usb.conf, ....]
But this late one generates other problem, /sbin/mkinitrd-mkinitrd references
/etc/modprobe.conf everywhere. If it just changes location, it is just a change,
but if it is split, ????
werewolf:~# egrep mod.*conf /sbin/mkinitrd-mkinitrd
modulefile=/etc/modules.conf <============ ?????
modulefile=/etc/modprobe.conf
modulefile=/etc/conf.modules
echo "options $module $options" >> $MNTIMAGE/etc/modprobe.conf
if [ "$module" = "zfcp" -a -f /etc/zfcp.conf ]; then
And last, are modprobe binaries in initrd the same as in distro ? If the answer is yes,
then probably the $MNTIMAGE/etc/modprobe.conf generated for initrd should also be relocated....
In short, a little chaos. I don't know if it is affecting something actually.
Hope this helps, at least as a detection of the problem.
by
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="008649.html">[Mageia-dev] ANN: kernel-3.1-rc9 landing...
</A></li>
<LI>Next message: <A HREF="008677.html">[Mageia-dev] ANN: kernel-3.1-rc9 landing...
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#8656">[ date ]</a>
<a href="thread.html#8656">[ thread ]</a>
<a href="subject.html#8656">[ subject ]</a>
<a href="author.html#8656">[ 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>
|
