Open Phundrak opened 2 years ago
@Phundrak thank you for raising this detailed issue. I had the same issue with my archlinux install with my gaze15 with Nvidia 1650. I found a workaround that worked for me based on this stackoverflow answer: https://stackoverflow.com/a/49138256
I worked around the problem by setting the
iomem
Kernelparameter torelaxed
via Grub:
I have systemd-boot instead of grub so what I did in my /boot/loader/entries/Arch.conf
was add the iomem=relaxed
in my options, e.g
title Arch
linux /vmlinuz-linux
options root=/dev/vg-main/root iomem=relaxed ...
...
AFAIU the culprit is the mmap
done to /dev/mem
as done here: https://github.com/pop-os/system76-firmware/blob/master/src/sideband.rs#L28. I don't have the low-level expertise to know what exactly is done here, but maybe there is a different way to achieve the same without this iomem=relaxed
option but that would be worthy to have it's own issue.
My only question here, and maybe @ahoneybun (from System76 support-team) can chip-in here, why is the latest available firmware version of the gaze15 is 2021-07-20_93c2809
, I can see that there are more recent versions here like 2022-02-15
.
@GerardoGR the firmware version on that page does not reflect the latest for any model. The latest version will be shown in the Settings -> Firmware or the CLI tool.
@ahoneybun thank you for the clarification!
@Phundrak thank you for raising this detailed issue. I had the same issue with my archlinux install with my gaze15 with Nvidia 1650. I found a workaround that worked for me based on this stackoverflow answer: stackoverflow.com/a/49138256
I worked around the problem by setting the
iomem
Kernelparameter torelaxed
via Grub:I have systemd-boot instead of grub so what I did in my
/boot/loader/entries/Arch.conf
was add theiomem=relaxed
in my options, e.gtitle Arch linux /vmlinuz-linux options root=/dev/vg-main/root iomem=relaxed ... ...
It seems this was the reason for the error I was getting when running system76-firmware-cli
, this time it did schedule the firmware update, and it appeared to have updated the firmware successfully, but I’m still stuck with the proprietary firmware.
Should I make a separate issue, or should I post relevant logs here? (In any case, is there any log file I should look for or are screen photos alright?)
Distribution (run
cat /etc/os-release
):Related Application and/or Package Version:
Issue/Bug Description: When I try to schedule an installation of a firmware, be it the open or the proprietary firmware, I get the following error message:
This happens whether the argument
--open
or--proprietary
are passed, even when only executingsudo system76-firmware-cli schedule
.Steps to reproduce (if you know):
Expected behavior: I assume
system76-firmware-cli
should return a positive message about successfully scheduling the firmware upgrade.Other Notes: The System76 packages that are installed on my Gazelle are the two packages mentioned above, as well as aur/system76-dkms. The service
system76-firmware-daemon.service
is enabled and running:The precise model is a 17″ gaze15 with an Nvidia 1650 Ti.