For what it is worth, I disabled these in debian/patches/series for my
2.2.0 based ppa at https://launchpad.net/~satadru-
umich/+archive/ubuntu/zfs-experimental/ ...
#ubuntu/0001-Revert-etc-systemd-zfs-mount-generator-serialise-han.patch
#ubuntu/0002-Revert-etc-systemd-zfs-mount-generator-output-t
This patch is incomplete.
The patches necessary are a combination of these:
https://gist.github.com/joanbm/37fd0590f30b41e7e89ade6e242ca16e
https://gist.github.com/joanbm/052d8e951ba63d5eb5b6960bfe4e031a
(with those patches applied, I don't get any errors in my dmesg and the
wireless card works
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 app
See https://github.com/openzfs/zfs/commits/zfs-2.1.5-staging
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1964827
Title:
zfs-linux upstream at 2.1.4, jammy has 2.1.2
Status in zfs
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 Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1964827
Title:
zfs-linux ups
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 impo
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"
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1961801/+attachment/5564828/+files/broadco
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
--- a
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 Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/
(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 a
** 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 Kernel
Packages, whic
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 l
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
Packag
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
AudioDev
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 5.
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: linux-image-raspi
This is not a problem in the 5.10 kernels.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1919398
Title:
amdgpu error amdgpu_dm_commit_planes.constprop.0+0x9cf/0x9f0
Status in linu
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 Kernel
Packages, which is subscr
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 shows
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:
https://github.com/archlinux/svntogi
*** 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 m
mp; 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/d6c2192f66cd14525049fd34d356d71d
Luckily the Ubuntu kernel patches se
/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
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 b
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 5.4.0-34.38
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.
https://www.ra
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
#0002-Check-for-META-and-DCH-consistency-i
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 bcmwl-kernel-source_6.30.223.271+bdcom-0ubun
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 Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1872373
Title:
zfs p
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 Kernel
Packages, which is subscribed to zfs-linux in
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 Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1872373
Title:
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 becaus
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&id=e78ab887e946418baac2abcaad24b9df19f22945
** Attachment added: "patch for 5.6"
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1872908/+attachment/5356260/+files/
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"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1872373/+attachment/53528
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, 5.7.0
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
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 n
ort" of my existing zfs pools.
Rebooted.
The previously imported zpools are not imported at boot!
I am currently using this hacky workaround:
https://gist.github.com/satmandu/4da5e900c2c80c93da38c76537291507
I would expect that local zpools I have manually imported would re-import
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 me
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 th
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 of
Patch updated for 5.6rc3:
https://gist.github.com/satmandu/67cbae9c4d461be0e64428a1707aef1c
Adapted from zfs PR PR #9961 & #10064
https://github.com/openzfs/zfs/pull/9961
https://github.com/openzfs/zfs/pull/10064
$ dkms status
zfs, 0.8.3, 5.6.0-050600rc2-generic, x86_64: installed
zfs, 0
I added a comment to the PR here:
https://github.com/openzfs/zfs/pull/9961#issuecomment-591076133
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1863136
Title:
zfs-dkms will not comp
Thanks. As I understand it there are no new changes needed for 5.5
support though, aside from modifying the META file and rerunning
./autogen.sh.
I've been running with just such changes on arm64 and amd64 (literally
sed -i 's/5.4/5.5/' META) with focal builds and 5.5 kernels for a bit
now with no
(after patching source I had to run ./autogen.sh in the module folder.)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1863136
Title:
zfs-dkms will not compile on kernel 5.6rc1
Stat
Public bug reported:
Bug mentioned here: https://github.com/zfsonlinux/zfs/issues/10001
Patch for zfs master branch here:
https://github.com/zfsonlinux/zfs/pull/9961
Patch modified for zfs-dkms_0.8.3-1ubuntu3 here:
https://paste.ubuntu.com/p/wsS9GFHjyv/
This is working for me in getting a 5.5.x
Public bug reported:
The 4gb RPI4 is more than capable of handling zfs.
( Even zfs root can be enabled manually with arm64 eoan builds using a variant
of the steps at https://github.com/zfsonlinux/zfs/wiki/Ubuntu-18.04-Root-on-ZFS
. )
Currently one has to install zfs-dkms for zfs support, but i
For what it is worth, zfs works quite well for a root fs rpool on a 4Gb
RPI4b.
--
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/1822797
Title:
ZFS module is installed for wrong kern
Thanks all!
Mainline builds of daily and 5.3-rc1 appear to have been generated for
amd64 last night.
--
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/1830961
Title:
Kernels & kernel drive
Any chance someone could get the recipes fixed for the mainline builds,
which also need the -fcf-protection=none retpoline flags added since
they're being built using "schroot -c eoan-amd64"?
(I'm not sure who needs to be looped in for that to happen.)
--
You received this bug notification becau
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: linux-meta (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bu
Thanks @kaihengfeng! I can't believe I missed that. [headdesk]
Indeed I just needed linux-modules-extra installed.
That indeed fixes my issue, which was clearly PEBCAK.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubunt
** Also affects: linux-meta (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1836291
Title:
5.2.0-8-generic regresses KMS edid fil
Public bug reported:
I have the kernel load an EDID file so that when connecting my amd64
machine to a tv and speaker bar through hdmi I get the full setup
information even if the speaker bar and tv might be off.
The relevant kernel cmdline is
"drm.edid_firmware=HDMI-A-1:edid/edid.bin"
In most r
FYI 5.2.0-8-generic in eoan/proposed has 0.8.1
strings /lib/modules/5.2.0-8-generic/kernel/zfs/zfs.ko | grep 0.8
version=0.8.1-1ubuntu5
Also you can install zfs-dkms...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
htt
It looks like this is being addressed in recent linux packages.
As per https://launchpad.net/ubuntu/+source/linux/5.2.0-8.9
"SAUCE: add -fcf-protection=none to retpoline flags"
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubu
The origin of this bug is the change in the gcc-9 package on 26 May
2019. Shouldn't the fcf-protection change there just be reverted?
As per the changelog:
gcc-9 (9.1.0-3) experimental; urgency=medium
* Update to SVN 20190526 (r271629) from the gcc-9-branch.
- Fix PR libgomp/90527, PR c++/
workaround this
issue, which works for arm64 mainline builds, here:
https://gist.github.com/satmandu/b60a804fa2275615c88367bc68e4bad0
As a quick summary of the problem, it appears that these files are
needed in the target architecture to build modules, but are in the
cross-compile host architecture
FYI the mainline arm64 kernels at https://kernel.ubuntu.com/~kernel-
ppa/mainline/v5.1.1/ boot on the 3B running arm64 on disco, with grub-
efi-arm64-bin installed and a commandline of modprobe.blacklist=vc,vc4
(but I haven't tried without using the module blacklist for some time.)
Since the defau
On the flip side, I am able to use dtoverlay=vc4-kms-v3d,cma-256 to boot
my 3B+ on the disco kernel, which appears to allow me to use hardware
accelerated decoding on the RPI.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
63 matches
Mail list logo
