[EN] light-red vertical line on screen

[Jörg]

Since a few days (unfortunately I do not know exactly) a very thin light-red vertical line is visible on my screen. It starts at the upper edge (5 cm from the left side) and goes down to the lower edge (until 6 cm from the lower edge). In the first moment I thought of a hardware-fault, but in the meantime I noticed that the light-red line disappears when I do "Ctrl+Alt+F1"  during DU.
Any help for a solution of my "little problem" will be appreciated!

Greetings,
Jörg

[dibl]

It could still be hardware, and it probably is, IMHO.

Your graphics chip has "modes".  Character mode is what you see on tty1-6.  Graphics mode is what you see when running X.  So my suspicion would fall on the graphics mode of your GPU.  Try booting a Live CD of some other Linux distribution -- I think you're going to see a red line.  (I wish I would be wrong on that.)

[absolut]

Jörg,
from your signature i read that you seem to have two cards...

please show us inxi -v3 and /var/log/Xorg.0.log

[Jörg]

Hello dibl,
thank you for your kind explanations. I have tried a Live CD, but as you thought already: the red line is present from the very beginning to the shutdown. So it must be a hardware problem?!

Hello absolut,
here is the output of:

Code: [Select]

[     
[10:54:59] root@thinkpad-s540:/home/jorg# inxi -v3
System:    Host: thinkpad-s540 Kernel: 3.17-1.towo.2-siduction-amd64 x86_64 (64 bit gcc: 4.9.1)
           Desktop: KDE 4.14.2 (Qt 4.8.6) Distro: siduction 13.2.1 December - kde - (201401272125)
Machine:   System: LENOVO product: 20B30064MH v: ThinkPad S5-S540 serial: MP04Y362
           Mobo: LENOVO model: 20B30064MH v: 0B98401 Pro serial: C1KS4162M0R
           Bios: LENOVO v: GPET50WW (1.50 ) date: 10/08/2013
CPU:       Dual core Intel Core i7-4500U (-HT-MCP-) cache: 4096 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 9580
           clock speeds: max: 3000 MHz 1: 2077 MHz 2: 2032 MHz 3: 1800 MHz 4: 2053 MHz
Graphics:  Card-1: Intel Haswell-ULT Integrated Graphics Controller bus-ID: 00:02.0
           Card-2: Advanced Micro Devices [AMD/ATI] Sun XT [Radeon HD 8670A/8670M/8690M] bus-ID: 06:00.0
           Display Server: X.org 1.16.1 drivers: ati,radeon,intel (unloaded: fbdev,vesa)
           tty size: 144x63 Advanced Data: N/A for root
Network:   Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: 4000 bus-ID: 03:00.0
           IF: eth0 state: down mac: 20:1a:06:c4:5b:c1
           Card-2: Intel Wireless 7260 driver: iwlwifi v: in-tree: bus-ID: 04:00.0
           IF: wlan0 state: up mac: 0c:8b:fd:65:c2:5f
Drives:    HDD Total Size: 256.1GB (14.0% used) ID-1: model: LITEONIT_LCS
Info:      Processes: 218 Uptime: 31 min Memory: 694.7/7642.4MB Init: systemd runlevel: 5 Gcc sys: 4.9.1
           Client: Shell (bash 4.3.301) inxi: 2.2.15
[code]


The output of /var/log/Xorg.0.log will exceed the maximum allowed length and I do not know how to post it.

Greetings,
Jörg

[absolut]

The output of /var/log/Xorg.0.log will exceed the maximum allowed length and I do not know how to post it.

you can use a pastebin... siduction provides a tool for that:

Code: [Select]

siduction-paste /var/log/Xorg.0.log
please give us the resulting URL

[Jörg]

Here is the wanted URL:
http://paste.siduction.org/20141029131234

[absolut]

the red line is present from the very beginning to the shutdown

is the red line present in bios ?
is the red line present before the bootstrap of the linux kernel ?
is it present when booting to tty (not X) ?

since two modules are loaded, intel and radeon, the question is, whether there might be some conflict (?)
can you turn off the dedicated radeon card?

[dibl]

I have tried a Live CD, but as you thought already: the red line is present from the very beginning to the shutdown.

This tells me the problem has nothing to do with the configuration or operation of your siduction OS.  It is a fault in the GPU which affects only the graphical mode.  Sorry.   

[Sir_Aim]

Even if it really seems to be a hardware problem - have you tried using fglrx for your amd card and disabled the Intel card in BIOS?

I have an AMD/ATI Radeon HD 6970 in my current System and I experiecend graphical errors always when using open source drivers. I had colored lines, blinking pixels or even a whole blinking pixel disco around windows. While, when running on fglrx everything works smooth without any problems...

Even if fglrx is not fully compatible (as it was a few month ago) and 3D rendering did not work the 2D fallback did a better job than the open source options.

Until now no live CD could handle my setup without graphical problems.

Code: [Select]

aim@i7:~/sshfs$ inxi -G
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Cayman XT [Radeon HD 6970]
           Display Server: X.Org 1.16.1 driver: fglrx
           Resolution: 1920x1200@59.95hz, 1920x1200@59.95hz, 1920x1200@59.95hz
           GLX Renderer: AMD Radeon HD 6900 Series GLX Version: 4.4.12968 - CPC 8.881

[Jörg]

Hello absolut,
the red line is present all the time: in the bios, before bootstrap and when booting to tty.
Could you find anything relevant in the Xorg.0.log?

Hello Sir_Aim,
which one(s) of the numerous fglrx-packages do I have to install?

After hours of thinking and searching the internet, I remembered an error-message with relation to radeon, i.e.:

Code: [Select]

jorg@thinkpad-s540:~$ su
Password:
[08:36:25] root@thinkpad-s540:/home/jorg# dmesg | grep radeon
[    2.217252] [drm] radeon kernel modesetting enabled.
[    4.736917] radeon 0000:06:00.0: VRAM: 2048M 0x0000000000000000 - 0x000000007FFFFFFF (2048M used)
[    4.736922] radeon 0000:06:00.0: GTT: 1024M 0x0000000080000000 - 0x00000000BFFFFFFF
[    4.737014] [drm] radeon: 2048M of VRAM memory ready
[    4.737016] [drm] radeon: 1024M of GTT memory ready.
[    4.737064] radeon 0000:06:00.0: firmware: failed to load radeon/hainan_pfp.bin (-2)
[    4.737119] radeon 0000:06:00.0: Direct firmware load for radeon/hainan_pfp.bin failed with error -2
[    4.737121] radeon 0000:06:00.0: Falling back to user helper
[    4.738039] radeon 0000:06:00.0: firmware: direct-loading firmware radeon/HAINAN_pfp.bin
[    4.738057] radeon 0000:06:00.0: firmware: failed to load radeon/hainan_me.bin (-2)
[    4.738106] radeon 0000:06:00.0: Direct firmware load for radeon/hainan_me.bin failed with error -2
[    4.738108] radeon 0000:06:00.0: Falling back to user helper
[    4.739082] radeon 0000:06:00.0: firmware: direct-loading firmware radeon/HAINAN_me.bin
[    4.739101] radeon 0000:06:00.0: firmware: failed to load radeon/hainan_ce.bin (-2)
[    4.739152] radeon 0000:06:00.0: Direct firmware load for radeon/hainan_ce.bin failed with error -2
[    4.739154] radeon 0000:06:00.0: Falling back to user helper
[    4.740242] radeon 0000:06:00.0: firmware: direct-loading firmware radeon/HAINAN_ce.bin
[    4.740261] radeon 0000:06:00.0: firmware: failed to load radeon/hainan_rlc.bin (-2)
[    4.740310] radeon 0000:06:00.0: Direct firmware load for radeon/hainan_rlc.bin failed with error -2
[    4.740313] radeon 0000:06:00.0: Falling back to user helper
[    4.741193] radeon 0000:06:00.0: firmware: direct-loading firmware radeon/HAINAN_rlc.bin
[    4.741210] radeon 0000:06:00.0: firmware: failed to load radeon/hainan_mc.bin (-2)
[    4.741262] radeon 0000:06:00.0: Direct firmware load for radeon/hainan_mc.bin failed with error -2
[    4.741264] radeon 0000:06:00.0: Falling back to user helper
[    4.743028] radeon 0000:06:00.0: firmware: direct-loading firmware radeon/HAINAN_mc2.bin
[    4.743033] [drm] radeon/HAINAN_mc2.bin: 31452 bytes
[    4.743049] radeon 0000:06:00.0: firmware: failed to load radeon/hainan_smc.bin (-2)
[    4.743103] radeon 0000:06:00.0: Direct firmware load for radeon/hainan_smc.bin failed with error -2
[    4.743105] radeon 0000:06:00.0: Falling back to user helper
[    4.744281] radeon 0000:06:00.0: firmware: direct-loading firmware radeon/HAINAN_smc.bin
[    4.757966] [drm] radeon: dpm initialized
[    4.759278] radeon 0000:06:00.0: WB enabled
[    4.759282] radeon 0000:06:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0xffff8800adc88c00
[    4.759285] radeon 0000:06:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0xffff8800adc88c04
[    4.759288] radeon 0000:06:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0xffff8800adc88c08
[    4.759291] radeon 0000:06:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0xffff8800adc88c0c
[    4.759294] radeon 0000:06:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0xffff8800adc88c10
[    4.759326] radeon 0000:06:00.0: irq 49 for MSI/MSI-X
[    4.759345] radeon 0000:06:00.0: radeon: using MSI.
[    4.759373] [drm] radeon: irq initialized.
[    5.020936] radeon 0000:06:00.0: No connectors reported connected with modes
[    5.023178] radeon 0000:06:00.0: fb1: radeondrmfb frame buffer device
[    5.024989] [drm] Initialized radeon 2.40.0 20080528 for 0000:06:00.0 on minor 1
[ 3173.016733] radeon 0000:06:00.0: WB enabled
[ 3173.016735] radeon 0000:06:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0xffff8800adc88c00
[ 3173.016737] radeon 0000:06:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0xffff8800adc88c04
[ 3173.016738] radeon 0000:06:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0xffff8800adc88c08
[ 3173.016740] radeon 0000:06:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0xffff8800adc88c0c
[ 3173.016741] radeon 0000:06:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0xffff8800adc88c10
[ 3505.882973] radeon 0000:06:00.0: WB enabled
[ 3505.882976] radeon 0000:06:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0xffff8800adc88c00
[ 3505.882979] radeon 0000:06:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0xffff8800adc88c04
[ 3505.882981] radeon 0000:06:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0xffff8800adc88c08
[ 3505.882983] radeon 0000:06:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0xffff8800adc88c0c
[ 3505.882985] radeon 0000:06:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0xffff8800adc88c10
[08:36:35] root@thinkpad-s540:/home/jorg#

Unfortunately I am not experienced enough to understand whether this have something to do with my "problem".

Greetings,
Jörg

[Sir_Aim]

Hi Jörg,
if the red line is present all the time I'm pretty sure that this is a hardware issue.

The problems I had with open source drivers appeared only in graphical enviroments.
BIOS and tty were not affected.

My installed fglrx packages are:

Code: [Select]

aim@i7:~$ dpkg --get-selections | grep fglrx                                                                                                                               
fglrx-atieventsd                                install                                                                                                                     
fglrx-control                                   install                                                                                                                     
fglrx-driver                                    install                                                                                                                     
fglrx-modules-dkms                              install                                                                                                                     
fglrx-source                                    install                                                                                                                     
glx-alternative-fglrx                           install                                                                                                                     
libfglrx:amd64                                  install                                                                                                                     
libfglrx:i386                                   install                                                                                                                     
libfglrx-amdxvba1:amd64                         install                                                                                                                     
libfglrx-amdxvba1:i386                          install
libgl1-fglrx-glx:amd64                          install
libgl1-fglrx-glx:i386                           install
libgl1-fglrx-glx-i386                           install

But I think installing fglrx-driver and fglrx-control will pull all required packages.

[OppaErich]

I guess broken RAM, bad solder joint(s) or it's running too hot. Bad solder joints could be fixed by baking the card...

Arrays of dots or vertical and horizontal lines are another common video RAM artifact. In the image above you can see a few areas of dots on the doors. Most examples have more dots than in this image. This kind of problem can appear both in 2D and 3D mode.

So what do you do if you think you have bad video RAM? Unfortunately, there's no well supported video RAM testing program that I'm aware of (there are a few old obscure ones that I don't trust) so it's not easy to test directly. One thing you should do is test your motherboard RAM. Video cards often store data in the motherboard RAM so sometimes it can cause artifacts which look like video RAM problems. It's easy to test your motherboard RAM so you should always do that before assuming that the video card's RAM is at fault. Overheating can definitely cause video RAM problems so you should try running your computer with the desk fan blowing on the video card as described above.

If you're overclocking your video card then the first thing you should do is back off on your overclock. Increasing your video RAM clock commonly causes artifacts. It can overheat your RAM enough to permanently damage it. The damage is cumulative and RAM seems especially vulnerable to it. I've seen plently of examples of people whose overclocks worked for a few months and then they started getting RAM artifacts. They discover that they have to reduce the RAM clock rate to make the artifacts go away. And then later they have to reduce their RAM clock more and more as their RAM deteriorates. They often end up running at clock rate far below stock to stop the artifacts. Overclocking is risky and increased heat accelerates the rate at which the RAM gets worse. Even if you're not overclocking then you can try underclocking your video RAM to see if the problem goes away. There are instructions on how to underclock on this page. If underclocking makes the artifacts go away then you know you have a hardware problem.

Unfortunately, there's not much you can do about bad video RAM. It's soldered to the video card and the video card manufacturers normally replace the whole card rather than try to rework individual chips. Sometimes you can make the symptoms go away by having an extra fan inside the computer blowing air past the video card. If it's an overheating problem then you can occasionally improve your situation by epoxying RAM heatsinks to the RAM chips but usually heatsinks don't help. Sometimes underclocking can help. But most of the time bad video RAM is permanently damaged and you just have to replace the video card.

http://www.playtool.com/pages/artifacts/artifacts.html

[Jörg]

The TFL-screen has been replaced (under guarantee) and my screen is perfect again. Thanks all for your support.

Greetings,
Jörg