Grub handles Manjaro, Mint different from Fedora Linux?

Support
1

Just wondering …

I have a multiboot system with manjaro, mint and fedora. Because i had troubles with interrups firering all the time i found a solution by masking one interrupt:

/sys/firmware/acpi/interrupts/gpe6E: 0 STS enabled masked

by modifying /etc/default/grub

GRUB_CMDLINE_LINUX_DEFAULT=“quiet udev.log_priority=3 acpi_mask_gpe=0x6E”

This solution works for manjaro and mint, but it does not work for fedora.

I start all linux system from manjaro !

All three systems are linux but fedora is differnet in which way ?

System-Info:

Generated on 2025-10-18 22:19:1760818795

#################### inxi -Fxzc0 ########################

System:
  Kernel: 6.12.48-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
  Desktop: Xfce v: 4.20.1 Distro: Manjaro base: Arch Linux
Machine:
  Type: Laptop System: LENOVO product: 81RS v: Lenovo Yoga S740-14IIL serial: <superuser required>
  Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial: <superuser required> UEFI: LENOVO
    v: BYCN39WW date: 05/28/2021
Battery:
  ID-1: BAT0 charge: 64.6 Wh (98.9%) condition: 65.3/62 Wh (105.3%) volts: 17.07 min: 15.4
    model: LGC L19L4PD2 status: full
  Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard charge: 55% (should be ignored)
    status: discharging
CPU:
  Info: quad core model: Intel Core i7-1065G7 bits: 64 type: MT MCP arch: Ice Lake rev: 5 cache:
    L1: 320 KiB L2: 2 MiB L3: 8 MiB
  Speed (MHz): avg: 1152 min/max: 400/3900 cores: 1: 1152 2: 1152 3: 1152 4: 1152 5: 1152 6: 1152
    7: 1152 8: 1152 bogomips: 23968
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Iris Plus Graphics G7 vendor: Lenovo driver: i915 v: kernel arch: Gen-11
    bus-ID: 00:02.0
  Device-2: NVIDIA GP108M [GeForce MX250] vendor: Lenovo driver: nvidia v: 580.82.09 arch: Pascal
    bus-ID: 2b:00.0
  Device-3: Chicony Integrated Camera driver: uvcvideo type: USB bus-ID: 3-5:6
  Display: x11 server: X.Org v: 21.1.18 driver: X: loaded: modesetting,nvidia unloaded: nouveau
    dri: iris gpu: i915 resolution: 1: 1920x1080~60Hz 2: N/A
  API: EGL v: 1.5 drivers: iris,nvidia,swrast platforms: active: gbm,x11,surfaceless,device
    inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 25.2.3-arch1.2 glx-v: 1.4
    direct-render: yes renderer: Mesa Intel Iris Plus Graphics (ICL GT2)
  API: Vulkan v: 1.4.321 drivers: intel,nvidia surfaces: N/A devices: 2
  Info: Tools: api: eglinfo, glxinfo, vulkaninfo de: xfce4-display-settings
    gpu: nvidia-settings,nvidia-smi x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Lenovo driver: sof-audio-pci-intel-icl
    bus-ID: 00:1f.3
  API: ALSA v: k6.12.48-1-MANJARO status: kernel-api
  Server-1: PipeWire v: 1.4.8 status: active
Network:
  Device-1: Intel Ice Lake-LP PCH CNVi WiFi driver: iwlwifi v: kernel bus-ID: 00:14.3
  IF: wlp0s20f3 state: down mac: <filter>
  Device-2: Realtek RTL8153 Gigabit Ethernet Adapter driver: r8152 type: USB bus-ID: 2-1.4:5
  IF: enp0s13f0u1u4 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Intel AX201 Bluetooth driver: btusb v: 0.8 type: USB bus-ID: 3-10:2
  Report: rfkill ID: hci0 rfk-id: 2 state: up address: see --recommends
Drives:
  Local Storage: total: 1.87 TiB used: 374.28 GiB (19.5%)
  ID-1: /dev/nvme0n1 vendor: Micron model: MTFDHBA1T0TCK size: 953.87 GiB temp: 53.9 C
  ID-2: /dev/sda vendor: SanDisk model: Extreme size: 29.25 GiB type: USB
  ID-3: /dev/sdb vendor: Western Digital model: WD10EARX-00N0YB0 size: 931.51 GiB type: USB
Partition:
  ID-1: / size: 57.85 GiB used: 36.14 GiB (62.5%) fs: ext4 dev: /dev/nvme0n1p8
  ID-2: /boot/efi size: 259.5 MiB used: 103.2 MiB (39.8%) fs: vfat dev: /dev/nvme0n1p1
Swap:
  ID-1: swap-1 type: partition size: 16.67 GiB used: 0 KiB (0.0%) dev: /dev/nvme0n1p9
Sensors:
  System Temperatures: cpu: 46.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 16 GiB note: est. available: 15.19 GiB used: 2.85 GiB (18.8%)
  Processes: 283 Uptime: 1d 54m Init: systemd
  Packages: 1782 Compilers: clang: 20.1.8 gcc: 15.2.1 Client: Unknown Client: wrapper-2.0
    inxi: 3.3.39

Ok. thats no real problem but would be nice to know the reason for this behaviour !

2

Would you please care to revisit your post and separate your actual text from the inxi terminal output? :folded_hands:

1 Like
3

Yep, i think you are long enough here to learn to format. There is a toolbar there…and preview…how hard can it be :grinning_face:

That said…it is normal. Different OS, different kernels, with different patches and flags.

4

A more manageable solution to multi-booting with several Linux flavours in the mix, is to use the refind boot manager as your initial boot loader, which in turn will effectively chainload every UEFI boot loader GRUB in your system, including that of Windows or BSD.

This allows one to leave each GRUB untouched and managed by it’s respective OS – this means less maintenance (no juggling settings just to enable a successful boot) – plus, the added convenience of being able to bypass any installed GRUB and boot the respective kernel stub directly.

6 Likes
5

This one saved my life several times:
super_grub2_disk_hybrid_2.04s1.iso

but i will think about your proposal …

p.s.

I don’t get any mail notice if someone answers to this topic … strange ! Perhaps gmx “eats” them ?

6

Or, perhaps you need to revisit your notification settings. :man_shrugging:

I mention refind briefly in my multi-boot tutorial;

7

boot your fedora installation then extract the cmdline

cat /proc/cmdline

Verify if the cmdline is as expected

8

I am now on Fedora thunderbird. The notifications were handled by filter of Fedora Discussion Summary so thunderbird seems to be the culpit ? I moved them manually to Manjaro Forum Summary. Thunderbird on Manjaro lost the filter for Manjaro Forum summary. Hope i remember in future where i have to look too. Also i extended at gmx Addressbook the mail address of manjaro forum summary , hope that will fix thies issue.

Mpf, that is somehow complicated !

9

It is correct:

cat /proc/cmdline
BOOT_IMAGE=(hd2,gpt7)/boot/vmlinuz-6.1.156-200.fc41.x86_64 root=UUID=d02cc318-ed54-412a-83ef-a0f81b204349 ro resume=UUID=3929678c-7b73-4532-9842-ceb0f11509d7 rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 acpi_mask_gpe=0x6

But i have to tell more:

Mint and fedora have theire own grub install, where i configured /etc/default/grub to mask this bad interrupt. And just now i started fedora by using an uefi-boot editor which calls the original boot of fedora and not the way of manjaro boot entries.

But don’t be worried about that. I know this issue and i take most of the time this uefi boot editor.

But was asking nyself where does this different behaviour from three linuxes come from … and this thread was born !

10

Since the issue arise from the kernel argument is not acknowledged on fedora, one can only deduce that the kernel on Fedora does not honor the argument - this is possibly the cause.