[Testing Update] 2022-10-07 - Kernels, Octopi, Deepin, GlibC, Haskell, Python

Hello community,

Another testing branch update with some usual package updates for you.

image
Don’t miss out on 15% discount on all our Manjaro Merch!

  • We updated most of our Kernels
    • This includes the release of 6.0 kernel series
    • Note that linux518 got dropped from our repos
  • Octopi is now at 0.14.0
  • Deepin gained some updates
  • GlibC fixed some issues, including locale generation
  • Some KDE-git, Haskell and Python updates as usual

Additional Info

Info about AUR packages

:warning: AUR (Arch User Repository) packages are neither supported by Arch nor Manjaro. Posts about them in Announcement topics are off-topic and will be flagged, moved or removed without warning.

:information_source: You may need to rebuild any AUR packages that install files to site-packages …

Get our latest daily developer images now from Github: Plasma, GNOME, XFCE. You can get the latest stable releases of Manjaro from CDN77.


Our current supported kernels

  • linux419 4.19.261
  • linux54 5.4.217
  • linux510 5.10.147
  • linux515 5.15.72
  • linux519 5.19.14
  • linux60 6.0.0
  • linux515-rt 5.15.71_rt51
  • linux519-rt 5.19.0_rt10

Package changes (Fri Oct 7 09:42:23 CEST 2022)

  • testing community x86_64: 680 new and 663 removed package(s)
  • testing core x86_64: 21 new and 24 removed package(s)
  • testing extra x86_64: 210 new and 318 removed package(s)
  • testing kde-unstable x86_64: 355 new and 355 removed package(s)
  • testing multilib x86_64: 3 new and 3 removed package(s)

A list of all package changes can be found here.

  • No issue, everything went smoothly
  • Yes there was an issue. I was able to resolve it myself.(Please post your solution)
  • Yes i am currently experiencing an issue due to the update. (Please post about it)

0 voters

Check if your mirror has already synced:

7 Likes

Known issues and solutions

This is a wiki post; please edit as necessary.
Please, consider subscribing to the Testing Updates Announcements RSS feed


Please RTFT (Read This Fine Thread) first before reporting the same issues over and over again!

:arrow_right: 2022-10-07

2022-09-23

Nvidia 3060RTX cards may have issues with the 515.76 driver
Removing python2 from the repositories

2022-09-23 - Jelle van der Waa

Python 2 went end of life January 2020. Since then we have been actively cutting down the number of projects depending on python2 in our repositories, and we have finally been able to drop it from our distribution. If you still have python2 installed on your system consider removing it and any python2 package.

If you still require the python2 package you can keep it around, but please be aware that there will be no security updates. If you need a patched package please consult the AUR, or use an unofficial user repository.*

Arch Linux - News: Removing python2 from the repositories

* Note: Unofficial user repositories are not supported

2022-08-27

Changes with Back In Time packages
  • backintime has been renamed to backintime-qt
  • backintime-cli has been renamed to backintime

After replacing backintime-cli with backintime, you will need to install backintime-qt manually if you want the Qt frontend installed again.

2022-08-23

electron12, electron13, electron14 & electron16 have been dropped to the AUR

Unsupported Electron packages have been dropped from the official repos to the AUR. They no longer receive security updates and nothing in the repos depend on them.

If you have AUR packages depending on those versions, install the binary version from the AUR to replace them; i.e., electron16-bin.

See FS#75490 - electron12, electron13, electron14, electron16 are unsupported and vulnerable packages

End of Support for 15.x.y and 16.x.y

Electron 15.x.y and 16.x.y has reached end-of-support. As per Electron’s new 8-week cadence, we were supporting the latest four versions of Electron until May 2022. With this Electron 19 release, we’ll return to supporting the latest three major versions, as well as the alpha, beta, and nightly releases.

Release electron v19.0.0 · electron/electron · GitHub

2022-08-12

element-desktop dependency error (fixed with 1.11.4)
error: failed to prepare transaction (could not satisfy dependencies)
:: installing electron (20.0.0-1) breaks dependency 'electron19' required by element-desktop

The upstream package was already flagged out of date (it needs to be rebuilt against latest electron).

Workaround for now:

sudo pacman -Syy electron electron19 --asdeps
sudo pacman -Su

2022-08-04

Glibc 2.36 update will break EasyAntiCheat within Proton (should be fixed with glibc 2.36-2)

Temporary workaround for now is to use the flatpak version of steam:

sudo pacman -S flatpak --needed --noconfirm
sudo flatpak install com.valvesoftware.Steam -y

You can use flatseal (another flatpak app) to grant it access to your existing game library so you don’t have to re-download your games (add the game library install path under “Other files” under “Filesystem”).

sudo flatpak install com.github.tchx84.Flatseal -y

For advanced users (not recommended by us): patched glibc and lib32-glibc are available here. They remove the commit that broke EAC.

2022-07-27

Fixed: Pamac shows archlinux-keyring (20220713-2) and manjaro-keyring (20220514-2) as orphans
sudo pacman -D --asexplicit archlinux-keyring manjaro-keyring

Resolved: w/ base 3-2 Revert changes:

sudo pacman -D --asdeps archlinux-keyring manjaro-keyring

2022-07-16

wxWidgets 3.2 update may need manual intervention

Packages have been renamed from wxgtk- to wxwidgets-. The GTK2 frontend is no longer provided. If you have wxgtk2 installed, the upgrade will fail with:

In such case, uninstall wxgtk2 first and then proceed with the upgrade.

2022-07-13

Linux518: could not insert 'amd_pstate': No such device

With Kernel 5.18.11 there was added a regression to AMD P-State driver preventing it from loading.

2022-07-08

Wireplumber 0.4.11 may crash for GDM users

Currently there is an issue with 0.4.11 and GDM crashing on boot-up. More in the upstream bugtracker issue: wireplumber segfault: system boot and could see in my dmesg (#305) · Issues · PipeWire / wireplumber · GitLab

2022-06-07

Locale file changes

C.UTF8 locale is now included in glibc:

Credits @diabonas for this change. Systemd wants us to include C.UTF8 by default and it seems the locale may be in included by glibc upstream in the future. To fix building and avoid nasty fixing in devtools, we include the locale in the package. See systemd/systemd#23252 (comment) FS#74864 : [systemd] >= 251 breaks devtools' locale

There is a pacsave for /etc/locale.conf as it has been removed from the filesystem package.

UPDATE: With filesystem 2022.06.08-2, it will automatically restore /etc/locale.conf if it did not already exist.

There is a pacnew for /etc/locale.gen. Please review it and regenerate your locale if necessary.

I have got many messages like this one from pamac:

Warnung: ruby-bundledgems wird vor seiner Abhängigkeit ruby installiert werden

So I choose not to install, but to install ruby first. Then I made another pamac update and no more warnings.

I get these every time there’s some major ruby update.
I wonder why the install process does the install backwards…

2 Likes

nvidia390.154 + linux60 = dkms install error code 10

LANG=C cat /var/lib/dkms/nvidia/390.154/build/make.log
DKMS make.log for nvidia-390.154 for kernel 6.0.0-1-MANJARO (x86_64)
Fr 7. Okt 12:10:55 CEST 2022
make[1]: Verzeichnis „/usr/lib/modules/6.0.0-1-MANJARO/build“ wird betreten
warning: the compiler differs from the one used to build the kernel
  The kernel was built by: gcc (GCC) 12.2.0
  You are using:           cc (GCC) 12.2.0
  SYMLINK /var/lib/dkms/nvidia/390.154/build/nvidia/nv-kernel.o
  SYMLINK /var/lib/dkms/nvidia/390.154/build/nvidia-modeset/nv-modeset-kernel.o
 CONFTEST: INIT_WORK
 CONFTEST: remap_pfn_range
 CONFTEST: hash__remap_4k_pfn
 CONFTEST: follow_pfn
 CONFTEST: vmap
 CONFTEST: set_pages_uc
 CONFTEST: list_is_first
 CONFTEST: set_memory_uc
 CONFTEST: set_memory_array_uc
 CONFTEST: change_page_attr
 CONFTEST: pci_get_class
 CONFTEST: pci_choose_state
 CONFTEST: vm_insert_page
 CONFTEST: acpi_device_id
 CONFTEST: acquire_console_sem
 CONFTEST: console_lock
 CONFTEST: kmem_cache_create
 CONFTEST: on_each_cpu
 CONFTEST: smp_call_function
 CONFTEST: acpi_evaluate_integer
 CONFTEST: ioremap_cache
 CONFTEST: ioremap_wc
 CONFTEST: acpi_walk_namespace
 CONFTEST: pci_domain_nr
 CONFTEST: dma_mapping_error
 CONFTEST: sg_alloc_table
 CONFTEST: sg_init_table
 CONFTEST: pci_get_domain_bus_and_slot
 CONFTEST: get_num_physpages
 CONFTEST: efi_enabled
 CONFTEST: proc_create_data
 CONFTEST: pde_data
 CONFTEST: PDE_DATA
 CONFTEST: proc_remove
 CONFTEST: pm_vt_switch_required
 CONFTEST: xen_ioemu_inject_msi
 CONFTEST: phys_to_dma
 CONFTEST: get_dma_ops
 CONFTEST: write_cr4
 CONFTEST: of_get_property
 CONFTEST: of_find_node_by_phandle
 CONFTEST: of_node_to_nid
 CONFTEST: pnv_pci_get_npu_dev
 CONFTEST: for_each_online_node
 CONFTEST: node_end_pfn
 CONFTEST: pci_bus_address
 CONFTEST: pci_stop_and_remove_bus_device
 CONFTEST: pci_remove_bus_device
 CONFTEST: request_threaded_irq
 CONFTEST: register_cpu_notifier
 CONFTEST: cpuhp_setup_state
 CONFTEST: dma_map_resource
 CONFTEST: backlight_device_register
 CONFTEST: register_acpi_notifier
 CONFTEST: timer_setup
 CONFTEST: kmem_cache_create_usercopy
 CONFTEST: do_gettimeofday
 CONFTEST: dma_direct_map_resource
 CONFTEST: vmf_insert_pfn
 CONFTEST: jiffies_to_timespec
 CONFTEST: ktime_get_raw_ts64
 CONFTEST: ktime_get_real_ts64
 CONFTEST: ioremap_nocache
 CONFTEST: vga_tryget
 CONFTEST: unsafe_follow_pfn
 CONFTEST: acpi_bus_get_device
 CONFTEST: remap_page_range
 CONFTEST: address_space_init_once
 CONFTEST: kbasename
 CONFTEST: fatal_signal_pending
 CONFTEST: list_cut_position
 CONFTEST: vzalloc
 CONFTEST: wait_on_bit_lock_argument_count
 CONFTEST: bitmap_clear
 CONFTEST: usleep_range
 CONFTEST: radix_tree_empty
 CONFTEST: radix_tree_replace_slot
 CONFTEST: drm_dev_unref
 CONFTEST: drm_reinit_primary_mode_group
 CONFTEST: get_user_pages_remote
 CONFTEST: get_user_pages
 CONFTEST: drm_gem_object_lookup
 CONFTEST: drm_atomic_state_ref_counting
 CONFTEST: drm_driver_has_gem_prime_res_obj
 CONFTEST: drm_atomic_helper_connector_dpms
 CONFTEST: drm_connector_funcs_have_mode_in_name
 CONFTEST: drm_framebuffer_get
 CONFTEST: drm_gem_object_get
 CONFTEST: drm_dev_put
 CONFTEST: drm_connector_for_each_possible_encoder
 CONFTEST: drm_gem_object_put_unlocked
 CONFTEST: is_export_symbol_gpl_of_node_to_nid
 CONFTEST: is_export_symbol_present_swiotlb_map_sg_attrs
 CONFTEST: is_export_symbol_present_swiotlb_dma_ops
 CONFTEST: i2c_adapter
 CONFTEST: pm_message_t
 CONFTEST: irq_handler_t
 CONFTEST: acpi_device_ops
 CONFTEST: acpi_op_remove
 CONFTEST: outer_flush_all
 CONFTEST: proc_dir_entry
 CONFTEST: scatterlist
 CONFTEST: sg_table
 CONFTEST: file_operations
 CONFTEST: vm_operations_struct
 CONFTEST: atomic_long_type
 CONFTEST: pci_save_state
 CONFTEST: file_inode
 CONFTEST: task_struct
 CONFTEST: kuid_t
 CONFTEST: dma_ops
 CONFTEST: swiotlb_dma_ops
 CONFTEST: dma_map_ops
 CONFTEST: noncoherent_swiotlb_dma_ops
 CONFTEST: vm_fault_present
 CONFTEST: vm_fault_has_address
 CONFTEST: kernel_write
 CONFTEST: strnstr
 CONFTEST: iterate_dir
 CONFTEST: kstrtoull
 CONFTEST: backlight_properties_type
 CONFTEST: proc_ops
 CONFTEST: timeval
 CONFTEST: mm_has_mmap_lock
 CONFTEST: kmem_cache_has_kobj_remove_work
 CONFTEST: sysfs_slab_unlink
 CONFTEST: vmalloc_has_pgprot_t_arg
 CONFTEST: pci_dev_has_skip_bus_pm
 CONFTEST: pci_channel_state
 CONFTEST: fault_flags
 CONFTEST: atomic64_type
 CONFTEST: address_space
 CONFTEST: backing_dev_info
 CONFTEST: mm_context_t
 CONFTEST: vm_ops_fault_removed_vma_arg
 CONFTEST: vm_fault_t
 CONFTEST: pnv_npu2_init_context
 CONFTEST: drm_bus_present
 CONFTEST: drm_bus_has_bus_type
 CONFTEST: drm_bus_has_get_irq
 CONFTEST: drm_bus_has_get_name
 CONFTEST: drm_driver_has_device_list
 CONFTEST: drm_driver_has_legacy_dev_list
 CONFTEST: drm_driver_has_set_busid
 CONFTEST: drm_crtc_state_has_connectors_changed
 CONFTEST: drm_init_function_args
 CONFTEST: drm_mode_connector_list_update_has_merge_type_bits_arg
 CONFTEST: drm_helper_mode_fill_fb_struct
 CONFTEST: drm_master_drop_has_from_release_arg
 CONFTEST: drm_driver_unload_has_int_return_type
 CONFTEST: kref_has_refcount_of_type_refcount_t
 CONFTEST: drm_atomic_helper_crtc_destroy_state_has_crtc_arg
 CONFTEST: drm_mode_object_find_has_file_priv_arg
 CONFTEST: drm_connector_list_iter
 CONFTEST: drm_atomic_helper_swap_state_has_stall_arg
 CONFTEST: drm_driver_prime_flag_present
 CONFTEST: drm_gem_prime_export_has_dev_arg
 CONFTEST: drm_gem_object_has_resv
 CONFTEST: drm_display_mode_has_vrefresh
 CONFTEST: drm_driver_master_set_has_int_return_type
 CONFTEST: drm_driver_has_gem_free_object
 CONFTEST: drm_prime_pages_to_sg_has_drm_device_arg
 CONFTEST: drm_driver_has_gem_prime_callbacks
 CONFTEST: drm_crtc_atomic_check_has_atomic_state_arg
 CONFTEST: drm_gem_object_vmap_has_map_arg
 CONFTEST: drm_plane_atomic_check_has_atomic_state_arg
 CONFTEST: drm_device_has_pdev
 CONFTEST: dma_resv_add_fence
 CONFTEST: dma_resv_reserve_fences
 CONFTEST: reservation_object_reserve_shared_has_num_fences_arg
 CONFTEST: dom0_kernel_present
 CONFTEST: nvidia_vgpu_kvm_build
 CONFTEST: nvidia_grid_build
 CONFTEST: drm_available
 CONFTEST: drm_atomic_available
 CONFTEST: is_export_symbol_gpl_refcount_inc
 CONFTEST: is_export_symbol_gpl_refcount_dec_and_test
  CC [M]  /var/lib/dkms/nvidia/390.154/build/nvidia/nv-frontend.o
  CC [M]  /var/lib/dkms/nvidia/390.154/build/nvidia/nv-instance.o
  CC [M]  /var/lib/dkms/nvidia/390.154/build/nvidia/nv-gpu-numa.o
  CC [M]  /var/lib/dkms/nvidia/390.154/build/nvidia/nv.o
  CC [M]  /var/lib/dkms/nvidia/390.154/build/nvidia/nv-acpi.o
  CC [M]  /var/lib/dkms/nvidia/390.154/build/nvidia/nv-chrdev.o
  CC [M]  /var/lib/dkms/nvidia/390.154/build/nvidia/nv-cray.o
In Datei, eingebunden von ./include/linux/rculist.h:10,
                 von ./include/linux/pid.h:5,
                 von ./include/linux/sched.h:14,
                 von ./include/linux/ratelimit.h:6,
                 von ./include/linux/dev_printk.h:16,
                 von ./include/linux/device.h:15,
                 von ./include/linux/dma-mapping.h:7,
                 von /var/lib/dkms/nvidia/390.154/build/common/inc/pci-dma-compat.h:8,
                 von /var/lib/dkms/nvidia/390.154/build/common/inc/nv.h:17,
                 von /var/lib/dkms/nvidia/390.154/build/common/inc/nv-linux.h:16,
                 von /var/lib/dkms/nvidia/390.154/build/nvidia/nv-acpi.c:15:
/var/lib/dkms/nvidia/390.154/build/nvidia/nv-acpi.c: In Funktion »nv_acpi_add«:
/var/lib/dkms/nvidia/390.154/build/nvidia/nv-acpi.c:259:43: Fehler: »struct acpi_device« hat kein Element namens »children«
  259 |     list_for_each_safe(node, next, &device->children)
      |                                           ^~
./include/linux/list.h:643:21: Anmerkung: in Definition des Makros »list_for_each_safe«
  643 |         for (pos = (head)->next, n = pos->next; \
      |                     ^~~~
./include/linux/list.h:643:32: Warnung: linker Operand des Komma-Ausdrucks hat keinen Effekt [-Wunused-value]
  643 |         for (pos = (head)->next, n = pos->next; \
      |                                ^
/var/lib/dkms/nvidia/390.154/build/nvidia/nv-acpi.c:259:5: Anmerkung: bei Substitution des Makros »list_for_each_safe«
  259 |     list_for_each_safe(node, next, &device->children)
      |     ^~~~~~~~~~~~~~~~~~
/var/lib/dkms/nvidia/390.154/build/nvidia/nv-acpi.c:259:43: Fehler: »struct acpi_device« hat kein Element namens »children«
  259 |     list_for_each_safe(node, next, &device->children)
      |                                           ^~
./include/linux/list.h:644:34: Anmerkung: in Definition des Makros »list_for_each_safe«
  644 |              !list_is_head(pos, (head)); \
      |                                  ^~~~
In Datei, eingebunden von ./include/linux/bits.h:22,
                 von ./include/linux/ratelimit_types.h:5,
                 von ./include/linux/ratelimit.h:5:
/var/lib/dkms/nvidia/390.154/build/nvidia/nv-acpi.c:262:50: Fehler: »struct acpi_device« hat kein Element namens »node«; meinten Sie »fwnode«?
  262 |             list_entry(node, struct acpi_device, node);
      |                                                  ^~~~
./include/linux/build_bug.h:78:56: Anmerkung: in Definition des Makros »__static_assert«
   78 | #define __static_assert(expr, msg, ...) _Static_assert(expr, msg)
      |                                                        ^~~~
./include/linux/container_of.h:19:9: Anmerkung: bei Substitution des Makros »static_assert«
   19 |         static_assert(__same_type(*(ptr), ((type *)0)->member) ||       \
      |         ^~~~~~~~~~~~~
./include/linux/container_of.h:19:23: Anmerkung: bei Substitution des Makros »__same_type«
   19 |         static_assert(__same_type(*(ptr), ((type *)0)->member) ||       \
      |                       ^~~~~~~~~~~
./include/linux/list.h:520:9: Anmerkung: bei Substitution des Makros »container_of«
  520 |         container_of(ptr, type, member)
      |         ^~~~~~~~~~~~
/var/lib/dkms/nvidia/390.154/build/nvidia/nv-acpi.c:262:13: Anmerkung: bei Substitution des Makros »list_entry«
  262 |             list_entry(node, struct acpi_device, node);
      |             ^~~~~~~~~~
././include/linux/compiler_types.h:295:27: Fehler: Ausdruck in statischer Behauptung ist keine Ganzzahl
  295 | #define __same_type(a, b) __builtin_types_compatible_p(typeof(a), typeof(b))
      |                           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
./include/linux/build_bug.h:78:56: Anmerkung: in Definition des Makros »__static_assert«
   78 | #define __static_assert(expr, msg, ...) _Static_assert(expr, msg)
      |                                                        ^~~~
./include/linux/container_of.h:19:9: Anmerkung: bei Substitution des Makros »static_assert«
   19 |         static_assert(__same_type(*(ptr), ((type *)0)->member) ||       \
      |         ^~~~~~~~~~~~~
./include/linux/container_of.h:19:23: Anmerkung: bei Substitution des Makros »__same_type«
   19 |         static_assert(__same_type(*(ptr), ((type *)0)->member) ||       \
      |                       ^~~~~~~~~~~
./include/linux/list.h:520:9: Anmerkung: bei Substitution des Makros »container_of«
  520 |         container_of(ptr, type, member)
      |         ^~~~~~~~~~~~
/var/lib/dkms/nvidia/390.154/build/nvidia/nv-acpi.c:262:13: Anmerkung: bei Substitution des Makros »list_entry«
  262 |             list_entry(node, struct acpi_device, node);
      |             ^~~~~~~~~~
In Datei, eingebunden von ./include/uapi/linux/posix_types.h:5,
                 von ./include/uapi/linux/types.h:14,
                 von ./include/linux/types.h:6,
                 von ./include/linux/kasan-checks.h:5,
                 von ./include/asm-generic/rwonce.h:26,
                 von ./arch/x86/include/generated/asm/rwonce.h:1,
                 von ./include/linux/compiler.h:254,
                 von ./include/linux/string.h:5,
                 von ./include/linux/dma-mapping.h:6:
/var/lib/dkms/nvidia/390.154/build/nvidia/nv-acpi.c:262:50: Fehler: »struct acpi_device« hat kein Element namens »node«; meinten Sie »fwnode«?
  262 |             list_entry(node, struct acpi_device, node);
      |                                                  ^~~~
./include/linux/stddef.h:16:58: Anmerkung: in Definition des Makros »offsetof«
   16 | #define offsetof(TYPE, MEMBER)  __builtin_offsetof(TYPE, MEMBER)
      |                                                          ^~~~~~
./include/linux/list.h:520:9: Anmerkung: bei Substitution des Makros »container_of«
  520 |         container_of(ptr, type, member)
      |         ^~~~~~~~~~~~
/var/lib/dkms/nvidia/390.154/build/nvidia/nv-acpi.c:262:13: Anmerkung: bei Substitution des Makros »list_entry«
  262 |             list_entry(node, struct acpi_device, node);
      |             ^~~~~~~~~~
/var/lib/dkms/nvidia/390.154/build/nvidia/nv-acpi.c: In Funktion »nv_acpi_methods_uninit«:
/var/lib/dkms/nvidia/390.154/build/nvidia/nv-acpi.c:675:25: Warnung: Variable »device« wird nicht verwendet [-Wunused-variable]
  675 |     struct acpi_device *device = NULL;
      |                         ^~~~~~
/var/lib/dkms/nvidia/390.154/build/nvidia/nv-acpi.c: In Funktion »nv_acpi_ddc_method«:
/var/lib/dkms/nvidia/390.154/build/nvidia/nv-acpi.c:1267:43: Fehler: »struct acpi_device« hat kein Element namens »children«
 1267 |     list_for_each_safe(node, next, &device->children)
      |                                           ^~
./include/linux/list.h:643:21: Anmerkung: in Definition des Makros »list_for_each_safe«
  643 |         for (pos = (head)->next, n = pos->next; \
      |                     ^~~~
./include/linux/list.h:643:32: Warnung: linker Operand des Komma-Ausdrucks hat keinen Effekt [-Wunused-value]
  643 |         for (pos = (head)->next, n = pos->next; \
      |                                ^
/var/lib/dkms/nvidia/390.154/build/nvidia/nv-acpi.c:1267:5: Anmerkung: bei Substitution des Makros »list_for_each_safe«
 1267 |     list_for_each_safe(node, next, &device->children)
      |     ^~~~~~~~~~~~~~~~~~
/var/lib/dkms/nvidia/390.154/build/nvidia/nv-acpi.c:1267:43: Fehler: »struct acpi_device« hat kein Element namens »children«
 1267 |     list_for_each_safe(node, next, &device->children)
      |                                           ^~
./include/linux/list.h:644:34: Anmerkung: in Definition des Makros »list_for_each_safe«
  644 |              !list_is_head(pos, (head)); \
      |                                  ^~~~
/var/lib/dkms/nvidia/390.154/build/nvidia/nv-acpi.c:1270:50: Fehler: »struct acpi_device« hat kein Element namens »node«; meinten Sie »fwnode«?
 1270 |             list_entry(node, struct acpi_device, node);
      |                                                  ^~~~
./include/linux/build_bug.h:78:56: Anmerkung: in Definition des Makros »__static_assert«
   78 | #define __static_assert(expr, msg, ...) _Static_assert(expr, msg)
      |                                                        ^~~~
./include/linux/container_of.h:19:9: Anmerkung: bei Substitution des Makros »static_assert«
   19 |         static_assert(__same_type(*(ptr), ((type *)0)->member) ||       \
      |         ^~~~~~~~~~~~~
./include/linux/container_of.h:19:23: Anmerkung: bei Substitution des Makros »__same_type«
   19 |         static_assert(__same_type(*(ptr), ((type *)0)->member) ||       \
      |                       ^~~~~~~~~~~
./include/linux/list.h:520:9: Anmerkung: bei Substitution des Makros »container_of«
  520 |         container_of(ptr, type, member)
      |         ^~~~~~~~~~~~
/var/lib/dkms/nvidia/390.154/build/nvidia/nv-acpi.c:1270:13: Anmerkung: bei Substitution des Makros »list_entry«
 1270 |             list_entry(node, struct acpi_device, node);
      |             ^~~~~~~~~~
././include/linux/compiler_types.h:295:27: Fehler: Ausdruck in statischer Behauptung ist keine Ganzzahl
  295 | #define __same_type(a, b) __builtin_types_compatible_p(typeof(a), typeof(b))
      |                           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
./include/linux/build_bug.h:78:56: Anmerkung: in Definition des Makros »__static_assert«
   78 | #define __static_assert(expr, msg, ...) _Static_assert(expr, msg)
      |                                                        ^~~~
./include/linux/container_of.h:19:9: Anmerkung: bei Substitution des Makros »static_assert«
   19 |         static_assert(__same_type(*(ptr), ((type *)0)->member) ||       \
      |         ^~~~~~~~~~~~~
./include/linux/container_of.h:19:23: Anmerkung: bei Substitution des Makros »__same_type«
   19 |         static_assert(__same_type(*(ptr), ((type *)0)->member) ||       \
      |                       ^~~~~~~~~~~
./include/linux/list.h:520:9: Anmerkung: bei Substitution des Makros »container_of«
  520 |         container_of(ptr, type, member)
      |         ^~~~~~~~~~~~
/var/lib/dkms/nvidia/390.154/build/nvidia/nv-acpi.c:1270:13: Anmerkung: bei Substitution des Makros »list_entry«
 1270 |             list_entry(node, struct acpi_device, node);
      |             ^~~~~~~~~~
/var/lib/dkms/nvidia/390.154/build/nvidia/nv-acpi.c:1270:50: Fehler: »struct acpi_device« hat kein Element namens »node«; meinten Sie »fwnode«?
 1270 |             list_entry(node, struct acpi_device, node);
      |                                                  ^~~~
./include/linux/stddef.h:16:58: Anmerkung: in Definition des Makros »offsetof«
   16 | #define offsetof(TYPE, MEMBER)  __builtin_offsetof(TYPE, MEMBER)
      |                                                          ^~~~~~
./include/linux/list.h:520:9: Anmerkung: bei Substitution des Makros »container_of«
  520 |         container_of(ptr, type, member)
      |         ^~~~~~~~~~~~
/var/lib/dkms/nvidia/390.154/build/nvidia/nv-acpi.c:1270:13: Anmerkung: bei Substitution des Makros »list_entry«
 1270 |             list_entry(node, struct acpi_device, node);
      |             ^~~~~~~~~~
make[2]: *** [scripts/Makefile.build:249: /var/lib/dkms/nvidia/390.154/build/nvidia/nv-acpi.o] Fehler 1
make[2]: *** Es wird auf noch nicht beendete Prozesse gewartet....
make[1]: *** [Makefile:1852: /var/lib/dkms/nvidia/390.154/build] Fehler 2
make[1]: Verzeichnis „/usr/lib/modules/6.0.0-1-MANJARO/build“ wird verlassen
make: *** [Makefile:81: modules] Fehler 2

It should be fixed with nvidia-390xx-dkms 390.154-2 coming along shortly.

yes, all fine after update nvidia-390.154-2
ty

There was so issue with linux54 which should been fixed by now:


User philm created a snapshot of branch 'unstable' to 'testing'.

 - testing community x86_64:  12 new and 11 removed package(s)
 - testing core x86_64:  2 new and 2 removed package(s)
 - testing extra x86_64:  14 new and 14 removed package(s)

:: Different overlay package(s) in repository community x86_64

-------------------------------------------------------------------------------
                             PACKAGE              testing             unstable
-------------------------------------------------------------------------------
               tuxedo-control-center              1.1.7-1              1.1.8-1
                tuxedo-keyboard-dkms             3.0.10-2             3.0.11-1


:: Different sync package(s) in repository community x86_64

-------------------------------------------------------------------------------
                             PACKAGE              testing             unstable
-------------------------------------------------------------------------------
                         cargo-audit             0.17.0-1             0.17.2-1
                          diesel-cli              2.0.0-1              2.0.1-1
                                 gap             4.12.0-3             4.12.0-4
                             gap-doc             4.12.0-3             4.12.0-4
                        gap-packages             4.12.0-3             4.12.0-4
                       libimagequant              4.0.1-1              4.0.4-1
                              physfs              3.0.2-2              3.2.0-1
                    python-gitpython             3.1.27-1             3.1.28-1
                           terraform              1.3.1-1              1.3.2-1
                              hblock                    -              3.4.0-2


:: Different overlay package(s) in repository core x86_64

-------------------------------------------------------------------------------
                             PACKAGE              testing             unstable
-------------------------------------------------------------------------------
                             linux54            5.4.216-1            5.4.217-1
                     linux54-headers            5.4.216-1            5.4.217-1


:: Different overlay package(s) in repository extra x86_64

-------------------------------------------------------------------------------
                             PACKAGE              testing             unstable
-------------------------------------------------------------------------------
                   linux54-acpi_call             1.2.2-57             1.2.2-58
                    linux54-bbswitch              0.8-231              0.8-232
                 linux54-broadcom-wl     6.30.223.271-232     6.30.223.271-233
                 linux54-ndiswrapper             1.63-187             1.63-188
                linux54-nvidia-390xx            390.154-9           390.154-10
                linux54-nvidia-470xx         470.141.03-9        470.141.03-10
                    linux54-nvidiabl             0.88-231             0.88-232
                       linux54-r8168          8.050.03-11          8.050.03-12
                   linux54-rtl8723bu           20220818-5           20220818-6
                    linux54-tp_smapi             0.43-231             0.43-232
                 linux54-vhba-module          20211218-53          20211218-54
     linux54-virtualbox-host-modules             6.1.38-6             6.1.38-7
                         linux54-zfs              2.1.6-3              2.1.6-4


:: Different sync package(s) in repository extra x86_64

-------------------------------------------------------------------------------
                             PACKAGE              testing             unstable
-------------------------------------------------------------------------------
                             libcdio              2.1.0-2              2.1.0-3

I’m seeing this on kernel 6

journalctl -b -p err..alert
blacklist: Problem blacklisting hash (-13)
inxi
  Kernel: 6.0.0-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.0-x86_64
    root=UUID=4d0cf064-ff95-41b6-89c9-10164abe8954 ro apparmor=1
    security=apparmor resume=UUID=8f33ffd8-9ad7-4723-8b79-77ceb37f2c68
    udev.log_priority=3
  Desktop: KDE Plasma v: 5.25.5 tk: Qt v: 5.15.6 wm: kwin_x11 vt: 1
    dm: SDDM Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Desktop System: Micro-Star product: MS-7A37 v: 1.0
    serial: <superuser required>
  Mobo: Micro-Star model: B350M MORTAR (MS-7A37) v: 1.0
    serial: <superuser required> UEFI: American Megatrends LLC. v: 1.O6
    date: 07/13/2022
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse MX Master
    serial: <filter> charge: 55% (should be ignored) rechargeable: yes
    status: discharging
CPU:
  Info: model: AMD Ryzen 7 3700X bits: 64 type: MT MCP arch: Zen 2 gen: 3
    level: v3 built: 2020-22 process: TSMC n7 (7nm) family: 0x17 (23)
    model-id: 0x71 (113) stepping: 0 microcode: 0x8701021
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
    L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
    L3: 32 MiB desc: 2x16 MiB
  Speed (MHz): avg: 2528 high: 3699 min/max: 2200/4426 boost: enabled
    scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 3600 2: 2313
    3: 2200 4: 2461 5: 3699 6: 2200 7: 2200 8: 2200 9: 2200 10: 2200 11: 2200
    12: 2789 13: 2200 14: 3600 15: 2200 16: 2200 bogomips: 115255
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT enabled with STIBP
    protection
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, STIBP:
    always-on, RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GP104 [GeForce GTX 1070] vendor: eVga.com. driver: nvidia
    v: 515.76 alternate: nouveau,nvidia_drm non-free: 515.xx+ status: current
    (as of 2022-08) arch: Pascal code: GP10x process: TSMC 16nm
    built: 2016-21 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3
    speed: 8 GT/s bus-ID: 26:00.0 chip-ID: 10de:1b81 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.4 with: Xwayland v: 22.1.3
    compositor: kwin_x11 driver: X: loaded: nvidia gpu: nvidia display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 5120x1440 s-dpi: 122 s-size: 1066x302mm (41.97x11.89")
    s-diag: 1108mm (43.62")
  Monitor-1: DP-2 pos: primary,right res: 2560x1440 hz: 60 dpi: 123
    size: 527x296mm (20.75x11.65") diag: 604mm (23.8") modes: N/A
  Monitor-2: DP-4 pos: primary,left res: 2560x1440 hz: 60 dpi: 123
    size: 527x296mm (20.75x11.65") diag: 604mm (23.8") modes: N/A
  OpenGL: renderer: NVIDIA GeForce GTX 1070/PCIe/SSE2 v: 4.6.0 NVIDIA
    515.76 direct render: Yes
Audio:
  Device-1: NVIDIA GP104 High Definition Audio vendor: eVga.com.
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 26:00.1 chip-ID: 10de:10f0 class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 28:00.4 chip-ID: 1022:1487 class-ID: 0403
  Sound Server-1: ALSA v: k6.0.0-1-MANJARO running: yes
  Sound Server-2: PulseAudio v: 16.1 running: no
  Sound Server-3: PipeWire v: 0.3.58 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Micro-Star MSI driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: f000 bus-ID: 22:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp34s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 3.15 TiB used: 434.86 GiB (13.5%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Corsair model: Force MP510
    size: 894.25 GiB block-size: physical: 512 B logical: 512 B
    speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: ECFM22.5
    temp: 36.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: ST2000LM015-2E8174
    size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    type: HDD rpm: 5400 serial: <filter> rev: 0001 scheme: MBR
  ID-3: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 850 EVO 500GB
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: 2B6Q scheme: MBR
Partition:
  ID-1: / raw-size: 146.48 GiB size: 143.13 GiB (97.71%) used: 15.46 GiB
    (10.8%) fs: ext4 dev: /dev/nvme0n1p6 maj-min: 259:6
  ID-2: /boot/efi raw-size: 500 MiB size: 499 MiB (99.80%) used: 900 KiB
    (0.2%) fs: vfat dev: /dev/nvme0n1p5 maj-min: 259:5
Swap:
  Kernel: swappiness: 10 (default 60) cache-pressure: 75 (default 100)
  ID-1: swap-1 type: partition size: 3.91 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/nvme0n1p7 maj-min: 259:7
Sensors:
  System Temperatures: cpu: 29.0 C mobo: 32.0 C gpu: nvidia temp: 44 C
  Fan Speeds (RPM): fan-1: 0 fan-2: 1320 fan-3: 799 fan-4: 791 fan-5: 753
    gpu: nvidia fan: 0%
  Power: 12v: N/A 5v: N/A 3.3v: 3.33 vbat: 3.20
Info:
  Processes: 326 Uptime: 2m wakeups: 2 Memory: 31.27 GiB used: 2.57 GiB
  (8.2%) Init: systemd v: 251 default: graphical tool: systemctl Compilers:
  gcc: 12.2.0 clang: 14.0.6 Packages: pm: pacman pkgs: 1283 libs: 369
  tools: pamac Shell: Zsh v: 5.9 default: Bash v: 5.1.16 running-in: yakuake
  inxi: 3.3.21```

but i have just updated my UEFI also (cant belive i can now fit a 5700x to B350M motherboard).

the last post here fixes this “issue”, obviously back up your keys if you need them.
edit: looks like it might be my secure boot keys not being removed properly.

https://bbs.archlinux.org/viewtopic.php?id=278860

Maybe late to the party, but for MSI boards (mostly dealt w b450) there is an option to disable deafult keys filling after purge…

Settings>Advanced>Windows OS Configuration>Secure Boot>Key Management> Provision Factory Default Key Management < set to disabled