I can confirm that downgrade to bios 1.13 definitively solves freezing
problem (was drastic on 1.18) and also grub slowness. After revert to
1.13, everything is now super stable.
Firmware downgrade, though, is not straightforward, here is procedure
This seems to be finally fixed by 1.15 firmware on Acer A315 41G.
Everything works, can boot without kernel params, suspend and function
keys works and powertop is down to ~7W idle (used to be ~14w) with 3+
hours of battery time.
GRUB is slow, but it is just a minor annoyance.
--
You received
After some more testing I found that these params are enough for me to
boot properly on A315-41G, bios 1.13, ubuntu 18.04, kernel 4.18, uefi,
secure boot:
"mem_encrypt=off ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2
rcu_nocbs=0-7 idle=nomwait acpi_enforce_resources=lax"
--
You received this
I haven't been able to boot with no params with 1.13. bios, but now I
can make it work with:
"text radeon.modeset=0 amdgpu.runpm=0 mem_encrypt=off
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 rcu_nocbs=0-7 idle=nomwait
acpi_enforce_resources=lax"
With these params everything works fine - gpu,
... 4.18 hwe kernel with hwe stack on ubuntu 18.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776563
Title:
Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
load, kernel
Yes, I tried:
"text ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 radeon.modeset=0
amdgpu.runpm=0"
"text ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 clocksource=hpet
iommu=on amd_iommu=on amdgpu.dc=1"
"idle=nomwait iommu=pt amd_iommu=on rcu_nocbs=0-7 pcie-aspm=off
ivrs_ioapic[4]=00:14.0
I can't make gpu and suspend work at the same time on Acer A315 41G R6IM
with Ryzen 2500U and Radeon 535.
If I use pci=noacpi gpu works fine, but laptop hangs on suspend, if I
use ivrs_ioapic... suspend works fine but with no 2d gpu acceleration -
everything works sluggish, very high cpu on
*** This bug is a duplicate of bug 1718658 ***
https://bugs.launchpad.net/bugs/1718658
** This bug has been marked a duplicate of bug 1718658
ecryptfs-mount-private fails to initialize ecryptfs keys
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This workaround might do the trick:
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726873
Title:
mount.ecryptfs_private can't
This workaround might do the trick:
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723826
Title:
Regression in
Still happening in 17.10... Shoud we report this to nouveau bug list ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641919
Title:
hibernation has stopped working in 16.10 Yakkety Yak
To manage
Something to do with this one, perhaps (systemd regression) ?
https://bugs.archlinux.org/task/55943
https://bbs.archlinux.org/viewtopic.php?id=230834
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Something to do with this one, perhaps (systemd regression) ?
https://bugs.archlinux.org/task/55943
https://bbs.archlinux.org/viewtopic.php?id=230834
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is a nouveau issue. Unload nouveau and hibernation start working
normally again.
Ctrl+Alt+F1
sudo service lightdm stop
sudo modprobe -r nouveau
sudo service lightdm start
Btw, how is it possible that system works completely normal after unloading
nouveau ?
Is it safe to do apt-get remove
Still persists for me
Linux laptop 4.8.0-34-generic #36-Ubuntu SMP Wed Dec 21 17:24:18 UTC
2016 x86_64 x86_64 x86_64 GNU/Linux
It goes like this:
fresh boot ok
sudo pm-hibernate ok
boot from hibernate ... everything seems ok
second sudo pm-hibernate does this:
Jan 19 16:38:03
Sorry I'm an idiot, I changed status to Fix Released while browsing. How
the f**k am I alllowed to change this status, anyway ?
Plese revert to Confirmed
** Changed in: gvfs (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
16 matches
Mail list logo
