[Unstable Update] 2021-12-13 - Python 3.10 Rebuilds

I confirm the above issue is no longer present for me as of the release of kernel 5.15.15, which makes me think that this regression with Intel Bluetooth was finally fixed upstream.

Before kernel 5.15.15:

Jan 05 23:20:39 manjaro-unstable kernel: Bluetooth: Core ver 2.22
Jan 05 23:20:39 manjaro-unstable kernel: NET: Registered PF_BLUETOOTH protocol family
Jan 05 23:20:39 manjaro-unstable kernel: Bluetooth: HCI device and connection manager initialized
Jan 05 23:20:39 manjaro-unstable kernel: Bluetooth: HCI socket layer initialized
Jan 05 23:20:39 manjaro-unstable kernel: Bluetooth: L2CAP socket layer initialized
Jan 05 23:20:39 manjaro-unstable kernel: Bluetooth: SCO socket layer initialized
Jan 05 23:20:40 manjaro-unstable kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Jan 05 23:20:40 manjaro-unstable kernel: Bluetooth: BNEP filters: protocol multicast
Jan 05 23:20:40 manjaro-unstable kernel: Bluetooth: BNEP socket layer initialized
Jan 05 23:20:42 manjaro-unstable kernel: Bluetooth: hci0: command 0xfc05 tx timeout
Jan 05 23:20:42 manjaro-unstable kernel: Bluetooth: hci0: Reading Intel version command failed (-110)

After kernel 5.15.15, by only restarting my system:

Jan 20 10:33:46 manjaro-unstable kernel: Bluetooth: Core ver 2.22
Jan 20 10:33:46 manjaro-unstable kernel: NET: Registered PF_BLUETOOTH protocol family
Jan 20 10:33:46 manjaro-unstable kernel: Bluetooth: HCI device and connection manager initialized
Jan 20 10:33:46 manjaro-unstable kernel: Bluetooth: HCI socket layer initialized
Jan 20 10:33:46 manjaro-unstable kernel: Bluetooth: L2CAP socket layer initialized
Jan 20 10:33:46 manjaro-unstable kernel: Bluetooth: SCO socket layer initialized
Jan 20 10:33:46 manjaro-unstable kernel: Bluetooth: hci0: Legacy ROM 2.5 revision 1.0 build 3 week 17 2014
Jan 20 10:33:46 manjaro-unstable kernel: Bluetooth: hci0: Intel device is already patched. patch num: 32
Jan 20 10:33:46 manjaro-unstable kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Jan 20 10:33:46 manjaro-unstable kernel: Bluetooth: BNEP filters: protocol multicast
Jan 20 10:33:46 manjaro-unstable kernel: Bluetooth: BNEP socket layer initialized
Jan 20 10:33:50 manjaro-unstable kernel: Bluetooth: RFCOMM TTY layer initialized
Jan 20 10:33:50 manjaro-unstable kernel: Bluetooth: RFCOMM socket layer initialized
Jan 20 10:33:50 manjaro-unstable kernel: Bluetooth: RFCOMM ver 1.11

Cheers! :slightly_smiling_face:

See FS#73427 - [pipewire-jack] conflicts with jack2 but doesn’t provides?

1 Like

:information_source: linux-firmware 20220119.0c6a7b3-2 requires kernel >=5.3 and package splitting

2022-01-21 - Andreas Radke

The linux-firmware package 20220119.0c6a7b3-2 implements kernel firmware compression. Linux kernel from 5.3 on support loading from xz compressed firmware.
CONFIG_FW_LOADER_COMPRESS kernel option must be enabled. All official Arch Linux kernel support this for a long time. [1]

The linux-firmware package has been split into smaller packages to further reduce required disk space. Some big firmware files of rarely used hardware have been split into separate packages.
This affects firmware for Mellanox Spectrum switches, Marvell devices, Qualcomm SoCs, Cavium LiquidIO server adapters, QLogic devices, Broadcom NetXtreme II 10Gb ethernet adapters.
Make sure to install additional firmware packages if needed. [2]

[1] FS#72899
[2] FS#72559 + svn commit

:point_right: For users with kernels <5.3 installed, they will need to migrate to a 5.x kernel. The 4.x series is now dropped from the repos. :point_left:

4 Likes

Any difference from linux-firmware-whence provided by Arch Linux?

I’m really liking reduced size of linux-firmware.

1 Like

linux-firmware-whence is provided by Arch. We just created the linux4x- overlays for kernels <5.3.

1 Like

2 posts were split to a new topic: Issues with accountsservice

Permissions for accountservice don’t seem to be correct

warning: directory permissions differ on /var/lib/AccountsService/
filesystem: 755  package: 775
1 Like

Getting this on Kernel 5.10.95:

==> WARNING: Possibly missing firmware for module: qla1280
==> WARNING: Possibly missing firmware for module: qed
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: qla2xxx

You did read this post above, right? :wink:

1 Like

A post was split to a new topic: Qbittorrent not working when using aur libraries

6 posts were split to a new topic: Where can I post questions and problems?

new update on sudo requires merging of new syntax in /etc/sudoers file. i merged using kompare and did the final change (for my user) only in visudo, and there were no complains. hope that is ok

1 Like

NVIDIA 510.47.03 drivers are pushed, kernel updates and extramodules will follow. Use nvidia-dkms for now if you want.

1 Like

After recent upgrade to manjaro-system (20210612-1 → 20220202-1).
User is not in the sudoers file. This incident will be reported.

Fix: Uncomment these two lines

## Uncomment to allow members of group wheel to execute any command
%wheel ALL=(ALL:ALL) ALL

## Uncomment to allow members of group sudo to execute any command
%sudo ALL=(ALL:ALL) ALL
1 Like

That is strange that here on Manjaro, sudo just worked without uncommenting those lines. I have

Manjaro:

## User privilege specification
##
root ALL=(ALL:ALL) ALL

In Arch (VM), I received that same comment as you, which I fixed by adding myself:
Arch:

## User privilege specification
##
root ALL=(ALL:ALL) ALL
jrichard ALL=(ALL:ALL) ALL

this? [Testing Update] 2022-02-01 - Kernels, Pipewire 0.3.44, Qt5, Mesa 21.3.5, Wine 7.0 - #31 by omano (EDIT 2 and 3)

This should not have happen, it removed the file discussed in link above. [Testing Update] 2022-02-01 - Kernels, Pipewire 0.3.44, Qt5, Mesa 21.3.5, Wine 7.0 - #36 by philm

My solution:
su
then:
groups

Result: exists no group called “sudo”
Therefore (as root):
groupadd sudo
then
usermod -a -G sudo "user"
and reboot. Voila.

1 Like

latest sudo (1.9.9-2) has “disable non-interactive auth”.

does that mean keyword “NOPASSWD:” is no more in-affect in sudoers file. :slightly_frowning_face: