Per coincidence, I worked on this same bug today, as I'm hoping to try
make use of the amdpro legacy OpenCL drivers, which will need amdgpu as
a base.
The issue is Ubuntu is providing newer kernel HWE stacks with amdgpu
driver modules, but failing to keep related Linux firmware packages up
to date
Another correction. For the one workaround, switching to discrete
graphics in the BIOS only seemed to get past the initial gnome login.
But resuming from DPMS off/suspend, the same error loop happens even
when hybrid graphics is disabled in the BIOS.
Even worse, seems hardware acceleration ends up
Here's the script I run to workaround the intital failure of gnome to
use the external display after unlocking or resuming from DPMS
suspend/off.
** Attachment added: "fix-hdmi-uhd.sh"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+attachment/5365719/+files/fix-hdmi-uhd.sh
--
Y
Apologies, continuing the comment above (mistakenly posted when adding
the log attachment). Let me retry.
Failure loop observed:
- Failed to blit shared framebuffer: EGL failed to allocate resources for the
requested operation.
- Failed to set CRTC mode 3840x2160: No such file or directory
To s
Hi, thanks to everyone, especially Daniel for unpacking this issue.
I have had a very similar issue, where gnome shell fails to run my
external 4K/UHD display at 60HZ and I see the following failure loop
triggered in `journalctl -b -p warning _COMM=gnome-shell`:
May 02 20:39:38 JNBA434499PLL gno
Apologises, I think I'm conflating a resume from hibernate issue vs a
resume from suspend issue, so the previous comment is probably not that
relevant.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
No sure if this will help, but there are plenty of debian bugs related
to this to check
If you are relying on the `resume=` kernel parameter with
/etc/default/grub, that might well be ignored. According to the message
below, there are various bugs in upstream debian (and I'm not sure if
Ubuntu pat
I too see this error for Seagate 'ST3500418AS' SATA drives via 88SE9123
PCIe SATA 6.0 Gb/s controller (Ubuntu 16.04.2, latest 4.8 Kernel)
```
exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
irq_stat 0x4001
failed command: SET FEATURES
cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 4
status: { D
It's still happening to me on 16.04 (Xenial), fully up to date.
@madbiologist, thanks, good to know where the cause might be.
Still, having to rebuild a kernel with one commit reverted is a fairly
cumbersome work-around and painful given fairly frequent kernel
updates...
As far as I can see, no
Notable upstream bugs with related issues
alegidly patched: https://bugzilla.kernel.org/show_bug.cgi?id=115771
maybe not patched yet: https://bugzilla.kernel.org/show_bug.cgi?id=93521
Workaround (to help other who find this bug)
Add `intel_pstate=disable` to `GRUB_CMDLINE_LINUX_DEFAULT` in
/etc/
Same, here, this message makes me fear that my system won't be able to
boot with the new kernel.
Setting up linux-signed-image-4.4.0-51-generic (4.4.0-51.72) ...
warning: file-aligned section .text extends beyond end of file
warning: checksum areas are greater than image size. Invalid section tabl
Update on the previous comment, I realised the issue was the the
partition where /var was mounted to hat nosuid set. Seems /var/lib/lxc
must allow for the suid bit to be set. The problem is that people often
have /home mounted with nosuid as a normal security precaution, so this
effects running unp
It also affected me on Ubuntu 16.04 LTS with /var/lib/lxc mount via
bind.
My original setup only had 8GB for /var, so a bind to directory in /home
was the custom hack I did to give lxc more space.
$ grep lxc /etc/fstab
/home/var/lib/lxc /var/lib/lxc nonebind
@Chistopher, thanks, the problem is now that my A15 bios can't even
enter setup mode or boot anything, so I'm not sure how to try flash the
most recent A16 version from (released just a month ago)? Searched the
laptop's manual, and no indication of any jumpers to clear/reset NVRAM
:-(
I agree and
*** This bug is a duplicate of bug 1082418 ***
https://bugs.launchpad.net/bugs/1082418
** This bug has been marked a duplicate of bug 1273060
[Fujitsu LIFEBOOK LH532 (UMA)] Ubuntu EFI install locks out firmware access
--
You received this bug notification because you are a member of Kerne
To summarise, there are at least two other related bug reports (which should
add motivation given the wider impact of the issue):
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082418
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1471380
--
You received this bug notification becaus
*** This bug is a duplicate of bug 1273060 ***
https://bugs.launchpad.net/bugs/1273060
** Changed in: linux (Ubuntu)
Status: Expired => Confirmed
** This bug has been marked a duplicate of bug 1273060
[Fujitsu LIFEBOOK LH532 (UMA)] Ubuntu EFI install locks out firmware access
--
Y
*** This bug is a duplicate of bug 1273060 ***
https://bugs.launchpad.net/bugs/1273060
** This bug has been marked a duplicate of bug 1273060
[Fujitsu LIFEBOOK LH532 (UMA)] Ubuntu EFI install locks out firmware access
--
You received this bug notification because you are a member of Kerne
And this bug isn't isolated to just to Fujitsu. The same thing just
happened to me with a Dell.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273060
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
This bug is high risk! It's effectively bricked a Dell Latitude E6540
:-(
My theory is that, somehow, the update caused a change to the firmware
NVRAM settings and boot entries for UEFI, and the Dell code can't handle
something unexpected. And after I've entered BIOS password, the firmware
code sa
20 matches
Mail list logo
