[Testing Update] 2019-06-01 - Kernels, Xorg-Server, FF-Dev, Haskell, Python

Kernels 4.19, 5.1 and now 5.2rc2-experimental* installed and running fine for both my machines.

*desktop only. the notebook won't boot with 5.2rc yet, it's locking up before Xorg is initialised. i'll investigate this further later. 4.19 and 5.1 are fine though.

2 Likes

all good for me: linux419/50+zfs+nvidia+cinnamon

Just updated my ManjaroTesting+FedoraStable VM. Did F first, all ok, then during its reboot i chose M & logged in. Did its update in Konsole via sudo pacman-mirrors -f 7 && sudo pacman -Syyu. Error messages right at the very end of the process but annoyingly i managed to accidentally close Yakuake & lose the output whilst trying to copy it. Decided to install kernel 5.1 before doing the reboot, saw IIRC the same error messages at the end:

Summary
The following packages will be installed:
linux51
linux51-virtualbox-guest-modules

Starting
resolving dependencies...
looking for conflicting packages...
Packages (2) linux51-5.1.6-1  linux51-virtualbox-guest-modules-6.0.8-5
Total Download Size:    77.37 MiB
Total Installed Size:  129.77 MiB
:: Proceed with installation? [Y/n]
:: Retrieving packages...
downloading linux51-5.1.6-1-x86_64.pkg.tar.xz...
downloading linux51-virtualbox-guest-modules-6.0.8-5-x86_64.pkg.tar.xz...
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
checking available disk space...
:: Processing package changes...
installing linux51...
Optional dependencies for linux51
    crda: to set the correct wireless channels of your country [installed]
installing linux51-virtualbox-guest-modules...
===> You may want to load vboxguest, vboxsf and vboxvideo
:: Running post-transaction hooks...
(1/4) Updating linux51 module dependencies...
(2/4) Updating linux51 initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux51.preset: 'default'
-> -k /boot/vmlinuz-5.1-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.1-x86_64.img
==> Starting build: 5.1.6-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]
cannot open file au
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.1-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux51.preset: 'fallback'
  -> -k /boot/vmlinuz-5.1-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.1-x86_64-fallback.img -S autodetect
==> Starting build: 5.1.6-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]
cannot open file au
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.1-x86_64-fallback.img
==> Image generation successful
(3/4) Updating Grub-Bootmenu
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.1-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.1-x86_64.img
Found initrd fallback image: /boot/initramfs-5.1-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.0-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.0-x86_64.img
Found initrd fallback image: /boot/initramfs-5.0-x86_64-fallback.img
Found linux image: /boot/vmlinuz-4.19-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.19-x86_64.img
Found initrd fallback image: /boot/initramfs-4.19-x86_64-fallback.img
/dev/mapper/control: open failed: No such device
Failure to communicate with kernel device-mapper driver.
Check that device-mapper is available in the kernel.
Incompatible libdevmapper 1.02.156 (2019-03-22) and kernel driver (unknown version).
Command failed.
/dev/mapper/control: open failed: No such device
Failure to communicate with kernel device-mapper driver.
Check that device-mapper is available in the kernel.
Incompatible libdevmapper 1.02.156 (2019-03-22) and kernel driver (unknown version).
Command failed.
Found memtest86+ image: /boot/memtest86+/memtest.bin
done
(4/4) Arming ConditionNeedsUpdate...


Done ...

Apparently oblivious to the maxim that doing the same thing over & over but expecting different outcomes is madness, i chose a manual attempt at updating grub:

Summary
[k@k-VM-ManjaroFedora ~]$ sudo update-grub
[sudo] password for k: 
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.1-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.1-x86_64.img
Found initrd fallback image: /boot/initramfs-5.1-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.0-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.0-x86_64.img
Found initrd fallback image: /boot/initramfs-5.0-x86_64-fallback.img
Found linux image: /boot/vmlinuz-4.19-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.19-x86_64.img
Found initrd fallback image: /boot/initramfs-4.19-x86_64-fallback.img
/dev/mapper/control: open failed: No such device
Failure to communicate with kernel device-mapper driver.
Check that device-mapper is available in the kernel.
Incompatible libdevmapper 1.02.156 (2019-03-22) and kernel driver (unknown version).
Command failed.
/dev/mapper/control: open failed: No such device
Failure to communicate with kernel device-mapper driver.
Check that device-mapper is available in the kernel.
Incompatible libdevmapper 1.02.156 (2019-03-22) and kernel driver (unknown version).
Command failed.
Found memtest86+ image: /boot/memtest86+/memtest.bin
done
[k@k-VM-ManjaroFedora ~]$

I've not attempted to reboot the VM as it seems likely to me it'll end up at a rescue screen. Should i play with trying downgrades of libdevmapper? This error is a new one for me.

You may need to re-check this in Octopi options -> General tab.

Worked fine in Xfce and Cinnamon via terminal.

I didn't get this error this time, but have gotten it occasionally in the past (real hardware, I don't have a VM). Being the novice that I am, I assumed it was because the kernel had been upgraded. I just rebooted and moved on in ignorant bliss with no ill effects.

I too had problems with Octopi. It would not run the update in a terminal. A terminal window opened, my sudo password was asked and when I typed it in the terminal window showed nothing. It just sat there empty. I killed the process, opened a TTY2 session and upgraded from there using pacman. The Octopi notifier went away as it should when I rebooted.

I have the same problem. It opened xterm instead of konsole. I tried to change it back in Octopi but it says that there are some information missing:
Symbol-Pfad Informationen sind unvollständig.
Don't know yet what to do now.

I have found one issue that I do not know if it came with this update or earlier this week:
pacman-mirrors now demand superuser. sudo no longer work, I have to be root to generate the mirror list.

Are you sure? I just did on a fresh install of the latest testing ISO to a brand new SSD yesterday, and did my usual:
sudo pacman-mirrors --geoip

Edit to add: As usual, at install time, I check the box to use same password as the root password.

Can't reproduce on my side: I can launch pacman-mirrors with sudo correctly.

[awesome@i56400 ~]$ date
Sat Jun  1 17:06:06 EDT 2019
[awesome@i56400 ~]$ sudo pacman-mirrors -f 3
[sudo] password for awesome: 
::INFO Downloading mirrors from repo.manjaro.org
::INFO Using custom mirror file
::INFO Querying mirrors - This may take some time
  1.196 United_States  : https://mirrors.ocf.berkeley.edu/manjaro/
  1.186 United_States  : https://mirror.math.princeton.edu/pub/manjaro/
  1.338 United_States  : http://distro.ibiblio.org/manjaro/
::INFO Writing mirror list
::United_States   : https://mirror.math.princeton.edu/pub/manjaro/testing/$repo/$a
::United_States   : https://mirrors.ocf.berkeley.edu/manjaro/testing/$repo/$arch
::United_States   : http://distro.ibiblio.org/manjaro/testing/$repo/$arch
::INFO Mirror list generated and saved to: /etc/pacman.d/mirrorlist
[awesome@i56400 ~]$ sudo pacman -Syyu
:: Synchronizing package databases...
 core                     151.7 KiB   203K/s 00:01 [######################] 100%
 extra                   1811.0 KiB   302K/s 00:06 [######################] 100%
 community                  5.2 MiB   313K/s 00:17 [######################] 100%
 multilib                 184.0 KiB   526K/s 00:00 [######################] 100%
 DEB_Arch_Extra             4.2 KiB  0.00B/s 00:00 [######################] 100%
 DEB_Arch_Extra.sig       280.0   B  0.00B/s 00:00 [######################] 100%
:: Starting full system upgrade...
 there is nothing to do
[awesome@i56400 ~]$ pacman -Q pacman-mirrors
pacman-mirrors 4.14.2-1
[awesome@i56400 ~]$ 

Let's see if others have a similar issue.

No issues here on Deepin unstable.

::INFO Downloading mirrors from repo.manjaro.org
::INFO User generated mirror list
::------------------------------------------------------------
::INFO Custom mirror file saved: /var/lib/pacman-mirrors/custom-mirrors.json
::INFO Using default mirror file
::INFO Querying mirrors - This may take some time
  1.066 United_States  : https://repo.ialab.dsu.edu/manjaro/
  0.605 United_States  : http://repo.ialab.dsu.edu/manjaro/
  1.120 United_States  : https://mirrors.ocf.berkeley.edu/manjaro/
  0.803 United_States  : https://mirror.math.princeton.edu/pub/manjaro/
  0.407 United_States  : https://mirrors.gigenet.com/manjaro/
  0.485 United_States  : http://mirrors.gigenet.com/manjaro/
::INFO Writing mirror list
::United_States   : https://mirrors.gigenet.com/manjaro/unstable
::United_States   : https://repo.ialab.dsu.edu/manjaro/unstable
::United_States   : https://mirror.math.princeton.edu/pub/manjaro/unstable
::United_States   : https://mirrors.ocf.berkeley.edu/manjaro/unstable
::INFO Mirror list generated and saved to: /etc/pacman.d/mirrorlist

::INFO Mirror list generated and saved to: /etc/pacman.d/mirrorlist
::INFO To reset custom mirrorlist 'sudo pacman-mirrors -id'
::INFO To remove custom config run 'sudo pacman-mirrors -c all'
error: you cannot perform this operation unless you are root.

See the last line? Apparently I cannot save changes the mirror list even as sudo. I do not get the error if I switch to su.

EDIT: Booting into my Xfce install. Same issue (also Testing). HOWEVER: Actually looking at the mirror list it seems to all be there. So it's one of the other commands that pacman-mirrors run that generates the error, but the end result looks correct. Weird.

EDIT again: I missed the sudo in the pacman -Syyu bit. Because stupid. Never mind me.

Ta. I slept on it, saw no additional thoughts herein [nor had i any], so grit my teeth & initiated the reboot of that VM, fearing the worst. No rescue screen, but no boot menu either, just straight into Manjaro [which itself is fine as usual]. Therein, i repeated the grub update, & happily this time, it worked correctly/fully, finding my Fedora 2nd-boot [which per my earlier post, had failed before]:

Summary
[k@k-VM-ManjaroFedora ~]$ sudo update-grub
[sudo] password for k: 
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.1-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.1-x86_64.img
Found initrd fallback image: /boot/initramfs-5.1-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.0-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.0-x86_64.img
Found initrd fallback image: /boot/initramfs-5.0-x86_64-fallback.img
Found linux image: /boot/vmlinuz-4.19-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.19-x86_64.img
Found initrd fallback image: /boot/initramfs-4.19-x86_64-fallback.img
Found Fedora 30 (Thirty) on /dev/sdb2
Found memtest86+ image: /boot/memtest86+/memtest.bin
done
[k@k-VM-ManjaroFedora ~]$ 

Did another VM reboot, & indeed now have the full boot menu back. Phew.

Given this VM was the dual-boot testbed i established weeks ago prior to then successfully deploying in Tower for real, this VM's update hiccup alarmed me & made me hold back from doing the update in real Tower. Now it seems i can proceed...


Additional info [irrelevant for all Manjaroos unless also using Fedora30, but provided fyi].

Upon reflection, i now strongly suspect that this storm in my teacup was caused by --surprise surprise-- my own usual ham-fisted incompetence. Unlike the magnificent Manjaro kernel update/install process that automatically includes the update-grub routine, in F30 when one installs a new kernel, one must remember afterwards to manually run the update command, before rebooting, otherwise said new kernel/s remain invisible in the boot menu. Furthermore, the choice of specific command is dependent on whether one's F30 installation was UEFI or legacy. In the case of my VM, last night i muddled myself & mistakenly ran the F30 command for UEFI, when in fact i should have done the GRUB2 one. Ie, last night i ran sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg, whereas this morning i corrected my error via sudo grub2-mkconfig -o /boot/grub2/grub.cfg.

Such a silly sausage.

3 Likes

mpv core dump with hwdec=yes or hwdec=cuda and Nvidia 430.14-3.

mpv
Segmentation fault (core dumped)

journalctl
systemd-coredump[1227]: Process 1193 (mpv) of user 1000 dumped core.

dmesg

[   45.235117] mpv[1193]: segfault at e ip 00007fe8ddfa30c0 sp 00007ffc5e248d40 error 4 in libnvcuvid.so.430.14[7fe8ddf62000+312000]
[   45.235123] Code: 48 c7 40 08 00 00 00 00 48 c7 40 10 00 00 00 00 c3 90 90 90 90 90 90 90 90 90 f6 07 08 53 48 89 fb 75 10 48 8b 97 50 01 00 00 <0f> b7 42 0e 66 ff c0 74 07 5b 31 c0 c3 0f

First reported on Testing 2019-5-29.

I had no issues, but getting this message during memtest:

Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1

1 Like

I think that BIOS does not support NVMe, only UEFI.

@Phrosgone
the link from banjo will sort you out. :wink:

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

Forum kindly sponsored by Bytemark