*** This bug is a duplicate of bug 27667 ***
https://bugs.launchpad.net/bugs/27667
** This bug has been marked a duplicate of bug 27667
Problems with xresprobe & Samsung 243T LCD
--
[Feisty] Wide screen not correctly detected (16/10)
https://bugs.launchpad.net/bugs/67369
You received this
*** This bug is a duplicate of bug 27667 ***
https://bugs.launchpad.net/bugs/27667
Hi all,
The confirmers in this bug report are all seeing a variety of different
bugs. Let me break things out:
1. Stéphane Graber and several others, I believe you may be seeing bug
27667. 27667 shows up fo
For Gutsy, I've tested and verified the use of the new Screens and
Graphics admin tool for widescreen setting. Indeed, this configuration
was my primary test case for the tool. So I know that provides an
adequate way of dealing with this bug.
However, I'm leaving this bug open because the ultima
Bug is still present in Gutsy tribe 5.
--
[Feisty] Wide screen not correctly detected (16/10)
https://bugs.launchpad.net/bugs/67369
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubun
I am also encountering this bug.
--
[Feisty] Wide screen not correctly detected (16/10)
https://bugs.launchpad.net/bugs/67369
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
The same problem for me using:
00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated
Graphics Controller (rev 02)
00:02.1 Display controller: Intel Corporation 82945G/GZ Integrated Graphics
Controller (rev 02)
And using an "Acer AL1916W" (19" 1440x900 Widescreen)
:wq!
--
Same here, Nvidia 6600, HANNS-G HW191D 19" Widescreen
--
[Feisty] Wide screen not correctly detected (16/10)
https://bugs.launchpad.net/bugs/67369
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
The program will disappear after we have a high degree of confidence
that xorg's detection is able to detect all scenarios that xresprobe can
detect. I.e., we may want to hang onto xresprobe as a fallback.
However, I'm planning to discuss strategies for relying less on
xresprobe at the distro spr
xrespose is still being used in gusty Tribe-2 . When is this program
going to disappear ? It appears Xorg (and randr) are doing a much better
job at detecting then xrespose is.
--
[Feisty] Wide screen not correctly detected (16/10)
https://bugs.launchpad.net/bugs/67369
You received this bug notif
I can confirm that the workaround of deleting xorg.conf works. I was
able to swith from 1024*768 to the proper 1920*1200 with a HP LP2465.
--
[Feisty] Wide screen not correctly detected (16/10)
https://bugs.launchpad.net/bugs/67369
You received this bug notification because you are a member of Ub
Will be fixed with Gutsy and the Xorg auto-detection (it works with my Acer
1440x900 monitor and all the others I tried with)
It's not the current default behaviour (as of Tribe-1), if you want to test it,
simply remove your /etc/X11/xorg.conf (or move it somewhere else), then restart
X.
I keep
I have resolved this issue on a Dell D620 with a 1440x900 display with a
GForce 7 Series graphics card in kubuntu / feisty
aptitude install nvidia-glx-new
restarted X-Server
with the d620 the 16x9 display is not properly detected. under system
settings / monitor + display / administrator mode /
I can confirm this, Acer 1916W, and im on the livecd. Feisty x86.
--
[Feisty] Wide screen not correctly detected (16/10)
https://bugs.launchpad.net/bugs/67369
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
I have always had problems with widescreen detection on my Acer laptop
since I first installed Ubuntu on it (I think it was Hoary at the time.)
I believe it is a problem with the Intel video chipset, I've had to use
the 855resolution program to set the correct mode. I can get exact
hardware details
Bumping up priority
** Changed in: xorg (Ubuntu)
Importance: Medium => High
--
[Feisty] Wide screen not correctly detected (16/10)
https://bugs.launchpad.net/bugs/67369
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu
Confirmed on Fiesty Beta (Acer AL1916W, resolution got set to 1400x1050
instead of 1440x900)
--
[Feisty] Wide screen not correctly detected (16/10)
https://bugs.launchpad.net/bugs/67369
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu
I got a Samsung SyncMaster 940bw (1440x900) with the same problems and
more
The resolution problem was not that big of a problem for me.
I created a modeline with this command: gtf 1440 900 60 -x
I looked for the correct monitor freq range with this command: sudo ddcprobe
some extra command for i
** Attachment added: "Xubuntu Feisty Herd 5 Test Report Version 1.0"
http://librarian.launchpad.net/6967518/Xubuntu%20Feisty%20Herd%205%20Test%20Report%20Version%201.0.txt
--
[Feisty] Wide screen not correctly detected (16/10)
https://launchpad.net/bugs/67369
--
ubuntu-bugs mailing list
ub
This is a problem that looks like it really is not going to be solved in
Feisty. Though there is an effort to resolve it POST Feisty:
https://wiki.ubuntu.com/SimpleXModeSelection
My Samsung 243T has an issue as well, but it mainly has to do with xrespose. I
have a bug here about it:
https://lau
I found a workaround to this problem. I didn't have the time to dig out exactly
how to solve this but this should do the trick.
Looks like Xorg, unlike the XFree, by default don't trust modes that can't be
confirmed by probing the hardware so, if you use this:
Option "ModeValidation" "NoDFPNative
Same problem using a LG L203WT. The default resolution is 1680x1050 but it goes
down to 1280x1024.
Xorg log says:
(WW) NVIDIA(0): No valid modes for "1680x1050"; removing.
(WW) NVIDIA(0): No valid modes for "1440x900"; removing.
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0): "1280x1024"
(II)
** Attachment added: "Results of ddcprobe on my desktop computer"
http://librarian.launchpad.net/6601640/ddcprobe
--
[Feisty] Wide screen not correctly detected (16/10)
https://launchpad.net/bugs/67369
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman
** Attachment added: "And from my laptop (no detection problem with it, just in
case it helps to have a working widescreen result)"
http://librarian.launchpad.net/6601651/ddcprobe
--
[Feisty] Wide screen not correctly detected (16/10)
https://launchpad.net/bugs/67369
--
ubuntu-bugs mailing
$ sudo ddcprobe
vbe: VESA 3.0 detected.
oem: NVIDIA
vendor: NVIDIA Corporation
product: G72 Board - travis1 Chip Rev
memory: 65536kb
mode: 640x400x256
mode: 640x480x256
mode: 800x600x16
mode: 800x600x256
mode: 1024x768x16
mode: 1024x768x256
mode: 320x200x64k
mode: 320x200x16m
mode: 640x480x64k
mode
The script "xresprobe" may possibly be at falut here. What does the
command "ddcprobe" output. Also what does the command "xresprobe"
output?
If you don't have it just install xresprobe via apt, or just run it as
root from the live cd.
--
[Feisty] Wide screen not correctly detected (16/10)
htt
Also happens on a Dell Latitude D620 on Feisty Herd4.
lspci|grep -i nvidia
01:00.0 VGA compatible controller: nVidia Corporation Quadro NVS 110M / GeForce
Go 7300 (rev a1)
Manually adding 1440x900 to xorg.conf resolves the problem.
--
[Feisty] Wide screen not correctly detected (16/10)
https:/
26 matches
Mail list logo
