I've booted twice, one with, one without nomodeset and looked for relevant changes. Both boots show good systemdctl status, no failed services.
diff <(cut -c 23- journalctl_output_without_nomodeset) <(cut -c 23- journalctl_output_with_nomodeset ) > 3 kernel: Booted with the nomodeset parameter. Only the system framebuffer will be available > 3 kernel: Driver imsttfb not loading because of nomodeset parameter > 3 kernel: Driver asiliantfb not loading because of nomodeset parameter < 3 kernel: PM: Magic number: 13:715:236 < 3 kernel: rtc_cmos rtc_cmos: hash matches < 3 kernel: acpi PNP0C0B:01: hash matches < 3 kernel: memory memory114: hash matches --- > 3 kernel: PM: Magic number: 13:233:742 < 3 kernel: i915 0000:00:02.0: [drm] GT0: GuC firmware i915/tgl_guc_70.bin version 70.44.1 < 3 kernel: i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3 < 3 kernel: i915 0000:00:02.0: [drm] GT0: HuC: authenticated for all workloads < 3 kernel: i915 0000:00:02.0: [drm] GT0: GUC: submission enabled < 3 kernel: i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled < 3 kernel: i915 0000:00:02.0: [drm] GT0: GUC: RC enabled < 3 kernel: mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915]) < 3 kernel: i915 0000:00:02.0: [drm] Protected Xe Path (PXP) protected content support initialized < 3 kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915]) < 3 kernel: i915 0000:00:02.0: [drm] Registered 3 planes with drm panic < 3 kernel: [drm] Initialized i915 1.6.0 for 0000:00:02.0 on minor 1 < 3 kernel: ACPI: video: Video Device [GFX0] (multi-head: yes rom: no post: no) < 3 kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input20 < 3 kernel: fbcon: i915drmfb (fb0) is primary device > 3 systemd[1]: plymouth-start.service - Show Plymouth Boot Screen was skipped > because of an unmet condition check (ConditionKernelCommandLine=splash). > 3 systemd[1]: systemd-ask-password-plymouth.path - Forward Password Requests > to Plymouth Directory Watch was skipped because of an unmet condition check > (ConditionPathExists=/run/plymouth/pid). < 3 kernel: Console: switching to colour frame buffer device 150x120 < 3 kernel: snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops intel_audio_component_bind_ops [i915]) < 3 kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device < 3 sddm-greeter-qt6[2488]: Adding view for "DSI-1" QRect(0,0 1200x1920) < 3 sddm-greeter-qt6[2488]: Message received from daemon: Capabilities < 3 sddm-greeter-qt6[2488]: Message received from daemon: HostName > 3 sddm-greeter-qt6[2144]: Adding view for "None-1" QRect(0,0 600x800) > 3 sddm-greeter-qt6[2144]: Message received from daemon: Capabilities > 3 sddm-greeter-qt6[2144]: Message received from daemon: HostName So without nomodeset, sddm-greeter detects the correct resolution and the screen is named "DSI-1", but the screen remains black. With nomodeset, the screen is "None-1" and limited to 600x800, but works. I'll have to figure out what these modules imsttfb asiliantfb actually do ** Attachment added: "journalctl after running without nomodeset" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2127674/+attachment/5917111/+files/journalctl_output_without_nomodeset -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2127674 Title: Screen resolution limited to 800x600 after update to 25.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2127674/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
