philm
24 September 2020 06:59
1
Hello community,
Another testing branch update with some interesting updates for you!
There is something in the works… #stayhome , #staysafe , #stayhealthy
We updated some of our KDE-git packages plus most of our Kernels
More Deepin updates
Coding-language Gambas is now at 3.15.2
Mhwd got a fix for Intel-Nvidia Prime cards
Systemd got renewed to 246.6
Firefox is now at 81.0
Mesa added some more fixes with 20.1.8
Usual Python and Haskell package updates and rebuilds
If you like following latest Plasma development you may also like to check out our current version of manjaro-kde-dev , which we build on a regular basis against kde-git master packages. Also check out our latest Manjaro Mikah 20.1 release! XFCE , KDE and Gnome
sudo pacman -Syy
sudo pacman -S pacman-static
sudo pacman-static -Syyu
Our current supported kernels
linux44 4.4.237
linux49 4.9.237
linux414 4.14.199
linux419 4.19.147
linux54 5.4.67
linux57 5.7.19 [EOL]
linux58 5.8.11
linux59 5.9-rc6
linux54-rt 5.4.66_rt38
linux56-rt 5.6.19_rt12
Packages Changes (Thu Sep 24 08:24:11 CEST 2020)
testing community x86_64: 1113 new and 1080 removed package(s)
testing core x86_64: 31 new and 35 removed package(s)
testing extra x86_64: 310 new and 311 removed package(s)
testing multilib x86_64: 25 new and 27 removed package(s)
A list of package changes may be found here
No issue, everything went smoothly
Yes there was an issue. I was able to resolve it myself.(Please post your solution)
Yes i am currently experiencing an issue due to the update. (Please post about it)
Check if your mirror has already synced:
9 Likes
philm
24 September 2020 06:59
2
Known issues and solutions
This is a wiki post; please edit as necessary.
Please, consider subscribing to the Testing Updates Announcements RSS feed
PAM and PAMBASE got updated, which might prevent you from login
Due to updates from pambase and pam you might take care about any .pacnew
files in /etc/pam.d
as for example pam_tally , pam_tally2 and pam_cracklib got deprecated . Read in the ArchWiki about managing those files.
Typical issue:
For recovery, it is enough to boot with kernel option “systemd.unit=rescue.target”, then proceed into /etc/pam.d and merge “system-auth” and “system-auth.pacnew”
Older Issues
System takes a long time to boot
If you’ve got errors like Failed to start Network Manager Wait Online.
you can try removing systemd
from passwd
and group
in /etc/nsswitch.conf
as described here
Update: If you can see the line
dbus-daemon[1453]: [system] Connection has not authenticated soon enough, closing it (auth_timeout=30000ms, elapsed: 45146ms)
in in your dbus log ( journalctl -b -u dbus
), the new/better workaround is to switch cups from service to socket as described here :
systemctl disable org.cups.cupsd.service
systemctl enable org.cups.cupsd.socket
I think I’ve some font problems
With the update of fontconfig some major rules how fonts get applied changed. Make sure that your system has ttf-dejavu
installed. A more in depth explanation can be found here .
Gnome-shell-extension-pop-shell is currently incompatible with wayland
… and causes the system to freeze when the first window is tiled and can render it unbootable. Solution is a hard reset and disabling either pop shell or wayland. If the system becomes unbootable, use a live USB to edit /etc/gdm/custom.conf to disable wayland and reboot.
Update not solved
Error Update
(12/24) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux58.preset: 'default'
-> -k /boot/vmlinuz-5.8-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.8-x86_64.img
==> ERROR: specified kernel image does not exist: `/boot/vmlinuz-5.8-x86_64'
==> Building image from preset: /etc/mkinitcpio.d/linux58.preset: 'fallback'
-> -k /boot/vmlinuz-5.8-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.8-x86_64-fallback.img -S autodetect
==> ERROR: specified kernel image does not exist: `/boot/vmlinuz-5.8-x86_64'
Fehler: Befehl konnte nicht korrekt ausgeführt werden
(13/24) Updating Kernel initcpios for Nvidia-DRM...
==> Building image from preset: /etc/mkinitcpio.d/linux58.preset: 'default'
-> -k /boot/vmlinuz-5.8-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.8-x86_64.img
==> ERROR: specified kernel image does not exist: `/boot/vmlinuz-5.8-x86_64'
==> Building image from preset: /etc/mkinitcpio.d/linux58.preset: 'fallback'
-> -k /boot/vmlinuz-5.8-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.8-x86_64-fallback.img -S autodetect
==> ERROR: specified kernel image does not exist: `/boot/vmlinuz-5.8-x86_64'
Fehler: Befehl konnte nicht korrekt ausgeführt werden
(14/24) Updating Grub-Bootmenu
Warning Update
(64/90) Aktualisiere manjaro-zsh-config [------------------------------------------------] 100%
Warnung: Verzeichnis-Berechtigungen unterscheiden sich für /root/
Dateisystem: 750 Paket: 755
...
(79/90) Aktualisiere samba [------------------------------------------------] 100%
Warnung: Verzeichnis-Berechtigungen unterscheiden sich für /etc/sudoers.d/
Dateisystem: 755 Paket: 750
(80/90) Aktualisiere sudo [------------------------------------------------] 100%
Warnung: Verzeichnis-Berechtigungen unterscheiden sich für /etc/sudoers.d/
Dateisystem: 755 Paket: 750
sudo mkinitcpio -P
sudo mkinitcpio -P
==> Building image from preset: /etc/mkinitcpio.d/linux58.preset: 'default'
-> -k /boot/vmlinuz-5.8-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.8-x86_64.img
==> ERROR: specified kernel image does not exist: `/boot/vmlinuz-5.8-x86_64'
==> Building image from preset: /etc/mkinitcpio.d/linux58.preset: 'fallback'
-> -k /boot/vmlinuz-5.8-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.8-x86_64-fallback.img -S autodetect
==> ERROR: specified kernel image does not exist: `/boot/vmlinuz-5.8-x86_64'
currently I do not get fixed the error … no reboot
thx for your tip … rename or copy from /boot/vmlinuz-linux58
to /boot/vmlinuz-5.8-x86_64
Something is not right with the hook, which copies the kernels to /boot
, the names are wrong and subsequently mkinitcpio
fails to build initramfs
:
(12/26) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux54.preset: 'default'
-> -k /boot/vmlinuz-5.4-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.4-x86_64.img
==> ERROR: specified kernel image does not exist: `/boot/vmlinuz-5.4-x86_64'
==> Building image from preset: /etc/mkinitcpio.d/linux58.preset: 'default'
-> -k /boot/vmlinuz-5.8-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.8-x86_64.img
==> ERROR: specified kernel image does not exist: `/boot/vmlinuz-5.8-x86_64'
Fehler: Befehl konnte nicht korrekt ausgeführt werden
(13/26) Updating Kernel initcpios for Nvidia-DRM...
==> Building image from preset: /etc/mkinitcpio.d/linux54.preset: 'default'
-> -k /boot/vmlinuz-5.4-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.4-x86_64.img
==> ERROR: specified kernel image does not exist: `/boot/vmlinuz-5.4-x86_64'
==> Building image from preset: /etc/mkinitcpio.d/linux58.preset: 'default'
-> -k /boot/vmlinuz-5.8-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.8-x86_64.img
==> ERROR: specified kernel image does not exist: `/boot/vmlinuz-5.8-x86_64'
Fehler: Befehl konnte nicht korrekt ausgeführt werden
(14/26) Updating Grub-Bootmenu
$ ll /boot/
drwxr-xr-x 7 root root 4,0K 24. Sep 09:05 .
drwxr-xr-x 21 root root 4,0K 21. Mai 13:24 ..
drwxr-xr-x 3 root root 512 1. Jan 1970 efi
drwxr-xr-x 6 root root 4,0K 24. Sep 09:05 grub
-rw-r--r-- 1 root root 3,1M 16. Jun 19:50 intel-ucode.img
-rw-r--r-- 1 root root 21 23. Sep 16:19 linux54-x86_64.kver
-rw-r--r-- 1 root root 21 23. Sep 16:34 linux58-x86_64.kver
-rw-r--r-- 1 root root 6,2M 24. Sep 09:05 vmlinuz-linux54
-rw-r--r-- 1 root root 6,5M 24. Sep 09:05 vmlinuz-linux58
Renamed them myself:
$ sudo mv /boot/vmlinuz-linux54 /boot/vmlinuz-5.4-x86_64
$ sudo mv /boot/vmlinuz-linux58 /boot/vmlinuz-5.8-x86_64
and afterwards reran:
$ sudo mkinitcpio -P && sudo update-grub
This results in unbootable systems otherwise!
8 Likes
pivpav
24 September 2020 07:53
5
During sudo mkinitcpio -P
I also noticed an error which might causing potential issues
==> Building image from preset: /etc/mkinitcpio.d/linux58.preset: 'default'
-> -k /boot/vmlinuz-5.8-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.8-x86_64.img
==> Starting build: 5.8.11-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [resume]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.8-x86_64.img
==> Image generation successful
This error doesn’t exist when building initramfs-5.7
Yochanan
Split this topic
24 September 2020 14:53
6
blw
24 September 2020 07:56
7
My system became unbootable as well. I had to revert to the btrfs-snapshot I made before the update.
Yochanan
Split this topic
24 September 2020 14:03
8
Nanook
24 September 2020 08:05
9
Problem with Opera: freezes when clicking Opera button, right-clicking, odd font sizes. Can be partially worked around by enabling HWA (opera://settings/system).See here: Latest Update Broke the Opera UI | Opera forums .
My laptop will not boot after this update on kernel 5.8, not sure why. It is stuck at HP splash screen which always shows up before log in screen. TTY does not work.
Can’t put in inxi
I’ll try to boot from kernel 5.7 and see how that works.
Managed to boot from kernel 5.7
inxi -Fxxxza -no-host on kernel 5.7
~ >>> inxi -Fxxxza -no-host
System:
Host: HP Kernel: 5.7.19-2-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-5.7-x86_64
root=UUID=9a466d45-9706-4f31-8e9b-737ed449768e rw quiet apparmor=1
security=apparmor udev.log_priority=3
Desktop: GNOME 3.36.6 tk: GTK 3.24.23 wm: gnome-shell dm: GDM 3.36.3
Distro: Manjaro Linux
Machine:
Type: Laptop System: HP product: HP Pavilion Gaming Laptop 15-cx0xxx
v: Type1ProductConfigId serial: <filter> Chassis: type: 10
serial: <filter>
Mobo: HP model: 8478 v: 70.57 serial: <filter> UEFI: Insyde v: F.22
date: 04/21/2020
Battery:
ID-1: BAT1 charge: 37.7 Wh condition: 37.7/52.8 Wh (71%) volts: 12.8/11.6
model: Hewlett-Packard PABAS0241231 type: Li-ion serial: <filter>
status: Full
CPU:
Topology: Quad Core model: Intel Core i5-8300H bits: 64 type: MT MCP
arch: Kaby Lake family: 6 model-id: 9E (158) stepping: A (10)
microcode: D6 L2 cache: 8192 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
bogomips: 36812
Speed: 800 MHz min/max: 800/4000 MHz Core speeds (MHz): 1: 800 2: 800
3: 800 4: 800 5: 800 6: 800 7: 800 8: 800
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional,
IBRS_FW, STIBP: conditional, RSB filling
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel UHD Graphics 630 vendor: Hewlett-Packard driver: i915
v: kernel bus ID: 00:02.0 chip ID: 8086:3e9b
Device-2: NVIDIA GP107M [GeForce GTX 1050 Mobile] vendor: Hewlett-Packard
driver: nvidia v: 450.66 alternate: nouveau,nvidia_drm bus ID: 01:00.0
chip ID: 10de:1c8d
Device-3: Cheng Uei Precision Industry (Foxlink) HP Wide Vision HD
Integrated Webcam
type: USB driver: uvcvideo bus ID: 1-5:3 chip ID: 05c8:03bc
Display: x11 server: X.org 1.20.9 compositor: gnome-shell
driver: modesetting,nvidia resolution: <xdpyinfo missing>
OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2) v: 4.6 Mesa 20.1.8
direct render: Yes
Audio:
Device-1: Intel Cannon Lake PCH cAVS vendor: Hewlett-Packard
driver: snd_hda_intel v: kernel alternate: snd_soc_skl,snd_sof_pci
bus ID: 00:1f.3 chip ID: 8086:a348
Device-2: NVIDIA GP107GL High Definition Audio vendor: Hewlett-Packard
driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:0fb9
Sound Server: ALSA v: k5.7.19-2-MANJARO
Network:
Device-1: Realtek RTL8822BE 802.11a/b/g/n/ac WiFi adapter
vendor: Hewlett-Packard driver: rtw_pci v: N/A modules: rtwpci port: 4000
bus ID: 02:00.0 chip ID: 10ec:b822
IF: wlo1 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Hewlett-Packard driver: r8169 v: kernel port: 3000 bus ID: 05:00.0
chip ID: 10ec:8168
IF: eno1 state: down mac: <filter>
Drives:
Local Storage: total: 238.47 GiB used: 102.78 GiB (43.1%)
SMART Message: Required tool smartctl not installed. Check --recommends
ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLW256HEHP-000H1
size: 238.47 GiB block size: physical: 512 B logical: 512 B
speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: CXB73H1Q scheme: GPT
Partition:
ID-1: / raw size: 238.17 GiB size: 233.43 GiB (98.01%)
used: 102.78 GiB (44.0%) fs: ext4 dev: /dev/nvme0n1p2
Swap:
Alert: No Swap data was found.
Unmounted:
Message: No unmounted partitions found.
Sensors:
System Temperatures: cpu: 55.0 C mobo: 29.8 C
Fan Speeds (RPM): N/A
Info:
Processes: 331 Uptime: 2m Memory: 15.53 GiB used: 1.79 GiB (11.5%)
Init: systemd v: 246 Compilers: gcc: 10.2.0 alt: 8/9 clang: 10.0.1
Packages: 1362 pacman: 1341 lib: 364 flatpak: 12 snap: 9 Shell: Zsh v: 5.8
running in: gnome-terminal inxi: 3.1.05
I am all ears in helping to solve this problem (not sure where to look first).
philm
24 September 2020 08:11
12
I’ve to see about mkinitcpio . I deleted our overlay . Let me see what to fix.
1 Like
My update showed none of these errors while updating (used terminal) so I wasn’t sure if it applied.
philm
24 September 2020 08:17
14
Pushed some more updates …
:: Different overlay package(s) in repository community x86_64
-------------------------------------------------------------------------------
PACKAGE testing unstable
-------------------------------------------------------------------------------
breeze-gtk-git5.20.80.r394.ga37192d-15.20.80.r395.g25b81e3-1
deepin-desktop-base 3:2019.07.10-1 -
deepin-kwin-dev 5.0.0-2 -
deepin-live 3.2-1 -
deepin-wallpapers 2:1.7.7-1 -
discover-git5.20.80.r7837.gb294c93f-15.20.80.r7839.g76b562c6-1
kde-cli-tools-git5.20.80.r1806.gede4ba5-15.20.80.r1807.gcbab4f0-1
kdeplasma-addons-git5.20.80.r8388.gfe86cf62f-15.20.80.r8389.geda917ebe-1
kio-git5.75.0.r4211.gd8fc059a-15.75.0.r4212.g5da32a17-1
kirigami2-git5.75.0.r2418.g7575cc3d-15.75.0.r2425.g95781e80-1
kquickcharts-git r380.geeb4ab0-1 r381.gb231ab0-1
krunner-git5.75.0.r503.g57ae6f4-15.75.0.r505.g635e11f-1
kwayland-integration-git5.20.80.r153.g43ba980-15.20.80.r154.g00ae501-1
plasma-framework-git5.75.0.r15573.gc0ebacfa6-15.75.0.r15576.g16f852ea4-1
plasma-wayland-session-git5.20.80.r9431.g811d85cbd-15.20.80.r9435.g665836f56-1
plasma-workspace-git5.20.80.r9431.g811d85cbd-15.20.80.r9435.g665836f56-1
systemsettings-git5.20.80.r2269.g14529229-15.20.80.r2270.g2e82e4fc-1
xdg-desktop-portal-kde-git5.20.80.r316.g0cd7a9d-15.20.80.r317.g8f488ca-1
:: Different overlay package(s) in repository core x86_64
-------------------------------------------------------------------------------
PACKAGE testing unstable
-------------------------------------------------------------------------------
mkinitcpio - 28-1.0
2 Likes
also same error on unstable for mkinitcpio
My issue solved by post 2
$ sudo mv /boot/vmlinuz-linux58 /boot/vmlinuz-5.8-x86_64
$ sudo mkinitcpio -P && sudo update-grub
2 Likes
philm
24 September 2020 08:30
21
Updated mkinitcpio fixes the issue:
Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux414.preset: 'default'
-> -k /boot/vmlinuz-4.14-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.14-x86_64.img
==> Starting build: 4.14.199-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-4.14-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux414.preset: 'fallback'
-> -k /boot/vmlinuz-4.14-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.14-x86_64-fallback.img -S autodetect
==> Starting build: 4.14.199-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-4.14-x86_64-fallback.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux419.preset: 'default'
-> -k /boot/vmlinuz-4.19-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.19-x86_64.img
==> Starting build: 4.19.147-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-4.19-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux419.preset: 'fallback'
-> -k /boot/vmlinuz-4.19-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.19-x86_64-fallback.img -S autodetect
==> Starting build: 4.19.147-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-4.19-x86_64-fallback.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux44.preset: 'default'
-> -k /boot/vmlinuz-4.4-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.4-x86_64.img
==> Starting build: 4.4.237-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-4.4-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux44.preset: 'fallback'
-> -k /boot/vmlinuz-4.4-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.4-x86_64-fallback.img -S autodetect
==> Starting build: 4.4.237-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-4.4-x86_64-fallback.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux49.preset: 'default'
-> -k /boot/vmlinuz-4.9-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.9-x86_64.img
==> Starting build: 4.9.237-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-4.9-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux49.preset: 'fallback'
-> -k /boot/vmlinuz-4.9-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.9-x86_64-fallback.img -S autodetect
==> Starting build: 4.9.237-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-4.9-x86_64-fallback.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux54.preset: 'default'
-> -k /boot/vmlinuz-5.4-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.4-x86_64.img
==> Starting build: 5.4.67-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.4-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux54.preset: 'fallback'
-> -k /boot/vmlinuz-5.4-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.4-x86_64-fallback.img -S autodetect
==> Starting build: 5.4.67-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.4-x86_64-fallback.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux57.preset: 'default'
-> -k /boot/vmlinuz-5.7-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.7-x86_64.img
==> Starting build: 5.7.19-2-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.7-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux57.preset: 'fallback'
-> -k /boot/vmlinuz-5.7-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.7-x86_64-fallback.img -S autodetect
==> Starting build: 5.7.19-2-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.7-x86_64-fallback.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux58.preset: 'default'
-> -k /boot/vmlinuz-5.8-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.8-x86_64.img
==> Starting build: 5.8.11-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.8-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux58.preset: 'fallback'
-> -k /boot/vmlinuz-5.8-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.8-x86_64-fallback.img -S autodetect
==> Starting build: 5.8.11-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.8-x86_64-fallback.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux59.preset: 'default'
-> -k /boot/vmlinuz-5.9-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.9-x86_64.img
==> Starting build: 5.9.0-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.9-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux59.preset: 'fallback'
-> -k /boot/vmlinuz-5.9-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.9-x86_64-fallback.img -S autodetect
==> Starting build: 5.9.0-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.9-x86_64-fallback.img
==> Image generation successful
Updating Grub-Bootmenu
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.9-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.9-x86_64.img
Found initrd fallback image: /boot/initramfs-5.9-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.8-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.8-x86_64.img
Found initrd fallback image: /boot/initramfs-5.8-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.7-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.7-x86_64.img
Found initrd fallback image: /boot/initramfs-5.7-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.4-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.4-x86_64.img
Found initrd fallback image: /boot/initramfs-5.4-x86_64-fallback.img
Found linux image: /boot/vmlinuz-4.19-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-4.19-x86_64.img
Found initrd fallback image: /boot/initramfs-4.19-x86_64-fallback.img
Found linux image: /boot/vmlinuz-4.14-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-4.14-x86_64.img
Found initrd fallback image: /boot/initramfs-4.14-x86_64-fallback.img
Found linux image: /boot/vmlinuz-4.9-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-4.9-x86_64.img
Found initrd fallback image: /boot/initramfs-4.9-x86_64-fallback.img
Found linux image: /boot/vmlinuz-4.4-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-4.4-x86_64.img
Found initrd fallback image: /boot/initramfs-4.4-x86_64-fallback.img
Found Manjaro Linux (18.0-alpha-1) on /dev/sda5
Found Manjaro Linux (19.0.2) on /dev/sda6
Adding boot menu entry for UEFI Firmware Settings ...
Found memtest86+ image: /boot/memtest86+/memtest.bin
done
4 Likes
something wrong here , i have update mirrors to get update mkinitcpio
is it this error " `/" that should be " '/" ?
update : error name come from old mkinitcpio
sudo mkinitcpio -P
==> Building image from preset: /etc/mkinitcpio.d/linux419.preset: 'default'
-> -k /boot/vmlinuz-4.19-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.19-x86_64.img
==> ERROR: specified kernel image does not exist: `/boot/vmlinuz-4.19-x86_64'
==> Building image from preset: /etc/mkinitcpio.d/linux419.preset: 'fallback'
-> -k /boot/vmlinuz-4.19-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.19-x86_64-fallback.img -S autodetect
==> ERROR: specified kernel image does not exist: `/boot/vmlinuz-4.19-x86_64'
==> Building image from preset: /etc/mkinitcpio.d/linux54.preset: 'default'
-> -k /boot/vmlinuz-5.4-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.4-x86_64.img
==> ERROR: specified kernel image does not exist: `/boot/vmlinuz-5.4-x86_64'
==> Building image from preset: /etc/mkinitcpio.d/linux54.preset: 'fallback'
-> -k /boot/vmlinuz-5.4-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.4-x86_64-fallback.img -S autodetect
==> ERROR: specified kernel image does not exist: `/boot/vmlinuz-5.4-x86_64'
==> Building image from preset: /etc/mkinitcpio.d/linux57.preset: 'default'
-> -k /boot/vmlinuz-5.7-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.7-x86_64.img
==> Starting build: 5.7.19-2-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.7-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux57.preset: 'fallback'
-> -k /boot/vmlinuz-5.7-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.7-x86_64-fallback.img -S autodetect
==> Starting build: 5.7.19-2-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: aic94xx
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.7-x86_64-fallback.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux58.preset: 'default'
-> -k /boot/vmlinuz-5.8-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.8-x86_64.img
==> ERROR: specified kernel image does not exist: `/boot/vmlinuz-5.8-x86_64'
==> Building image from preset: /etc/mkinitcpio.d/linux58.preset: 'fallback'
-> -k /boot/vmlinuz-5.8-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.8-x86_64-fallback.img -S autodetect
==> ERROR: specified kernel image does not exist: `/boot/vmlinuz-5.8-x86_64'
mbod
24 September 2020 09:08
24
May be I am wrong, but I believe the mkinitcpio
update is not fixing the initial problem.
The initial problem is that the new kernel packages linux54-5.4.67-1-x86_64.pkg.tar.zst
and linux58-5.8.11-1-x86_64.pkg.tar.zst
install kernel images with wrong names:
/boot/vmlinuz-5.4
/boot/vmlinuz-5.8
It is my understanding that they are not found even by the new mkinitcpio
.
They should be renamed to
/boot/vmlinuz-5.4-x86_64
/boot/vmlinuz-5.8-x86_64
1 Like
this come form /etc/mkinitcpio.d/linuxXY.preset
i have this 4.14 , 5.4 also 5.8
# mkinitcpio preset file for the 'linux54' package
ALL_config="/etc/mkinitcpio.conf"
ALL_kver="/boot/vmlinuz-5.4-x86_64"
PRESETS=('default' 'fallback')
#default_config="/etc/mkinitcpio.conf"
default_image="/boot/initramfs-5.4-x86_64.img"
#default_options=""
#fallback_config="/etc/mkinitcpio.conf"
fallback_image="/boot/initramfs-5.4-x86_64-fallback.img"
fallback_options="-S autodetect"
and if you have bad name vmlinuz
ls -lha vmlinuz*
-rw-r--r-- 1 root root 5,8M 24 sept. 10:34 vmlinuz-419-x86_64
-rw-r--r-- 1 root root 6,2M 24 sept. 10:34 vmlinuz-54-x86_64
-rw-r--r-- 1 root root 6,5M 24 sept. 10:34 vmlinuz-58-x86_64
soluce :
suppress vmlinuz ( name bad )
redo
sudo pacman -S linuxNM
it’s ok for result mkinitcpio