[Solved] Wifi not working , MEDIATEK Corp. MT7921 802.11ax

beast41514 · 2024-01-11 08:55:45

Hi everyone i am a new to linux and I have dual booted with windows 10. I have an Asus Rog strix g15 laptop. My wifi is not working, i have been trying to fix it for the past month and have been unable to do so.

# I have checked the drivers using the lspci -k, this is the relevant part of the output:

03:00.0 Network controller: MEDIATEK Corp. MT7921 802.11ax PCI Express Wireless Network Adapter
	Subsystem: AzureWave MT7921 802.11ax PCI Express Wireless Network Adapter
	Kernel modules: mt7921e

# Also a wireless interface has not been created, this is my output of ip link:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
    link/ether 50:eb:f6:d0:94:fa brd ff:ff:ff:ff:ff:ff
3: enp5s0f4u2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 1000
    link/ether 82:24:04:89:49:10 brd ff:ff:ff:ff:ff:ff

# Then i checked the kernal logs for any related messages, this is the output of dmesg | grep mt7921e:

[    5.059228] mt7921e 0000:03:00.0: enabling device (0000 -> 0002)
[    5.083277] mt7921e 0000:03:00.0: ASIC revision: 79610010
[    5.164255] mt7921e: probe of 0000:03:00.0 failed with error -12

# I found out that -12 indicates some problem with initialization, so i tried to reinitialize the driver for my wireless card using these:
1.

sudo modprobe -r mt7921e

2.

sudo modprobe mt7921e

# After this when i tried to read the kernal logs, one more error was added:

[    5.059228] mt7921e 0000:03:00.0: enabling device (0000 -> 0002)
[    5.083277] mt7921e 0000:03:00.0: ASIC revision: 79610010
[    5.164255] mt7921e: probe of 0000:03:00.0 failed with error -12
[ 2635.069521] mt7921e 0000:03:00.0: Unable to change power state from D3cold to D0, device inaccessible
[ 2636.258438] mt7921e 0000:03:00.0: driver own failed
[ 2636.258490] mt7921e: probe of 0000:03:00.0 failed with error -5

# This is the content of my /usr/lib/firmware/mediatek/ (i thought this might be helpful):

BT_RAM_CODE_MT7922_1_1_hdr.bin.zst
BT_RAM_CODE_MT7961_1_2_hdr.bin.zst
mt7601u.bin.zst
mt7610e.bin.zst
mt7610u.bin.zst
mt7615_cr4.bin.zst
mt7615_n9.bin.zst
mt7615_rom_patch.bin.zst
mt7622_n9.bin.zst
mt7622pr2h.bin.zst
mt7622_rom_patch.bin.zst
mt7650.bin.zst
mt7650e.bin.zst
mt7662.bin.zst
mt7662_rom_patch.bin.zst
mt7662u.bin.zst
mt7662u_rom_patch.bin.zst
mt7663_n9_rebb.bin.zst
mt7663_n9_v3.bin.zst
mt7663pr2h.bin.zst
mt7663pr2h_rebb.bin.zst
mt7668pr2h.bin.zst
mt7915_eeprom.bin.zst
mt7915_eeprom_dbdc.bin.zst
mt7915_rom_patch.bin.zst
mt7915_wa.bin.zst
mt7915_wm.bin.zst
mt7916_eeprom.bin.zst
mt7916_rom_patch.bin.zst
mt7916_wa.bin.zst
mt7916_wm.bin.zst
mt7981_rom_patch.bin.zst
mt7981_wa.bin.zst
mt7981_wm.bin.zst
mt7981_wo.bin.zst
mt7986_eeprom_mt7975_dual.bin.zst
mt7986_eeprom_mt7976.bin.zst
mt7986_eeprom_mt7976_dbdc.bin.zst
mt7986_eeprom_mt7976_dual.bin.zst
mt7986_rom_patch.bin.zst
mt7986_rom_patch_mt7975.bin.zst
mt7986_wa.bin.zst
mt7986_wm.bin.zst
mt7986_wm_mt7975.bin.zst
mt7986_wo_0.bin.zst
mt7986_wo_1.bin.zst
mt7988
mt8173
mt8183
mt8186
mt8192
mt8195
sof
sof-tplg
WIFI_MT7922_patch_mcu_1_1_hdr.bin.zst
WIFI_MT7961_patch_mcu_1_2_hdr.bin.zst
WIFI_RAM_CODE_MT7922_1.bin.zst
WIFI_RAM_CODE_MT7961_1.bin.zst

This is my first time in a forum so forgive me if i made any mistakes and please let me know if you need anything else.

Last edited by beast41514 (2024-01-12 15:17:08)

seth · 2024-01-11 09:26:14

Please use [code][/code] tags. Edit your post in this regard.

12 is ENOMEM, you're out of RAM… 5 is EIO (IO error) because "Unable to change power state from D3cold to D0, device inaccessible" the device doesn't power up.
Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Ceterum censeo: is there a parallel windows installation?
3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

beast41514 · 2024-01-11 14:34:06

# Complete system journal:

http://0x0.st/HIpi.txt

Q. Ceterum censeo: is there a parallel windows installation?
Ans. Yes i have dual booted with windows 10.

# How to boot w/o GUI:

[Odd@Odd ~]$ systemctl get-default
graphical.target
[Odd@Odd ~]$ systemctl set-default multi-user.target
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-unit-files ====
Authentication is required to manage system service or unit files.
Authenticating as: Odd
Password:
==== AUTHENTICATION COMPLETE ====
Created symlink /etc/systemd/system/default.target → /usr/lib/systemd/system/multi-user.target.
[Odd@Odd ~]$

Do let me know if you need anything else and thank you, i didn't expect someone to reply this early.

seth · 2024-01-11 14:37:28

Ans. Yes i have dual booted with windows 10.
# How to boot w/o GUI:

seth wrote:

3rd link below.

latest?cb=20100325001624

beast41514 · 2024-01-11 15:07:16

So i did both these things How to boot w/o GUI and Disable Windows Fast-Start!. Also rebooted linux two times. Still not working.

# Output of

dmesg | grep mt7921e

after following the above steps:-

[    5.563332] mt7921e 0000:03:00.0: enabling device (0000 -> 0002)
[    5.591677] mt7921e 0000:03:00.0: ASIC revision: 79610010
[    5.668624] mt7921e: probe of 0000:03:00.0 failed with error -12

# After i executed these two commands:

sudo modprobe -r mt7921e

sudo modprobe -mt7921e

# The output of

 dmesg | grep mt7921e

is:

[    5.563332] mt7921e 0000:03:00.0: enabling device (0000 -> 0002)
[    5.591677] mt7921e 0000:03:00.0: ASIC revision: 79610010
[    5.668624] mt7921e: probe of 0000:03:00.0 failed with error -12
[  251.871887] mt7921e 0000:03:00.0: ASIC revision: 79610010
[  251.949068] mt7921e: probe of 0000:03:00.0 failed with error -12

Last edited by beast41514 (2024-01-11 15:08:13)

seth · 2024-01-11 15:15:52

You can revert to the graphical.target, this is completely irrelevant to the problem.

Why do you issue "pci=nocrs"?

There're more problems…

Jan 12 00:48:53 Odd kernel: ------------[ cut here ]------------
Jan 12 00:48:53 Odd kernel: WARNING: CPU: 7 PID: 254 at drivers/iommu/dma-iommu.c:1038 iommu_dma_unmap_page+0x7d/0x90
Jan 12 00:48:53 Odd kernel: Modules linked in: amdgpu(+) nouveau(+) serio_raw atkbd mxm_wmi libps2 gpu_sched drm_ttm_helper vivaldi_fmap ttm drm_buddy nvme drm_display_helper crc32c_intel xhci_pci nvme_core video xhci_pci_renesas cec i8042 nvme_common serio wmi
Jan 12 00:48:53 Odd kernel: CPU: 7 PID: 254 Comm: (udev-worker) Not tainted 6.1.65-1-lts #1 5f937405bb4d37e08d1e10e72ecd38f8cce6046d
Jan 12 00:48:53 Odd kernel: Hardware name: ASUSTeK COMPUTER INC. ROG Strix G513IC_G513IC/G513IC, BIOS G513IC.329 03/01/2023
Jan 12 00:48:53 Odd kernel: RIP: 0010:iommu_dma_unmap_page+0x7d/0x90
Jan 12 00:48:53 Odd kernel: Code: 2b 48 3b 28 72 26 48 3b 68 08 73 20 4d 89 f8 44 89 f1 4c 89 ea 48 89 ee 48 89 df 5b 5d 41 5c 41 5d 41 5e 41 5f e9 a3 85 9b ff <0f> 0b 5b 5d 41 5c 41 5d 41 5e 41 5f e9 f2 54 87 00 66 90 f3 0f 1e
Jan 12 00:48:53 Odd kernel: RSP: 0018:ffffb04201527af8 EFLAGS: 00010246
Jan 12 00:48:53 Odd kernel: RAX: 0000000000000000 RBX: ffff975501a350d0 RCX: 0000000000000027
Jan 12 00:48:53 Odd kernel: RDX: 0000000000000000 RSI: 0000000000000003 RDI: ffffb04201527ad8
Jan 12 00:48:53 Odd kernel: RBP: ffffb04201527b60 R08: ffffffffffffffff R09: 0000000000000001
Jan 12 00:48:53 Odd kernel: R10: 0000000000000007 R11: 0000000000000000 R12: ffffffffffffffff
Jan 12 00:48:53 Odd kernel: R13: 0000000000001000 R14: 0000000000000000 R15: 0000000000000000
Jan 12 00:48:53 Odd kernel: FS:  00007f94c58e4480(0000) GS:ffff9757df7c0000(0000) knlGS:0000000000000000
Jan 12 00:48:53 Odd kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 12 00:48:53 Odd kernel: CR2: 000056547f952078 CR3: 0000000103e2e000 CR4: 0000000000350ee0
Jan 12 00:48:53 Odd kernel: Call Trace:
Jan 12 00:48:53 Odd kernel:  <TASK>
Jan 12 00:48:53 Odd kernel:  ? iommu_dma_unmap_page+0x7d/0x90
Jan 12 00:48:53 Odd kernel:  ? __warn+0x7d/0xd0
Jan 12 00:48:53 Odd kernel:  ? iommu_dma_unmap_page+0x7d/0x90
Jan 12 00:48:53 Odd kernel:  ? report_bug+0xe6/0x150
Jan 12 00:48:53 Odd kernel:  ? handle_bug+0x3c/0x80
Jan 12 00:48:53 Odd kernel:  ? exc_invalid_op+0x17/0x70
Jan 12 00:48:53 Odd kernel:  ? asm_exc_invalid_op+0x1a/0x20
Jan 12 00:48:53 Odd kernel:  ? iommu_dma_unmap_page+0x7d/0x90
Jan 12 00:48:53 Odd kernel:  ? iommu_dma_unmap_page+0x32/0x90
Jan 12 00:48:53 Odd kernel:  gf100_fb_dtor+0x35/0x50 [nouveau c7d524e555efbbef0239de738a113248a7207017]
Jan 12 00:48:53 Odd kernel:  nvkm_subdev_del+0x7d/0xb0 [nouveau c7d524e555efbbef0239de738a113248a7207017]
Jan 12 00:48:53 Odd kernel:  nvkm_device_del+0x71/0x130 [nouveau c7d524e555efbbef0239de738a113248a7207017]
Jan 12 00:48:53 Odd kernel:  nouveau_drm_probe+0x15e/0x1f0 [nouveau c7d524e555efbbef0239de738a113248a7207017]
Jan 12 00:48:53 Odd kernel:  local_pci_probe+0x45/0x80
Jan 12 00:48:53 Odd kernel:  pci_device_probe+0xc1/0x250
Jan 12 00:48:53 Odd kernel:  ? sysfs_do_create_link_sd+0x6e/0xe0
Jan 12 00:48:53 Odd kernel:  really_probe+0xde/0x380
Jan 12 00:48:53 Odd kernel:  ? pm_runtime_barrier+0x54/0x90
Jan 12 00:48:53 Odd kernel:  __driver_probe_device+0x78/0x120
Jan 12 00:48:53 Odd kernel:  driver_probe_device+0x1f/0x90
Jan 12 00:48:53 Odd kernel:  __driver_attach+0xd2/0x1c0
Jan 12 00:48:53 Odd kernel:  ? __device_attach_driver+0x110/0x110
Jan 12 00:48:53 Odd kernel:  bus_for_each_dev+0x8b/0xd0
Jan 12 00:48:53 Odd kernel:  bus_add_driver+0x1b2/0x200
Jan 12 00:48:53 Odd kernel:  driver_register+0x8d/0xe0
Jan 12 00:48:53 Odd kernel:  ? 0xffffffffc07e1000
Jan 12 00:48:53 Odd kernel:  do_one_initcall+0x5d/0x230
Jan 12 00:48:53 Odd kernel:  do_init_module+0x4a/0x1e0
Jan 12 00:48:53 Odd kernel:  __do_sys_finit_module+0xac/0x120
Jan 12 00:48:53 Odd kernel:  do_syscall_64+0x60/0x90
Jan 12 00:48:53 Odd kernel:  ? exit_to_user_mode_prepare+0x17d/0x1f0
Jan 12 00:48:53 Odd kernel:  ? syscall_exit_to_user_mode+0x2b/0x40
Jan 12 00:48:53 Odd kernel:  ? do_syscall_64+0x6c/0x90
Jan 12 00:48:53 Odd kernel:  ? do_syscall_64+0x6c/0x90
Jan 12 00:48:53 Odd kernel:  ? exc_page_fault+0x7c/0x180
Jan 12 00:48:53 Odd kernel:  entry_SYSCALL_64_after_hwframe+0x64/0xce
Jan 12 00:48:53 Odd kernel: RIP: 0033:0x7f94c639b73d
Jan 12 00:48:53 Odd 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 c3 48 8b 0d c3 95 0c 00 f7 d8 64 89 01 48
Jan 12 00:48:53 Odd kernel: RSP: 002b:00007ffc95340208 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
Jan 12 00:48:53 Odd kernel: RAX: ffffffffffffffda RBX: 000056547f9603a0 RCX: 00007f94c639b73d
Jan 12 00:48:53 Odd kernel: RDX: 0000000000000000 RSI: 00007f94c64a8376 RDI: 000000000000000f
Jan 12 00:48:53 Odd kernel: RBP: 00007f94c64a8376 R08: 0000000000000001 R09: fffffffffffffe90
Jan 12 00:48:53 Odd kernel: R10: 0000000000000050 R11: 0000000000000246 R12: 0000000000020000
Jan 12 00:48:53 Odd kernel: R13: 000056547f9642a0 R14: 0000000000000000 R15: 000056547f94a470
Jan 12 00:48:53 Odd kernel:  </TASK>
Jan 12 00:48:53 Odd kernel: ---[ end trace 0000000000000000 ]---
Jan 12 00:48:53 Odd kernel: nouveau: probe of 0000:01:00.0 failed with error -14

You've an Ampere chip, https://wiki.archlinux.org/title/NVIDIA#Installation (pay attention to all steps, notably #5 - and don't let the Count down again )

Jan 12 00:48:54 Odd kernel: kvm_amd: Unknown symbol __SCK__kvm_x86_cache_reg (err -2)
…

Next up: you've at least systemd-netword, NetworkManager and dhcpcd enabled and running.
Pick one, disable the others.
Then post the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

After fixing these things, please post an updated journal.

beast41514 · 2024-01-11 16:34:20

Q. Why do you issue "pci=nocrs"?
Ans. I don't remember the exact error that i was facing but it was related to kvm virtualization or something. Basically my system was not shutting down it was getting stuck at that kvm virtualization thing (as far as i remember). So adding pci=nocrs to the boot parameters fixed my problem.

I chose network manager and disbled others:

[Odd@Odd ~]$ sudo systemctl stop systemd-networkd
[sudo] password for Odd:
Stopping 'systemd-networkd.service', but its triggering units are still >
systemd-networkd.socket
[Odd@Odd ~]$ sudo systemctl disable systemd-networkd
[sudo] password for Odd:
Removed "/etc/systemd/system/dbus-org.freedesktop.network1.service".
Removed "/etc/systemd/system/sockets.target.wants/systemd-networkd.socke>
Removed "/etc/systemd/system/multi-user.target.wants/systemd-networkd.se>
Removed "/etc/systemd/system/sysinit.target.wants/systemd-network-genera>
Removed "/etc/systemd/system/network-online.target.wants/systemd-network>
Disabling 'systemd-networkd.service', but its triggering units are still>
systemd-networkd.socket
[Odd@Odd ~]$ sudo systemctl stop dhcpcd
[sudo] password for Odd:
[Odd@Odd ~]$ sudo systemctl disable dhcpcd
[sudo] password for Odd:
Removed "/etc/systemd/system/multi-user.target.wants/dhcpcd.service".
[Odd@Odd ~]$ sudo systemctl enable NetworkManager
[sudo] password for Odd:
[Odd@Odd ~]$ sudo systemctl start NetworkManager
[sudo] password for Odd:
[Odd@Odd ~]$

Following the NVIDIA installation guide.

# output of "lspci -k | grep -A 2 -E "(VGA|3D)"":

 
01:00.0 VGA compatible controller: NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] (rev a1)
	Subsystem: ASUSTeK Computer Inc. GA107M [GeForce RTX 3050 Mobile]
	Kernel modules: nouveau
--
05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Renoir (rev c6)
	Subsystem: ASUSTeK Computer Inc. Renoir
	Kernel driver in use: amdgpu

# My graphics card code is:

NV170 family (Ampere)
Code name 	        Official Name
NV177 (GA107) 	GeForce RTX 3050

It falls Ampere family which is not mentioned on the site only these are mentioned. NV110/GMXXX, Turing (NV160/TUXXX), Kepler (NVE0/GKXXX).
Which one should i choose ?

Last edited by beast41514 (2024-01-11 16:41:10)

seth · 2024-01-11 16:41:00

"the Maxwell (NV110/GMXXX) series and newer"

d.ALT · 2024-01-11 16:43:54

<EDIT>
I'm always so slow... Meh...
</EDIT>

Last edited by d.ALT (2024-01-11 16:44:42)

beast41514 · 2024-01-11 17:21:56

For the #4th step. I followed the instructions to enable multilib.

# If you want to run 32 bit applications on your x86_64 system,
# enable the multilib repositories as required here.

#[multilib-testing]
#Include = /etc/pacman.d/mirrorlist

#[multilib]
Include = /etc/pacman.d/mirrorlist

Then it said to upgrade the system. So i did it with:

sudo pacman -Syu

At the end it said "Errors occurred, no packages were upgraded."

[Odd@Odd etc]$ sudo pacman -Syu
[sudo] password for Odd:
:: Synchronizing package databases...
 core is up to date
 extra is up to date
:: Starting full system upgrade...
:: Replace onevpl with extra/libvpl? [Y/n] y
resolving dependencies...
:: There are 2 providers available for dbus-units:
:: Repository core
   1) dbus-broker-units  2) dbus-daemon-units

Enter a number (default=1):
looking for conflicting packages...

Packages (85) alacritty-0.13.1-1  amd-ucode-20231211.f2e52a1c-1
              aom-3.8.0-2  archlinux-keyring-20231222-1
              at-spi2-core-2.50.1-1  autoconf-2.72-1
              avahi-1:0.8+r194+g3f79789-1  bluez-libs-5.71-3
              ca-certificates-mozilla-3.96.1-1  dbus-1.14.10-2
              dbus-broker-35-2  dbus-broker-units-35-2  dhcpcd-10.0.6-1
              ffmpeg-2:6.1.1-1  fftw-3.3.10-4  firefox-121.0.1-1
              fontconfig-2:2.15.0-2  glib2-2.78.3-1  glslang-13.1.1-3
              gperftools-2.15-1  grub-2:2.12-1  gtk3-1:3.24.39-2
              harfbuzz-8.3.0-2  hwdata-0.378-1  hwloc-2.10.0-1
              icu-74.2-1  iproute2-6.7.0-1  iputils-20231222-2
              kbd-2.6.4-1  krb5-1.21.2-2  lcms2-2.16-1  libbpf-1.3.0-1
              libcap-ng-0.8.4-1  libdovi-3.2.0-2  libdrm-2.4.119-1
              libnl-3.9.0-1  libplacebo-6.338.1-1  librsvg-2:2.57.1-1
              libseccomp-2.5.5-1  libsecret-0.21.2-1  libssh-0.10.6-2
              libvpl-2.10.1-1  libxkbcommon-x11-1.6.0-1
              libxml2-2.12.3-1  licenses-20231215-1  lightdm-1:1.32.0-5
              linux-6.6.10.arch1-1
              linux-firmware-whence-20231211.f2e52a1c-1
              linux-headers-6.6.10.arch1-1  linux-lts-6.6.11-1
              lz4-1:1.9.4-2  mesa-1:23.3.2-2  mkinitcpio-37.1-2
              nspr-4.35-2  nss-3.96.1-1  nvidia-lts-1:545.29.06-11
              onevpl-2023.4.0-1 [removal]  openmpi-4.1.6-1
              openpmix-4.2.6-1  openssl-3.2.0-1  pixman-0.43.0-1
              pkgconf-2.1.0-2  rubberband-3.3.0-1  shaderc-2023.7-2
              snappy-1.1.10-1  spirv-tools-2023.5-1  sudo-1.9.15.p5-1
              svt-av1-1.8.0-1  systemd-255.2-2  systemd-libs-255.2-2
              systemd-sysvcompat-255.2-2  thunar-4.18.10-1
              tracker3-3.6.0-2  tzdata-2023d-1  util-linux-2.39.3-1
              util-linux-libs-2.39.3-1  v4l-utils-1.26.1-1
              vim-9.1.0000-1  vim-runtime-9.1.0000-1  vmaf-3.0.0-1
              vulkan-icd-loader-1.3.274-1  wlroots-0.17.1-1
              xorg-server-21.1.10-1  xorg-server-common-21.1.10-1
              xxhash-0.8.2-1

Total Installed Size:  1233.87 MiB
Net Upgrade Size:        84.03 MiB

:: Proceed with installation? [Y/n] y
(84/84) checking keys in keyring                   [###############] 100%
(84/84) checking package integrity                 [###############] 100%
error: mkinitcpio: signature from "Levente Polyak (anthraxx) <levente@leventepolyak.net>" is unknown trust
:: File /var/cache/pacman/pkg/mkinitcpio-37.1-2-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: failed to commit transaction (invalid or corrupted package)
Errors occurred, no packages were upgraded.
[Odd@Odd etc]$

I get this when i try to download it.

[Odd@Odd etc]$ sudo pacman -S lib32-nvidia-utils
[sudo] password for Odd:
error: target not found: lib32-nvidia-utils
[Odd@Odd etc]$

What am i doing wrong ? Btw i will reply to you tommorrow since its night time here.

Last edited by beast41514 (2024-01-11 17:26:11)

seth · 2024-01-11 20:37:27

#[multilib]
Include = /etc/pacman.d/mirrorlist

You didn't actually uncomment the repo.

beast41514 · 2024-01-12 05:50:52

So i followed all the way to the #5th step and regenerated the initramfs. by running this command "sudo mkinitcpio -P":

[Odd@Odd etc]$ sudo mkinitcpio -P
[sudo] password for Odd:
==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux-lts -g /boot/initramfs-linux-lts.img --microcode /boot/amd-ucode.img
==> Starting build: '6.1.65-1-lts'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-lts.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux-lts -g /boot/initramfs-linux-lts-fallback.img -S autodetect --microcode /boot/amd-ucode.img
==> Starting build: '6.1.65-1-lts'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'qla1280'
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-lts-fallback.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux.img --microcode /boot/amd-ucode.img
==> Starting build: '6.6.3-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux-fallback.img -S autodetect --microcode /boot/amd-ucode.img
==> Starting build: '6.6.3-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'qla1280'
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img'
==> Image generation successful
[Odd@Odd etc]

#Then on to the 6th step and rebooted.Then it said to continue to #Xorg configuration or #Wayland. I went on the xorg link. There it said to run this command "nvidia-xconfig":

User
[Odd@Odd ~]$ nvidia-xconfig

WARNING: Unable to locate/open X configuration file.


WARNING: Unable to parse X.Org version string.


ERROR: Unable to find any GPUs in the system.


ERROR: Unable to write to directory '/etc/X11'.

My "/etc/X11/xorg.conf" is empty.

What seems to be the problem ?

Btw i think you should know this that in order to boot into arch i have to disable secure boot and to boot into windows i have to enable it. Also i have dropped my laptop so my screen flickers on movement and my wifi card works in windows but if i move my laptop physcially like picking it up the wifi goes away, even the option to enable it. So i have to restart my system to get it on. This wifi issue did not happen right after if dropped my laptop but after a month or so.

Last edited by beast41514 (2024-01-12 05:51:51)

seth · 2024-01-12 08:04:40

My "/etc/X11/xorg.conf" is empty.

That file should not even exist, remove it again, don't run nvidia-xconfig, it produces cruft.

Why are you running linux 6.6.3?
If you only installed the nvidia packages, the current modules won't match that kernel and you'll end up w/o any kernel module (as nouveau gets blacklisted)
Do not conduction partial updates, run "pacman -Syu"

beast41514 · 2024-01-12 08:25:21

I am sorry i mistook xorg.conf for a file actually it was a directory, its full name is "xorg.conf.d"

I am getting this everytime i run "pacman -Syu". It says to replace "onevpl" with "extra/libvpl" and when i enter yes and choose one of the providers. At the end it always says that some file is corrupted, asks if you want to delete it and when i enter yes, it says "error: failed to commit transaction. errors occurred, no packages were upgraded."

$ Output of "pacman -Syu":

[Odd@Odd ~]$ sudo pacman -Syu
[sudo] password for Odd:
:: Synchronizing package databases...
 core                  128.9 KiB   128 KiB/s 00:01 [###############] 100%
 extra                   8.3 MiB  4.52 MiB/s 00:02 [###############] 100%
 multilib              139.5 KiB   488 KiB/s 00:00 [###############] 100%
:: Starting full system upgrade...
:: Replace onevpl with extra/libvpl? [Y/n] y
resolving dependencies...
:: There are 2 providers available for dbus-units:
:: Repository core
   1) dbus-broker-units  2) dbus-daemon-units

Enter a number (default=1): 1
looking for conflicting packages...

Packages (81) alacritty-0.13.1-1  amd-ucode-20231211.f2e52a1c-1
              aom-3.8.0-2  archlinux-keyring-20231222-1
              at-spi2-core-2.50.1-1  autoconf-2.72-1
              avahi-1:0.8+r194+g3f79789-1  bluez-libs-5.71-3
              ca-certificates-mozilla-3.96.1-1  dbus-1.14.10-2
              dbus-broker-35-2  dbus-broker-units-35-2  dhcpcd-10.0.6-1
              ffmpeg-2:6.1.1-1  fftw-3.3.10-4  firefox-121.0.1-1
              fontconfig-2:2.15.0-2  glib2-2.78.3-1  glslang-13.1.1-3
              gperftools-2.15-1  grub-2:2.12-1  gtk3-1:3.24.39-2
              harfbuzz-8.3.0-2  hwdata-0.378-1  hwloc-2.10.0-1
              icu-74.2-1  iproute2-6.7.0-1  iputils-20231222-2
              kbd-2.6.4-1  krb5-1.21.2-2  lcms2-2.16-1  libbpf-1.3.0-1
              libcap-ng-0.8.4-1  libdovi-3.2.0-2  libdrm-2.4.119-1
              libnl-3.9.0-1  libplacebo-6.338.1-1  librsvg-2:2.57.1-1
              libseccomp-2.5.5-1  libsecret-0.21.2-1  libssh-0.10.6-2
              libvpl-2.10.1-1  libxkbcommon-x11-1.6.0-1
              libxml2-2.12.3-1  licenses-20231215-1
              linux-6.6.10.arch1-1
              linux-firmware-whence-20231211.f2e52a1c-1
              linux-headers-6.6.10.arch1-1  linux-lts-6.6.11-1
              lz4-1:1.9.4-2  mesa-1:23.3.2-2  mkinitcpio-37.1-2
              nspr-4.35-2  nss-3.96.1-1  nvidia-lts-1:545.29.06-11
              onevpl-2023.4.0-1 [removal]  openmpi-4.1.6-1
              openpmix-4.2.6-1  openssl-3.2.0-1  pixman-0.43.0-1
              pkgconf-2.1.0-2  rubberband-3.3.0-1  shaderc-2023.7-2
              snappy-1.1.10-1  spirv-tools-2023.5-1  sudo-1.9.15.p5-1
              svt-av1-1.8.0-1  systemd-255.2-2  systemd-libs-255.2-2
              systemd-sysvcompat-255.2-2  thunar-4.18.10-1
              tracker3-3.6.0-3  tzdata-2023d-1  util-linux-2.39.3-1
              util-linux-libs-2.39.3-1  v4l-utils-1.26.1-1
              vim-9.1.0000-1  vim-runtime-9.1.0000-1  vmaf-3.0.0-1
              vulkan-icd-loader-1.3.274-1  wlroots-0.17.1-1

Total Download Size:      0.76 MiB
Total Installed Size:  1228.50 MiB
Net Upgrade Size:        83.63 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages...
 tracker3-3.6.0-3...   721.0 KiB  2.01 MiB/s 00:00 [###############] 100%
 mkinitcpio-37.1-...    52.9 KiB  98.0 KiB/s 00:01 [###############] 100%
 Total (2/2)           774.0 KiB   649 KiB/s 00:01 [###############] 100%
(80/80) checking keys in keyring                   [###############] 100%
(80/80) checking package integrity                 [###############] 100%
error: mkinitcpio: signature from "Levente Polyak (anthraxx) <levente@leventepolyak.net>" is unknown trust
:: File /var/cache/pacman/pkg/mkinitcpio-37.1-2-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: failed to commit transaction (invalid or corrupted package)
Errors occurred, no packages were upgraded.

Last edited by beast41514 (2024-01-12 08:28:32)

seth · 2024-01-12 08:27:48

rm xorg.conf.d/

Don't! That directory is supposed to be there (details matter…)

pacman -S archlinux-keyring
pacman -Syu

beast41514 · 2024-01-12 08:32:03

Dont worry i didn't delete it.

Do you want the output of "pacman -Syu" after installing "archlinux-keyring" ?

Last edited by beast41514 (2024-01-12 08:32:45)

seth · 2024-01-12 08:34:25

The only question is whether it succeeded or anthraxx is still of unknown trust.

beast41514 · 2024-01-12 09:09:32

Well I got myself in a new problem. So I decided I don't want my "lightdm" display manager. So in order to remove it, I had to remove "lightdm-gtk-greeter" first. After rebooting my qtile GUI didn't work, all I have is the terminal. So I asked chatgpt, how to make my qtile GUI work with a display manager and he said to include "exec qtile" at the end of my ~./bashrc file and run "source ~/.bashrc".

But after rebooting I am stuck in a login loop. I get the prompt to enter username and password again and again. After adding "init=/bin/bash" at the end of the linux line. I was in recovery mode but was not able to type anything, it said "bash: no job control in this shell." So I added "single" instead of "init=/bin/bash" and it asks me for my password but I am not able to type anything. What should I do ?

Last edited by beast41514 (2024-01-12 09:12:24)

seth · 2024-01-12 09:11:21

Stop flailing around, you're not making it easier by creating a moving target.
Boot the multi-user.target (2nd link below) and focus on the issue at hand, that is the bus errors. Not some fucking DM preferences.

beast41514 · 2024-01-12 09:19:01

Ok sorry it won't happen again

Last edited by beast41514 (2024-01-12 09:22:03)

beast41514 · 2024-01-12 09:27:55

Even after adding "systemd.unit=multi-user.target" at the end of the linux line to the boot parameters. I am still stuck in the login loop

Last edited by beast41514 (2024-01-12 09:29:57)

seth · 2024-01-12 09:30:39

I asked chatgpt, how to make my qtile GUI work with a display manager and he said to include "exec qtile" at the end of my ~./bashrc file and run "source ~/.bashrc".

Undo that. And don't ask this bullshit generator things. It'll only tell you bullshit.

You're probably still able to login as root to fix your bashrc, otherwise you'll have to boot the install iso, mount your home partition and edit the file from there.

beast41514 · 2024-01-12 09:55:46

Ok so I did this "boot the install iso, mount your home partition and edit the file from there".

[root@archiso ~]# nano ~/.bashrc

But now the file is empty.

V1del · 2024-01-12 10:18:37

You are operating on the root user there, it's quite unlikely that this is your standard user, check /home/youruser/.bashrc

beast41514 · 2024-01-12 10:28:23

Thank you I am able to login now.

Last edited by beast41514 (2024-01-12 10:43:27)

Arch Linux

#1 2024-01-11 08:55:45

[Solved] Wifi not working , MEDIATEK Corp. MT7921 802.11ax

#2 2024-01-11 09:26:14

Re: [Solved] Wifi not working , MEDIATEK Corp. MT7921 802.11ax

#3 2024-01-11 14:34:06

Re: [Solved] Wifi not working , MEDIATEK Corp. MT7921 802.11ax

#4 2024-01-11 14:37:28

Re: [Solved] Wifi not working , MEDIATEK Corp. MT7921 802.11ax

#5 2024-01-11 15:07:16

Re: [Solved] Wifi not working , MEDIATEK Corp. MT7921 802.11ax

#6 2024-01-11 15:15:52

Re: [Solved] Wifi not working , MEDIATEK Corp. MT7921 802.11ax

#7 2024-01-11 16:34:20

Re: [Solved] Wifi not working , MEDIATEK Corp. MT7921 802.11ax

#8 2024-01-11 16:41:00

Re: [Solved] Wifi not working , MEDIATEK Corp. MT7921 802.11ax

#9 2024-01-11 16:43:54

Re: [Solved] Wifi not working , MEDIATEK Corp. MT7921 802.11ax

#10 2024-01-11 17:21:56

Re: [Solved] Wifi not working , MEDIATEK Corp. MT7921 802.11ax

#11 2024-01-11 20:37:27

Re: [Solved] Wifi not working , MEDIATEK Corp. MT7921 802.11ax

#12 2024-01-12 05:50:52

Re: [Solved] Wifi not working , MEDIATEK Corp. MT7921 802.11ax

#13 2024-01-12 08:04:40

Re: [Solved] Wifi not working , MEDIATEK Corp. MT7921 802.11ax

#14 2024-01-12 08:25:21

Re: [Solved] Wifi not working , MEDIATEK Corp. MT7921 802.11ax

#15 2024-01-12 08:27:48

Re: [Solved] Wifi not working , MEDIATEK Corp. MT7921 802.11ax

#16 2024-01-12 08:32:03

Re: [Solved] Wifi not working , MEDIATEK Corp. MT7921 802.11ax

#17 2024-01-12 08:34:25

Re: [Solved] Wifi not working , MEDIATEK Corp. MT7921 802.11ax

#18 2024-01-12 09:09:32

Re: [Solved] Wifi not working , MEDIATEK Corp. MT7921 802.11ax

#19 2024-01-12 09:11:21

Re: [Solved] Wifi not working , MEDIATEK Corp. MT7921 802.11ax

#20 2024-01-12 09:19:01

Re: [Solved] Wifi not working , MEDIATEK Corp. MT7921 802.11ax

#21 2024-01-12 09:27:55

Re: [Solved] Wifi not working , MEDIATEK Corp. MT7921 802.11ax

#22 2024-01-12 09:30:39

Re: [Solved] Wifi not working , MEDIATEK Corp. MT7921 802.11ax

#23 2024-01-12 09:55:46

Re: [Solved] Wifi not working , MEDIATEK Corp. MT7921 802.11ax

#24 2024-01-12 10:18:37

Re: [Solved] Wifi not working , MEDIATEK Corp. MT7921 802.11ax

#25 2024-01-12 10:28:23

Re: [Solved] Wifi not working , MEDIATEK Corp. MT7921 802.11ax

Board footer