** Changed in: flash-kernel (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863145
Title:
arm64 cloud image contains flash-kernel which leads to apt
On Wed, 4 Mar 2020 at 01:15, Steve Langasek
wrote:
> Why is the default.plymouth alternative not set up on the rpi images?
> Are no theme packages installed?
>
The plymouth-theme-ubuntu-text package is installed, but that doesn't seem
to provide any "alternative"; i.e. update-alternatives --quer
Public bug reported:
In the fix for LP: #1864586 the following change was made:
THEME_PATH="$(update-alternatives --query default.plymouth 2>/dev/null | sed
-e '/^Value:/!d' -e 's/^Value: \(.*\)/\1/')"
+IMAGE_PATH=$(grep "ImageDir *= *" ${THEME_PATH} | sed 's/ImageDir *= *//')
THEME="$(basenam
> Perhaps we should test this on 19.10.1 so we aren't adding the
additional variable of running Focal.
I've added an Eoan version of the package to the same PPA
(https://launchpad.net/~waveform/+archive/ubuntu/firmware/+packages).
--
You received this bug notification because you are a member of
Some test packages for focal and bionic are available from the following
PPA:
https://launchpad.net/~waveform/+archive/ubuntu/flash-kernel/+packages
The relevant branches are:
https://code.launchpad.net/~waveform/ubuntu/+source/flash-kernel/+git
/flash-kernel/+ref/no-lxc-focal
https://code.laun
ckage upgrade which results in all sorts of fun with u-boot and the
migration of boot configurations on pi for the .4 release).
I'll add a check to ensure flash-kernel dies quietly in the case it
finds itself in a container.
** Changed in: flash-kernel (Ubuntu)
Assignee: (unassigned) =>
A package with the latest firmware is available from the following PPA:
https://launchpad.net/~waveform/+archive/ubuntu/firmware/+packages
This package includes diversions for the following files (which are also
present in linux-firmware):
/lib/firmware/brcm/brcmfmac43455-sdio.bin
/lib/firmware/
A package with the latest firmware is available from the following PPA:
https://launchpad.net/~waveform/+archive/ubuntu/firmware/+packages
I've now tested this booting and operating wifi on a 3B+ and a 4B
against "classic" 2.4GHz wifi, and 5GHz wifi but only 802.11n (as that's
all I've got locall
** Description changed:
Impact
==
Under most circumstances, the impact is minimal (a few extra redundant
comment lines in apt sources. However, if users are automating source
removal / addition on a machine (as in comment 11), there is the
potential to wind up with an excessivel
@juergh given the Pi 3A+, 3B+, and 4B share the same wifi chipset (but
not the 3B) I'd expect similar behaviour across those three models, if
indeed the firmware is the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
** Changed in: linux-firmware-raspi2 (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848247
Title:
3A+ boot failure on Eoan
To manage notifications a
** Changed in: linux-raspi2 (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847596
Title:
rpi3b+: corrupted screen on hdmi
To manage notificatio
** Description changed:
[Impact]
In version 3.98ubuntu10 of flash-kernel (f-k henceforth), when both f-k
and the kernel are upgraded in the same cycle, depending on the ordering
of dpkg trigger execution, f-k may find the content of /boot
"inconsistent" causing it to fail and exit wit
** Description changed:
+ Impact
+ ==
+
+ Under most circumstances, the impact is minimal (a few extra redundant
+ comment lines in apt sources. However, if users are automating source
+ removal / addition on a machine (as in comment 11), there is the
+ potential to wind up with an excessivel
** Description changed:
[Impact]
In version 3.98ubuntu10 of flash-kernel (f-k henceforth), when both f-k
and the kernel are upgraded in the same cycle, depending on the ordering
of dpkg trigger execution, f-k may find the content of /boot
"inconsistent" causing it to fail and exit wit
Public bug reported:
In version 3.98ubuntu10 of flash-kernel (f-k henceforth), when both f-k
and the kernel are upgraded in the same cycle, depending on the ordering
of dpkg trigger execution, f-k may find the content of /boot
"inconsistent" causing it to fail and exit with code 2:
ubuntu@ubuntu:
After a bit more experimentation, I've found that only the first part of
the workaround mentioned in the description (comment #43 from LP:
#1854798), namely adding the i8042.nopnp option to the kernel command
line, is necessary to work around the issue.
--
You received this bug notification becau
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1860791/+attachment/5322873/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860791
Title:
Sy
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1860791/+attachment/5322874/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860791
Ti
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1860791/+attachment/5322861/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860791
Title:
Synapt
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1860791/+attachment/5322863/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860791
Title:
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1860791/+attachment/5322871/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860791
Titl
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1860791/+attachment/5322865/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860791
Title:
Syna
Above logs collected after reverting the fix mentioned in the
description (so the logs should represent the "broken" state rather than
the "worked around" state).
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member o
apport information
** Tags added: apport-collected bionic
** Description changed:
On my Acer Travelmate laptop, the Synaptics touchpad does not work under
either the live environment, or after installation (after all updates
had been applied, which brought the kernel to version 5.3.0-26-ge
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1860791/+attachment/5322862/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860791
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1860791/+attachment/5322872/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860791
Title:
Sy
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1860791/+attachment/5322866/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860791
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1860791/+attachment/5322869/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/186
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1860791/+attachment/5322870/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860791
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1860791/+attachment/5322867/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1860791/+attachment/5322864/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860791
Title:
Syna
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1860791/+attachment/5322868/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860791
Public bug reported:
On my Acer Travelmate laptop, the Synaptics touchpad does not work under
either the live environment, or after installation (after all updates
had been applied, which brought the kernel to version 5.3.0-26-generic).
The touchscreen operated normally in both, so mouse control w
** Description changed:
Impact
==
The current stable release (bionic) does not support booting on the
Raspberry Pi 4. Several packages need back-porting from devel to support
this, along with a new kernel.
Bionic back-port branch:
https://code.launchpad.net/~waveform/ubu
** Description changed:
Impact
==
The current stable release (bionic) does not support booting on the
Raspberry Pi 4. Several packages need back-porting from devel to support
this, along with a new kernel. In addition, there are now changes in the
back-port that require updates
Are we sure this is fixed for Bionic? I've just installed 18.04.3 on an
old Acer Travelmate B118; under the live USB the touchpad didn't work
which sent me hunting around for bugs and eventually this one. After the
installation concluded I found the touchpad still didn't work so I
attempted Nilesh'
** Description changed:
Impact
==
The current stable release (bionic) does not support booting on the
Raspberry Pi 4. Several packages need back-porting from devel to support
- this, along with a new kernel.
+ this, along with a new kernel. In addition, there are now changes in the
** Description changed:
Impact
==
The current stable release (bionic) does not support booting on the
Raspberry Pi 4. Several packages need back-porting from devel to support
this, along with a new kernel.
- Relevant branch:
+ Bionic back-port branch:
https://code.launchpa
> so this is not completely updated to focal-proposed?
No, that was just certain focal-proposed packages on a focal image (on a
pi4). Have now re-run with a full focal-proposed chroot (under the same
focal image), and that doesn't reproduce the issue:
(focal-arm64)root@ubuntu:~# cat /etc/apt/sour
> Do you have the new python3.7 installed from focal-proposed?
> note, i was running everything from proposed. Since libffi6 & 7 might
> be used by python3.7.
Ah, no I didn't. However, doesn't seem like it makes much difference:
ubuntu@ubuntu:~$ sudo apt install -t focal-proposed python3.7
Readi
Reproduced on a Pi4 running the current focal daily:
ubuntu@ubuntu:~$ python3 -c "import goocalendar;
print(goocalendar.__version__)"
Unable to init server: Could not connec
** Description changed:
Impact
==
The current stable release (bionic) does not support booting on the
Raspberry Pi 4. Several packages need back-porting from devel to support
this, along with a new kernel.
+
+ Relevant branch:
+
+ https://code.launchpad.net/~waveform/ubuntu/+sou
** Description changed:
Impact
==
The current stable release (bionic) does not support booting on the
Raspberry Pi 4. Several packages need back-porting from devel to support
this, along with a new kernel.
+
+ Relevant branch:
+
+ https://code.launchpad.net/~waveform/ubuntu/+sou
Public bug reported:
We've just come across a situation where cloud-init races systemd to
mount a partition, with the result that either cloud-init fails to load
its seed, or a relatively important partition fails to mount. I'm not
entirely sure this is a bug - it could well be argued this is mis-
** Summary changed:
- [FFe] Firmware bump for Pi 4 boot support
+ [SRU] Firmware bump for Pi 4 boot support
** Description changed:
Impact
==
- Updated firmware is required to support booting the Raspberry Pi 4,
- primarily by providing Pi 4 specific variants of start*.elf and
- fixup
** Description changed:
Impact
==
The current stable release (bionic) does not support booting on the
Raspberry Pi 4. Several packages need back-porting from devel to support
this, along with a new kernel.
Test Case
=
* Attempt to boot the latest bionic image (
** Summary changed:
- [FFe] 2019.07 to support Pi4 boot
+ [SRU] 2019.07 to support Pi4 boot
** Description changed:
Impact
==
- The proposed version supports booting Ubuntu on the Raspberry Pi 4, both
- by providing a Pi 4 compatible variant of u-boot (which requires the
- version bum
** Changed in: linux-firmware-raspi2 (Ubuntu Bionic)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: linux-firmware-raspi2 (Ubuntu Bionic)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
** Changed in: u-boot (Ubuntu Bionic)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: u-boot (Ubuntu Bionic)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: flash-kernel (Ubuntu Bionic)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: flash-kernel (Ubuntu Bionic)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
Impact
==
- Apt upgrades performed on a Raspberry Pi 4 complain about missing
- database entries during the flash-kernel trigger. An updated version of
- flash-kernel with a Pi 4 entry in the database is available in the
- following PPA:
-
- https://launchpa
** Summary changed:
- Add entries for Pi 4
+ [SRU] Add entries for Pi 4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847587
Title:
[SRU] Add entries for Pi 4
To manage notifications about this b
I have an updated patch available from the following branch for focal:
https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
/python-apt/+ref/fix-dupe-ppa
Currently building a test package in the following PPA:
https://launchpad.net/~waveform/+archive/ubuntu/python-apt/+pa
** Changed in: linux-firmware-raspi2 (Ubuntu Eoan)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848247
Title:
3A+ boot failure on Eoan
To manage notificati
@Erik @wanthalf any chance the people with Pi 4 rev 1.2s can have a look
at verifying LP: #1854487 ? Unfortunately I don't have a rev 1.2 (yet)
and don't have a (reliable) means of obtaining one (yet). Should be
reasonably trivial to verify; thanks for any assistance!
--
You received this bug not
@jblainemitre indeed - but presumably one can pick any directory? I'm
assuming there's no particular requirement that the selected dir is
world-writeable like /tmp and /var/tmp (or at least there doesn't seem
to be in my setup?)
--
You received this bug notification because you are a member of Ub
** Description changed:
+ Impact
+ ==
+
A new variant of the Raspberry Pi 4 (revision 1.2) has been released
- (presumably to deal with the USB-C power issue [1]). An entry will need
- to be added to the flash-kernel database to permit it to recognize the
- platform.
+ (presumably to deal w
Proposed package available from ppa:waveform/flash-kernel at
https://launchpad.net/~waveform/+archive/ubuntu/flash-kernel/+packages
(with version bump to build in PPA)
Related branch is https://code.launchpad.net/~waveform/ubuntu/+source
/flash-kernel/+git/flash-kernel/+ref/pi4-rev-1-2
--
You re
@Erik I don't think we've got a bug filed for that yet - I'll rectify
that now as rev 1.2 of the Pi 4 will need to be added ... LP: #1854487.
I'll try and get that patched and released reasonably quickly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Public bug reported:
A new variant of the Raspberry Pi 4 (revision 1.2) has been released
(presumably to deal with the USB-C power issue [1]). An entry will need
to be added to the flash-kernel database to permit it to recognize the
platform.
[1] https://www.scorpia.co.uk/2019/06/28/pi4-not-worki
Tested the new armhf kernel on RPi3B+; copied 40Mb and 600Mb files
successfully with no issues. Compared performance of the 40Mb copy+sync
to the same machine running Disco (which has dwc_otg) and performance on
eoan with the new kernel was marginally quicker (6.8-7.0s on eoan with
dwc2 vs 8.2s-8.5
On Fri, 15 Nov 2019 at 09:30, Hui Wang wrote:
>
> I did test with VMSPLIT_2G today, the mmc/sd controller will not work
> anymore on rpi4 boards, so enable VMSPLIT_2G is not a solution so far.
Oh well, was worth a try.
> And today I also tested dwc2, it worked well, maybe we could enable dwc2
>
Some additional notes from testing last night (more or less blindly
after a load of googling for dwc_otg errors and mitigations):
* Adding dwc_otg.speed=1 (limiting the driver speed to Full Speed
USB1.1), fixes the mass-storage issue, but breaks compatibility with
most keyboards. So, not terribly
> The upstream kernel of https://github.com/raspberrypi/linux.git also
has this issue.
This be one reason why Raspbian uses three different kernels (one for
0/B+, one for 2B/3B/3B+, one for 4B).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Tested on 3A+ under armhf and arm64; all working.
** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841955
Title:
Can't
Tested on 3, 3+, CM3, CM3+, and 4 under armhf and arm64 with eoan-
proposed image. No regressions detected.
** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Description changed:
[Impact]
- Specific to the Raspberry Pi, when flash-kernel is executed to copy
- things to the boot partition, only the dtb of the Pi that it is being
- executed on is copied. In order to support moving the SD card between Pi
- models, flash-kernel needs to copy *all*
** Changed in: flash-kernel (Ubuntu)
Status: New => In Progress
** Changed in: flash-kernel (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Fixed version of flash-kernel available from ppa:waveform/flash-kernel
at:
https://launchpad.net/~waveform/+archive/ubuntu/flash-kernel/
Built from branch at (final commit is the version bump; remove this for
proposed commits):
https://code.launchpad.net/~waveform/ubuntu/+source/flash-
k
Can confirm that the test kernel from LP: #1848790 comment #11 fixes
boot on 3A+ (remove vc4-fkms-v3d overlay from config.txt too, and boot
operates correctly with framebuffer working). Tested on arm64 3A+ (and
3B, 3B+, 4B); need to test on armhf too.
--
You received this bug notification because
Public bug reported:
Specific to the Raspberry Pi, when flash-kernel is executed to copy
things to the boot partition, only the dtb of the Pi that it is being
executed on is copied. In order to support moving the SD card between Pi
models, flash-kernel needs to copy *all* dtbs provided by the kern
I've now tested the armhf and arm64 variants of Hui's test kernel from
comment #11 on the Pi 2, 3, and 4 (several memory variants) and all
seems good so far. Still need to finish testing on the compute modules,
though.
As regards flash-kernel, the relevant tickets for the missing entries
are LP: #
Test package for devel available from PPA (we'll see about SRUing to
bionic and presumably eoan once this has landed):
https://launchpad.net/~waveform/+archive/ubuntu/flash-kernel
Relevant branch:
https://code.launchpad.net/~waveform/ubuntu/+source/flash-
kernel/+git/flash-kernel/+ref/pi
** Description changed:
Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard
which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10
armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the
keyboard on either. Booting the arm64 image on a Raspberr
Please note for testing:
add-apt-repository does not operate without the updated package either,
so just download the relevant .debs and install manually with "sudo dpkg
-i" for testing. The package that's really needed is python-apt-common
(which contains the updated template output), but you may
Updated python-apt package available in the following PPA:
https://launchpad.net/~waveform/+archive/ubuntu/pkg
Branch from which the package was built:
https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
/python-apt/+ref/focal-entry
--
You received this bug notification bec
** Changed in: python-apt (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: python-apt (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
unassigned) => Dave Jones (waveform)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1006905
Title:
Case inconsistency in machine field definitions
To manage notifications about this bug
** Changed in: flash-kernel (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1690650
Title:
flash kernel reports unsupported platform on rpi 2 1.2
To
Confirmed the 3A+ entry is missing from flash-kernel; I'll get this
added for Eoan and open an SRU for Bionic (we need to backport flash-
kernel to bionic anyway for Pi4 support).
** Changed in: flash-kernel (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed i
> I mean the simplefb driver in the kernel in the #3, I didn't know
there is a simplefb driver in the uboot too.
Ah, I'm afraid my lack of kernel knowledge is showing there: I didn't
realize the was a simplefb in the kernel! I should've thought given the
kernel starts off looking fine, and only sh
Additional detail from dmesg:
...
[1.390148] usbcore: registered new interface driver lan78xx
[1.391889] usbcore: registered new interface driver smsc95xx
[1.393568] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[1.395273] ehci-pci: EHCI PCI platform driver
[1.396
Public bug reported:
Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard
which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10
armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the
keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the
I'm at a similar place; currently digging into the simplefb side of
things. My current thoughts are as follows:
1. Ideally I want to ditch the vc4-fkms-v3d overlay; firstly this
resolves the 3A+ booting issue, secondly it's something that should be
an option rather than mandatory to the boot proce
Related to #1847596 - commenting out the vc4-fkms-v3d overlay in
config.txt permits the 3A+ to boot, albeit with corrupted framebuffer.
In other words, solving #1847596 "properly" should also yield a fix for
this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
For now, I've adjusted the boot configuration written by the base image
(and migrated by u-boot-rpi) to include the vc4-fkms-v3d overlay on all
models. While this seems to alleviate the problem, it should be
considered temporary workaround only (we should figure out why this
occurs and try and fix
The firmware currently included in bionic-updates is from 2019-02-15
(primarily to support booting the CM3+), and in eoan is 2019-08-19; both
of these support .dtbo files.
** Changed in: linux-firmware-raspi2 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification becau
Fix released for eoan; needs backport to bionic and disco.
** Changed in: linux-firmware-raspi2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818286
Title:
Public bug reported:
The current Eoan image hits a kernel panic when booting on a Raspberry
Pi 3A+. Unfortunately it does so before the serial console has been
enabled so there's no useful output beyond what scrolls by rapidly on
the framebuffer console.
It is notable that the start.elf bootloade
The current versions of linux-firmware-raspi2 for bionic and eoan
(1.20190215-0ubuntu0.18.04.1 and 1.20190819-0ubuntu2 respectively)
shouldn't conflict in this manner; neither include the -sdio.bin files,
just the configuration text files and related .clm-blob files. Is anyone
still seeing this iss
Just had a look at linux-firmware-raspi2 for bionic, and the latest
version (1.20190215-0ubuntu0.18.04.1) no longer contains
/lib/firmware/brcm/brcmfmac43455-sdio.bin; can you confirm you're still
seeing this error with the latest version?
--
You received this bug notification because you are a m
The current version of linux-firmware-raspi2 supports wifi on the Pi3
(and the 3+). The forthcoming version to be released with Eoan also adds
support for wifi on the Pi4, so I think we can (belatedly) mark this as
released!
** Changed in: linux-firmware-raspi2 (Ubuntu)
Status: Triaged => F
@satmandu thanks for the information! I'd got as far as figuring out the
dram_init call was getting the available RAM info from the mailbox,
which only permitted a single bank to be reported, which was then
getting used in the fdt fixup called by the bootm. As it happens the fdt
/memory node was al
Figured it out; you're using the v2019.07-rpi4-wip branch while I based
the latest u-boot on the rpi4 branch (which is slightly later and
appears a bit more polished). After a bit of experimentation it turns
out the crucial difference is in the config, specifically in a comment
(which is why it too
Public bug reported:
Impact
==
On the current eoan daily images, the wifi adapter doesn't appear at
all. A bump to binary blob and configuration of the BCM43455 firmware is
required to enable the wifi adapter. A version of linux-firmware-raspi2
with required changes is available in the follow
> For WiFi, I remember I found the firmware from someplace, then the
WiFi worked.
> ubuntu@ubuntu:~$ ls /lib/firmware/brcm/brcmfmac43455-sdio.* -la
> -rw-r--r-- 1 root root 600487 Sep 1 05:45
> /lib/firmware/brcm/brcmfmac43455-sdio.bin
> -rw-r--r-- 1 root root 14036 Sep 1 05:45
> /lib/firmware/b
Can you attach the content of your /boot/firmware/config.txt?
I suspect it's lacking the vc4-fkms-v3d overlay which is now required as
of the pi4-compatible kernel (I'd originally, mistakenly, thought this
was only required on the pi4 but it turns out all pi models need it).
Tomorrow's dailies sho
Public bug reported:
Impact
==
Apt upgrades performed on a Raspberry Pi 4 complain about missing
database entries during the flash-kernel trigger. An updated version of
flash-kernel with a Pi 4 entry in the database is available in the
following PPA:
https://launchpad.net/~waveform/+arch
> Now when doing apt update from the Pi4 itself, this came up:>
> Processing triggers for flash-kernel (3.98ubuntu3) ...
> Unsupported platform.
> dpkg: error processing package flash-kernel (--configure):
> installed flash-kernel package post-installation script subprocess
> retu
901 - 1000 of 1078 matches
Mail list logo
