KDE freezes, desktop becomes unusable

mrmazda · 12-27-2023, 05:33 PM

Input/output from inxi -GSaz after first running sudo inxi -U in Konsole would provide a better overall synopsis of your hardware/software configuration. Example:

Code:

# inxi -GSaz
System:
  Host: ab560 Kernel: 5.14.21-150500.55.36-default arch: x86_64 bits: 64
    compiler: gcc v: 7.5.0 clocksource: tsc available: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz root=LABEL=<filter> noresume
    ipv6.disable=1 net.ifnames=0 consoleblank=0 preempt=full mitigations=off
  Desktop: KDE Plasma v: 5.27.4 tk: Qt v: 5.15.8 wm: kwin_x11 vt: 7 dm:
    1: KDM 2: XDM Distro: openSUSE Leap 15.5
Graphics:
  Device-1: Intel RocketLake-S GT1 [UHD Graphics 730] vendor: ASUSTeK
    driver: i915 v: kernel arch: Gen-12.1 process: Intel 10nm built: 2020-21
    ports: active: DP-1,HDMI-A-1,HDMI-A-2 empty: HDMI-A-3 bus-ID: 00:02.0
    chip-ID: 8086:4c8b class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.4 compositor: kwin_x11 driver: X:
    loaded: modesetting unloaded: fbdev,vesa alternate: intel dri: iris
    gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3600x2640 s-dpi: 120 s-size: 762x558mm (30.00x21.97")
    s-diag: 944mm (37.18")
  Monitor-1: DP-1 pos: primary,bottom-l model: Acer K272HUL serial: <filter>
    built: 2018 res: 2560x1440 hz: 60 dpi: 109 gamma: 1.2
    size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes:
    max: 2560x1440 min: 720x400
  Monitor-2: HDMI-A-1 mapped: HDMI-1 pos: top-left model: NEC EA243WM
    serial: <filter> built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2
    size: 519x324mm (20.43x12.76") diag: 612mm (24.1") ratio: 16:10 modes:
    max: 1920x1200 min: 640x480
  Monitor-3: HDMI-A-2 mapped: HDMI-2 pos: top-right model: Dell P2213
    serial: <filter> built: 2012 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2
    size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes:
    max: 1680x1050 min: 720x400
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
    device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris x11: drv: iris
    inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 22.3.5 glx-v: 1.4
    direct-render: yes renderer: Mesa Intel Graphics (RKL GT1)
    device-ID: 8086:4c8b memory: 29.48 GiB unified: yes
#

On your login screen there should be an icon to click that allows you to select a different session type. If you have enabled auto-login, then you'll have to first log out without rebooting to reach the login screen. You should be able to switch Plasma from Wayland to X11 or vice versa, so try it. You should also be able to switch to IceWM instead of Plasma. Try that too. If IceWM is missing from the menu, do Ctrl-Alt-F3, login as root, then do zypper in icewm. Upon X restart or reboot, IceWM should appear as a selection. Do these changes have any impact on the problem?

If none of above is helpful, while not logged into a Plasma session, try removing all content from ~/.cache/ before logging into Plasma again. If that is not helpful, try creating a new user for testing, then perform the same tests. You can create a new user via another Ctrl-Alt-F3 root login using yast users after logging in.

To get back to the GUI after a Ctrl-Alt-Fn switch for running commands, try Alt-F7, Alt-F2 or Alt-F1.

anothernewbie123 · 12-28-2023, 01:29 PM

Code:

# inxi -U
Starting inxi self updater.
Using tiny as downloader.
Currently running inxi version number: 3.3.23
Current version patch number: 00
Current version release date: 2022-10-31
Updating inxi in /usr/bin using main branch as download source...
Validating downloaded data...
Successfully updated to main branch version: 3.3.31
New main branch version patch number: 00
New main branch version release date: 2023-11-02
To run the new version, just start inxi again.
----------------------------------------

Starting download of man page file now.
Updating inxi.1 in /usr/share/man/man1
using main branch branch as download source
Downloading man page file...
Download successful. Validating downloaded man file data...
Contents validated. Writing to man location...
Writing successful. Compressing file...
Download, install, and compression of man page successful.
Check to make sure it works: man inxi

Code:

# inxi -GSaz
System:
  Kernel: 5.14.21-150500.55.39-default arch: x86_64 bits: 64 compiler: gcc v: 7.5.0
    clocksource: tsc available: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-5.14.21-150500.55.39-default
    root=UUID=3661aedd-dddc-4985-89e5-516fa398a9ca splash=silent preempt=full mitigations=auto
    quiet security=apparmor
  Console: pty pts/1 DM: SDDM Distro: openSUSE Leap 15.5
Graphics:
  Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] vendor: ASUSTeK driver: i915 v: kernel
    arch: Gen-12.1 process: Intel 10nm built: 2020-21 ports: active: HDMI-A-1 off: eDP-1 empty: DP-1
    bus-ID: 0000:00:02.0 chip-ID: 8086:9a49 class-ID: 0300
  Device-2: IMC Networks USB2.0 HD UVC WebCam driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-6:3 chip-ID: 13d3:5458 class-ID: fe01
    serial: <filter>
  Display: x11 server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.5 compositor: kwin_x11 driver:
    X: loaded: modesetting unloaded: fbdev,vesa alternate: intel dri: iris gpu: i915 tty: 178x38
  Monitor-1: HDMI-A-1 model: Samsung S24R65x serial: <filter> built: 2022 res: 1920x1080 dpi: 93
    gamma: 1.2 size: 527x296mm (20.75x11.65") diag: 604mm (23.8") ratio: 16:9 modes: max: 1920x1080
    min: 720x400
  Monitor-2: eDP-1 model: Samsung 0x4161 built: 2020 res: 1920x1080 dpi: 142 gamma: 1.2
    size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio: 16:9 modes: 1920x1080
  API: OpenGL Message: GL data unavailable in console for root.
  API: Vulkan v: 1.2.133 layers: 1 device: 0 type: integrated-gpu name: Intel Xe Graphics (TGL
    GT2) driver: mesa intel v: 22.3.5 device-ID: 8086:9a49 surfaces: N/A
Use of uninitialized value $val2 in string eq at /usr/bin/inxi line 7464.
Use of uninitialized value $val2 in split at /usr/bin/inxi line 7469.
Use of uninitialized value $val2 in concatenation (.) or string at /usr/bin/inxi line 7472.
Use of uninitialized value $val2 in concatenation (.) or string at /usr/bin/inxi line 7475.
Use of uninitialized value $val2 in concatenation (.) or string at /usr/bin/inxi line 7476.
  API: EGL Message:

The desktop problem goes on and off by itself, so it's difficult to compare different setups.

mrmazda · 12-28-2023, 04:35 PM

Before reading further, have you tried all that I suggested in comment #17? If not, skip this until after you have.

Too much information going into logs can tie up a PC in short order, which a misconfiguration or bug can cause. These logs are accessed through dmesg, and the journal. If this is the cause, adding kernel command line option pci=noaer appended to the end of the linu line after striking the E key at the Grub menu may serve as a workaround. Simply dmesg | less will let you browse the kernel log. dmesg | grep aile will return any lines in the log that contain the strings "failed", "Failing" or "failure", which would be clues to your problem. If persistent journal is enabled, which it is if /var/log/journal/ exists, journalctl -b -2 --no-hostname would allow you to browse the journal from the second previous boot, looking for clues in similar manner to dmesg | less. journalctl -b | grep aile would present failures listed in the current boot even if persistent journal is not enabled. Excessive messages going into the logs make themselves apparent by their sheer number, usually many repeats, resulting in huge logs. dmesg | wc -l will report how many lines are in the current log. I just did that here. In 53 hours of uptime with no problems apparent, there are 953 lines. journal -b | wc -l will produce line count for journal on current boot. A 4 digit line count shortly after a boot could mean log spam and a problem, and 5 or more digits certainly would.

There have been many threads about trouble with Iris Xe Graphics. Some may be solved via cmdline options. Since I don't have Iris Xe, I'm not familiar with why any specific one may be needed. This is a list of some you may try from kernel documentation:

Code:

	intel_iommu=	[DMAR] Intel IOMMU driver (DMAR) option
		on
			Enable intel iommu driver.
		off
			Disable intel iommu driver.
		igfx_off [Default Off]
			By default, gfx is mapped as normal device. If a gfx
			device has a dedicated DMAR unit, the DMAR unit is
			bypassed by not enabling DMAR with this option. In
			this case, gfx device will use physical address for
			DMA.
		strict [Default Off]
			Deprecated, equivalent to iommu.strict=1.
		sp_off [Default Off]
			By default, super page will be supported if Intel IOMMU
			has the capability. With this option, super page will
			not be supported.
		sm_on
			Enable the Intel IOMMU scalable mode if the hardware
			advertises that it has support for the scalable mode
			translation.
		sm_off
			Disallow use of the Intel IOMMU scalable mode.
		tboot_noforce [Default Off]
			Do not force the Intel IOMMU enabled under tboot.
			By default, tboot will force Intel IOMMU on, which
			could harm performance of some high-throughput
			devices like 40GBit network cards, even if identity
			mapping is enabled.
			Note that using this option lowers the security
			provided by tboot because it makes the system
			vulnerable to DMA attacks.

	intel_idle.max_cstate=	[KNL,HW,ACPI,X86]
			0	disables intel_idle and fall back on acpi_idle.
			1 to 9	specify maximum depth of C-state.

	intel_pstate=	[X86]
			disable
			  Do not enable intel_pstate as the default
			  scaling driver for the supported processors
                        active
                          Use intel_pstate driver to bypass the scaling
                          governors layer of cpufreq and provides it own
                          algorithms for p-state selection. There are two
                          P-state selection algorithms provided by
                          intel_pstate in the active mode: powersave and
                          performance.  The way they both operate depends
                          on whether or not the hardware managed P-states
                          (HWP) feature has been enabled in the processor
                          and possibly on the processor model.
			passive
			  Use intel_pstate as a scaling driver, but configure it
			  to work with generic cpufreq governors (instead of
			  enabling its internal governor).  This mode cannot be
			  used along with the hardware-managed P-states (HWP)
			  feature.
			force
			  Enable intel_pstate on systems that prohibit it by default
			  in favor of acpi-cpufreq. Forcing the intel_pstate driver
			  instead of acpi-cpufreq may disable platform features, such
			  as thermal controls and power capping, that rely on ACPI
			  P-States information being indicated to OSPM and therefore
			  should be used with caution. This option does not work with
			  processors that aren't supported by the intel_pstate driver
			  or on platforms that use pcc-cpufreq instead of acpi-cpufreq.
			no_hwp
			  Do not enable hardware P state control (HWP)
			  if available.
			hwp_only
			  Only load intel_pstate on systems which support
			  hardware P state control (HWP) if available.
			support_acpi_ppc
			  Enforce ACPI _PPC performance limits. If the Fixed ACPI
			  Description Table, specifies preferred power management
			  profile as "Enterprise Server" or "Performance Server",
			  then this feature is turned on by default.
			per_cpu_perf_limits
			  Allow per-logical-CPU P-State performance control limits using
			  cpufreq sysfs interface

There are probably others. Pending finding a specific fix for your exact 8086:9a49, I think I'd try intel_iommu=on first and iommu=pt next, after which both together. If none of those work, I'd go next with intel_iommu=igfx_off, and if that didn't work, I might switch to doing more Googling.

Asking on the Intel developers mailing list might get a better or faster response. intel-gfx@lists.freedesktop.org

anothernewbie123 · 12-29-2023, 07:17 AM

dmesg | grep aile returns:

Code:

[    2.680858] pci 10000:e0:1d.0: BAR 13: failed to assign [io  size 0x1000]
[    2.680859] pci 10000:e0:1d.0: BAR 13: failed to assign [io  size 0x1000]

journalctl -b -2 --no-hostname

Code:

Specifying boot ID or boot offset has no effect, no persistent journal was found.

One of the lines that journalctl -b --no-hostname returns:

Code:

kernel: [Firmware Bug]: TSC ADJUST: CPU0: -601648447 force to 0

anothernewbie123 · 12-29-2023, 08:33 AM

I installed Ubuntu 23.10 with GNOME 45.1 on the same machine. There are more errors but graphics look OK.

inxi -U

Code:

# inxi -U
Error 20: Option: U has been disabled by the inxi distribution maintainer.

inxi -GSaz

Code:

System:
  Kernel: 6.5.0-14-generic arch: x86_64 bits: 64 compiler: N/A
    clocksource: tsc available: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
    root=UUID=47f22fb0-c67b-4a4f-9f50-14a35b6fa0e9 ro quiet splash
    vt.handoff=7
  Desktop: GNOME v: 45.1 tk: GTK v: 3.24.38 wm: gnome-shell dm: GDM3
    v: 45.beta Distro: Ubuntu 23.10 (Mantic Minotaur)
Graphics:
  Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] vendor: ASUSTeK
    driver: i915 v: kernel arch: Gen-12.1 process: Intel 10nm built: 2020-21
    ports: active: HDMI-A-1 off: eDP-1 empty: DP-1 bus-ID: 0000:00:02.0
    chip-ID: 8086:9a49 class-ID: 0300
  Device-2: IMC Networks USB2.0 HD UVC WebCam driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-6:3 chip-ID: 13d3:5458
    class-ID: fe01 serial: <filter>
  Display: server: X.Org v: 1.23.2 with: Xwayland v: 23.2.0
    compositor: gnome-shell driver: dri: iris gpu: i915 display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.00x11.26")
    s-diag: 583mm (22.95")
  Monitor-1: HDMI-1 res: 1920x1080 hz: 60 dpi: 92
    size: 530x300mm (20.87x11.81") diag: 609mm (23.98") modes: N/A
  API: OpenGL v: 4.6 Mesa 23.2.1-1ubuntu3.1 renderer: Mesa Intel Xe
    Graphics (TGL GT2) direct-render: Yes

dmesg | grep aile

Code:

 dmesg | grep aile
[    0.802825] pci 10000:e0:1d.0: BAR 13: failed to assign [io  size 0x1000]
[    0.802830] pci 10000:e0:1d.0: BAR 13: failed to assign [io  size 0x1000]
[    1.578536] asus_wmi: fan_curve_get_factory_default (0x00110024) failed: -19
[    1.578778] asus_wmi: fan_curve_get_factory_default (0x00110025) failed: -19

journalctl -b | grep aile

Code:

kernel: pci 10000:e0:1d.0: BAR 13: failed to assign [io  size 0x1000]
kernel: pci 10000:e0:1d.0: BAR 13: failed to assign [io  size 0x1000]
(udev-worker)[327]: nvme0n1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1.
(udev-worker)[312]: nvme0n1p2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1.
(udev-worker)[327]: nvme0n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1.
kernel: asus_wmi: fan_curve_get_factory_default (0x00110024) failed: -19
kernel: asus_wmi: fan_curve_get_factory_default (0x00110025) failed: -19
systemd[1]: Dependency failed for sssd-nss.socket - SSSD NSS Service responder socket.
systemd[1]: sssd-nss.socket: Job sssd-nss.socket/start failed with result 'dependency'.
systemd[1]: Dependency failed for sssd-autofs.socket - SSSD AutoFS Service responder socket.
systemd[1]: sssd-autofs.socket: Job sssd-autofs.socket/start failed with result 'dependency'.
systemd[1]: Dependency failed for sssd-pac.socket - SSSD PAC Service responder socket.
systemd[1]: sssd-pac.socket: Job sssd-pac.socket/start failed with result 'dependency'.
systemd[1]: Dependency failed for sssd-pam-priv.socket - SSSD PAM Service responder private socket.
systemd[1]: Dependency failed for sssd-pam.socket - SSSD PAM Service responder socket.
systemd[1]: sssd-pam.socket: Job sssd-pam.socket/start failed with result 'dependency'.
systemd[1]: sssd-pam-priv.socket: Job sssd-pam-priv.socket/start failed with result 'dependency'.
systemd[1]: Dependency failed for sssd-ssh.socket - SSSD SSH Service responder socket.
systemd[1]: sssd-ssh.socket: Job sssd-ssh.socket/start failed with result 'dependency'.
systemd[1]: Dependency failed for sssd-sudo.socket - SSSD Sudo Service responder socket.
systemd[1]: sssd-sudo.socket: Job sssd-sudo.socket/start failed with result 'dependency'.
systemd[1]: Starting grub-initrd-fallback.service - GRUB failed boot detection...
systemd[1]: Finished grub-initrd-fallback.service - GRUB failed boot detection.
NetworkManager[654]: <info>  [1703859378.1460] failed to open /run/network/ifstate
systemd[1]: Started update-notifier-download.timer - Download data for packages that failed at package install time.
/usr/libexec/gdm-wayland-session[1047]: dbus-daemon[1047]: [session uid=123 pid=1047] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
systemd[987]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Failed with result 'exit-code'.
wireplumber[1017]: <WpPortalPermissionStorePlugin:0x55d1e7a155a0> Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera
org.gnome.Shell.desktop[1100]: Window manager warning: Failed to parse saved session file: Failed to open file “/var/lib/gdm3/.config/mutter/sessions/1034169ef9263c89931703859381207900000010550000.ms”: No such file or directory
/usr/libexec/gdm-wayland-session[1047]: dbus-daemon[1047]: [session uid=123 pid=1047] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
gsd-sharing[1240]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
gsd-sharing[1240]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
gnome-shell[1100]: Failed to query file info on '/var/lib/gdm3/.local/share/icc/.goutputstream-JLCCG2': Error when getting information for file “/var/lib/gdm3/.local/share/icc/.goutputstream-JLCCG2”: No such file or directory
gnome-shell[1100]: Failed to query file info on '/var/lib/gdm3/.local/share/icc/.goutputstream-9L18F2': Error when getting information for file “/var/lib/gdm3/.local/share/icc/.goutputstream-9L18F2”: No such file or directory
gsd-media-keys[1272]: Failed to grab accelerator for keybinding settings:playback-repeat
gsd-media-keys[1272]: Failed to grab accelerator for keybinding settings:hibernate
wireplumber[1611]: inotify_add_watch() failed: Permission denied
wireplumber[1611]: inotify_add_watch() failed: Permission denied
snapd-desktop-i[1781]: Failed to do gtk init. Waiting for a new session with desktop capabilities.
systemd[1583]: app-gnome-gnome\x2dkeyring\x2dpkcs11-1821.scope: Failed to add PIDs to scope's control group: No such process
systemd[1583]: app-gnome-gnome\x2dkeyring\x2dpkcs11-1821.scope: Failed with result 'resources'.
systemd[1583]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-1821.scope - Application launched by gnome-session-binary.
systemd[1583]: app-gnome-xdg\x2duser\x2ddirs-1830.scope: Failed to add PIDs to scope's control group: No such process
systemd[1583]: app-gnome-xdg\x2duser\x2ddirs-1830.scope: Failed with result 'resources'.
systemd[1583]: Failed to start app-gnome-xdg\x2duser\x2ddirs-1830.scope - Application launched by gnome-session-binary.
systemd[1583]: Dependency failed for org.gnome.SettingsDaemon.XSettings.service - GNOME XSettings service.
systemd[1583]: org.gnome.SettingsDaemon.XSettings.service: Job org.gnome.SettingsDaemon.XSettings.service/start failed with result 'dependency'.
systemd[1583]: gnome-session-x11-services-ready.target: Job gnome-session-x11-services-ready.target/verify-active failed with result 'dependency'.
at-spi2-registr[1961]: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
gnome-shell[1829]: Failed to query file info on '/home/u/.local/share/icc/.goutputstream-VRPBG2': Error when getting information for file “/home/u/.local/share/icc/.goutputstream-VRPBG2”: No such file or directory
gnome-shell[1829]: Failed to query file info on '/home/u/.local/share/icc/.goutputstream-PQZAG2': Error when getting information for file “/home/u/.local/share/icc/.goutputstream-PQZAG2”: No such file or directory
gsd-media-keys[2025]: Failed to grab accelerator for keybinding settings:hibernate
gsd-media-keys[2025]: Failed to grab accelerator for keybinding settings:playback-repeat
gnome-shell[1829]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
systemd[987]: xdg-document-portal.service: Failed with result 'exit-code'.
systemd[987]: xdg-permission-store.service: Failed with result 'exit-code'.
gnome-shell[1829]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
gnome-shell[1829]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
gnome-shell[1829]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
systemd[1]: Starting update-notifier-download.service - Download data for packages that failed at package install time...
systemd[1]: Finished update-notifier-download.service - Download data for packages that failed at package install time.

mrmazda · 12-29-2023, 10:12 AM

Quote:

Originally Posted by anothernewbie123

Why does this happen?

Iris Xe was a rather radical change in Intel Graphics from prior versions. It has been taking a while for all the issues to be found and resolved in the complex system that is Linux graphics. Ubuntu 23.10 is the newest of the distros you have listed. If you're happy with 23.10, keep it. If not, there are others of recent vintage available, and others coming along. Ubuntu will have the latest LTS version in April. Leap 15.6 is available now in alpha, will be beta in February, and released in May or June. Fedora 39 was released shortly after 23.10. Debian stable Bookworm went to v12.4 less than 3 weeks ago. Mageia 9 was released in late August. All I just listed I have installed here, except for 23.10, but I do have 22.04, and alpha 24.04.

Debian and its derivatives disable self updating of inxi. Its upstream version changes often, generally between 6 and 10 week intervals. To allow self-updating, edit /etc/inxi.conf to disable the disabler - change B_ALLOW_UPDATE= to true.

anothernewbie123 · 12-31-2023, 08:19 AM

Quote:

Debian and its derivatives disable self updating of inxi. Its upstream version changes often, generally between 6 and 10 week intervals. To allow self-updating, edit /etc/inxi.conf to disable the disabler - change B_ALLOW_UPDATE= to true.

Code:

ls: cannot access '/etc/inxi.conf': No such file or directory

mrmazda · 12-31-2023, 09:43 AM

IME, /etc/inxi.conf only exists if inxi has been installed from a .deb package. openSUSE is not a Debian derivative, while Leap does not often offer a current inxi version. Currently, 15.5 provides 3.3.23, while upstream is 3.3.31, soon to be 3.3.32.

flipchip · 01-10-2024, 12:22 AM

It could also be that the OP forgot to double check their partition layout before instantiating their distribution of choice. It would really help if the OP would provide the community here on LQthe benefit of providing us with the correct log files which ar most commonly found in /var/log/XX.log.

Aeterna · 01-10-2024, 03:22 PM

I have Tiger Lake and it is really stable. This is not LP. Anyway I used 5.x - 6.7 kernels without any issues. Iris Xe just works. There was originally an issue with sound (mic) but never with video.
Maybe there was a problem with installation?