I also had this problem with VMWare and a 5.15.12 kernel, although
technically the kernel did boot because I could get kernel output and
log in over a serial console, it's just that VMWare showed a black
screen. The workaround described at
I'm not able to boot with the workaround provided in the final release
Jammy 22.04 or latest daily Ubuntu Jammy 22.04 ISO using VMWare
Technology Preview "Professional Version e.x.p (19431034)."
I've edited the grub config in the Ubuntu installer to include the
mentioned acpi=force option, but it
I am trying to _install_ Ubuntu 20.04 ARM on Tech preview 21H1 (build
#19431034) and "acpi=force" solution seems to have no effect. What I do: boot
from installation ISO. Press `e` in GRUB menu and add "acpi=force" (w/o quotes)
after "quiet splash" but before triple dash:
...
linux
Any news on this one? I can boot the Ubuntu Jammy desktop using acpi=force and
install the desktop.
However, on subsequent boots it hangs with the same error in spite of the
changed grub config.
Also, shutdown does not work at all. Ubuntu just hangs silently.
This is on VMware Fusion (latest
This can be the efifb regression Linus also encountered.
FWIW, the initial efifb runtime PM grabbing is written by me.
--
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/1953671
Title:
5.15
Michael,
Is it possible to perform git bisect to find the offending commit?
--
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/1953671
Title:
5.15 and 5.16 arm64 kernels fail to boot in
Hi there, VMware here...
We're able to repro this and have the following temporary workaround while we
figure out who's code needs adjusting:
We are able to boot by adding:
acpi=force
to: GRUB_CMDLINE_LINUX_DEFAULT
in: /etc/default/grub
Such that the full line reads:
This problem persists with both v5.15.11 and v5.16-rc6
--
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/1953671
Title:
5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion
Status in
I've just updated with the logs from:
apport-collect 1953671
Please note: these are gathered when using the 5.13.0-21-generic kernel.
However, VMWare Fusion requires at least 5.14, so I have been running
v5.14.21-051421-generic day-to-day, and only switched to 5.13.0-21 in
order to report these
apport information
** Description changed:
I am using VMWare Fusion Tech Preview on an Apple M1 Max MacBook Pro
per:
https://blogs.vmware.com/teamfusion/2021/09/fusion-for-m1-public-tech-
preview-now-available.html
I am successfully using the 5.14 kernel series (currently
I've tried to provide some information via:
$ sudo apport-collect -p linux-image-generic 1953671
If there is a better command I can run, please let me know.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected jammy third-party-packages uec-images
** Description changed:
I am using VMWare Fusion Tech Preview on an Apple M1 Max MacBook Pro
per:
https://blogs.vmware.com/teamfusion/2021/09/fusion-for-m1-public-tech-
preview-now-available.html
@Chris - understood. Per my most recent message, running apport-collect
triggers the following warning:
"It appears you are currently running a mainline kernel. It would be
better to report this bug upstream at http://bugzilla.kernel.org/ so
that the upstream kernel developers are aware of the
Can you please do a kernel bisection?
--
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/1953671
Title:
5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion
Status in linux package in
Without full package/release details, this bug is not likely to get much
attention until details have been provided (using apport tools).
Please run the apport-collect using the last kernel that booted; and
just note that it was run with the working kernel, and not the kernel
the bug report was
Per my comments in the issue description, I can't run apport-collect
because I can't boot the 5.15 or 5.16 kernels. And when I try to run it
for 5.14.21 it tells me I'm running a mainline kernel, despite having
installed the debs from https://kernel.ubuntu.com/~kernel-
ppa/mainline/v5.14.21/.
16 matches
Mail list logo
