On 09/01/14 01:35, Christopher M. Penalver wrote:
Brian Burch, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images
Lucid was updated to xorg 2:1.7.6-2ubuntu7.3 recently and I found a
significant improvement over the previous version. However, that only
means lucid is now as bad as karmic was on the SVGA interface, so don't
get too pleased! (Presumably a regression bug was fixed.) (Also, the
behaviour of the
OK. I've now found out this topic is a hornets nest - anyone who is
interested should take a look at
http://bugs.freedesktop.org/show_bug.cgi?id=23705
I can't override the DPI in xorg.conf because it is ignored. I tried
xrandr --dpi, but it didn't make any difference on the VGA system when I
Works fine when lucid upgraded from karmic, and also with a clean
install of lucid. As far as I am concerned, this problem has gone
away
--
UK keyboard layout has gone wrong
https://bugs.launchpad.net/bugs/492874
You received this bug notification because you are a member of Ubuntu-X,
which
Something really strange is going on...
My SVGA Xlog shows: Display dimensions (510, 290) mm and DPI set to
(101,100). The Dell specification says the display area is (509.95,
286.84) mm (confirmed by ruler to be more-or-less right). The Dell spec
also gives the pixel pitch as 0.249 mm, which
I got hold of a DVI-D cable and tried it with nouveau, KMS enabled and
NO xorg.conf (i.e. using the EDID). The screen came up perfectly at
2048x1...@60.
I need to compare the drm kernel xorg log messages for the two best
cases (VGA and DVI) to see whether I can find a significant difference.
--
I really don't think this problem is related to the nouveau driver,
because I get the same symptoms using the binary nVidia drivers. I have
also connected the monitor to a system running Hardy LTS on the VIA
chipset (X.Org X Server 1.4.0.90 and CHROME driver). The EDID data looks
the same and is
I went back to karmic to run gtf and cvt - they produced slightly
different modelines, but I was more concerned about them selecting
197.97 mHz as the pixel clock rate when the Dell specification and the
EDID modeline says 156.75. I ran cvt --reduced 2048 1152 60 and was
astonished to see that it
This is very frustrating because my changes have not been reproducible
because the monitor is too clever for its own good - it auto-adjusts
the image and apparently remembers the optimal alignment for that
particular resolution.
I've discovered (the hard way) that I can only be sure my test
Thanks for your advice, Chris. I've been messing around with modelines,
etc, whenever I've found a spare hour. I'm fairly sure the answer lies
with the vertical frequency, but I'm new to this stuff and am on a steep
learning curve.
I've been concentrating on the Dell optimal mode, which is also
Got some black screens, but now I realise this happens whenever I run
Xorg -config -retro and then Ctl/C. I MUST reboot after I get this
message NOUVEAU(0): failed to destroy server context - if I try an
different mode I lose the entire display, including the text-mode
console session. I guess
Well, that is a surprise! I thought this would be the best mode line because it
had the same synch polarity as the specification:
Modeline 2048x1152_60.00_h_plus 197.97 2048 2184 2408 2768 1152 1153 1156
1192 +HSync -Vsync
... but the vertical alignment is wrong - I lose at least one pixel
I've been messing around with lots of different programs to calculate
the best modeline, but all of them seem to wrong in some way. (Perhaps
the authors never tested resolutions and scan frequencies in the range
of this particular monitor?)
I found an obsolete web page that seems to tell me
Public bug reported:
Binary package hint: xorg
This monitor has a preferred resolution of 2048x1152 @ 60Hz. The desktop
does not fill the display and leaves a 2 cm black strip on the left
margin. The monitor manual adjustments do not permit the image to be
moved or expanded to fill the screen.
** Attachment added: get-edid binary from lucid beta
http://launchpadlibrarian.net/44259049/get-edid
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/44256685/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/44256686/CurrentDmesg.txt
**
** Attachment added: ddcprobe from lucid beta
http://launchpadlibrarian.net/44259377/ddcprobe
--
Invalid EDID for Dell SP2309W in VGA mode
https://bugs.launchpad.net/bugs/563774
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
** Attachment added: xrandr from lucid beta
http://launchpadlibrarian.net/44259480/xrandr
--
Invalid EDID for Dell SP2309W in VGA mode
https://bugs.launchpad.net/bugs/563774
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
Please note that lucid beta is running from an unmodified CD downloaded
as ubuntu-10.04-beta2-desktop-i386.iso. That means the /etc/X11/
directory does NOT contain an xorg.conf file.
According to the X.Org web site, X Server 1.7.6 is the up-coming next
stable release.
** Attachment added:
I found several reports of this monitor not working properly on its hdmi
interface (particularly the mythbuntu faq), and tried all the work-
arounds proposed, but none of them seemed to make an improvement (some
were disastrous!). My screen is attached via the vga interface: I am not
sure whether
lucid beta uses KMS (kernel mode setting) and this is reported in the
log. my karmic system is still using xorg for configuration. I think
this means the problem is attributable to the monitor's EDID data,
rather than the nvidia driver or the dynamic configuration logic.
p.s. I do not have a
I forgot to mention that I tested under lucid with-and-without the kvm
switch. There was no visible difference in the screen images, but the
files I have attached to this bug report were collected WITHOUT the kvm
switch. I conclude the switch is not contributing to the problem.
--
Invalid EDID
I have the same problem... the system works fine when I boot hardy or
jaunty, but not with a clean install of karmic. I tried bill's
circumvention, but it hasn't made any difference for me. Incidentally,
whatever I change I still get the wrong keyboard mapping in the try it
box of the keyboard
22 matches
Mail list logo