- This topic has 19 replies, 7 voices, and was last updated 4 years ago by
.
-
Posts
-
Hi.
We have a lot of Wyse 5010 with dual monitor setup running fine. This model are now replaced by Wyse 3040 with two monitors connected with displayport cables.
We have got some feedback from 3040 users that one of the monitors suddenly disappears. Then they have to reboot the client to get two monitors again.
It is not specific monitor models or dp cables.
I was connected to one of the clients when the problem came and it seems that the client are messing up screen 1 and 2 and which port has a specific serial# connected
11:07:47.509 Screen1: [Oxe22, 0x345f] HP E233 Week(5) Year(2018) S/N:3CQ805154F
11:07:51.660 Screen1: [0xe22, 0x345f] HP E233 Week(15) Year(2018) S/N:3CQ8152D6D
11:07:51.660 Screen2: [0xe22, 0x345f] HP E233 Week(5) Year(2018) S/N:3CQ805154F
11:08:13.630 Screen1: [0xe22, 0x345f] HP E233 Week(5) Year(2018) S/N:3CQ805154F
11:08:22.894 Screen1: [Oxe22, 0x345f] HP E233 Week(15) Year(2018) S/N:3CQ8152D6D
11:08:22.894 Screen2: [0xe22, 0x345f] HP E233 Week(S) Year(2018) S/N:3CQ805154F
11:11:27.940 Screenl: [0xe22, 0x345f] HP E233 Week(5) Year(2018) S/N:3CQ805154F
11:12:45.958 Screenl: [0xe22, 0x345f] HP E233 Week(15) Year(2018) S/N:302815206D
11:12:45.958 Screen2: [0xe22, 0x345f] HP E233 Week(S) Year(2018) S/N:3CQ805154F
11:13:05.795 Screenl: [0xe22, 0x345f] HP E233 Week(5) Year(2018) S/N:3CQ805154FRunning ThinOS 8.5_017 Bios 1.2.4
Anyone else with this strange behavior?
/ Torsten
Yes,
if you are using a direct cable i.e. DP to DVI or DP to HDMI etc they ‘play up’.
You need to either use a DP-DP or if you need to connect to a VGA or DVI input you have to use an Active adaptor, we found this when deploying 2000+ of these devices.
https://www.startech.com/uk/m/AV/Displayport-Converters/Active-DisplayPort-to-DVI-Adapter~DP2DVIS
As an example.
Basically, if changing the monitor side to anything but a direct DP-DP you must use an active adaptor not a passive straight through converter cable.
Hi.
Thanks for your reply.
We just checked at this specific client and it was connected with a dp-dp cable.
Does it have to be double shielded or something?
Standard DP-DP should be fine, only had issues when using DP > VGA/DVI/HDMI when not using Active adaptors.
Whats your ini setup?
As said, we have approx. 2000 all dual screen devices using a whole variety of brands (Samsung/Acer/Dell/HP) All fine.. my ini reads:
;*************************************************************
;* Display *
;*************************************************************Desktop=BackgroundDefault.jpg Layout=Stretch
Dualhead=yes ManualOverride=yes Mainscreen=1 Orientation=hort MonitorAutoDetect=yes
Screensaver=15 LockTerminal=yes Type=2 Image=background.gifMy ini is just:
;*************************************************************
;* Display *
;************************************
Dualhead=yes MonitorAutoDetect=yesOk, well ignoring our background setting etc…
try updating yours to:
Dualhead=yes ManualOverride=yes Mainscreen=1 Orientation=hort MonitorAutoDetect=yes
As said, works for us no issue….
We are seeing this behavior at one of our clinics. Brand new 3040s and P2419H monitors and I contacted my Dell reps and they said that it was an issue at another location in the midwest. I was given an early release ThinOS and bios to test last week. You may want to contact your Dell representative and hopefully they can help.
Hi
I contacted Dell and got a beta ThinOS 8.5.019.56 which I have tried on some devices. At the moment it seems not to resolve the issue. I have got feedback from one of the affected users that it threw the monitor minutes after the ThinOS update.
You also got a bios update from them? Mine is 1.2.4
@dougblack3684 I also updated the monitor ini-settings on the same devices, and it did not solve itI did get a bios update on Thursday from Dell because I had reports that it did continue to happen again. They gave me bios version 1.2.5. Hopefully it fixes the problem. I’m sure if it does happen I will find out from the users today so I will update this post with what I find out.
I also have got 1.2.5 today and deployed it to a couple of devices.
Really hope this will solve it, but nothing mentioned in the release note, so I do not have high expectations.
Well the bios update didn’t help, per my end users. I am going to contact Dell and see what they would like me to try next. How did your test go?
Same here.
They have asked me to do a trace on one of the affected devices.
Unfortunately the devices are located in UK and I am in Denmark. But we have enabled trace to USB and waiting for monitor to drop again.
What kind and model of monitors are your problem thin clients using? I am using DELL P2419H.
We are using a different kind of models – mainly Lenovo. We have the same issue regardless if it is HP og Lenovo monitors.
I got a beta release 8.5_021.96 and tested that on one 3040. We have not seen the issues after the update on that device.
This is reported back to support and I am waiting for next step.
- You must be logged in to reply to this topic.