@Daniel could you try out the bluez package from the following PPA:
https://launchpad.net/~waveform/+archive/ubuntu/pi-bluetooth/+packages ?
Should be as simple as doing:
sudo add-apt-repository ppa:waveform/pi-bluetooth
sudo apt update
sudo apt upgrade
The version in that PPA contains the
@henry-sprog yup, that looks like the same
Attached a patch to fix this in hirsute; once landed will SRU this to
groovy and earlier.
** Patch added: "lp1903048.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+attachment/5431962/+files/lp1903048.debdiff
--
You received
k a MAC address.
** Affects: bluez (Ubuntu)
Importance: Undecided
Assignee: Dave Jones (waveform)
Status: New
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
--
You received this bug notification because you are a member of Kernel
Packages, which is s
Public bug reported:
The CONFIG_SECURITY_DMESG_RESTRICT option is not set on the Ubuntu Pi
kernels, resulting in dmesg being accessible to ordinary users.
This is in contrast to PC installs, where dmesg is now restricted to the
"root" user in 20.10 onwards. The following messages from the ubuntu-
Public bug reported:
On the Pi 4 board revision 1.4 (of which the 8Gb model is currently the
main example), the VL805 USB controller doesn't appear to be recognized
by the 5.3 kernel. To reproduce:
* Flash a current bionic image (e.g.
http://cdimage.ubuntu.com/releases/bionic/release/ubuntu-18.0
** Description changed:
- linux-raspi2 was renamed to linux-raspi for Focal
+ linux-raspi2 was renamed to linux-raspi for Focal, but is still required
+ for Bionic. Once Bionic is unsupported, this package can removed.
--
You received this bug notification because you are a member of Kernel
Pack
Public bug reported:
linux-raspi2 was renamed to linux-raspi for Focal
** Affects: linux-raspi2 (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
I'm several steps down the bisect at this point and have overcome
several compilation issues along the way (old kernels won't compile with
gcc-9, so installed gcc-8, patched around an issue building with newer
headers,
https://gitlab.freedesktop.org/drm/msm/commit/dfbd199a7cfe3e3cd8531e1353cdbd7175
Started the bisection; this may take several days to finish (each "good"
result takes many hours to verify given that the problem sometimes
didn't manifest for several hours). I'll update the ticket when I've got
some further results.
--
You received this bug notification because you are a member
> Which kernel did the system use in Xenial? Can you please roll back to
the older kernel and test it?
Looks like 4.15.0-99 was the last kernel I used on Xenial before the
upgrade. Is it possible to use a kernel that old on focal? If so, would
the bisect instructions in LP: #1798979 be sufficient
** Description changed:
I have a "UGreen USB3 Hub/SD card reader" which worked reliably under
Ubuntu Xenial for many months. Recently, I re-installed the machine it
was attached to with a fresh install of Ubuntu Focal. When initially
booted, the device works perfectly (at least, the USB3 p
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1879393/+attachment/5373659/+files/PulseList.txt
--
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/
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1879393/+attachment/5373657/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1879393/+attachment/5373658/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1879393/+attachment/5373653/+files/Lsusb-v.txt
--
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/1879
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1879393/+attachment/5373660/+files/UdevDb.txt
--
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/1879393
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1879393/+attachment/5373656/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1879393/+attachment/5373654/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1879393/+attachment/5373661/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1879393/+attachment/5373655/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1879393/+attachment/5373652/+files/Lsusb-t.txt
--
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/1879
apport information
** Attachment added: "AudioDevicesInUse.txt"
https://bugs.launchpad.net/bugs/1879393/+attachment/5373646/+files/AudioDevicesInUse.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1879393/+attachment/5373648/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1879393/+attachment/5373649/+files/Lspci.txt
--
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/1879393
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1879393/+attachment/5373647/+files/CRDA.txt
--
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/1879393
Ti
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1879393/+attachment/5373645/+files/AlsaInfo.txt
--
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/18
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1879393/+attachment/5373650/+files/Lspci-vt.txt
--
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/18
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1879393/+attachment/5373651/+files/Lsusb.txt
--
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/1879393
Public bug reported:
I have a "UGreen USB3 Hub/SD card reader" which worked reliably under
Ubuntu Xenial for many months. Recently, I re-installed the machine it
was attached to with a fresh install of Ubuntu Focal. When initially
booted, the device works perfectly (at least, the USB3 ports and SD
Public bug reported:
We need to add the "iw" package to the pi images (for configuration of
the wifi region upon boot). However, as we don't have per-device seeds
this can't be placed directly in the seed for the images (without
affecting other images which don't need it). Hence, adding it as a
"f
> 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
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
@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 Kernel
Packages, which is subscribed to linux-firmware
** Changed in: linux-raspi2 (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1847596
Title:
rpi3b+: corrupted screen on hdmi
S
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860791
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
** 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860791
Ti
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/18
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860791
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860791
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: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1860791/+attachment/5322865/+files/Lsusb.txt
--
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/1860791
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
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
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'
@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
@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 Kernel
Packages, which is
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 Kernel
Packages, which is subscribe
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 Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1841
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
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
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
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
Thanks Paolo - I can confirm the pre-cooked image displays the boot logo
nicely (couldn't test the snap itself, but I suspect that's due to me
lacking the correction snap incantations rather than anything wrong with
it - snap complained about replacing a signed kernel with an unasserted
one).
--
@p-pisati: that assumes the overlay isn't required by anyone; as ogra
notes above, the overlay is required for mir-kiosk to work. I don't know
how important mir-kiosk is, but it seems it might be fairly relevant to
core [1]. Either way, it seems less risky to me to add modules to initrd
(which only
Indeed - I'd rather not remove overlays without being certain we don't
need them. For now though, let's just get the splash screen working
again (as it's a little un-nerving for new users to be presented with a
straight black screen during boot and have no indication anything's
working other than a
Tested Oliver's suggestion and indeed it does work if the overlay is
removed but I assume that the overlay is there for a reason.
Furthermore, extracting the psplash binary from the psplash initrd and
running it after boot has concluded (at which point /dev/fb0 exists)
works successfully which sugg
It would be nice to start building compressed arm64 kernels for eoan,
but it may have to wait a bit as the core boot-env won't yet handle this
correctly (that doesn't matter for core-16, but core-18 has arm64
images).
--
You received this bug notification because you are a member of Kernel
Packag
368844
** Changed in: flash-kernel (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
--
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/1808056
Title:
vmlinuz is very large
I've put together an update for flash-kernel that handles booting an
uncompressed image (to support existing arm64 installs), a self-
compressed image (to support existing armhf installs), and a gzip'd
image (to support the proposed format). It assumes the kernel is called
"vmlinuz" in all cases (b
Had these exact symptoms (lockup, not even sysrq working) on Ubuntu
16.04 with kernel 4.4.0-116 and 4.13.0-37 (booting to the "prior stable"
kernel in each case, 4.4.0-112 and 4.13.0-36, worked successfully).
There's quite a lot in the changelog
(http://changelogs.ubuntu.com/changelogs/pool/main/l/
101 - 175 of 175 matches
Mail list logo
