- Arch-general - lists.archlinux.org

PKCS#7 signature not signed with a trusted key
by Ralf Mardorf 17 Apr '23

17 Apr '23

Hi, some kernels that do boot on my old UEFI computer with legacy boot enabled, don't boot on my new UEFI computer were the Intel processor graphics doesn't allow to enable legacy boot, but at least _secure boot_ is _disabled_. What can I do to get rid of the error? The kernel parameter "module.sig_enforce=1" is _never_ used. A kernel that fails to boot with "PKCS#7 signature not signed with a trusted key": [rocketmouse@archlinux ~]$ ls -hl /lib/modules/4.19.271-rt120-0.300-cornflower/updates/dkms/ .rw-r--r-- root root 65 KB Sun Apr 2 15:42:39 2023  r8125.ko.xz .rw-r--r-- root root 142 KB Wed Mar 1 20:17:25 2023  vboxdrv.ko.xz .rw-r--r-- root root 4.6 KB Wed Mar 1 20:17:25 2023  vboxnetadp.ko.xz .rw-r--r-- root root 14 KB Wed Mar 1 20:17:25 2023  vboxnetflt.ko.xz [rocketmouse@archlinux ~]$ grep MODULE_SIG /lib/modules/4.19.271-rt120-0.300-cornflower/build/.config CONFIG_MODULE_SIG=y # CONFIG_MODULE_SIG_FORCE is not set CONFIG_MODULE_SIG_ALL=y # CONFIG_MODULE_SIG_SHA1 is not set # CONFIG_MODULE_SIG_SHA224 is not set # CONFIG_MODULE_SIG_SHA256 is not set # CONFIG_MODULE_SIG_SHA384 is not set CONFIG_MODULE_SIG_SHA512=y CONFIG_MODULE_SIG_HASH="sha512" CONFIG_MODULE_SIG_KEY="certs/signing_key.pem" A kernel that doesn't fail: [rocketmouse@archlinux ~]$ ls -hl /lib/modules/6.2.10-arch1-1/updates/dkms/ .rw-r--r-- root root 116 KB Sun Apr 9 13:32:10 2023  r8125.ko.zst .rw-r--r-- root root 221 KB Sun Apr 9 13:31:59 2023  vboxdrv.ko.zst .rw-r--r-- root root 27 KB Sun Apr 9 13:31:59 2023  vboxnetadp.ko.zst .rw-r--r-- root root 47 KB Sun Apr 9 13:31:59 2023  vboxnetflt.ko.zst [rocketmouse@archlinux ~]$ grep MODULE_SIG /lib/modules/6.2.10-arch1-1/build/.config CONFIG_MODULE_SIG_FORMAT=y CONFIG_MODULE_SIG=y # CONFIG_MODULE_SIG_FORCE is not set CONFIG_MODULE_SIG_ALL=y # CONFIG_MODULE_SIG_SHA1 is not set # CONFIG_MODULE_SIG_SHA224 is not set # CONFIG_MODULE_SIG_SHA256 is not set # CONFIG_MODULE_SIG_SHA384 is not set CONFIG_MODULE_SIG_SHA512=y CONFIG_MODULE_SIG_HASH="sha512" CONFIG_MODULE_SIG_KEY="certs/signing_key.pem" # CONFIG_MODULE_SIG_KEY_TYPE_RSA is not set CONFIG_MODULE_SIG_KEY_TYPE_ECDSA=y Regards, Ralf

3 5

Is a tool available to check the integrity of copied files?
by Ralf Mardorf 16 Apr '23

16 Apr '23

Hi, my google search was "does linux diff compare data using a cache". I'm trying to figure out what's going on. The first diff of 10 GiB of data copied from a SATA3 SSD to an USB 2 stick connected to an USB 3 port took around a minute, right after the copy finished. A second diff needed 3 seconds. Both returned exit status 0. It's impossible to read 10 GiB of data in 3 seconds from an USB 2 stick. Does diff use cached data instead of comparing the "real" files line by line? Google returned "diff isn't doing any caching. The OS is. If you are using Linux, you can flush the disk buffers and cache". I expected that diff ensures to compare the "real" files line by line, but seemingly diff isn't aimed to check integrity of data. Does a command exist that compares "real" files, not just cached files by default? I experience weird things with Raptor Lake hardware, especially if USB is involved and I want to check the integrity of USB transferred, saved files by using a tool, without manually clearing cached data manually. Regards, Ralf

7 12

System is randomly freezing, would like troubleshooting help
by Luna Celeste 16 Apr '23

16 Apr '23

I have a System76 Thelio machine running Arch (fully up to date as of a few hours ago today). For quite a while now (at least a few months), it's been randomly hanging. I've configured the system to provide a crash dump per the Kdump wiki page, but whenever I reboot it after one of these hangs (or use the sysrq crash key), there is no /proc/vmcore file, and there's nothing in the logs. As you can understand, this makes troubleshooting difficult. In addition to this, I've not been able to identify many common factors of the hangs. The only thing that seems to be consistent is that most of the hangs occur when the system puts the display to sleep. But even this isn't consistent; today's hang occurred while the display was active (though I turned off the monitor). I've changed hardware and operating systems a few times. I originally ran PopOS on this machine, and experienced hangs there with an NVIDIA graphics card, but I moved to AMD when installing Manjaro. Again, to be clear, the machine does have a very up to date Arch install presently. The hangs occur with both X11 and Wayland. Sometimes it happens a few hours after I boot the machine, sometimes (like today's) it took a week or two. About the only unusual thing about the system is that I'm running ZFS. The root filesystem for this installation runs on ZFS, but this wasn't the case when it ran PopOS. I still had a ZFS pool on the PopOS machine. I have another ZFS pool with my home directory and my libvirt VMs on it. That said, neither of the pools have any errors, and I scrub them regularly. As I said at the start of this message, I've been struggling to figure out the problem for a few months and I'm not sure how to make progress troubleshooting it. I don't see anything in dmesg about overheating, or hardware failures, or anything like that. The machine works great... until it very suddenly doesn't. So how do I go about figuring out what's going on? I'd love to be able to -- Cheers, Luna Celeste

6 26

patches, command line long options support for arch-nspawn from devtools
by u34＠net9.ga 16 Apr '23

16 Apr '23

Hello, offload-build.in, https://gitlab.archlinux.org/archlinux/devtools/-/blob/master/src/offload-b… , has long options support for some time. Perhaps a long time. The following add long options support for arch-nspawn.in. The way long options is implemented for arch-nsapwn neccesitate changing the way it is called. There fore, archbuild.in, makechrootpkg.in and mkarchroot.in, were modfied accordingly. https://gitlab.com/ZjYwMj/devtools/-/commit/37c4602efb7642012c35a75b70a2943… (arch-nspawn.in) https://gitlab.com/ZjYwMj/devtools/-/commit/701c306d231e8faa2adc5d16b480165… (archbuild.in) https://gitlab.com/ZjYwMj/devtools/-/commit/64a434af60a1cadec37a9665318f0de… (makechrootpkg.in) https://gitlab.com/ZjYwMj/devtools/-/commit/6cc49ba9c8eed250c2cfe7bd05c6784… (mkarchroot.in) I can see the follwoing 12 scripts also call arch-nspawn: 1. /usr/bin/extra-x86_64-build 2. /usr/bin/extra-x86_64_v3-build 3. /usr/bin/gnome-unstable-x86_64-build 4. /usr/bin/kde-unstable-x86_64-build 5. /usr/bin/makerepropkg 6. /usr/bin/multilib-build 7. /usr/bin/multilib-staging-build 8. /usr/bin/multilib-testing-build 9. /usr/bin/staging-x86_64-build 10. /usr/bin/staging-x86_64_v3-build 11. /usr/bin/testing-x86_64-build 12. /usr/bin/testing-x86_64_v3-build I could not see where their source files are. In addition, manual pages, and other documentation, were not updated. Hardly tested. Please comment. -- u34

1 0

grub.cfg
by Ralf Mardorf 10 Apr '23

10 Apr '23

Hi, this is an old syslinux menu entry I try to convert to a grub.cfg menu entry. $ grep "X .Moon" /boot/syslinux/syslinux.cfg -B1 -A3 LABEL Moonstudio MENU LABEL Ubuntu X ^Moon Studio lowlatency LINUX /.boot/ubuntu_moonstudio/boot/vmlinuz-lowlatency APPEND root=LABEL=moonstudio ro INITRD /.boot/ubuntu_moonstudio/boot/initrd.img-lowlatency I don't understand a few things provided by https://wiki.archlinux.org/title/GRUB#Boot_menu_entry_examples . The syslinux bootloader, syslinux.cfg and the path /.boot/ubuntu_moonstudio/boot/ are on a MBR partition with the label "s3.archlinux", the directories of the other Linux install's root directory are on a partition with the label "moonstudio". The new grub2 and grub.cfg are on a GPT partition with the label "m1.xubu20.04", but this shouldn't matter. IIUC the grub.cfg entry should read menuentry "Ubuntu X Moon Studio lowlatency" { search --no-floppy --set=root --label s3.archlinux linux /.boot/ubuntu_moonstudio/boot/vmlinuz-lowlatency root=LABEL=moonstudio ro initrd /.boot/ubuntu_moonstudio/boot/initrd.img-lowlatency } OTOH I've got some doubts, should it be vice versa search --no-floppy --set=root --label moonstudio linux /.boot/ubuntu_moonstudio/boot/vmlinuz-lowlatency root=LABEL=s3.archlinux ro should it read root=LABEL or root=label or else? The fstab of the "Ubuntu X Moon Studio lowlatency" install contains a line to bind mount boot: /mnt/archlinux/.boot/ubuntu_moonstudio/boot /boot none bind 0 0 Regards, Ralf

1 3

X11 Input Settings Reset During Kernel Upgrade
by 2QdxY4RzWzUUiLuE＠potatochowder.com 09 Apr '23

09 Apr '23

Greetings, Call me old fashioned, but I run startx manually and I have an .xinitrc file. In that file, I run setxkbmap, xset, and xinput to set up my keyboard and my trackpad. This has been working for years, across three consecutive laptops, with minor adjustments to the parameters and input device names. A few weeks or a month ago, some system upgrades (i.e., pacman -S ...) reset those settings. The symptoms are an extremely slow trackpad and the default keyboard layout (dead keys and all). If I re-run the configuration commands from my .xinitrc file, all is well. It's hard to tell exactly which part of the process resets my settings, but I'm pretty sure it's during the post-transaction hooks, possibly around step 5/7 Updating module dependencies, or near the beginning of step 6/7 updating linux initcpios. It only happens when pacman rebuilds my kernel; at first, I thought it was tied to systemd upgrades, but it happened this morning, and there is no systemd upgrade. I run a stock kernel with liitle no customization. So far, none of the upgrades have failed, and I've not had problems rebooting with the new kernels. I do see entries in Xorg.0.log related to input devices from around that time, but I can't correlate those entries with the output from pacman. I hope the relevant section is below. Any thoughts? What other information can I provide? What experiments can I run? Thank you, Dan [759472.487] (II) config/udev: Adding input device PC Speaker (/dev/input/event8) [759472.487] (II) No input driver specified, ignoring this device. [759472.487] (II) This device may have been added with another device file. [759472.487] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event17) [759472.487] (II) No input driver specified, ignoring this device. [759472.487] (II) This device may have been added with another device file. [759472.488] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=8 (/dev/input/event20) [759472.488] (II) No input driver specified, ignoring this device. [759472.488] (II) This device may have been added with another device file. [759472.488] (II) config/udev: removing device ELAN0412:01 04F3:316F Touchpad [759472.488] (**) Option "fd" "88" [759472.488] (II) event15 - ELAN0412:01 04F3:316F Touchpad: device removed [759472.488] (II) UnloadModule: "libinput" [759472.488] (II) systemd-logind: releasing fd for 13:79 [759472.530] (II) config/udev: Adding input device ELAN0412:01 04F3:316F Touchpad (/dev/input/event15) [759472.530] (**) ELAN0412:01 04F3:316F Touchpad: Applying InputClass "libinput touchpad catchall" [759472.530] (II) Using input driver 'libinput' for 'ELAN0412:01 04F3:316F Touchpad' [759472.531] (II) systemd-logind: got fd for /dev/input/event15 13:79 fd 86 paused 0 [759472.531] (**) ELAN0412:01 04F3:316F Touchpad: always reports core events [759472.531] (**) Option "Device" "/dev/input/event15" [759472.532] (II) event15 - ELAN0412:01 04F3:316F Touchpad: is tagged by udev as: Touchpad [759472.532] (II) event15 - ELAN0412:01 04F3:316F Touchpad: device is a touchpad [759472.532] (II) event15 - ELAN0412:01 04F3:316F Touchpad: device removed [759472.533] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-15/i2c-ELAN0412:01/0018:04F3:316F.0001/input/input21/event15" [759472.533] (II) XINPUT: Adding extended input device "ELAN0412:01 04F3:316F Touchpad" (type: TOUCHPAD, id 13) [759472.533] (**) Option "AccelerationScheme" "none" [759472.533] (**) ELAN0412:01 04F3:316F Touchpad: (accel) selected scheme none/0 [759472.533] (**) ELAN0412:01 04F3:316F Touchpad: (accel) acceleration factor: 2.000 [759472.533] (**) ELAN0412:01 04F3:316F Touchpad: (accel) acceleration threshold: 4 [759472.534] (II) event15 - ELAN0412:01 04F3:316F Touchpad: is tagged by udev as: Touchpad [759472.535] (II) event15 - ELAN0412:01 04F3:316F Touchpad: device is a touchpad [759472.535] (II) config/udev: removing device ETPS/2 Elantech Touchpad [759472.535] (**) Option "fd" "75" [759472.535] (II) event22 - ETPS/2 Elantech Touchpad: device removed [759472.535] (II) UnloadModule: "libinput" [759472.535] (II) systemd-logind: releasing fd for 13:86 [759472.580] (II) config/udev: Adding input device ETPS/2 Elantech Touchpad (/dev/input/event22) [759472.580] (**) ETPS/2 Elantech Touchpad: Applying InputClass "libinput touchpad catchall" [759472.580] (II) Using input driver 'libinput' for 'ETPS/2 Elantech Touchpad' [759472.581] (II) systemd-logind: got fd for /dev/input/event22 13:86 fd 75 paused 0 [759472.581] (**) ETPS/2 Elantech Touchpad: always reports core events [759472.581] (**) Option "Device" "/dev/input/event22" [759472.581] (II) event22 - ETPS/2 Elantech Touchpad: is tagged by udev as: Touchpad [759472.582] (II) event22 - ETPS/2 Elantech Touchpad: device is a touchpad [759472.582] (II) event22 - ETPS/2 Elantech Touchpad: device removed [759472.582] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input10/event22" [759472.582] (II) XINPUT: Adding extended input device "ETPS/2 Elantech Touchpad" (type: TOUCHPAD, id 16) [759472.583] (**) Option "AccelerationScheme" "none" [759472.583] (**) ETPS/2 Elantech Touchpad: (accel) selected scheme none/0 [759472.583] (**) ETPS/2 Elantech Touchpad: (accel) acceleration factor: 2.000 [759472.583] (**) ETPS/2 Elantech Touchpad: (accel) acceleration threshold: 4 [759472.583] (II) event22 - ETPS/2 Elantech Touchpad: is tagged by udev as: Touchpad [759472.584] (II) event22 - ETPS/2 Elantech Touchpad: device is a touchpad [759472.584] (EE) event15 - ELAN0412:01 04F3:316F Touchpad: client bug: event processing lagging behind by 46ms, your system is too slow [759472.585] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=9 (/dev/input/event21) [759472.585] (II) No input driver specified, ignoring this device. [759472.585] (II) This device may have been added with another device file. [759472.585] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event10) [759472.585] (II) No input driver specified, ignoring this device. [759472.585] (II) This device may have been added with another device file. [759472.585] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event16) [759472.585] (II) No input driver specified, ignoring this device. [759472.585] (II) This device may have been added with another device file. [759472.585] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event13) [759472.585] (II) No input driver specified, ignoring this device. [759472.585] (II) This device may have been added with another device file. -- I can eat glass, it does not hurt me. Dan Sommers, http://www.tombstonezero.net/dan

2 2

firefox no longer starts - could it be wayland package?
by Genes Lists 07 Apr '23

07 Apr '23

Running on gnome This may have to do with updated updated wayland package (1.22.0-1) - didn't see much else that may be related. I tried rolling back firefox and makes no difference - I also tried with and without MOZ_ENABLE_WAYLAND - always get instant crash with: ExceptionHandler::GenerateDump cloned child 5628 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... Anyone else seeing similar and any suggestions for fix? thanks gene

6 11

moving /boot
by Fons Adriaensen 07 Apr '23

07 Apr '23

Hello all, I'm having a problem with updating a laptop: the /boot partition is too small for the new ramfs images. The system uses GPT partioning and BIOS boot using syslinux. /dev/sda1 1M Type = BIOS Boot /dev/sda2 /boot 95M Attributes: LegacyBIOSBootable /dev/sda3 / 93G (others for /home, /data and SWAP) One solution would be to move the /boot directory to / instead of giving it its own partition. The syslinux wiki page tells me that the absolute sector address of /boot/syslinux/ldlinux.sys plays a role in the boot sequence, so I suspect that just moving the boot directory and removing /dev/sda2 from /etc/fstab won't be enough. Would re-installing syslinux after that do the trick (and also take care of the LegacyBIOSBootable attribute) ? If not, what would be the correct and safe way to do this ? TIA, -- FA

3 3

Re: gui network icon not connected
by Rino Mardo 07 Apr '23

07 Apr '23

upon running nmcli, it shows disconnected but the wlan0 have an ip address. i remembered when i finished the installation i only have CLI. also no network connectivity. somehow i managed to have network connectivity by installing the package iwd. after that, i have connection via my wireless and i proceeded to install kde (including plasma-nm). since recalling i'm using iwd package, when i stop that service the GUI network icon still shows all 5 bars but no AP listed. when i restart iwd, i get a list of AP in my area and i also get network connectivity in terminal. so i guess the network icon is the problem then? On Sun, Mar 26, 2023 at 1:55 AM "accounts(a)lrose.de [via Relay]" <noreply(a)relay.firefox.com> wrote: > > Forwarded from wna8xt5uv(a)mozmail.com by Firefox Relay ⁨0⁩ email trackers removed Upgrade for more protection > > On 25. Mar 2023, at 15:18, Doug Newgard <dnewgard(a)outlook.com> wrote: > > What did you enable? What did you configure? YOU did all of this, right? You > should be able to tell us what you did, not the other way around. > > Only because a user installed their system, doesn't mean they completely understand it. It's a continuous learning process, and we should support everyone who's willing to learn. > > In this case, it seems like you're actually using NetworkManager, plasma-nm is a frontend for it. However, it is possible that you have a second network manager or static configuration configured, so network manager backs out. You can check that by typing nmcli in the terminal, it should show you the status of network manager on your system. If it shows connected, then the display applet in your Toolbar is the issue. If it shows disconnected, then you should check what other network manager you have installed, and uninstall it. > > https://wiki.archlinux.org/title/Network_configuration Shows a list of possible options. You should check if any of those besides NetworkManager are installed. > Your dashboard -- "This message was typed on my mobile phone. Please excuse any brevity or hilarious auto correct mistakes." http://about.me/RinoMardo

4 4

Can not build arch v6.2.* linux. Does that much swap space required?
by u34＠net9.ga 06 Apr '23

06 Apr '23

Hello, I haven't tried all the 6.2.*. Only some of the earliest, and some of the latest. v6.2.9, at this time. I could build the earliest v6.1.*. And also v6.1.12. Which is arch latest v6.1.*, doesn't it? I got what looks to me a similar issue with v6.1.7, if I remember correctly. As of v6.2.7 and v6.2.9, I get: $ cat -n linux-6.2.9.arch1-1-x86_64-build.log | tail 19288 AR arch/x86/video/built-in.a 19289 AR built-in.a 19290 AR vmlinux.a 19291 LD vmlinux.o 19292 vmlinux.o: warning: objtool: hyperv_init+0x42f: unreachable instruction 19293 make[1]: *** Deleting file 'vmlinux.o' 19294 make[1]: *** [scripts/Makefile.vmlinux_o:61: vmlinux.o] Interrupt 19295 make: *** [Makefile:1245: vmlinux_o] Interrupt 19296 19297 ==> ERROR: Aborted by user! Exiting... After it stalled for a long time at line #19291, or at line #19292, I interrupted it, ^c, manually. I forgot to look at the resource usage before interrupting v6.2.9 build. For some of the prevoius versions it happend, I saw the LD proccess consumed almost all of the machine free memory. And also a lot of swap. Which happend right at the LD operation, not before. It is only a desktop, Only 4G RAM. I am also confused about the unreachable warning. I think I saw it earlier only once. Possibly at some later v6.2.* version. But I can't find it at any log file. Perhaps I have deleted the file. I am using a local version for PKGBUILD. Does the follwoign diff maters? 63c63 < make all # htmldocs --- > make htmldocs all 195,196c195 < # pkgname=("$pkgbase" "$pkgbase-headers" "$pkgbase-docs") < pkgname=("$pkgbase" "$pkgbase-headers") --- > pkgname=("$pkgbase" "$pkgbase-headers" "$pkgbase-docs") There is also ccache enabled for makepkg. -- u34

4 9