Public bug reported:
Steps to reproduce:
pip3 install imagehash
Standard output:
ERROR: Command errored out with exit status 1:
command: /home/adam/.pyenv/versions/3.7.2/bin/python3.7 -c 'import sys,
setuptools, tokenize; sys.argv[0] =
Public bug reported:
I have a primary drive with not much free space, and a second drive
mounted that has a ton of space. Brasero keeps telling me that there's
no space, even though the image file I specified is on the disk with
terabytes free.
It allowed a copy when I moved files to the other
Sorry for the slow reply. Launchpad bug report messages seem to end up
in my junk folder. I currently don't use the pi at the moment so can't
test the patch immediately (are you aiming for the 20.04 release?). The
patch testing for the raspberry pi seems sensible. My only issue with
your patch
Easy fix that worked for me (on Mint 19.3): in the Driver Manager, an
older Nvidia driver was selected (390). I manually changed it to 435,
and on reboot I had my 2nd monitor back.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@David that is a problem caused by a package installed from the Ubuntu
Flavour Maker PPA. That ppa is maintained by Martin Wimpress and is used
by his version of Ubuntu Mate for the pi. He needs to solve it for
Ubuntu mate users. I suggest you raise a bug with him.
--
You received this bug
Somebody has already done it bug 1839054.
See https://ubuntu-mate.community/t/error-updating-ubuntu-mate-18-04-on-
pi-3b/20001
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761483
Title:
Firmware
Public bug reported:
Looking at the upstream calamares code there doesn't seem to be any
support for the arm architectures. Currently the bootloader code only
deals with i386/amd64. Whilst armhf can be a bit of a mess, I believe
there is now a consensus forming around grub on arm64/aarch64. It
Public bug reported:
Ubiquity currently does not support arm64
Attached is a (untested) patch that should add support.
** Affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Patch added: "ubiquity-diff.txt"
WiFi files are now included but have different names
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/?id=638a91ab5d066929d92c808e064c295a3ccab41d
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Linux-firmware now contains the NVRAM WiFi config files for the pi
3B/B+. See https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source
/linux-firmware/commit/?id=638a91ab5d066929d92c808e064c295a3ccab41d
The config files should now be removed from linux-firmware-raspi2.
**
I asked on the pi forum if they could help with the upstream bug report
https://www.raspberrypi.org/forums/viewtopic.php?f=66=233552 . I like
the pi, but the people that make it are obnoxious. They are not going
to help.
I posted some more patches from endless os in that thread.
--
You
** Summary changed:
- Enable v4l2 hardware accelerated video decode
+ Enable v4l2 hardware accelerated video decode for ARM devices
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799686
Title:
Apologies, it appears the filename path is missing from the patch. The
file is fstab.d/basic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770093
Title:
Ubiquity crashes with mount points that
Expanding comment #46 above...
On the raspi3 armhf image the config.txt in the unmounted /boot/firmware
is from livecd-rootfs (so doesn't have the correct fdt address). The
uboot.bin is the pi2 version.
Investigating where these files came from I noticed that both livecd-
rootfs and u-boot-rpi
New compute module released today. Flash-kernel/linux-firmware-raspi2
/linux-raspi2 will all need updating
--
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
The new Linux-firmware-raspi2 package contains kernel.img and
kernel7.img. These definitely shouldn't be included in the package.
--
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:
Inspecting the raspi3 images on another computer /boot/firmware is
populated with files. These do not match the files on the system-boot
partition. /boot/firmware should be empty until mounted as system-boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Where does the config.txt on the raspi3 images come from? It is not
livecd-rootfs.
--
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
Why are the raspi3 images 120MB bigger than the raspi2 images?
--
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
Lukasz, any plans to make Bluetooth work out of the box on the pi 3B/B+?
https://wiki.gentoo.org/wiki/Raspberry_Pi#Bluetooth
Could this be added to linux-firmware-raspi2 if that is now being used?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Linux-firmware-raspi2 forcefully sets config.txt to use 0x0200.
It is unnecessary to specify an address. See https://elinux.org/RPi_U-
Boot#Booting_from_an_SD_card
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Why not drop the boot.scr and use uboot.env like for the pi2 and the
pi2/3 gadget snaps?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811216
Title:
Support both armhf and arm64 raspi3 in
See bug 1791466
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811216
Title:
Support both armhf and arm64 raspi3 in flash-kernel
To manage notifications about this bug go to:
Bug 1811216 should be part of this bug.
--
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:
This changes the fdt_addr_r to 0x0300. Although the previous number
did not work, I believe the fdt_addr_r will have been changed by many
users. For example, Ryan Finnie's pi3 images have this set to
0x02008000. So this updated flash-kernel package will stop those
images/installations
To use arm64 the config.txt should contain arm_64bit=1. You've got
kernel=uboot.bin, but there is no uboot.bin on arm64. So what is
happening is the pi is falling back to searching for kernel8.img which
puts it automatically in arm64 mode. Yes it works, but only because the
config.txt contains
The config.txt generated by livecd-rootfs will not work on arm64 and the
fdt address conflicts with the bootscript address used with the pi3.
The beta image may boot okay, but that is only because so many mistakes
have been made across the pi packages that somehow, miraculously, it
actually works.
How on earth do they work as intended? You've ignored everything I've
written.
--
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
*** This bug is a duplicate of bug 1424201 ***
https://bugs.launchpad.net/bugs/1424201
My concern is that v4l2 will be forgotten about on the other bug report.
Va-api won't work on the pi.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
There is already a bug for vaapi - bug 1424201
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799686
Title:
Enable v4l2 hardware accelerated video decode
To manage notifications about this bug go
Vaapi is not the only mechanism that can be used for hardware decode.
V4l2 is an alternative, the one that will be used on the raspberry pi
with the open source vc4 driver (see blog posts
https://anholt.github.io/twivc4/2018/02/12/twiv/ ). I believe there is
some communication between chromium
See Gentoo pull request https://github.com/sakaki-/bcmrpi3-kernel-
bis/pull/3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797975
Title:
[armhf+raspi2] Error: Driver 'sdhost-bcm2835' is already
Same for 32 bit (bug 1710517).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779478
Title:
Kernel needs CONFIG_EFI_ARMSTUB=y to boot with grub
To manage notifications about this bug go to:
I reported this back in April (bug 1762835) and sent a patch to the
mailing list.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797975
Title:
[armhf+raspi2] Error: Driver 'sdhost-bcm2835' is
Public bug reported:
Currently it is not possible to install the raspi2 kernels in armhf and
arm64 on the raspberry pi 2/3 using the Debian-installer.
** Affects: base-installer (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
For completeness I'll point out some problems with flash-kernel The
3B+ is not supported (bug 1764491), nor is the CM3 or new 3A+. Whenever
a new revision of a board comes out it breaks.
The unforgiveable thing though is that the pi3 bootscript doesn't work (bug
1791466). This clearly has
Scrap the bit about it still not working. They probably didn't have the
fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806813
Title:
Add Pi Compute Module 3 Support
To manage notifications
With the server/cloud image you need ethernet connected on first boot.
Did you do that?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806813
Title:
Add Pi Compute Module 3 Support
To manage
Ethernet stopped working on the 3b+ due to an update to linux-raspi2
(bug 1797406). According to people on the Ubuntu mate forum it still
wasn't working correctly after the fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
But 1806813 contains results from some early testing.
--
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
That should of read bug 1806813 !
--
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:
Excellent! It's probably worth opening a new bug for those network
problems. That maybe is a problem with linux-raspi2. People with a 3b+
have had problems too, @ogra may know more.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also, raspi3-firmware was intended for use with the generic kernel. The
Debian generic kernel can be booted directly by the pi firmware (unlike
Ubuntu's which needs the assistance of u-boot/grub2). Consequently the
scripts expect different dtb names to those used by the linux-raspi2
kernel.
--
** Package changed: linux-raspi2 (Ubuntu) => flash-kernel (Ubuntu)
** Also affects: u-boot (Ubuntu)
Importance: Undecided
Status: New
** Also affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
Hi David, can you add your voice to bug 1805668 please? I expect the
beta image you are using uses the updated packages described in that bug
report.
I have no experience of the compute module, but I expect changes similar
to
It's not just me who thinks raspi3-firmware is "useless for many users"
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848101
** Bug watch added: Debian Bug tracker #848101
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848101
--
You received this bug notification because you are a
Ubuntu core and classic haven't been in sync for over a year. Linux-
firmware-raspi2 and the pi2 gadget use different versions of the
firmware. The pi2 v1.2 is closer to the pi3b than the original pi2.
Pegging the version of firmware for the pi2 makes little sense, stopping
usb booting for
To answer the description update by vorlon: The raspi3-firmware package
contains scripts that get run on a kernel update. This creates a new
config.txt and makes copies of kernel/dtb etc. Pretty certain this is
not how gadget snaps work (the firmware is obtained directly from git is
it not?).
Not sure why something that is clearly broken should be accepted?
--
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
If Ubuntu has to continue with u-boot (and I don't know why it does),
then it should implement the recent improvements i.e. you don't have to
specify a FDT address.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
One of the good things about Raspbian is it is able to run on any Pi.
You can take an SD card out of a Pi2 and it will work in a Pi3B+ or vice
versa. This is definitely what Ubuntu should be aiming for and it is
not hard to implement.
--
You received this bug notification because you are a
** Attachment added: "kern.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803206/+attachment/5218150/+files/kern.log
--
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:
I don't agree with the alterations to u-boot either. Arm64 doesn't need
to be called kernel8.img. The config.txt should be changed to tell the
pi's bootloader to expect aarch64. That way you can keep the uboot.bin
name and it is consistent between armhf and arm64.
This bug fails to address
The raspi3 additions to livecd-rootfs are just wrong. Is the use of
raspi3-firmware intentional?
If it is you've got pi2 and pi3 having completely different booting. The
config.txt created by livecd-rootfs will be overwritten by raspi3-firmware.
Which is not necessarily bad, because the
Recently the 3A+ was released https://www.raspberrypi.org/magpi/pi-3a-
interview/ so this should be supported too in any new builds.
--
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:
A bit confused by this bug. Ubuntu doesn't use raspi3-firmware. The
package used is linux-firmware-raspi2. I also think there is a high
regression potential with the uboot/firmware packages - what happens to
the people using Ryan Finnie's unofficial images?
Whilst an image that works with the
Public bug reported:
Using the generic arm64 kernel on my raspberry pi 3 it seems impossible
to use any apps that require 3D graphics. The X session crashes and a
reboot is needed to make it bootable again.
Inspecting dmesg, there are a lot of "failed to allocate CMA" messages.
Adding cma=256M
Public bug reported:
On armhf and arm64 U-boot is now capable of acting as UEFI. This is
great for devices such as the raspberry pi. However, grub-installer
currently always tries to update NVRAM which is non existent on the pi.
I was going to write a patch to add a preseedable option to
I've created a new bug to enable hardware acceleration via v4l2 codecs
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1799686
. Patches linked in the bug. This would give machines like the
Raspberry Pi hardware acceleration (although currently the kernel needs
patches too!).
--
Public bug reported:
Chromium browser is capable of decoding video via v4l2 codecs. ChromeOS
uses this on arm devices to achieve good performance.
Patches to enable this in Linux can be found here
https://github.com/Igalia/chromium/commit/58cca7607828bbadc4e154dde36e9c96469ba2d0
and here
Note it is currently not possible to boot the pi in Ubuntu armhf using
uefi. As previously mentioned, the generic kernel is missing pi
modules, and Linux-raspi2 is missing efi-stub
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1710517
--
You received this bug notification because
The current thinking seems to be that efi passes grub2 the flattened
device tree. The problem with this is that the dtb is not at all
stable. It is supposed to be independent of operating system, but there
are differences between the upstream and rpi foundation kernels. Grub2
or U-boot can give
I understand why flash-kernel was used, and in the past I myself have
suggested its use (https://bugs.launchpad.net/raspbian/+bug/1723203 ).
I've created installers for the pi using ubiquity (https://ubuntu-
mate.community/t/aarch64-on-raspberry-pi-2-rev-1-2-3b-3b/16853 ) and the
debian-installer,
Fedora now include the files
https://lists.fedoraproject.org/archives/list/a...@lists.fedoraproject.org/thread/ZLO7EAYV7VRX3ZBWJ2IBSMPDQNOMKXPD/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799443
I believe Ubuntu's pi core images also include the files.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799443
Title:
Firmware missing for Raspberry Pi 3
To manage notifications about this bug go
I guess this is fixed in 18.10 due to new firmware files.
I've created a new bug on the missing brcmfmac43430-sdio.txt file
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1799443 .
In there I've put a link to a discussion on the license.
--
You received this bug notification
Public bug reported:
The Raspberry Pi 3 WiFi does not work out of the box due to missing file
brcmfmac43430-sdio.txt. The pi's Bluetooth also doesn't work, also due
to missing firmware files.
Some discussion about licenses for these files is here
Oliver, thanks for the comment. Interesting that core has started to
implement this. I don't know much about snaps/gadgets.
The rpi2 u-boot is supposed to work with the pi3 if the pi3-miniuart-bt
overlay is used. However, the single u-boot file opensuse uses appears
to be doing something
Trying the latest opensuse armhf image, they seem to have a U-boot.bin
that works on the pi 2 and 3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765628
Title:
Create an image for all raspberry
This https://ubuntu-mate.community/t/aarch64-on-raspberry-pi-2-rev-1-2
-3b-3b/16853/37 is currently what you have to do to use the armhf
netboot installer on a pi 2/3B/3B+. The debian-installer has no
knowledge of the raspi2 kernel (you can't force it to install it), nor
does raspi2 have any
Just an aside, Debian uses the raspi3-firmware package to copy the
latest vmlinuz/initrd.img, but that has its problems too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764491
Title:
Missing
Yep, the use of U-boot/flash-kernel makes no sense to me. I did create
a bug to try and discuss options on how to remove U-boot - bug #1765628.
U-boot makes sense without flash-kernel copying vmlinuz/initrd.img, or
flash-kernel without U-boot, but using the two together as currently is
silly.
--
Yes I wrote the instructions on the raspberry pi wiki about how to boot
arm64. But I'm not talking about that here.
Raspberry pi is now supposedly fully supported in the Linux kernel -
https://www.omgubuntu.co.uk/2018/08/linux-4-18-kernel-release-features -
but I don't want to have to go through
Public bug reported:
I've been trying to boot the generic-lpae kernel on my pi 3B. I've
tried via U-boot and the pi's built in bootloader, but without success.
There seems to be something inherently missing from the kernel. There
are no bcm dtb files under armhf, but they are there for arm64.
@satmandu I'm guessing you are using an 'upstream' or a generic kernel.
They seem to have different dtb file names to the raspi2 kernels.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764491
Title:
Firefox working too on armhf xubuntu 18.04! (Pi 3B)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711337
Title:
Firefox crashes at start on armv7L after 55.0.1 update
To manage notifications
I see now my initial description was probably not the clearest since
there is an OEM user account. What I was referring to was the end user
setup.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
There are two stages to an OEM install; preparing the image for shipping
and the user first boot.
Preparing for shipping is fine, but when ubiquity runs on the user first
boot there is no /target as far as I'm aware. This is when ubiquity
creates a /target folder with the telemetry file in it.
Public bug reported:
Experimenting with an oem install, after the user setup and the
installation is complete there is a /target/var/log/installer/telemetry
file. This file location seems to be hard coded into ubiquity, but
there is no /target at the oem user setup stage.
This is using
This really needs fixing as it clearly is confusing users. It is a very
visible error message, especially if you boot with 'quite splash' as it
remains on the boot screen for quite a few seconds.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I sent the patch to the kernel mailing list back in April:
https://lists.ubuntu.com/archives/kernel-team/2018-April/091646.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762835
Title:
Nope, that's not it. Snippet from syslog:
Jan 28 16:15:44 xubuntu ubiquity: #!/bin/sh
Jan 28 16:15:44 xubuntu ubiquity:
Jan 28 16:15:44 xubuntu ubiquity: # Install Raspberry Pi firmware. Parts of
this have been stolen/adapted from flash-kernel-installer.
Jan 28 16:15:44 xubuntu ubiquity:
Jan
I think I've figured out what could be going wrong. The success_command
script is living on a fat formatted partition. This loses its
executable-ness. Copying it to tmp, and chmod +x'ing it maybe the
solution.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Hi, I'm using a custom script that is executed via preseeding
d-i ubiquity/success_command string
/cdrom/preseed/raspberry/success_command
I'd like the script to read some other preseeded values (d-i debian-
installer/add-kernel-opts), but if I place
.
Public bug reported:
Hi, I've used ubiquity as an installer for the Raspberry Pi 2/3. One of
the quirks of the Pi is its need for a FAT formatted boot partition.
The Pi packages (flash-kernel etc) expect this to be mounted at
/boot/firmware. However if I give ubiquity this mount point then it
Invalid. They are now contained in the linux-modules package. No pi2
though - is this correct?
** Changed in: linux-raspi2 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It should have the file bcm2710-rpi-3-b.dtb for the pi3. I would expect
it to also now have a file for the 3B+, and also maybe the pi2 since the
latest revisions are 64 bit too?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Bionic raspi2 64 bit seems to be shipping with the wrong dtb file. The
upstream device tree blob?
It fails to boot with the shipped dtb file. Even when I specify the
device_tree in the config.txt.
Copying the armhf dtb allows a successful boot.
** Affects: linux-raspi2
Public bug reported:
Currently (Xenial to Bionic) server images only run on the raspberry pi
2. This is due to the u-boot bootloader.
However it is possible to produce one image that runs on a pi 2 and 3.
Fedora arm 32 bit produce such an image. They make use of conditional
filters in the
I've created a new bug for the raspi2 server image - Bug #1765154
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566468
Title:
systemd-modules-load.service: Failing due to missing module 'ib_iser'
Public bug reported:
Booting the xenial and bionic raspi2 server images we have a rather
prominent and off putting systemd failure message.
systemd[1]: Failed to start Load Kernel Modules.
This is essentially Bug #1566468, except that seems to have been solved
for all the generic kernels. The
** Description changed:
The new Raspberry Pi 3B+ is missing from the flash-kernel database.
- Support has been added to the bionic kernel, so it would be great if the
- other packages could support it too.
+ Support has been added to the bionic raspi2 kernel, so it would be great
+ if the other
Raspbian dmesg
** Attachment added: "rasp-dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1762835/+attachment/5120090/+files/rasp-dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is the dmesg with the patched kernel (upstream mmc modules
removed).
** Attachment added: "ubuntu-patched-dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1762835/+attachment/5120013/+files/ubuntu-patched-dmesg.txt
--
You received this bug notification because you
Just for fun I did the reverse - i.e. downstream mmc modules removed and
upstream modules kept in. Note how confusing the mmc module messages are
in dmesg. It is impossible for the casual reader of the dmesg logs to
tell which mmc module are in use.
** Attachment added:
Public bug reported:
The new Raspberry Pi 3B+ is missing from the flash-kernel database.
Support has been added to the bionic kernel, so it would be great if the
other packages could support it too.
** Affects: flash-kernel (Ubuntu)
Importance: Undecided
Status: New
** Tags:
** Description changed:
+ SRU Justification
+
+ [Impact]
+
+ The Bionic Linux-raspi2 kernel has both the upstream and downstream pi
+ mmc modules enabled. Running the latest server image users can see this
+ error in dmesg:
+
+ Error: Driver 'sdhost-bcm2835' is already registered, aborting...
Attached is a config patch.
Is a device tree change needed too?
** Patch added: "mmc_config.patch"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1762835/+attachment/5111407/+files/mmc_config.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This is the Xenial config: It uses bcm2835 and bcm2835_sdhost which is a
mix of the upstream and downstream drivers.
CONFIG_MMC=y
CONFIG_MMC35240=m
CONFIG_MMC_ARMMMCI=y
CONFIG_MMC_BCM2835=y
CONFIG_MMC_BCM2835_DMA=y
CONFIG_MMC_BCM2835_PIO_DMA_BARRIER=2
CONFIG_MMC_BCM2835_SDHOST=y
Marking as invalid because on re-testing the server image I notice the
*2709*.bak is already in place.
** Changed in: flash-kernel (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
1 - 100 of 384 matches
Mail list logo
