Public bug reported:
Binary package hint: xserver-xorg-video-intel
Failure on Dell Mini 9 (945GME).
Upgrade from Karmic alpha 2 (netboot remix installer) kills X.
Added Option"AccelMethod" "uxa" to xorg.conf and X goes to blank
screen.attempts to switch VTs fail.
ProblemType: Bug
Archit
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/28720147/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/28720148/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/28720149/Dependencies.txt
** A
Reverting to kernel 2.6.30 allows the machine to boot with X working
(and UXA enabled).
Any chance of a newer kernel snapshot?
It looks like this may be a kernel issue that has been fixed in git as
per this link:
http://bugzilla.kernel.org/show_bug.cgi?id=13593
** Bug watch added: Linux Kernel
Installing http://kernel.ubuntu.com/~kernel-
ppa/mainline/v2.6.31-rc1-fix1/linux-
image-2.6.31-020631rc1gc0d1117-generic_2.6.31-020631rc1gc0d1117_i386.deb
also fixes this problem!
--
X Crash (UXA)
https://bugs.launchpad.net/bugs/395914
You received this bug notification because you are a member o
Public bug reported:
I these messages constantly in dmesg, and in kern.log:
Jul 11 19:04:39 dellmini9 kernel: [ 1145.712280] [drm:drm_wait_vblank] *ERROR*
failed to acquire vblank counter, -22
Jul 11 19:04:39 dellmini9 kernel: [ 1145.712305] [drm:drm_wait_vblank] *ERROR*
failed to acquire vblank
** Attachment added: "uname-a.log"
http://launchpadlibrarian.net/28921935/uname-a.log
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/28921936/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/28921937/CurrentDmesg.txt
** Attachment
Public bug reported:
Issue is with karmic. It boots up fine aside from the progress
indicator not working.
Still not working as of today's 2.6.31-3-generic kernel.
dmesg error:
[2.876958] <6>usplash[918]: segfault at b7fd8530 ip 001344f0 sp bfca1660
error 6 in libusplash.so.0[11+2c000
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/29156982/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/29156992/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/29156994/Dependencies.txt
** A
*** This bug is a duplicate of bug 477106 ***
https://bugs.launchpad.net/bugs/477106
** This bug is no longer a duplicate of bug 436729
[Dell Inc. Inspiron 910] suspend/resume failure when SD card is mounted
** This bug has been marked a duplicate of bug 477106
[regression] lucid alpha-2
*** This bug is a duplicate of bug 477106 ***
https://bugs.launchpad.net/bugs/477106
** This bug is no longer a duplicate of bug 436729
[Dell Inc. Inspiron 910] suspend/resume failure when SD card is mounted
** This bug has been marked a duplicate of bug 477106
[regression] lucid alpha-2
*** This bug is a duplicate of bug 477106 ***
https://bugs.launchpad.net/bugs/477106
** This bug is no longer a duplicate of bug 436729
[Dell Inc. Inspiron 910] suspend/resume failure when SD card is mounted
** This bug has been marked a duplicate of bug 477106
[regression] lucid alpha-2
*** This bug is a duplicate of bug 477106 ***
https://bugs.launchpad.net/bugs/477106
** This bug is no longer a duplicate of bug 436729
[Dell Inc. Inspiron 910] suspend/resume failure when SD card is mounted
** This bug has been marked a duplicate of bug 477106
[regression] lucid alpha-2
*** This bug is a duplicate of bug 477106 ***
https://bugs.launchpad.net/bugs/477106
** This bug is no longer a duplicate of bug 436729
[Dell Inc. Inspiron 910] suspend/resume failure when SD card is mounted
** This bug has been marked a duplicate of bug 477106
[regression] lucid alpha-2
*** This bug is a duplicate of bug 477106 ***
https://bugs.launchpad.net/bugs/477106
** This bug is no longer a duplicate of bug 464712
Black screen + freeze when suspending or hibernating with mounted SD Card
** This bug has been marked a duplicate of bug 477106
[regression] lucid alpha
*** This bug is a duplicate of bug 477106 ***
https://bugs.launchpad.net/bugs/477106
** This bug is no longer a duplicate of bug 464712
Black screen + freeze when suspending or hibernating with mounted SD Card
** This bug has been marked a duplicate of bug 477106
[regression] lucid alpha
*** This bug is a duplicate of bug 477106 ***
https://bugs.launchpad.net/bugs/477106
** This bug is no longer a duplicate of bug 464712
Black screen + freeze when suspending or hibernating with mounted SD Card
** This bug has been marked a duplicate of bug 477106
[regression] lucid alpha
*** This bug is a duplicate of bug 477106 ***
https://bugs.launchpad.net/bugs/477106
** This bug is no longer a duplicate of bug 464712
Black screen + freeze when suspending or hibernating with mounted SD Card
** This bug has been marked a duplicate of bug 477106
[regression] lucid alpha
*** This bug is a duplicate of bug 477106 ***
https://bugs.launchpad.net/bugs/477106
** This bug is no longer a duplicate of bug 436729
[Dell Inc. Inspiron 910] suspend/resume failure when SD card is mounted
** This bug has been marked a duplicate of bug 477106
[regression] lucid alpha-2
*** This bug is a duplicate of bug 477106 ***
https://bugs.launchpad.net/bugs/477106
** This bug has been marked a duplicate of bug 477106
[regression] lucid alpha-2 and earlier freeze upon suspend with sd card
plugged in with some hardware
--
[Dell Inc. Inspiron 910] suspend/resume fail
*** This bug is a duplicate of bug 477106 ***
https://bugs.launchpad.net/bugs/477106
** This bug is no longer a duplicate of bug 464712
Black screen + freeze when suspending or hibernating with mounted SD Card
** This bug has been marked a duplicate of bug 477106
[regression] lucid alpha
*** This bug is a duplicate of bug 477106 ***
https://bugs.launchpad.net/bugs/477106
** This bug is no longer a duplicate of bug 464712
Black screen + freeze when suspending or hibernating with mounted SD Card
** This bug has been marked a duplicate of bug 477106
[regression] lucid alpha
*** This bug is a duplicate of bug 477106 ***
https://bugs.launchpad.net/bugs/477106
** This bug is no longer a duplicate of bug 464712
Black screen + freeze when suspending or hibernating with mounted SD Card
** This bug has been marked a duplicate of bug 477106
[regression] lucid alpha
I believe this got fixed in a later release. This can be closed.
..
On Mar 14, 2010, at 1:11 AM, Jeremy Foshee
wrote:
> Hi satmandu,
>
> This bug was reported a while ago and there hasn't been any activity
> in
> it recently. We were wondering if this is still an issue
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 thi
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 notification
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
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.
https://bugs.launchpad.net/bugs/190
@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.
https://bugs.launchp
Public bug reported:
The mainline ARM64 kernels have CONFIG_EFI_ARMSTUB=y and are able to be
used to boot with u-boot and 64-bit Tiano Core UEFI launched grub. The
default kernel config for linux-raspi2 just needs that to be able to do
so as well.
Being able to use grub to boot the raspberry pi m
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863136
Title:
zfs-dkms will not compile on kernel 5.6
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
Public bug reported:
u-boot-rpi:arm64 installs uboot_rpi_4.bin into /boot/firmware and uses
that to boot as per entries in /boot/firmware/config.txt
While this version boots arm64 eoan using a recent rpi kernel, it
doesn't show all 4Gb of RAM on the 4GB versions of the rpi4, only
showing 1Gb.
Up
FYI ram was limited to 1Gb to avoid issues with DMA since the DMA needs
to be restricted to the first 1Gb of RAM.
FYI mainline u-boot 2010/v2019.10 boots just fine with 4GB made
available when using rpi_4_defconfig . No patching is needed.
--
You received this bug notification because you are a
Whoops, I meant mainline u-boot using tag v2019.10.
(The ram restriction was more complicated on arm64 since there was some
bounce buffer voodoo that needed to be done, IIRC.)
git clone --depth 1 --branch v2019.10 https://github.com/u-boot/u-boot.git
cd u-boot
ARCH=arm64 CROSS_COMPILE=aarch64-lin
Public bug reported:
install from Oct 14 live installer failed.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubiquity 19.10.20
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVer
Did a "sudo apt update ; sudo apt dist-upgrade -y" before running
ubiquity.
I did a chroot to /target, and then here's the error I get when running
"update-grub", which is the command that failed:
cannot open 'This:' no such pool
zfs properties:
https://paste.ubuntu.com/p/86jzxpgZsG/
relev
** Summary changed:
- eoan zfs install fails w/ grub error
+ experimental zfs install fails w/ grub error
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848399
Title:
experimental zfs install fails
/boot/grub/grub.cfg on BOOT doesn't seem to get populated, but there was
a grub.cfg.new which I was able to copy over.
Upon boot initramfs and kernel load from BOOT, but rpool fails to mount
and initram drops to shell.
doing this at initramfs prompt lets me login:
zpool import -R /root -N rpo
I'm only getting a grub.cfg.new with useful information when I move
/etc/grub.d/10_linux_zfs to /etc/grub.d/10_linux_zfs.old
Default grub.cfg generated:
https://paste.ubuntu.com/p/snQKzDh8Kg/
With
https://paste.ubuntu.com/p/m5w4mTrPVQ/
Looks like /etc/grub.d/10_linux_zfs is the culprit here.
*
For what it is worth I also have other zfs pools (from other non-boot
drives) on my system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848399
Title:
experimental zfs install fails w/ grub error
Looks like this is an edge case due to some of my pools having features
which are slated for support after the zfs-0.8.x series.
Running 10_linux_zfs with -x:
https://paste.ubuntu.com/p/x9cCwS3Y7S/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
"zpool import -f -a -o cachefile=none -N" is throwing an error when a
zpool isn't importable.
Changing this line:
zpool import -f -a -o cachefile=none -N 2>/dev/null
to
zpool import -f -a -o cachefile=none -N 2>/dev/null || true
Allows update-grub to succeed.
There's still an error, but i
I have log_spacemap enabled.
zpool import -f -a -o cachefile=none -N
"This pool uses the following feature(s) not supported by this system:
com.delphix:log_spacemap (Log metaslab changes on a single spacemap and
flush them periodically.)
All unsupported features are only required for writ
FYI:
One can replace the "zpool import -f -a -o cachefile=none -N" line with this:
local pipe="/tmp/zpool_pipe"
no_import_pools=$(mkfifo ${pipe}; zpool import -f -a -o cachefile=none -N
2> ${pipe} | cut -d \' -f 2 ${pipe}; rm ${pipe})
If one wants a list of the pools which can not be imp
This patch was added to the nvidia-340 package in 340.107-0ubuntu5 as
per http://changelogs.ubuntu.com/changelogs/pool/restricted/n/nvidia-
graphics-drivers-340/nvidia-graphics-drivers-
340_340.107-0ubuntu7/changelog so this bug can be marked as resolved.
--
You received this bug notification bec
If this is still relevant, the easiest workaround for using the
raspberry pi bootloader directly and bypassing u-boot is to do the
following. (This is actually useful if you use a custom kernel, since
the needed dtb file for u-boot may not be the one you want to use for
your custom kernel.)
Do NOT
Whoops! Need an "exit 0" at the end of that last file.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811984
Title:
flash-kernel 3.90ubuntu3.18.10.1 fails with mkimage: not found if no
uboot is u
Here's a script to set that up:
https://gist.github.com/satmandu/4266de009e54146ef55833e7cae8de25
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811984
Title:
flash-kernel 3.90ubuntu3.18.10.1
Public bug reported:
The /etc/apcupsd/apcupsd.conf lists this:
# To get apcupsd to work, in addition to defining the cable
# above, you must also define a UPSTYPE, which corresponds to
# the type of UPS you have (see the Description for more details).
# You must also specify a DEVICE, sometimes r
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
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.
https://bugs.l
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 bug
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
*** 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
-
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
The additional patch needed can be modeled off the one at
https://bugs.archlinux.org/task/62610 labeled as nvidia-340xx.patch
I've updated the patch to be additive on top of the
buildfix_kernel_5.0.patch
** Patch added: "buildfix_kernel_5.1.patch"
https://bugs.launchpad.net/ubuntu/+source/nv
There's actually a second patch that is recommended as per the libreelec
tree:
https://github.com/LibreELEC/LibreELEC.tv/blob/9012226b40baa26241069317fdce6174935ca71b/packages/x11/driver/xf86
-video-nvidia-legacy/patches/xf86-video-nvidia-legacy-02-fix-
linux-5.1.patch
I've combined both patches.
This is the patch from debian for this issue. The driver seems to
compile fine with it.
** Patch added: "kmem_cache_create_usercopy.patch"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1802622/+attachment/5264097/+files/kmem_cache_create_usercopy.patch
--
You re
Public bug reported:
Compiling kernels & kernel modules fails due to these errors:
./include/linux/compiler.h:193:1: error: ‘-mindirect-branch’ and ‘-fcf-
protection’ are not compatible
(This happens with any kernel modules.)
This appears to be due to the changes in 9.1.0-3ubuntu1 enabling -fc
I saw this as well after rebooting.
I was able to manually mount my home folder using the command this
generates:
mount | grep rpool/USERDATA/ | head -1 | \
awk -F '_' '{print $2}' | awk -v user=$USER \
'{print "sudo zfs mount rpool/USERDATA/" user "_"$1}'
--
You received this bug notificatio
Public bug reported:
Error reported during build, but dkms reports successful build.
Dkms build appears to complete successfully despite error reports, so
maybe only a cosmetic error during the build process?
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: nvidia-340 340.107-0ubuntu7
ProcV
Public bug reported:
Installed ubuntu 19.10 onto a zfs bpool/rpool.
Installed zsys.
Did a "zpool import" 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.co
You can remove that property thus:
sudo zfs inherit org.zsys:bootfs-datasets
rpool/USERDATA/_
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849179
Title:
canmount property switches to noauto in us
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822797
Title:
ZFS module is installed for wrong kernel on arm64-raspi3 s
Public bug reported:
Running on arm64 eoan build with kernel from raspberry pi folks (
4.19.71-v8-g6de367fd7 ) on a rpi4.
lsb_release -rd
Description:Ubuntu Eoan Ermine (development branch)
Release:19.10
With wpasupplicant 2.29, wifi comes up on boot, but then drops out shortly
the
** Description changed:
Running on arm64 eoan build with kernel from raspberry pi folks (
4.19.71-v8-g6de367fd7 ) on a rpi4.
lsb_release -rd
Description:Ubuntu Eoan Ermine (development branch)
Release:19.10
-
- With wpasupplicant 2.29, wifi comes up on boot, but then drops
Here is the wpa supplicant log, gathered as per:
https://gist.github.com/wch/8305204#gistcomment-2477237
https://paste.ubuntu.com/p/Nm7G6STc22/
Note there are 3 sections.
The first section starts with "wpa_supplicant v2.6"
When I upgrade to 2.9 you can see this start with "wpa_supplicant v2.9"
Wh
I'm still seeing this issue on resume from sleep today on my updated
19.10 setup with gnome-shell 3.34.0-1ubuntu1.
For what it is worth I also see this in my dmesg at boot:
[ 19.404177] gnome-shell[3485]: segfault at 18 ip 7f82407d4924 sp
7ffeb4e50f08 error 4 in libmutter-5.so.0.0.0[7f
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
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 subscribed
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 th
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 you
*** 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
*** 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
-
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
https://gitlab.manjaro.org/packages/extra/linux57-extr
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
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 compil
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
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.
https://bugs.launchpad.net/
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 *:
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
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
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
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, wh
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 tim
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 i
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 zs
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
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
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.
https://bugs.launchpad.net/b
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/
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
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;)
| ^
./include/li
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.
https://bu
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
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,
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 fi
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 for
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.
https://b
1 - 100 of 195 matches
Mail list logo
