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/010543.html | 141 +++++++++++++++++++++++++++ 1 file changed, 141 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-December/010543.html (limited to 'zarb-ml/mageia-dev/2011-December/010543.html') diff --git a/zarb-ml/mageia-dev/2011-December/010543.html b/zarb-ml/mageia-dev/2011-December/010543.html new file mode 100644 index 000000000..b2b459733 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-December/010543.html @@ -0,0 +1,141 @@ + + + + [Mageia-dev] Issues with dracut + + + + + + + + + +

[Mageia-dev] Issues with dracut

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Sat Dec 17 00:19:55 CET 2011 +

+
+ +
'Twas brillig, and JA Magallon at 16/12/11 23:08 did gyre and gimble:
+> 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
+
+Well it's in a udev rule so it's not 100% predictable what it's using.
+I'll have a wee look just now.
+
+Col
+
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + + + + + + + + +
+

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