Solution taken from: https://askubuntu.com/questions/1060245/what-do-these-ata-error-messages-mean
==> add to: GRUB_CMDLINE_LINUX_DEFAULT new entry: “libata.force=noncq”
EDIT: please look for:
2-EDIT: problem has gone with kernl-version 5.15.2-2
There’s an nvidia-fake-powerd package in the AUR now, built from those instructions.
I think it should go without saying, but use at your own discretion! Used with 495xx drivers.
Nvidia GT730 Geforce not longer working after update (unstable) 07.11.2021.
Error: “Driver doesnot support your GT730”
SOLUTION:
in GRUB press “E” and add to bootoptions: 3 nomodeset
Boot (F10) => login prompt => login and type:
After updates of btrfs-progs-5.15-1, harfbuzz-3.1.1-1. harfbuzz-icu-3.1.1-1, and lib32-harfbuzz-3.1.1-1
==> Building image from preset: /etc/mkinitcpio.d/linux514.preset: 'default'
-> -k /boot/vmlinuz-5.14-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.14-x86_64.img
==> ERROR: '/lib/modules/5.14.17-1-MANJARO' is not a valid kernel module directory
==> Building image from preset: /etc/mkinitcpio.d/linux514.preset: 'fallback'
-> -k /boot/vmlinuz-5.14-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.14-x86_64-fallback.img -S autodetect
==> ERROR: '/lib/modules/5.14.17-1-MANJARO' is not a valid kernel module directory
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'default'
-> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64.img
==> Starting build: 5.15.1-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [mdadm_udev]
Custom /etc/mdadm.conf file will be used in initramfs for assembling arrays.
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.15-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'fallback'
-> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64-fallback.img -S autodetect
==> Starting build: 5.15.1-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [mdadm_udev]
Custom /etc/mdadm.conf file will be used in initramfs for assembling arrays.
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.15-x86_64-fallback.img
==> Image generation successful
error: command failed to execute correctly
Edit: Something had nuked /usr/lib/modules/5.14.17-1-MANJARO entirely…
I uninstalled and reinstalled linux514, and the folder and its contents are back.
I’m getting a strange update issue that sounds like it would be system-breaking, as of just now. I declined, of course. What should I do? Here’s what I saw in my terminal:
[alex@alex-pc ~]$ sudo pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
:: xf86-input-elographics and xorg-server are in conflict. Remove xorg-server? [y/N] N
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: xf86-input-elographics and xorg-server are in conflict (xorg-server<21.1.1)
[alex@alex-pc ~]$
After the last update (Plasma 5.23.3) Octopi fails to start with the following error:
octopi: error while loading shared libraries: libqtermwidget5.so.0: cannot open shared object file: No such file or directory
UPD: sudo ln -s /lib/libqtermwidget5.so.1.0.0 /lib/libqtermwidget5.so.0 worked for now. I know it’s a workaround but I don’t care much as I use Octopi only for ez browsing of packages anyway.
Latest xorg-server update to 21.1.1-2 can cause some “fun” with scaling on plasma. I had to force the old default of 96dpi to reduce huge icons and fonts to proper size again. Plasma scaling was set to 100% at all times.
Temporarily ignore the update for mhwd-nvidia-470xx. They’re only database files and it appears you don’t have the NVIDIA 470 driver installed, anyway. I’ll look at it tomorrow.
Since last Update (09.November2021)
GNOME boots into Wayland, although “X-11” is choosen (= target wanted).
Automatic login, entry “Gnome on xorg” selected.
Manual login into x-org works, if switched from “Gnome on xorg” to “Gnome”
and back to “Gnome on xorg”. Does not survive reboot…
Simple solution:
edit: /etc/gdm/custom and uncheck “WaylandEnable=false”
NO really a solution, only workaround.
Whats wrong with the Tigers??