From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2011-December/010541.html | 122 +++++++++++++++++++++++++++ 1 file changed, 122 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-December/010541.html (limited to 'zarb-ml/mageia-dev/2011-December/010541.html') diff --git a/zarb-ml/mageia-dev/2011-December/010541.html b/zarb-ml/mageia-dev/2011-December/010541.html new file mode 100644 index 000000000..c6e924b25 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-December/010541.html @@ -0,0 +1,122 @@ + + + + [Mageia-dev] Issues with dracut + + + + + + + + + +

[Mageia-dev] Issues with dracut

+ JA Magallon + jamagallon at ono.com +
+ Sat Dec 17 00:08:36 CET 2011 +

+
+ +
On Fri, 16 Dec 2011 12:35:22 +0000
+Colin Guthrie <mageia at colin.guthr.ie> wrote:
+
+> Hiya,
+> 
+> 'Twas brillig, and JA Magallon at 16/12/11 12:06 did gyre and gimble:
+> > After those couple previous thread it looks like move to dracut is
+> > ongoing, so I decided to try it.
+> 
+> Good! This is exactly the kind of feedback we need!
+> 
+> > I found a couple problems:
+> > 
+> > - dracut inists on loading nouveau driver. With mknitrd, just booting with nokmsboot
+> >   works. Booting with a dracut generated initrd ignores that. I think it is plymouth
+> >   that forces it, even if I added 'blacklist nouveau' in a .conf file in modprobe.d:
+> > 
+> > dracut -f:
+> 
+> I'll include it but if it's blacklisted, it shouldn't ultimately be used
+> in the ramfs even if it's included. That said, it's clearly inefficient
+> to include it if it is blacklisted so we should try and fix that. Anssi,
+> could this be your code to detect the h/w that causes it to bypass any
+> blacklist checks (not sure if there are actually any blacklist checks
+> when building the initrd... not relaly looked at it much)
+> 
+> I think the nokmsboot parameter is not working in dracut because the
+> udev rule that interprets it uses the grep command and that is not
+> currently included in the ramdisk. I could hack it in easy enough, but
+> we should maybe see if a more minimal method of detecting it in the
+> commandline is possible.
+> 
+
+If its is (d)ash:
+
+CMDLINE=$(cat /proc/cmdline)
+case "${CMDLINE}" in
+    *" nokmsboot "*)
+        echo YES
+        ;;
+esac
+
+if if uses bash:
+
+CMDLINE=$(cat /proc/cmdline)
+if [[ "${CMDLINE}" == *" nokmsboot "* ]]
+then
+    echo YES
+fi
+
+
+ + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1