Knowledgebase

Portal Home > Knowledgebase > Articles Database > Screen Resolution issue

Screen Resolution issue

Posted by mtrc, 02-11-2015, 10:45 AM

I try to connect by KVM to a Fedora machine. After kernel selection the screen goes automatically to 1600x1200 and become black, useless. I suppose KVM console doesn't support big resolutions. I tried to change resolution by ssh, but everything failed to change this 1600x1200 mode. xrandr Can't open display Xorg Fatal server error: (EE) no screens found(EE) Any idea?

---

Posted by mtrc, 02-11-2015, 11:09 PM

I have added a .conf file under /etc/X11 with these lines inside, but without any change. Section "Screen" Identifier "Default Screen" DefaultDepth 24 SubSection "Display" Depth 24 Modes "1280x1024" "1024x768" "640x480" EndSubSection EndSection Section "Monitor" Identifier "VGA1" Option "PreferredMode" "1024x768" EndSection Can someone please give me an advice?

---

Posted by YUPAPA, 02-12-2015, 03:32 AM

This looks like a driver / module issue to me rather than Xorg config. Use Xorg -configure to create a new xorg.conf and use the driver directive to load the proper driver.

---

Posted by mtrc, 02-12-2015, 04:13 AM

Xorg returns Loading extension GLX (EE) Fatal server error: (EE) no screens found(EE)

---

Posted by mtrc, 02-12-2015, 07:36 AM

Indeed it has nothing to do with Xorg. It is about text console screen resolution actually. I found this on other forum: The newest kernels have moved the video mode setting into the kernel. So all the programming of the hardware specific clock rates and registers on the video card happen in the kernel rather than in the X driver when the X server starts.. This makes it possible to have high resolution nice looking splash (boot) screens and flicker free transitions from boot splash to login screen. Unfortunately, on some cards this doesnt work properly and you end up with a black screen. Adding the nomodeset parameter instructs the kernel to not load video drivers and use BIOS modes instead until X is loaded. nomodeset kernel parameter solved my issue as I don't need such a high resolution on console.

---

Add to Favourites    Print this Article

bigvps down? (Views: 783)

Current Bad Experience with Coast Internet Solutions (Views: 762)

What mod_security ruleset are you using? (Views: 701)

SSL On Shared Accounts. (Views: 722)

Startcom SSL (Views: 706)