Disregard my issue with my second machine, it didn't have the 'UUID='
part in /etc/default/grub. Adding that solved the issues with that
machine as well. So definite +1 solved for me.
That does lead to the question, why doesn't forgetting to add 'UUID='
give a better error message, and instead giv
actually, I jumped the gun on my 2nd machine which is a laptop. It's
showing a completely wrong major/minor of: 2623:602885, the
resume_offset in /sys/power is the same as my grub/cmdline though. My
major/minor should be 259:1
--
You received this bug notification because you are a member of Ubun
enabled proposed, but the update didn't come automatically. Manually
selected the newer version with aptitude. Can confirm this works on 2
machines now. Awesome! But what a regression in the first place? I had
to search pretty hard to find this.
--
You received this bug notification because you a
This was a clear regression introduced in:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/noble/commit/?h=master-
next&id=c30411266fd67ea3c02a05c157231654d5a3bdc9
Fixed in: https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/unstable/commit/?id=3c2ea5ec1d86d073
It was solved, yet I am now on kernel 5.4.0-43 and I am hitting this now
again since a week when using Jetbrains products. Clearly a regression,
how could this 've happened. The linux-image* package changelog is
pretty much worthless to investigate this.
--
You received this bug notification beca
You still can't edit comments on LP :S?
I am running kernel 5.4.0-42 instead of the earlier mentioned 5.4.0-43
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872001
Title:
5.3.0-46-generic - i915 -
this change, introduced way after the freezes in march, was really
aggravating tbh. Our automated deploys were broken on the day of the
launch as we had to hotfix the netboot url first.
This was poorly communicated for such an important change which impact
all parties, but not restricted to, using
#57 this works.
Hard to install on 18.04 though, you need the headers package (linux-
headers-5.3.0-48_5.3.0-48.41_all.deb) from eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872001
Title:
5.
I can confirm it works:
- Tested with Qemu, BIOS (not uefi)
- 2 NVMe devices, each:
- GPT
- 1 biosgrub partition
- 2x raid
2x Raid1 partitions, for '/' and '/boot'.
If actual hardware test is needed, please let me know.
--
You received this bug notification because you are a member of Ub
@mathieu, I have to see if there's time at work to do this. Fyi, when I was
hit with this bug, I debugged this further with qemu which can emulate nvme
devices pretty easily.
On Mon, Jul 16, 2018, 19:26 Mathieu Trudel-Lapierre
wrote:
> @Hans,
>
> Could you help verifying that this fix is working
@mathieu, I have to see if there's time at work to do this. Fyi, when I
was hit with this bug, I debugged this further with qemu which can
emulate nvme devices pretty easily.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
** Patch added: "pc-mdadm-nvme.diff"
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1771845/+attachment/5140996/+files/pc-mdadm-nvme.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
12 matches
Mail list logo
