#grub — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #grub, aggregated by home.social.
-
"THAT'S MY OPINION" 🗣️#birbsday
Unfortunately I didn't have a long enough lens, so this is a HEAVY crop and the quality isn't great. But it made me giggle! 😂
I'm not 100% sure what kind of birds they are - but I believe they are in the Tit family. ✨#photography #amateurphotography #birds
#tit #birdsofmastodon #birdphotography #birdsday #wildlife #grub #insect #wildlifephotography #urbangarden #nature #urbannature #italy #italia #bologna #europe #canonphotography #canon #meme -
-
If you use #Linux on your desktop, the foundation you *should* support is not the Linux foundation, but rather the @XOrgFoundation AKA freedesktop.org. The X.Org foundation is the home of:
- #X11
- #Wayland
- #Mesa
- #Noveau
- #DBus
- #GRUB
- #GStreamer
- #PulseAudio
- #PipeWire
- #NetworkManager
- the Linux kernel graphics subsystem
- the #XDG base directory specification
- and more!Also, development of what would later become #Flatpak started here.
These projects have a way stronger impact on your day-to-day computing experience than anything managed by the Linux foundation.
-
Tanto #GOG como #Epic van a lanzar sendas tiendas para #GNU.
No ha hecho falta una base de usuarios muy grande para que se decidan a hacerlo.
Sí que ha hecho falta alguien que creyera en un sistema más justo.
#goodoldgames #epicgames #valve #steamdeck #steammachine #steamos #linux #glibc #x11 #xorg #wayland #mesa #gcc #kde #gnome #bash #grub #wine #dxvk #d7vk #proton
-
Actualicé mi @archlinux y pasó lo que tenía que pasar:
- comenzó a reiniciarse de forma random.
- actualicé de nuevo: nueva versión del núcleo.
- se apagó, se rompió el grub.
- reinicié con un live.
- no estaba el núcleo compilado en el /boot.
- hice chroot al / de mi instalación.
- reinstalé el núcleo Linux, los firmwares, el grub, su configuración, y creé el ramdisk.
- reinicié y acá está andando.... nada del otro mundo, bah 😅
-
Successfully loading Haiku from Grub now (I used to use reFind). Awesome!
-
This is why you don't use #Limine.
https://slopscan.ava.pet/repo/https%3A%2F%2Fgithub%2Ecom%2FLimine%2DBootloader%2FLimine
Why is AI being used to maintain a bootloader of all things? One of the most CRITICAL parts to use a system? One broken AI update and your system is unbootable without a backup USB.
Just go use #GRUB. It's not that hard to use, and if you're doing OSDev, it's generally easier to use multiboot(2) anyway.
Good they moved from #Codeberg a while back. Lots of recent commits have Claude all over them.
-
Fun fact.
Btrfs c'est bien, ça te fais gagner de la place (et pas qu'un peu)(et les Snapshot, mais pas encore testé).Mais grub et os-prober, il aime pas.
C'est un comble quand même, ça fais des années que le format existe, et Grub ne sait même pas aller chercher dans des sous-volumes les kernel, initramfs et tout le toutim...Faut faire à la mano, configurer une nouvelle entrée dans /etc/grub.d, pour qu'il veuille bien rajouter ton nouvel OS dans son menu...
J'ai mis une plombe à dépatouiller le truc.
(Appartement, Arch a os-prober-btrfs, mais pas Debian...)
-
Linux, GRUB, btrfs - It seems that for some reason the system thinks that every boot fails and waits always for the 30 seconds on boot. Yeah, I know you can configure the failure timeout to shorter time. But I think it’s “wrong fix”. Why the status of previous boot doesn’t get correctly updated is the real question. #Linux #GRUB #BTRFS #boot
-
After so many years of using #GNU / #Linux I finally got the curiosity of compiling the Kernel and customize it.
It is amazing how easy it is! and by creating a second #grub entry its quite safe.
Here are the steps:
1) Clone the git repo
2) Copy your current's distribution .config file
3) Customize & upgrade the config.
4) Compile it
5) Install the modules
6) Copy the kernel boot image into
7) Generate the file system image
8) Create a grub entry.I recommend it for learning 😀
-
Avvio ritardato su linux Mint 22.3
Ho installato Linux Mint 22.3 su un vecchio pc portatile Lenovo. Tutto bene. Al riavvio, però, passano 30 secondi prima di iniziare il boot. Certo, premendo invio l’avvio prosegue subito, ma è seccante. Cambiare il timeout nel file di grub non è sufficiente.
La soluzione è qui.
In breve, come root:
vi /etc/default/grub
Modificate e/o aggiungete le seguenti righe:
GRUB_TIMEOUT_STYLE=menu
GRUB_TIMEOUT=3
GRUB_RECORDFAIL_TIMEOUT=$GRUB_TIMEOUTChiudete e salvate e aggiornate il file di configurazione di grub con il comando:
update-grub
Riavviate per verificare che tutto sia come voluto.
#avvio #boot #grub #linux #mint223 -
#RISC_OS folks: New #MerlinProject YouTube video update with 3D Graphics API and RISC OS Merlin booting via #GRUB on #x86 and #KVM! More details and link to the video here:
-
История о том, как я в Debian машину времени вкрячивал
Как в Debian настроить Btrfs, Snapper и grub-btrfs так, чтобы после неудачного обновления вернуть рабочую систему за несколько минут.
-
Neues von Minetosh online (https://www.minetoshsoft.com):
Linux neben Mac OS-X auf einem Apple Rechner installieren
Ich habe zum Thema Installation eines Multi-Boot Mac eine kleine Anleitung verfasst, die ich unter dem untenstehenden Link als PDF-Datei zum Download zur Verfügung stelle. Diese Anleitung behandelt die Vorbereitung, die Installation von Linux neben OS-X und einige Post-Installations-Hinweise (#grub, Treiberinstallation, SSD-Optimierung).
Die Datei kann hier heruntergeladen werden: https://www.minetoshsoft.com/nmzeugs/index.php#linux #LinuxMint #mac #imac #macbook #MateDesktop #LinuxSoftware #linuxmac #multiboot #minetosh #OSX #ssd #InstallationsAnleitung #InstallationTuturial #GuideInstallation
-
Hello les mastonautes !
S’il y a des experts Linux dans le coin, on a un souci au boulot avec grub et le secure boot :
Nos machines sont en dual boot RedHat 9 / Windows 11. Dans la journée, le boot par défaut est Windows. Afin de mettre à jour Linux, les machines démarrent automatiquement à 4H00 et on a configuré grub pour que entre 4H00 et 7H00 le boot par défaut soit Linux.
Cependant, quand on active le Secure Boot, la variable ${HOUR} reste vide après avoir chargé le module datehook.Nous avons retourné une grosse partie d'internet à ce sujet, passer pas mal de temps à expérimenter sans succès.
Y aurait-il dans l'assistance des experts grub / secure boot qui pourraient éclairer nos lanternes ?
Merci d'avance !
-
[July - now not possible (except possibly with higher RAM)]
Wow! Congratulations!
Live Virtualization is possible in Kicksecure!https://www.kicksecure.com/wiki/Dev/user-sysmaint-split
(Live | Persistent | Testing)
https://www.kicksecure.com/wiki/Grub-liveDevelopment for greater stability needed #fundinternetfreedom
liblxqt5networka5t64
https://pkgs.org/download/libqt5-network
* [ALERT] Lxqt gui conflicts with Security-Misc!
(disable if upgrading and keep disabled if updating Trixie)
* Have you allocated enough disk space?
Size of Trixie upgrade appears to overwhelm resources.
recommend targeted updates:
apt install –only-upgrade <package>
* comment out non-free in Kicksecure repo
* consider disabling repo until “dummy” dependencies and other issues are cleared up#Debian #tech #Privacy #Security #ConfidentialComputing #tor #Linux #Qemu #grub #virtualization
@debian @whonix -
I’ve got a #laptop which I have installed #Linux mint on to dual boot with #Windows11.
The #grub #BootManager has been set up with the first option being Linux. Recently Windows installed an update, and everything went well until the point where it said that the system will now restart.
The boot manager came up on the screen and then the computer just crashed nothing I could do could prevent this.I’m wondering if I were to change the order of operating system systems on the boot manager to have Windows as the first option that this would cure it. How can I do this? When I turn it on the boot manager comes up but only stays on the screen for about two seconds before the computer crashes.
Comments and suggestions would be appreciated. 😊
-
🚛 Neuer Beitrag auf ChristiansBlog.eu
Nextcloud-Server von einer USB-NVMe auf eine interne SATA-Festplatte migrieren – ohne Neuinstallation
Ein Praxis-Tutorial zur Migration eines laufenden Debian- und Nextcloud-Servers von einer USB-NVMe auf eine interne SATA-Festplatte – inklusive GRUB, rsync, fstab und typischer Fehlerfallen.
🔗 https://christiansblog.eu/post/tutorial/serverumzug/
#NextCloud #Debian #Linux #Server #Migration #NVMe #SATA #Apache #GRUB #Tutorial #HomeServer #Selfhosting
-
I had to rescue my
grubbootloader setup, again. Running a multi-boot system can have its downsides, I guess. So here's a note to my future self how to fix it.Scenario:
I am running a multi-boot setup with Arch (daily use), Debian (fallback) and FreeBSD (getting familiar) on different partitions and disks.
After upgrading packages in Debian, my
grubsetup was broken: Debian overwrote Arch'sgrubconfig and itsos-proberdid not generate a valid config for Arch, neither did I have a custom rule in place to get FreeBSD into the menu, since Arch is my primary system and I usegrubexclusively from there. (Note to self: Removegrubfrom Debian!)Fixing it:
I booted from an Arch installation USB I had lying around, then re-setup
grub:# mount EFI system partition mount /dev/sda1 /boot # mount Arch root partition mount /dev/nvme0n1p2 /mnt # mount EFI partition into Arch root partition at proper path mount -o bind /boot /mnt/boot # switch into Arch root filesystem arch-chroot /mnt # re-install grub into EFI system partition grub-install --target=x86_64-efi --efi-directory=/boot/ --bootloader-id=grubAfterwards, unmount and reboot - everything is back in place, hooray! :brdCool:
Docs:
-
Habe am Wochenende einen meiner Laptops von Windows 11 befreit und #linux #debian13 installiert. Eine Warnung zum #grub loader ignoriert und schwupps hatte ich nur schwarzen Bildschirm mit Eingabeaufforderung. Mit ein bisschen Rückenwind von #claude war das aber schnell behoben. Bin begeistert wie einfach das einrichten war und wie aufgeräumt alles ist.Touchscreen, Klappfunktion läuft top. Heute war gleich der nächste Laptop dran. Und der #diday kommt erst noch. #dutgemacht #asus #zenbook flip
-
When two Hetzner servers died at the same time
On May 12, 2026, two of my Arch Linux + LUKS servers at Hetzner became unreachable at the same moment. Both had been running for 4+ months without issue. Both had received the same
pacman -Syyuthe day before, but had stayed on the old kernel until the morning the websites stopped responding. I rebooted — SSH never came back.nmap -Pn -p 22showedfilteredfrom anywhere. No ping. No banner. The Hetzner Robot panel insisted the hardware was fine.Several hours went into hypotheses that turned out to be wrong:
- The
encryptsshinitcpio hook referencing a/usr/lib/initcpio/udev/11-dm-initramfs.rulesfile that no longer exists. Real bug, no boot impact — the initramfs rebuilds anyway. PermitRootLogin noinsshd_config. Real misconfiguration, fixed it, didn’t help. A refusing sshd showsclosed, notfiltered.- Predictable interface-naming drift after the systemd 260 upgrade. Patched the
.networkconfig to match by MAC. Useful hardening; not the cause. - Stale GRUB stage1 +
core.imgin the MBR. Arch never re-runsgrub-installafter agrubpackage upgrade. Refreshed it. Still filtered. - Kernel 7.0.5 regression. Downgraded to 6.18.3, the kernel that had run for 4 months. Still filtered. So the kernel itself wasn’t it either.
The clue was in the persistent journal: a single recorded boot from December 31 to May 12 10:13 UTC, and absolutely nothing after. Every reboot since the upgrade was failing before
systemd-journaldcould flush to disk — so the failure had to be in the initramfs, before the root filesystem was even mounted.What it almost certainly was
Hetzner Dedicated servers configure the initramfs network with
ip=dhcpon the kernel command line. That depends on Hetzner’s DHCP server replying to whatever request format the current kernel sends. Somewhere between kernel 6.18 / iproute2 6.18 and kernel 7.0 / iproute2 7.0, the request format changed enough that Hetzner’s DHCP stopped responding. Effects:- Old kernel at runtime kept the interface already configured (Phase A — 32 hours of healthy operation after the package upgrade).
- New kernel cold-boots, hits DHCP, never gets an IP, dropbear cannot listen, port 22 stays
filtered.
Hetzner’s own documentation has been quietly moving away from
ip=dhcptoward static IPv4 in the kernel command line. The fix is exactly that:GRUB_CMDLINE_LINUX="cryptdevice=/dev/md1:cryptroot ip=A.B.C.D::GATEWAY:255.255.255.255:hostname:eth0:none"One line in
/etc/default/grub,grub-mkconfig, reboot. No more dependency on Hetzner’s DHCP responding to whatever your current kernel sends.Why it matters for anyone running this stack
If you run Arch on Hetzner Dedicated with full-disk encryption and remote unlock via dropbear, the
ip=dhcpshipped byinstallimageis a latent bug. It can keep working for years and then break overnight, on every machine you have, after a routinepacman -Syyu. The static-IP version is what Hetzner now recommends and removes the entire dependency.Tooling
While debugging, I turned the whole rescue / chroot / diagnose / fix workflow into a Python CLI (
hal) — includinghal fix static-ip, which derives the static cmdline directly from your existingsystemd-networkd.networkfile:→ github.com/kevinveenbirkenbach/hetzner-arch-luks
Single command, idempotent, reversible (the original
#ArchLinux #bootFailure #debugging #DevOps #DHCP #Dropbear #fullDiskEncryption #GRUB #Hetzner #initramfs #kernelUpgrade #Linux #LUKS #mkinitcpio #pacman #postmortem #PythonCLI #serverOutage #sysadmin #systemdNetworkd/etc/default/grubis backed up to.hal-backup). If you’re on this stack, switch to static IP before the next kernel upgrade catches you. - The