It looks like python3-distutils package didn't get generated from the
build?
https://launchpad.net/ubuntu/+source/python3-stdlib-
extensions/3.12.2-3ubuntu4
Also, the file list of the current python3-distutils package looks like
it is all python 3.11 files.
--
You received this bug
You can use https://launchpad.net/~kelebek333/+archive/ubuntu/nvidia-
legacy for support on jammy, but why bother?
The legacy Nvidia driver doesn't support Wayland with mutter, so you're
probably better off just using the nouveau driver anyways.
--
You received this bug notification because you
Also seeing this issue on a Raspberry Pi 4B, so it isn't just limited to
x86_64 arch...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969243
Title:
gdm 42.0-1ubuntu4 no longer shows Wayland option
See https://github.com/openzfs/zfs/commits/zfs-2.1.5-staging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964827
Title:
zfs-linux upstream at 2.1.4, jammy has 2.1.2
To manage notifications about
Since the 2.1 branch is itself cherry-picks of updates backported from
zfs master, it might make sense to just follow the 2.1 series for jammy,
as opposed to re-cherry-picking from the upstream cherry-pick backports
to the 2.1?
Otherwise, there will be a lot of duplicated work...
The zfs-devs
Here's a ppa with working packages: https://launchpad.net/~satadru-
umich/+archive/ubuntu/zfs-experimental
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964827
Title:
zfs-linux upstream at 2.1.3,
Public bug reported:
I know Jammy is in freeze
zfs upstream is now at 2.1.3, which has a lovely set of fixes for issues
I have noticed (such as zfs complaining when waking for sleep, and also
patches to support 5.16 better and also for the support of 5.17.)
Please peruse the large number of
The patch at
https://gist.github.com/joanbm/37fd0590f30b41e7e89ade6e242ca16e from
Joan Bruguera completely solves the issue.
(Patch is attached.)
** Patch added: "broadcom-wl-fix-linux-5.17.patch"
This is my attempt at getting around the warning message, but clearly,
more work will need to be done to update the driver for post-5.17.
With just the following part of the patch the driver builds and runs
fine on kernel 5.17-rc5.
diff -Npaur a/src/wl/sys/wl_linux.c b/src/wl/sys/wl_linux.c
---
This happens because of
https://github.com/torvalds/linux/commit/adeef3e32146a8d2a73c399dc6f5d76a449131b1
netdev->dev_addr is a const now...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961801
(Worth noting that is a warning, and the network still works.)
** Patch removed: "Fix PDE_DATA change in 5.17"
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1961801/+attachment/5562741/+files/0030-add-support-for-Linux-5.17.patch
--
You received this bug notification because you are
** Patch added: "Updated patch which allows compile but still causes a warning"
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1961801/+attachment/5562822/+files/0030-add-support-for-Linux-5.17.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This is the kernel issue I get with the expanded patch.
[7.508238] [ cut here ]
[7.508239] netdevice: wlp3s0: Incorrect netdev->dev_addr
[7.508257] WARNING: CPU: 3 PID: 1710 at net/core/dev_addr_lists.c:517
dev_addr_check.cold+0x65/0x9f
[7.508267] Modules
Public bug reported:
At the very minimum, 5.17 replaces PDE_DATA with pde_data as per
https://lore.kernel.org/all/20211124081956.87711-2-songmuc...@bytedance.com/T/#u
The attached patch addresses that issue, but the module still doesn't
work...
ProblemType: Bug
DistroRelease: Ubuntu 22.04
@jawn-smith, I'm using this display:
https://www.waveshare.com/5.5inch-hdmi-amoled-with-case.htm
with this cmdline.txt:
console=tty1 root=LABEL=writable rootfstype=ext4 rootwait quiet splash
video=HDMI-A-1:1080x1920M@60,rotate=90,panel_orientation=right_side_up
I'm also seeing this same issue with a 5.15-rc4 kernel built from
https://github.com/raspberrypi/linux/tree/rpi-5.15.y
[ 408.326395] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]]
*ERROR* [CRTC:77:crtc-3] flip_done timed out
[ 408.326477] [drm:drm_crtc_commit_wait [drm]] *ERROR*
@vanvugt would you be willing to open an issue about this at
https://github.com/raspberrypi/linux/issues since this does look like a kernel
issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
(The screen still doesn't come back after blanking properly... but we
might have to kick that issue upstream, as I'm still even seeing that in
5.15-rc4 kernels built from https://github.com/raspberrypi/linux )
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
@juergh removing overclocking fixed the issue. Looks like the GPU was
giving errors when overclocked.
Thanks for asking me to check that.
The firmware in linux-firmware-raspi2_5-0ubuntu1~ppa1_arm64.deb works
fine with the 5.13.0-1008-raspi kernel.
You can mark this issue as resolved for me.
--
I do still get this error eventually with the 5.13.0-1008-raspi kernel.
This usually happens overnight after the screen has gone to sleep, after
which I can not bring the screen back up until a reboot.
[ 6411.078361] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]]
*ERROR*
@waveform The issue might be with the bcm2711-rpi-4-b.dtb...
sudo dpkg -i linux-firmware-raspi2_5-0ubuntu0~21.04~ppa1_arm64.deb ;
sudo flash-kernel --force 5.11.22-9021-raspi ; sudo reboot
Result: no video.
sudo dpkg -i linux-firmware-raspi2_5-0ubuntu1~ppa1_arm64.deb ; sudo
flash-kernel --force
The kernel at https://kernel.ubuntu.com/~juergh/hirsute-raspi/ does let
video work.
It even works with the current firmware!
debug info attached using current firmware..
** Attachment added: "impish-debug-10_05_2021_2123EDT.txt"
Apologies.
flash-kernel --force 5.11.0-1017-raspi results in working video, using
the firmware that came with it.
Using newer firmware does not fix the system.
(Now testing the kernel at https://kernel.ubuntu.com/~juergh/hirsute-
raspi/ )
--
You received this bug notification because you are
5.11.0-1017-raspi is fine, also using the same latest hexxeh firmware.
(Not using the .dtb files from the hexxeh repo.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944397
Title:
HDMI does not
Here is more debug logging from using the latest RPI firmware from
https://github.com/Hexxeh/rpi-firmware/commits/master
(Using the 5.13.0-1008.9-raspi kernel, obviously.)
My display is blank, but the system thinks that the display is working,
as I have ffplay playing a video stream upon
Public bug reported:
This is using KMS, not fKMS...
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-raspi (not installed)
ProcVersionSignature: Ubuntu 5.13.0-1008.9-raspi 5.13.14
Uname: Linux 5.13.0-1008-raspi aarch64
ApportVersion: 2.20.11-0ubuntu69
Architecture: arm64
Thanks. This will break Wayland though, no? "The full KMS overlay is
required for X11 application support under wayland."
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944397
Title:
HDMI does not
kitchen sink debug output...
** Attachment added: "debug.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1944397/+attachment/5527119/+files/debug.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
(I would note that even with this kernel I have issues with getting the
screen to come back from sleep... which might explain the dmesg errors
at the end.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
vc-log output for working boot:
[5.506129] vcos: brfs: File read: /mfs/sd/config.txt
[5.506979] vcos: brfs: File read: 1663 bytes
[5.560501] vcos: brfs: File read: /mfs/sd/edid.dat
[5.578718] vcos: brfs: File read: 256 bytes
[5.586393] vcos: brfs: File read: /mfs/sd/config.txt
@brian-murray The linux-image-5.13.0-1006-raspi kernel is working fine,
so yes this is a regression.
5.11.0-1016-raspi also works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944397
Title:
(FYI I set this to overclock to 2Ghz today, which is stable, and within
warranty for the device, but the issues were happening before I changed
that setting.)
** Attachment added: "config.txt"
** Attachment added: "cmdline.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1944397/+attachment/5527113/+files/cmdline.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944397
My system does indeed boot with this fix!
Unfortunately, there is some other kernel breakage with linux-
image-5.13.0-1007-raspi which is killing any display output and forcing
me to do a hard reset to reboot the system.
So I've opened a separate bug for that here:
Full dmesg from broken linux-image-5.13.0-1007-raspi:
https://paste.ubuntu.com/p/XV6N9bKPnm/
dmesg from working linux-image-unsigned-5.15.0-051500rc2-generic:
https://paste.ubuntu.com/p/Yy3JHR3CHr/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
linux-image-5.13.0-1006-raspi boots when linux-modules-extra-raspi installed.
linux-image-5.13.0-1007-raspi gives these kernel errors.
linux-image-unsigned-5.15.0-051500rc2-generic boots properly
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Here is the error message which is filling up my dmesg:
[ 24.621271] WARNING: CPU: 1 PID: 252 at
drivers/gpu/drm/vc4/vc4_hdmi_regs.h:445 vc5_hdmi_set_timings+0x984/0xd80 [vc4]
[ 24.621304] Modules linked in: snd_soc_hdmi_codec vc4 joydev drm_kms_helper
cec snd_usb_audio btsdio snd_soc_core
Installing the mainline 5.15-rc2 kernel from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.15-rc2/arm64/ resolves
this issue for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944397
Title:
Public bug reported:
Have a HDMI display w/o audio hooked up to this RPI4B.
With the latest kernel update the screen does not turn on due to this.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-1007-raspi 5.13.0-1007.8
ProcVersionSignature: Ubuntu 5.13.0-1007.8-raspi
*** This bug is a duplicate of bug 1943097 ***
https://bugs.launchpad.net/bugs/1943097
I can confirm that installing linux-modules-extra-raspi fixes this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Could we have the usb-storage modules moved back out of linux-modules-
extra? Alternately ensure that linux-modules-extra is installed on
upgrades so installs don't break?
I don't think you want to break installs which don't have that
installed. Booting from USB is officially supported on
using a cmdline of "console=tty1 root=LABEL=writable rootfstype=ext4
rootwait quiet splash
video=HDMI-A-1:1080x1920M@60,rotate=90,panel_orientation=right_side_up
drm.edid_firmware=edid/Waveshare5.5Amoled4.bin fbcon=rotate:1
fsck.mode=force fsck.repair=yes" gives the same issue.
--
You received
Public bug reported:
The hirsute 5.11.x linux-image-raspi kernels boot fine on my rpi4b, but
the 5.13.x kernels freeze before showing anything on the connected hdmi
screen.
Reverting to the 5.11.x hirsute kernels fixes boot.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package:
This was an issue with corruption via an attempted AMDGPU-PRO driver
install.
Cleaning that out fixed the issue.
** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
Status: New => Invalid
** Summary changed:
- No Acceleration w/ amdgpu driver, needs rebuild for newer xorg?
+ Trying to
Public bug reported:
I'm seeing this in the xorg log:
[ 429.296] (II) Loading /usr/lib/xorg/modules/drivers/amdgpu_drv.so
[ 429.296] (II) Module amdgpu: vendor="X.Org Foundation"
[ 429.297]compiled for 1.20.11, module version = 21.0.0
[ 429.297]Module class: X.Org Video Driver
[
Comment #2 also fixed this issue for my MacBookAir4,2 machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925010
Title:
shim-signed 15.4 does not boot on EFI 1.10 systems
To manage
Also got hit with this on my MacBookAir4,2 machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925010
Title:
shim-signed 15.4 does not boot on EFI 1.10 systems
To manage notifications about
This is not a problem in the 5.10 kernels.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919398
Title:
amdgpu error amdgpu_dm_commit_planes.constprop.0+0x9cf/0x9f0
To manage notifications about
upstream bug opened at
https://gitlab.freedesktop.org/drm/amd/-/issues/1531
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #1531
https://gitlab.freedesktop.org/drm/amd/-/issues/1531
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Running 5.11.0-11-lowlatency on radeon RX 5500 XT "[AMD/ATI] Navi 14
[Radeon RX 5500/5500M / Pro 5500M] (rev c5)"
Primary application is Kodi, which freezes on start, requiring the
process to be restarted (sometimes this requires a reboot of the entire
machine.)
dmesg
Arch has patches for kernels through 5.10:
See
https://github.com/archlinux/svntogit-community/tree/packages/broadcom-wl-dkms/trunk
and also
https://github.com/archlinux/svntogit-community/blob/packages/broadcom-wl-dkms/trunk/PKGBUILD
Note the patch for 5.10:
@albertomilone the debian nvidia-legacy-340xx-kernel-dkms (340.108-10)
package builds and installs successfully with the ubuntu 5.10.0-9.10
bootstrap kernel on amd64.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This isn't solved until the patches are added to the ubuntu package,
right?
Please unmark it as solved until debian's package is imported into
ubuntu?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attaching the nvidia 340.108 patch for kernel 5.10 from the
aforementioned link.
** Patch added: "nvidia-340.108-fix-5.10-kernel-compile"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+attachment/5443469/+files/nvidia-340.108-fix-5.10-kernel-compile.patch
Note also a patch for kernel 5.9 there:
https://aur.archlinux.org/cgit/aur.git/tree/0003-kernel-5.9.patch?h
=nvidia-340xx
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896878
Title:
Doesn't
Public bug reported:
dkms.conf can be changed to just use
PATCH[0]="kernel-5.7.patch"
PATCH[1]="buildfix_kernel_5.8.patch"
with patches from archlinux:
https://aur.archlinux.org/cgit/aur.git/tree/buildfix_kernel_5.8.patch?h=nvidia-340xx
and
*** This bug is a duplicate of bug 1878045 ***
https://bugs.launchpad.net/bugs/1878045
Fix also mentioned here:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1878045/comments/7
** This bug has been marked a duplicate of bug 1878045
doing dist-upgrade got error related do Broadcom
*** This bug is a duplicate of bug 1878045 ***
https://bugs.launchpad.net/bugs/1878045
The problem is due to 0028-add-support-for-linux-5.6.patch having many
of a/src/src/... instead of a/src/...
Fixing that patch solves this for me.
--
You received this bug notification because you are a
Thanks! I've submitted a version to intel-gfx mailing list as [RFC PATCH
1/1] Remove DPCD Aux Backlight Control PWM_PIN check after discussions
with Redhat's Lyude Paul.
https://lists.freedesktop.org/archives/intel-
gfx/2020-September/248938.html
--
You received this bug notification because
*** This bug is a duplicate of bug 1894593 ***
https://bugs.launchpad.net/bugs/1894593
** This bug has been marked a duplicate of bug 1894593
Fractional scaling switch doesn't work
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Dmesg: https://paste.ubuntu.com/p/jNCR2qTKWQ/
Also maybe seeing this error:
Sep 15 13:37:15 nocturne gnome-control-c[2021]: file
../panels/display/cc-display-config.c: line 452 (get_fractional_scaling_key):
should not be reached
** Also affects: gnome-control-center (Ubuntu)
Importance:
Public bug reported:
Setting Fractional Scaling in the X11 Gnome Session is working fine. I
can set the 3000x2000 screen to 150%.
In the Gnome-Wayland Session, the Fractional Scaling Toggle doesn't
stick, and I don't see any fractional scaling percentage options show
up.
(Running a slightly
/board-overlays/+/1171922
Discussion of issue & solution: https://github.com/EmbeddedAndroid
/linux-eve/issues/2#issuecomment-561382927
This can be fixed with a simple patch which I have applied successfully to
mainline 5.9-rc5:
https://gist.github.com/satmandu/d6c2192f66cd14525049fd34d356
@vorlon it is in the graphic which shows up in the GUI surrounding the checkbox
to enable -proposed
here:
https://wiki.ubuntu.com/Testing/EnableProposed?action=AttachFile=get=devoptions_1604.png
Thank you @knox for the clarification. This was largely my fault for doing a
's/focal/groovy/g' in
Fully aware that proposed is not supported, and that this may cause
instability.
Just trying to be helpful as per
https://wiki.ubuntu.com/Testing/EnableProposed
"Proposed updates are only for testing updates and providing development
feedback. Enabling this may introduce instability."
This bug
This problem went away once I stopped using groovy-proposed and
(painfully) removed libffi8ubuntu1 and all dependencies which used it.
** Also affects: libffi (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- gnome-shell crashing with Wayland
+ gnome-shell crashing
Public bug reported:
Seeing this on groovy installs after an update.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-shell 3.36.4-1ubuntu2~build1
Uname: Linux 5.8.3-050803-generic x86_64
ApportVersion: 2.20.11-0ubuntu44
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Aug 25
Any resolution on this? Has anyone contacted people who work on util-
linux?
** Also affects: util-linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I suspect this is due to my not having cryptsetup-initramfs installed.
Without that, cryptroot never gets created.
cryptsetup-initramfs's /usr/share/local-top/cryptroot
has this: mkdir -p /cryptroot # might not exist yet if the main system has no
crypttab
--
You received this bug notification
Public bug reported:
boot ends before rpool loads with a failure to find the crypttab file,
which doesn't exist.
Maybe this has a dependency upon a package that makes that?
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: zfs-initramfs 0.8.4-1ubuntu5
ProcVersionSignature: Ubuntu
Clearing out the old docker datasets makes the problem go away. Thanks!
(FYI I stopped using the zfs docker storage driver, and am now using
aufs instead since it seems to feel a lot quicker.) I was using docker-
ce, but will try switching over to docker.io with the zfs storage driver
since that
And apt installs are so much snappier now!
** Changed in: zsys (Ubuntu)
Status: New => 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/1882090
Title:
"ERROR couldn't connect to
Public bug reported:
Have "ERROR couldn't connect to zsys daemon: timed out waiting for
server handshake" error every single time I run apt upgrade.
Example:
Fetched 312 kB in 2s (136 kB/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state
Happens every time I do an apt upgrade. Reported at Bug #1882090:
https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1882090
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875564
Title:
Enhance
Still seeing "ERROR couldn't connect to zsys daemon: timed out waiting
for server handshake " after updating to groovy, but not seeing the
"context deadline exceeded while the daemon is doing work" message any
more.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This suggested policy change is welcome. As per
https://bugs.launchpad.net/ubuntu/+source/linux-
raspi2/+bug/1852119/comments/2 the argument was that the RPI4 only has
4Gb of ram.
"we do not support ZFS unless you have at least 4GB of memory free.
Today the 8Gb RPI4 was announced.
Thanks.
Please consider adding https://github.com/openzfs/zfs/pull/10163 and
https://github.com/openzfs/zfs/pull/10184
When I made my patch series to get zfs 0.84 working on focal here is
what I used:
#0001-Prevent-manual-builds-in-the-DKMS-source.patch
The patch in 6.30.223.271+bdcom-0ubuntu6 doesn't appear to work when
installed on focal:
sudo dpkg -i bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu6_amd64.deb
(Reading database ... 170331 files and directories currently installed.)
Preparing to unpack
FYI this patch is part of the just released 0.8.4 in
https://github.com/openzfs/zfs/tree/zfs-0.8-release as per the patch
pull request: https://github.com/openzfs/zfs/pull/10209
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Linux 5.7 patches have now gone into
https://github.com/openzfs/zfs/tree/zfs-0.8-release with the release of
0.8.4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872373
Title:
zfs patches needed
Here's what I did:
sudo zpool set listsnapshots=on bpool
zfs list -o space -r bpool
That gave me a list of snapshots on pool and told me how big they were,
and then I was able to go in and delete the right snapshot to get space
back.
Hopefully garbage collection will realize this happened and
Because after deleting some bpool snapshots I'm definitely seeing errors when I
run update-grub complaining about missing snapshots.
e.g.
cannot open 'bpool/BOOT/ubuntu_pzg8hb@autozsys_r0tzci': dataset does not exist
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I'm seeing the same issue and can't update my kernel either. Anyone have
a good set of commands to run to clear out the oldest snapshots from
pool (and rpool as well, ideally?)
update-initramfs: Generating /boot/initrd.img-5.4.0-31-lowlatency
Error 24 : Write error : cannot write compressed block
Maybe it makes sense to create a virtual package dependency which can
pull in zfs-dkms for the non-arm64 architectures which get zfsutils-
linux installed?
For instance aufs-dkms is a virtual package which is satisfied by the
official kernel packages.
--
You received this bug notification
FYI it looks like support for 5.7 this will be part of the 0.8.4 release
as per https://github.com/openzfs/zfs/pull/10209
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872373
Title:
zfs patches
The other patches are needed! For instance, there is display corruption
after sleep without one of the other patches.
(That has returned after the other patches were removed.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Great work kelebek333!
Has anybody heard about any usable patches to make this work on 5.7?
./include/linux/cpumask.h:266:9: warning: comparison of integer expressions of
different signedness: ‘int’ and ‘unsigned int’ [-Wsign-compare]
266 | (cpu) < nr_cpu_ids;)
| ^
So until the package gets updated do this:
Add this line to /usr/src/bcmwl-6.30.223.271+bdcom/dkms.conf
PATCH[13]="0028-add-support-for-Linux-5.6.patch"
Save the patch at
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1872908/+attachment/5356260/+files
/broadcom-wl-dkms-arch-patch as this
There is an arch patch for this:
https://git.archlinux.org/svntogit/community.git/commit/trunk?h=packages
/broadcom-wl-dkms=e78ab887e946418baac2abcaad24b9df19f22945
** Attachment added: "patch for 5.6"
This is a script which can be used to update the zfs-dkms package
locally.
I imagine it doesn't make sense to update the final package until later
in the 5.7 rc series...
** Attachment added: "zfs-dkms updater"
Public bug reported:
As per https://github.com/openzfs/zfs/pull/10187 there is now a patch
for Linux 5.7 compat: blk_alloc_queue(). Of course there may be more
patches for the 5.7 series.
I've hacked up the patch to backport it to work with the 0.8.x series.
It appears to work: zfs, 0.8.3,
Definitely still seeing this, but over 12 hours later I can immediately
use the devices again in mainline 5.6.3.
dmesg | grep 'magic\|apple'
[68065.162639] apple *:*:*.*: unknown main item tag 0x0
[68065.163407] apple *:*:*.*: input,hidraw5: BLUETOOTH HID v0.50 Keyboard
[satadru’s keyboard] on
Definitely still get the error message, at least right at first connection,
using mainline 5.6.3 on focal beta:
magicmouse *:*:*:*: unknown main item tag 0x0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think this is the same issue as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1385113
has anybody submitted this upstream to the linux-input mailing list yet?
It's definitely happening with 5.4.0-23-lowlatency on focal beta and my
magicmouse trackpad.
I will try with a mainline kernel
This is resolved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848230
Title:
uboot_rpi_4.bin doesn't show 4Gb RAM on rpi4, needs update to
u-boot/v2019.10
To manage notifications about this
I don't think this is fixed, because now grub.cfg has NO entries in it
aside from that for accessing the bios menu.
(Is this related to corresponding grub-common changes?)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm not sure which package to file a bug report on, but I have multiple
pools, and after this last update, bpool wouldn't mount properly due to
files on /boot, and as a result update-grub updated grub.cfg with no
info about my kernels. :/
--
You received this bug notification because you are a
Public bug reported:
CONFIG_PREEMPT_RCU=y enabled post 5.4.x kernels have __rcu_read_lock
exposed as GPL-ONLY, which breaks zfs compilation on kernels with that
enabled. (Ubuntu low-latency kernels have that enabled IIRC.)
The patch for the .8 series implementing this inside zfs to circumvent
*** This bug is a duplicate of bug 1866377 ***
https://bugs.launchpad.net/bugs/1866377
Nice.
Patch for the lazy:
diff -Npaur a/usr/share/initramfs-tools/hooks/plymouth
b/usr/share/initramfs-tools/hooks/plymouth
--- a/usr/share/initramfs-tools/hooks/plymouth 2020-03-06 12:45:51.563041573
Thanks for the policy clarification. But as I understand it "4 GiB of
memory is recommended for normal performance in basic workloads"
referred to 4Gb of memory in total, not 4gb of free memory.
I'll ask again once there is a device with more than 4Gb of RAM, but
FYI, since the raspberry pi may
1 - 100 of 198 matches
Mail list logo
