** Changed in: firefox (Ubuntu)
Status: Triaged => Invalid
--
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/2083538
Title:
amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:3
*** This bug is a duplicate of bug 2084046 ***
https://bugs.launchpad.net/bugs/2084046
This is Intel Meteor Lake, so bug 2084046 instead.
** This bug is no longer a duplicate of bug 2083329
[regression] Phantom "Unknown Display" shown in Settings since kernel 6.11
and 6.8.0-51
** This bu
** Summary changed:
- [regression] Phantom "Unknown Display" shown in Settings since kernel 6.11
and 6.8.0-51
+ [regression] [nvidia] Phantom "Unknown Display" shown in Settings since
kernel 6.11 and 6.8.0-51
--
You received this bug notification because you are a member of Kernel
Packages, wh
kernels 6.8.0-50 and 6.8.0-51 have regressed, for the same reasons as
kernel 6.11: the simple-framebuffer device in sysfs is no longer at
/sys/devices/platform/simple-framebuffer.0 (comment #99)
But for some reason, I only get a phantom display in Wayland. Instead,
comment #29 previously mentioned
Paolo, any idea what commit has regressed noble?
Nothing stands out looking at drivers/drm/i915
--
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/2084046
Title:
[i915] Phantom "Unknown" di
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Oracular)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
* Installed the firefox snap from --channge=edge, which is core24
* Verified following the test plan that it would reproduce the crash
* Added noble-proposed to the mesa-2404 recipe
package-repositories:
- type: apt
url: http://archive.ubuntu.com/ubuntu
suites: [noble-proposed]
com
Thank you for the bug report.
Could you try this solution from the forums?
https://askubuntu.com/a/1315513
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: xorg (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Pa
* Added jammy-proposed to the gnome-42-2204 snapcraft recipe
package-repositories:
- type: apt
url: http://archive.ubuntu.com/ubuntu
suites: [jammy-proposed]
components: [main, universe]
key-id: F6ECB3762474EDA9D21B7022871920D1991BC93C
key-server: keyserver.ubuntu.com
$ snapc
Any idea why the `mesa-va-drivers` binary package does not have a
`23.2.1-1ubuntu3.1~22.04.3` build in proposed, while all the other
binary packages that mesa produces do?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ht
Ahh, pardon, I didn't realize that's a universe package :o
--
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/2083538
Title:
amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 /
** Description changed:
- [Summary]
- On HP ZBook Fury G11 platform preloaded with Ubuntu 22.04. The windowing
system in "Settings -> About" is Xorg. After doing kernel upgrade from 6.5-oem
to 6.8-hwe, windowing system become Wayland.
+ [ Impact ]
+ On some nvidia hybrid systems, like the HP
kernel/drivers people, any idea how this would happen?
** Summary changed:
- External HDMI does not work after dist upgrade
+ Nvidia driver changed to nouveau after dist upgrade to oracular
** Also affects: nvidia-graphics-drivers-560 (Ubuntu)
Importance: Undecided
Status: New
** No l
> the interesting bit is that my i915 GPU is marked as card1, and not
card0 (e.g. simpledrm was loaded earlier, attached as card0 but later
unloaded?)
Yes, that's what happens.
As soon as i195 registers fb0, simpledrm is unloaded:
[ 280.175042] i915 :00:02.0: [drm] fb0: i915drmfb frame buffer
See https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968929
The verification of the gdm update that was supposed to make Wayland the
default option was not done correctly:
We can see that all comments between #37 and #45 mention that Xorg was still
their default but that they now had the opt
Actually, I don't think Wayland was disabled but just not the default.
So we need another explanation. Luckily I got another explanation :)
Both the default Xorg and the default Wayland sessions are called
"ubuntu.desktop" (under /usr/share/xsessions/ and /usr/share/wayland-sessions/
respectivel
> The default session type is meant to be remembered. So GDM's preference of
> default should actually be irrelevant if the user has ever logged in prior to
> the kernel update.
>
> If previous successful logins used Xorg and suddenly it's going to Wayland
> then perhaps the attempt to use Xorg
** Changed in: gdm3 (Ubuntu)
Status: New => In Progress
** Changed in: gdm3 (Ubuntu)
Assignee: (unassigned) => Alessandro Astone (aleasto)
** Changed in: gdm3 (Ubuntu)
Milestone: None => jammy-updates
--
You received this bug notification because you are a member
Analysis from 201912_27623_journal_log.txt
Early on during boot we see:
kernel: EDID block 0 (tag 0x00) checksum is invalid, remainder is 61
kernel: [00] BAD 00 ff ff ff ff ff ff 00 04 69 c4 24 cc 83 03 00
kernel: [00] BAD 2c 18 01 03 80 35 1e 78 2a a0 a5 a6 56 52 9d 27
kernel:
https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+build/29164342 has the exfat module in linux-
modules-extra
** Tags removed: verification-needed-noble-linux-hwe-6.11
** Tags added: verification-done-noble-linux-hwe-6.11
--
You received this bug notification because you are a m
** Description changed:
+ [ Impact ]
+
+ * amdgpu changes in kernel 6.11 make VAAPI video playback crash the GPU
+ and bring down the whole system.
+
+ * A fix was shipped in mesa 24.2, which is already in Oracular - the
+ only version with kernel 6.11 currently, but snaps bundle their own
+ v
Yeah I'll handle the SRU template.
Please coordinate the upload with tjaalton who's looking into the raspi
enablement patches.
--
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/2083538
Title
Proposing a backport to jammy
** Patch added: "mesa_23.2.1-1ubuntu3.1~22.04.3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2083538/+attachment/5826285/+files/mesa_23.2.1-1ubuntu3.1~22.04.3.debdiff
--
You received this bug notification because you are a member of Kernel
Packa
ntu Jammy)
Assignee: (unassigned) => Alessandro Astone (aleasto)
** Changed in: mesa (Ubuntu Noble)
Status: New => In Progress
** Changed in: mesa (Ubuntu Noble)
Assignee: (unassigned) => Alessandro Astone (aleasto)
** Changed in: mesa (Ubuntu)
Status: In Pro
Bisected:
https://gitlab.freedesktop.org/mesa/mesa/-/commit/bceb2328c48a3eb8a9039911393fb2a7c23d5ad1
It fixes both green artifacts and crashing
** Changed in: mesa (Ubuntu)
Status: New => In Progress
** Changed in: firefox (Ubuntu)
Status: New => Triaged
** Bug watch added: gitlab
I don't think there's interest in upgrading mesa in jammy at this point
so here comes a 4-versions-across bisect 😰
--
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/2083538
Title:
amdgpu: [
Indeed installing mesa 24.2 in the snap resolves the issue.
However the patch that was linked in the mesa bug alone does not:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29124
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: mesa (Ubuntu)
Assignee: (unassigned) => Alessandro Astone (aleasto)
** Changed in: firefox (Ubuntu)
Assignee: (unassigned) => Alessandro Astone (aleasto)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
I cannot reproduce with the prebuilt firefox tarball from upstream,
running on oracular with mesa 24.2.3 (and LLVM 19)
--
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/2083538
Title:
amdgp
I'm hitting the same issue `amdgpu: [mmhub] page fault (src_id:0 ring:8
vmid:1 pasid:32785)` when playing twitter videos in the firefox snap
through VAAPI -- media.ffmpeg.vaapi.enabled=true in about:config.
The firefox snap uses mesa 23.2.1 from jammy and that hasn't changed in
a while.
I get no
We cannot just globally enable NVreg_EnableS0ixPowerManagement as, per nvidia's
documentation, it requires that "both the platform and the GPU support
S0ix-based power management", which my card does not for example.
It might be harmless to enable it even if the card does not support S0ix, but
i
@Daniel I know you've been working to make sure that the 470 driver
still works well in mutter despite knowing it would be EOL by now,
considering that it enables hardware that the newer drivers dropped.
So were you aware of this change?
--
You received this bug notification because you are a me
> That's bug 2062082 but I'm not sure how much it matters on Jammy.
There's no fallback-to-zink in jammy, so it would fall back to swrast instead.
However that's an issue for single-NVIDIA systems, while on hybrids it should
pick the integrated GPU.
--
You received this bug notification because
** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
Assignee: (unassigned) => Alessandro Astone (aleasto)
** Changed in: nvidia-graphics-drivers-525 (Ubuntu)
Status: Triaged => Won't Fix
** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
Assignee: (unassigned) =&
I get good performance with Nvidia 560 on both kernel 6.11.0 and 6.8.0.
This was a fresh install of Oracular, using a Pascal card.
--
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/2081140
Ti
> In 'NVIDIA Settings' it looks like the reason might be a lack of power
profiles ("Performance Levels").
I don't see those in the 550 driver either though.
Remembering that 560 is the first driver we ship with Wayland explicit-
sync support, I wonder if __NV_DISABLE_EXPLICIT_SYNC=1 changes the
b
> Same issue in 535. Is it the new kernel perhaps?
Oh. Okay then...
--
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/2081140
Title:
[regression] Very poor performance in Nvidia Wayland se
*** This bug is a duplicate of bug 1965563 ***
https://bugs.launchpad.net/bugs/1965563
> NVIDIA does intend to eventually allow egl-wayland to work on hybrid
systems, but I don't see any time commitment.
Scratch that, it seems supported by setting __NV_PRIME_RENDER_OFFLOAD.
Which switcheroo-c
** Changed in: linux (Ubuntu Oracular)
Status: Triaged => Fix Committed
--
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/2076428
Title:
Enable CONFIG_EXFAT_FS in s390x too
Status i
>From the GLVND documentation:
> EGL can't rely on asking an X server for a vendor name like GLX can,
so instead, it enumerates and loads every available vendor library.
Loading every vendor is also needed to support extensions such as
EGL_EXT_device_enumeration.
> When the application calls eglG
Verified [ Regression Test Plan - Virtual Machines ] with ubuntu-
drivers-common 1:0.9.6.2~0.22.04.7 on Ubuntu 22.04.4 LTS
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bu
Verified [ Regression Test Plan - Intel/AMD graphics ] with ubuntu-
drivers-common 1:0.9.7.6ubuntu3.1 on Ubuntu 24.04.1 LTS on an AMD
thinkpad.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://
Verified [ Regression Test Plan - Virtual Machines ] with ubuntu-drivers-common
1:0.9.7.6ubuntu3.1 on Ubuntu 24.04 LTS by using KVM:
```
```
Even with nvidia-driver-535 or nvidia-driver-550 installed, the system
has kept access to SimpleDRM and can still boot a Wayland session.
--
You rece
** Description changed:
[ Impact ]
After installing Nvidia driver 545 on a single (27") monitor system,
Settings shows a phantom 46" monitor of the same resolution.
It looks like the phantom monitor is /dev/dri/card0 which is still
controlled by simpledrm, while Nvidia uses /dev/dr
** Description changed:
[ Impact ]
After installing Nvidia driver 545 on a single (27") monitor system,
Settings shows a phantom 46" monitor of the same resolution.
It looks like the phantom monitor is /dev/dri/card0 which is still
controlled by simpledrm, while Nvidia uses /dev/dr
** Description changed:
[ Impact ]
After installing Nvidia driver 545 on a single (27") monitor system,
Settings shows a phantom 46" monitor of the same resolution.
It looks like the phantom monitor is /dev/dri/card0 which is still
controlled by simpledrm, while Nvidia uses /dev/dr
Very early in the boot process SimpleDRM will claim card0 as a DRM device
backed by the BIOS framebuffer, mostly useful to offer Wayland-friendly
graphics on systems without a GPU.
When the system loads a GPU driver that brings its own framebuffer, it will
automatically unload SimpleDRM. The nvi
As far as I can see there's no s390x build, so nothing to verify
** Tags removed: verification-needed-noble-linux-oem-6.11
** Tags added: verification-done-noble-linux-oem-6.11
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubun
** Also affects: linux (Ubuntu Oracular)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2076428
Title:
Enable CONFIG_EXFAT_FS in s390x too
St
** Description changed:
- There doesn't seem to be a specific reason for keeping this disabled in
- s390x.
-
The Desktop Team is looking to MIR exfatprogs and include it in the Desktop
image.
Autopkgtests detected missing support for CONFIG_EXFAT_FS in s390x when
trying to mount an exfat im
Public bug reported:
There doesn't seem to be a specific reason for keeping this disabled in
s390x.
The Desktop Team is looking to MIR exfatprogs and include it in the Desktop
image.
Autopkgtests detected missing support for CONFIG_EXFAT_FS in s390x when trying
to mount an exfat image.
We shou
** Changed in: ubuntu-drivers-common (Ubuntu Noble)
Status: In Progress => Fix Committed
** Changed in: ubuntu-drivers-common (Ubuntu Jammy)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nv
52 matches
Mail list logo
