October 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1231167] Enable CONFIG_SCSI_UFS_QCOM for UFS support on QCOM platforms
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231167 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |afaerber(a)suse.com, | |andrea.porta(a)suse.com, | |ivan.ivanov(a)suse.com, | |stanimir.varbanov(a)suse.com, | |tiwai(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1230149] PPC64LE: ioctl(LOOP_SET_BLOCK_SIZE) accepts values larger than pagesize
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230149 https://bugzilla.suse.com/show_bug.cgi?id=1230149#c7 --- Comment #7 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Coly Li from comment #6) > And for Tumbleweed kernel, it is always from Factory of the latest mainline > kernel. Now I see the master branch is updated to 6.12-rc1, so I assume the > fixing patch is included in Tumbleweed kernel already. Tumbleweed sources from the stable branch, so 6.11. I believe the commit is not in 6.11 yet? (You didn't share the SHA and I don't see it in. Neither in -next.) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1230149] PPC64LE: ioctl(LOOP_SET_BLOCK_SIZE) accepts values larger than pagesize
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230149 https://bugzilla.suse.com/show_bug.cgi?id=1230149#c6 --- Comment #6 from Coly Li <colyli(a)suse.com> --- (In reply to Coly Li from comment #5) > (In reply to Avinesh Kumar from comment #4) > > Looks like this issue is being addressed in - > > https://lore.kernel.org/all/20240827081757.37646-1-liwang@redhat.com/ > > Thanks for the notice. After it is merged into upstream kernel, I will pick > it for necessary kernel(s). OK now they are in mainline kernel. I checked SLE15-SP6 we don't have the breaker commit fe3d508ba95b ("block: Validate logical block size in blk_validate_limits()"), so it is unnecessary to backport the fix at this moment. And for Tumbleweed kernel, it is always from Factory of the latest mainline kernel. Now I see the master branch is updated to 6.12-rc1, so I assume the fixing patch is included in Tumbleweed kernel already. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231067] X11:Drivers:Video:Redesign/nvidia-open-driver-G06-signed: Bug - driver does not function after kernel 6.10
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231067 https://bugzilla.suse.com/show_bug.cgi?id=1231067#c11 --- Comment #11 from pallas wept <pallaswept(a)proton.me> --- > No, NVIDIA claims 550.120 has fixed that issue. Sorry, I should have said, all of the *available* drivers. I mean to say, all the ones I could install from the oss, nvidia or cuda repos. I anticipate that it will be fixed in .120. > > With nvidia_drm.fbdev=1 in the kernel command line (and conf), boots into > > plasma, without corruption, but with 100% CPU usage and unusably slow > I guess you're now implicitely using > nvidia-drm modeset=0 nvidia_drm.fbdev=1 In this state, fbdev is added to stock, that is the only change. So, modeset=1 should be set by the conf file here. fbdev=1 should be set twice, once in boot command, once in conf file. This seems true, as with the 550 driver, I see the boot message that the param is not supported and has been ignored, twice. Note that the behaviour is different with fbdev=1 specified in both places, compared to specified only in the conf file. > 550 closed driver (nvidia repo) Unmodified is just like 560 > With nvidia_drm.fbdev=1 in the kernel command line (and conf), boots into > plasma, seems normal > This sounds unexpected. It is most unexpected. This is the real problem I am reporting here, the behaviour of the boot command and modprobe conf files seems inconsistent. I don't even know if it's limited to the nvidia packages. We just see it here, because of the fbdev bug in the driver. It's probably nothing, but it is potentially major, so I thought I should follow up. > Mabye you didn't run 'dracut -f' after changinge the config? In that scenario, I set the boot command with yast, and I'm fairly sure that rebuilds the initrd, as dracut would? I did not change the modprobe conf, just kept the stock modeset=1 fbdev=1 from the existing conf file. -- You are receiving this mail because: You are on the CC list for the bug.

1 0