I’m not an English speaker I’m American. 
(Humor, but you all knew that right?)
Seriously, I just tried hooking up a Samsung TV to my compurter with hdmi cable and so far I can’t get it to work. This may just mean I don’t know how to do this. In SystemSettings it show up indicating that hardware is seen by system but it won’t enable. If I boot with only the TV I see black screen windows made famous.
Note: Compositor settings in SystemSettings do not seem to be respected. If I reboot they reset to a default regardless of my changes. This is disturbing.
Post-edit: In other words I’m trying to get to where I can attempt to reporduce the problem. Thought I should get this working in installed system first before trying with ‘Live’ ISO.
I don’t think using a TV with hdmi connection works. I tried:
$ xrandr -q
...
HDMI-2 connected (normal left inverted right x axis y axis)
1920x1080 60.00 + 60.00 50.00 59.94 30.00 25.00 24.00 29.97 23.98
...
$ sudo xrandr --addmode HDMI-2 "1920x1080"
$ xrandr --addmode HDMI-2 "1920x1080"
Working with developer on this. So far we know something is not working correctly but not what or why. So will report when I know more.
I use a standard VGA cable connection for my TV.
I would poiint out that I did not have this problem with 3.03, 4 Alpha, or 4 Beta. So something may have changed since the Beta. I had other issues, and was looking forward to seeing them fixed in the Final (I rarely even check out the Alpha or Beta of a distro).
I’m glad to know it’s not just my hardware.
Ok let’s start at the beginning with this one.
The first difficulty is that this Lenovo has dual graphics cards.
Intel HD Graphics 4000
NVIDIA NVS™ 5400M
This is nasty because the system does not know which one to activate. This is made worse because you have the TV monitor plugged it which will be auto-detected by the X server. Since the HDMI port is almost certainly connected to the nVidia card the nVidia card will be activated. Unfortunately the default boot process will probably have activated the Intel graphics. This situation can cause issues with the X server we have seen this in the past.
The first thing to try is unplugging the TV monitor for the time being and trying to boot the iso to the laptop screen .
If this does not work then step two is to boot to a non-graphical mode so that we can diagnose the the issue. To do this choose the Troubleshooting option and pick the second option “Start Openmandriva Lx live in CLI mode”
This should boot you to a terminal screen where we can run some diagnostics
Run this command…
lsmod | grep nouveau
If this returns 7 or 8 lines with nouveau in them we can probably get you going.
Let us know what you find and we will advise further.
Actually, no it doesn’t. My T430 only has Intel 4000 graphics. And I have the TV plugged in as a VGA monitor, not HDMI.
This was taken from my Terminal on Linux Mint 19.1:
zaivala@zaivala-ThinkPad-T430:~$ lsmod | grep nouveau
zaivala@zaivala-ThinkPad-T430:~$
So, no news for me? That will seriously affect my review for Distrohoppers’ Digest.
Please consider also it’s holidays time, human beings need some rest, sometimes.
1 Like
Perhaps, and I hope everyone is enjoying what holidays they observe, but this has been going on for a while now. And I do a new podcast each month, with a distro being used for an entire monthand this was the month to be trying out OM 4.
NEW INFORMATION:
At the risk of severe eyestrain and with the help of a magnifying glass, I got the brilliant idea to try to install OpenMandriva Lx 4 FIRST, and THEN change the monitors. The Displays program worked great, and then refused to close, with the same issue I had before – the mouse pointer moved, and nothing else did.
STILL ANOTHER ISSUE, but one which is on Calamares’ doorstep: Calamares has developed a problem where, when you try to install onto an alread-in-use partition, it creates an imaginary partition and formats both the imaginary partition and the partition you wanted to install to, and the installation gets split between the two, resulting in a broken installation. I had this problem first with Feren OS and now with OM Lx 4. This is a new issue for Calamares, as it did not have this problem with Lx 3 (had another issue which was fixed easily) or the Alpha or Beta, so both you and Feren seem to have picked it up at about the same time. You need to ignore this for the most part, and I have just reported this to Calamares.
This needs a bug report. Post-edit: And a bug report is going to need some information. Like the already requested information. It is not reasonable to expect developers to try to problem solve when they have nothing to work with.
The best problem solver we have has been away recently and still is this week.
Well, now I can certainly try to get that information for you, since the install worked. If the system does not automatically set my monitor and freeze, that is. So I will try.
For an easier and quicker way to provide some information you could do this:
$ sudo sh /usr/bin/omv-bug-report.sh
That will create the file ‘omv-bug-report.log.xz’. Attach that to any bug report and also upload that to this thread. That file may have enough so we have something to work on.
Here’s what I did to try and reproduce this issue. I disconnected my regular monitor and plugged in my TV (hdmi cable in my case) and rebooted my fully updated Rock system. I am writing this while viewing my desktop on my TV. So I can not reproduce the problem myself.
I can report that when I boot this way with TV instead of regular monitor my wifi does not work and is not seen by nmcli which is odd as you would not think that would be affected by graphics. But with ethernet connected all appears to be working here.
Post-edit: Upon rebooting with TV as monitor it seems that things are sometimes hesitant, you have to wait for things to work until desktop settles in, and sometimes wifi does work, sometimes it doesn’t. But for my hardware this does seem to be working now.
Post-edit-2: Don’t know for sure about this but based on what I’m seeing when you see your system appear to “freeze” maybe that is temporary and if you wait long enough system will start working. That is what it seems like here.
My computers all have Intel graphics this one has:
$ inxi -G
Graphics: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics driver: i915 v: kernel
Display: x11 server: OpenMandriva X.org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa DRI Intel Haswell Desktop v: 4.5 Mesa 19.1.0
The above post were done on my desktop where I can unplug my regular monitor. I try this on a notebook and it does not work well at all. So my above posts are meant to show that some part of this is working but there are clearly some issues with this also.
You all should know by now I’m a user in terms on knowledge not a developer. However I’m starting to wonder if this is not somehow related to how systemd and graphics work together? Or not, just wondering.
It seems then that this is related to the (VGA) TV screen. Since you have installed Lx4 and it boots right up to the point of display detection. Ben points out that it took a which to stabilise have you tried giving it some time?
Getting more diagnostics is important for us to have any chance of finding out what is breaking.
To do this you will need to first boot the INSTALLED sytem to the point when the display appears to lock up. I have a feeling this might be something quite simple. Most laptops have key combination that switches the display output from the integral screen to an external screen. It could be that on that there is a race between the activation of these key combinations and the screen selection program.
Have you tried manually switching back to the laptop screen using the key combination. Can you reactivate the laptop screen?
If this does not work try pressing alt+ctrl+F2 does this switch either display to console mode (command prompt). If it does then we can get some diagnostics immediately.
This command:-
sudo journalctl -b --nopager >bootlog.txt
Will create the file bootlog.txt in your home directory please attach this file to the bug report.
Please also attach the file .local/share/sddm/xorg-session.log from your home directory.
If you are unable to activate the console mode with alt+ctrl+F2 then reboot the machine without the TV screen connected and run this slightly changed command to get the info required.
sudo journalctl -b -1 --nopager >bootlog.txt
Again please attach the the file .local/share/sddm/xorg-session.log from your home directory.
I would encourage you to file a bug report for this problem so that all developers on the team get to view the problem. This may prompt additional responses.
2 Likes
At the present time, now that I have the system (OM4) installed, it boots up, shows the flowered screen, plays the music, and while the music is playing the screen blanks. I have waited several minutes and nothing else happens. I have a black screen with a mouse pointer, which moves freely as directed, but nothing else.
I believe my next move is to attempt to get out of KDE, I believe the keystrokes are Ctrl-Alt-F3… am I correct? Without this, there is no way to get to a terminal, except to reinstall (without telling OM4 to use the external monitor, hurting my eyes) and then run whatever commands would be wanted from Terminal.
They are called VTs or Virtual Terminals. You are correct in how to access them. To be specific the keys Ctl>Alt>F2-6 should all go to a VT. To return to desktop is Ctl>Alt>F1. If you can do that using the TV and gather the information that will be awesome. Otherwise follow what @Colin suggests as he is a developer and I’m not. In a VT you should be able to do anything you would in Konsole or any other terminal on your desktop.
And I do realize this is not exactly easy for you. It will be helpful for OM the distro if we can find what is wrong and get it corrected so your efforts are much appreciated.
Continuing the discussion from OM Lx 4.0 'LIve' ISO does not work with TV Monitor:
I just ran my phone with video for a seven-minute boot process, at the end of which I did Ctrl-alt-f3, got to a terminal, and created the bug report you requested. My only difficulty now is accessing that bug report and sending it to you. I suppose I could display it on the screen and take a photo but it may be larger than the photo.
OK, I’m back on my desktop continuing this. The phone version of Firefox was harder than I thought it would be to use in this forum.
Education time: How do I get to my OM4 partition and copy the bug report I just created? Those are usually hidden files, and I have yet to successfully access them on a different partition than the one I’m on. I will go try and see if I can get it before waiting for the help just requested.
Update: I managed to get into there. But the report is not there. /usr/bin/omv-bug-report.sh is what I believe I’m looking for… Oops was looking on the wrong partition.
Moderator: Removed script. Please attach things like that as a .txt file. Anything longer than 20 lines should go in a .txt file and attach the file here.