On 2018-04-14, francis.montag...@inria.fr wrote:
> Thus, for the running kernel:
>
> /bin/kernel-install add $(uname -r) /lib/$(uname -r)/vmlinuz
>
> It will regenerate the initramfs and eventually other things like the
> grub.cfg.
>
> I tested to add a
You can also use lsinitrd to show the current files in any initramfs
and/or cat out the contents of single files you see in the initramfs.
On Sat, Apr 14, 2018 at 10:43 AM, wrote:
>
> On Sat, 14 Apr 2018 15:07:28 - Grant Edwards wrote:
>> On 2018-04-14,
On Sat, 14 Apr 2018 15:07:28 - Grant Edwards wrote:
> On 2018-04-14, francis.montag...@inria.fr wrote:
>> Thus, for the running kernel:
>> /bin/kernel-install add $(uname -r) /lib/$(uname -r)/vmlinuz
> Thanks! That looks like a good option. I may prompt the
On 2018-04-14, francis.montag...@inria.fr wrote:
> On Fri, 13 Apr 2018 21:03:34 - Grant Edwards wrote:
>
>> First create a file named /etc/dracut.conf.d/foo containing the line
>> omit_drivers+="foo". Then either
>
> Bexware, this file should have .conf as suffix.
Hi.
On Fri, 13 Apr 2018 21:03:34 - Grant Edwards wrote:
> First create a file named /etc/dracut.conf.d/foo containing the line
> omit_drivers+="foo". Then either
Beware, this file should have .conf as suffix.
> 1. Rebuild the initramfs with the 'dracut' command. I haven't tested
>
On 2018-04-13, Rick Stevens wrote:
> On 04/13/2018 09:34 AM, Grant Edwards wrote:
>> What's the best way to remove the old, broken driver from the
>> initramfs so that the driver in the root filesystem is used on boot?
>>
>> Is there a way to prevent the kernel update
On 04/13/2018 09:34 AM, Grant Edwards wrote:
> On Fedora 27 with kernel recently updated to 4.15.15-300.fc27.i686, I
> ran into a problem when I installed a new version of a driver (we'll
> call "foo") in /lib/modules/$(uname -r)/kernel/drivers/[...].
>
> Doing a "rmmod foo; modprobe foo" loads