#initrd — Public Fediverse posts

Half of the support for the #initrd (not to be confused with #initramfs!) was removed from #Linux 7.0 through a #vfs merge from @brauner:

https://git.kernel.org/torvalds/c/996812c453cafa042f2e674738dbf8fa495661f3 and https://git.kernel.org/torvalds/c/ef12d0573a7f5e7a495e81d773ae5f3e98230cd4

""Remove the deprecated linuxrc-based initrd code path and related dead code. The linuxrc initrd path was deprecated in 2020 and this series completes its removal. If we see real-life regressions we'll revert. […]

The no-op load_ramdisk= and prompt_ramdisk= parameters are dropped, and noinitrd and ramdisk_start= gain deprecation warnings.

Initramfs is entirely unaffected. The non-linuxrc initrd path (root=/dev/ram0) is preserved but now carries a deprecation warning targeting January 2027 removal""

#Kernel #LinuxKernel

Half of the support for the #initrd (not to be confused with #initramfs!) was removed from #Linux 7.0 through a #vfs merge from @brauner:

https://git.kernel.org/torvalds/c/996812c453cafa042f2e674738dbf8fa495661f3 and https://git.kernel.org/torvalds/c/ef12d0573a7f5e7a495e81d773ae5f3e98230cd4

""Remove the deprecated linuxrc-based initrd code path and related dead code. The linuxrc initrd path was deprecated in 2020 and this series completes its removal. If we see real-life regressions we'll revert. […]

The no-op load_ramdisk= and prompt_ramdisk= parameters are dropped, and noinitrd and ramdisk_start= gain deprecation warnings.

Initramfs is entirely unaffected. The non-linuxrc initrd path (root=/dev/ram0) is preserved but now carries a deprecation warning targeting January 2027 removal""

#Kernel #LinuxKernel

Half of the support for the #initrd (not to be confused with #initramfs!) was removed from #Linux 7.0 through a #vfs merge from @brauner:

https://git.kernel.org/torvalds/c/996812c453cafa042f2e674738dbf8fa495661f3 and https://git.kernel.org/torvalds/c/ef12d0573a7f5e7a495e81d773ae5f3e98230cd4

""Remove the deprecated linuxrc-based initrd code path and related dead code. The linuxrc initrd path was deprecated in 2020 and this series completes its removal. If we see real-life regressions we'll revert. […]

The no-op load_ramdisk= and prompt_ramdisk= parameters are dropped, and noinitrd and ramdisk_start= gain deprecation warnings.

Initramfs is entirely unaffected. The non-linuxrc initrd path (root=/dev/ram0) is preserved but now carries a deprecation warning targeting January 2027 removal""

#Kernel #LinuxKernel

Half of the support for the #initrd (not to be confused with #initramfs!) was removed from #Linux 7.0 through a #vfs merge from @brauner:

https://git.kernel.org/torvalds/c/996812c453cafa042f2e674738dbf8fa495661f3 and https://git.kernel.org/torvalds/c/ef12d0573a7f5e7a495e81d773ae5f3e98230cd4

""Remove the deprecated linuxrc-based initrd code path and related dead code. The linuxrc initrd path was deprecated in 2020 and this series completes its removal. If we see real-life regressions we'll revert. […]

The no-op load_ramdisk= and prompt_ramdisk= parameters are dropped, and noinitrd and ramdisk_start= gain deprecation warnings.

Initramfs is entirely unaffected. The non-linuxrc initrd path (root=/dev/ram0) is preserved but now carries a deprecation warning targeting January 2027 removal""

#Kernel #LinuxKernel

So I tried out #LinuxMint with the default Cinnamon Desktop for the last few days. It was quite nice. I would recommend it for those new to Linux. The desktop is sweet perfection, like #XFCE.

But sound did not work on my new laptop. Updating the kernel and found what seems like every possible bug with Linux Mint. Now I have no wireless AND no sound. For some reason, I can't get into the Grub boot menu to revert changes. Gone are the days when I can simply edit a text file for boot order and init.d startup. Searching forums and two days of debugging and reinstalling, trying to work with the #systemd and #initrd layers made me give it up. Seems like modularity between systems got tangled up like cold spaghetti in the fridge overnight.

#FreeBSD it is. #UNIX my old friend, you have always been loyal and true. At least I can fix what I break. Downloading now.

Автоматический выбор версии NVIDIA драйвера при загрузке Linux дистрибутива PocketHandyBox

Проприетарные драйвера NVIDIA для Linux по умолчанию не предполагают возможности соседства нескольких версий в одной файловой системе в классических дистрибутивах. Но эта проблема может быть легко решена в модульных дистрибутивах путем создания отдельных squashfs модулей с разными версиями NVIDIA драйверов. Таким образом получаем рабочий драйвер NVIDIA сразу после запуска и без дополнительных манипуляций.

https://habr.com/ru/articles/961400/

#nvidia #linux #debian #initrd #initramfs

Fedora 43 to Use Zstd Compression for Faster Boot and Smaller Initrd #fedora43 #zstd #initrd #initramfs #fastboot #linux #dracut
https://ostechnix.com/fedora-43-initrd-zstd-compression/

Fedora 43 to Use Zstd Compression for Faster Boot and Smaller Initrd #fedora43 #zstd #initrd #initramfs #fastboot #linux #dracut
https://ostechnix.com/fedora-43-initrd-zstd-compression/

Fedora 43 to Use Zstd Compression for Faster Boot and Smaller Initrd #fedora43 #zstd #initrd #initramfs #fastboot #linux #dracut
https://ostechnix.com/fedora-43-initrd-zstd-compression/

Fedora 43 to Use Zstd Compression for Faster Boot and Smaller Initrd #fedora43 #zstd #initrd #initramfs #fastboot #linux #dracut
https://ostechnix.com/fedora-43-initrd-zstd-compression/

Fedora 43 to Use Zstd Compression for Faster Boot and Smaller Initrd #fedora43 #zstd #initrd #initramfs #fastboot #linux #dracut
https://ostechnix.com/fedora-43-initrd-zstd-compression/

Ubuntu 25.10 will use Dracut

While Ubuntu 25.04 is still ongoing development, there has been progress in switching from initramfs-tools to Dracut. Those tools both handle initrd generation for booting into the Linux kernel in preparation for the full system boot. The Ubuntu engineers are working hard to migrate such tool to Dracut to ensure better bootstrapping by reducing hard-coded logic as much as possible.

Initially, Ubuntu 25.04 would have used Dracut as the initrd generator, but the work wasn’t complete yet, so the Ubuntu engineers have delayed the migration to after Ubuntu 25.04 gets released so that the next version of Ubuntu uses Dracut completely.

However, you have an opportunity to try out Dracut in Ubuntu 25.04 when it gets released. This is so that you can provide feedback to the Ubuntu team about your experience with the Dracut integration.

Ubuntu 25.04 will be the last version that uses initramfs-tools as the default initrd generator, with the October release of Ubuntu being the first version that uses Dracut. This is going to be exciting news for the next year’s Ubuntu LTS release that will be out in the next April.

https://audiomack.com/aptivi/song/ubuntu-2510-will-use-dracut

#2504 #2510 #Dracut #Initramfs #InitramfsTools #Initrd #news #Plucky #PluckyPuffin #Puffin #Tech #Technology #Ubuntu #Ubuntu2504 #Ubuntu2504Plucky #Ubuntu2504PluckyPuffin #Ubuntu2510 #update

Ubuntu 25.10 will use Dracut

While Ubuntu 25.04 is still ongoing development, there has been progress in switching from initramfs-tools to Dracut. Those tools both handle initrd generation for booting into the Linux kernel in preparation for the full system boot. The Ubuntu engineers are working hard to migrate such tool to Dracut to ensure better bootstrapping by reducing hard-coded logic as much as possible.

Initially, Ubuntu 25.04 would have used Dracut as the initrd generator, but the work wasn’t complete yet, so the Ubuntu engineers have delayed the migration to after Ubuntu 25.04 gets released so that the next version of Ubuntu uses Dracut completely.

However, you have an opportunity to try out Dracut in Ubuntu 25.04 when it gets released. This is so that you can provide feedback to the Ubuntu team about your experience with the Dracut integration.

Ubuntu 25.04 will be the last version that uses initramfs-tools as the default initrd generator, with the October release of Ubuntu being the first version that uses Dracut. This is going to be exciting news for the next year’s Ubuntu LTS release that will be out in the next April.

#2504 #2510 #Dracut #Initramfs #InitramfsTools #Initrd #news #Plucky #PluckyPuffin #Puffin #Tech #Technology #Ubuntu #Ubuntu2504 #Ubuntu2504Plucky #Ubuntu2504PluckyPuffin #Ubuntu2510 #update

Ubuntu 25.10 will use Dracut

While Ubuntu 25.04 is still ongoing development, there has been progress in switching from initramfs-tools to Dracut. Those tools both handle initrd generation for booting into the Linux kernel in preparation for the full system boot. The Ubuntu engineers are working hard to migrate such tool to Dracut to ensure better bootstrapping by reducing hard-coded logic as much as possible.

Initially, Ubuntu 25.04 would have used Dracut as the initrd generator, but the work wasn’t complete yet, so the Ubuntu engineers have delayed the migration to after Ubuntu 25.04 gets released so that the next version of Ubuntu uses Dracut completely.

However, you have an opportunity to try out Dracut in Ubuntu 25.04 when it gets released. This is so that you can provide feedback to the Ubuntu team about your experience with the Dracut integration.

Ubuntu 25.04 will be the last version that uses initramfs-tools as the default initrd generator, with the October release of Ubuntu being the first version that uses Dracut. This is going to be exciting news for the next year’s Ubuntu LTS release that will be out in the next April.

https://audiomack.com/aptivi/song/ubuntu-2510-will-use-dracut

#2504 #2510 #Dracut #Initramfs #InitramfsTools #Initrd #news #Plucky #PluckyPuffin #Puffin #Tech #Technology #Ubuntu #Ubuntu2504 #Ubuntu2504Plucky #Ubuntu2504PluckyPuffin #Ubuntu2510 #update

Ubuntu 25.10 will use Dracut

While Ubuntu 25.04 is still ongoing development, there has been progress in switching from initramfs-tools to Dracut. Those tools both handle initrd generation for booting into the Linux kernel in preparation for the full system boot. The Ubuntu engineers are working hard to migrate such tool to Dracut to ensure better bootstrapping by reducing hard-coded logic as much as possible.

Initially, Ubuntu 25.04 would have used Dracut as the initrd generator, but the work wasn’t complete yet, so the Ubuntu engineers have delayed the migration to after Ubuntu 25.04 gets released so that the next version of Ubuntu uses Dracut completely.

However, you have an opportunity to try out Dracut in Ubuntu 25.04 when it gets released. This is so that you can provide feedback to the Ubuntu team about your experience with the Dracut integration.

Ubuntu 25.04 will be the last version that uses initramfs-tools as the default initrd generator, with the October release of Ubuntu being the first version that uses Dracut. This is going to be exciting news for the next year’s Ubuntu LTS release that will be out in the next April.

#2504 #2510 #Dracut #Initramfs #InitramfsTools #Initrd #news #Plucky #PluckyPuffin #Puffin #Tech #Technology #Ubuntu #Ubuntu2504 #Ubuntu2504Plucky #Ubuntu2504PluckyPuffin #Ubuntu2510 #update

Ubuntu 25.10 will use Dracut

While Ubuntu 25.04 is still ongoing development, there has been progress in switching from initramfs-tools to Dracut. Those tools both handle initrd generation for booting into the Linux kernel in preparation for the full system boot. The Ubuntu engineers are working hard to migrate such tool to Dracut to ensure better bootstrapping by reducing hard-coded logic as much as possible.

Initially, Ubuntu 25.04 would have used Dracut as the initrd generator, but the work wasn’t complete yet, so the Ubuntu engineers have delayed the migration to after Ubuntu 25.04 gets released so that the next version of Ubuntu uses Dracut completely.

However, you have an opportunity to try out Dracut in Ubuntu 25.04 when it gets released. This is so that you can provide feedback to the Ubuntu team about your experience with the Dracut integration.

Ubuntu 25.04 will be the last version that uses initramfs-tools as the default initrd generator, with the October release of Ubuntu being the first version that uses Dracut. This is going to be exciting news for the next year’s Ubuntu LTS release that will be out in the next April.

https://audiomack.com/aptivi/song/ubuntu-2510-will-use-dracut

#2504 #2510 #Dracut #Initramfs #InitramfsTools #Initrd #news #Plucky #PluckyPuffin #Puffin #Tech #Technology #Ubuntu #Ubuntu2504 #Ubuntu2504Plucky #Ubuntu2504PluckyPuffin #Ubuntu2510 #update

To share the results:

/etc/initramfs-tools/initramfs.conf (or a .d if you want)
MODULES=dep
COMPRESS=zstd
COMPRESSLEVEL=19

gets the #debian #initrd #boot image down to ~20 MiB

Main system still doesn't start a window manager; I might need to figure out how to rebuild #dkms -- or reinstall the kernel packages.

Edit: Uninstalling & reinstalling the non-most-current kernel & headers did the trick. If you uninstall the newest image, the headers pull in the unsigned kernel as dep. Same size, so..

Погружаемся в initrd

Приветствую! Меня зовут Валерий, я инженер операционных систем в секторе клиентской и мобильной ОС. Сегодня хочу затронуть фундаментальные вопросы: - процесс загрузки операционной системы в автоматизированное рабочее место (АРМ), - распаковку начального образа оперативной памяти, - подробный разбор initrd, что это такое и с чем его едят. Этот материал поможет понять как природу загрузки ОС Astra Linux Special Edition в частности, так и загрузку GNU/Linux в целом.

https://habr.com/ru/companies/astralinux/articles/851056/

#initrd #grub #скрипт #udev #переменные_окружения #каталог #операционная_система #автоматизированное_рабочее_место #оперативная_память

Ryan Does #NixOS - Part 7

I was able to generate the required files for #iPXE booting a #flake (#kernel + #initrd w/ #squashfs + iPXE script file), but kept running into issues with the kernel "unable to mount root fs" or "initramfs unpacking failed: invalid magic at start of compressed archive". What is weird is that https://github.com/nix-community/nixos-images/ when booted through netboot.xyz works just fine, if I grab the underlying kernel + initrd + iPXE script on MULTIPLE #systems , it fails with the latter message.

This is really boggling my mind as I thought there was data corruption happening, but I am more likely to believe something is happening within NixOS's #zstd compression, or with that building process.

@brokenix it's been quite a while that #Dropbear isn't the default in #NixOS' #initrd anymore. See this commit for more details and the reasoning behind this decision:
https://github.com/NixOS/nixpkgs/commit/d930466b7728e5515991cb73c060fc3f32bdc001

#OpenSSH

Linux boot times speed-up at works! 🚀

"We aim to capitalize on the cryptographic checks already performed on the kernel and initrd images during the secure boot process.

As a result, we can significantly improve the boot speed without compromising system security." ~Alessandro Carminati (Red Hat)

=> https://lore.kernel.org/lkml/202309141[email protected]/

#Linux #kernel #boot #development #speed #RedHat #initrd

@dagaz In the end I am trying to make the IT world a bit better by trying to point out: that the place where you type in your #Linux #luks disk #passphrase is not safe and could be better protected if the #boot and upgrade process would be implemented slightly different with the ability to ship #distribution, #organization and device #signatures on #kernel and #initrd.
Then we can really start and demand signature editing in every firmware!

Как известно, при работе с проприетарным драйвером nvidia-drivers , невозможно использовать фреймбуфер через nouveau  или доступный в ядре фреймбуфер для NVIDIA, так как они конфликтуют с драйвером, который используется в X-сервере. Добиться работы фреймбуфера в консоли без костылей типа выгрузки nouveau перед запуском X-сервера можно только используя uvesafb .

Однако, подавляющее большинство инструкций описывают настройку uvesafb в сочетании с initrd, что бесполезно, если ядро собрано без его поддержки.

Само собой, необходимо выполнить все инструкции, которые необходимы для работы драйверов от NVIDIA без конфликтов:

• Включить поддержку модулей

  [*] Enable loadable module support --->

• Включить MTRR

  Processor type and features --->    [*] MTRR (Memory Type Range Register) supportProcessor type and features --->    [*] MTRR (Memory Type Range Register) support

• Отключить встроенные драйверы ядра для фреймбуфера на видеокартах NVIDIA

  Device Drivers --->    Graphics support --->        Frame buffer Devices --->             Support for frame buffer devices --->            < >   nVidia Framebuffer Support            < >   nVidia Riva support

• Собрать DRM модулем или вовсе выключить его в ядре (NVIDIA использует свой DRM)

  Device drivers --->    Graphics support --->        < > Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)

  У меня при встроенном модуле DRM в dmesg  можно было наблюдать ошибки и конфликт с драйвером nvidia , но как ни странно, в итоге всё работало. Когда я убрал модуль, вместе с ним пропали и ошибки.

Здесь путь с обычной инструкцией расходится, так как мы не используем initrd при загрузке. В ядре нужно включить поддержку uvesafb в виде модуля:

Device Drivers  --->     Connector - unified userspace  kernelspace linker  --->    Graphics support  --->        [*] Support for frame buffer devices  --->            [*]   Enable firmware EDID               Userspace VESA VGA graphics support            [*]   Simple framebuffer support

И собрать нужные для uvesafb пакеты:

emerge -aq v86d

Теперь прописываем загрузку модуля uvesafb с параметрами:

# ...modules="uvesafb"# ...module_uvesafb_args="mode_option=1920x1080-24 mtrr=2 scroll=ywrap"

Альтернативой module_uvesafb_args  может быть создание конфига в /etc/modprobe.d/  c такими же параметрами:

options uvesafb mode_option=1920x1080-24 mtrr=2 scroll=ywrap

Здесь важно задать параметры, подходящие под вашу текущую конфигурацию системы:

• mode_option — разрешение и глубина цвета (также можно указать частоту обновления в виде 1920×1080-24@60 , но лучше оставить автоматическое значение)
• mtrr — доступный режим MTRR. Узнать, какие режимы доступны можно в файле /proc/mtrr. Таблица соответствия выглядит так:

  0 - Disabled (equivalent to nomtrr) (default)1 - Uncacheable2 - Write-back3 - Write-combining4 - Write-through

• scroll — режим прокрутки. Типичное значение — ywrap. Посмотреть подробнее можно в документации.

Можно собирать ядро и устанавливать его. Если у вас используется отдельный раздел под /boot , то нужно сначала смонтировать его: mount /boot. Также, если были убраны какие-то модули, а версия ядра не менялась, не лишним может быть и удаление установленных в данный момент модулей из /lib64/modules/. Сделать это можно, например, так:

rm -rf /lib64/modules/`uname -r`

В /usr/src/linux выполняем:

make -j4 && make modules_install && make install

Теперь подправим конфиг GRUB2 (для GRUB первой версии настройки будут другими):

# ...GRUB_GFXMODE=1920x1080# ...GRUB_GFXPAYLOAD_LINUX=keep

Кстати, здесь мы заодно и в GRUB2 выставили высокое разрешение первым параметром. Остаётся сгенерировать новый конфиг для GRUB2:

grub2-mkconfig -o /boot/grub/grub.cfg

Не стоит забывать и о том, что не лишним будет пересобрать драйвера — особенно, если изменилась версия ядра:

emerge -aq nvidia-drivers

Отмонтируем /boot  и перезагружаемся, чтобы проверить.

Удачи!

Полезная информация:

• http://gentoo-en.vfose.ru/wiki/Framebuffer
• http://wiki.gentoo.org/wiki/NVidia/nvidia-drivers/ru
• http://wiki.gentoo.org/wiki/Uvesafb
• https://www.kernel.org/doc/Documentation/fb/uvesafb.txt
• http://wiki.gentoo.org/wiki/GRUB2#Configuration
• https://wiki.archlinux.org/index.php/uvesafb

https://skobk.in/2015/01/gentoo-nvidia-drivers-uvesafb-framebuffer-without-initrd/