October 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1189423] New: VUL-0: tensorflow2: update to 2.6.0, multiple CVEs
by bugzilla_noreply＠suse.com 18 Jun '22

18 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1189423 Bug ID: 1189423 Summary: VUL-0: tensorflow2: update to 2.6.0, multiple CVEs Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: cgoll(a)suse.com Reporter: gabriele.sonnu(a)suse.com QA Contact: security-team(a)suse.de Found By: --- Blocker: --- excerpt from the changelog: Security Fixes a heap out of bounds access in sparse reduction operations (CVE-2021-37635) Fixes a floating point exception in SparseDenseCwiseDiv (CVE-2021-37636) Fixes a null pointer dereference in CompressElement (CVE-2021-37637) Fixes a null pointer dereference in RaggedTensorToTensor (CVE-2021-37638) Fixes a null pointer dereference and a heap OOB read arising from operations restoring tensors (CVE-2021-37639) Fixes an integer division by 0 in sparse reshaping (CVE-2021-37640) Fixes a division by 0 in ResourceScatterDiv (CVE-2021-37642) Fixes a heap OOB in RaggedGather (CVE-2021-37641) Fixes a std::abort raised from TensorListReserve (CVE-2021-37644) Fixes a null pointer dereference in MatrixDiagPartOp (CVE-2021-37643) Fixes an integer overflow due to conversion to unsigned (CVE-2021-37645) Fixes a bad allocation error in StringNGrams caused by integer conversion (CVE-2021-37646) Fixes a null pointer dereference in SparseTensorSliceDataset (CVE-2021-37647) Fixes an incorrect validation of SaveV2 inputs (CVE-2021-37648) Fixes a null pointer dereference in UncompressElement (CVE-2021-37649) Fixes a segfault and a heap buffer overflow in {Experimental,}DatasetToTFRecord (CVE-2021-37650) Fixes a heap buffer overflow in FractionalAvgPoolGrad (CVE-2021-37651) Fixes a use after free in boosted trees creation (CVE-2021-37652) Fixes a division by 0 in ResourceGather (CVE-2021-37653) Fixes a heap OOB and a CHECK fail in ResourceGather (CVE-2021-37654) Fixes a heap OOB in ResourceScatterUpdate (CVE-2021-37655) Fixes an undefined behavior arising from reference binding to nullptr in RaggedTensorToSparse (CVE-2021-37656) Fixes an undefined behavior arising from reference binding to nullptr in MatrixDiagV* ops (CVE-2021-37657) Fixes an undefined behavior arising from reference binding to nullptr in MatrixSetDiagV* ops (CVE-2021-37658) Fixes an undefined behavior arising from reference binding to nullptr and heap OOB in binary cwise ops (CVE-2021-37659) Fixes a division by 0 in inplace operations (CVE-2021-37660) Fixes a crash caused by integer conversion to unsigned (CVE-2021-37661) Fixes an undefined behavior arising from reference binding to nullptr in boosted trees (CVE-2021-37662) Fixes a heap OOB in boosted trees (CVE-2021-37664) Fixes vulnerabilities arising from incomplete validation in QuantizeV2 (CVE-2021-37663) Fixes vulnerabilities arising from incomplete validation in MKL requantization (CVE-2021-37665) Fixes an undefined behavior arising from reference binding to nullptr in RaggedTensorToVariant (CVE-2021-37666) Fixes an undefined behavior arising from reference binding to nullptr in unicode encoding (CVE-2021-37667) Fixes an FPE in tf.raw_ops.UnravelIndex (CVE-2021-37668) Fixes a crash in NMS ops caused by integer conversion to unsigned (CVE-2021-37669) Fixes a heap OOB in UpperBound and LowerBound (CVE-2021-37670) Fixes an undefined behavior arising from reference binding to nullptr in map operations (CVE-2021-37671) Fixes a heap OOB in SdcaOptimizerV2 (CVE-2021-37672) Fixes a CHECK-fail in MapStage (CVE-2021-37673) Fixes a vulnerability arising from incomplete validation in MaxPoolGrad (CVE-2021-37674) Fixes an undefined behavior arising from reference binding to nullptr in shape inference (CVE-2021-37676) Fixes a division by 0 in most convolution operators (CVE-2021-37675) Fixes vulnerabilities arising from missing validation in shape inference for Dequantize (CVE-2021-37677) Fixes an arbitrary code execution due to YAML deserialization (CVE-2021-37678) Fixes a heap OOB in nested tf.map_fn with RaggedTensors (CVE-2021-37679) Fixes a division by zero in TFLite (CVE-2021-37680) Fixes an NPE in TFLite (CVE-2021-37681) Fixes a vulnerability arising from use of unitialized value in TFLite (CVE-2021-37682) Fixes an FPE in TFLite division operations (CVE-2021-37683) Fixes an FPE in TFLite pooling operations (CVE-2021-37684) Fixes an infinite loop in TFLite (CVE-2021-37686) Fixes a heap OOB in TFLite (CVE-2021-37685) Fixes a heap OOB in TFLite's Gather* implementations (CVE-2021-37687) Fixes an undefined behavior arising from null pointer dereference in TFLite (CVE-2021-37688) Fixes an undefined behavior arising from null pointer dereference in TFLite MLIR optimizations (CVE-2021-37689) Fixes a FPE in LSH in TFLite (CVE-2021-37691) Fixes a segfault on strings tensors with mismatched dimensions, arising in Go code (CVE-2021-37692) Fixes a use after free and a potential segfault in shape inference functions (CVE-2021-37690) -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1191066] New: kdump: finish UsrMerge, install to /usr
by bugzilla_noreply＠suse.com 17 Jun '22

17 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1191066 Bug ID: 1191066 Summary: kdump: finish UsrMerge, install to /usr Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: ptesarik(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de CC: db7532(a)qq.com Blocks: 1191054 Found By: --- Blocker: --- Following up on the discussion on the Factory list https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/message… All packages installing files into /bin, /sbin, /lib and /lib64 should change the location to the counterpart in /usr instead. Please consider doing that for kdump. If kdump still needs to build for released distros you may keep the legacy locations within a "%if %suse_version < 1550" block of course. If you do that, please do *NOT* install symlinks from/to /usr as it was done with some packages in the past. Move the files in question instead. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1170826] New: Go packages miss binutils-gold dependency
by bugzilla_noreply＠novell.com 17 Jun '22

17 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1170826 Bug ID: 1170826 Summary: Go packages miss binutils-gold dependency Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On arm and aarch64, 'go' requires 'binutils-gold' dependency at runtime, but go packages only require it as BuildRequires. So, binutils-gold must be installed manually, which breaks some builds in OBS, such as rclone [0]. Without 'binutils-gold', we ge the following error: [ 138s] /usr/lib64/go/1.11/pkg/tool/linux_arm64/link: running gcc failed: exit status 1 [ 138s] collect2: fatal error: cannot find 'ld' So, we need to add 'Requires: binutils-gold' to all go1.x packages. [0]: https://build.opensuse.org/package/show/network/rclone -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1173720] New: No sound after upgrade from Leap 15.1
by bugzilla_noreply＠suse.com 17 Jun '22

17 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1173720 Bug ID: 1173720 Summary: No sound after upgrade from Leap 15.1 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: alberto.zacchetti(a)tiscali.it QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After upgrading from Leap 15.1 to Leap 15.2, the system no longer plays any sound (even from Yast sound setting) although the snd-hda-intel driver appears to be loaded. The chipset is a C600/X79 and it worked wonderfully on Leap 15.1. Now in Yast I see all the volume controls, but I don't hear any sound on headphones. Also in KDE the only item that appears is the digital output (which I can't verify) while every other analog output has disappeared. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1179584] New: Installing python3-gobject but not python3-cairo breaks `pip3 check`
by bugzilla_noreply＠suse.com 16 Jun '22

16 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1179584 Bug ID: 1179584 Summary: Installing python3-gobject but not python3-cairo breaks `pip3 check` Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: openSUSE Leap 15.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: me(a)manueljacob.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Setup: zypper install -y python3-pip python3-gobject Expected behavior: `pip3 check` succeeds and prints ��No broken requirements found.��. Actual behavior: `pip3 check` fails and prints ��pygobject 3.34.0 requires pycairo, which is not installed.��. Workaround: Install package python3-cairo. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1185647] New: GNOME Software not updating RPM packages
by bugzilla_noreply＠suse.com 16 Jun '22

16 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1185647 Bug ID: 1185647 Summary: GNOME Software not updating RPM packages Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: dfaggioli(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- So, with Snapshot 20210427, pkcon now works for installing packages, e.g., from a terminal (although, it does follow weak dependencies, but that's another issue). However, updating via GNOME Software does not work yet. So, this is the situation right after install: dario@localhost:~> sudo snapper list # | Type | Pre # | Date | User | Used Space | Cleanup | Description | Userdata ---+--------+-------+---------------------------------+------+------------+---------+-----------------------+-------------- 0 | single | | | root | | | current | 1* | single | | Wed 05 May 2021 07:17:32 AM UTC | root | 43.02 MiB | | first root filesystem | 2 | single | | Wed 05 May 2021 07:24:05 AM UTC | root | 36.47 MiB | number | after installation | important=yes In GNOME Software, I see the notification of some updates, I can go to the proper tab, click 'Download' and then click 'Restart & Install'. At which point, on the GUI, I see this error message: "Unable to install updates: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._pk_2dengine_2derror-2dquark.Code1:Failed to create symlink: Read-only file system" If I go ahead, after the reboot, the updates have not been installed. This is the status of system snapshots: dario@localhost:~> sudo snapper list [sudo] password for root: # | Type | Pre # | Date | User | Used Space | Cleanup | Description | Userdata ---+--------+-------+---------------------------------+------+------------+---------+-----------------------+------------------------------------- 0 | single | | | root | | | current | 1* | single | | Wed 05 May 2021 07:17:32 AM UTC | root | 144.00 KiB | | first root filesystem | 2 | single | | Wed 05 May 2021 07:24:05 AM UTC | root | 36.47 MiB | number | after installation | important=yes 3 | single | | Wed 05 May 2021 10:51:00 AM UTC | root | 19.75 MiB | | Snapshot Update of #1 | transactional-update-in-progress=yes 4 | single | | Wed 05 May 2021 10:55:47 AM UTC | root | 19.75 MiB | | Snapshot Update of #1 | transactional-update-in-progress=yes 5 | single | | Wed 05 May 2021 11:06:10 AM UTC | root | 19.75 MiB | | Snapshot Update of #1 | transactional-update-in-progress=yes 6 | single | | Wed 05 May 2021 11:06:48 AM UTC | root | 160.00 KiB | | Snapshot Update of #1 | transactional-update-in-progress=yes In journalctl, I see a bunch of lines like these: May 05 11:07:19 localhost.localdomain systemd[1706]: \x2esnapshots-6-snapshot-.snapshots.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: \x2esnapshots-6-snapshot-boot-writable.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: \x2esnapshots-6-snapshot-root.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: \x2esnapshots-6-snapshot-sys-fs-fuse-connections.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: \x2esnapshots-6-snapshot-sys-kernel-config.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: \x2esnapshots-6-snapshot-sys-kernel-tracing.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: \x2esnapshots-6-snapshot-sys.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: tmp-transactional\x2dupdate\x2djNF9Qy-proc.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: tmp-transactional\x2dupdate\x2djNF9Qy-dev.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: tmp-transactional\x2dupdate\x2djNF9Qy-sys-kernel-config.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: tmp-transactional\x2dupdate\x2djNF9Qy-sys-kernel-tracing.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: tmp-transactional\x2dupdate\x2djNF9Qy-sys-kernel-debug.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: tmp-transactional\x2dupdate\x2djNF9Qy-sys-fs-selinux.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: tmp-transactional\x2dupdate\x2djNF9Qy-sys-fs-bpf.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: tmp-transactional\x2dupdate\x2djNF9Qy-sys-fs-pstore.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: tmp-transactional\x2dupdate\x2djNF9Qy-sys-fs-cgroup.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: tmp-transactional\x2dupdate\x2djNF9Qy-sys-kernel-security.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: tmp-transactional\x2dupdate\x2djNF9Qy-sys-fs-fuse-connections.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: tmp-transactional\x2dupdate\x2djNF9Qy-sys.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: tmp-transactional\x2dupdate\x2djNF9Qy.mount: Succeeded. PackageKit logs does not seem to me to contain anything related to this operation, but I'm happy to provide further info. After a few seconds, `snapper list` is slightly different (probably due to the fact that, right after boot, packagekit was scanning for updates): dario@localhost:~> sudo snapper list # | Type | Pre # | Date | User | Used Space | Cleanup | Description | Userdata ---+--------+-------+---------------------------------+------+------------+---------+-----------------------+------------------------------------- 0 | single | | | root | | | current | 1* | single | | Wed 05 May 2021 07:17:32 AM UTC | root | 19.72 MiB | | first root filesystem | 2 | single | | Wed 05 May 2021 07:24:05 AM UTC | root | 36.47 MiB | number | after installation | important=yes 3 | single | | Wed 05 May 2021 10:51:00 AM UTC | root | 19.75 MiB | | Snapshot Update of #1 | transactional-update-in-progress=yes 4 | single | | Wed 05 May 2021 10:55:47 AM UTC | root | 19.75 MiB | | Snapshot Update of #1 | transactional-update-in-progress=yes 5 | single | | Wed 05 May 2021 11:06:10 AM UTC | root | 19.75 MiB | | Snapshot Update of #1 | transactional-update-in-progress=yes Of course, the expected results would be that packages are actually updated/installed. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1176233] New: Unable to install nvidia driver 450.66
by bugzilla_noreply＠suse.com 15 Jun '22

15 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1176233 Bug ID: 1176233 Summary: Unable to install nvidia driver 450.66 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: juergen-fuhrmann(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi on a fresh install of tumbleweed (kernel 5.8) (and btw also on Leap 15.2 with Kernel 5.3) the nvidia driver 450.66 installation fails. The culprit seems to be that the make system complains about missing scripts/Makefile.kcsan Trying to report this to nvidia as well... -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 925275] New: NVIDIA Driver not installable
by bugzilla_noreply＠novell.com 15 Jun '22

15 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=925275 Bug ID: 925275 Summary: NVIDIA Driver not installable Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: fbernasek(a)netscape.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 629479 --> http://bugzilla.opensuse.org/attachment.cgi?id=629479&action=edit nvidia driver install log install opensuse tumbleweed 20150329 no problems. after reboot i like to install the NVIDIA-346.47 or 349.12 with booth the same problem can't install the driver. now i update with the kernel from the kernel:stable repositories the same problem. 20150328 the same problem -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1004201] New: System hangs during boot due to loop trying to load nvidia modules
by bugzilla_noreply＠novell.com 15 Jun '22

15 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1004201 Bug ID: 1004201 Summary: System hangs during boot due to loop trying to load nvidia modules Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: marcelo.jimenez(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- lspci is: 01:00.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 730] (rev a1) Nvidia site explicitly says that the 367.44 driver does support GT 730. In my opinion, there are two problems here: 1 - The system initialization should not loop forever trying to load a module it has already tryed to load and failed 2 - The 367.44 NVIDIA driver should support my hardware. The NVRM messages repeat forever: ... Oct 09 09:17:23 linux-af78 kernel: [drm] Initialized drm 1.1.0 20060810 Oct 09 09:17:23 linux-af78 kernel: nvidia_modeset: module license 'NVIDIA' taints kernel. Oct 09 09:17:23 linux-af78 kernel: Disabling lock debugging due to kernel taint Oct 09 09:17:23 linux-af78 systemd-journal[120]: Journal started Oct 09 09:17:23 linux-af78 kernel: nvidia_modeset: Unknown symbol nvidia_register_module (err 0) Oct 09 09:17:23 linux-af78 kernel: nvidia_modeset: Unknown symbol nvidia_get_rm_ops (err 0) Oct 09 09:17:23 linux-af78 kernel: nvidia_modeset: Unknown symbol nvidia_unregister_module (err 0) Oct 09 09:17:23 linux-af78 systemd[1]: Started Journal Service. ... Oct 09 09:17:31 linux-af78 systemd[1]: Mounting /home... Oct 09 09:17:31 linux-af78 mtp-probe[579]: checking bus 6, device 2: "/sys/devices/pci0000:00/0000:00:1d.2/usb6/6-1" Oct 09 09:17:31 linux-af78 mtp-probe[578]: checking bus 5, device 2: "/sys/devices/pci0000:00/0000:00:1d.1/usb5/5-2" Oct 09 09:17:31 linux-af78 mtp-probe[578]: bus: 5, device: 2 was not an MTP device Oct 09 09:17:31 linux-af78 mtp-probe[579]: bus: 6, device: 2 was not an MTP device Oct 09 09:17:32 linux-af78 kernel: vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem Oct 09 09:17:32 linux-af78 kernel: NVRM: The Unknown NVIDIA G8x Series GPU installed in this NVRM: system is not supported through the 367.44 NVIDIA NVRM: driver. You can try the NVIDIA 340.xx Legacy drivers. NVRM: Please visit http://www.nvidia.com/object/unix.html NVRM: for download information. The 367.44 NVIDIA driver NVRM: will ignore this GPU. Continuing probe... Oct 09 09:17:32 linux-af78 kernel: nvidia: probe of 0000:01:00.0 failed with error -1 Oct 09 09:17:32 linux-af78 kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 246 Oct 09 09:17:32 linux-af78 kernel: NVRM: The NVIDIA probe routine failed for 1 device(s). Oct 09 09:17:32 linux-af78 kernel: NVRM: None of the NVIDIA graphics adapters were initialized! Oct 09 09:17:32 linux-af78 kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 246 Oct 09 09:17:32 linux-af78 kernel: NVRM: NVIDIA init module failed! Oct 09 09:17:32 linux-af78 systemd[1]: Mounted /home. Oct 09 09:17:32 linux-af78 systemd[1]: Starting Local File Systems. Oct 09 09:17:32 linux-af78 systemd[1]: Reached target Local File Systems. Oct 09 09:17:32 linux-af78 systemd[1]: Starting Tell Plymouth To Write Out Runtime Data... Oct 09 09:17:32 linux-af78 systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage... Oct 09 09:17:32 linux-af78 kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) Oct 09 09:17:32 linux-af78 kernel: vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=none,decodes=none:owns=io+mem Oct 09 09:17:32 linux-af78 kernel: NVRM: The Unknown NVIDIA G8x Series GPU installed in this NVRM: system is not supported through the 367.44 NVIDIA NVRM: driver. You can try the NVIDIA 340.xx Legacy drivers. NVRM: Please visit http://www.nvidia.com/object/unix.html NVRM: for download information. The 367.44 NVIDIA driver NVRM: will ignore this GPU. Continuing probe... Oct 09 09:17:32 linux-af78 kernel: nvidia: probe of 0000:01:00.0 failed with error -1 Oct 09 09:17:32 linux-af78 kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 246 Oct 09 09:17:32 linux-af78 kernel: NVRM: The NVIDIA probe routine failed for 1 device(s). Oct 09 09:17:32 linux-af78 kernel: NVRM: None of the NVIDIA graphics adapters were initialized! Oct 09 09:17:32 linux-af78 kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 246 Oct 09 09:17:32 linux-af78 kernel: NVRM: NVIDIA init module failed! Oct 09 09:17:32 linux-af78 kernel: vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=none,decodes=none:owns=io+mem Oct 09 09:17:32 linux-af78 kernel: NVRM: The Unknown NVIDIA G8x Series GPU installed in this NVRM: system is not supported through the 367.44 NVIDIA NVRM: driver. You can try the NVIDIA 340.xx Legacy drivers. NVRM: Please visit http://www.nvidia.com/object/unix.html NVRM: for download information. The 367.44 NVIDIA driver NVRM: will ignore this GPU. Continuing probe... Oct 09 09:17:32 linux-af78 kernel: nvidia: probe of 0000:01:00.0 failed with error -1 Oct 09 09:17:32 linux-af78 kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 246 Oct 09 09:17:32 linux-af78 kernel: NVRM: The NVIDIA probe routine failed for 1 device(s). Oct 09 09:17:32 linux-af78 kernel: NVRM: None of the NVIDIA graphics adapters were initialized! Oct 09 09:17:32 linux-af78 kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 246 Oct 09 09:17:32 linux-af78 kernel: NVRM: NVIDIA init module failed! Oct 09 09:17:32 linux-af78 systemd[1]: Started Tell Plymouth To Write Out Runtime Data. Oct 09 09:17:32 linux-af78 kernel: vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=none,decodes=none:owns=io+mem -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1179981] New: EFI on raid1: grub2-install fails to update nvram
by bugzilla_noreply＠suse.com 14 Jun '22

14 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1179981 Bug ID: 1179981 Summary: EFI on raid1: grub2-install fails to update nvram Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: openSUSE Leap 15.2 Status: NEW Severity: Major Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: jjletho67-esus(a)yahoo.it QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 844418 --> https://bugzilla.suse.com/attachment.cgi?id=844418&action=edit Partitions layout I installed openSUSE LEAP 15.2 on a kvm virtual machine with ovmf firmware. My disks layout is configured for a full redundancy, so the efi partition is on raid1 (I've already used this layout on openSUSE 42.3 and by doc it should be supported https://doc.opensuse.org/documentation/leap/startup/single-html/book-opensu…) I'm attaching the partition layout. All file systems are ext4, secureboot is disabled The machine has worked fine ( i rebooted severak times) until i performed a a full patch (zypper patch). At the next reboot grub was not able to boot the os and stop with the error: "error: verification requested but nobody cares" I immediately found this bug https://bugzilla.suse.com/show_bug.cgi?id=1175766 but the solving patch was already installed. Curiously i was able to boot with the installation disk, selecting the "boot from hard disk" option. I tried to launch grub2-install --verbose manually and it ended up with this error: " ... grub2-install: info: copying `/boot/grub2/x86_64-efi/core.efi' -> `/boot/efi/EFI/opensuse/grubx64.efi'. grub2-install: info: Registering with EFI: distributor = `opensuse', path = `\EFI\opensuse\grubx64.efi', ESP at mduuid/9182c46b9d469f79b48850b68f3371a5. grub2-install: info: executing efibootmgr --version </dev/null >/dev/null. grub2-install: info: executing modprobe -q efivars. grub2-install: info: executing efibootmgr -c -d. efibootmgr: option requires an argument -- 'd' efibootmgr version 14 usage: efibootmgr [options] -a | --active sets bootnum active -A | --inactive sets bootnum inactive -b | --bootnum XXXX modify BootXXXX (hex) -B | --delete-bootnum delete bootnum (specified with -b) --delete delete entry by bootnum (-b), by UUID (-P) or by disk+partition[+file] (-d -p -l) -c | --create create new variable bootnum and add to bootorder -C | --create-only create new variable bootnum and do not ... " My speculation is that efibootmgr hasn't the disks parameter due to the raid configuration of the efi partition. Some updated packages has "lost" the ability to deal properly with EFI on raid1 STEP TO REPRODUCE: Install LEAP 15.2 with the same partitions layout described above. Perform a "zypper patch" and reboot it ACTUAL RESULTS: the system does not boot, grub stops with "error: verification requested but nobody cares" EXPECTED RESULTS: the system continues to boot properly -- You are receiving this mail because: You are on the CC list for the bug.

1 29