My display problem have been solved now by connecting monitor by HDMI
cable and DisplayPort/HDMI converter to HDMI-2 port.
This with kernel
Linux ci547 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2 (2019-08-28) x86_64
GNU/Linux
Using HDMI cable on DP-1 port make drm issue "Link Training Unsuccessful"
mes
Update...
ZOTAC ZI547 have 2 output ports, 1 DisplayPort and 1 HDMI.
My monitor only have HDMI and VGA input.
xrandr see HDMI as DP-1.
Until now I have connected by this using HDMI cable, experiencing problems
with max display, and drm giving "Link Training Unsuccessful".
xrandr see DisplayPort
start fine in 1920x1080.
I will now monitor and see if this is stable.
Looks like first boot, when monitor is cold, still go for 1024x768.
/Torben
--
Torben Schou Jensen
Swamp Thing
Homepage: http://swampthing.dk/~tsj/
Skype: swampthing38
This error still exist in latest Debian Stable kernel
Linux ci547 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2 (2019-08-28) x86_64
GNU/Linux
After upgrade to Debian Stable 10 (Buster) this is still a problem.
Kernel 4.9.0-9 handle 1920x1080 without problems.
Kernel 4.19.0-5 handle max 1024x768.
Same hardware, ZOTAC CI547, with Intel HD Graphics 620 using driver i915.
In log I see
[drm:intel_dp_get_link_train_fallback_values [i915]] *
inxi -Gx
Graphics: Card: Intel HD Graphics 620 bus-ID: 00:02.0
Display Server: X.Org 1.19.6
drivers: modesetting (unloaded: fbdev,vesa)
Resolution: 1024x768@60.00hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 620 (Kaby Lake GT2)
version: 4.5
xrandr
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
DP-1 connected primary 1024x768+0+0 (normal left inverted right x axis y
axis) 598mm x 336mm
1024x768 60.00*
800x600 75.0060.32
720x576 50.00
720x480 60.0059.94
640x480 7
Package: src:linux
Version: 4.14.17-1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Upgrading from Stable to Testing, display drop from 1920x1080 to 1024x768.
* What exactly did you do
Ok, so x86_64_BUG_CPU_INSECURE will be optional in kernel config.
As I read Meltdown is primary a security risk on server farms where
multiple customers use same CPU.
If I have my own private server on own hardware, and thereby have full
control over software in use, then I might get a performanc
1080.
On kernel 4.7 monitor start fine on HDMI cable, but not on kernel 4.8 and up.
Brgds
Torben Schou Jensen
Hi
After applying latest updates to Debian testing, my system here will not
boot to graphical mode on kernel 4.8.0-1-686-pae and 4.8.0-2-686-pae.
During boot it drop connection to monitor, and not even a command prompt
is available.
Same setup work fine with kernel 4.7.0-1-686-pae.
lspci show
01:
Trace messages, but XL still unuseable
until reboot.
Brgds
Torben Schou Jensen
> On Sat, 2016-01-02 at 18:55 +0100, Torben Schou Jensen wrote:
>> > Since upgrade to linux-image-4.3.0-1-686-pae I experience unstable
>> system
>> > after 60 minutes.
>> > I am using XFCE desktop and primary Iceweasel.
>> > After about 60 minu
ssible to identify what is causing oom-killer.
>
> Brgds
> Torben Schou Jensen
>
Wifi has something to do with this.
With linux-image-4.3.0-1-686-pae I see a few error messages from
wpa_supplicant, always within a minute before oom-killer start.
I have now removed my USB Wifi, comput
.
If I boot up in linux-image-4.2.0-1-686-pae, all is stable again.
linux-image-4.2.0-1-686-pae 4.2.6-3 i386
linux-image-4.3.0-1-686-pae 4.3.3-2 i386
I have tried to setup atop to log memory every 10 seconds, but until now
not possible to identify what is causing oom-killer.
Brgds
Torben Schou
15 matches
Mail list logo
