Reinstalling grub can be a risky task as I already mentioned. So if you are unsure, please avoid doing so, even the system might have some security risks. You have to balance the trade off based on the risk not having a bootable system if some goes wrong and inform yourself on how to fix that later before even considering reinstalling grub. Especially with multiboot options.
2 Likes
@TheDubster Maybe this could help you?
Quick tip:
Use LC_ALL=C to force command output to be in English.
For example;
LC_ALL=C sudo pacman -S install-grub
4 Likes
Spectacle stopped working after this update, fixed it by downgrading glslang back to 15.1.0-1
spectacle: symbol lookup error: /usr/lib/libglslang.so.15: undefined symbol: spvValidatorOptionsSetAllowOffsetTextureOperand
1 Like
It could be that pamac was not really terminated, but continued to run in the background. I have had this problem several times recently, always when major updates have been rolled out.
I had already posted this in the German forum.
https://forum.manjaro.org/t/kein-bootlaufwerk-mehr-nur-noch-uefi-firmware-settings/175816
At that time I had the same problem due to a hasty restart, as I was not aware at the time that pamac was still running in the background.
In this case, I now use tail -f /var/log/pacman.log to check whether pamac is still running. For me a practical workaround.
1 Like
Hello everyone. I am using manjaro kde on my huawei matebook d16 laptop and I have a problem after the latest update. I set the limits for charging the battery to 40% and 80% (start charging below 40% and stop charging above 80% battery charge). After the update, when the charge reaches 80%, the charger disconnects as if physically (as if the charger is pulled out, the icon in the tray and the sound from the speakers indicate this). A few seconds or minutes pass and the charger is connected again (the icon and sound also signal this). It was not like this before: when 80% charge was reached, charging stopped, but the icon signaled that the charger was connected. I donāt think this should be the case, because it increases the battery charge cycle counter.
P.S. I checked with several power supplies, the problem is not in them.
Tried with kernel versions 6.13.9 and 6.14.0
upd: itās a bug in upower https://www.reddit.com/r/kde/comments/1jqyjuo/634_update_laptop_constantly_switching_between/
i solved it by installing upower v1.90.9 from aur
A post was split to a new topic: I have a problem trying to update
After this update I have blank screen on grub, but then I press āEscā - menu appeared, also SSD with Windows 10 disappeared.
inxi -Fza
System:
Kernel: 6.12.21-4-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.12-x86_64
root=UUID=eccc78ae-a2e1-49c9-a78f-9c39efaf08fb rw quiet splash
resume=UUID=42c778e5-dd0d-49bc-af0c-60e8ac21b178 udev.log_priority=3
Desktop: KDE Plasma v: 6.3.4 tk: Qt v: N/A info: frameworks v: 6.12.0
wm: kwin_x11 vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
Type: Portable System: Dell product: Inspiron 7720 v: N/A
serial: <superuser required> Chassis: type: 8 v: 0.1
serial: <superuser required>
Mobo: Dell model: 04M3YM v: A00 serial: <superuser required>
uuid: <superuser required> UEFI-[Legacy]: Dell v: A12 date: 12/18/2012
CPU:
Info: model: Intel Core i7-3630QM bits: 64 type: MCP arch: Ivy Bridge
gen: core 3 level: v2 built: 2012-15 process: Intel 22nm family: 6
model-id: 0x3A (58) stepping: 9 microcode: 0x21
Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 smt: <unsupported> cache:
L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
L3: 6 MiB desc: 1x6 MiB
Speed (MHz): avg: 1197 min/max: 1200/3400 scaling: driver: intel_cpufreq
governor: schedutil cores: 1: 1197 2: 1197 3: 1197 4: 1197 bogomips: 19167
Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: itlb_multihit status: KVM: Split huge pages
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
disabled
Type: mds mitigation: Clear CPU buffers; SMT disabled
Type: meltdown mitigation: PTI
Type: mmio_stale_data status: Unknown: No mitigations
Type: reg_file_data_sampling status: Not affected
Type: retbleed status: Not affected
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW;
STIBP: disabled; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not
affected
Type: srbds status: Vulnerable: No microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel 3rd Gen Core processor Graphics vendor: Dell driver: i915
v: kernel arch: Gen-7 process: Intel 22nm built: 2012-13 ports:
active: HDMI-A-1,LVDS-1 empty: DP-1,VGA-1 bus-ID: 00:02.0
chip-ID: 8086:0166 class-ID: 0300
Device-2: NVIDIA GK107M [GeForce GT 650M] vendor: Dell driver: N/A
alternate: nouveau, nvidia_drm, nvidia non-free: series: 470.xx+
status: legacy-active (EOL~2024-09-xx) arch: Kepler-2 code: GKxxx
process: TSMC 28nm built: 2012-2018 pcie: speed: Unknown lanes: 63
link-max: gen: 6 speed: 64 GT/s bus-ID: 01:00.0 chip-ID: 10de:0fd1
class-ID: 0300
Device-3: Suyin Laptop_Integrated_Webcam_HD driver: uvcvideo type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-1.5:4
chip-ID: 064e:8126 class-ID: 0e02
Display: x11 server: X.Org v: 21.1.16 with: Xwayland v: 24.1.6
compositor: kwin_x11 driver: X: loaded: intel dri: i965 gpu: i915
display-ID: :0 screens: 1
Screen-1: 0 s-res: 3840x1184 s-dpi: 96 s-size: 1013x312mm (39.88x12.28")
s-diag: 1060mm (41.73") monitors: <missing: xrandr>
Monitor-1: HDMI-A-1 model: Idek Iiyama PLX2783H serial: <filter>
built: 2021 res: 1920x1080 dpi: 82 gamma: 1.2 size: 598x336mm (23.54x13.23")
diag: 686mm (27") ratio: 16:9 modes: max: 1920x1080 min: 720x400
Monitor-2: LVDS-1 model: ChiMei InnoLux 0x1720 built: 2011 res: 1920x1080
dpi: 128 gamma: 1.2 size: 382x215mm (15.04x8.46") diag: 438mm (17.3")
ratio: 16:9 modes: 1920x1080
API: EGL v: 1.5 hw: drv: intel crocus platforms: device: 0 drv: crocus
device: 1 drv: swrast gbm: drv: crocus surfaceless: drv: crocus x11:
drv: crocus inactive: wayland
API: OpenGL v: 4.5 compat-v: 4.2 vendor: intel mesa v: 25.0.3-arch1.1
glx-v: 1.4 direct-render: yes renderer: Mesa Intel HD Graphics 4000 (IVB
GT2) device-ID: 8086:0166 memory: 1.46 GiB unified: yes
API: Vulkan Message: No Vulkan data available.
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
wl: wayland-info x11: xdpyinfo,xprop
Audio:
Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Dell
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1e20
class-ID: 0403
API: ALSA v: k6.12.21-4-MANJARO status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: JACK v: 1.9.22 status: off tools: N/A
Server-3: PipeWire v: 1.4.1 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Centrino Wireless-N 2230 driver: iwlwifi v: kernel pcie:
gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 02:00.0 chip-ID: 8086:0887
class-ID: 0280
IF: wlp2s0 state: up mac: <filter>
Device-2: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell
driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 2000
bus-ID: 03:00.0 chip-ID: 10ec:8136 class-ID: 0200
IF: enp3s0 state: up speed: 100 Mbps duplex: full mac: <filter>
IF-ID-1: amn0 state: unknown speed: 10000 Mbps duplex: full mac: N/A
IF-ID-2: br-27f6707ba464 state: down mac: <filter>
IF-ID-3: br-3183c4a798c2 state: up speed: 10000 Mbps duplex: unknown
mac: <filter>
IF-ID-4: br-36a26f45c277 state: up speed: 10000 Mbps duplex: unknown
mac: <filter>
IF-ID-5: br-5b8827f2ead5 state: down mac: <filter>
IF-ID-6: br-628943c57393 state: down mac: <filter>
IF-ID-7: br-71e1190f8cb5 state: down mac: <filter>
IF-ID-8: br-74ffa936fcf6 state: down mac: <filter>
IF-ID-9: br-7afcfb75cc15 state: down mac: <filter>
IF-ID-10: br-961d2e4558b4 state: down mac: <filter>
IF-ID-11: br-a248d3b92d7b state: down mac: <filter>
IF-ID-12: br-a86628535cea state: down mac: <filter>
IF-ID-13: br-b0d83105a434 state: down mac: <filter>
IF-ID-14: br-b73814262b13 state: down mac: <filter>
IF-ID-15: br-c91ce88d9c0e state: down mac: <filter>
IF-ID-16: br-d3f4f9bae4f6 state: down mac: <filter>
IF-ID-17: br-d50ad4bc7378 state: down mac: <filter>
IF-ID-18: docker0 state: down mac: <filter>
IF-ID-19: veth1d8c682 state: up speed: 10000 Mbps duplex: full
mac: <filter>
IF-ID-20: veth324e16b state: up speed: 10000 Mbps duplex: full
mac: <filter>
IF-ID-21: veth5e31138 state: up speed: 10000 Mbps duplex: full
mac: <filter>
IF-ID-22: veth9c5952c state: up speed: 10000 Mbps duplex: full
mac: <filter>
IF-ID-23: vetheb41697 state: up speed: 10000 Mbps duplex: full
mac: <filter>
IF-ID-24: vethec307b6 state: up speed: 10000 Mbps duplex: full
mac: <filter>
IF-ID-25: vethef2d86e state: up speed: 10000 Mbps duplex: full
mac: <filter>
IF-ID-26: vethfe16870 state: up speed: 10000 Mbps duplex: full
mac: <filter>
Info: services: apache2, NetworkManager, smbd, systemd-timesyncd,
wpa_supplicant
Bluetooth:
Device-1: Intel Centrino Bluetooth Wireless Transceiver driver: btusb v: 0.8
type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 4-1.5:3
chip-ID: 8087:07da class-ID: e001
Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Drives:
Local Storage: total: 1.37 TiB used: 484.7 GiB (34.6%)
SMART Message: Required tool smartctl not installed. Check --recommends
ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 EVO 250GB
size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 1B6Q scheme: MBR
ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: ST1000LM024 HN-M101MBB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
tech: HDD rpm: 5400 serial: <filter> fw-rev: 0003 scheme: GPT
ID-3: /dev/sdc maj-min: 8:32 vendor: Netac model: SSD 256GB
size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
tech: SSD serial: <filter> fw-rev: 4A0 scheme: MBR
Partition:
ID-1: / raw-size: 224.08 GiB size: 219.51 GiB (97.96%)
used: 122.22 GiB (55.7%) fs: ext4 dev: /dev/sda1 maj-min: 8:1
Swap:
Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: partition size: 8.8 GiB used: 566 MiB (6.3%)
priority: -2 dev: /dev/sda2 maj-min: 8:2
Sensors:
System Temperatures: cpu: 69.0 C mobo: 50.0 C sodimm: 50.0 C
Fan Speeds (rpm): N/A
Info:
Memory: total: 8 GiB available: 7.61 GiB used: 5.06 GiB (66.4%)
Processes: 286 Power: uptime: 1h 22m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 3.02 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Packages: 1501 pm: dpkg pkgs: 0 pm: pacman pkgs: 1490 libs: 404
tools: pamac pm: flatpak pkgs: 11 Compilers: gcc: 14.2.1 Shell: Bash
v: 5.2.37 running-in: far2l inxi: 3.3.38
sudo parted -l
Model: ATA Samsung SSD 870 (scsi)
Disk /dev/sda: 250GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 241GB 241GB primary ext4 boot
2 241GB 250GB 9449MB primary linux-swap(v1) swap
Model: ATA ST1000LM024 HN-M (scsi)
Disk /dev/sdb: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 525MB 524MB fat32 EFI system partition boot, esp
2 525MB 567MB 41,9MB fat32 Basic data partition hidden
3 567MB 701MB 134MB Microsoft reserved partition msftres
4 701MB 1226MB 524MB ntfs Basic data partition hidden, diag
5 1226MB 985GB 984GB ext4 ST1000
6 985GB 985GB 472MB ntfs hidden, diag
7 985GB 1000GB 14,9GB ntfs Microsoft recovery partition hidden, diag
Model: ATA Netac SSD 256GB (scsi)
Disk /dev/sdc: 256GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 368MB 367MB primary ntfs boot
2 368MB 255GB 255GB primary ntfs
3 255GB 256GB 576MB primary ntfs msftres
Windows located on Netac SSD (/dev/sdc2).
Do you often feel ambiguous?
Thatās actually a valid point, and also one of the reasons I use rEFInd as my primary boot loader, which effectively chainloads any GRUB instances on my multi-boot system.
There are also valid reasons why Manjaroās GRUB would be the best choice as default boot loader in other scenarioās. @Aragorn will likely explain the definitive reasoning for that, if you catch him in the Members Hub.
3 Likes
@Nikit maybe try this: [Stable Updates] 2025-04-12 - Kernels, Plasma, Systemd, Mesa, Grub, Wine3 - #61 by xman1
1 Like
Thank you! Itās worked for me:
-
Mount the Windows SSD partitions in Dolphin (ensure both the Windows boot and main partitions are mounted).
-
Switch to root privileges: su
-
Update GRUB: update-grub
-
Done! GRUB should now detect Windows.
1 Like
I updated via tty, everything went smoothly - afterwards I ran āsudo install-grubā.
After completing, I got a warning:
[...]
Warning: GRUB bootloader at /boot/efi/EFI/Manjaro was updated,
but it seems like you are not using it by default.
Please check your EFI boot priorities!
Itās a single-boot system on my 2023 Dell XPS 15. The UEFI boot options only include my main partition and UEFI https.
Should I worry?
1 Like
Hmm, if you are booting/rebooting fine it might be an erroneous messageā¦ perhaps it might be a good idea to run efibootmgr in the terminal and inspect the output.
Iām not super proficient with this tool, but I think if you can confirm the āBootOrderā line starts with the number for the line containing āManjaroā with a similar path to your warning messageā¦ I think you may be okay.
i.e. For me, my āBootOrderā line starts with ā0003ā, and the line starting with āBoot003ā lists Manjaroā¦
efibootmgr
BootCurrent: 0003
Timeout: 0 seconds
BootOrder: 0003,0000,2001,2002,2003
Boot0000* EFI Hard Drive (WD_BLACK SN850X 1000GB) PciRoot(0x0)/Pci(0x2,0x4)/Pci(0x0,0x0)/NVMe(0x1)/HD(1,GPT,cbca07b0-8cfc-47dd-b988-5a17de4dda4b,0x800,0x100000)RC
Boot0002* EFI PXE 0 for IPv4 (MAC) PciRoot(0x0)/Pci(0x8,0x1)/Pci(0x0,0x3)/USB(6,0)/USB(2,0)/MAC(0c3796801cc6,0)/IPv4(0.0.0.0,0,DHCP,0.0.0.0,0.0.0.0,0.0.0.0)RC
Boot0003* Manjaro HD(1,GPT,cbca07b0-8cfc-47dd-b988-5a17de4dda4b,0x800,0x100000)/\EFI\Manjaro\grubx64.efi
Boot0004* Windows Boot Manager HD(2,GPT,d164f3ab-8c53-41eb-a9fb-bb57b7c9245c,0xa00800,0x82000)/\EFI\Microsoft\Boot\bootmgfw.efi57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000044000100000010000000040000007fff0400
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RC
Note: I have not run install-grub myself (yet).
1 Like
If you use MBR you donāt have to count on GRUB at allā¦ you can directly boot windows when you press F12 (at least works for gigabyte bios) at initialising Bios to choose your Windows Drive to boot from it.
Donāt worry. If you donāt have any other operating systems on your drive, then you are most likely booting up from the generic āUEFI OSā entry in the EFI boot manager, i.e. /boot/efi/EFI/boot/bootx64.efi, which should normally be identical to /boot/efi/EFI/Manjaro/grubx64.efi.
If they are not identical, then you should runā¦ 
sudo grub-install --recheck --removable
The ā--removableā argument is what generates the /boot/efi/EFI/boot/bootx64.efi file. It is intended both for removable drives and as a fallback option.
Another way of generating the file is by simply copying over /boot/efi/EFI/Manjaro/grubx64.efi to /boot/efi/EFI/boot and renaming it bootx64.efi.
cd /boot/efi/EFI && sudo cp ./Manjaro/grubx64.efi ./boot/bootx64.efi
2 Likes
Noob question, but how can I determine if the two files are identical? I received the same warning after running sudo install-grub.
man diff
Other than that, you can also verify whether they have the same sizeā¦
cd /boot/efi/EFI
for i in boot/bootx64.efi manjaro/grubx64.efi ; do ls -l $i ; done
cd
I have not taken a look at the code of install-grub ā it is a script, and I donāt have it installed. But if you runā¦
sudo grub-install --recheck --removable
ā¦ then they will be identical, because this will update them both.
Note: Thatās the grub-install command, not the install-grub script.
Check the md5sum of both files to be the same
sudo md5sum /boot/efi/EFI/boot/bootx64.efi
1 Like
Thank you @Daniel-I and @Aragorn!
efibootmgr shows ā\EFI\Boot\BootX64.efiā as first in boot order.
ā/boot/efi/EFI/Manjaro/grubx64.efiā and ā/boot/efi/EFI/boot/bootx64.efiā are identical - I will ignore the warning.
1 Like
Upgraded from Manjaro 24.2.1 (Yonada). Everything works as expected 
; excluding one and most important thing for me. Hardware acceleration on Gen 3 onboard has gone. Renderer turned into llvmpipe. It recognized as i915 (: G33) in Mesa 24.2.8. Iāve replaced Mesa 25.0.3 with Mesa 21.3.9 Amber but this time OpenGL compat-v dropped to 1.4 from 2.1 and some simple 3D applications (such as Luanti ā aka open source Minecraft) didnāt work because of requirements.
I followed Arch instructions, then added necessary config lines to achieve 2.1. It reported correct version but performance was still terrible (~70% loss). I gave up after a few hours efforts and decided to roll back. In the middle of process timeshift couldnāt complete and gave kernel panic causing total freeze needed hard power-off. So that I faced black grub screen and system didnāt boot up. Thankfully I had system ISO that I used last year on USB. I recovered last state and will keep like that for a long time (static release 
). Itās loosing its capabilities on every new update day by day. Sounds like itās the end of way for this kind of outdated hardware in the journey (at least in any rolling release distro). 