Launchpad has imported 17 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=10238.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
The bug task for the somerville project has been removed by an automated
script. This bug has been cloned on that project and is available here:
https://bugs.launchpad.net/bugs/1305977
** No longer affects: somerville
--
You received this bug notification because you are a member of Ubuntu
** Changed in: somerville
Status: New = Fix Released
** No longer affects: dell
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/89853
Title:
[regression] 7.2 broke vesa: No matching modes
** Changed in: xorg-server
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/89853
Title:
[regression] 7.2 broke vesa: No matching modes found
--
ubuntu-bugs mailing
** Changed in: xorg-server
Importance: Medium = Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/89853
Title:
[regression] 7.2 broke vesa: No matching modes found
--
ubuntu-bugs mailing
** Changed in: xorg-server
Importance: Unknown = Medium
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I had the same problem in Ubuntu Intrepid Ibex when booting form live CD
or USB.
The video card is an ATI HD2400 Mobility Radeon in a Toshiba A200 laptop.
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/19551346/Xorg.0.log
--
[regression] 7.2 broke vesa: No matching modes
** Tags added: valid-xorg-conf
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I have a samilar problem with Ubuntu Hardy alpha 5 :
(EE) Screen(s) found, but none have a usable configuration.
Fatal server error:
no screens found
http://launchpadlibrarian.net/12164870/log.txt
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
** Changed in: dell
Status: Fix Committed = Fix Released
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
Closing for the other components as well!
** Changed in: xserver-xorg-video-vesa (Ubuntu)
Status: Fix Committed = Fix Released
** Changed in: xorg-server (Ubuntu)
Assignee: Timo Aaltonen = (unassigned)
--
[regression] 7.2 broke vesa: No matching modes found
** Changed in: xorg-server (Ubuntu)
Status: Fix Committed = Fix Released
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Thanks for confirming that Timo's patch to -vesa fixed the issue.
Closing as such.
** Changed in: xorg (Ubuntu)
Importance: Undecided = High
Status: New = Fix Released
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug
By the way, for those wishing to participate in more in-depth testing of
new drivers for Radeon and other chipsets, you may wish to join the
Ubuntu X Testing Forum at
http://ubuntuforums.org/showthread.php?t=490982. We're currently
analyzing the xrandr-enabled 2.7.192 -ati driver, and hope to
** Changed in: dell
Status: New = Fix Committed
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Do we need to do a bug report, or is one already in progress? Maybe
they will just consider this a wishlist item...
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug notification because you are a member of Ubuntu
Bugs, which is
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/136699
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Tormod Volden: With daily-live 20070831 the X server finally started
without a problem on my Mobility Radeon X1600.
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Petr: that's good news, hopefully it works for others, too :)
** Changed in: xserver-xorg-video-vesa (Ubuntu)
Sourcepackagename: xorg = xserver-xorg-video-vesa
Status: New = Fix Committed
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You
Where do I get the daily-live build iso? (Path)
I will try it and let you know.
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
brokencrystal.com: http://cdimage.ubuntu.com/daily-live/current/
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
Hey I just tried the daily build and it worked for me as well. Great job
thanks to all the devs who helped fix this bug... it had been bugging me
for quite a while.
By the way I have an Inspiron 6400 with Radeon X1300 (128mb).
--
[regression] 7.2 broke vesa: No matching modes found
I tried the daily-live build and for the first time since Herd 4 I went
straight to the Desktop without X troubles. Wrong resolution, but at least aI
have X working.
Looks like we can finally close this bug.
Thanks to everyone who took care for this bug. It's people like you that
make strong
finally
for the first time
since ubuntu 6.04
i can finally install the system without jumping through hoops
thanks to the daily 31/08 iso of ubuntu gutsy gibbon
my system is lg P1 pro express dual, running on ati radeon x1400 with a
widescreen
the resolution seems to work fine btw
which is
OK, now will it support my native resolution? The last time I checked,
I didn't see 1280 by 800 even listed...
Dell Inspiron E1505 Notebook
ATI Mobility Radeon X1300
1280 by 800 Native Pixels 32Bit Color 60 Hertz PnP LCD Monitor
Gutsy Tribe 5
--
[regression] 7.2 broke vesa: No matching modes
No. The vesa driver will only support vesa modes, which doesn't include
any widescreen modes.
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
I wouldn't get your hopes up, I've been waiting since Feburary for this bug
to be fixed.
Perhaps 8.03 with the next version of xorg.
On 8/28/07, brokencrystal.com [EMAIL PROTECTED] wrote:
I was hoping this would be fixed by tribe 5, but I am still having the
same problem with tribe 5 as well.
Please try the new xserver-xorg-video-vesa 1.3.0-1ubuntu5 now in Gutsy.
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
** Tags added: iso-testing
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
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
https://bugs.launchpad.net/ubuntu/+bug/131799
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
I noticed that my trace with X700 in comment #142 seems to be the same
as the one from András in comment #98 (from April): crash in same
function and line number. But in the original report there is no crash
and the server log is different. So this must be another issue, although
one may
I was hoping this would be fixed by tribe 5, but I am still having the
same problem with tribe 5 as well.
Dell Inspiron E1505 Notebook
ATI Mobility Radeon X1300
1280 by 800 Native Pixels 32Bit Color 60 Hertz PnP LCD Monitor
Gutsy Tribe 5
--
[regression] 7.2 broke vesa: No matching modes found
I am experincing troubles with this Failed to start the X server since Ubuntu
7.04 on my laptop with ATi Mobility Radeon X1600.
I tried todays gutsy daily-live(20070825), where xorg-server
2:1.3.0.0.dfsg-12ubuntu1 already presents, but the problem still remains.
--
[regression] 7.2 broke vesa:
Andrea:
You managed to get the server working by reconfiguring it, so the patch
_does_ work :) Poor resolution is because of vesa, it doesn't support
widescreen modes.
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug
** Attachment added: log of a startx just after ubuntu boot
http://launchpadlibrarian.net/8969666/Xorg.0.log.BEFORE
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug notification because you are a member of Ubuntu
Bugs, which
@ Timo Aaltonen: Sorry, but your fix is not working for me.
I downloaded and launched (in live mode) Tribe 5 on my Inspiron 6400 (Ati
Radeon Mobility X1400, my hardware isn't changed at all).
As I thought, X is not working yet. Anyway, the behaviour is just slightly
changed: as you can see in
** Attachment added: log of a startx after upgrading to Timo's patched xserver
http://launchpadlibrarian.net/8969668/Xorg.0.log.AFTER
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug notification because you are a member of
Well, I really hope this is true, but since my original report for this bug I
said that reconfiguring xserver allows to start x, so nothing looks changed to
my non_developer non_X_expert eyes. :)
Probably a good test would be to launch ubuntu live with your patched server.
Do you have any
Andrea: If that's the case, then your issue is different from this one.
There are reports that the live-cd doesn't generate a working config,
but after reconfiguration things are working...
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received
Timo: probably my poor english is not helping to understand each other.
Anyway, what I say is that when I reconfigure xserver-xorg I can start X, and
this is true both if the standard xserver is installed and if I upgrade to your
patched xserver. But I noted that launching X, using the original
Timo: I don't think Andrea's issue could be different from this one -
Andrea is the original reporter :)
Perhaps some other people have other issues that are addressed by the
patch, but if it doesn't fix Andrea's original problem that would mean
that their bugs have been misdiagnosed and should
I don't know if it helps at all, but I installed the x86_64 version of
7.04 on my T60 and it worked fine.
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
If anyone of you is using gutsy at the moment, please test a new xserver
version available here:
http://users.tkk.fi/~tjaalton/dpkg/xserver
It has a patch which should fix this for good.
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received
** Changed in: xorg-server (Ubuntu)
Status: Incomplete = Fix Committed
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Tested the -12 xserver and vesa will still not start on ATI X700. Tried to
debug a little with gdb:
- segfaults at line 683 in vesa.c
- the pScrn-display-modes linked list is corrupted, -next is invalid (see
gdb session)
** Attachment added: gdb session crashing vesa
** Attachment added: Xorg log file using vesa driver on X700
http://launchpadlibrarian.net/8961277/Xorg.0.log.vesa
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug notification because you are a member of Ubuntu
Bugs, which
I can confirm this bug on integrated ati xpress 1250 on HP Compaq 6715s
notebook.
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Dell Inspiron E1505 Notebook
ATI Mobility Radeon X1300
1280 by 800 Native Pixels 32Bit Color 60 Hertz PnP LCD Monitor
Ubuntu Gutsy Herd 4
Confirmed
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/8926210/Xorg.0.log.old
--
[regression] 7.2 broke vesa: No matching modes found
Installed restricted driver from command line... These are my logs and
outputs after I did this and was able to get into Gnome...
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/8926215/Xorg.0.log
--
[regression] 7.2 broke vesa: No matching modes found
** Attachment added: E1505GutsyOutputi386Tribe4.txt
http://launchpadlibrarian.net/8926221/E1505GutsyOutputi386Tribe4.txt
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug notification because you are a member of Ubuntu
Bugs,
Installing fglrx driver 8.40.4 on Tribe4 got this message:
[EMAIL PROTECTED]:~$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.4 (2.1 Mesa 7.0)
[EMAIL PROTECTED]:~$
I think some problem
yeap, here too
same bug still here on tribe 4
i use radeon mobile x1400
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Updates from Tribe 4:
The bug is still there, but sudo dpkg-reconfigure xserver-xorg now
allows to start X (no more backtrace and server fatal error) with vesa
driver, without needing to download fglrx.
Sadly, the situation is identical with my original report for this bug,
4 months ago.
--
Going back to Andrea Colangelo's comment, can someone who understands
this better than I sanity check this?
Xorg.0.log showed the monitor could support 1280x800:
(II) VESA(0): Modeline 1280x800 71.11 1280 1328 1360 1440 800 802
808 823 -hsync -vsync
The bios returned SEVERAL 1280x1024
So, I would like to access the shell after xserver crashes loading the LiveCD.
I have read this solution from thayerw that says to:
2. When the screen goes blank and the CD spins down, press CTRL+ALT+F6
I can't figure out when to use the magic combo :)
After X crashes and you says it to show
Ehi, I am experiencing this problem with Tribe3, but I know gutsy is getting
pieces of xorg 7.3.
When is this supposed to be a reality, in Ubuntu?
http://people.ubuntu.com/~bryce/BulletProofX/
If someone say: Tribe5! I will leave for my holidaty happy and get
back more happy to install Ubuntu
I downloaded Gutsy Gibbon Tribe 3 (Desktop) and tried to launch it live to
check about this bug.
Well, the situation isn't changed so much. I can't still boot X due to this No
matching modes found problem.
Anyway, in the original report for this bug, I said: a sudo dpkg-
reconfigure
** Attachment added: Xorg.log for a startx AFTER dpkg-reconfigure xserver-xorg
http://launchpadlibrarian.net/8532248/Xorg.0.log
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug notification because you are a member of Ubuntu
The interpretation I make of your Xorg.log output, (and someone more
knowledgable than I should correct me if I get this wrong) is:
1. You got a perfectly good EDID transfer that described your monitor.
2. Your monitor said the ONLY video mode it will accept is 1280x800.
3. The BIOS of the video
Hi William, I am one of the original bug reporters for this issue.
Looking at your comments I think you are reporting your issues in the
wrong bug report. All the initial reports of this bug show the same
symptom: the error message 'No Matching modes found'. In all original
reports the EDID data
Wow! You're right. I should have gone back and reviewed the earlier
log files.
In the learning I've done since jumping into this situation, I think I
understand what your problem is:
In the situation when the EDID transfer is good, if the display offers a
mode line that the BIOS does not
With help from a friend, I built a test kernel that cuts out a change to
vm86.c that silenced superfluous errors from the audit subsystem, but
which messed with the registers on the return from the int10 call. That
fixed the problem. We KNOW what the root cause is!
ajackson from Red Hat also
Hi,
I have an AMILO Pi 1536 with an ATI X1400 video card.
When I tried the Ubuntu Gutsy Gibbon Tribe 2,I have the same problem.
See attachements.
** Attachment added: dmesg
http://launchpadlibrarian.net/8361625/dmesg
--
[regression] 7.2 broke vesa: No matching modes found
Ask me if you want more details and how can I help you.
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/8361657/Xorg.0.log
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug notification because you are a member
** Also affects: redfish (upstream)
Importance: Undecided
Status: Unconfirmed
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
I think it's not really useful to solve the problem but I tried to use
Ubuntu Gutsy Gibbon Tribe 1 cd under VMWare. The live cd starts
flawlessly... maybe it's really a kernel problem? Gutsy has the new
kernel 2.6.22-6.13 (2.6.22-rc3-based)...
Hope it helps...
--
[regression] 7.2 broke vesa: No
I just ran a new test case:
I managed to run the version 6.8.2 X server under RHEL 5 which normally
runs the 7.1.1 X server. I got it to go far enough to manifest the SAME
partial read with zero padding flakiness that stock RHEL 5, and which
Ubuntu 7.04 manifest.
I conclude that this is a
S.Rey: Thanks very much for the clue of the keyboard accelerator to
move the window. My problem was I could not find any way to do that.
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug notification because you are a member of
Folks, a friend helped me dig into the X server sources, and I now
understand this situation much better.
Many have suggested a work-around that involves setting explicit HorizSync and
VertRefresh values.
This will not help if your monitor is connected to the DVI port of the ATI
Radeon X1300
I am trying to install Feisty on a Dell Optiplex 745 with a Radeon X1300 Pro.
This bug prevents the installation from going forward because the X display
starts up, but at 800x600, and starting with the VERY FIRST dialog of the
installer, selection of the language, the Next button is further than
I am trying to install Feisty on a Dell Optiplex 745 with a Radeon X1300 Pro.
This bug prevents the installation from going forward because the X display
starts up, but at 800x600, and starting with the VERY FIRST dialog of the
installer, selection of the language, the Next button is further than
William:
Do you need 3D and/or an accelerated X? If so, I think you're in for a rough
ride with your choice of hardware on Linux. Why would you choose such kit for
Linux (if it's for Windows and Linux is a sideshow then the question is
irrelevant)?
--
[regression] 7.2 broke vesa: No matching
I scrolled back a bit, and decided to try and follow the proffered procedure of
running
dpkg-reconfigure xserver-xorg
Following that procedure, X is running off the Feisty Desktop Live CD at
1280x1024.
Attached are the xorg.conf and Xorg.0.log files. The ones called good were
after
the
One odd thing: That Xorg.0.log file I just attached was labeled
Xorg.0.log.old, and to my mind, it should be the SAME as the
Xorg.0.log-ubuntu-7.04 file I attached earlier.
Oh! I forgot! I aborted the reconfigure-display once halfway through. This
means that the xorg.conf.old I am about to
** Attachment added: xorg.conf that worked after dpkg-reconfigure
http://librarian.launchpad.net/7731737/xorg.conf-ub-7.04-good
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug notification because you are a member of Ubuntu
** Attachment added: earlier version of xorg.conf that I think is valid.
http://librarian.launchpad.net/7731738/Xorg.0.log-ub-7.04-old
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug notification because you are a member of
Sitsofe, in answer to your query: MIT, like many enterprises,
standardizes on ONE hardware recommendation. Most customers buy it
first and ask if Linux runs on it only later. We are following a
successful multi-use recommendation of the Dell Optiplex GX 620 which
served extremely well for both
How close is this to be resolved?
If I can help more send me instructions and i'm happy to provide more data.
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Use an alternate CD to install and the following instruction to get video
working.
http://www.mikesplanet.net/2007/04/installing-ubuntu-704-ati-x-cards/
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug notification because you
That doesn't apply to all. For instance ATi dropped support for my
Radeon 9000 almost a year ago now.
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
ATI Mobility Radeon x1400, resolution 1280x800
On a clean Feisty install, I can confirm that this works for me too:
1) sudo dpkg-reconfigure xserver-xorg
2) choose Vesa
3) remove all resolutions except 640x480
4) set HorizSync 36-52 and VertRefresh 36-60
5) startx
Cheers
I have Acer
Since dell is going to be shipping notebooks with 7.04, I assume there
will be a re-spin of 7.04 to address this very issue?
Since almost all dell model's have a x1300 or x1400 currently available.
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You
bong bungalan: please see bug 110662 - it may be related to this bug,
but we have yet to confirm that it is, so you are better off following
that bug for updates on solving your issue
Thanks,
-Gabriel
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
On a Mobility Radeon X1400, I can also confirm that installing both the
server and vesa debs fixed this for me.
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
I have experience these things at first run (after installation) of
UBUNTU (Breezy and Feisty) and fixed it by adding horiz and vertical
freqs in xorg.conf. But in Feisty release, sice Im excited about its
desktop effect... i tried to enable the desktop effects and i end up
with all white display
Some additional information: I installed the xserver-xorg-video-
vesa-1.3.0 source package. When I applied the patch 100-fedora-
vesa-1.3.0-mode-heuristics.patch the Xorg exited with a segmentation
fault (same backtrack). Without the patch the Xorg started in 1024x768.
I also tried the live cd
Andras: Thank you for the backtrace, I believe it has useful information
to find the cause.
..but I'm confused how it works without that patch, since when the
original bug was reported that patch was not applied to the package.
Anyway, here is a version which doesn't have the patch:
I've tried, it works. Xorg started in 1024x768
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ATI Mobility Radeon x1400, resolution 1280x800
On a clean Feisty install, I can confirm that this works for me too:
1) sudo dpkg-reconfigure xserver-xorg
2) choose Vesa
3) remove all resolutions except 640x480
4) set HorizSync 36-52 and VertRefresh 36-60
5) startx
Cheers
--
[regression] 7.2
Glen: many thanks for testing, but I'm afraid it doesn't contain much
information.. cannot remove breakpoints.. is puzzling me. Also, the
backtrace is shorter than I'd thought, maybe running 'backtrace full'
would get a more useful output? I know it's lot of work to do...
I've tried the livecd on
The same bug on Thinkpad Z61m, ATI X1400, the native resolution is
1650x1080. I don't how important is this information, but the bug also
occurs if I use externel monitor. I also try to send a backtrace, if
it's needed.
--
[regression] 7.2 broke vesa: No matching modes found
Here is the backtrace of Xorg.
** Attachment added: gdb-Xorg.txt
http://librarian.launchpad.net/7386867/gdb-Xorg.txt
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug notification because you are a member of Ubuntu
Bugs, which
I have a Fujitsu Amilo Pi 1536, Core Duo, ATI x1400, resolution 1280x800
Ubuntu 7.04 (final) Desktop CD x86
I have this bug. More precisely, this one (as It seems to be 2 similar
bugs around):
No valid modes left. Trying less strict filter...
Fatal server error:
Caught signal 11. Server aborting
I'm a total noob but I confirm this bug on an Acer Aspire 5103WLMI with
Mobility Radeon X1300.
Adding HorizSync 36-52 and VertRefresh 36-60 allows me to run the X server.
--
[regression] 7.2 broke vesa: No matching modes found
https://bugs.launchpad.net/bugs/89853
You received this bug
I confirm the bug on an Asus A6ja Centrino Duo with Ati Mobility Radeon X1600.
I've tried both modifing the xorg.conf and a sudo dpkg-reconfigure
xserver-xorg, but they didn't work for me.
Also the first workaround gives a crash, telling Caught signal 11. Server
aborting.
I'll try later the
I got into a soup by removing the restricted ATI driver in my upgraded
version of Feisty (from 6.10 through Herd 5). Not during live CD install
of final Feisty. I just wanted to install the newest ATI driver and
thought that was the way to go, remove first and then add latest. I was
expecting
Rey's workaround works for me. (sudo dpkg-reconfe xserver-xorg, and choosing
only the 640x480 mode).
However I didn't installed the propietary drivers because I couldn't get to
Internet (my fault I think), but after that everything should go well.
--
[regression] 7.2 broke vesa: No matching
Please, no need to confirm this anymore, we know it's broken and are
trying to find the cure.
The bug is not in the driver, since Herd5 didn't have that. I've now put
new xserver-xorg-core which has debugging symbols in it. so no need to
install a -dbg too, so go grab these and get a backtrace:
From my understanding it's possible to get this working with the
Alternate CD, but is there any way at all to get a Live CD booted? I do
a lot of testing with the Live desktops and it would be a godsend if I
could find a way to boot into it. Is there a way to boot without the
GUI using the Live
I figured out a temporary workaround for the Live CD blank screen on
Kubuntu:
[b]This post could be related to an Ubuntu bug filed at[/b]:
[url]https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/89853[/url]
[br].[/br] [br].[/br] [br].[/br]
1 - 100 of 152 matches
Mail list logo
