I have a video driver related issue. I installed OpenSUSE Leap 42.2 on my laptop (Lenovo Thinkpad R400) and it can’t use the secondary monitor to display the desktop. Let me explain my setup.
I have the laptop placed in a docking station and attached a monitor through the VGA display port on the dock. I currently use the monitor as my main display device and the laptop screen is not used, since the laptop is not even opened when I start it (basically I use the laptop as a desktop PC with a monitor attached). While for Ubuntu this is not an issue, OpenSUSE will not use the monitor for display.
I have booted OpenSUSE, with the cover of the laptop not opened, and it puts the laptop in sleep mode. The monitor does not show anything. If I boot OpenSUSE with the laptop opened then it uses the laptop’s display to show the desktop.
Not sure what is the issue here, as this is my first time running Linux on a PC (not within a virtual machine). I have Ubuntu installed but I don’t get this issue with it.
Here is the result from running the command “hwinfo --gfxcard”:
Neither suggestions helped. In the System settings, under display and monitor I cannot find my monitor as a selectable display, only the laptop display, named “default”.
Regarding the suspend issue that you mentioned, I don’t think it is related to my issue.
Here is the code that I get when using the “xrandr” command:
mariusv@linux-demi:~> xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1280 x 800, current 1280 x 800, maximum 1280 x 800
default connected primary 1280x800+0+0 0mm x 0mm
1280x800 76.00*
I tried to use it with “sudo” but is says that it “can’t open the display”.
I have looked in the Yast settings>display to see if the monitor is detected, but couldn’t find it at all. All I could find was the laptop display.
Umm, unless I didn’t read your first post correctly, I’m pretty sure you conveyed that you have a suspend issue as well. If that is the case, then read the suggestion as it pertains to lid closes and docking.
Revisiting your /lspci output, and what I missed earlier is that, it is clear that the intel kernel driver is not loaded. The output from hwinfo is deceiving.
Then I should try to load the intel kernel driver.
Not sure if it helps, but I did mention that I have the laptop docked in the docking station and the monitor is connected through the dock to the laptop. When I have the laptop lid closed and boot OpenSUSE after I select to boot OpenSUSE it loads up to the point where the splash screen should start and the loading of the KDE environment, but instead the laptop is put to sleep mode. If I have the lid opened then it boots normally and ignores the monitor.
Yes, and you can achieve that by removing the nomodeset boot option, as it effectively prevents the kernel driver from loading. Right now you’d be using the generic fbdev driver. Out of curiosity, why did you have that (nomodeset) placed there?
Not sure if it helps, but I did mention that I have the laptop docked in the docking station and the monitor is connected through the dock to the laptop. When I have the laptop lid closed and boot OpenSUSE after I select to boot OpenSUSE it loads up to the point where the splash screen should start and the loading of the KDE environment, but instead the laptop is put to sleep mode. If I have the lid opened then it boots normally and ignores the monitor.
Unless you changed something, by default, a “lid close” is = suspend. Similarly, the default for “when lid closed and docked” is = ignore.
IIRC, the fbdev driver doesn’t do multi-monitor … there is a single video output, and if your video adapter happens to have multiple outputs, then the signal on all outputs is simply a clone of the one output signal provided by the fbdev. I believe the above logind logic is kicking in after login – simply, because the laptop’s panel (which is attached to the primary output of the video adapter) is not receiving a signal, it believes that it is undocked and a simple “lid closed” has occured; hence sleep. I believe that when the intel driver stack is employed, this should go away.
I tried to remove the “nomodeset” option from the CMDLINE file but it just wouldn’t write the changes. I get the Input/Output error message in Nano editor. So, no luck trying to remove it from the file. Any other suggestions?
Use the boatloader module available in Yast > System > Boat Loader > Kernel Parameters … then remove it from the “optional kernel command lne parameter” box, click okay, and your linux boot command will be re-written for the grub boat loader. Next time you reboot your system, you’re kernel drm graphics driver will be able to do a modeset