October 2024 - Arch-general - lists.archlinux.org

Re: Future of salt in our repositories
by Genes Lists 05 Oct '24

05 Oct '24

On Sat, 2024-10-05 at 17:36 +0200, Morten Linderud wrote: > Yo, > > `salt` is a framework for server provisioning, change management and > ... > `salt` as of version `3007` does not support Python 3.12, and the > release `3008` > seems far away, ... > salt is going for the vendor > approach they call `onedir` and instead bundle *everyting*, including > their own > Python runtime, into a directory. This is going to be a mess to > properly support > ... ... > As long as there are not any major issues I intend to drop this > package ahead of > our Python 3.13 release and prep work. Replying via general. This does indeed make a lot of sense. 'onedir' sounds pretty horrible. It might worthwhile noting that salt was acquired by VMware which in turn was acquired by broadcom a couple years ago. I have no views if this is significant for its future trajectory or not. I wonder if some people might be considering migrating to Ansible or another alternative? thanks for staying on top of things and keeping us informed. gene -- Gene

1 0

Delayed responsiveness on resume after upgrade
by SET 05 Oct '24

05 Oct '24

Hello, I just upgraded a host and noticed a waiting of about 90s before the desktop (KDE) becomes responsive (typing to unlock the screen, the mouse cursor can be moved). This was not the case before the upgrade. This box has 3 remote shares attached via sshfs. The delay to responsiveness is near immediate if it is suspended while the remote shares are not connected. With remote shares connected on suspend: [Sat Oct 5 12:05:03 2024] OOM killer enabled. [Sat Oct 5 12:05:03 2024] Restarting tasks ... done. [Sat Oct 5 12:05:03 2024] random: crng reseeded on system resumption [Sat Oct 5 12:05:03 2024] PM: suspend exit [Sat Oct 5 12:05:03 2024] r8169 0000:06:00.0 eth0: Link is Up - 1Gbps/ Full - flow control off [Sat Oct 5 12:06:35 2024] r8169 0000:06:00.0 eth0: Link is Down [Sat Oct 5 12:06:35 2024] Generic FE-GE Realtek PHY r8169-0-600:00: attached PHY driver (mii_bus:phy_addr=r8169-0-600:00, irq=MAC) [Sat Oct 5 12:06:35 2024] r8169 0000:06:00.0 eth0: Link is Down [Sat Oct 5 12:06:39 2024] r8169 0000:06:00.0 eth0: Link is Up - 1Gbps/ Full - flow control off With remote shares disconnected on suspend: [Sat Oct 5 12:10:55 2024] OOM killer enabled. [Sat Oct 5 12:10:55 2024] Restarting tasks ... done. [Sat Oct 5 12:10:55 2024] random: crng reseeded on system resumption [Sat Oct 5 12:10:55 2024] PM: suspend exit [Sat Oct 5 12:10:55 2024] Generic FE-GE Realtek PHY r8169-0-600:00: attached PHY driver (mii_bus:phy_addr=r8169-0-600:00, irq=MAC) [Sat Oct 5 12:10:56 2024] r8169 0000:06:00.0 eth0: Link is Down [Sat Oct 5 12:10:58 2024] r8169 0000:06:00.0 eth0: Link is Up - 1Gbps/ Full - flow control off It seems that the network link remains 'up' when the remote shares are connected, then has to go down and that's where the delay lies. Afterwards, it quickly returns to the up state. 'modinfo r8169' does not expose any option at all. I wish to know if there's a simple known solution to quickly resume the host. The root cause could also lie deep in the kernel and may perhaps disappear on a future upgrade. I can live with it, it's just annoying. Thanks for any input.

1 0

Sound system not working on Macbook Pro (2017)
by Sadeep Madurange 05 Oct '24

05 Oct '24

Hello, I installed Arch Linux 6.11.1-arch1-1 on a 2017 Macbook Pro with KDE Plasma desktop package (initially installed the plasma-meta and kde-applications-meta, but I've since gotten rid of them). Sound output is not working with the speakers or headphones. KDE shows "No output or input devices found". During my troubleshoot, I ended up removingn pipewire stuff. Now I have pulseaudio, pulseaudio-alsa, and alsa-utils installed. I created a file /etc/modprobe.d/50-sound.conf and added "options snd_hda_intel model=intel-mac-auto" to it (and restarted), but that did not help. I have installed alsa firmware and sof-firmware. The output of lspci: 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Iris Plus Graphics 640 (rev 06) 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21) 00:15.2 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #2 (rev 21) 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1) 00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1) 00:1d.1 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #10 (rev f1) 00:1e.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO UART Controller #0 (rev 21) 00:1e.3 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO SPI Controller #1 (rev 21) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point LPC/eSPI Controller (rev 21) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) 01:00.0 Mass storage controller: Apple Inc. S3X NVMe Controller (rev 12) 02:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4350 802.11ac Wireless Network Adapter (rev 05) 03:00.0 Multimedia controller: Broadcom Inc. and subsidiaries 720p FaceTime HD Camera 04:00.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] (rev 02) 05:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 05:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 05:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 05:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 06:00.0 System peripheral: Intel Corporation JHL6540 Thunderbolt 3 NHI (C step) [Alpine Ridge 4C 2016] (rev 02) 07:00.0 USB controller: Intel Corporation JHL6540 Thunderbolt 3 USB Controller (C step) [Alpine Ridge 4C 2016] (rev 02) In alsamixer, Card shows as PulseAudio and the master volume is 100%. If I press F6 (to select sound card), the first entry is "- (default)". The second is "default:0 HDA Intel PCH". If I choose the second one, I see S/PDIF, S/PDIF 1, and S/PDIF 2. All of them are unmuted but the volume is 00. I can't increase it. The 00 is in a green square (not a rectangle up to 100%). I can hear the chime when the Macbook starts up, so the hardware is working fine.

2 1

Estimate for Linux 6.11 to move from testing to core?
by David C. Rankin 02 Oct '24

02 Oct '24

All, Devs, I've been watching https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/issues to try and get a handle on when to expect the 6.11 kernel. I can't read the tea-leaves very well. Does anyone involved in the process have an estimate of when we should look for the new kernel to be released? I ask because I have one production box to update and want to set aside time in case I have to troubleshoot. Though thankfully, the 6.10 -> 6.11 update looks benign from a server standpoint. Are we just waiting on the i915 shadow frame-buffer issue or one of the other audio issues? -- David C. Rankin, J.D.,P.E.

4 4

Wayland performance issues after upgrading linux and nvidia
by Edward Toroshchyn 02 Oct '24

02 Oct '24

All, Just wanted to drop a short FYI here, in case you've also encountered issues running Wayland after updating linux (6.10.10.arch1-1 -> 6.11.1.arch1-1) and nvidia (560.35.03-6 -> 560.35.03-9). For me, downgrading helped: # cd /var/cache/pacman/pkg/; pacman -U nvidia-560.35.03-3-x86_64.pkg.tar.zst linux-6.10.8.arch1-1-x86_64.pkg.tar.zst I've reported the issue here: https://gitlab.archlinux.org/archlinux/packaging/packages/nvidia/-/issues/9 Worm regards, -- Edward

1 0