Installed the released kernel now available from updates. All works as
expected.
The HWE 22.10 kernel also works in 22.04.2.
The 22.04.2 ISO installer still has a 5.19.0-32 kernel, though. It
exhibits the blank screen issue when choosing the "Ubuntu Server with
HWE kernel" installer option. I
Thanks Matthew. I was erring on the side of caution as it was easy for
me to at least give that variant a whirl on my trusty Jammy VM. I'll
definitely take your lead on the need for future testing.
Looking forward to release next week. I'll update you on my experiences
- but I suspect that it'll
Apologies for the typo - I meant the linux-nvidia-5.19/5.19.0-1014.14
kernel in -proposed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2007001
Title:
vmwgfx fails to reserve graphics
I can verify that the 5.10.0-1014 kernel in -proposed does boot on a
VMware Fusion VM running Jammy aarch64, and that the console appears as
expected. I'm hesitant to change the tag to verification-done-jammy
since I don't have anything nVidia on arm64. I can do that if my testing
meets what
Matthew,
I installed the 5.19.0-44.45 kernel from -proposed, and the console now
appears. It does seem to solve the problem.
dmesg reports:
[9.808628] vmwgfx :00:0f.0: [drm] Register MMIO at 0x0x3d00
size is 4096 kiB
[9.808637] vmwgfx :00:0f.0: [drm] VRAM at
Whatever patch series is needed does seem to be included in Linus' 5.19
tree as the mainline kernel 5.19.17 (supposedly built from Linus'
sources) does not have this issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
I'm not an Ubuntu kernel engineer, so I can't help identify the offending
commit.
What I do see is the following in dmesg:
[ 11.135360] vmwgfx :00:0f.0: BAR 2: can't reserve [mem
0x7000-0x77ff 64bit pref]
[ 11.135366] vmwgfx: probe of :00:0f.0 failed with error -16
And a
Kernel logging shows that the vmwgfx driver encounters an error when
loading. The error indicates that a memory range could not be acquired
by the driver. The error is eerily similar to
https://bugzilla.kernel.org/show_bug.cgi?id=215678 which was fixed in
kernel source in 5.19.
The behavior seen
This same issue impacts Ubuntu 22.04.2 HWE 5.19.0-32 kernels on aarch64.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2007001
Title:
Blank console display with aarch64 kernel
** Summary changed:
- Blank console display with aarch64 kernel 5.19.0-31 aarch64
+ Blank console display with aarch64 kernel 5.19.0-31
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Upgraded the kernel on 22.10 aarch64 (running in a VM on VMware Fusion
13.0.1 on Apple Silicon_ from 5.19.0-29 to 5.19.0-31. After the upgrade
and after rebooting the VM no text or graphical console appears on the
VM.
The VM is running and can be accessed through SSH.
11 matches
Mail list logo
