[opensuse] graphic display blinks
Hello, Here I just ask for general debug ideas, as the relevant computer is not in my hands, but I may have to work on it or it's brothers some day. it's an old computer, 7 years old, but sufficient and 64 bits, but only 2Gb ram. Intel graphics. Desktop. I first installed tumbleweed 32 bits, then (today) tested live Leap 15, with same result: when started as init 3 (number 3 added at the end on grub linux line), works. When started as default, the screen blinks with around 1/2s frequency, obviously its's X that stops and restart as the keyboard is nearly not responsive (unusable). I tried nomodeset, vga on linux grub line, same result start X from terminal and blinking, the blinking continues even after the return under terminal. But... opensuse 12.1 works as expected I could install 13.2 32 bits from live usb and it worked with graphics nothing visible in X logs, apart the last line (stopped on error (1)) what can I save as ideas to test next time? the problem was visible at my LUG meeting but also at the owners home (different monitor) thanks jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
jdd@dodin.org composed on 2018-04-28 18:28 (UTC+0200):
Here I just ask for general debug ideas, as the relevant computer is not in my hands, but I may have to work on it or it's brothers some day.
it's an old computer, 7 years old, but sufficient and 64 bits, but only 2Gb ram. Intel graphics. Desktop.
Sounds like Intel's Sandy Bridge chipset and HD 2000 graphics.
I first installed tumbleweed 32 bits, then (today) tested live Leap 15, with same result: when started as init 3 (number 3 added at the end on grub linux line), works.
When started as default, the screen blinks with around 1/2s frequency, obviously its's X that stops and restart as the keyboard is nearly not responsive (unusable).
I tried nomodeset, vga on linux grub line, same result
The two competent Xorg video drivers (modesetting, internal to Xorg; xf86-video-intel) for use with Intel absolutely require modesetting. nomodeset on cmdline is for repairing problems or troubleshooting only. The crude fallback xorg drivers (fbdev & vesa) may or may not be functional while modesetting is disabled.
start X from terminal and blinking, the blinking continues even after the return under terminal.
Does it also blink if you boot with 3 on cmdline, login as root, then try 'startx'? If that works, try startx as normal user (probably will generate a permissions error).
But...
opensuse 12.1 works as expected
I could install 13.2 32 bits from live usb and it worked with graphics
nothing visible in X logs, apart the last line (stopped on error (1))
what can I save as ideas to test next time?
the problem was visible at my LUG meeting but also at the owners home (different monitor)
Things to try (in order): 1-if the PC and display have alternate cable types that could be used, try the different cable type(s) (DVI, VGA, DisplayPort, HDMI) 2-'zypper rm xf86-video-intel' (simplest way to switch to modesetting xorg driver). If not already installed, install it. 3-drm-kmp-default: if installed, remove; if not installed, install 4-'zypper rm plymouth' (first test with plymouth.enable=0 on cmdline) 5-Replace sddm with kdm or lightdm or gdm. Run 'lspci -nnk | grep -A4 VGA' and 'inxi -G -c0' and report results if problem remains and you need to continue the thread. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Does it also blink if you boot with 3 on cmdline, login as root, then
Le 28/04/2018 à 19:16, Felix Miata a écrit : try 'startx'? If that works, try startx as normal user (probably will generate a permissions error). since some (large) amount of time, startx do not works as root, say "no display". This install was from a live usb pen, so I had only kde
Things to try (in order):
I will save this for future use :-)
1-if the PC and display have alternate cable types that could be used, try the different cable type(s) (DVI, VGA, DisplayPort, HDMI)
good idea. I didn't test this
2-'zypper rm xf86-video-intel' (simplest way to switch to modesetting xorg driver). If not already installed, install it.
was not installed, the install didn't change anything
3-drm-kmp-default: if installed, remove; if not installed, install
4-'zypper rm plymouth' (first test with plymouth.enable=0 on cmdline)
not tested, but plymouth starts and run without problem - the blink happen only when X starts.
5-Replace sddm with kdm or lightdm or gdm.
not tested, but sddm initiates the blinking
Run 'lspci -nnk | grep -A4 VGA' and 'inxi -G -c0' and report results if problem remains and you need to continue the thread.
ok The first install of tumbleweed was made 15 days ago, and the owner of the computer asked for help on the french "alionet" forum, but with no result. Given there are on this computer old install perfectly running, is there a way to use the old kernel for test purpose? thanks jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
jdd composed on 2018-04-28 19:45 (UTC+0200):
Felix Miata a écrit :
Does it also blink if you boot with 3 on cmdline, login as root, then try 'startx'? If that works, try startx as normal user (probably will generate a permissions error).
since some (large) amount of time, startx do not works as root, say "no display". This install was from a live usb pen, so I had only kde
Not a problem on the hundreds of Linux installations here, including more than a dozen 42.3, more than 6 15.0 and at least 20 TW. Apparently there exists certain hardware that makes startx a problem: https://bugzilla.opensuse.org/show_bug.cgi?id=1089620...
Given there are on this computer old install perfectly running, is there a way to use the old kernel for test purpose?
For 42.3? TW? By what to you mean "old kernel"? Original 42.3 kernel? Kernel for older distribution release? Any kernel rpm can be downloaded manually and installed via rpm, unless it turns out to require something that is unavailable in the target system. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 28/04/2018 à 20:35, Felix Miata a écrit :
Not a problem on the hundreds of Linux installations here
do you start hundred of installs with startx that your own link say "startx is no longer supported since more than a decade now"? anyway it's not the problem I want to discuss now.
Given there are on this computer old install perfectly running, is there a way to use the old kernel for test purpose?
For 42.3? TW? By what to you mean "old kernel"? Original 42.3 kernel? Kernel for older distribution release?
as said there is a 12.1 install running on this computer (the goal was to install something more modern :-(), so there is a kernel on this system that works jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
jdd@dodin.org composed on 2018-04-28 20:58 (UTC+0200):
Felix Miata a écrit :
Not a problem on the hundreds of Linux installations here
do you start hundred of installs with startx that your own link say "startx is no longer supported since more than a decade now"?
None say anything about support. That "not supported" stuff is from devs such as Stefan Dirsch. Startx is a part of Xorg as provided by upstream freesdesktop.org. It's in every openSUSE and every other Linux release I've ever used, and, as root, _always_ works here unless X is broken so that it cannot be run at all.
Given there are on this computer old install perfectly running, is there a way to use the old kernel for test purpose?
For 42.3? TW? By what to you mean "old kernel"? Original 42.3 kernel? Kernel for older distribution release?
as said there is a 12.1 install running on this computer (the goal was to install something more modern :-(), so there is a kernel on this system that works
12.1 is probably way too old, with only minimal support for systemd. Maybe the extended support 3.12 kernel for 13.1 could be used if you think the kernel is the problem, which I doubt. I do remember when new Sandy Bridge seemed to be particularly troublesome to support. Maybe it still is, and a special kernel or Xorg startup option would solve the blinking??? -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 28/04/2018 à 21:12, Felix Miata a écrit :
12.1 is probably way too old
During my Linux User Group meetings, we try to help people. We often notice, like in this example, people using very old installs we made some years ago, and never caring to upgrade (may be not even update) and with no problem whatsoever :-) Linux is so :-( but there the owner was thinking better to upgrade. At first is seemed to be a 32 bit (7 years old) computer, so my only recent 32bits usb pen was tumbleweed. At the end of the meeting, the screen was blinking and I directed the owner to forum support. He come today saying the forum (Alionet, french openSUSE support) could not solve the problem (no idea what was done). So why I tested the very last leap 15 live usb pen, after discovering the computer was 64 bits, still blinking. , with only minimal support for systemd. Maybe the
extended support 3.12 kernel for 13.1 could be used if you think the kernel is the problem, which I doubt. I do remember when new Sandy Bridge seemed to be particularly troublesome to support. Maybe it still is, and a special kernel or Xorg startup option would solve the blinking???
it's obviously a regression, as 12.1 works and finally after successful test I could install 13.2 :-) still I guess it's a minor fix to do as 12.1 and 13.2 works with graphics. I would like to have Leap15 running. If the fix is simple I could instruct the owner (through mail) to test live Leap 15 with the fix :-) thanks jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 28/04/2018 à 21:12, Felix Miata a écrit :
12.1 is probably way too old
During my Linux User Group meetings, we try to help people. We often notice, like in this example, people using very old installs we made some years ago, and never caring to upgrade (may be not even update) and with no problem whatsoever :-)
Linux is so :-(
but there the owner was thinking better to upgrade. At first is seemed to be a 32 bit (7 years old) computer, so my only recent 32bits usb pen was tumbleweed. At the end of the meeting, the screen was blinking and I directed the owner to forum support. He come today saying the forum (Alionet, french openSUSE support) could not solve the problem (no idea what was done).
So why I tested the very last leap 15 live usb pen, after discovering the computer was 64 bits, still blinking.
, with only minimal support for systemd. Maybe the
extended support 3.12 kernel for 13.1 could be used if you think the kernel is the problem, which I doubt. I do remember when new Sandy Bridge seemed to be particularly troublesome to support. Maybe it still is, and a special kernel or Xorg startup option would solve the blinking???
it's obviously a regression, as 12.1 works and finally after successful test I could install 13.2 :-)
still I guess it's a minor fix to do as 12.1 and 13.2 works with graphics. I would like to have Leap15 running. If the fix is simple I could instruct the owner (through mail) to test live Leap 15 with the fix :-)
thanks jdd Only in case. If this is or should be an ironlake chipset you have to (!) and
In data sabato 28 aprile 2018 21:29:12 CEST, jdd@dodin.org ha scritto: this is a real exclamation mark, to uninstall the package drm-kmp-default. Otherwise older intel chipset will not function (in my experience) after Kernel 4.1 upward. There have been quite some regressions with the intel graphics driver. Not really thinking that Intel or anybody else does even think remotely to fix them. They need to sell new computers, I guess. _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 29/04/2018 à 12:15, stakanov a écrit :
Only in case. If this is or should be an ironlake chipset you have to (!) and this is a real exclamation mark, to uninstall the package drm-kmp-default. Otherwise older intel chipset will not function (in my experience) after Kernel 4.1 upward.
will try this, thanks jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 28/04/18 03:12 PM, Felix Miata wrote:
Startx is a part of Xorg as provided by upstream freesdesktop.org. It's in every openSUSE and every other Linux release I've ever used, and, as root, _always_ works here unless X is broken so that it cannot be run at all.
More specifically: # which startx /usr/bin/startx # rpm -qf /usr/bin/startx xinit-1.3.4-4.3.x86_64 Which version of xinit may vary with release, but that's where it lives, along with ... # rpm -ql xinit /etc/X11/Xresources /etc/X11/xinit /etc/X11/xinit/xinitrc /etc/X11/xinit/xinitrc.common /etc/X11/xinit/xinitrc.d /etc/X11/xinit/xserverrc /etc/skel/.xinitrc.template /usr/bin/keygen /usr/bin/startx /usr/bin/xinit /usr/share/doc/packages/xinit /usr/share/doc/packages/xinit/COPYING /usr/share/doc/packages/xinit/ChangeLog /usr/share/doc/packages/xinit/README /usr/share/man/man1/keygen.1.gz /usr/share/man/man1/startx.1.gz /usr/share/man/man1/xinit.1.gz -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Anton Aylward -
Felix Miata -
jdd＠dodin.org -
stakanov