the monitor on my opensuse installation decides to crap itself after like 30 minutes of use and suddenly theres no signal, i reboot and there still isnt a signal. this happened yesterday and i didnt decide to do anything until today where the issue fixed itself (only for a bit) and then now theres no signal???
using kde desktop environment on a fresh install
i dont wanna have to reinstall again wtf do i do???
Disconnect and reconnect cables to power and computer. Cycle power on display. Try another cable from PC to display. You haven’t given us much to work from. How old are these things? Who made them? If you can get it to go long enough, from Konsole, run inxi -GSaz --za to copy its input and output and paste it all here.
- my monitor is an MSI optix g273
- i tried changing the port on my monitor and pc with no luck, i dont have another hdmi cable on me either but i dont think its the cable since it displays the boot screen and everything else fine
Hi, what is the output of:
Open Konsole and enter that command above. Oh, you using Gnome or KDE desktop Environment?
Is this your monitor and specifications? :< https://www.msi.com/Monitor/Optix-G273/Specification
If you need to try another cable, get a DisplayPort cable if your computer provides a DisplayPort output. HDMI was originally designed for Television. DisplayPort was originally designed for computers, and supports displays with only HDMI inputs, as well as things HDMI cannot.
- i cant open a console and run the command since the monitor doesnt display anything
- i am using kde plasma as my desktop environment
- yes, that is my monitor i believe
i do have a seperate laptop with opensuse linux on it so i might try ocnnecting the hdmi cable from my computer into it to see if it can display on that
@wago I’d also check it’s not the external power supply getting flakey…
Are you able to see the Grub boot menu displayed when you power up the machine?
yes, i can see and interact with it but when it boots into linux it stops displaying anything
my laptop doesnt have an hdmi port nvm
Likely a graphics issue, so when you first boot and at grub,
press the e key to edit the boot options,
use the arrow keys to go down to the line starting linux or linuxefi and then press the end key and add nomodeset and press the F10 key to boot.
That should get something started, resolution may not be great, but at least can get additional information about your system(s).
okay this worked so im gonna run the command in the first reply
System:
Kernel: 6.17.8-1-default arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.17.8-1-default root=UUID=<filter>
splash=silent
resume=/dev/disk/by-uuid/48f17db3-a772-4afa-b514-803ada5f627d
mitigations=auto quiet security=selinux selinux=1 nomodeset
Desktop: KDE Plasma v: 6.5.2 tk: Qt v: N/A info: frameworks v: 6.20.0
wm: kwin_x11 tools: avail: xscreensaver vt: 2 dm: SDDM Distro: openSUSE
Tumbleweed 20251119
Graphics:
Device-1: NVIDIA GP104 [GeForce GTX 1070] vendor: PC Partner / Sapphire
driver: N/A alternate: nouveau non-free: 550-580.xx+ status: current (as of
2025-08; EOL~2026-12-xx) arch: Pascal code: GP10x process: TSMC 16nm
built: 2016-2021 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3
speed: 8 GT/s bus-ID: 01:00.0 chip-ID: 10de:1b81 class-ID: 0300
Display: x11 server: X.Org v: 21.1.15 with: Xwayland v: 24.1.8
compositor: kwin_x11 driver: X: loaded: modesetting unloaded: vesa
alternate: fbdev,nouveau,nv,nvidia gpu: N/A display-ID: :0 screens: 1
Screen-1: 0 s-res: 640x480 s-dpi: 96 s-size: 169x127mm (6.65x5.00")
s-diag: 211mm (8.32")
Monitor-1: Unknown-1 mapped: None-1 res: mode: 640x480 hz: 60
scale: 100% (1) size: N/A modes: 640x480
API: EGL v: 1.5 platforms: device: 0 drv: swrast surfaceless: drv: swrast
x11: drv: swrast inactive: gbm,wayland
API: OpenGL v: 4.5 vendor: mesa v: 25.3.0 glx-v: 1.4 direct-render: yes
renderer: llvmpipe (LLVM 21.1.5 256 bits) device-ID: ffffffff:ffffffff
memory: 22.86 GiB unified: yes
API: Vulkan v: 1.4.328 layers: 5 device: 0 type: cpu name: llvmpipe (LLVM
21.1.5 256 bits) driver: mesa llvmpipe v: 25.3.0 (LLVM 21.1.5)
device-ID: 10005:0000 surfaces: N/A
Info: Tools: api: eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor wl: wayland-info
x11: xdpyinfo, xprop, xrandr
What is the output of zypper lr -d? That will show the repository information and if Nvidia repository is enabled.
Shows there is no Nvidia driver currently engaged.
That’s to be expected booting using nomodeset.
heres the output
# | Alias | Name | Enabled | GPG Check | Refresh | Keep | Priority | Type | URI | Service
---+----------------------------------+----------------------------------------+---------+-----------+---------+------+----------+--------+-----------------------------------------------------------------------+---------
1 | NVIDIA:repo-non-free | repo-non-free | Yes | (r ) Yes | Yes | - | 99 | rpm-md | https://download.nvidia.com/opensuse/tumbleweed | NVIDIA
2 | download.opensuse.org-non-oss | Main Repository (NON-OSS) | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://download.opensuse.org/tumbleweed/repo/non-oss/ |
3 | download.opensuse.org-oss | Main Repository (OSS) | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://download.opensuse.org/tumbleweed/repo/oss/ |
4 | download.opensuse.org-tumbleweed | Main Update Repository | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://download.opensuse.org/update/tumbleweed/ |
5 | openSUSE-20251031-0 | openSUSE-20251031-0 | No | ---- | ---- | - | 99 | rpm-md | hd:/?device=/dev/disk/by-id/usb-Generic_Flash_Disk_E0DA2FA7-0:0-part2 |
6 | openSUSE:repo-non-oss | repo-non-oss | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://cdn.opensuse.org/tumbleweed/repo/non-oss | openSUSE
7 | openSUSE:repo-openh264 | repo-openh264 | Yes | (r ) Yes | Yes | - | 99 | rpm-md | https://codecs.opensuse.org/openh264/openSUSE_Tumbleweed | openSUSE
8 | openSUSE:repo-oss | repo-oss | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://cdn.opensuse.org/tumbleweed/repo/oss | openSUSE
9 | openSUSE:repo-oss-debug | repo-oss-debug | No | ---- | ---- | - | 99 | N/A | http://cdn.opensuse.org/debug/tumbleweed/repo/oss | openSUSE
10 | openSUSE:repo-oss-source | repo-oss-source | No | ---- | ---- | - | 99 | N/A | http://cdn.opensuse.org/source/tumbleweed/repo/oss | openSUSE
11 | openSUSE:update-tumbleweed | update-tumbleweed | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://cdn.opensuse.org/update/tumbleweed | openSUSE
12 | repo-debug | openSUSE-Tumbleweed-Debug | No | ---- | ---- | - | 99 | N/A | http://download.opensuse.org/debug/tumbleweed/repo/oss/ |
13 | repo-openh264 | Open H.264 Codec (openSUSE Tumbleweed) | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed |
14 | repo-source | openSUSE-Tumbleweed-Source | No | ---- | ---- | - | 99 | N/A | http://download.opensuse.org/source/tumbleweed/repo/oss/
Is your goal to use FOSS nouveau or Nvidia drivers with the machine? Your hardware seems newer and able to take full advantage of the Nvidia drivers. Other more advanced users may have more information.
I would personally pass # zypper inr(= install recommended), in Konsole in attempt to pull in recommended Nvidia packages at this time.
-Great Hopes
rebooting after trying zypper inr seems to have gotten me into emergency mode but atleast the resolution is fixed
Sorry to see this. My first thought is a BIOS update may be required for the machines motherboard. Other more advanced person/s will most likely have suggestion to press forward.
wait it might be because i was setting up my hard drives to auto mount and it might of caused this to happen last time
Well, you could try passing the root password. Then pass journalctl -xb to view system logs as per above image suggests. Viewing the logs will hopefully help further the resolve on this scenerio.
Perhaps also you can explain more about:
Did you perform some of that adjustment after you installed recommends with ‘zypper inr’ and power cycled the machine?
