April 2025

Need output of lspci for AMD graphics card
by David C Rankin 12 Apr '25

12 Apr '25

All, If you have an AMD graphics card, could you please show me the output of: $ lspci | grep "VGA compatible controller:" I have Intel and Nvidia, but no AMD card to test. I'm creating a lookup table for a program that adjusts display backlight on laptops/boxes with integrated displays and have no way to get the current vendor/make model string for AMD. Thanks! -- David C. Rankin, J.D.,P.E.

8 17

[oS-EN] Tmux problem
by Carlos E. R. 11 Apr '25

11 Apr '25

Hi, since 2020 I had this .tmux.conf: Telcontar:~ # cat .tmux.conf history-limit 2000 history_size=10000000 Telcontar:~ # This now produces an error when starting "tmux new": /root/.tmux.conf:1: unknown command: history-limit [0/0] Google says I have to now precede each with "set -g " Telcontar:~ # cat .tmux.conf set -g history-limit 2000 set -g history_size=10000000 Telcontar:~ # It still produces an error: /root/.tmux.conf:2: invalid option: history_size=10000000 [0/… [View More]

4 4

zypper is downgrading and changing package vendor:
by -pj 11 Apr '25

11 Apr '25

Hi, openSUSE Tumbleweed installed here. I would like to understand why after a # zypper dup then powercycle then # zypper ref && zypper dup there are 20 packages chosen for downgrade *and* vendor switch. This has occurred twice on two separate occasions now. I thought when the packman repository is used it creates a sticky and solver settings in /etc/zypp/zypp.conf are not able to override this? - Solver is currently on these settings: # grep ^solver /etc/zypp/zypp.conf solver.… [View More]onlyRequires = true solver.allowVendorChange = true solver.dupAllowVendorChange = true - :~> sudo zypper ref && sudo zypper dup [sudo] password for root: Repository 'update-tumbleweed' is up to date. Repository 'Games' is up to date. Repository 'Kernel builds for branch stable (standard)' is up to date. Repository 'libdvdcss2' is up to date. Repository 'repo-non-oss' is up to date. Repository 'repo-openh264' is up to date. Repository 'repo-oss' is up to date. Repository 'packman-essentials' is up to date. All repositories have been refreshed. Refreshing service 'openSUSE'. Loading repository data... Reading installed packages... Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Computing distribution upgrade... The following 20 packages are going to be downgraded: libgbm1 libOSMesa8 libvdpau_nouveau libvdpau_r600 libvdpau_radeonsi libvulkan_intel libvulkan_lvp libvulkan_radeon Mesa Mesa-dri Mesa-gallium Mesa-KHR-devel Mesa-libEGL1 Mesa-libEGL-devel Mesa-libGL1 Mesa-libGL-devel Mesa-libGLESv1_CM-devel Mesa-libGLESv2-devel Mesa-libva Mesa-vulkan-device-select The following 20 packages are going to change vendor: libgbm1 http://packman.links2linux.de -> openSUSE libOSMesa8 http://packman.links2linux.de -> openSUSE libvdpau_nouveau http://packman.links2linux.de -> openSUSE libvdpau_r600 http://packman.links2linux.de -> openSUSE libvdpau_radeonsi http://packman.links2linux.de -> openSUSE libvulkan_intel http://packman.links2linux.de -> openSUSE libvulkan_lvp http://packman.links2linux.de -> openSUSE libvulkan_radeon http://packman.links2linux.de -> openSUSE Mesa http://packman.links2linux.de -> openSUSE Mesa-dri http://packman.links2linux.de -> openSUSE Mesa-gallium http://packman.links2linux.de -> openSUSE Mesa-KHR-devel http://packman.links2linux.de -> openSUSE Mesa-libEGL1 http://packman.links2linux.de -> openSUSE Mesa-libEGL-devel http://packman.links2linux.de -> openSUSE Mesa-libGL1 http://packman.links2linux.de -> openSUSE Mesa-libGL-devel http://packman.links2linux.de -> openSUSE Mesa-libGLESv1_CM-devel http://packman.links2linux.de -> openSUSE Mesa-libGLESv2-devel http://packman.links2linux.de -> openSUSE Mesa-libva http://packman.links2linux.de -> openSUSE Mesa-vulkan-device-select http://packman.links2linux.de -> openSUSE 20 packages to downgrade, 20 to change vendor. Package download size: 40.3 MiB Package install size change: | 209.0 MiB required by packages that will be installed -112.0 KiB | - 209.1 MiB released by packages that will be removed Backend: classic_rpmtrans Continue? [y/n/v/...? shows all options] (y): y - I have chosen y and proceeded without error. Why is this happening? -Regards [View Less]

4 3

gitlab amd goes silent on fixing issues.
by -pj 11 Apr '25

11 Apr '25

Hi, I have previously created a bugzilla report about 'drm schedular comp' related errors. https://bugzilla.opensuse.org/show_bug.cgi?id=1236318 Reference upstream on Gitlab, https://gitlab.freedesktop.org/drm/amd/-/issues/3746#note_2840851 The video card in question is older, Advanced Micro Devices, Inc. [AMD/ATI] Lexa [Radeon 540X/550X/630 / RX 640 / E9171 MCM] (rev c1) Is it well known that AMD refuses to repair certain issues? It seems that upstream has gone completely silent at least in this case.

1 0

x11vnc daemon startup issue
by Marc Chamberlin 11 Apr '25

11 Apr '25

Hello again OpenSuSE - I have a number of OpenSuSE 15.6 systems running KDE/Plasma/X11 desktops. On each system I run an x11vnc user service which is enabled to start up automatically i.e. - systemctl --user enable x11vnc.service systemctl --user start x11vnc.service I start it up as a user service because as a system service I cannot figure out how to get access to two environment variable - $DISPLAY and $XAUTHORITY which are needed in order to start x11vnc. The service file … [View More]

3 9

Encrypted disk & TPM2
by Cyrus 08 Apr '25

08 Apr '25

Hello!, I'm trying to setup a laptop with TPM2 based disk decryption, I've followed this procedure: https://news.opensuse.org/2024/09/20/quickstart-fde-yast2/ Installed Slowroll on a Lenovo X1 Carbon Gen 9, and trying to enroll the device I see this: nb-x1-03:/etc/zypp/repos.d # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS nvme0n1 259:0 0 1.8T 0 disk ├─nvme0n1p1 259:1 0 512M 0 part /boot/efi ├─nvme0n1p2 259:2 0 1.8T 0 part │ └─cr_root 254:0 0 1.8T 0 crypt … [View More]

4 11

Re: Usual fun: 6.14.0 and no nvidia-390.157 driver, no X11
by David C Rankin 08 Apr '25

08 Apr '25

On 4/7/25 9:06 AM, paka wrote: This is a bit confusing: > here is cmdline: > > BOOT_IMAGE=/boot/vmlinuz-6.14.0-1-default > root=UUID=94757ae2-29cb-44c5-a9eb-5c2c42f93189 splash=verbose > plymouth.enable=0 consoleblank=150 nosimplefb=1 security=apparmor > nvidia-drm.modeset=1 > > <snip> > [ 105.328] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.11.0-1- > default root=UUID=94757ae2-29cb-44c5-a9eb-5c2c42f93189 > splash=verbose plymouth.enable=0 … [View More]

2 1

sudden system-wide unwanted scrolling/cycling
by gumb 07 Apr '25

07 Apr '25

Very weird issue just started all of a sudden on my Leap 15.6 laptop. Don't know if I've inadvertently hit some key combo that could have activated some modifier keys or accessibility setting. First way I saw it manifest was the tab bar in Firefox, whereupon moving the mouse over, the tabs all start scrolling left until reaching the right-most one at the end. Thinking I'd hit some weird quirk in Firefox I closed and reopened it, but same thing. Then a webpage open on the 'old' reddit, the … [View More]

2 3

HDPI
by Cyrus 07 Apr '25

07 Apr '25

Hello! is there any guide to setup properly a machine with 4k screen resolution?. I've setup the overlap screen ratio to 200% in KDE, but the cursor is still tiny, as well as login screen, bootloader screen and console access. Regards.

2 1

Re: Usual fun: 6.14.0 and no nvidia-390.157 driver, no X11
by David C Rankin 07 Apr '25

07 Apr '25

On 4/6/25 9:06 PM, Stefan Dirsch wrote: >> Any ideas on why TW is now throwing a undefined symbol: fbdevHWSave error? > G04 driver packages just add > > /usr/lib64/xorg/modules/drivers/nvidia_drv.so > > as X.Org driver/module. I don't see how this can be responsable for such > undefined symbol errors in other X modules/drivers. Thank you Stephan, That was my initial thought as well after seeing the fbdevHWSave symbol error effecting boxes that have no Nvidia … [View More]driver. I've yet to update my laptop with the G04 card as I'm troubleshooting .jpg loading issues that have cropped up. We have reports from others of the Nv 6.14 patch working fine for both Archlinux and openSUSE (Peter's report earlier in this thread). The odd thing I'm struggling to understand is Patrick reports that all is fine when booting TW with the 6.13.8 kernel, but when fully updated to the 6.14 kernel this problem appears. Patrick if you can, send me the output of $ cat /proc/cmdline and the inxi info and we will go from there. With G04, so long as I pass "nosimplefb=1 nvidia-drm.modeset=1" as kernel parameters, I haven't run into issues. I add "acpi_backlight=video" on the laptop (or boxes with integrated displays) to have the /sys/class/backlight/apci_video0 interface active to control display brightness. Some of the threads I've read regarding the fbdevHWSave symbol issue discuss using xorg.conf to control the order the modules are tried. There may be something odd like that happening if somehow the issue. The inxi output with the 6.13.8 kernel shows: Host: crash.wahoo.no-ip.org Kernel: 6.13.8-1-default arch: x86_64 bits: 64 compiler: gcc v: 14.2.1 clocksource: tsc avail: hpet,acpi_pm parameters: BOOT_IMAGE=/boot/vmlinuz-6.13.8-1-default root=UUID=94757ae2-29cb-44c5-a9eb-5c2c42f93189 splash=verbose plymouth.enable=0 consoleblank=150 nosimplefb=1 security=apparmor Console: pty pts/65 DM: SDDM Distro: openSUSE Tumbleweed 20250403 ... Graphics: Device-1: NVIDIA GF106 [GeForce GTS 450] vendor: PNY driver: nvidia v: 390.157 alternate: nouveau,nvidia_drm non-free: series: 390.xx+ status: legacy (EOL~2022-11-22) last: release: 390.157 kernel: 6.0 xorg: 1.21 arch: Fermi code: GF1xx process: 40/28nm built: 2010-2016 pcie: gen: 2 speed: 5 GT/s lanes: 16 link-max: gen: 1 speed: 2.5 GT/s ports: active: none off: DVI-I-1,HDMI-A-1 empty: DVI-I-2 bus-ID: 03:00.0 chip-ID: 10de:0dc4 class-ID: 0300 Display: unspecified server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.6 compositor: kwin_x11 driver: X: loaded: nvidia unloaded: fbdev,modesetting,nouveau,vesa failed: nv gpu: nvidia tty: 120x30 Monitor-1: DVI-I-1 model: Samsung S27C500 serial: <filter> built: 2013 res: 1920x1080 dpi: 82 gamma: 1.2 size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes: max: 1920x1080 min: 640x480 Monitor-2: HDMI-A-1 model: Samsung Odyssey G93SC serial: <filter> built: 2024 res: 3840x1080 dpi: 82 gamma: 1.2 size: 1193x336mm (46.97x13.23") diag: 1239mm (48.8") modes: max: 1920x1080 min: 640x480 API: OpenGL Message: GL data unavailable in console for root. API: Vulkan v: 1.4.309 layers: 3 device: 0 type: cpu name: llvmpipe (LLVM 18.1.1 128 bits) driver: N/A device-ID: 10005:0000 surfaces: N/A API: EGL Message: EGL data unavailable in console, eglinfo missing. That shows: driver: X: loaded: nvidia unloaded: fbdev,modesetting,nouveau,vesa failed: nv gpu: nvidia So I'm scratching my head why when trying to boot 6.14 you run into the error: /usr/lib64/xorg/modules/drivers/nv_drv.so: undefined symbol: fbdevHWSave Can you double-check the Xorg.0.log after the crash with the 6.14 driver *OR* if you reboot to the 6.13.8 driver, check the "Xorg.0.log.old" log to make sure we have everything from the failed boot? If anybody else sees something I'm missing, please jump in :) -- David C. Rankin, J.D.,P.E. [View Less]

3 2

Main

Development

Information

Community

Social Media

Other

openSUSE Users