-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Grub message not removed #3
Comments
It doesnt seem to be able to match the "Welcome to Grub!" message |
ugh. I unfortunately no longer have a GPT machine I can try this on. I may try to build a VM or similar, but will take me some time to debug this :/ Don't have any useful suggestion otherwise. |
I've managed to hide the messages by downloading grub from arch abs and modifiying the pkgbuild script and remove the text inbetween the quotes where the welcome messages are I removed the following : (Welcome to GRUB!\n\n) , (loading) , (GRUB) , (.) , (\r\n) grub-install --recheck --target=i386-pc /dev/sda After rebooting the messages are now gone !! |
Weclome to GRUB! Still shows but the "loading grub" has been removed
Grub version : grub 1:2.02.beta2-6
OS : arch x86_x64
DE : gnome-shell
Disk /dev/sda: 240GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 3146kB 2097kB bios_grub
2 3146kB 240GB 240GB ext4
sh-4.3# ./mbr -g /dev/sda
opened: /dev/sda
read: 2048 bytes from /dev/sda
match[0]: NOT FOUND
match[1]: NOT FOUND
match[2]: found at 384, "GRUB ", 'G'
Found mbr header of gpt disk.
Make sure to also run this on the ef02 partition of this drive.
PATCHED SUCCESSFULLY!
(the message should be gone next time you reboot, good luck!)
sh-4.3# ./mbr -g /dev/sda1
opened: /dev/sda1
read: 2048 bytes from /dev/sda1
match[0]: found at 283, "loading", 'l'
match[1]: found at 291, ".", '.'
match[2]: NOT FOUND
Found ef02 header of gpt grub partition.
Make sure to also run this on full drive.
PATCHED SUCCESSFULLY!
(the message should be gone next time you reboot, good luck!)
The text was updated successfully, but these errors were encountered: