All went well with my update (below). Great updated packages.
Question:
With the ongoing discussion on grub, how do i know whether my system is susceptible? Does this apply to all grub users? What are the potential consequences of not doing the upgrade? I have a luks encrypted system and would not want to reinstall given all the time it takes to tweak the configuration.
NOTE: Please make sure that if/when you attempt re-installing grub, that you have a bootable flash drive in case you end up with an unbootable system.
The grub re-install was not scripted probably because not everyone has grub setup the same way. There isn’t really a universal command for reinstalling grub exactly the way everyone has it. In this case it is better to let the end user take care of it per their configuration, than risk borking a lot of installs.
For example, I did the grub update initially with
sudo grub-install /dev/sdY
(specific to Legacy/BIOS systems; replace Y with actual device)
Only to have an unbootable system afterward. Turns out I had used GPT with Legacy/BIOS, and while my system had been working fine for years, apparently it wasn’t a supported configuration (it did not have a separate 8mb partition with the “bios_grub” flag).
To get my setup bootable again, I used gparted to:
shrink my boot partition by 8mb (this can be any partition within the first 2TB of space on the drive)
format the new 8mb space as “unformatted”
mark the 8mb partition with “bios_grub” flag
chroot into my system and run the grub-install command again.
@jim1112 i was in the same boat. Refer to the steps outlined in this post. If you still need help, create a support thread and link it here.
Only one issue related to backlight on kernel 5.8:
$ ls -la /sys/class/backlight/
total 0
drwxr-xr-x 2 root root 0 Aug 16 18:20 .
drwxr-xr-x 70 root root 0 Aug 16 18:20 ..
lrwxrwxrwx 1 root root 0 Aug 16 18:20 amdgpu_bl0 -> ../../devices/pci0000:00/0000:00:08.1/0000:04:00.0/backlight/amdgpu_bl0
$ systemctl status systemd-backlight@backlight\:amdgpu_bl0.service
● systemd-backlight@backlight:amdgpu_bl0.service - Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0
Loaded: loaded (/usr/lib/systemd/system/systemd-backlight@.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2020-08-16 18:20:20 BST; 13min ago
Docs: man:systemd-backlight@.service(8)
Process: 824 ExecStart=/usr/lib/systemd/systemd-backlight load backlight:amdgpu_bl0 (code=exited, status=1/FAILURE)
Main PID: 824 (code=exited, status=1/FAILURE)
Aug 16 18:20:20 my-pc systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0...
Aug 16 18:20:20 my-pc systemd-backlight[824]: amdgpu_bl0: Saved brightness 64000 too high; decreasing to 255.
Aug 16 18:20:20 my-pc systemd-backlight[824]: amdgpu_bl0: Failed to write system 'brightness' attribute: No such device or address
Aug 16 18:20:20 my-pc systemd[1]: systemd-backlight@backlight:amdgpu_bl0.service: Main process exited, code=exited, status=1/FAILURE
Aug 16 18:20:20 my-pc systemd[1]: systemd-backlight@backlight:amdgpu_bl0.service: Failed with result 'exit-code'.
Aug 16 18:20:20 my-pc systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0.
$ journalctl -b _PID=824
-- Logs begin at Tue 2019-11-12 20:32:42 GMT, end at Sun 2020-08-16 18:35:44 BST. --
Aug 16 18:20:20 my-pc systemd-backlight[824]: amdgpu_bl0: Saved brightness 64000 too high; decreasing to 255.
Aug 16 18:20:20 my-pc systemd-backlight[824]: amdgpu_bl0: Failed to write system 'brightness' attribute: No such device or address
As a consequence this message appears during startup…
Failed to start Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0.
Hi @jaroMAN. Neither do I Just run convert.lua conkyfile . Normally all will be fine after this . There could be some minor issues.
Conky-manager doesn’t work anymore. If I’m not mistaken, there is also a conky-manager2 (git) in the AUR [but it won’t compile. (Something with missing dependencies, but I didn’t have the time to look at it.]
Now i’m confused regarding this grub update note.
Do i have to do something before updating the system? If so, what and how exactly?
Or can i do the system update and then do the grub update?
Does the system reboot after update if i didn’t update grub before?
Me dumb, I was clicking on an optional stuff for conky-lua-nv. Now it installs, but it installs nothing… The conky executable doesn’t exist. It only install this :
Thanks Lunix, but didn’t help me all files including ones with .conf all report same error:
./convert.lua: line 6: syntax error near unexpected token `newline’
./convert.lua: line 6: ‘<! DOCTYPE html>’
Adding html tags dosn’t help LoL.
Looking at “conky-startup.sh” and no widgets enabled now.
ALSO running conky conky_file has a NEW error:
conky: error while loading shared libraries: liblua.so.5.3: cannot open shared object file: No such file or directory
So looking around, liblua.so.5.3 is only found in the timeshift snapshots.
And in /usr/lib it’s 5.1 !!!
Clearly not enough/any Manjaro testers use conky.
TOMORROW I’m going to timeshift back to pre-Sunday’s update and will start incremental updates (kernel, microcode, etc) until I find what’s messing up lua.
Just run convert.lua conkyfile . Normally all will be fine after this . There could be some minor issues.
