How do I handle .pacnews and hooks()?

magus · 8 December 2025 20:34

Hi there dear Manjaro community!

The upgrade went smoothly, thank you for this new release!

Using KDE- Plasma, click to show details.

Operating System: Manjaro Linux 
KDE Plasma Version: 6.5.3
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.1
Kernel Version: 6.17.11-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-3470 CPU @ 3.20GHz
Memory: 16 GiB of RAM (15.6 GiB usable)
Graphics Processor: Quadro K620
Manufacturer: FUJITSU
Product Name: ESPRIMO E510

I got a pacnew for mkinitcpio.conf though, that I don’t know how to solve the “puzzle”. Yes, I’ve read the wiki, but it’s not relevant in this scenario (in terms of safety first).

So the original vs pacnew is as follows:

FROM (original, as it was shipped by the installer iso):
HOOKS=(base udev autodetect microcode kms modconf block keyboard keymap consolefont plymouth filesystems)

TO (after today’s uprade):
HOOKS=(base systemd autodetect microcode modconf kms keyboard keymap sd-vconsole block filesystems fsck)

How to resolve this? Is it safe to use the .pacnew variant?

majik · 8 December 2025 20:44

I got a pacnew for mkinitcpio.conf though, that I don’t know how to solve the “puzzle”.

might this help perhaps?

magus · 8 December 2025 20:46

I have seen that thanks, but I want an official confirmation from Manjaro devs.

Teo · 9 December 2025 11:01

Hooks for arch are 100% valid for manjaro

soundofthunder · 9 December 2025 11:02

Your posts have been moved to a dedicated topic, hopefully with less congestion.

Please start by providing your system information as described (below) and add any other detail that you might find relevant.

I’m sure someone will help when they are able.

Regards.

What follows is from a standard template.

Welcome to the Manjaro community

As a new or infrequent forum user, please take some time to familiarise yourself with forum requirements, and the many ways to use the forum to your benefit.

Note: By virtue of using the Manjaro forum you acknowledge and agree to follow Rules and Guidelines outlined; so, you really should read them:

Required Reading

Highly Recommended

Work with us, not against us

It is important to provide as much actionable information as possible in your first post, rather than simply indicating there is a problem. Please also be prepared to provide output from commands if/when asked.

Simply waiting for others to ask you questions is counter-productive – typically, nobody has a at their disposal – and your clear, concise and accurate input is often relied upon in order to help you.

Please help others to make informed suggestions based on information you provide.

System Information

While information from *-fetch type apps might be fine for someone wishing to buy your computer, for Support purposes it’s better to ask your system directly;

Output of the inxi command (with appropriate parameters, and formatted according to forum guidelines) will generate information useful for those wishing to help:

Suggested inxi command (use either):


`inxi -zv8`	(short-form)
`inxi --filter --verbosity=8`	(long-form)
inxi man pages	(manual)

If running `inxi` within a `chroot` environment

Add --color=0 to the long-form command, or…
Change the short-form command to inxi -zv8c0

Your privacy is respected

Update Announcements

Technical Resources

Teo · 9 December 2025 11:41

Since this now became a separate topic, once again the source for all guides and instructions is this arch page.

There is a table with all hooks explained. One just have to choose a column (classic or systemd based hooks) and then write from top to bottom all the hooks that are applicable (mainly the optional things are encryption and resume from hibernation, pretty much all else is obligatory).

So the new array in the first post is good, you can even remove base and keymap.

soundofthunder · 9 December 2025 12:25

Here are some other informative resources:

Typically a .pacnew file contains changes that you might merge into the existing file – but seldom ever replace directly. The user should normally decide whether specific hooks are needed.

Please see the following to gain a better understanding of hooks in context of mkinitcpio.conf – the linked page lists all possible hooks with a description.

Yours:

Mine:

My current hooks() array in mkinitcpio.conf is:

HOOKS=(base udev autodetect microcode kms modconf block keyboard keymap consolefont plymouth resume filesystems fsck)

(this only differs from yours in that I use the resume hook for swap)

And hooks() in mkinitcpio.conf.pacnew:

HOOKS=(base systemd autodetect microcode modconf kms keyboard keymap sd-vconsole block filesystems fsck)

(this is identical to yours)

Perhaps others might suggest a few of their preferred hooks, but as it stands there is nothing inherently un-safe about any of them – it’s mainly a question of whether or not you have a need for each one.

Please provide your system information as previously requested.
Topic title changed to better reflect the actual issue.

magus · 9 December 2025 13:29

Hi, thanks for moving this into a separate thread, and sorry for the delay, I’m working meanwhile. Here’s my inxi

System:
  Kernel: 6.17.11-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-6.17-x86_64
    root=UUID=962b0fc4-5e80-4896-b8cc-d95dfcec14d2 rw rootflags=subvol=@
    quiet splash udev.log_priority=3
  Desktop: KDE Plasma v: 6.5.3 tk: Qt v: N/A info: frameworks v: 6.20.0
    wm: kwin_wayland vt: 1 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop System: FUJITSU product: ESPRIMO E510 v: N/A
    serial: <superuser required> Chassis: type: 3 v: C$ELW3
    serial: <superuser required>
  Mobo: FUJITSU model: D3171-A1 v: S26361-D3171-A1
    serial: <superuser required> part-nu: S26361-Kxxx-Vyyy
    uuid: <superuser required> Firmware: UEFI vendor: FUJITSU // American
    Megatrends v: 4.6.5.3 R1.30.0 for D3171-A1x date: 04/22/2015
Battery:
  Message: No system battery data found. Is one present?
Memory:
  System RAM: total: 16 GiB available: 15.57 GiB used: 2.47 GiB (15.8%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 32 GiB slots: 4 modules: 2 EC: None
    max-module-size: 8 GiB note: est.
  Device-1: DIMM 1A type: no module installed
  Device-2: DIMM A1 type: DDR3 detail: synchronous size: 8 GiB
    speed: 1600 MT/s volts: N/A width (bits): data: 64 total: 64
    manufacturer: Micron part-no: 16KTF1G64AZ-1G6E1 serial: <filter>
  Device-3: DIMM 1B type: no module installed
  Device-4: DIMM B2 type: DDR3 detail: synchronous size: 8 GiB
    speed: 1600 MT/s volts: N/A width (bits): data: 64 total: 64
    manufacturer: Micron part-no: 16KTF1G64AZ-1G6E1 serial: <filter>
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: Intel Core i5-3470 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: 1597 min/max: 1600/3600 scaling: driver: intel_cpufreq
    governor: schedutil cores: 1: 1597 2: 1597 3: 1597 4: 1597 bogomips: 25541
  Flags: acpi aes aperfmperf apic arat arch_perfmon avx bts clflush cmov
    constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64 dtherm dts epb
    ept erms est f16c flexpriority flush_l1d fpu fsgsbase fxsr ht ibpb ibrs
    ida lahf_lm lm mca mce md_clear mmx monitor msr mtrr nonstop_tsc nopl nx
    pae pat pbe pcid pclmulqdq pdcm pebs pge pln pni popcnt pse pse36 pti pts
    rdrand rdtscp rep_good sep smep smx ss ssbd sse sse2 sse4_1 sse4_2 ssse3
    stibp syscall tm tm2 tpr_shadow tsc tsc_deadline_timer vme vmx vnmi vpid
    x2apic xsave xsaveopt xtopology xtpr
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: ghostwrite status: Not affected
  Type: indirect_target_selection 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: Not affected
  Type: old_microcode status: Not affected
  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: tsa status: Not affected
  Type: tsx_async_abort status: Not affected
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: NVIDIA GM107GL [Quadro K620] driver: nvidia v: 580.105.08
    alternate: nouveau,nova_core,nvidia_drm non-free: 550-580.xx+ status: current
    (as of 2025-11; EOL~2026-12-xx) arch: Maxwell code: GMxxx
    process: TSMC 28nm built: 2014-2019 pcie: gen: 2 speed: 5 GT/s lanes: 16
    ports: active: DVI-I-1 empty: DP-1 bus-ID: 01:00.0 chip-ID: 10de:13bb
    class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
    compositor: kwin_wayland driver: X: loaded: nvidia
    gpu: nvidia,nvidia-nvswitch display-ID: 0
  Monitor-1: DVI-I-1 model: Fujitsu Siemens B22W-7 LED serial: <filter>
    built: 2015 res: mode: 1680x1050 hz: 60 scale: 100% (1) dpi: 90 gamma: 1.2
    chroma: red: x: 0.635 y: 0.337 green: x: 0.333 y: 0.627 blue: x: 0.157
    y: 0.043 white: x: 0.314 y: 0.329 size: 474x296mm (18.66x11.65")
    diag: 559mm (22") ratio: 16:10 modes: 1680x1050, 1600x900, 1280x1024,
    1440x900, 1280x720, 1024x768, 800x600, 640x480
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
    drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia
    x11: drv: nvidia inactive: device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 580.105.08
    glx-v: 1.4 direct-render: yes renderer: Quadro K620/PCIe/SSE2
    memory: 1.95 GiB display-ID: :1.0
  API: Vulkan v: 1.4.328 layers: 9 device: 0 type: discrete-gpu
    name: Quadro K620 driver: nvidia v: 580.105.08 device-ID: 10de:13bb
    surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
    wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Fujitsu
    Solutions B75 Ivy Bridge   CX20642 on Esprimo P510 D3171
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1e20
    class-ID: 0403
  Device-2: NVIDIA GM107 High Definition Audio [GeForce 940MX]
    driver: snd_hda_intel v: kernel alternate: nova_core pcie: gen: 2
    speed: 5 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:0fbc class-ID: 0403
  API: ALSA v: k6.17.11-1-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.9 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: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Fujitsu Solutions RTL8211DN on Esprimo P510 D3171 driver: r8169
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 03:00.0
    chip-ID: 10ec:8168 class-ID: 0200
  IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: link
  Info: services: NetworkManager,systemd-timesyncd
  WAN IP: <filter>
Bluetooth:
  Message: No bluetooth data found.
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 231.03 GiB used: 117.99 GiB (51.1%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SV300S37A120G
    size: 111.79 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
    tech: SSD serial: <filter> fw-rev: BBF2 scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: SanDisk model: SD8SB8U-128G-1006
    size: 119.24 GiB block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 0006 scheme: GPT
  Optical-1: /dev/sr0 vendor: HL-DT-ST model: DVD-ROM DH10N rev: 0F03
    dev-links: cdrom
  Features: speed: 32 multisession: yes audio: yes dvd: yes rw: none
    state: running
Partition:
  ID-1: / raw-size: 118.95 GiB size: 118.95 GiB (100.00%)
    used: 101.52 GiB (85.3%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
    label: Manjaro uuid: 962b0fc4-5e80-4896-b8cc-d95dfcec14d2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 648 KiB (0.2%) fs: vfat dev: /dev/sdb1 maj-min: 8:17 label: N/A
    uuid: A753-B2B1
  ID-3: /home raw-size: 118.95 GiB size: 118.95 GiB (100.00%)
    used: 101.52 GiB (85.3%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
    label: Manjaro uuid: 962b0fc4-5e80-4896-b8cc-d95dfcec14d2
  ID-4: /mnt/Kingston raw-size: 111.79 GiB size: 109.47 GiB (97.93%)
    used: 16.47 GiB (15.0%) fs: ext4 dev: /dev/sda1 maj-min: 8:1 label: Kingston
    uuid: 99b0af80-1b1e-4ee6-ac8d-fee31cc0aa7c
  ID-5: /swap raw-size: 118.95 GiB size: 118.95 GiB (100.00%)
    used: 101.52 GiB (85.3%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
    label: Manjaro uuid: 962b0fc4-5e80-4896-b8cc-d95dfcec14d2
  ID-6: /var/cache raw-size: 118.95 GiB size: 118.95 GiB (100.00%)
    used: 101.52 GiB (85.3%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
    label: Manjaro uuid: 962b0fc4-5e80-4896-b8cc-d95dfcec14d2
  ID-7: /var/log raw-size: 118.95 GiB size: 118.95 GiB (100.00%)
    used: 101.52 GiB (85.3%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
    label: Manjaro uuid: 962b0fc4-5e80-4896-b8cc-d95dfcec14d2
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: file size: 512 MiB used: 0 KiB (0.0%) priority: -2
    file: /swap/swapfile
Unmounted:
  Message: No unmounted partitions found.
USB:
  Hub-1: 1-0:1 info: full speed or root hub ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-2: 1-1:2 info: Intel Integrated Rate Matching Hub ports: 6 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 8087:0024
    class-ID: 0900
  Hub-3: 1-1.6:12 info: Prolific USB 2.0 Hub ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 067b:2586 class-ID: 0900
  Device-1: 1-1.6.3:13 info: Trust Keyboard [GXT 830] type: keyboard,HID
    driver: hid-generic,usbhid interfaces: 2 rev: 1.1
    speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 100mA
    chip-ID: 145f:01e5 class-ID: 0300
  Device-2: 1-1.6.4:14 info: Nordic 2.4G Wireless Receiver
    type: keyboard,mouse driver: hid-generic,usbhid interfaces: 2 rev: 1.1
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
    chip-ID: 260d:1001 class-ID: 0301
  Hub-4: 2-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-5: 3-0:1 info: super-speed hub ports: 4 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-6: 4-0:1 info: full speed or root hub ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-7: 4-1:2 info: Intel Integrated Rate Matching Hub ports: 6 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 8087:0024
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 32.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Repos:
  Packages: pm: pacman pkgs: 1581 libs: 395 tools: pamac pm: flatpak pkgs: 0
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://quantum-mirror.hu/mirrors/pub/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 256
  1: cpu: 26.3% command: konsole pid: 1957 mem: 295.2 MiB (1.8%)
  2: cpu: 14.9% command: chrome pid: 1465 mem: 265.6 MiB (1.6%)
  3: cpu: 14.2% command: zsh pid: 1971 mem: 12.2 MiB (0.0%)
  4: cpu: 5.1% command: chrome pid: 1633 mem: 308.0 MiB (1.9%)
  5: cpu: 2.1% command: kwin_wayland pid: 629 mem: 206.1 MiB (1.2%)
  Memory top: 5 of 256
  1: mem: 448.3 MiB (2.8%) command: plasmashell pid: 781 cpu: 1.7%
  2: mem: 328.5 MiB (2.0%) command: chrome pid: 1418 cpu: 1.9%
  3: mem: 308.0 MiB (1.9%) command: chrome pid: 1633 cpu: 5.1%
  4: mem: 295.2 MiB (1.8%) command: konsole pid: 1957 cpu: 26.3%
  5: mem: 265.6 MiB (1.6%) command: chrome pid: 1465 cpu: 14.9%
Info:
  Processes: 256 Power: uptime: 9m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 6.17 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 258 default: graphical
    tool: systemctl
  Compilers: clang: 21.1.6 gcc: 15.2.1 Shell: Zsh v: 5.9 running-in: konsole
    inxi: 3.3.40

Teo · 9 December 2025 14:32

Soundofthunder runs Plymouth?
You’re a bad boy and you will receive 1 present less because of that

soundofthunder · 9 December 2025 14:47

Only since the fresh installation a few weeks ago.
I’m actually surprised it’s given no trouble, given the delays, but then, I’m not using Nvidia – that’s always a bonus.

magus · 9 December 2025 14:50

Thank you @Teo. While it is true that I used Arch and Arch based systems in general in the past, my knowledge became rusty over the times while I was away on Debian based distros. But now I returned and things start to click together again I admit I never really understood the “mechanics” behind mkinitcpio HOOKS, but I think I get it now thanks to you. So, out of curiosity, based on the previous HOOKS, for me it seems it was previously based or optimized (if thats the good wording) for busybox, but from now on it’s all systemd, am I right?

soundofthunder · 9 December 2025 14:56

I’ll just note that contents of .pacnews are (sometimes) more best-practice than much else – sometimes there might be no real need to change anything.

The mkinitcpio.conf.pacnew file contains a few hooks I’m not at all sure that I personally need. Another thing to add to my “ToDo” list, I suppose.

Aragorn · 9 December 2025 15:10

Not really. With the systemd and sd-vconsolehooks, you don’t need the keymap and resume hooks.

Also, the base hook is useless by default when used together with the systemd hook, because then all it does is add a rescue shell in the initramfs, but this rescue shell is disabled by default unless you boot with a special kernel parameter.

The previous hooks were very conservative. The systemd and sd-* hooks have already been around for many years — and they’re just a smidgen faster — but Arch still used the conservative hooks, and Manjaro simply followed Arch in that. But now Arch itself has switched to the systemd and sd-* hooks, and so now have we.

magus · 9 December 2025 15:24

Indeed. And I also thank you for moving this thread here, it truly is less polluted, and helped me in terms of readability, thanks @soundofthunder

Right? We’re “suffering” the same fate then, because I aswell don’t know whether I need those or not xD This is why I never touch or customise anything that I have zero knowledge of, and rather just trust in my distro’s dev, to simply use these pacnew files, and call it a day :3 But yeah, the ToDo list is also in my practice, specially in this case, I didn’t overwrote it till I got a confirmation here from official Manjaro members So, thank you both of you. And I also learned a bit today about these hooks, so two flies on one slap I guess

Thats good to know thanks

system · 12 December 2025 15:24

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.