12800 can't be right.Code:
/etc/default/grubGRUB_CMDLINE_LINUX_DEFAULT="quiet fbcon=rotate:1 i915.enable_psr=0"GRUB_GFXMODE=800x12800
A lot of what inxi wants to show is inaccessible to it when running in a vt instead of X. z filters output that needn't be shared with the public. --vs shows inxi version. This is more like what I expect to see from inxi -Ga:Code:
inxi -GazGraphics: Device-1: Intel Alder Lake-N [UHD Graphics] driver: i915 v: kernel arch: Gen-12.2 process: Intel 10nm built: 2021-22+ ports: active: DSI-1 empty: DP-1,HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:46d1 class-ID: 0300 Device-2: icSpring camera type: USB driver: uvcvideo bus-ID: 3-3:2 chip-ID: 32e6:9005 class-ID: 0e02 Display: x11 server: X.org v: 1.21.1.7 with: Xwayland v: 22.1.9 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 tty: 163x57 Monitor-1: DSI-1 size-res: N/A in console modes: 800x1280 API: OpenGL Message: GL data unavailable in console for root.
Code:
# inxi -GSaz --vsinxi 3.3.36-00 (2024-09-04)System: Kernel: 6.1.0-22-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 clocksource: tsc avail: hpet,acpi_pm parameters: BOOT_IMAGE=/vmlinuz root=LABEL=tm8p10deb12 noresume ipv6.disable=1 net.ifnames=0 consoleblank=0 preempt=full mitigations=off video=1440x900@60 Desktop: TDE (Trinity) v: R14.1.2 tk: Qt v: 3.5.0 wm: Twin v: 3.0 with: kicker vt: 7 dm: 1: TDM 2: XDM Distro: Debian GNU/Linux 12 (bookworm)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.7 compositor: Twin v: 3.0 driver: X: loaded: modesetting unloaded: fbdev,vesa 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 vendor: intel mesa v: 22.3.6 glx-v: 1.4 es-v: 3.2 direct-render: yes renderer: Mesa Intel Graphics (RKL GT1) device-ID: 8086:4c8b memory: 29.48 GiB unified: yes API: Vulkan v: 1.3.239 layers: 3 device: 0 type: integrated-gpu name: Intel Graphics (RKL GT1) driver: mesa intel v: 22.3.6 device-ID: 8086:4c8b surfaces: xcb,xlib device: 1 type: cpu name: llvmpipe (LLVM 15.0.6 256 bits) driver: mesa llvmpipe v: 22.3.6 (LLVM 15.0.6) device-ID: 10005:0000 surfaces: xcb,xlib#Plymouth shows up among messages I can make out in your image. Could be 12800 or something else is interfering with its exit, thus interfering with SDDM. I never use SDDM, even in Neon; Plymouth either. When not using TDM or KDM3 I use LightDM. Try removing or disabling Plymouth, and a DM other than SDDM.using xe.force_probe=46d1 i915.force_probe=!46d1 it looks like it ignores the xe and continues to use i915
...
this results in text being displayed but it looks similar to nomode set and its hanging up after it starts cups, so i presume its SDDM failing to display... I have to CTRL-ALT-F2 to get a prompt
...
with SDDM disabled i am able to reach a command prompt, but when i try to start plasma, it fails:Code:
startplasma-waylandError: could not determine $DISPLAYError: can not contact kdeinit5!org.kde.startup: "kdeinit5_shutdown" () exited with code 255
Does dbus-run-session startplasma-wayland behave any better? Does startplasma-x11 produce similar results?
Statistics: Posted by mrmazda — 2024-09-05 04:31 — Replies 3 — Views 2916