This commit adds the feature I'm looking for, but it's not been accepted for 3 whole years. Why?

I currently have a 240Gb NVME drive on my computer, which is currently partitioned as follows: / - 50Gb and /home - 190Gb. SWAP is in the 8Gb file on the / partition. The file system is ext4, unencrypted. The /home/user directory is managed by systemd-homed, which is encrypted and in turn formatted with the btrfs file system.

The plan is to add a 120Gb SSD. So the computer would have a total of 240Gb NVME and 120Gb SSD. In addition, the plan is to start using / partition snapshots (for Archlinux upgrades) and disk encryption. systemd-homed would continue to be used, the new size of the / partition could be 60Gb and the remaining 320Gb is used for /home.

Which file systems to use ? Would it make sense to use btrfs for the / partition ? Can the /home partition be used virtually over NVME and SSD at the same time ? Should I encrypt both physical disks separately or just the / partition, assuming systemd-homed uses encryption anyway ? Which methods could I use and in which order ? Thank you in advance !

So I was using yay today and out of the sudden this message appeared: We'll be murdered in our beds! Which I didn't take it serious, and now I started thinking about it

Hi, I recently noticed that my USB drives weren't registering at all when plugged into either of my laptops USB A ports (USB C works, I tested with a different pen drive). I did some research and having recently been testing out tlp to try and improve my battery life I discovered that that is a common cause. I uninstalled TLP and reverted back to my default GRUB, rebooted and have still had no success.

I've tried to follow other peoples fixes but running dmesg -w or journalctl -f and inserting the drive shows no activity at all. If anyone has any ideas what this could be I'd be massively grateful!

I've done everything so far that is on the installation, except for the timezone, location and Initramfs.

After I used the command "arch-chroot /mnt" my terminal red thing now is gray and since I couldn't use grub last time (this is my 3rd attempt installing this) I decided to go with systemd-boot, but I don't know how to do it. The steps ahead are confusing for me and I don't know how to check that I have done everything correctly.

All the steps I've followed so far are from the installation guide only so I did not used any command that is not there, expect to wipe out the storage.

I want to cross-compile some binaries for aarch64 target on my amd64 ArchLinux machine. How can I do so? Where can I find the necessary packages? What I'm looking for is the GCC toolchain for ARM. I found the arm-none-eabi-gccarm-none-eabi-gcc package which works for bare metal applications, but I want to compile applications with the standard C library. I plan to execute the binaries using qemu. How can I do this? Can someone please help me out?

When I try to compile this program:

#include <stdio.h>

int main()
{
        printf("Hello Worldn");
        return 0;
}

using arm-none-eabi-gcc hello.c, I get the following errors due to missing glibc:

hello.c:1:10: fatal error: stdio.h: No such file or directory
    1 | #include <stdio.h>
      |          ^~~~~~~~~
compilation terminated.

How can I fix this?

On my t14 the mute switch works fine but the light never turns off unless i manually set the value 0. Is there a missing firmware or driver that i dont have which is causing this? Any help will be appreciated.

Hi to all!

After updating the kernel to 6.12.7-arch1-1 I get the following trace event raised by the kernel. What should I do? Apparently the system works correctly ...

------------[ cut here ]------------

dic 28 21:19:48 D9330 kernel: WARNING: CPU: 3 PID: 193 at kernel/trace/trace_events.c:577 trace_event_raw_init+0x159/0x660

dic 28 21:19:48 D9330 kernel: Modules linked in: xe(+) drm_ttm_helper gpu_sched drm_suballoc_helper drm_gpuvm drm_exec spi_ljca usb_ljca uas usb_storage i915 i2c_algo_bit serio_raw drm_bud>

dic 28 21:19:48 D9330 kernel: CPU: 3 UID: 0 PID: 193 Comm: (udev-worker) Not tainted 6.12.7-arch1-1 #1 9e77c5d99557be92f482a3ac6317d887bb3ffaf9

dic 28 21:19:48 D9330 kernel: Hardware name: Dell Inc. Latitude 9330/0RN079, BIOS 1.25.0 11/12/2024

dic 28 21:19:48 D9330 kernel: RIP: 0010:trace_event_raw_init+0x159/0x660

dic 28 21:19:48 D9330 kernel: Code: 89 ea 0f 83 3b 04 00 00 e8 44 db ff ff 84 c0 74 10 8b 0c 24 48 c7 c0 fe ff ff ff 48 d3 c0 49 21 c6 4d 85 f6 0f 84 d6 fe ff ff <0f> 0b bb 01 00 00 00 41 >

dic 28 21:19:48 D9330 kernel: RSP: 0018:ffffa1ed80897990 EFLAGS: 00010206

dic 28 21:19:48 D9330 kernel: RAX: ffffffffffffffdf RBX: ffffffffc0db1731 RCX: 0000000000000005

dic 28 21:19:48 D9330 kernel: RDX: 0000000000000002 RSI: 0000000000000001 RDI: ffffffffc0db1727

dic 28 21:19:48 D9330 kernel: RBP: ffffffffc0db1640 R08: 0000000000000039 R09: 0000000000000000

dic 28 21:19:48 D9330 kernel: R10: 0000000000000076 R11: 000000000000004e R12: 00000000000000f2

dic 28 21:19:48 D9330 kernel: R13: ffffffffc0db2760 R14: 0000000000000018 R15: 0000000000000000

dic 28 21:19:48 D9330 kernel: FS: 000074348b53b880(0000) GS:ffff90a8bf580000(0000) knlGS:0000000000000000

dic 28 21:19:48 D9330 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

dic 28 21:19:48 D9330 kernel: CR2: 000074348bfb2de0 CR3: 00000001019b6000 CR4: 0000000000f50ef0

dic 28 21:19:48 D9330 kernel: PKRU: 55555554

dic 28 21:19:48 D9330 kernel: Call Trace:

dic 28 21:19:48 D9330 kernel: <TASK>

dic 28 21:19:48 D9330 kernel: ? trace_event_raw_init+0x159/0x660

dic 28 21:19:48 D9330 kernel: ? __warn.cold+0x93/0xf6

dic 28 21:19:48 D9330 kernel: ? trace_event_raw_init+0x159/0x660

dic 28 21:19:48 D9330 kernel: ? report_bug+0xff/0x140

dic 28 21:19:48 D9330 kernel: ? handle_bug+0x58/0x90

dic 28 21:19:48 D9330 kernel: ? exc_invalid_op+0x17/0x70

dic 28 21:19:48 D9330 kernel: ? asm_exc_invalid_op+0x1a/0x20

dic 28 21:19:48 D9330 kernel: ? trace_event_raw_init+0x159/0x660

dic 28 21:19:48 D9330 kernel: event_init+0x28/0x70

dic 28 21:19:48 D9330 kernel: trace_module_notify+0x1a4/0x260

dic 28 21:19:48 D9330 kernel: notifier_call_chain+0x5a/0xd0

dic 28 21:19:48 D9330 kernel: blocking_notifier_call_chain_robust+0x65/0xc0

dic 28 21:19:48 D9330 kernel: load_module+0x1822/0x1cf0

dic 28 21:19:48 D9330 kernel: ? vmap+0x83/0xe0

dic 28 21:19:48 D9330 kernel: ? __vunmap_range_noflush+0x325/0x470

dic 28 21:19:48 D9330 kernel: ? init_module_from_file+0x89/0xe0

dic 28 21:19:48 D9330 kernel: init_module_from_file+0x89/0xe0

dic 28 21:19:48 D9330 kernel: idempotent_init_module+0x11e/0x310

dic 28 21:19:48 D9330 kernel: __x64_sys_finit_module+0x5e/0xb0

dic 28 21:19:48 D9330 kernel: do_syscall_64+0x82/0x190

dic 28 21:19:48 D9330 kernel: ? syscall_exit_to_user_mode+0x37/0x1c0

dic 28 21:19:48 D9330 kernel: ? do_syscall_64+0x8e/0x190

dic 28 21:19:48 D9330 kernel: ? do_sys_openat2+0x9c/0xe0

dic 28 21:19:48 D9330 kernel: ? syscall_exit_to_user_mode+0x37/0x1c0

dic 28 21:19:48 D9330 kernel: ? do_syscall_64+0x8e/0x190

dic 28 21:19:48 D9330 kernel: ? do_syscall_64+0x8e/0x190

dic 28 21:19:48 D9330 kernel: ? do_syscall_64+0x8e/0x190

dic 28 21:19:48 D9330 kernel: entry_SYSCALL_64_after_hwframe+0x76/0x7e

dic 28 21:19:48 D9330 kernel: RIP: 0033:0x74348bd321fd

dic 28 21:19:48 D9330 kernel: Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 >

dic 28 21:19:48 D9330 kernel: RSP: 002b:00007fffdcc10108 EFLAGS: 00000246 ORIG_RAX: 0000000000000139

dic 28 21:19:48 D9330 kernel: RAX: ffffffffffffffda RBX: 000059053b8b9980 RCX: 000074348bd321fd

dic 28 21:19:48 D9330 kernel: RDX: 0000000000000004 RSI: 000074348b53505d RDI: 0000000000000024

dic 28 21:19:48 D9330 kernel: RBP: 00007fffdcc101c0 R08: 0000000000000001 R09: 00007fffdcc10150

dic 28 21:19:48 D9330 kernel: R10: 0000000000000040 R11: 0000000000000246 R12: 000074348b53505d

dic 28 21:19:48 D9330 kernel: R13: 0000000000020000 R14: 000059053b8ba300 R15: 000059053b8bafa0

dic 28 21:19:48 D9330 kernel: </TASK>

dic 28 21:19:48 D9330 kernel: ---[ end trace 0000000000000000 ]---

dic 28 21:19:48 D9330 kernel: event xe_bo_move has unsafe dereference of argument 4

dic 28 21:19:48 D9330 kernel: print_fmt: "move_lacks_source:%s, migrate object %p [size %zu] from %s to %s device_id:%s", REC->move_lacks_source ? "yes" : "no", REC->bo, REC->size, xe_mem_>

Hey all, I frequently update my computers and this morning my desktop took a bit longer to start than usual with a warning that waydroid failed to start. I no longer use waydroid so I figured I'd uninstall it. I just ran a simple pacman -R waydroid and it was gone but I noticed my working was off so I figured I'd reboot since it probably messed with ip tables, etc.

After rebooting my nfs mounts all timed out and I noticed I can reach the outside network but not my lan network other than gateway. After a bit of poking around I decided to reinstall waydroid and it seemed to fix my lan access issue. I rebooted to confirm and sadly I can't reach local network again. I'm not entirely sure where to start but I'll include a few things that might be helpful: (yes i temporarily have a /21 b/c i started moving things around and got lazy, gw is .18.1)

$ ip route show default via 192.168.18.1 dev br0 proto dhcp src 192.168.18.39 metric 1024 default via 192.168.18.1 dev enp3s0 proto dhcp src 192.168.18.39 metric 20100 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 172.18.0.0/16 dev br-8df2687bb087 proto kernel scope link src 172.18.0.1 linkdown 173.255.215.209 via 192.168.18.1 dev br0 proto dhcp src 192.168.18.39 metric 1024 192.168.16.0/21 dev enp3s0 proto kernel scope link src 192.168.18.39 metric 100 192.168.16.0/21 dev br0 proto kernel scope link src 192.168.18.39 metric 1024 192.168.18.1 dev br0 proto dhcp scope link src 192.168.18.39 metric 1024 205.161.200.3 via 192.168.18.1 dev br0 proto dhcp src 192.168.18.39 metric 1024

``` $ ip add 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host noprefixroute valid_lft forever preferred_lft forever 2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br0 state UP group default qlen 1000 link/ether 18:c0:... brd ff:ff:ff:ff:ff:ff altname enx18c0... inet 192.168.18.39/21 brd 192.168.23.255 scope global dynamic noprefixroute enp3s0 valid_lft 862780sec preferred_lft 862780sec inet6 fe80::.../64 scope link noprefixroute valid_lft forever preferred_lft forever 3: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 18:... brd ff:ff:ff:ff:ff:ff inet 192.168.18.39/21 metric 1024 brd 192.168.23.255 scope global dynamic br0 valid_lft 862780sec preferred_lft 862780sec inet6 fe80::.../64 scope link proto kernel_ll valid_lft forever preferred_lft forever 4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:58:... brd ff:ff:ff:ff:ff:ff inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0 valid_lft forever preferred_lft forever 5: br-8df2687bb087: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:43:... brd ff:ff:ff:ff:ff:ff inet 172.18.0.1/16 brd 172.18.255.255 scope global br-8df2687bb087 valid_lft forever preferred_lft forever

```

pmlogger.service is failing to collect data

The only thing that works for a little while is clearing the logs folder then restarting it.
Nothing really explains to what is causing it, it just fails.

It will show the stats in cockpit for a moment when I get it cleared then when I come back it is failing again.
This used to work with no issue.,

I have installed bleuz, blues-utils and blueman, turn start/enable service, check rfkill. Check twice info from archwiki!

dmesg: Bluetooth:hci0 Opcode 0x0e03 failed: -110

Asus TUF motherboard. Windows bluetooth worked fine before

hey :)
did someone of you get the gb-operator running? Or has deal with it?

It will even happen when you are playing very small games like Madness Nexus Project 2
tested on CS2 too
it happens when the game show up for a few moment[like 30 seconds]
and when it happens,all the graphic get freeze,after a while,screen get glitched,then pop me back to the login menu and reset the gpu

dmesg:https://0x0.st/8sKU.txt
neofetch

(base)   dynamo   ~ git-[ main]-  neofetch
                   -`                    dynamo@archyyds
                  .o+`                   ---------------
                 `ooo/                   OS: Arch Linux x86_64
                `+oooo:                  Kernel: 6.11.3-273-tkg-bore
               `+oooooo:                 Uptime: 14 mins
               -+oooooo+:                Packages: 2857 (pacman), 9 (flatpak)
             `/:-:++oooo+:               Shell: zsh 5.9
            `/++++/+++++++:              Resolution: 1920x1080
           `/++++++++++++++:             DE: Hyprland
          `/+++ooooooooooooo/`           Theme: Adwaita [GTK3]
         ./ooosssso++osssssso+`          Icons: breeze [GTK2/3]
        .oossssso-````/ossssss+`         Terminal: alacritty
       -osssssso.      :ssssssso.        CPU: Intel i5-6600K (4) @ 3.900GHz
      :osssssss/        osssso+++.       GPU: AMD ATI Radeon RX Vega 56/64
     /ossssssss/        +ssssooo/-       Memory: 4637MiB / 15930MiB
   `/ossssso+/:-        -:/+osssso+-
  `+sso+:-`                 `.-/+oso:
 `++:.                           `-/+/
 .`                                 `/

Using Vega56[not overclocked]

rocm-smi:

======================================== ROCm System Management Interface ========================================
================================================== Concise Info ==================================================
Device  Node  IDs              Temp    Power     Partitions          SCLK  MCLK  Fan  Perf  PwrCap  VRAM%  GPU%
              (DID,     GUID)  (Edge)  (Socket)  (Mem, Compute, ID)
==================================================================================================================
0       1     0x687f,   51005  42.0°C  4.0W      N/A, N/A, 0         None  None  0%   auto  260.0W  7%     0%
==================================================================================================================
============================================== End of ROCm SMI Log ===============================================

I notice a strange thing that in lact,the overclock is strangely on[didn't turn it on manually]
when i try to disable overclocking support in lact
it says

2024-12-27T13:28:21.097121Z  WARN lact_gui::app: Got error from daemon, end of client boundary

Caused by:
Overclocking was not enabled through LACT (file at /etc/modprobe.d/99-amdgpu-overdrive.conf does not exist)

lspci -nnk

(base)   dynamo   ~ git-[ main]-  lspci -nnk
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [8086:191f] (rev 07)
Subsystem: ASRock Incorporation Device [1849:191f]
Kernel driver in use: skl_uncore
Kernel modules: ie31200_edac
00:01.0 PCI bridge [0604]: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) [8086:1901] (rev 07)
Subsystem: ASRock Incorporation Device [1849:1901]
Kernel driver in use: pcieport
00:14.0 USB controller [0c03]: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller [8086:a12f] (rev 31)
Subsystem: ASRock Incorporation Device [1849:a12f]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
00:14.2 Signal processing controller [1180]: Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem [8086:a131] (rev 31)
Subsystem: ASRock Incorporation Device [1849:a131]
Kernel driver in use: intel_pch_thermal
Kernel modules: intel_pch_thermal
00:16.0 Communication controller [0780]: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 [8086:a13a] (rev 31)
Subsystem: ASRock Incorporation Device [1849:a13a]
Kernel driver in use: mei_me
Kernel modules: mei_me
00:17.0 SATA controller [0106]: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] [8086:a102] (rev 31)
Subsystem: ASRock Incorporation Device [1849:a102]
Kernel driver in use: ahci
00:1c.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #5 [8086:a114] (rev f1)
Subsystem: ASRock Incorporation Device [1849:a114]
Kernel driver in use: pcieport
00:1d.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #9 [8086:a118] (rev f1)
Subsystem: ASRock Incorporation Device [1849:a118]
Kernel driver in use: pcieport
00:1d.3 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #12 [8086:a11b] (rev f1)
Subsystem: ASRock Incorporation Device [1849:a11b]
Kernel driver in use: pcieport
00:1f.0 ISA bridge [0601]: Intel Corporation B150 Chipset LPC/eSPI Controller [8086:a148] (rev 31)
Subsystem: ASRock Incorporation Device [1849:a148]
00:1f.2 Memory controller [0580]: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller [8086:a121] (rev 31)
Subsystem: ASRock Incorporation Device [1849:a121]
00:1f.3 Audio device [0403]: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller [8086:a170] (rev 31)
Subsystem: ASRock Incorporation Device [1849:1151]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_avs
00:1f.4 SMBus [0c05]: Intel Corporation 100 Series/C230 Series Chipset Family SMBus [8086:a123] (rev 31)
Subsystem: ASRock Incorporation Device [1849:a123]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801
01:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Vega 10 PCIe Bridge [1022:1470] (rev c3)
Kernel driver in use: pcieport
02:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Vega 10 PCIe Bridge [1022:1471]
Subsystem: Advanced Micro Devices, Inc. [AMD] Vega 10 PCIe Bridge [1022:1471]
Kernel driver in use: pcieport
03:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XL/XT [Radeon RX Vega 56/64] [1002:687f] (rev c3)
Subsystem: ASUSTeK Computer Inc. Device [1043:0555]
Kernel driver in use: amdgpu
Kernel modules: amdgpu
03:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 HDMI Audio [Radeon Vega 56/64] [1002:aaf8]
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 HDMI Audio [Radeon Vega 56/64] [1002:aaf8]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
05:00.0 Ethernet controller [0200]: Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller [1969:e0a1] (rev 10)
Subsystem: ASRock Incorporation Device [1849:e0a1]
Kernel driver in use: alx
Kernel modules: alx
06:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev bb)
Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [Wilkins Peak 2] [8086:c470]
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
(base)   dynamo   ~ git-[ main]- 

grub kernel parameters:

GRUB_CMDLINE_LINUX_DEFAULT="loglevel=5 amdgpu.aspm=0 amdgpu.runpm=0 amdgpu.bapm=0 amdgpu.noretry=0 amdgpu.ppfeaturemask=0xffffcff8 intel_iommu=on iommu=pt video=efifb:off pcie_acs_override=downstream,multifunction vfio-pci.ids=1002:687f,1002:aaf8"

[i disabled vfio in mkinitcpio.conf and don't have any other configs]

part of these parameters come from this post:https://bbs.archlinux.org/viewtopic.php?id=299883

Switching into linux stable kernel doesn't works

switched to mesa 24.2.7,doesn't work
all the mesa packages:

(base)   dynamo   ~ git-[ main]-  sudo pacman -Qs mesa
local/glu 9.0.3-2
    Mesa OpenGL utility library
local/lib32-glu 9.0.3-2
    Mesa OpenGL utility library (32 bits)
local/lib32-mesa 1:24.2.7-1
    Open-source OpenGL drivers - 32-bit
local/lib32-vulkan-mesa-layers 1:24.2.7-1
    Mesa's Vulkan layers - 32-bit
local/mesa 1:24.2.7-1
    Open-source OpenGL drivers
local/mesa-demos 9.0.0-5
    Mesa demos
local/mesa-utils 9.0.0-5
    Essential Mesa utilities
local/vulkan-mesa-layers 1:24.2.7-1
    Mesa's Vulkan layersswitched to mesa 24.2.7,doesn't work
all the mesa packages:(base)   dynamo   ~ git-[ main]-  sudo pacman -Qs mesa
local/glu 9.0.3-2
    Mesa OpenGL utility library
local/lib32-glu 9.0.3-2
    Mesa OpenGL utility library (32 bits)
local/lib32-mesa 1:24.2.7-1
    Open-source OpenGL drivers - 32-bit
local/lib32-vulkan-mesa-layers 1:24.2.7-1
    Mesa's Vulkan layers - 32-bit
local/mesa 1:24.2.7-1
    Open-source OpenGL drivers
local/mesa-demos 9.0.0-5
    Mesa demos
local/mesa-utils 9.0.0-5
    Essential Mesa utilities
local/vulkan-mesa-layers 1:24.2.7-1
    Mesa's Vulkan layers

tested on Windows
in Windows,playing Battlefield 1 is completely fine

playing Minecraft[JAVA]is okay[with a high-end shader]
i assume it only happens on proton?

Downgrading vulkan-radeon[include lib32]make the crash slower[at least i can get loaded and get into the game for a while]
but it still crashes

https://0x0.st/8smf.txt

switching to lts doesn't work

disabling iommu doesn't work either

tried to clear all grub launch parameter
still doesn't work

i can use ollama 8b llm good

When I try to boot KDE Plasma, It gets to the bit where the loading bar and KDE logo is on screen before kicking me out and sending me back to the display manager. This started today.

A much older problem is that when I try to boot into deepin DE, the screen goes black for 5-15 mins before going back to the display manager.

Gnome works perfectly fine, but I prefer KDE Plasma and would like to use it again.

Hello,

I'm hoping the community can help me. I am using Arch Linux with KDE Plasma. My laptop is an XPS 9640 which uses the intel ipu6 MIPI camera. I read here: https://aur.archlinux.org/packages/intel-ipu6-dkms-git that the 6.10 kernel should support it (I believe) but it's not working when I attempt to use it on webcamtests website. Does anyone have any idea how I should investigate this?

I'm new to Installing Arch Linux.
I done the steps of Installing Arch Linux (Btw Window to Arch Linux)

Problem: When I hit Enter on my Bootable USB it keeps looping on Boot Menu

Device
Laptop Model: T460 Laptop (ThinkPad) - Type 20FM
CPU Type: Intel (R) Core (TM) i7-6600U CPU
Installed Memory: 8192MB
USB Flash Drive: General UDisk USB Device (31.2 GB)

ISO: archlinux-2024.12.01-x86_64.iso (Link: https://asia.mirror.pkgbuild.com/iso/2024.12.01/)

ThinkPad Setup
Secure Boot: [Disabled]
Boot Priority Order: I move the USB HDD: General UDisk at 1.
UEFI/Legacy Boot: [UEFI Only]
CSM Support: [No]

Rufus
Partition Scheme: GPT
Target System: UEFI (non CSM)
File System: FAT32 (Default)
Cluster size: 16 kilobytes (Default)

Video Error Loop Link: https://www.youtube.com/watch?v=aHDG48rNL74 (Noise Warning)

I just installed Arch on my laptop, I installed it on disk absolutely for sure. But it works only from usb flash. Why can it happen? Everything is working correctly as I set it up, but only from flash. Is something wrong with loader, I don’t understand…

now I recently posted about archinstall module not found I have done a successful install via 3.0.1 I choose hyprland but when i type my password the screen goes black for a second then again the sddm screen comes.....pls pls help guys I have marked that other one solved

So I wanted to update my cheapino's keymap today which uses qmk, But when trying to compile the firmware, I get an error, as qmk uses python-milc and it is out of date in the arch repos(though it is aldready reported). What should one do in such a situation?

I'm using arch sometimes with hyprland sometimes with kde-plasma, idk if that matters or anything. So, i am using a firefox based browser (Zen) and whenever i join a vc, test if my mic works, doing anything that requires me to use my microphone just crashes the tab almost instantly (almost). One time i actually was able to say 1 word in the vc but it crashed right after anyways. I also tried using firefox but that didn't work. I haven't tried using a chromium based browser yet, i might try that but does anyone know why this happens? I'm pretty sure it isn't a browser problem since i used Pop OS for a really long time before switching to arch and i had no problem there. Maybe a pipewire problem?

Edit : It was a Zen browser related problem, i tried firefox again and it worked.

Upon inputting a wrong password sddm would repeatly reattempt that wrong password until it is locked out by pam(I discovered this via journals), each failed attempt will cause it to empty the input bar so I have to wait until it is locked by pam to input a new password, this is rather a strange behaviour, do you have any idea how to debug this/ what might be causing the issue?

I started installing archlinux and wanted to connect to the Internet, but on the arch wiki I only found a case with password-free Internet or wifi. So what command do I need to use to connect to the wired internet with a password (PPPoE)?

This is my first time posting. Do let me know if I got this right since I never usually post anywhere.

Context:
I am running Arch with i3wm, and jack2, qjackctl, PulseAudio, pavucontrol. I use the shell/script method outlined here: https://wiki.archlinux.org/title/PulseAudio/Examples#The_shell_script_method in order to allow PulseAudio and JACK to work together. All of this works perfectly, so my ambitions are slightly larger now.

What I want to do now:
I want to plug in my Focusrite Scarlett 8i6, then see qjackctl open in a new workspace (ideally workspace 9). Then, once I unplug/poweroff the 8i6, I want jackd to be stopped correctly (in accordance of the pre-stop and post-stop scripts) then qjackctl to close too.

What I tried so far:
I created this script (it is called focusrite-detect.sh):

#!/bin/bash

# God forbid debugging.
exec >> /home/music/audiohell/focusrite_log.txt 2>&1

# Maybe UDEV needs the paths explicitly...
export PATH=$PATH:/usr/bin:/usr/sbin:/bin:/sbin:/usr/local/bin
export HOME=/home/music
export USER=music

# Define the vendor ID and product ID for your Focusrite 8i6
FOCUSRITE_VENDOR_ID="1235"  # Replace with the actual vendor ID
FOCUSRITE_PRODUCT_ID="8213"  # Replace with the actual product ID

WORKSPACE="9"  # i3 workspace where qjackctl should open

# Function to check if the Focusrite device is connected using vendor and product IDs
is_focusrite_connected() {
    # Check if the device with the specified vendor and product ID is connected
    if /usr/bin/lsusb | /usr/bin/grep -q "$FOCUSRITE_VENDOR_ID:$FOCUSRITE_PRODUCT_ID"; then
        return 0  # Device found
    else
        return 1  # Device not found
    fi
}

# Function to check if qjackctl is running
is_qjackctl_running() {
    /usr/bin/pgrep -x "qjackctl" > /dev/null
    return $?
}

# Function to stop jackd gracefully via qjackctl
stop_jackd_gracefully() {
    if is_qjackctl_running; then
        # Use jack_control to stop jackd gracefully via qjackctl
        /usr/bin/jack_control stop
        # Optionally, you can quit qjackctl after stopping jackd
        /usr/bin/pkill qjackctl
    fi
}

# Function to launch qjackctl on workspace 9
launch_qjackctl() {
    if ! is_qjackctl_running; then
        # Launch qjackctl minimised on workspace 9
        /usr/bin/i3-msg workspace $WORKSPACE
        /usr/bin/i3-msg exec "/usr/bin/qjackctl &"
    fi
}

# Main script logic

if is_focusrite_connected; then
    # If the Focusrite is plugged in and qjackctl isn't running, launch it
    launch_qjackctl
else
    # If Focusrite is unplugged and qjackctl is running, stop jackd gracefully and quit qjackctl
    stop_jackd_gracefully
fi

I ensured it was executable (chmod +x focusrite-detect.sh) and after executing it manually, it works perfectly every time. The focusrite_log.txt also tells me its a success with no errors.

I wanted to try and execute that script using a udev rule. This is where I had no luck:

1. I created focusrite-usb.rules in /lib/udev/rules.d/99-focusrite-usb.rules. The cat command output:ACTION=="add|remove", SUBSYSTEM=="usb", ATTR{idVendor}=="1235", ATTR{idProduct}=="8213", RUN+="/home/music/audiohell/focusrite-detect.sh"
2. Upon reloading udev and switching on the 8i6, I got this (by typing "journalctl | grep udev"):

Dec 27 23:57:36 archlinux (udev-worker)[18228]: 3-3: Process '/home/music/audiohell/focusrite-detect.sh' failed with exit code 1.

When switching the device off, nothing happens (no logs, no prompt from anything).

3) In the udev rule I changed focusrite-detect.sh to an alternative executable script order to try a simpler command, just in case it worked. The alternative script successfully created the text file once the 8i6 was plugged in. I then manually removed the text file with the expectation that the file creation would happen again once the device was switched off. It didn't. Nothing happened at all, not a single log anywhere.

All feedback is appreciated since I'm lost for ideas for how to make this idea work. (And if anything needs changing or editing because I got it wrong, do let me know) Thank you very much.

Edit 1a: Response to u/CWRau, running "sudo udevadm monitor" to check events:

Plugging device in:

monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[196.750884] change   /devices/virtual/thermal/thermal_zone0 (thermal)
UDEV  [196.757657] change   /devices/virtual/thermal/thermal_zone0 (thermal)
KERNEL[314.490606] add      /devices/pci0000:00/0000:00:14.0/usb3/3-3 (usb)
KERNEL[314.493094] add      /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0 (usb)
KERNEL[314.493209] add      /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.1 (usb)
KERNEL[314.493353] add      /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.2 (usb)
KERNEL[314.493525] add      /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.3 (usb)
KERNEL[314.493624] add      /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.4 (usb)
KERNEL[314.493713] add      /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.5 (usb)
KERNEL[314.493771] bind     /devices/pci0000:00/0000:00:14.0/usb3/3-3 (usb)
UDEV  [317.545016] add      /devices/pci0000:00/0000:00:14.0/usb3/3-3 (usb)
UDEV  [317.550892] add      /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.1 (usb)
UDEV  [317.552694] add      /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.3 (usb)
UDEV  [317.553066] add      /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.2 (usb)
KERNEL[317.560210] add      /bus/snd_seq (bus)
KERNEL[317.560246] add      /module/snd_seq_device (module)
UDEV  [317.560711] add      /module/snd_seq_device (module)
UDEV  [317.560817] add      /bus/snd_seq (bus)
KERNEL[317.571510] add      /module/snd_rawmidi (module)
UDEV  [317.572950] add      /module/snd_rawmidi (module)
KERNEL[317.576537] add      /module/snd_ump (module)
UDEV  [317.576853] add      /module/snd_ump (module)
KERNEL[317.582068] add      /module/snd_usbmidi_lib (module)
UDEV  [317.582747] add      /module/snd_usbmidi_lib (module)
KERNEL[318.346373] bind     /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.1 (usb)
KERNEL[319.096387] bind     /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.2 (usb)
KERNEL[319.125573] bind     /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0 (usb)
KERNEL[319.125635] bind     /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.4 (usb)
KERNEL[319.125656] add      /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1 (sound)
KERNEL[319.125685] add      /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1/pcmC1D0p (sound)
KERNEL[319.125814] add      /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1/pcmC1D0c (sound)
KERNEL[319.126060] add      /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1/midiC1D0 (sound)
KERNEL[319.126120] add      /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1/midi1 (sound)
KERNEL[319.126211] add      /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1/dmmidi1 (sound)
KERNEL[319.126243] add      /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1/seq-midi-1-0 (snd_seq)
KERNEL[319.126433] add      /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1/hwC1D0 (sound)
KERNEL[319.126551] add      /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1/controlC1 (sound)
KERNEL[319.126618] bind     /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.5 (usb)
KERNEL[319.126650] add      /bus/usb/drivers/snd-usb-audio (drivers)
KERNEL[319.126697] add      /module/snd_usb_audio (module)
UDEV  [319.127113] add      /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.5 (usb)
UDEV  [319.127184] add      /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0 (usb)
UDEV  [319.127249] add      /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.4 (usb)
UDEV  [319.127322] add      /module/snd_usb_audio (module)
UDEV  [319.127388] add      /bus/usb/drivers/snd-usb-audio (drivers)
UDEV  [319.134111] bind     /devices/pci0000:00/0000:00:14.0/usb3/3-3 (usb)
UDEV  [319.136259] bind     /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.4 (usb)
UDEV  [319.136398] bind     /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0 (usb)
UDEV  [319.136512] bind     /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.1 (usb)
UDEV  [319.136816] bind     /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.5 (usb)
UDEV  [319.136898] bind     /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.2 (usb)
UDEV  [319.137684] add      /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1 (sound)
UDEV  [319.139515] add      /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1/pcmC1D0p (sound)
UDEV  [319.139713] add      /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1/pcmC1D0c (sound)
UDEV  [319.139770] add      /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1/seq-midi-1-0 (snd_seq)
UDEV  [319.140143] add      /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1/midiC1D0 (sound)
UDEV  [319.140228] add      /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1/dmmidi1 (sound)
UDEV  [319.140295] add      /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1/midi1 (sound)
UDEV  [319.141458] add      /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1/hwC1D0 (sound)
KERNEL[319.142689] change   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1 (sound)
UDEV  [319.159519] add      /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1/controlC1 (sound)
UDEV  [319.160941] change   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1 (sound)

Unplugging the device:

KERNEL[538.733587] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1/controlC1 (sound)
KERNEL[538.733666] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1/hwC1D0 (sound)
KERNEL[538.733695] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1/seq-midi-1-0 (snd_seq)
KERNEL[538.733724] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1/midi1 (sound)
KERNEL[538.733753] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1/dmmidi1 (sound)
KERNEL[538.733804] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1/midiC1D0 (sound)
KERNEL[538.733875] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1/pcmC1D0p (sound)
KERNEL[538.733942] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1/pcmC1D0c (sound)
KERNEL[538.734013] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1 (sound)
KERNEL[538.734050] unbind   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0 (usb)
KERNEL[538.734094] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0 (usb)
KERNEL[538.734144] unbind   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.1 (usb)
KERNEL[538.734185] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.1 (usb)
KERNEL[538.734221] unbind   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.2 (usb)
KERNEL[538.734262] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.2 (usb)
KERNEL[538.734299] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.3 (usb)
KERNEL[538.734328] unbind   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.4 (usb)
KERNEL[538.734366] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.4 (usb)
KERNEL[538.735209] unbind   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.5 (usb)
KERNEL[538.735258] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.5 (usb)
KERNEL[538.735793] unbind   /devices/pci0000:00/0000:00:14.0/usb3/3-3 (usb)
KERNEL[538.735854] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-3 (usb)
UDEV  [538.742456] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1/hwC1D0 (sound)
UDEV  [538.742805] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1/controlC1 (sound)
UDEV  [538.743432] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1/seq-midi-1-0 (snd_seq)
UDEV  [538.744143] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1/midi1 (sound)
UDEV  [538.745399] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1/pcmC1D0c (sound)
UDEV  [538.745557] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1/pcmC1D0p (sound)
UDEV  [538.745723] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1/midiC1D0 (sound)
UDEV  [538.745812] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1/dmmidi1 (sound)
UDEV  [538.747465] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.3 (usb)
UDEV  [538.747704] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/sound/card1 (sound)
UDEV  [538.840316] unbind   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.5 (usb)
UDEV  [538.840407] unbind   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.2 (usb)
UDEV  [538.840466] unbind   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.1 (usb)
UDEV  [538.840613] unbind   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0 (usb)
UDEV  [538.840726] unbind   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.4 (usb)
UDEV  [538.841057] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.1 (usb)
UDEV  [538.841114] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0 (usb)
UDEV  [538.841172] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.2 (usb)
UDEV  [538.841231] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.5 (usb)
UDEV  [538.841293] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.4 (usb)
UDEV  [538.843110] unbind   /devices/pci0000:00/0000:00:14.0/usb3/3-3 (usb)
UDEV  [538.844341] remove   /devices/pci0000:00/0000:00:14.0/usb3/3-3 (usb)

Edit 1b: Response to u/remenic, adding set -x to the top of the script.

Plugging device in response:

+ export PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin:/usr/sbin:/bin:/sbin:/usr/local/bin
+ PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin:/usr/sbin:/bin:/sbin:/usr/local/bin
+ export HOME=/home/music
+ HOME=/home/music
+ export USER=music
+ USER=music
+ FOCUSRITE_VENDOR_ID=1235
+ FOCUSRITE_PRODUCT_ID=8213
+ WORKSPACE=9
+ is_focusrite_connected
+ /usr/bin/grep -q 1235:8213
+ /usr/bin/lsusb
+ return 0
+ launch_qjackctl
+ is_qjackctl_running
+ /usr/bin/pgrep -x qjackctl
+ return 1
+ /usr/bin/i3-msg workspace 9
i3-msg: Could not determine i3 socket path: Success
+ /usr/bin/i3-msg exec '/usr/bin/qjackctl &'
i3-msg: Could not determine i3 socket path: Success

(I'll add a note just in case this is significant: running i3 --get-socketpath returns "/run/user/1000/i3/ipc-socket.833" and every time I shutdown or reboot, a stop job always runs for this process UID 1000).

Unplugging device response: (I removed the previous log to allow for the file to be created again)

The script doesn't execute at all, no new file was created.

I will look into a systemd service in the mean time, thank you.