[opensuse-factory] [Intel/13.2] xorg.conf.d/50-monitor.conf, xorg.conf, & EDID preferred are ignored
Looks like no automagic X for Intel users. xf86-video-intel-2.99.916-2.1 on the 13.2 mirrors was built 6 October, meaning https://bugzilla.opensuse.org/show_bug.cgi?id=901506 didn't get a fix, and neither has X11:XOrg as yet. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
I had no time till now to get a proper patch(set) tested on top of 916. You may use "home:tobijk:X11:XOrg" which just contains a recent snapshot (which works properly at least for me ;-) ). Greetings, Tobias On 01.11.2014 18:45, Felix Miata wrote:
Looks like no automagic X for Intel users. xf86-video-intel-2.99.916-2.1 on the 13.2 mirrors was built 6 October, meaning https://bugzilla.opensuse.org/show_bug.cgi?id=901506 didn't get a fix, and neither has X11:XOrg as yet.
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Tobias Klausmann composed on 2014-11-01 11:45 (UTC+0100):
Felix Miata wrote:
Looks like no automagic X for Intel users. xf86-video-intel-2.99.916-2.1 on the 13.2 mirrors was built 6 October, meaning https://bugzilla.opensuse.org/show_bug.cgi?id=901506 didn't get a fix, and neither has X11:XOrg as yet.
I had no time till now to get a proper patch(set) tested on top of 916. You may use "home:tobijk:X11:XOrg" which just contains a recent snapshot (which works properly at least for me ;-) ).
xf86-video-intel-2.99.916.2-179.1.x86_64 from that repo produced no improvement here. Manual configuration is still required to escape from 1024x768. :-( 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03) (VGA cable only connection used) and 00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02) sumski a month or more ago had a git3.0.0 that worked but seems to have been replaced by the broken 2.99.91x or disappeared altogether. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 02.11.2014 03:59, Felix Miata wrote:
(snip) xf86-video-intel-2.99.916.2-179.1.x86_64 from that repo produced no improvement here. Manual configuration is still required to escape from 1024x768. :-(
00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03) (VGA cable only connection used)
and
00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02)
sumski a month or more ago had a git3.0.0 that worked but seems to have been replaced by the broken 2.99.91x or disappeared altogether.
Well i can just state that the patches noted in https://bugs.freedesktop.org/show_bug.cgi?id=8501 are included in that build. Maybe it broke again, or sumski fixed it differently. sumski, any advice? :) (Please note: 2.99.x versions are 3.0 prereleases, i'm not aware of a special branch for 3.0) Tobias -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op zondag 2 november 2014 04:29:13 schreef Tobias Klausmann:
On 02.11.2014 03:59, Felix Miata wrote:
(snip) xf86-video-intel-2.99.916.2-179.1.x86_64 from that repo produced no improvement here. Manual configuration is still required to escape from 1024x768. :-(
00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03) (VGA cable only connection used)
and
00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02)
sumski a month or more ago had a git3.0.0 that worked but seems to have been replaced by the broken 2.99.91x or disappeared altogether. Well i can just state that the patches noted in https://bugs.freedesktop.org/show_bug.cgi?id=8501 are included in that build. Maybe it broke again, or sumski fixed it differently.
sumski, any advice? :)
(Please note: 2.99.x versions are 3.0 prereleases, i'm not aware of a special branch for 3.0)
Tobias
I have a new laptop with Intel N3530 chip with Intel HD Graphics. I can use openSUSE 13.2RC1 and Factory only in Rescue mode. It boots in non-Rescue mode up to the log in screen for KDE, but soon after logging in and the appearance of the first element in the KDE splash screen, a picture of a hard disc, the screen becomes black. Using ssh to get into the system from another system works OK, however I can't find any error message why the screen becomes black. Does this sound the same as the above problem? If so, what should I do? -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On November 3, 2014 6:51:29 AM EST, Freek de Kruijf
On 02.11.2014 03:59, Felix Miata wrote:
(snip) xf86-video-intel-2.99.916.2-179.1.x86_64 from that repo produced no improvement here. Manual configuration is still required to escape from 1024x768. :-(
00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev
cable only connection used)
and
00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02)
sumski a month or more ago had a git3.0.0 that worked but seems to have been replaced by the broken 2.99.91x or disappeared altogether. Well i can just state that the patches noted in https://bugs.freedesktop.org/show_bug.cgi?id=8501 are included in
Op zondag 2 november 2014 04:29:13 schreef Tobias Klausmann: 03) (VGA that
build. Maybe it broke again, or sumski fixed it differently.
sumski, any advice? :)
(Please note: 2.99.x versions are 3.0 prereleases, i'm not aware of a special branch for 3.0)
Tobias
I have a new laptop with Intel N3530 chip with Intel HD Graphics. I can use openSUSE 13.2RC1 and Factory only in Rescue mode. It boots in non-Rescue mode up to the log in screen for KDE, but soon after logging in and the appearance of the first element in the KDE splash screen, a picture of a hard disc, the screen becomes black. Using ssh to get into the system from another system works OK, however I can't find any error message why the screen becomes black.
Does this sound the same as the above problem? If so, what should I do?
I don't do anything fancy with my X interface and there is a bug on my laptop when I run the Intel driver, so I simply uninstall it. I can still run X/KDE. zypper rm xf86-video-intel My bug: http://bugzilla.opensuse.org/show_bug.cgi?id=899610 Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Freek de Kruijf composed on 2014-11-03 12:51 (UTC+0100):
I have a new laptop with Intel N3530 chip with Intel HD Graphics. I can use openSUSE 13.2RC1 and Factory only in Rescue mode. It boots in non-Rescue mode up to the log in screen for KDE, but soon after logging in and the appearance of the first element in the KDE splash screen, a picture of a hard disc, the screen becomes black. Using ssh to get into the system from another system works OK, however I can't find any error message why the screen becomes black.
Does this sound the same as the above problem?
This thread is about: https://bugzilla.opensuse.org/show_bug.cgi?id=901506 which is upstream: https://bugs.freedesktop.org/show_bug.cgi?id=85016
If so, what should I do?
I recommend to ask on intel-gfx@lists.freedesktop.org to see if it is a known issue or already fixed or if there is a workaround. Searching its archive and https://bugs.freedesktop.org/query.cgi might find an answer faster. Can you log into IceWM or TWM session without going black? If so, problem would be in KDE. Possibly asking on kde@mail.kde.org list could be fruitful. Does configuring 'Option "Composite" "Disable"' (global bling disable) in /etc/X11/xorg.conf* help? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op maandag 3 november 2014 09:37:35 schreef Felix Miata:
Freek de Kruijf composed on 2014-11-03 12:51 (UTC+0100):
I have a new laptop with Intel N3530 chip with Intel HD Graphics. I can use openSUSE 13.2RC1 and Factory only in Rescue mode. It boots in non-Rescue mode up to the log in screen for KDE, but soon after logging in and the appearance of the first element in the KDE splash screen, a picture of a hard disc, the screen becomes black. Using ssh to get into the system from another system works OK, however I can't find any error message why the screen becomes black.
Does this sound the same as the above problem?
This thread is about: https://bugzilla.opensuse.org/show_bug.cgi?id=901506 which is upstream: https://bugs.freedesktop.org/show_bug.cgi?id=85016
If so, what should I do?
I recommend to ask on intel-gfx@lists.freedesktop.org to see if it is a known issue or already fixed or if there is a workaround. Searching its archive and https://bugs.freedesktop.org/query.cgi might find an answer faster.
Maybe in the end I will do that.
Can you log into IceWM or TWM session without going black? If so, problem would be in KDE. Possibly asking on kde@mail.kde.org list could be fruitful.
What I wrote above is only the first time I try to log in into KDE. After that booting the system already gives a black screen early in boot process. In another thread removing xf86-video-intel is suggested, however that did not solve the problem, but I still can use the Rescue mode.
Does configuring 'Option "Composite" "Disable"' (global bling disable) in /etc/X11/xorg.conf* help?
I did not find anything in these configuration files about this. -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Freek de Kruijf composed on 2014-11-03 22:31 (UTC+0100):
Maybe in the end I will do that.
What I wrote above is only the first time I try to log in into KDE. After that booting the system already gives a black screen early in boot process.
In another thread removing xf86-video-intel is suggested, however that did not solve the problem, but I still can use the Rescue mode.
Does not rescue mode result in the login greeter where you can select which DM to start? Unless you also have other video besides Intel, you should reinstall xf86-video-intel, and after trying to use it, pastebin /var/log/Xorg.0.log. http://susepaste.org/
Does configuring 'Option "Composite" "Disable"' (global bling disable) in /etc/X11/xorg.conf* help?
I did not find anything in these configuration files about this.
It needs to go into /etc/X11/xorg.conf.d/ in a file you create and name. I named mine 70-extensions.conf with the following as its content: Section "Extensions" Option "Composite" "Disable" EndSection Optionally (instead) you could put that in /etc/X11/xorg.conf. Either should have identical effect, or not, depending on if compositing has anything to do with your trouble. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op maandag 3 november 2014 17:01:42 schreef Felix Miata:
Freek de Kruijf composed on 2014-11-03 22:31 (UTC+0100):
Maybe in the end I will do that.
What I wrote above is only the first time I try to log in into KDE. After that booting the system already gives a black screen early in boot process.
In another thread removing xf86-video-intel is suggested, however that did not solve the problem, but I still can use the Rescue mode.
Does not rescue mode result in the login greeter where you can select which DM to start?
Yes and I can use KDE as I used to.
Unless you also have other video besides Intel, you should reinstall xf86-video-intel, and after trying to use it, pastebin /var/log/Xorg.0.log. http://susepaste.org/
It is a laptop and I only have an Intel chip N3530 (4 cores) and I assume it has Intel HD Graphics incorporated with 8 GB memory.
Does configuring 'Option "Composite" "Disable"' (global bling disable) in /etc/X11/xorg.conf* help?
I did not find anything in these configuration files about this.
It needs to go into /etc/X11/xorg.conf.d/ in a file you create and name. I named mine 70-extensions.conf with the following as its content:
Section "Extensions" Option "Composite" "Disable" EndSection
Optionally (instead) you could put that in /etc/X11/xorg.conf. Either should have identical effect, or not, depending on if compositing has anything to do with your trouble.
Installed xf86-video-intel again and added the suggested 70-extension.conf. Did not change anything. Output of lspci is: 00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register (rev 0e) 00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0e) 00:13.0 SATA controller: Intel Corporation Device 0f23 (rev 0e) 00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series USB xHCI (rev 0e) 00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine (rev 0e) 00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller (rev 0e) 00:1c.0 PCI bridge: Intel Corporation Device 0f48 (rev 0e) 00:1c.1 PCI bridge: Intel Corporation Device 0f4a (rev 0e) 00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit (rev 0e) 00:1f.3 SMBus: Intel Corporation Device 0f12 (rev 0e) 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5287 (rev 01) 01:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 12) 02:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01) Searching for warnings and errors in Xorg.0.log* linux-dyyx:~ # grep EE /var/log/Xorg.0.log.old [ 25.734] Current Operating System: Linux linux-dyyx 3.17.1-1.g5c4d099- desktop #1 SMP PREEMPT Sat Oct 18 23:36:23 UTC 2014 (5c4d099) x86_64 (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 25.840] (EE) Failed to load module "vboxvideo" (module does not exist, 0) [ 25.842] (EE) Failed to load module "vmware" (module does not exist, 0) [ 25.845] (EE) open /dev/dri/card0: No such file or directory [ 25.846] (EE) open /dev/dri/card0: No such file or directory [ 25.847] (EE) Screen 0 deleted because of no matching config section. [ 25.876] (EE) AIGLX: reverting to software rendering [ 207.357] (EE) Server terminated successfully (0). Closing log file. linux-dyyx:~ # grep EE /var/log/Xorg.0.log [ 27.153] Current Operating System: Linux linux-dyyx 3.17.1-1.g5c4d099- desktop #1 SMP PREEMPT Sat Oct 18 23:36:23 UTC 2014 (5c4d099) x86_64 (WW) warning, (EE) error, (NI) not implemented, (??) unknown. linux-dyyx:~ # grep WW /var/log/Xorg.0.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 27.167] (WW) The directory "/usr/share/fonts/misc/sgi" does not exist. [ 27.512] (WW) Falling back to old probe method for modesetting [ 27.513] (WW) Falling back to old probe method for fbdev [ 27.515] (WW) Falling back to old probe method for vesa [ 28.132] (WW) evdev: MOSART Semi. 2.4G Keyboard Mouse: ignoring absolute axes. linux-dyyx:~ # grep WW /var/log/Xorg.0.log.old (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 25.754] (WW) The directory "/usr/share/fonts/misc/sgi" does not exist. [ 25.840] (WW) Warning, couldn't open module vboxvideo [ 25.841] (WW) Warning, couldn't open module vmware [ 25.845] (WW) Falling back to old probe method for modesetting [ 25.847] (WW) Falling back to old probe method for vesa [ 26.374] (WW) evdev: MOSART Semi. 2.4G Keyboard Mouse: ignoring absolute axes. linux-dyyx:~ # -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Freek de Kruijf composed on 2014-11-04 00:02 (UTC+0100):
xf86-video-intel, and after trying to use it, pastebin /var/log/Xorg.0.log. http://susepaste.org/
Searching for warnings and errors in Xorg.0.log*
linux-dyyx:~ # grep EE /var/log/Xorg.0.log.old linux-dyyx:~ # grep EE /var/log/Xorg.0.log linux-dyyx:~ # grep WW /var/log/Xorg.0.log linux-dyyx:~ # grep WW /var/log/Xorg.0.log.old
Not everything in Xorg.0.log relevant to troubleshooting shows up on an EE or WW line. e.g. What's on your kernel cmdline when not using rescue stanza? How does it differ from using rescue WRT video? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op maandag 3 november 2014 18:34:47 schreef Felix Miata:
Freek de Kruijf composed on 2014-11-04 00:02 (UTC+0100):
Not everything in Xorg.0.log relevant to troubleshooting shows up on an EE or WW line. e.g. What's on your kernel cmdline when not using rescue stanza? How does it differ from using rescue WRT video?
The strange thing in the earlier log lines is that in Rescue mode there is an error message about a missing config file for 0:, where this is not present in the log of the normal boot Xorg.0.log.old. To answer your question: Normal boot has: linuxefi /boot/vmlinuz... root=UUID=... ro ${extra_cmdline} resume=/dev.... Rescue boot has: linuxefi /boot/vmlinuz... root=UUID=... ro ${extra_cmdline} showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 04.11.2014 01:08, Freek de Kruijf wrote:
Freek de Kruijf composed on 2014-11-04 00:02 (UTC+0100): Not everything in Xorg.0.log relevant to troubleshooting shows up on an EE or WW line. e.g. What's on your kernel cmdline when not using rescue stanza? How does it differ from using rescue WRT video? The strange thing in the earlier log lines is that in Rescue mode there is an error message about a missing config file for 0:, where this is not present in
Op maandag 3 november 2014 18:34:47 schreef Felix Miata: the log of the normal boot Xorg.0.log.old.
To answer your question:
Normal boot has:
linuxefi /boot/vmlinuz... root=UUID=... ro ${extra_cmdline} resume=/dev....
Rescue boot has:
linuxefi /boot/vmlinuz... root=UUID=... ro ${extra_cmdline} showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe
Attach (pastebin) full dmesg and Xorg.0.log, maybe that shows something... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Freek de Kruijf composed on 2014-11-04 01:08 (UTC+0100):
Normal boot has:
linuxefi /boot/vmlinuz... root=UUID=... ro ${extra_cmdline} resume=/dev....
Rescue boot has:
linuxefi /boot/vmlinuz... root=UUID=... ro ${extra_cmdline} showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe
Not having xf86-cideo-intel installed produces same result as nomodeset: you're running on a fallback driver instead of the Intel driver, which would be included in the Xorg.0.log Tobias and I asked for unassociated with any EE or WW. With it installed, the deault stanza wants the Intel driver, but for your hardware something's obviously broken. Something else to try (besides providing dmesg and Xorg.0.log): Add to kernel cmdline splash=verbose and if quiet is included, get rid of it. It could be the real "black" problem is Plymouth conflicting with the Intel driver. The Intel driver in 13.2 is clearly known to be broken at least for some hardware. Maybe the original thread problem is yours as well, just a bit differently manifested from reports. The log almost certainly will provide more insight. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op maandag 3 november 2014 19:38:37 schreef Felix Miata:
Freek de Kruijf composed on 2014-11-04 01:08 (UTC+0100):
Normal boot has:
linuxefi /boot/vmlinuz... root=UUID=... ro ${extra_cmdline} resume=/dev....
Rescue boot has:
linuxefi /boot/vmlinuz... root=UUID=... ro ${extra_cmdline} showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe
Not having xf86-cideo-intel installed produces same result as nomodeset: you're running on a fallback driver instead of the Intel driver, which would be included in the Xorg.0.log Tobias and I asked for unassociated with any EE or WW. With it installed, the deault stanza wants the Intel driver, but for your hardware something's obviously broken.
Something else to try (besides providing dmesg and Xorg.0.log):
Add to kernel cmdline splash=verbose and if quiet is included, get rid of it. It could be the real "black" problem is Plymouth conflicting with the Intel driver.
The Intel driver in 13.2 is clearly known to be broken at least for some hardware. Maybe the original thread problem is yours as well, just a bit differently manifested from reports. The log almost certainly will provide more insight.
Just by chance I started the laptop on battery without plugging in the power. Now the system came up, not using the Rescue mode, with the log in screen and I could log in into KDE and do whatever I need to do. At that time I realized I did not turn on the power using the switch on the switch box, so I turned on the power and immediately the screen turned black. Unplugging the power gave me back the desktop I was working on and I could continue. The battery lasts 5 hours, so I have some time to finish what I was doing. So it must have something to do with a module which controls power and which is turned off using Rescue mode. Clicking on the battery icon, I found a check box to enable/disable power control, which I unchecked. Now I can plug in the power and do not get a black screen. So what module is causing this? -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Mandag den 3. november 2014 22:31:24 skrev Freek de Kruijf:
Op maandag 3 november 2014 09:37:35 schreef Felix Miata:
Freek de Kruijf composed on 2014-11-03 12:51 (UTC+0100):
I have a new laptop with Intel N3530 chip with Intel HD Graphics. I can use openSUSE 13.2RC1 and Factory only in Rescue mode. It boots in non-Rescue mode up to the log in screen for KDE, but soon after logging in and the appearance of the first element in the KDE splash screen, a picture of a hard disc, the screen becomes black. Using ssh to get into the system from another system works OK, however I can't find any error message why the screen becomes black.
Does this sound the same as the above problem?
This thread is about: https://bugzilla.opensuse.org/show_bug.cgi?id=901506 which is upstream: https://bugs.freedesktop.org/show_bug.cgi?id=85016
If so, what should I do?
I recommend to ask on intel-gfx@lists.freedesktop.org to see if it is a known issue or already fixed or if there is a workaround. Searching its archive and https://bugs.freedesktop.org/query.cgi might find an answer faster.
Maybe in the end I will do that.
Can you log into IceWM or TWM session without going black? If so, problem would be in KDE. Possibly asking on kde@mail.kde.org list could be fruitful. What I wrote above is only the first time I try to log in into KDE. After that booting the system already gives a black screen early in boot process.
In another thread removing xf86-video-intel is suggested, however that did not solve the problem, but I still can use the Rescue mode.
Does configuring 'Option "Composite" "Disable"' (global bling disable) in /etc/X11/xorg.conf* help?
I did not find anything in these configuration files about this.
Not sure if it's relevant. But, yesterday I dup'ed my Factory/Plasma5 virtualbox installation, for the first time in 3-4 weeks, and it got me a black screen too. I had previously switched the system to lightdm, but switching back to kdm, seemed to fix the problem. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 04.11.2014 um 11:04 schrieb Martin Schlander:
Not sure if it's relevant.
But, yesterday I dup'ed my Factory/Plasma5 virtualbox installation, for the first time in 3-4 weeks, and it got me a black screen too.
I had previously switched the system to lightdm, but switching back to kdm, seemed to fix the problem.
In my case, gdm goes black or just shows the background image. Installing and selecting lightdm (or xdm) worked better for me. Upgrade was via zypper dup. Still, I am seeing screen artifacts related to the mouse cursor. And it seems three (active) screens are recognized, whereas in 13.1 it was just two screens. The notebook has both Intel i915 and AMD radeon graphics. The integrated one seems to be active (Intel Sandybridge), and vgaswitcheroo is unable to change power settings or to switch. Regards, Andreas -- SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 21284 AG Nürnberg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
At Thu, 13 Nov 2014 12:09:12 +0100, Andreas Färber wrote:
Am 04.11.2014 um 11:04 schrieb Martin Schlander:
Not sure if it's relevant.
But, yesterday I dup'ed my Factory/Plasma5 virtualbox installation, for the first time in 3-4 weeks, and it got me a black screen too.
I had previously switched the system to lightdm, but switching back to kdm, seemed to fix the problem.
In my case, gdm goes black or just shows the background image. Installing and selecting lightdm (or xdm) worked better for me. Upgrade was via zypper dup.
Still, I am seeing screen artifacts related to the mouse cursor.
And it seems three (active) screens are recognized, whereas in 13.1 it was just two screens. The notebook has both Intel i915 and AMD radeon graphics. The integrated one seems to be active (Intel Sandybridge), and vgaswitcheroo is unable to change power settings or to switch.
Is it a hybrid (aka muxless or optimus) graphics or switchable graphics? In the latter case, we've got already a bug report (bnc#904417). The power of DGPU is controlled in runtime in the recent kernels, so vgaswitcheroo can't turn off explicitly. It seems mostly working for hybrid graphics case, but the switchable graphics might be problematic with this... Takashi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (7)
-
Andreas Färber -
Felix Miata -
Freek de Kruijf -
Greg Freemyer -
Martin Schlander -
Takashi Iwai -
Tobias Klausmann