They also changed screen coating - possibly because of the mentioned
crystall effect many sensitive people complain on. When selectiong a
new monitor, me also got affraid of these (as revealed today - vaste
ones) complains.
--
On 23/09/13 11:11, Ivanko B wrote:
> Oops,sure - me did a mistake. Cheaper U2713HM (edge W-LED, 16mln
> color) & pro U2713H (matrix BG-LED, high-contrast, 1bln color)
I just went on the Dell website, and it seems the U2711 has been
replaced by the U2713H model. I haven't looked in more detail t
I have never heard of the "crystal effect" before. No idea what it is, sorry.
==
That mean the effect was really exaggerated.
DELL U2317H(M)
==
Oops,sure - me did a mistake. Cheaper U2713HM (edge W-LED, 16mln
color) & pro U2713H (matrix BG-LED, high-contrast, 1bln color)
On 23/09/13 10:06, Ivanko B wrote:
> Me was affaraid this (and some ohers) model because of huge crystall
> effect shown by
I have never heard of the "crystal effect" before. No idea what it is,
sorry.
> But it seems that this effect was highly exaggerated as to real
> feeling, correct ?
All I
I couldn't find many, but glad I spotted and choose the U2711. Another
well know monitory is the 27" Apple Display - but at a crazy high
price.
===
Me was affaraid this (and some ohers) model because of huge crystall
effect shown by
"www.overclockers.ru/images/lab/2013/08/06/1/98_kristaleff
I forgot to say XAA was dropped in newer xorg versions, still working in
Ubuntu 12.04 LTS and Debian 7.
For new xorg versions, disabling EXAPixmaps or disabling acceleration is
the only way for the moment.
--
Julio Jiménez Borreguero
On Saturday 21 September 2013 10:49:54 Julio Jiménez wrote:
> What I did in the mean time.
>
> For ATI cards.
>
> Added file /etc/modprobe.d/radeon-kms.conf
> content: options radeon modeset=0
>
> Added to xorg.conf (or your xorg config file...) Device section:
>
> Option "AccelMethod" "XAA"
but glad I spotted and choose the U2711
==
A good monitor :). Also features the quite rare (for 27'') CCFL (no
LED PWM issues to eyes) backlight.
--
LIMITED TIME SALE - Full Year of Microsoft Traini
On Saturday 21/09/2013 at 14:34, Ivanko B wrote:
Me also had to swicth to 27 inches monitor (combo with analog+digital
TV) "LG 27MA53D-PZ" IPS) - 1920x1080 for highly expected large 0.31mm
I was specifically looking for the higher resolution 27" displays. I
couldn't find many, but glad I
Correct, I switched from a dual 19" LCD setup to a single 27" LCD setup.
I am currently using the 27" DELL U2711 IPS display, which is absolutely
brilliant.
==
Me also had to swicth to 27 inches monitor (combo with analog+digital
TV) "LG 27MA53D-PZ" IPS) - 1920x1080 for highly expec
2013/9/21 Graeme Geldenhuys
> On 2013-09-21 09:18, Julio Jiménez wrote:
> > As I
> > said it was probably because no xorg.con supplied and this will be fixes
> > setting the proper modeline in xorg.conf.
>
> I don't specify manual modeline's in my xorg.conf - I simply specify the
> monitro displa
On 2013-09-21 09:18, Julio Jiménez wrote:
> As I
> said it was probably because no xorg.con supplied and this will be fixes
> setting the proper modeline in xorg.conf.
I don't specify manual modeline's in my xorg.conf - I simply specify the
monitro display size, and the resolution I'm interested
Hello Ivanko,
On 2013-09-20 23:05, Ivanko B wrote:
> Graeme, it seem that You had to switch to a large LED backlight monitor (27
> inches me guess). How did You tune its backlight & brightness level so that
> your eyes feel comfortable ?
Correct, I switched from a dual 19" LCD setup to a single 2
Am 21.09.2013 09:49, schrieb Julio Jiménez:
> What I did in the mean time.
>
> For ATI cards.
>
> Added file /etc/modprobe.d/radeon-kms.conf
> content: options radeon modeset=0
>
> Added to xorg.conf (or your xorg config file...) Device section:
>
> Option "AccelMethod" "XAA"
>
> in this way, I h
What I did in the mean time.
For ATI cards.
Added file /etc/modprobe.d/radeon-kms.conf
content: options radeon modeset=0
Added to xorg.conf (or your xorg config file...) Device section:
Option "AccelMethod" "XAA"
in this way, I have MSEide working fine and have hardware acceleration. 3D
Hi
The true problem is the artifacts when using EXA acceleration. I'm not
going to use VESA son I didn't want to waste time investigating why it
detected and dropped the true monitor resolution and fall to 1024x768. As I
said it was probably because no xorg.con supplied and this will be fixes
sett
Julio's machine doesn't provide full resolution when using the VESA driver
=
To get all supported resolutions, there's UVESA driver (kernel module +
v86d userspace tuner) instead. Its drawback is unable to have booting
penguins (earliest stage graphic console) :)
2013/9/21 Ivanko B
VESA, UVESA & KMS (DRM based) Nouveau/Radeon disallow any h/w accelarating
but simpliest area copying in rare cases. With modern hardware, they can be
considered as deep fallbacks.
Graeme, it seem that You had to switch to a large LED backlight monitor (27
inches me guess). How did You tune its ba
Hallo Graeme,
Du schriebst am Fri, 20 Sep 2013 13:57:45 +0100:
> > If Julio runs Linux, which he probabely does, it is quite possible that
> > the VESA driver doesn't support all the built-in firmware
...
> Nope, I installed X11 via FreeBSD's ports system (from source code). The
...
> driver I'm
On 2013-09-19 21:43, Sieghard wrote:
> This might be the reason, there _are_ differences between the systems.
> If Julio runs Linux, which he probabely does, it is quite possible that the
> VESA driver doesn't support all the built-in firmware functionality, as it
> is mainly provided as a fallback
Hallo Graeme,
Du schriebst am Wed, 18 Sep 2013 23:32:20 +0100:
> > No way to disable EXA.. change modeset makes use of VESA driver and max
> > resolution is 1024x768.. of course MSE runs fine with VESA
>
> Not sure if I understood you statement correctly. I run the X11 VESA
> driver here, under
I got it working fine using nouveau driver too.. just had to disable thee
hw acceleration.
I added to xorg.conf
Section "Device"
Identifier "Nouveau"
Driver "nouveau"
Option "NoAccel" "on"
EndSection
Like for EXAPixmaps "off" there is a performance penalization, but this is
better t
2013/9/19 Martin Schreiber
>
> >
> > may be a issue related to ati and radeon open source drivers.
>
I meant nouveau*(nvidia) and radeon :)
--
Julio Jiménez Borreguero
--
LIMITED TIME SALE - Full Year of Microsoft Tr
On Thursday 19 September 2013 11:49:15 Julio Jiménez wrote:
> 2013/9/19 Martin Schreiber
>
> > I saw artefacts without fades too. For example in objectinspector there
> > can be
> > not painted white or garbage areas. With fades the problems are more
> > visible
> > it seeems.
>
> Yes, that's why
2013/9/19 Martin Schreiber
>
> I saw artefacts without fades too. For example in objectinspector there
> can be
> not painted white or garbage areas. With fades the problems are more
> visible
> it seeems.
>
>
Yes, that's why I asked if you were using fades in tfilenameedit
components... (mse con
On Wednesday 18 September 2013 20:37:24 Julio Jiménez wrote:
> There are lots of reports about EXA issues. I can fill a bug report, but
> probably you are more indicated to do it. You know how MSE interact with
> xrender in deep ;)
>
> About NOUVEAU xorg driver... I'm unable to make it working prop
On Thursday 19 September 2013 10:43:24 Julio Jiménez wrote:
> 2013/9/19 Martin Schreiber
>
> > I think something goes wrong with clipping mask plane. IIRC widget
> > refreshing
> > does not help. What happens if you build with -dmse_flushgdi? It then
> > doesn't
> > use an intermediate pixmap for
2013/9/19 Martin Schreiber
>
> I think something goes wrong with clipping mask plane. IIRC widget
> refreshing
> does not help. What happens if you build with -dmse_flushgdi? It then
> doesn't
> use an intermediate pixmap for flicker free drawing.
>
>
Compiling with -dmse_flushgdi is working fine
On Thursday 19 September 2013 09:48:36 Julio Jiménez wrote:
> I have observed that if you switch from one working area to another, when
> you return all is rendered fine, It looks something related to
> refresh/invalidate. I haven't tested if invalidating the widget may help...
>
I think something
I have observed that if you switch from one working area to another, when
you return all is rendered fine, It looks something related to
refresh/invalidate. I haven't tested if invalidating the widget may help...
Regards
2013/9/19 Martin Schreiber
> On Wednesday 18 September 2013 21:42:12 Juli
By default (with no xorg.conf) logs said was unable to set other screen
resolutions. Probably I had to set the modeline in xorg.conf to enable
other resolutions. I didn't investigate it.. was only trying to set
nouveau driver working with MSEide.
Regards.
2013/9/19 Graeme Geldenhuys
> On 201
On Wednesday 18 September 2013 21:42:12 Julio Jiménez wrote:
> 2013/9/18 Martin Schreiber
>
> > I tried to find workarounds for Radeon in MSEgui, no success.
>
> What about not using xrender stretched bitmaps and make all required the
> images in fpc? but probably too much work and poor performan
On 2013-09-18 19:44, Julio Jiménez wrote:
> No way to disable EXA.. change modeset makes use of VESA driver and max
> resolution is 1024x768.. of course MSE runs fine with VESA
>
Not sure if I understood you statement correctly. I run the X11 VESA
driver here, under FreeBSD 9.1 and my resolution
Hi all!
After several years, it seems that the problem still persists. My
observations:
ATI AMD proprietary fglrx graphics driver: all is fine.
NVIDIA propietary graphics driver: all is fine
Radeon xorg driver: using EXA is fine if you disable EXAPixmaps. If you do
not use EXA is ok too.(Of cour
2013/9/18 Martin Schreiber
>
> I tried to find workarounds for Radeon in MSEgui, no success.
>
What about not using xrender stretched bitmaps and make all required the
images in fpc? but probably too much work and poor performance
--
Julio Jiménez Borreguero
--
I was thinking in nouveau driver :)
2013/9/18 Ivanko B
> but some drivers are unable to work without KMS
> =
> These may only be framebuffer-based ones ( "fbdev.drv" accomp by
> "UseFBDev=true").
>
>
--
Julio Jiménez Borreguero
--
2013/9/18 Ivanko B
> I think is the combination of drivers and KMS enabled.
> ==
> KMS=framebuffer VGA, correct ? Then there're possible problems with
>
http://nouveau.freedesktop.org/wiki/KernelModeSetting/
> MTRR sharing & their modes (write-through, write-combining,..).
but some drivers are unable to work without KMS
=
These may only be framebuffer-based ones ( "fbdev.drv" accomp by
"UseFBDev=true").
--
LIMITED TIME SALE - Full Year of Microsoft Training For Just $
I think is the combination of drivers and KMS enabled.
==
KMS=framebuffer VGA, correct ? Then there're possible problems with
MTRR sharing & their modes (write-through, write-combining,..).
--
LIMITED T
2013/9/18 Martin Schreiber
>
> Somebody should make bug reports at freedesktop.org.
> I tried to find workarounds for Radeon in MSEgui, no success.
>
>
Done (from your bug report at OpenSuse list...) ;)
https://bugs.freedesktop.org/show_bug.cgi?id=69543
--
Julio Jiménez Borreguero
--
2013/9/18 Ivanko B
> NOUVEAU
> ==
> Youd be a lucky LUNUXer if have these working :
> 1) any ATI HD+ drivers (me've even stopped downloading & trying these)
>
ATI open source drivers (radeon) working fine:
- Use radeon.modeset=0 (this makes radeon using another hw acce
On Wednesday 18 September 2013 18:16:58 Julio Jiménez wrote:
>
> I wonder why other toolkits like Gtk2, Cairo, Qt don't show this problem.
> Perhaps they use their own implementation for stretched bitmaps.. dunno.
>
Because the X11 driver devels test there work with the mainstream toolkits.
> I wo
NOUVEAU
==
Youd be a lucky LUNUXer if have these working :
1) any ATI HD+ drivers (me've even stopped downloading & trying these)
2) NOUVEAU powered NVidia.
It's definitely a driver's issue.
--
LIM
There are lots of reports about EXA issues. I can fill a bug report, but
probably you are more indicated to do it. You know how MSE interact with
xrender in deep ;)
About NOUVEAU xorg driver... I'm unable to make it working properly.
Not using skins is a temporal solution, but still getting issue
I forgot to say that INTEL graphics are ok too.
2013/9/18 Julio Jiménez
> Hi all!
>
> After several years, it seems that the problem still persists. My
> observations:
>
> ATI AMD proprietary fglrx graphics driver: all is fine.
> NVIDIA propietary graphics driver: all is fine
> Radeon xorg driv
45 matches
Mail list logo
