March 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1196797] amdgpu: AMD RX6500XT (Navi24) not yet supported?
by bugzilla_noreply＠suse.com 06 Mar '22

06 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196797 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Can't display properly with |amdgpu: AMD RX6500XT |my new display card AMD |(Navi24) not yet supported? |RX6500XT | -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196797] Can't display properly with my new display card AMD RX6500XT
by bugzilla_noreply＠suse.com 06 Mar '22

06 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196797 http://bugzilla.opensuse.org/show_bug.cgi?id=1196797#c1 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sndirsch(a)suse.com Component|X11 3rd Party Driver |Kernel Assignee|gfx-bugs(a)suse.de |kernel-bugs(a)opensuse.org QA Contact|sndirsch(a)suse.com |qa-bugs(a)suse.de --- Comment #1 from Stefan Dirsch <sndirsch(a)suse.com> --- According to Wikipedia this is a very new card (Release January 2022). So I guess this is not yet supported by our Leap 15.3 kernel. So either you need a newer kernel (KOTD = Kernel of the day), which hopefully supports the GPU already or switch to 1080p framebuffer resolution. Unfortunately I no longer know how to specify this nowadays on the kernel boot line. :-( Please add the output of hwinfo --gfxcard hwinfo --framebuffer Reassigning to kernel component. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196778] amdgpu bug
by bugzilla_noreply＠suse.com 05 Mar '22

05 Mar '22

https://bugzilla.suse.com/show_bug.cgi?id=1196778 https://bugzilla.suse.com/show_bug.cgi?id=1196778#c3 --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- BTW, the hang can be a different problem, so let's concentrate only on the non-working high resolution at first. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196778] amdgpu bug
by bugzilla_noreply＠suse.com 05 Mar '22

05 Mar '22

https://bugzilla.suse.com/show_bug.cgi?id=1196778 https://bugzilla.suse.com/show_bug.cgi?id=1196778#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com Flags| |needinfo?(james(a)sevener.us) --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- Could you check whether the problem persists with the latest 5.17-rc kernel in OBS Kernel:HEAD repo? If it's still reproducible, please check with kernel-vanilla in OBS home:tiwai:kernel:drm-tip, too. The latter is a kernel built from the latest drm-tip git repo. If the problem is still present with drm-tip, we have to report it to the upstream devs, gitlab.freedesktop.org Issues. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196779] Bluetooth adapter not included in modul btusb
by bugzilla_noreply＠suse.com 05 Mar '22

05 Mar '22

https://bugzilla.suse.com/show_bug.cgi?id=1196779 https://bugzilla.suse.com/show_bug.cgi?id=1196779#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |RMurr(a)t-online.de, | |tiwai(a)suse.com Flags| |needinfo?(RMurr(a)t-online.de | |) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- I suppose this isn't supported even by the latest upstream as is? If so, we need to submit the fix patch at first. In anyway, please upload hwinfo output, also the usb-devices output for the corresponding device. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196104] no resume or bad resume after suspend
by bugzilla_noreply＠suse.com 04 Mar '22

04 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196104 http://bugzilla.opensuse.org/show_bug.cgi?id=1196104#c23 --- Comment #23 from Klaus Schneider-Grosch <funedv(a)gmx.de> --- (In reply to Takashi Iwai from comment #22) > Hrm, not sure about crash problem. It might be the crash version included > in Leap 15.3. > > What do you mean "almost works perfectly"? You got this bug even with > 5.16.9, right? Did you have any kernel version that worked with hibernation? Yes, I got this bug with 5.16.x. The reason to change from 5.3.18-150300.59.49-default to 5.16.9 was bad function (I described). Since then I worked only with 5.16.x. "Almost works perfectly" means that I just have this problem with resume after suspense, by the way with other distros too (knoppix 9.1, qtfsarciver live DVD). Resume after hibernation function with OpenSUSE Kernel 5.16.x is perfect. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196744] android apps kernel changes
by bugzilla_noreply＠suse.com 04 Mar '22

04 Mar '22

https://bugzilla.suse.com/show_bug.cgi?id=1196744 https://bugzilla.suse.com/show_bug.cgi?id=1196744#c7 --- Comment #7 from Dead Mozay <dead_mozay(a)opensuse.org> --- (In reply to Takashi Iwai from comment #6) > For your convenience, I created an OBS repo that builds the kernel package > with binder and ashmem enabled. It's being built in OBS > home:tiwai:kernel:android. This should be automatically updated at each > time OBS Kernel:stable gets updated. Let's see whether this works. Great, we'll check if it works or not, thanks. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196744] android apps kernel changes
by bugzilla_noreply＠suse.com 04 Mar '22

04 Mar '22

https://bugzilla.suse.com/show_bug.cgi?id=1196744 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |WONTFIX -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196744] android apps kernel changes
by bugzilla_noreply＠suse.com 04 Mar '22

04 Mar '22

https://bugzilla.suse.com/show_bug.cgi?id=1196744 https://bugzilla.suse.com/show_bug.cgi?id=1196744#c6 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|WONTFIX |FIXED --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- For your convenience, I created an OBS repo that builds the kernel package with binder and ashmem enabled. It's being built in OBS home:tiwai:kernel:android. This should be automatically updated at each time OBS Kernel:stable gets updated. Let's see whether this works. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196744] android apps kernel changes
by bugzilla_noreply＠suse.com 04 Mar '22

04 Mar '22

https://bugzilla.suse.com/show_bug.cgi?id=1196744 https://bugzilla.suse.com/show_bug.cgi?id=1196744#c5 Dead Mozay <dead_mozay(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #5 from Dead Mozay <dead_mozay(a)opensuse.org> --- (In reply to Takashi Iwai from comment #4) > Well, the bottom line is that those drivers can be built as modules. But > the currently those are only built as built-in kernel, and for allowing them > to be built as modules, we need to patch the kernel code. I asked to hack > it by yourself and check whether it works. > > But after writing this, I remembered that I chatted with Ben Hutchings some > time ago about this topic. There are a couple of downstream patches for > Ubuntu to build those as modules: > > https://salsa.debian.org/kernel-team/linux/blob/master/debian/patches/debia… > android-enable-building-ashmem-and-binder-as-modules.patch > > https://salsa.debian.org/kernel-team/linux/blob/master/debian/patches/debia… > export-symbols-needed-by-android-drivers.patch > > However, the problem is that the latter one (to add exported symbols to core > code) would be VERY unlikely accepted by the upstream. The first attempt > failed miserably: > > https://lore.kernel.org/linux-fsdevel/20180730143710.14413-1- > christian(a)brauner.io/T/#m32f56e7f2f3dbb8105009e2fb62ffc71243e89bd > > That is, the binder stuff can almost never be a module, hence we can't go > for it for our standard kernel. > > OTOH, the ashmem seems to have a better chance, as it has little > dependencies on other core parts, but I have no idea whether ashmem alone > would make any sense. Now it��s clear, then there��s no point in ashmem either. Thank you for the clarification. I think the bug can be closed. -- You are receiving this mail because: You are the assignee for the bug.

1 0