January 2023 - openSUSE Users - openSUSE Mailing Lists

[oS-EN] New monitor when sent to sleep doesn't awake
by Carlos E. R. 26 Jan '23

26 Jan '23

Hi, I have a new monitor on this old machine at a secondary location. Got it cheap, a returned item to a shop. An LG 22MP410, connected to my old machine with Nvidia graphics. The problem is that (apparently) when the desktop sends the display to sleep for inactivity, pressing a key doesn't wake it up. Nor disconnecting both cables. What works is pressing the menu key of the monitor. I am using XFCE desktop on Leap 15.4. Screensaver is disabled. Power Manager / Display is set to - Blank after 10 minutes - put to sleep after 10 minutes - Switch off after 30 minutes. But it is all deactivated! (I had it deactivated for the previous display, decades old hardware, that would hang the machine on sleep. I will try to activate it and see). Hum... Now that I write this, I'm suspecting that it was "powered off". But this thing doesn't have a power on/off switch! It has a... tiny "joystick" in a recess under the bottom edge. It can be pressed, which activates the menu, and moved to the sides as a cursor key. I found it by blind touching everywhere this morning. The papers don't mention it. Maybe it went to sleep because the monitor, not the computer, decided so... no, that is set to 4 hours. It was the computer. Elesar:~ # hwinfo --gfxcard 18: PCI 100.0: 0300 VGA compatible controller (VGA) [Created at pci.386] Unique ID: VCu0.on6Ysc6JyT1 Parent ID: H0_h.3kPMz12AcD0 SysFS ID: /devices/pci0000:00/0000:00:06.0/0000:01:00.0 SysFS BusID: 0000:01:00.0 Hardware Class: graphics card Model: "nVidia G96C [GeForce 9500 GT]" Vendor: pci 0x10de "nVidia Corporation" Device: pci 0x0640 "G96C [GeForce 9500 GT]" SubVendor: pci 0x1462 "Micro-Star International Co., Ltd. [MSI]" SubDevice: pci 0x1573 Revision: 0xa1 Driver: "nouveau" Driver Modules: "nouveau" Memory Range: 0xfd000000-0xfdffffff (rw,non-prefetchable) Memory Range: 0xd0000000-0xdfffffff (ro,non-prefetchable) Memory Range: 0xfa000000-0xfbffffff (rw,non-prefetchable) I/O Ports: 0x9c00-0x9c7f (rw) Memory Range: 0x000c0000-0x000dffff (rw,non-prefetchable,disabled) IRQ: 32 (2267233 events) I/O Ports: 0x3c0-0x3df (rw) Module Alias: "pci:v000010DEd00000640sv00001462sd00001573bc03sc00i00" Driver Info #0: Driver Status: nouveau is active Driver Activation Cmd: "modprobe nouveau" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #30 (PCI bridge) Primary display adapter: #18 Elesar:~ # hwinfo --monitor 31: None 00.0: 10002 LCD Monitor [Created at monitor.125] Unique ID: rdCR.uluPkDjUuA7 Parent ID: VCu0.on6Ysc6JyT1 Hardware Class: monitor Model: "LG ELECTRONICS LG FULL HD" Vendor: GSM "LG ELECTRONICS" Device: eisa 0x5bfb "LG FULL HD" Serial ID: "" Resolution: 720x400@70Hz Resolution: 640x480@60Hz Resolution: 640x480@75Hz Resolution: 800x600@60Hz Resolution: 800x600@75Hz Resolution: 1024x768@60Hz Resolution: 1024x768@75Hz Resolution: 1280x1024@75Hz Resolution: 1152x864@75Hz Resolution: 1280x1024@60Hz Resolution: 1920x1080@60Hz Size: 480x270 mm Year of Manufacture: 2016 Week of Manufacture: 1 Detailed Timings #0: Resolution: 1920x1080 Horizontal: 1920 2008 2052 2200 (+88 +132 +280) +hsync Vertical: 1080 1084 1089 1125 (+4 +9 +45) +vsync Frequencies: 148.50 MHz, 67.50 kHz, 60.00 Hz Driver Info #0: Max. Resolution: 1920x1080 Vert. Sync Range: 56-75 Hz Hor. Sync Range: 30-85 kHz Bandwidth: 148 MHz Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #11 (VGA compatible controller) Elesar:~ # Elesar:~ # inxi -G Graphics: Device-1: NVIDIA G96C [GeForce 9500 GT] driver: nouveau v: kernel Display: server: X.Org 1.20.3 driver: loaded: nouveau unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz OpenGL: renderer: NV96 v: 3.3 Mesa 21.2.4 Elesar:~ # inxi CPU: Quad Core Intel Core2 Quad Q9550 (-MCP-) speed: 2841 MHz Kernel: 5.14.21-150400.24.38-default x86_64 Up: 4h 47m Mem: 4667.4/7942.3 MiB (58.8%) Storage: 232.89 GiB (14.7% used) Procs: 301 Shell: Bash inxi: 3.3.07 Elesar:~ # -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.4)

6 13

Brasero showing twice in gnome software (Installed)
by Pete Thorsen Jr. 26 Jan '23

26 Jan '23

Hi, I've installed Brasero from the gnome software application, which said that it was installed from the opensuse repo. When I click on the “Installed” tab of the gnome software application, it indicates that Brasero is installed twice. Originally, I wrote to the Brasero folks about this. They said that they couldn't do anything about it. I wrote to the Gnome folks, I never heard back from anyone. Now I am writing here hoping to clean up this bug. One of the Brasero devs replied to me and said, “Your distro provides the PackageKit back-end from which the information comes.” Hopefully, someone here can pass along this information to get it looked at and fix it so that only one instance appears in the Installed software tab of the gnome software application. Thanks in advance, Pete

3 2

Cut and paste
by Marc Chamberlin 25 Jan '23

25 Jan '23

I have noticed an intermittent problem on my OpenSuSE 15.3 and 15.4 x64 systems running KDE/Plasma desktop and I wonder if others are seeing it also and what can be done to fix it. Cut/Copy and Paste does not always work. Particularly noticeable in Firefox and Thunderbird, though Kate, Emacs, LibreOffice and other apps as well, display the problem. I select a string of characters from somewhere, even within an app itself, like Thunderbird, right click the mouse to Copy or Cut the selection, then try an paste it either somewhere back in the app itself, or in some other app, and the paste operation fails. It acts and if there is nothing to paste and the paste menu item remains grayed out and unusable. Sometime Ctrl V works and sometimes not. I usually double check what's in the the Clipboard KDE/Plasma to make sure that what I tried to Copy or Cut is at the top of the clipboard app, and it always is. Kinda annoying and sometimes it is impossible to get the Cut/Copy and Paste to work at all. Sometimes it does work and I have no idea why or what causes the Cut/Copy and Paste to work in some cases and not in others. Any ideas? Thanks in advance as always.... Marc...

5 11

KDE bug fix inquiry
by Marc Chamberlin 24 Jan '23

24 Jan '23

This is probably the wrong group to ask, but I will start here and then follow any pointers to where I should ask my question... I am running Leap 15.4 with the KDE/Plasma desktop. There is a bug, reported and fixed/resolved - https://bugs.kde.org/show_bug.cgi?id=453280 which is bugging me now. This was resolved last year (June) and I am wondering when this fix will show up in an update for my system? It is annoying to have to log out and log back in whenever this problem shows up on my systems, so I thought I would ask and hopefully get an update soon that fixes it. Marc... -- *"The Truth is out there" - Spooky* *_ _ . . . . . . _ _ . _ _ _ _ . . . . _ . . . . _ _ . _ _ _ . . . . _ _ . _ . . _ . _ _ _ _ . _ . _ . _ . _ . * Computers: the final frontier. These are the voyages of the user Marc. His mission: to explore strange new hardware. To seek out new software and new applications. To boldly go where no Marc has gone before! (/This email is digitally signed and the OpenPGP electronic signature is added as an attachment. If you know how, you can use my public key to prove this email indeed came from me and has not been modified in transit. My public key, which can be used for sending encrypted email to me also, can be found at - https://keys.openpgp.org/search?q=marc@marcchamberlin.com or just ask me for it and I will send it to you as an attachment. If you don't understand all this geek speak, no worries, just ignore this explanation and ignore the OpenPGP signature key attached to this email (it will look like gibberish if you open it) and/or ask me to explain it further if you like./)

9 56

[oS-en] new syslog noise about usb
by Carlos E. R. 23 Jan '23

23 Jan '23

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Leap 15.4 Today, I was getting a lot of these new messages in the log (I did an update yesterday): <1.4> 2023-01-23T12:24:34.810643+01:00 Telcontar tracker-extract 12239 - - Locale 'LANG' is not set, defaulting to C locale <3.6> 2023-01-23T12:24:34.810796+01:00 Telcontar dbus-daemon 6603 - - [session uid=1000 pid=6603] Successfully activated service 'org.freedesktop.Tracker3.Miner.Extract' <0.4> 2023-01-23T12:24:39.931135+01:00 Telcontar kernel - - - [ 1419.750050][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:24:40.439134+01:00 Telcontar kernel - - - [ 1420.262039][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:24:40.471128+01:00 Telcontar kernel - - - [ 1420.294034][ C11] [drm] Fence fallback timer expired on ring sdma0 <0.4> 2023-01-23T12:24:40.951290+01:00 Telcontar kernel - - - [ 1420.774202][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:24:40.986395+01:00 Telcontar kernel - - - [ 1420.806033][ C11] [drm] Fence fallback timer expired on ring sdma0 <0.4> 2023-01-23T12:24:41.467291+01:00 Telcontar kernel - - - [ 1421.286047][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:24:41.979281+01:00 Telcontar kernel - - - [ 1421.798197][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:24:42.491121+01:00 Telcontar kernel - - - [ 1422.310037][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:24:42.651117+01:00 Telcontar kernel - - - [ 1422.470030][ C5] [drm] Fence fallback timer expired on ring sdma1 <0.4> 2023-01-23T12:24:43.003273+01:00 Telcontar kernel - - - [ 1422.822197][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:24:43.511303+01:00 Telcontar kernel - - - [ 1423.334196][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:24:43.916745+01:00 Telcontar kernel - - - [ 1423.739516][ T395] usb 3-2: Device not responding to setup address. <0.4> 2023-01-23T12:24:49.891122+01:00 Telcontar kernel - - - [ 1429.710009][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:24:50.399123+01:00 Telcontar kernel - - - [ 1430.218010][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:24:50.427147+01:00 Telcontar kernel - - - [ 1430.250010][ C11] [drm] Fence fallback timer expired on ring sdma0 <0.4> 2023-01-23T12:24:50.955118+01:00 Telcontar kernel - - - [ 1430.774008][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:24:53.755131+01:00 Telcontar kernel - - - [ 1433.574774][ T395] usb 3-2: Device not responding to setup address. <0.3> 2023-01-23T12:24:53.963281+01:00 Telcontar kernel - - - [ 1433.782006][ T395] usb 3-2: device not accepting address 32, error -71 <0.6> 2023-01-23T12:24:54.159124+01:00 Telcontar kernel - - - [ 1433.978002][ T395] usb 3-2: new low-speed USB device number 33 using xhci_hcd <0.4> 2023-01-23T12:24:59.935122+01:00 Telcontar kernel - - - [ 1439.753975][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:25:03.783959+01:00 Telcontar kernel - - - [ 1443.606710][ T395] usb 3-2: Device not responding to setup address. <0.4> 2023-01-23T12:25:09.623152+01:00 Telcontar kernel - - - [ 1449.445966][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:25:09.623170+01:00 Telcontar kernel - - - [ 1449.445968][ C5] [drm] Fence fallback timer expired on ring sdma0 <0.4> 2023-01-23T12:25:10.143119+01:00 Telcontar kernel - - - [ 1449.961947][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:25:10.175409+01:00 Telcontar kernel - - - [ 1449.993945][ C5] [drm] Fence fallback timer expired on ring sdma0 <0.4> 2023-01-23T12:25:13.624717+01:00 Telcontar kernel - - - [ 1453.446974][ T395] usb 3-2: Device not responding to setup address. <0.3> 2023-01-23T12:25:13.835118+01:00 Telcontar kernel - - - [ 1453.653946][ T395] usb 3-2: device not accepting address 33, error -71 <0.3> 2023-01-23T12:25:13.835132+01:00 Telcontar kernel - - - [ 1453.654249][ T395] usb usb3-port2: unable to enumerate USB device usb trouble, and drm trouble. The only things connected to the usb now are in the back of the computer, thus the keyboard, mouse, and other things that should be disconnected. In fact, response at the keyboard stalled, but now seems normal and messages have stopped. Ideas? No, keyboard stalling again, new messages: <1.4> 2023-01-23T12:30:19.882428+01:00 Telcontar tracker-extract 12711 - - Locale 'LANG' is not set, defaulting to C locale <3.6> 2023-01-23T12:30:19.882531+01:00 Telcontar dbus-daemon 6603 - - [session uid=1000 pid=6603] Successfully activated service 'org.freedesktop.Tracker3.Miner.Extract' <0.3> 2023-01-23T12:30:29.799125+01:00 Telcontar kernel - - - [ 1769.617886][ T395] usb 3-2: device descriptor read/64, error -110 <0.6> 2023-01-23T12:30:29.911120+01:00 Telcontar kernel - - - [ 1769.730163][ T395] usb usb3-port2: attempt power cycle <0.6> 2023-01-23T12:30:30.399127+01:00 Telcontar kernel - - - [ 1770.217854][ T395] usb 3-2: new low-speed USB device number 36 using xhci_hcd <0.4> 2023-01-23T12:30:36.059120+01:00 Telcontar kernel - - - [ 1775.877858][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:30:36.571120+01:00 Telcontar kernel - - - [ 1776.389858][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:30:36.855129+01:00 Telcontar kernel - - - [ 1776.677862][ C5] [drm] Fence fallback timer expired on ring sdma0 <0.4> 2023-01-23T12:30:37.083124+01:00 Telcontar kernel - - - [ 1776.901858][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:30:37.599121+01:00 Telcontar kernel - - - [ 1777.417864][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:30:38.107212+01:00 Telcontar kernel - - - [ 1777.926139][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:30:38.619390+01:00 Telcontar kernel - - - [ 1778.438142][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:30:39.127407+01:00 Telcontar kernel - - - [ 1778.950135][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:30:39.643394+01:00 Telcontar kernel - - - [ 1779.462155][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:30:40.024784+01:00 Telcontar kernel - - - [ 1779.847416][ T395] usb 3-2: Device not responding to setup address. <0.4> 2023-01-23T12:30:46.015303+01:00 Telcontar kernel - - - [ 1785.833890][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:30:46.527119+01:00 Telcontar kernel - - - [ 1786.345877][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:30:47.043303+01:00 Telcontar kernel - - - [ 1786.862061][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:30:49.860021+01:00 Telcontar kernel - - - [ 1789.682597][ T395] usb 3-2: Device not responding to setup address. <0.3> 2023-01-23T12:30:50.070655+01:00 Telcontar kernel - - - [ 1789.889885][ T395] usb 3-2: device not accepting address 36, error -71 <0.6> 2023-01-23T12:30:50.275127+01:00 Telcontar kernel - - - [ 1790.093893][ T395] usb 3-2: new low-speed USB device number 37 using xhci_hcd <0.4> 2023-01-23T12:30:56.031128+01:00 Telcontar kernel - - - [ 1795.849892][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:30:56.535353+01:00 Telcontar kernel - - - [ 1796.358114][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:30:57.047311+01:00 Telcontar kernel - - - [ 1796.870071][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:30:57.559295+01:00 Telcontar kernel - - - [ 1797.382062][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:30:58.079114+01:00 Telcontar kernel - - - [ 1797.897895][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:30:59.903115+01:00 Telcontar kernel - - - [ 1799.722583][ T395] usb 3-2: Device not responding to setup address. <0.4> 2023-01-23T12:31:05.791119+01:00 Telcontar kernel - - - [ 1805.609906][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:31:06.303299+01:00 Telcontar kernel - - - [ 1806.121910][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:31:06.335293+01:00 Telcontar kernel - - - [ 1806.153908][ C5] [drm] Fence fallback timer expired on ring sdma0 <0.4> 2023-01-23T12:31:06.815304+01:00 Telcontar kernel - - - [ 1806.633908][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:31:06.847122+01:00 Telcontar kernel - - - [ 1806.665906][ C5] [drm] Fence fallback timer expired on ring sdma0 <0.4> 2023-01-23T12:31:07.327297+01:00 Telcontar kernel - - - [ 1807.145928][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:31:07.359280+01:00 Telcontar kernel - - - [ 1807.177907][ C5] [drm] Fence fallback timer expired on ring sdma0 <0.4> 2023-01-23T12:31:07.839119+01:00 Telcontar kernel - - - [ 1807.658088][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:31:08.350096+01:00 Telcontar kernel - - - [ 1808.169912][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:31:08.863136+01:00 Telcontar kernel - - - [ 1808.681913][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:31:09.371133+01:00 Telcontar kernel - - - [ 1809.189930][ C10] [drm] Fence fallback timer expired on ring gfx <0.4> 2023-01-23T12:31:09.743116+01:00 Telcontar kernel - - - [ 1809.562870][ T395] usb 3-2: Device not responding to setup address. <0.3> 2023-01-23T12:31:09.951127+01:00 Telcontar kernel - - - [ 1809.769916][ T395] usb 3-2: device not accepting address 37, error -71 <0.3> 2023-01-23T12:31:09.951142+01:00 Telcontar kernel - - - [ 1809.770222][ T395] usb usb3-port2: unable to enumerate USB device I'll probably try booting an older kernel. [...] Did so. Another problem: system stalled at the "reached boot target" message, but did not power off nor reboot. Now using: cer@Telcontar:~> uname -a Linux Telcontar 5.14.21-150400.24.33-default #1 SMP PREEMPT_DYNAMIC Fri Nov 4 13:55:06 UTC 2022 (76cfe60) x86_64 x86_64 x86_64 GNU/Linux I don't see noise in the log, the keyboard responds normally. cer@Telcontar:~> rpm -q kernel-default kernel-default-5.14.21-150400.24.33.2.x86_64 kernel-default-5.14.21-150400.24.38.1.x86_64 cer@Telcontar:~> - -- Cheers Carlos E. R. (from 15.4 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCY85y2Bwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVuEYAn2nir8ELdOju4kibZ6yI cKW8jQ9zAJ0a4l7tDhMORxCsxMKVdlJ4q+eH7g== =uAXm -----END PGP SIGNATURE-----

1 0

Technical question: does the current grub in Tumbleweed (the current boot loader) understand md/v1.x metadata?
by Stakanov 22 Jan '23

22 Jan '23

Or do I have to create my boot raid with --metadata 0.90 as setting? Thank you.

2 2

Re: Mdadm: can I resize the partition of a mdam if I have only one primary partition per disk and RAID 1? In yast?
by David C. Rankin 22 Jan '23

22 Jan '23

On 1/19/23 14:19, Stratos Zolotas wrote: > I suppose something like > > mdadm --grow --size max /dev/md0 I would not grow to max, but "max - 300M". A replacement 8T drive may not have exactly the same "max" size preventing syncing to the new drive. It is always recommended to leave 1/4 to 1G unused for this reason. -- David C. Rankin, J.D.,P.E.

6 13

[heroes] what changed today that I can't use SeaMonkey 2.53.14 for the forums?
by Felix Miata 21 Jan '23

21 Jan '23

Now the site is headed by: [quote] Unfortunately, your browser is unsupported. Please switch to a supported browser to view rich content, log in and reply.[/quote] It won't let me login. I can't switch to 2.53.15 yet, because Buc's alternate version[1] that supports iso 8601 is not yet available. [1] https://buc.fedorapeople.org/seamonkey/download/ -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata

6 15

Mdadm: can I resize the partition of a mdam if I have only one primary partition per disk and RAID 1? In yast?
by Stakanov 20 Jan '23

20 Jan '23

I have a mdam md0 with two hdd 4 TB. They are in use as /home I now have two HDD with 8TB. I normally work with mdam in CLI. I did up to now a planed degrading of the secondary disk of the md0. Then a hot remove. Then I added the first 8TB. with other words: silversurfer:~ # mdadm --manage --set-faulty /dev/md0 /dev/sde1 mdadm: set /dev/sde1 faulty in /dev/md0 silversurfer:~ # mdadm --manage /dev/md0 -r /dev/sde1 mdadm: hot removed /dev/sde1 from /dev/md0 You have new mail in /var/mail/root silversurfer:~ # mdadm --manage /dev/md0 -a /dev/sdg1 mdadm: added /dev/sdg1 It does now sync the data with the 4 TB (hence creating a 4TB on a 8TB disc. Rest of the disk is empty, no other partitions. I will then declare failed the first 4 TB disk, hence hot remove and add 8TB. (here md0 /dev/sdb1) This will again sync 4TB on 8TB disk. Now, one the sync is done, is it possible to expand (e.g. in yast partition manager) the 4TB to the max capacity of the disc, although it is a Raid? How would I proceed and if it is not possible, how would I manage to expand a RAID1? Current status: entropy@silversurfer:~> lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 232,9G 0 disk └─sda1 8:1 0 232,9G 0 part └─md127 9:127 0 232,9G 0 raid1 /usr/local /boot/grub2/x86_64-efi /srv /opt /var /root /boot/grub2/i386-pc /.snapshots / sdb 8:16 0 3,6T 0 disk └─sdb1 8:17 0 3,6T 0 part └─md0 9:0 0 3,6T 0 raid1 /home sdc 8:32 0 298,1G 0 disk ├─sdc1 8:33 0 1K 0 part └─sdc5 8:37 0 298,1G 0 part /boot/efi sdd 8:48 0 447,1G 0 disk ├─sdd1 8:49 0 232,9G 0 part │ └─md127 9:127 0 232,9G 0 raid1 /usr/local │ /boot/grub2/x86_64-efi │ /srv │ /opt │ /var │ /root │ /boot/grub2/i386-pc │ /.snapshots │ / ├─sdd2 8:50 0 100G 0 part /var/tmp ├─sdd3 8:51 0 50G 0 part /tmp └─sdd4 8:52 0 64,2G 0 part [SWAP] sde 8:64 0 3,6T 0 disk └─sde1 8:65 0 3,6T 0 part sdf 8:80 0 1,8T 0 disk └─sdf1 8:81 0 1,8T 0 part └─md126 9:126 0 1,8T 0 raid1 ├─md126p1 259:0 0 200G 0 part └─md126p2 259:1 0 1,6T 0 part /var/lib/libvirt sdg 8:96 0 7,3T 0 disk └─sdg1 8:97 0 7,3T 0 part └─md0 9:0 0 3,6T 0 raid1 /home sdh 8:112 0 7,3T 0 disk └─sdh1 8:113 0 1,8T 0 part └─md126 9:126 0 1,8T 0 raid1 ├─md126p1 259:0 0 200G 0 part └─md126p2 259:1 0 1,6T 0 part /var/lib/libvirt sdi 8:128 1 0B 0 disk sdj 8:144 1 0B 0 disk sdk 8:160 1 0B 0 disk sdl 8:176 1 0B 0 disk sr0 11:0 1 1024M 0 rom Thanks in advance

4 7

It seems that I need a 6.1.x kernel, Leap 15.4
by Darryl Gregorash 19 Jan '23

19 Jan '23

Are the kernels at http://download.opensuse.org/repositories/Kernel:/stable/standard/ suitable for use in Leap 15.4? Background: It seems that ASUS removed all WMI support from its motherboards with the X570/B550/TRX40 chipset (apparently as a result of AMD doing so so for the X670/B650 chips (?) ), and that broke temperature/fan speed monitoring on those boards. The lack of WMI support means the NCT6775 module is loaded on these systems, but previously, that driver attempted to read/write directly to the ACPI table, which according to this discussion: https://bugzilla.kernel.org/show_bug.cgi?id=204807# (see especially comment 37) is rather bad thing to allow. The patch to NCT6775 was only accepted into the kernel beginning with ver 6.1.2, and has not yet been backported to the 5.14 kernel. Therefore, to regain temp/fan speed monitoring, I need to install that kernel or later (ver 6.1.7 was just released on download.o.o today).

7 17