[Bug 1813623] Re: Failed to start LightDM on disco
https://prnt.sc/mdcy64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813623 Title: Failed to start LightDM on disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1813623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813623] [NEW] Failed to start LightDM on disco
Public bug reported: I installed Ubuntu 19.04 in VirtualBox using the net install ISO. I then installed a minimal XFCE4 desktop and LightDM using apt: sudo apt install xfce4 --no-install-recommends sudo apt install lightdm --no-install-recommends After rebooting, it hangs on the loading screen. I pressed CTRL + ALT + G and saw that systemd had tried to start LightDM several times but failed at every one. The boot process hangs on "A start job is running for Hold until boot process finishes up". The only way to solve this is by either reinstalling Ubuntu or chrooting into the installation from a live CD and removing the lightdm package. ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813623 Title: Failed to start LightDM on disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1813623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811706] Re: eval: en: not found
bump -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811706 Title: eval: en: not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1811706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811706] Re: eval: en: not found
bump -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811706 Title: eval: en: not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1811706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811706] Re: eval: en: not found
bump -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811706 Title: eval: en: not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1811706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812546] [NEW] raspi3-firmware overwrites u-boot in the beta server image
Public bug reported: I tried out the Ubuntu Server 18.04 ARM64 beta image on my Raspberry Pi 3 and when raspi3-firmware's script is run, the config.txt gets overwritten to use the Pi's built-in bootloader to boot the kernel and initramfs instead of u-boot. There are multiple solutions to this: *Stop using raspi3-firmware and start using u-boot. *Stop using u-boot in the server image and start using raspi3-firmware and the Pi's built-in bootloader. *Update raspi3-firmware so that if it detects a u-boot binary in /boot/firmware, it won't update the config.txt. *Enable CONFIG_DMA_CMA=y in the generic ARM64 kernel and start using that with GRUB2 and u-boot instead. ** Affects: raspi3-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812546 Title: raspi3-firmware overwrites u-boot in the beta server image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/raspi3-firmware/+bug/1812546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805668] Re: Building armhf and arm64 Raspberry Pi 3 images
I don't see the need for separate images for the Pi 2 and 3. I think that there should only be one image that should work on both the Pi 2 and 3. u-boot works on the Pi 3 if setup with rpi_3_defconfig (for 64-bit) or rpi_3_32b_config (for 32-bit). You can enable BCM2836 support (if setup with rpi_3_32b_config) and then compile. This results in one u-boot binary that works on both the Pi 2 and 3). raspi3-firmware is a script that gets run on every kernel update. It creates a new config.txt file so that the Pi will boot from the new kernel and initramfs. The problem is that it overwrites the existing config.txt instead of just overwriting the kernel and initramfs settings in config.txt. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805668 Title: Building armhf and arm64 Raspberry Pi 3 images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1805668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811706] [NEW] eval: en: not found
Public bug reported: I tried to create a minimal Ubuntu bionic arm64 installation using debootstrap that I would use to create a bootable Kubuntu 18.04 image for the Pi 3, but debootstrap seems to fail to configure keyboard- configuration, and therefore fails to install the Ubuntu base. Looking into the debootstrap logs, I get the error "eval: en: not found". I've searched Google for solutions but found nothing relevant. ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811706 Title: eval: en: not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1811706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805668] Re: Building armhf and arm64 Raspberry Pi 3 images
I suggest ditching u-boot or compiling it using rpi_3_32b_config and then enabling BCM2836 support in menuconfig. To boot the official server image on the Pi 3, you have to make a few tweaks first, which include disabling u-boot, updating the bootloader files, and adding additional firmware for WiFi to work. An official image with all of this done beforehand would be more simple. Considering that the original Pi 3 was released in 2016, Ubuntu Server should work on both the Pi 3B and 3B+/3A+ out of the box. It's a pretty easy thing to implement. First, either the linux-firmware-raspi2 or raspi3-firmware package should be dropped. We don't need two packages that contain the same files. Secondly, whichever package remains should be updated to include bootloader files compatible with the 3B+ and 3A+. Thirdly, the linux- raspi2 kernel should be updated to a version that is still receiving updates because the version included in bionic is past EOL. Fourth, compile future versions of the generic ARM64 kernel with CONFIG_DMA_CMA=y so that this kernel is actually usable on the Pi 3. See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803206. That way, people can create Ubuntu images using GRUB2, u-boot, and the generic kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805668 Title: Building armhf and arm64 Raspberry Pi 3 images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1805668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811196] [NEW] raspi3-firmware includes old versions of the bootloader in bionic
Public bug reported: raspi3-firmware still includes old versions of the Raspberry Pi bootloader (*.elf, *.dat, bootcode.bin). Since these files are from December 2017, Pi models that use the second revision of the BCM2837 SoC (BCM2837B0) do not boot using raspi3-firmware since the bootloader included in this package is incompatible with the new SoC. For these models to boot, newer bootloader files are needed. disco already has a raspi3-firmware package based on the latest bootloader files, so it shouldn't be too hard to implement these into bionic. ** Affects: raspi3-firmware (Ubuntu) Importance: Undecided Status: New ** Description changed: raspi3-firmware still includes old versions of the Raspberry Pi bootloader (*.elf, *.dat, bootcode.bin). Since these files are from December 2017, Pi models that use the second revision of the BCM2837 SoC (BCM2837B0) do not boot using raspi3-firmware since the bootloader included in this package is incompatible with the new SoC. - For the Pi 3B+ to boot, newer bootloader files are needed. disco already - has a raspi3-firmware package based on the latest bootloader files, so - it shouldn't be too hard to implement these into bionic. + For these models to boot, newer bootloader files are needed. disco + already has a raspi3-firmware package based on the latest bootloader + files, so it shouldn't be too hard to implement these into bionic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811196 Title: raspi3-firmware includes old versions of the bootloader in bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/raspi3-firmware/+bug/1811196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811195] [NEW] Kernel in bionic hasn't received updates since April 2018 and is based on an EOL release of the Linux kernel
Public bug reported: In bionic and bionic-updates, the linux-raspi2 kernel hasn't received any updates since April 2018 and is based on Linux kernel 4.15, which is now past End of Life. This means it doesn't include the latest security patches and bug fixes. cosmic and cosmic-updates have a newer version of the linux-raspi2 kernel (4.18), but this has also reached End of Life. The linux-raspi2 kernel should be updated alongside the generic kernels, or should at least be based on a recent LTS version that is still receiving updates. ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811195 Title: Kernel in bionic hasn't received updates since April 2018 and is based on an EOL release of the Linux kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1811195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803206] Re: Please enable CONFIG_DMA_CMA=y on arm64
Same issue here. Apps like Chromium freeze the Pi, and the display output also goes off screen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803206 Title: Please enable CONFIG_DMA_CMA=y on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
