Is that a permanent solution? In the terminal, I tried…
set i915.enable_psr=0
…But for that to work, I had to restart Manjaro thereafter, and it only works when I type it in and restart.
I assume, in /etc/default/grub, there is a text file where I can edit GRUB_CMDLINE_LINUX="" to GRUB_CMDLINE_LINUX="i915.enable_psr=0", yes? I’ll find out when I boot up Manjaro again. My knowledge of Linux is nowhere close to that of Windows or Android.
I found the grub text file, made the change to GRUB_CMDLINE_LINUX="", then ran ‘sudo update-grub’ in the terminal. Unfortunately it didn’t work, unless GRUB_CMDLINE_LINUX="" appears more than once in that grub file and they need to be changed.
As I said before, I tried to paste the entire system info after running the command in the terminal, and this message board rejected it, interpreting some of the material within as links. Is there a way to work around that problem?
Never mind.
UPDATE: Here it is, in preformatted text:
Too many errors, could not resolve host, failed to synchronize all databases, invalid url for server.
Just a sample of the errors I got with this failed update. Neither kernel installed.
I must remind you that I have 2 operating systems on my laptop, on separate SSDs (Manjaro on Drive 0 and Windows 10, pre-installed, on drive 1). I wonder if the flickers are caused by the name I chose for my laptop in Manjaro. I have the same name for Windows 10. My Windows XP VM (in VMware Workstation) was flagged with “A duplicate name exists on the network”; same computer name as my main Win10 OS. I changed the name in my VM and the error disappeared.
And how do I get my Manjaro setup to detect my Wi-Fi signal? My Windows setup had no problem detecting multiple nearby Wi-Fi networks upon system installation. I had to use a USB-to-RJ45 Ethernet interface to get an Internet connection in Manjaro and install the OS.
I tried it with the network cable. I’ve been installing updates all along with the network cable because I can’t find the software to enable Wi-Fi in Manjaro and I don’t know the appropriate command for the terminal to search the repositories the Web.
Kernel 5.13 would not install in TTY2. I looked as if it had trouble finding the repositories there…
…But it had no trouble when I ran the same commands in the main OS. I used the terminal, of course…
[cookymonzta@LAPTOP-Q2DERVP7 ~]$ sudo mhwd-kernel --install linux513
[sudo] password for cookymonzta:
:: Synchronizing package databases...
core 169.4 KiB 376 KiB/s 00:00 [###################################################################] 100%
extra 1906.4 KiB 1294 KiB/s 00:01 [###################################################################] 100%
community 6.6 MiB 994 KiB/s 00:07 [###################################################################] 100%
multilib 176.2 KiB 1152 KiB/s 00:00 [###################################################################] 100%
resolving dependencies...
looking for conflicting packages...
Packages (1) linux513-5.13.11-1
Total Download Size: 96.55 MiB
Total Installed Size: 101.05 MiB
:: Proceed with installation? [Y/n] y
:: Retrieving packages...
linux513-5.13.11-1-x86_64 96.5 MiB 1085 KiB/s 01:31 [###################################################################] 100%
(1/1) checking keys in keyring [###################################################################] 100%
(1/1) checking package integrity [###################################################################] 100%
(1/1) loading package files [###################################################################] 100%
(1/1) checking for file conflicts [###################################################################] 100%
(1/1) checking available disk space [###################################################################] 100%
:: Processing package changes...
(1/1) installing linux513 [###################################################################] 100%
Optional dependencies for linux513
crda: to set the correct wireless channels of your country [installed]
:: Running post-transaction hooks...
(1/4) Arming ConditionNeedsUpdate...
(2/4) Updating module dependencies...
(3/4) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux513.preset: 'default'
-> -k /boot/vmlinuz-5.13-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.13-x86_64.img
==> Starting build: 5.13.11-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: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [resume]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.13-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux513.preset: 'fallback'
-> -k /boot/vmlinuz-5.13-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.13-x86_64-fallback.img -S autodetect
==> Starting build: 5.13.11-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [resume]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.13-x86_64-fallback.img
==> Image generation successful
(4/4) Updating Grub-Bootmenu
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.13-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.13-x86_64.img
Found initrd fallback image: /boot/initramfs-5.13-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.10-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.10-x86_64.img
Found initrd fallback image: /boot/initramfs-5.10-x86_64-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Found Windows Boot Manager on /dev/mmcblk0p1@/efi/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for UEFI Firmware Settings ...
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done
And with Kernel 5.13 installed, the system readout is as follows:
Unfortunately it still flickers, on and off, almost with every other reboot. I noticed on some occasions that it is stable when the clock is wrong (the OS has a habit of setting the clock back 4 hours early or the Windows clock 4 hours ahead).
I’ve removed just about every suggestion from the GRUB text file (it is now back to its original code), but left Kernel 5.13 in place.