** Tags added: iso-testing
--
Xorg resolution falling back to 640x480 and/or 800x600 when h/v freqs incorrect
https://bugs.launchpad.net/bugs/3731
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
Sorry to bring this up again, but I've just upgraded to Intrepid and
it's doing it again.
I have a Quadro FX 500/600 nVidia card
The driver that fixes this bug was released on 7th Oct 2008 (version
177). This, however is not available from the repos yet.
This is the changelog for version 177
I think we can now close this bug as fixed as of the Gutsy release.
While some resolution detection issues remain, they are uncommon and
typically unrelated to the original bug report, and of course should be
entered as their own bug reports.
For the 42 duplicates to this bug, I'm going to also
I encounter the same bug with a fresh install of Kubuntu Hardy Alpha 3.
I have a Fujitsu laptop with i945GMA video and a 1280x800 LCD panel.
kdm appears with very big fonts, so I guess it uses a 640x480
resolution.
Attached is my Xorg.log
NB: the JHardy Alpha 3 LiveCd guessed the correct
Don't guess, instead attach the output of 'xranrd'. Fonts being big
could be an issue with KDE at the moment.
--
Xorg resolution falling back to 640x480 and/or 800x600 when h/v freqs incorrect
https://bugs.launchpad.net/bugs/3731
You received this bug notification because you are a member of
uh, make that 'xrandr'..
--
Xorg resolution falling back to 640x480 and/or 800x600 when h/v freqs incorrect
https://bugs.launchpad.net/bugs/3731
You received this bug notification because you are a member of Kubuntu
Team, which is a subscriber of a duplicate bug.
--
kubuntu-bugs mailing list
I'm sorry. I think the resolution is correct. Only the fonts are very big when
kdm launches.
Here is the result of xrandr:
Screen 0: minimum 320 x 200, current 1280 x 800, maximum 1280 x 1280
VGA disconnected (normal left inverted right x axis y axis)
LVDS connected 1280x800+0+0 (normal left
Thanks very much Bryce
Here is the correct info
parse-edid: parse-edid version 1.4.1
get-edid: get-edid version 1.4.1
Performing real mode VBE call
Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
Function supported
Call successful
VBE version 300
VBE
blokeinlondon, the output of get-edid is binary data (thus the weird
characters). You should run it like this:
get-edid | parse-edid
--
Xorg resolution falling back to 640x480 and/or 800x600 when h/v freqs incorrect
https://bugs.launchpad.net/bugs/3731
You received this bug notification
On my computer the get-edid command causes serious corruption see the
strange characters at the end of this comment maybe this helps.
sudo get-edid
get-edid: get-edid version 1.4.1
Performing real mode VBE call
Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
Function supported
I'm dropping the priority of this from critical to high, because while
there are still some important resolution problems, it appears we've
solved the worst monsters. Almost every article published about Ubuntu
Feisty included a mention of failure to detect resolution, but reviews
of Ubuntu Gutsy
I managed to fix (via workaround) for this problem by installing gutsy and then
installing Envy.
Envy is not core ubuntu software it is written by some italian guy but
the code needs to be included Ubuntu as it solves a lot of monitor
configuration problems.
--
Xorg resolution falling back to
I found bug 115220 recently; looks like Bryce patched the aspect ratio
code on Oct. 17th.
Even with that patch, I still have to delete 1600x1200 from xorg.conf
to get X to start up. And then the maximum resolution is 1400x1050
instead of 1680x1050. I'm probably seeing the issue where the
Well I see this what I believe to be this bug with Gutsy but not
Drapper. And in Gutsy it affects all but text-mode: that is both
Graphical boot screen AND X, both in the live CD + when installed. Not
knowing how to override to a textmode install I had to used the live CD
by pushing Ctrl+Alt+Minus
Oh and safe VGA mode on the CD had the same issues!
--
Xorg resolution falling back to 640x480 and/or 800x600 when h/v freqs incorrect
https://bugs.launchpad.net/bugs/3731
You received this bug notification because you are a member of Kubuntu
Team, which is a subscriber of a duplicate bug.
--
The way I found to get the boot screen working was to install StartUp-
Manager and choose a new resolution there.
--
Xorg resolution falling back to 640x480 and/or 800x600 when h/v freqs incorrect
https://bugs.launchpad.net/bugs/3731
You received this bug notification because you are a member of
I wrote a few days ago to say that the Live CD works OK with my setup.
I have now upgraded my installed version from Feisty to Gutsy and have
found that the splash screen and boot progress bar does not display
because the monitor complains that the settings are out of range. In
Feisty the work
May I tell you about my own issue? It's not the Tecra 8000. The Tecra
8000 issue is a pleasant problem-solving exercise compared to this:
X.Org wrongly detects the screen resolutions available on my monitor. I
have an ATI Radeon X1900 XT connected to a ViewSonic VG2230wm monitor.
It's a
Checkmate, take a look at the description of this bug, and try some of
the suggested things there.
sudo ddcprobe
(attach the output)
Perhaps install the read-edid package, and post the output from:
sudo get-edid
What is the output of:
sudo get-edid | parse-edid
--
Xorg resolution falling back
Peter, attached is the output of sudo ddcprobe.
I can't use read-edid on my 64-bit system. I extracted the EDID hex data from
Xorg.0.log, compiled my own parse-edid, and fed it into there. Here's what I
got:
# EDID version 1 revision 3
Section Monitor
# Block type: 2:0 3:ff
Ah, 64 bit. As I understand it, there are some issues probing monitor
info on 64 bit machines that people are working on. Hopefully it will be
resolved by Hardy.
People not replying probably means they don't know how to help.. that or
are jealous of your huge hi-res monitor ;)
--
Xorg
I doubt the 64-bitness is a problem here, because it got the EDID data
from my monitor. The vesa driver has to use an x86 emulator to run code
from the video BIOS, but I think it manages that fine (Fine here, but
not on my Tecra 8000).
I looked at the source code for ddcprobe (part of xresprobe)
Attached is a patch for the file ddcprobe/ddcprobe.c in xresprobe.
Here is the REAL spec for the aspect field of a standard timing descriptor:
00: 16/10
01: 4/3
10: 5/4
11: 16/9
After applying this patch, it mostly works. There's no more 1680x1680 or
1440x1440 when I do sudo dpkg-reconfigure
Changing Gutsy screen resolutions does not work on my computer.
Gutsy incorrectly chooses 1920x1440 at 61Hz and although I see options
to change such, when I click apply nothing happens.
The screen resolution I need is 1152x864. I did hope that Ubuntu would
finally work this time around, but no.
It is fixable - you need to edit your xorg.conf file. There will be
instructions somewhere - probably on the wiki.
The screen resolution I need is 1152x864. I did hope that Ubuntu would
finally work this time around, but no.
I now have a coaster with Ubuntu Gutsy on it.
Oh well. Maybe this
of troublesome displays and corresponding EDID files if this
shows some promise to resolve some issues.
-original message-
Subject: [Bug 3731] Re: Xorg resolution falling back to 640x480 and/or 800x600
when h/v freqs incorrect
From: Chris [EMAIL PROTECTED]
Date: 20/10/2007 17:16
Changing Gutsy screen
Just downloaded the Gutsy Live CD and it works fine with my ATI Radeon
Xpress 200 graphics and HP vs17x monitor. This was the acid test for me
that the problems I originally had with the Dapper live CD install have
been fixed. Awesome and well done!
--
Xorg resolution falling back to 640x480
similar problem to Caroline
sudo ddcprobe
vbe: VESA 3.0 detected.
oem: NVidia
vendor: NVidia Corporation
product: NV17 () Board Chip Rev A2
memory: 131072kb
mode: 640x400x256
mode: 640x480x256
mode: 800x600x16
mode: 800x600x256
mode: 1024x768x16
mode: 1024x768x256
mode: 1280x1024x16
mode:
Demosthenes, please report the focus issue to a separate bug; it's
almost assuredly unrelated to this one.
Caroline, interesting, it seems your card is mis-reporting its
capabilities via ddcprobe. I've not run across this situation before.
Are you also able to successfully specify 1280x1024 in
John, so yeah if you're seeing 'edidfail', then your bug is 94994. I
recommend subscribing to that one. I have some ideas on that one and am
hopeful we can knock it out next week; there's been some really good
successes the past couple weeks at solving some long standing resolution
bugs, and I
Checkmate: wow, that's an insidious little bug you've found! We'll
want to do some testing before we commit that. Can you file a new bug
requesting that patch, and assign it to me? I think if it causes no
other unusual behavior we can roll out that change for Gutsy.
--
Xorg resolution
Bryce: I have submitted bug 146643.
--
Xorg resolution falling back to 640x480 and/or 800x600 when h/v freqs incorrect
https://bugs.launchpad.net/bugs/3731
You received this bug notification because you are a member of Kubuntu
Team, which is a subscriber of a duplicate bug.
--
kubuntu-bugs
thanks Bryce.. I finally found the timings for the Viewsonic VA1912W
and manually created a 1440x900 resolution and enabled it and it works,
and enabled anti-aliasing, vibrance, etc with the Nvidia control panel -
but now another weird problem when some apps close (like a full screen
app just
ddc probe finds the resolutions for my monitor, but not for my graphics
chip?
sudo ddcprobe
Password:
vbe: VESA 3.0 detected.
oem: NVIDIA
vendor: NVIDIA Corporation
product: CR17 Board Chip Rev A3
memory: 32768kb
mode: 640x400x256
mode: 640x480x256
mode: 800x600x16
mode: 800x600x256
mode:
I tried sudo ddcprobe and command was not found.. Using standard Ubuntu
installation with Nvidia card and Viewsonic widescreen (VA1912W) that
should be 1440x900.
Any ideas?? It's the only thing left that stops me from switching from
XP to Ubuntu.
--
Xorg resolution falling back to 640x480
Heya all,
I'm just surfacing to report some progress made on resolution detection
for Gutsy. We've found a fix for a sub-class of this bug, for
situations involving LCDs with analog connections (I assume this is
VGA connections as opposed to DVI) where the highest (and most correct)
resolution
OK. This is from the X.Org mailing list (I wrote to it):
Julien Cristau wrote:
On Thu, Sep 20, 2007 at 20:13:15 -0700, Nolan Check wrote:
I own a Toshiba Tecra 8000 laptop. The display device is a NeoMagic
MagicGraph256AV, which uses the NM2200 chipset. The monitor goes up to
1024x768.
This is already reported: Tecra 8000 laptop video (Neomagic
MagicGraphAV256 with NM2200 chipset) automatically detects as only
640x480. I can fix that by setting HorizSync and VertSync in
/etc/X11/xorg.conf. Then the fonts are way too small, so I fix that by
setting a workable DPI value. I think
Gutsy, LG Studioworks 57i is not recognized correctly resulting in
[EMAIL PROTECTED] :) mode. This fortunately falls back to [EMAIL PROTECTED]
Running displayconfig-gtk and selecting generic monitor solves the
problem (this very model is not in the database).
--
Xorg resolution falling back to
GeForce 6x series and VA1912W widescreen monitor that should be
1440x900.. Stuck on 1024x768. Don't want to go mucking anything up but
this is what I believe to be the relevant sections of my XConfig file -
I have enabled the 'restricted' NVidia driver (restricted, it's only
restrictive to be
I don't know if this information helps, but I have to tell ;)
When I connect my beamer to my laptop with a long (5m) vga-cable, the desktop
and beamer resolution is set to 800x600 and I don't get the resolution higher.
When I use a short cable (1.5m) everything works fine (1024x768).
So for now,
Apparently the longer cable is defective.
I do not know how long the cable can be until the roundtrip for the
signal is too long for ddc to work but 5m is not that much.
--
Xorg resolution falling back to 640x480 and/or 800x600 when h/v freqs incorrect
https://bugs.launchpad.net/bugs/3731
You
Michal:
I've noticed monitor signals don't travel well in really long VGA cables and
_some_ laptops seem more susceptible than others to the problem (this is under
Windows to projectors). This doesn't rule out the possibility of being able to
workaround the issue but once you get a cable over
Thanks for all the info in this post. It was very helpful.
To those with a Westinghouse LTV-32w3 LCD TV - use the following and you will
see all resolutions...
HorizSync 50-75
VertRefresh60-75
--
Xorg resolution falling back to 640x480 and/or 800x600 when h/v freqs
Byce,
Not sure if I should post this here or add to the wiki solution but I
have attached the boot screen for the MEPIS solution to the Ubuntu #3731
bug. The MEPIS 6.0 Linux distro is actually based on Ubuntu packages
but they added this front end capability to resolve the monitor
resolution
Let's also start a spec for a true fix for this:
https://wiki.ubuntu.com/X/AutodetectMonitorFrequency
DisplayConfigGtk and BulletproofX are both important, yet they are just
workarounds to the true underlying problems I've outlined in the above
link.
Please join with me in drafting up a much
Many thanks, Bryce, for investing so much in this solution. I love
testing a wide range of Linux live CDs and find that a % recognize my
i810 1024/768 laptop monitor and a % do not recognize it. My question
is not part of the wiki spec discussion but more general. Can I ask if,
in your mind,
Just tested tribe 5 Ubuntu and hoped the new GUI for screen resolution
would finally assist in recognizing my 1028 x 768 LCD intel 810/815
screen resolution.
Did not work. Only worked at low resolution on the safe video mode
start up. Then use the terminal and the sudo dpkg-reconfigure xserver-
Just a heads up, Bryce has a discussion thread about this here:
http://ubuntuforums.org/showthread.php?t=490982
On page 11, at post 105, Bryce talks about some of his work, very
interesting. He posted it yesterday.
http://ubuntuforums.org/showpost.php?p=3248403postcount=105
--
Xorg resolution
I just tested tribe 5, Kubuntu and Ubuntu.
Monitor = 19 Viewsonic G90f+
GPU = ATI x1950 PRO
MB = Gigabyte GA-M55PLUS-S3G
RAM = 2GB (2x1GB)
CPU = AMD 64 X2 3800+
Kubuntu 64bit
gutsy-desktop-amd64.iso
* default screen resolution 1920 x 1440 61Hz (unable to move from this)
* could not change this
Hi Bryce,
Any news about this project?
Anything to test yet?
Chris
--
Xorg resolution falling back to 640x480 and/or 800x600 when h/v freqs incorrect
https://bugs.launchpad.net/bugs/3731
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
Bryce: The X autodetection is not a solution for now. It is so poorly
designed it is unusable.
It does not work by commenting out sections in the config file. You have
to *REMOVE* the config file *COMPLETELY*.
This means that many settings for which there are no reasonable defaults
break.
I fixed the tiling issue with the compaq evo n1000v.
I had to specify HorizSync and VertRefresh in my monitor definition:
Section Monitor
Identifier Monitor0
VendorName LGP
ModelName 6e54
Option DPMS
HorizSync 31.5-90.0
VertRefresh 59.0-60.0
EndSection
After I did this, everything was back to
This gives a black border on the left
Sorry, the black border is on the right.
The resolution should be 1024x768 preferably 24 or 32bpp.
According to the xorg.log, there is DDC data to establish screen
resolution and DPI (I am experiencing DPI issues on Gutsy on other
machines):
(II)
Michal: For automatic device detection, the plan is to let xorg do full
autodetection of both the monitor and the graphics card. That is still
a work in progress (although it already works well for many
configurations). This is actually considered the *true* fix for this
bug 3731, and I'm
Bryce:
Will your BulletProofX work for the Live CD? In my original Bug #68905
the big problem for me was getting my hard drive repartitioned because I
couldn't run gparted in the low resolution. If you remember, I was lucky
to find a Gparted live CD which had a wide range of video setup options.
Bryce:
This sounds similar to what was proposed in
https://wiki.ubuntu.com/XserverFailover
--
Xorg resolution falling back to 640x480 and/or 800x600 when h/v freqs incorrect
https://bugs.launchpad.net/bugs/3731
You received this bug notification because you are a member of Kubuntu
Team, which
An early preview about a GUI config tool we've been working on to help
address this problem, since I know many people are having this problem
and wondering what the plan is:
http://people.ubuntu.com/~bryce/BulletProofX/
This is not a true fix for the root cause of this bug, however it is
going
Keep up the good work Bryce. Looks great so far!
--
Xorg resolution falling back to 640x480 and/or 800x600 when h/v freqs incorrect
https://bugs.launchpad.net/bugs/3731
You received this bug notification because you are a member of Kubuntu
Team, which is a subscriber of a duplicate bug.
--
Looks good, this is certainly an improvement over the X broke, you are
to keep the pieces dialog.
I would suggest several other things:
- when I set the driver to iwantaponny (or physically change the
card) I would like the tool to automatically remove the card section and
generate a new one,
I have attached output from get-edid for my HPvs17x monitor as
requested.
Since getting this problem with Dapper (Bug #68905), I have upgraded to
Edgy. With Edgy I experienced a similar problem. During the boot
sequence the monitor complained about the settings it was given (it asks
for
@Tony, Your edid seems to be correct, and X should use it without
problems.
Video mode setting code for the OS splash screen is in the kernel, and
we hope it will be solved when (and if) the mode setting code is moved
to the kernel. Regardless of that, current kernel code could be
patched, but
I believe that the same class of problems are causing many monitor
resolution/refresh rate problems as listed in bugs 50048, 27667 (these
are the bugs I made comments on) and probably many more. The problems
with the edid data.
The new Xorg server should be able to query monitor by itself for DDC
Yes this happens to me also when I changed my card from Igma to Nvidia
6600 GT
--
Xorg resolution falling back to 640x480 and/or 800x600 when h/v freqs incorrect
https://bugs.launchpad.net/bugs/3731
You received this bug notification because you are a member of Kubuntu
Team, which is a
For Feisty, xresprobe is not included in the default installation. In
theory, this should not be an issue for most people, however I think for
people who don't have xresprobe installed, if they reconfigure Xorg then
the new xorg.conf file could result in incomplete monitor detection, and
thus
In bug 94673, this monitor non-detection is occurring intermittently -
sometimes it detects correctly, sometimes it sets it as generic monitor.
Have others seen intermittent behaviors like this, from boot to boot?
--
Xorg resolution falling back to 640x480 and/or 800x600 when h/v freqs incorrect
Yes, with a rv100 card and Sony G200 monitor. It was not from boot to
boot but from X start to X start. That is probably why Windows keep the
resolution settings when no screen is detected. It may be turned off,
disconnected, or the detection just might have failed.
--
Xorg resolution falling
I remember that after installing the crt was in the 1024 x 768 mode
(after a restart) I played with the desktop effects and switched those
off again. After some time the crt switched spontaneously to 800 x 600
and in the menu only this mode and 640 x 480 was available. The
xresprobe install solved
had a buddy with this problem in his 7.04 and fixed the problem by going
to system settings..monitor and display...addmin
mode..hardware...monitor configure...chose generic...click the right
resolution for your screen ok and restart Xserversorry about not
applying you with tecnical info I am a
Here is a related thread to discuss this further, to complement this
launchpad Bug #3731 reporting:
http://ubuntuforums.org/showthread.php?t=423745
--
Xorg resolution falling back to 640x480 and/or 800x600 when h/v freqs incorrect
https://bugs.launchpad.net/bugs/3731
You received this bug
Hi
My name is Ed [EMAIL PROTECTED]
I had a problem installing version 7.0. I could not get a resolution
greater than 640 x 480. This prevented me from installing the system,
therefore I could not do any of the tweaks that you folks had suggested.
My solution was to upgrade my video card
** Tags added: metabug
--
Xorg resolution falling back to 640x480 and/or 800x600 when h/v freqs incorrect
https://bugs.launchpad.net/bugs/3731
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
Just wanted to add that this doesen't have much to do with the H/V-freqs
being wrong - having no freqs in xorg.conf has the same effect, even
though the X server reads the monitor's EDID info correctly.
--
Xorg resolution falling back to 640x480 and/or 800x600 when h/v freqs incorrect
Bug posted 109483, a possible dupe of 3731.
Ref:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/109483
Related Gutsy Gibbon idea suggestion thread:
http://ubuntuforums.org/showthread.php?t=423745
I am ready to test possible solutions as this bug affects my current
hardware. I await to be
I would like to add that X often does not detect the monitor either. In
some cases xresprobe or similar can read the monitor info but X cannot.
Sometimes it is the other way around. I suspect there are some marginal
setups that require several retries/longer timeouts than usual.
And there are
bug 91292 shows similar behavior with a cluster of bugs against the
nvidia restricted driver. Several have reported that the failed monitor
detection only showed up after upgrading to Feisty from earlier
versions, suggesting there is a software change involved (perhaps
xresprobe went missing, or
Also see bug 8177 regarding vbetool. Also has some good background into
the ddcprobe situation and describes some of the amd64 portability
problems.
--
Xorg resolution falling back to 640x480 and/or 800x600 when h/v freqs incorrect
https://bugs.launchpad.net/bugs/3731
You received this bug
I have manually edited the xorg.conf many times, with many variations.
Yes setting the H and V refresh rates and modes will eventually enable
one of a few viewable outcomes, but such is easily broken.
For example, I went to see the 3d cube, Compiz, installed/enabled the
drivers, reboot and I was
Hi,
as this bug seems to be the one where to gather resolution autodetection
problems, here I go.
Feisty failed to detect well the native resolution (1400x1050) of my
laptop screen. That is strange because xresprobe gave the right one. I
have no idea what went wrong.
It's an asus laptop based
** Summary changed:
- Xorg resolution falling back to 640x480 when h/v freqs incorrect
+ Xorg resolution falling back to 640x480 and/or 800x600 when h/v freqs
incorrect
** Description changed:
I'm upgrade my system to ubuntu 5.10, after that, xorg can't load the
correct resolution of the
Some data points from my own experimentation with hardware at hand:
Did NOT detect monitor on an Intel x86_64 box with nVidia Quadro NVS 285
card that has a VGA splitter cord that makes the card dual-head
capable. It was tricky getting xinerama working on this card so I'm not
surprised it had
** Description changed:
I'm upgrade my system to ubuntu 5.10, after that, xorg can't load the
correct resolution of the monitor ( 1024 x 768 ). I'ts only load
640x480. I've used dpkg-recunfigure xserver-xorg, and insert the correct
values, but don't work. The system is a Samsung 753dfx
82 matches
Mail list logo
