You are here

Mailing List Archive - From September 2014

Mail List Archive (Current)     Mail List Archive (up to September 2014)

[EdLUG] Module parameters are different from cmdline pre { white-space: pre-wrap; /* css-2.1, curent FF, Opera, Safari */ }

[EdLUG] Module parameters are different from cmdline

Edinburgh Linux Users Group edlug at
Wed Dec 28 23:01:03 UTC 2016

On 2016.12.28 21:12, Edinburgh Linux Users Group wrote:
> Hi Roy,
> I see your point. Interesting, I see the entries from i915 (about
> tainting
> kernel) Before any root fs mounting. Which means that it's either
> built
> into the kernel or should be inside initramfs.
> Also, apart from the config, if I try to run this command:
> *$ grep i915 /lib/modules/4.8.0-32-generic/modules.builtin*
> It gives no output, which means that i915 must be a separate module.
> However, when I try to look into initramfs:
> *$ cpio -i < initrd.img-4.8.0-32-generic*
> I see only one file there:
> *./kernel/x86/microcode/GenuineIntel.bin*
> Now I'm a bit confused - it's loaded before root fs, it's referred as
> a
> separate module in all configs, but it's not in initrd...
> Best Regards,
> Maxim


A few things.  I've put Ubuntu 16.10 into a Virtualbox VM beside
a scrap Gentoo, so I can unpick the initramfs.

Firstly. its init script parses /proc/cmdline so the init script
in the initramfs can respond to kernel command line
parameters.  It has lots defined already.  As you have
the initrd unpacked its easy to read.
I don't see it doing anything for i915 though.

i915.ko is indeed in the initramfs. Look in it its
lib/modules/.../kernel/drivers/gpu/drm ...

I've had a look in the initramfs etc/m* and don't
see anything passing parameters to i915 but I don't
know my way around Ubuntu.


Roy Bamford.

More information about the EdLUG mailing list