![]() Registered Member ![]()
|
Hello
I use HP Pavilion g6 with secondary monitor attached. Native resolutions are 1366x768 (the built-in one) and 1920x1080 (the external one). In last 6 months I've been using Fedora 18 with KDE and everything worked just fine. KDE recognized second monitor and both of them worked in they native resolutions. Last week I did clean install of Fedora 19. The external monitor didn't show up under Settings, and I've got only three choices for the built-in one: 1024x768, 800x600 and 640x480. This morning, with no apparent reason, KDE started in it's native resolution. The choices were 1366x768 (native) and 1368x768. It was still unaware of the second monitor. However, when I restarted the system after minor kernel update, it started in 1366x768, but after about 20 seconds it spontaneously switched back to 1024x768. Can anyone help me solve this please. |
![]() Administrator ![]()
|
Can you check the output of "glxinfo" to see if your system is using hardware direct rendering, or software rendering?
Also, please check /usr/share/X11/xorg.conf.d/ to see if anything is forcing the usage of "fbdev" or drivers not suitable for your hardware.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
![]() Registered Member ![]()
|
glxinfo output:
The content of /usr/share/X11/xorg.conf.d/:
I'm not sure what to look for. The files seem to deal with input devices (touchpads and mice), except for glamor.conf who's content is:
No mention of fbdev.
Last edited by tap3ah on Mon Jul 15, 2013 8:34 am, edited 1 time in total.
|
![]() Administrator ![]()
|
That is the "llvmpipe" software renderer. What type of graphics card does your system have?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
![]() Registered Member ![]()
|
I just checked. Apparently it has two graphic adapters: Intel HD and Radeon HD 6470M.
|
![]() Administrator ![]()
|
Okay, that means you have some form of Hybrid graphics then, which complicates matters. Can you try examining the content of /var/log/Xorg.0.log to see what X thinks of your system state? It should reveal which driver(s) it is trying to use, and which ones it ends up using.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
![]() Registered Member ![]()
|
The content of /var/log/Xorg.0.log. For convenience, I cut out the list of arguments for each Mode.
|
![]() Administrator ![]()
|
Ah, in this case the Intel kernel module is unavailable because you have disabled mode setting.
You need to reboot with mode setting enabled in your kernel (simply removing the nomodeset kernel argument should suffice), after which it should all start working properly again.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
![]() Registered Member ![]()
|
Bingo! It works!
I started Fedora for the first time with nomodeset argument and didn't realize that pressing F12 saves changes into grub.cfg. Thanks a lot, mate, you've been more than helpful. |
Registered users: Baidu [Spider], Bing [Bot], Google [Bot]