Have 42.3 installed on my laptop and whilst I was logged in, I inserted an HDMI cable from the laptop into the TV. The screen didn’t match but if I opened a window it was shown on the TV but my laptop was still the desktop. The TV was kind of a continuation of the laptop screen. I couldn’t open any more windows as if the system had frozen. I couldn’t turn it off normally as it wasn’t responding so had to turn it off. I now go to boot it and it is stuck in emergency mode and I can’t seem to boot into my normal screen, with or without the HDMI cable plugged in.
Pretty ridiculous that a system appears to be broken/non-functioning after just plugging in an HDMI cable.
I am tempted to completely wipe the whole thing if it doesn’t work. It’s a dual boot system about 4 years old and, no surprises, windows is beginning to run a bit slower than it used to so I’m tempted to just wipe the linux partitions, reinstall windows and then reinstall SuSE…will see if that fixes it first though. If not I shall be back! I did try the installation USB stick and tried an “upgrade” to see if that may fix it, but it kept hanging on probing for system files. I do find it ridiculous that this apepars to have happened because I plugged an HDMI cable into it.
Is this one of those laptops with both Intel and NVidia video? If yes, what is laptop model, and output from
lspci -nnk | grep -A4 VGA
and/or
inxi -G -c0
Is the TV one of those 720Ps whose actual native resolution is 1366x768 and properly supports 1080 only for TV programs? Can you get xrandr output from an Xterm?
It might be coincidence that this happened when you plugged in the HDMI cable. Maybe it flushed out a hardware limitation.
FWIW, I had an old Toshiba laptop with openSUSE 42.3 on it (and btrfs file system ) which did the same to me a week or so ago, after I had updated it. Rather than try to investigate and fix it, I decided to undertake a clean install with Leap 15.
Deano Ferrari - did that solve your problem? The issue I have is that when I tried installing (fresh install, not update) Leap 15 it just hung on loading udev, yet Leap 42.3 worked absolutely fine.
I wonder why 15 is a fair bit smaller than 42.3, too?
The TV is an old 42 inch Samsung and it is 1080p. The laptop doesn’t have that aspect ratio from what I’m aware. If I can get Windows to work on the screen, should there be some way of getting Suse to work too?
Thanks
Ps I’m going to wipe Suse and windows and start totally fresh. The laptop is a spare with nothing on there I haven’t got backed up. I was purely going to use it for connecting to my TV and hard drives to watch media from, browse the Internet etc. As Windows was running slower than a few years back I decided to wipe it and it’s currently installing now. Once done I’ll set it up and hopefully you can advise on 15 vs 42.3
linux-a87l:/home/ross # lspci -nnk | grep -A4 VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation Atom Processor Z36xxx/Z37xxx
Series Graphics & Display [8086:0f31] (rev 0e)
Subsystem: ASUSTeK Computer Inc. Device [1043:161d]
Kernel driver in use: i915
Kernel modules: i915
00:13.0 SATA controller [0106]: Intel Corporation Atom Processor E3800 Series SATA AHCI
Controller [8086:0f23] (rev 0e)
The native resolution of the TV may well be 1024x768. Is it worth making the laptop that resolution and then trying the HDMI again? Having just reinstalled WIndows and SUSE 42.3 (15 won’t work) I’m worried that it’ll just mess it right up again.
I put my laptop into the different resolution, rebooted it with the HDMI cable in. It appeared the same again (where the TV was an extension of the screen, rather than replacing it) and I opened system settings > display and monitor. I then put the primary output to HDMI but still no such luck. I then disabled the laptop monitor and hey presto, all works well.
I’ve rebooted the laptop a few times with or without the HDMI plugged in and it seems to work fine, although the screen size is odd if I don’t use the HDMI because of the altered output resolution…I’m weary to try and change this back to normal in case it messes my system up again!
It doesn’t matter a great deal because the laptop will be tucked away under my TV and used as a media player/internet browser through the TV so not really used as a laptop.
would have been, and still would be, more telling.
xrandr
would be too. 1366x768 is a 16:9 ratio widescreen mode, same as 1600x900, 1920x1080 (1080p), 2560x1440 and 3840x2160 (4K). 1024x768 is a 4:3 ratio VESA mode technically supported by virtually everything going back nearly three decades. Everything intended for 16:9 is going to be compressed horizontally on a 4:3 display, unless it’s letterboxed (black bands top and bottom). Same goes for that which is intended for a 4:3 display, which will be stretched horizontally on a 16:9 display unless pillarboxed (black bands at the sides).
ross@linux-a87l:~> inxi -G -c0
If ‘inxi’ is not a typo you can use command-not-found to lookup the package that contain
s it, like this:
cnf inxi
The laptop is currently unplugged from the TV but
ross@linux-a87l:~> xrandr
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
eDP-1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 344mm x
193mm
1366x768 60.02 +
1024x768 60.04* 60.00
960x720 60.00
928x696 60.05
896x672 60.01
800x600 60.00 60.32 56.25
700x525 59.98
640x512 60.02
640x480 60.00 59.94
512x384 60.00
400x300 60.32 56.34
320x240 60.05
VGA-1 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)
I’ll try to post this up later when the HDMI is connected. I’m going to try and reset the resolution/aspect ratio on the laptop and then try the HDMI and see what happens!
I have just tried changing the ratio on the laptop to get that back to normal and it was fine…plugged HDMI back in and both screens went black/ Unplugged HDMI and set “no primary output” and now the laptop works fine if it’s unplugged from the TV, and then the TV works when I plug in the HDMI…so all is working.
I wonder why I had that weird error earlier? Ended up doing a fresh 42.3 install.
