[Bug 1845347] [NEW] Lenovo Yoga C630 not supported in Ubuntu
Public bug reported: Support for the Lenovo Yoga C630 was added to mainline in v5.4. Ubuntu Eoan will be released based on v5.3, thus the latest release will not boot. This would be a shame, as one of the first laptops based on AArch64 it's a ground breaking piece of H/W. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845347 Title: Lenovo Yoga C630 not supported in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839317] Re: Grub fails to chainload the Windows Boot Manager
With `set debug="chain,secureboot,dl"` added to the Grub menu entry, we get a flash of: SecureBoot: 0 SetupMode: 0 linuxefi_secure_validate: 1 No shimlock protocol loader/efi/chainloader: Secure boot is not enabled Looks like Grub is insisting on Secure Boot, which we need to disable in order to boot Linux. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839317 Title: Grub fails to chainload the Windows Boot Manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1839317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839317] Re: Grub fails to chainload the Windows Boot Manager
I should add that I experienced this on an AArch64 platform. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839317 Title: Grub fails to chainload the Windows Boot Manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1839317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839317] [NEW] Grub fails to chainload the Windows Boot Manager
Public bug reported: After an update to 2.04 Grub fails to chainload into Windows. When selecting the menu item to boot into the Windows Boot Manager, the menu flashes and returns. When trying to chainload/boot via the Grub command line, nothing happens and the prompt reappears. When using the same commands in an earlier version (on a bootable USB stick) Windows sparks into life. ** Affects: grub (Ubuntu) Importance: Undecided Status: New ** Package changed: ubuntu => grub (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839317 Title: Grub fails to chainload the Windows Boot Manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub/+bug/1839317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819442] [NEW] Cannot boot installer on platforms requiring Device Tree
Private bug reported:
In the past, when booting Linux on non-(x84_64|i386) machines, it was a
requirement to configure and build Linux kernels tailored specifically
for a particular device. Now, after many efforts ("one image to rule
them all" and the like) to unify and consolidate vendor fragmentation,
it is now possible to boot Single Board Computers (SBCs) of similar core
architectures with one single binary image.
In order to make this possible Linux is provided with a description of
the hardware it is expected to operate on. There are currently two main
technologies which provide these functionality; Advanced Configuration
and Power Interface (ACPI) and Device Tree (DT). This report only deals
with Device Tree (DT).
In an ideal world firmware installed onto a device would be readily
upgradable and thus provide Linux with an up-to-date hardware
description that it can work with. However, there are some devices
which do not contain either capable or upgradable (or both) firmware, so
this information has to be sought from elsewhere.
The kernel packages provided by the Ubuntu build system do contain pre-
compiled Device Tree Binaries (DTBs) for currently supported hardware,
however these do not make it into the Ubuntu Installers. Instead only a
single kernel binary exists which expects to be informed of platform
specifics via ACPI tables provided by the platform's firmware. This
means that many devices which could easily be supported by the Ubuntu
Installer, are not.
There are a couple of ideas which we'd like to put forward to start the
conversation off:
1. Place all supported DTBs into the installer
2. Allow for a small writable partition on the install media for a user to
place a DTB
3. Enable Grub to be able to pick a DTB from a menu at boot time
At worst case, as long as the DTBs find their way into the installer a
user can manually add a 'devicetree' (similar to 'linux' and 'initrd')
entry to the Grub menuentry, which would also achieve the aim.
Any help to boot such devices would be gratefully received.
** Affects: debian-installer (Ubuntu)
Importance: Undecided
Status: Invalid
** Information type changed from Public to Private
** Changed in: debian-installer (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819442
Title:
Cannot boot installer on platforms requiring Device Tree
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1819442/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
