Hey paul, this issue is about missing kernel modules, not about anything
in the core22 snap ...
Part of the kernel stuff is being handled already in
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2024443
though ...
** Summary changed:
- Core 22 is missing Realtek and TI drivers, that
Public bug reported:
While included in UC20, the mt7601u.ko and rtl8192cu.ko seem to be
missing in UC22 kernels, please move it back in place, our customers
that run UC20 or tested with UC20 will expect their hardware to keep
working in UC22 installs
** Affects: linux-raspi (Ubuntu)
Importan
Public bug reported:
i recently recommended a TP-Link TL-WN722N to an UbuntuCore customer
asking for a recommendation of a USB wifi adapter with external antenna
for the RPi since i use this card in various RPi projects ...
trying it on UC22 it turns out that the module driving this card is not
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
--
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/1994126
Title:
NULL pointer dereference in power_supply
** Changed in: linux-raspi (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/1968469
Title:
ILITEK_ILI9881C panel driver missing
Status in
Public bug reported:
the current 5.15.0-1004-raspi kernel for 22.04 does not enable the
CONFIG_DRM_PANEL_ILITEK_ILI9881C=m option, thus such touchscreen panels
can not be used
the cutiepi (https://cutiepi.io/) project does use this hardware for their pi
based tablets.
booting ubuntu 22.04 on s
Public bug reported:
To attach TFT touchscreens the pi-foundation kernel ships the fbtft
devicetree overlay along with rpi-display.
While you can attach a stand-alone TFT display just fine when only using
rpi-display to provide the drivers with hardcoded GPIO assignments, it
gets extremely tricky
note that i did never really follow up with that setup in the end but i
found out that even modern SSDs (not only rotary HDDs) usually draw more
power than the USB3 port can provide, you will need an Y-Cable or
external power supply ... while i can not fully confirm (due to lack of
time and testing
hirsute does not have Ubuntu Core images ;)
It seems to be solvable via a simple defconfig change according to:
https://github.com/raspberrypi/linux/issues/4205
We have at least one UC customer implementing a CM4 baseboard with TPM
for Full disk encryption and secureboot in UC20, for this the cl
Public bug reported:
There is a timing issue when using the CM4 with the official CM4 IO
baseboard.
The CM4 baseboard comes with a built in rtc and a battery holder by
default, to enable it a devicetree overlay needs to be enabled and a
matching module gets loaded ...
$ tail -2 /run/mnt/ubuntu-s
Public bug reported:
Trying to use a default USB boot on a Raspberry Pi using either an USB3
UAS SSD enclosure or even a simple USB 2 stick fails (due to the missing
console output it simply hangs indefinitely with a black screen
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1914608).
Public bug reported:
when booting UC20 on a Pi4 the screen backlight is completely off and no
signal is produced.
inspecting the boot a little closer it seems the necessary modules for
bringing up the vc4 framebuffer are not included in the initramfs on
ubuntu core. once they get loaded (after bo
Public bug reported:
supposedly the bluetooth firmware from:
https://launchpad.net/ubuntu/+source/linux-firmware-
raspi2/3-0ubuntu1~20.04.1
should be shipped in the latest pi-kernel snap in the edge/beta channel.
the BCM4345C5.hcd (as mentioned in the last changelog entry above) is
essential for
so this is indeed not an issue with the modules but with the kernel
itself and the support for sas, uas or the enclosure services.
i test-built all tags from https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux-raspi/+git/focal/refs/tags from 1023.26
going backwards and found that it rel
the config option seems to be:
CONFIG_VIDEO_CODEC_BCM2835=m
** Also affects: linux-raspi (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.n
i'll try over the weekend ...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1881623
Title:
USB support missing in initrd makes booting core with writable on USB
impossible
Sta
in fact it seems like in 5.3 USB is not working at all !!! i verified
that today ...
my self-built kernel uses the focal 5.4 branch where USB works fine
then:
https://github.com/ogra1/linux-raspberrypi-
org/blob/master/snap/snapcraft.yaml
--
You received this bug notification because you are a
also note that the fabrica appliance you linked uses a re-built kernel
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1881623
Title:
USB support missing in initrd makes booting co
hmm, i wonder why they dont load then ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1881623
Title:
USB support missing in initrd makes booting core with writable on USB
impos
this is definitely a regression, mounting partitions should work ...
marking as critical.
** Changed in: linux-raspi2 (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
ht
** Also affects: linux-raspi (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1881623
Title:
USB support missing in initrd makes
** Description changed:
when using a gadget.yaml like:
volumes:
pi4-system-boot:
schema: mbr
bootloader: u-boot
structure:
- type: 0C
filesystem: vfat
filesystem-label: system-boot
size: 512M
content:
- source
** Description changed:
when using a gadget.yaml like:
volumes:
pi4-system-boot:
schema: mbr
bootloader: u-boot
structure:
- type: 0C
filesystem: vfat
filesystem-label: system-boot
size: 512M
content:
- source
Public bug reported:
when using a gadget.yaml like:
volumes:
pi4-system-boot:
schema: mbr
bootloader: u-boot
structure:
- type: 0C
filesystem: vfat
filesystem-label: system-boot
size: 512M
content:
- source: boot-assets/
ta
adding bionic since we're supposed to fully support the pi4 there too
** Also affects: linux-raspi (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://
the included snapcraft.yaml means i need to have the whole tree locally
on disk, as someone who maintains a ton of community images for
UbuntuCore i prefer to just have the snapcraft.yaml locally so the disk
is only cluttered during build. along with that i am trying to build the
eoan tree for the
well, as a user/customer building my own kernel i'd kind of expect the
defconfig for a flavour to not be a debug config.
but indeed you are correct, i should have taken a look at the included
snapcraft.yaml which, despite being for the wrong flavour (generic/pc-
kernel), indeed contains CONFIG_DEB
ok, this looks a bit more reasonable now ...
$ ls -lh pi4-kernel_raspi2-5.3.0-1011.12_armhf.snap
-rw-r--r-- 1 ogra ogra 211M Nov 4 17:05
pi4-kernel_raspi2-5.3.0-1011.12_armhf.snap
so CONFIG_DEBUG_INFO=y should better be turned off by default for people
building snaps from our trees ;)
--
You
yup, seems this is (surprisingly) on by default ...
$ grep DEBUG_INFO parts/kernel/build/.config
CONFIG_DEBUG_INFO=y
# CONFIG_DEBUG_INFO_REDUCED is not set
# CONFIG_DEBUG_INFO_SPLIT is not set
CONFIG_DEBUG_INFO_DWARF4=y
# CONFIG_DEBUG_INFO_BTF is not set
i'll try a re-build and override that opt
i also tried using the "source-branch: raspi2" argument in the
snapcraft.yaml instead of using teh master branch and the "source-tag:"
option, but this results in the same big size ...
additionally i'd like to remark that due to the transactional nature of
UbuntuCore we need to keep the kernel thr
Public bug reported:
typically a kernel snap built from the kernel.ubuntu.com tree using the
raspi2 defconfig results in a snap package that is below 150MB in size:
$ ls -lh pi2-kernel_raspi2-4.4.0-1110.snap
-rw--- 1 root root 129M Jun 4 15:01 pi2-kernel_raspi2-4.4.0-1110.snap
trying to bu
mir-kiosk is currently the only supported way to get grahical (mostly
kiosk) applications up and running on ubuntu core, some of our digital-
signage customers use it so currently the overlay is a requirement
(until the mir team solves it with a pi specific mir backend or the vc4
driver changes in
the overlay is needed for mir-kiosk to allow it to work at all
(unaccelerated though)
to have mir-kiosk fully accelerated one needs to use -kms-v3d instead
but this in turn disables all video decoding in the vc4 core. i
originally picked -fkms-v3d for the gadget since it is the least evil
(makes m
just as a followup ... better ignore my comment above ... KVM is indeed
not KMS ... sorry for causing confusion here
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1783961
Title:
Public bug reported:
attaching a raspberry pi camera to the pi camera interface (CSI) works
fine when capturing video, pictures and streams directly through the
picamera python library.
when trying to use software that relies on using /dev/videoX with a
camera attached to the CSI interface, the b
enabling CONFIG_KVM instead of enabling KVM via the dtb overlay will
hard-disable all video acceleration of the upstream proprietary driver
of the pi and make it completely unusable for any kind of setup that
uses any upstram acceleration features from the raspberry pi foundation
(i.e. via /opt/vc4
@gerald: right, there is no way to protect you from turning the device
into a brick if this step goes wrong (unlike kernel or rootfs we can not
roll back the bootloader)
note that the gadget snap from edge will not have a working dtb for the
old kernel which will likely make you end up with an unb
@anthony ... technically that would be me ... practically the gadget
will never update the firmware files (the firmware files as well as the
dtb are usually in a dead-lock with the kernel version)
i'm waiting for a solution for this from the core team before we can
move on ... your best bet is to
@ying-chun the kernel snap only upgrades the kerne, modules and files in
/lib/firmware ...
the gadget snap only updates the gadget.yaml, snap.yaml and files not in
/boot (i.e. it excludes all bootloader bits by default). until there is
a solution for potential unbootable systems this will not chan
https://github.com/snapcore/pi3-gadget/commit/8b88f06ab5681d0ff41704a7813665a0203cbafc
for reference
--
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/1647936
Title:
Raspberry Pi 3: a small
the gadget snap in edge has this fix since a while already, it just did
not make it into a stable image yet.
** Changed in: snappy
Status: New => Fix Committed
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a membe
ogra@pi3:~$ cd /boot/uboot/
ogra@pi3:~$ sudo tar xvf pi2-kernel_22.snap/dtbs/overlays.tgz
then adding "dtoverlay=vc4-kms-v3d" and creating /etc/modules-
load.d/vc4.conf with just "vc4" in it seems to get me vc4 loaded and i
get:
[4.952421] vc-cma: Videocore CMA driver
[4.956535] vc-cma: v
where exactly did you add the overlays in the first paragraph ? only
overlays in /boot/uboot/overlays are read by the proprietary bootloader
(you need to create the dir)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
http
@markus: not sure, i dont know how the non snappy images set the MAC,
technically if they use similar uboot scripts the MAC should come from
the first dtb snippet that is read from the ROM/closed bootloader, that
part should not be related to the actual dtb address at all...
--
You received this
the newer firmware (start.elf,fixup.dat and bootcode.bin) hard-requires
0x0200 because it initializes the hardware differently in the newer
version...
looks like linux-firmware-raspi2 was not properly updated alongside with
flash-kernel and the kernel itself, there is a hard lockstep between
t
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
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/1625177
Title:
OOPS on beaglebone on boot of 4.4.0-36-g
oh, do you ship mesa in the mir server snap ? i didnt think that would
be possible
--
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/1625805
Title:
arm64 kernel panic for l2 mmu with unity8
i assume this is running a snap on a classic image, not on an ubuntu core one ?
(since we have no EGL support in teh core image yet)
--
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/1625805
the log is in the pastebin mentioned in the description ...
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1625177
Tit
Public bug reported:
trying to assemble a new series 16 ubuntu core image for the beaglebone
black i am constantly running into an OOPS on first boot. seemingly
related to the NIC driver since the NIC does not work after the OOPS.
syslog can be found at http://paste.ubuntu.com/23202737/
a test i
snapd is seeded in everything but powerpc. images will only be created
for i386, amd64, armhf and arm64. we do build generic and module-less
initrds at rootfs build time that require hackery to be re-packed when
you build a kernel snap, this is what we would like to avoid ... (one
expectation is to
Public bug reported:
snapd is seeded in all images in xenial by default and snaps are
squashfs files.
the snappy images need squashfs available at boot time and use official
kernels.
currently squashfs is the only module that forces us to re-pack initrds
to add it everywhere for snappy images, i
On the MX4 specifically there is also the issue with the "home" button
staying active for about 30sec when the display was turned off, when
shoving the phone into your pocket it is easy to create a button press
event if you do not wait long enough.
--
You received this bug notification because yo
this looks like wlan0 was brought up just fine
seems to mostly be a cosmetic issue that /etc/network/if-up.d/ubuntu-fan doesnt
exit quietly
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/b
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- wifi USB dongle fails to work
+ wifi USB dongle fails to work with musb-hdrc error
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
oops, totally forgot this is still open, the problem turned out to be a
completely stuck fan wrapped in filth ... cleaning it ave the system
proper values so thermald does the right thing now.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Vivid)
one thing i noticed is that after dropping intel_pstate=disable from teh kernel
commandline, thermald does not seem to star/run at all .. starting it manually
i captured http://paste.ubuntu.com/11541063/
note that the behavior gets minimally better with thermald running, but
switching workspace
Public bug reported:
I finally got around to upgrade my work laptop (first gen dell XPS
sputnik system (ivy bridge)) yesterday, to find myself with a completely
unusable and sluggish desktop, constantly spinning CPU fans and a hot
enough laptop case that you can burn your fingers after the first r
just for completeness (in case someone looks for a wrokaround), adding
intel_pstate=disable to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub
and running sudo update-grub got me the ondemand driver back and got the
system back to behave as stable as in 14.10.
--
You received this bug notificatio
** Changed in: alsa-lib (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs/1276901
Title:
alsa-lib: UCM - hammerhead sound doesn't wo
I merged this into alsa-lib now so users do not have to apply teh files
by hand to teh readonly images, please add further improvements you find
here or open a new bug
** Changed in: alsa-lib (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are
** Also affects: alsa-lib (Ubuntu)
Importance: Undecided
Status: New
** Changed in: alsa-lib (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-lib in Ubuntu.
https://bugs.launchpad.ne
i cut that down to http://paste.ubuntu.com/6217518/, applied it and
built a kernel ... sadly now Mir does not start at all, SurfaceFlinger
does, but is very slow and complains:
W/SurfaceFlinger( 659): Timed out waiting for hw vsync; faking it
so i guess for using this patch some changes on the u
h !
look what i found !
http://review.cyanogenmod.org/#/c/28068/
--
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/1234743
Title:
omapfb module floods system with udev events on samsu
adjusting bug description, this is sadly a constant condition, not
related to movie playback
** Summary changed:
- omapfb module floods system with udev events on samsung galaxy nexus when
playing mp4
+ omapfb module floods system with udev events on samsung galaxy nexus
--
You received this b
pitti pointed on IRC to
https://android.googlesource.com/kernel/msm/+/57195292 ... which doesnt
help for our driver, but the problem does not seem to be uniqe
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
note that touch images do not use unity-panel-service anywhere
--
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/1235649
Title:
uevent spam causes session upstart to consume massive amounts
i can definitely make it stop consuming more ram by stopping the
upstart-event-bridge session job.
this works on both devices.
the ram does not get freed but the consumption does not keep rising either
anymore then.
--
You received this bug notification because you are a member of Kernel
Packa
68 matches
Mail list logo
