[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 https://help.launchpad.net/InterBugTracking. On 2007-03-09T15:09:04+00:00 Diego Sánchez Román wrote: Hi, I have a ATI x1400 graphic card. Since xorg 7.2, I can't go into graphic mode because X fails to start. It gives me the following error Vesa (0): No modes found. I got this problem with both Fedora Core 7 Test 2 and Ubuntu Feisty Daily CD (09/03/07). I can't use ati driver either. It doesn't support x1000 series. I hope this to be solved so that I can use these distros. Thanks More Hardware Info: AMILO PI 1536: Intel Core2 7200 2Ghz 2 GB RAM 120 GB HD ATI x1400 128 MB Please, ask me if you need more info. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/89853/comments/12 On 2007-03-11T18:16:07+00:00 Ajax-a wrote: test2 had a broken vesa driver. this should be working in test3, or just update the vesa driver to the one in rawhide. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/89853/comments/24 On 2007-03-13T02:33:37+00:00 Sbrewer-k wrote: I have this exact bug as well. Is the Fedora fix going to be merged back into the vesa driver? If not, then the bug should not be closed just yet. This bug is affecting ubuntu as well: https://launchpad.net/ubuntu/+source/xorg/+bug/89853 Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/89853/comments/25 On 2007-03-13T06:32:01+00:00 Timo Aaltonen wrote: Reopening since this is not fixed upstream, and affects other distros as well. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/89853/comments/26 On 2007-04-16T22:30:50+00:00 Timo Aaltonen wrote: the driver fails with: (EE) VESA(0): No matching modes (EE) Screen(s) found, but none have a usable configuration. and it seems to affect at least some other r5xx-cards as well Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/89853/comments/42 On 2007-05-21T13:46:50+00:00 William Cattey wrote: I am wondering if this is the same bug that is killing Red Hat 5, Ubuntu 7.04, and SuSE 10.1 on the ATI Radeon X1300 card. I will attach Xorg.0.log files from RHEL 4 which successfully configures the X server, and RHEL 5 which says it gets a successful DDC read but which has no actual data from the display with which to configure itself. Is this due to the alleged i2c timeout issue reported in bug 6886? Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/89853/comments/116 On 2007-05-21T13:55:27+00:00 William Cattey wrote: Created attachment 10062 Successful DDC transfer. X version 6.8.2. RHEL 4.5 Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/89853/comments/117 On 2007-05-21T13:56:42+00:00 William Cattey wrote: Created attachment 10064 Failed DDC transfer. X version 7.1.1. RHEL 5. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/89853/comments/118 On 2007-05-21T13:57:46+00:00 William Cattey wrote: Created attachment 10065 Failed DDC transfer. X version 7.2.0. Ubuntu 7.04. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/89853/comments/119 On 2007-05-21T13:59:11+00:00 William Cattey wrote: Created attachment 10066 Successful DDC transfer. X version 7.1.1 with ATI proprietery driver. Ubuntu 6.10. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/89853/comments/120 On 2007-05-28T12:08:20+00:00 William Cattey wrote: A friend and I have dug into the X server sources of RHEL 5, and understand the problem much better. We've put details into the Red Hat buzilla bug 236416 at: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=236416 There we provide a patch and various Xorg.0.log output and a detailed analysis. For the convenience of people looking at the issue from this bug, we attach the patch here. The patch adds printing of a hex dump of the EDID BIOS fetch, and a sleep (2) which seems to enable
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/89853 Title: [regression] 7.2 broke vesa: No matching modes found To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/89853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
** 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 found To manage notifications about this bug go to: https://bugs.launchpad.net/somerville/+bug/89853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
** 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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
** 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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
** 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
** 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
** 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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 start testing AMD's new driver as soon as code becomes available. -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
** 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [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 our community. -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 sth that was fucked up in previouse verssions as well :) thank you all crazy programers that know more than me on how to fix these things now if only my agre modem and soundcard would work 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 contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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. 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 https://bugs.launchpad.net/bugs/89853 You received this bug notification because you are a direct subscriber of the bug. -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
** 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 trigger/expose the other in some situations. So I opened bug #135218 for our crash issue. -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [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: 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
** 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 is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
@ 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 the log, I have not either a backtrace information or a clear error message. I installed Timo's xserver (I made a dpkg -i xserver-xorg-*) but nothing is changed. I attach the Xorg.0.log both before and after the upgrade. Anyway, the usual sudo dpkg-reconfigure xserver-xorg allowed me to start x, altough with a poor 1024x768 resolution, as always. ** Attachment added: xorg.conf as configured by ubuntu http://launchpadlibrarian.net/8969652/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 the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
** 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 Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 indications about the best way to do this? -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 xorg.conf, after installing your patched xserver doesn't work, so it appears to me that your patch doesn't change the situation. I am not an expert about X, but I believe that it could be interesting to see what happens if I boot a live-cd with your patched xserver. -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 be moved to separate reports. ...just to clear things up... Thanks a lot for all of your work towards fixing this, -Gabriel -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
** 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 http://launchpadlibrarian.net/8958234/vesa-gdb-session.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 Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
** 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 is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [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 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [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, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 with kernel version ? Here is my Xorg.0.log X Window System Version 1.3.0 Release Date: 19 April 2007 X Protocol Version 11, Revision 0, Release 1.3 Build Operating System: Linux Ubuntu Current Operating System: Linux linux-ubuntu 2.6.22-9-386 #1 Fri Aug 3 00:21:52 GMT 2007 i686 Build Date: 26 July 2007 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Fri Aug 17 23:22:54 2007 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout Default Layout (**) |--Screen Default Screen (0) (**) | |--Monitor SyncMaster (**) | |--Device ATI Technologies Inc RV350 AR [Radeon 9600] (**) |--Input Device Generic Keyboard (**) |--Input Device Configured Mouse (**) |--Input Device stylus (**) |--Input Device cursor (**) |--Input Device eraser (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/cyrillic, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType (==) RgbPath set to /etc/X11/rgb (==) ModulePath set to /usr/lib/xorg/modules (**) Extension Composite is disabled (II) Open ACPI successful (/var/run/acpid.socket) (II) Loader magic: 0x81e5980 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 1.2 X.Org XInput driver : 0.7 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on linux (II) LoadModule: pcidata (II) Loading /usr/lib/xorg/modules//libpcidata.so (II) Module pcidata: vendor=X.Org Foundation compiled for 1.3.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 1.2 (++) using VT number 7 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1106,0282 card 1043,80a3 rev 00 class 06,00,00 hdr 80 (II) PCI: 00:00:1: chip 1106,1282 card , rev 00 class 06,00,00 hdr 00 (II) PCI: 00:00:2: chip 1106,2282 card , rev 00 class 06,00,00 hdr 00 (II) PCI: 00:00:3: chip 1106,3282 card , rev 00 class 06,00,00 hdr 00 (II) PCI: 00:00:4: chip 1106,4282 card , rev 00 class 06,00,00 hdr 00 (II) PCI: 00:00:7: chip 1106,7282 card , rev 00 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1106,b188 card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:0b:0: chip 109e,036e card , rev 11 class 04,00,00 hdr 80 (II) PCI: 00:0b:1: chip 109e,0878 card , rev 11 class 04,80,00 hdr 80 (II) PCI: 00:0d:0: chip 10b7,9200 card 10b7,1000 rev 74 class 02,00,00 hdr 00 (II) PCI: 00:0e:0: chip 1102,0002 card 1102,8040 rev 05 class 04,01,00 hdr 80 (II) PCI: 00:0e:1: chip 1102,7002 card 1102,0020 rev 05 class 09,80,00 hdr 80 (II) PCI: 00:0f:0: chip 1106,3149 card 1043,80ed rev 80 class 01,04,00 hdr 80 (II) PCI: 00:0f:1: chip 1106,0571 card 1043,80ed rev 06 class 01,01,8a hdr 00 (II) PCI: 00:10:0: chip 1106,3038 card 1043,80ed rev 81 class 0c,03,00 hdr 80 (II) PCI: 00:10:1: chip 1106,3038 card 1043,80ed rev 81 class 0c,03,00 hdr 80 (II) PCI: 00:10:2: chip 1106,3038 card 1043,80ed rev 81 class 0c,03,00 hdr 80 (II) PCI: 00:10:3: chip 1106,3038 card 1043,80ed rev 81 class 0c,03,00 hdr 80 (II) PCI: 00:10:4: chip 1106,3104 card 1043,80ed rev 86 class 0c,03,20 hdr 80 (II) PCI: 00:11:0: chip 1106,3227 card 1043,80ed rev 00 class 06,01,00 hdr 80 (II) PCI: 00:11:5: chip 1106,3059 card 1043,810d rev 60 class 04,01,00 hdr 00 (II) PCI: 00:11:6: chip 1106,3068 card , rev 80 class 07,80,00 hdr 00 (II) PCI: 00:12:0: chip 1106,3065 card 1043,80ed rev 78 class 02,00,00 hdr 00 (II) PCI: 00:18:0: chip 1022,1100 card , rev 00 class 06,00,00 hdr 80 (II) PCI: 00:18:1: chip 1022,1101 card , rev 00 class 06,00,00 hdr 80 (II) PCI: 00:18:2: chip 1022,1102 card , rev 00 class 06,00,00 hdr 80 (II) PCI: 00:18:3: chip 1022,1103 card , rev 00 class 06,00,00 hdr 80 (II) PCI: 01:00:0: chip 1002,4152 card 148c,2079 rev 00 class 03,00,00 hdr 80 (II) PCI: 01:00:1: chip 1002,4172 card 148c,2078 rev 00 class 03,80,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x -
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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. -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 modes: Mode: 107 (1280x1024) Mode: 119 (1280x1024) Mode: 11a (1280x1024) Mode: 11b (1280x1024) Mode: 163 (1280x1024) Mode: 164 (1280x1024) Mode: 165 (1280x1024) Mode: 166 (1280x1024) Mode: 124 (1280x1024) but then it concluded: (II) VESA(0): Total Memory: 256 64KB banks (16384kB) (II) VESA(0): Generic Monitor: Using hsync range of 28.00-51.00 kHz (II) VESA(0): Generic Monitor: Using vrefresh range of 43.00-60.00 Hz (II) VESA(0): Not using built-in mode 1024x768 (no mode of this name) (II) VESA(0): Not using built-in mode 1024x768 (no mode of this name) (II) VESA(0): Not using built-in mode 800x600 (no mode of this name) (II) VESA(0): Not using built-in mode 800x600 (no mode of this name) (II) VESA(0): Not using built-in mode 640x480 (no mode of this name) (II) VESA(0): Not using built-in mode 640x480 (no mode of this name) (WW) VESA(0): No valid modes left. Trying less strict filter... Backtrace: 0: /usr/bin/X11/X(xf86SigHandler+0x81) [0x80c8641] 1: [0xe420] 2: /usr/bin/X11/X(InitOutput+0x9a4) [0x80a8304] 3: /usr/bin/X11/X(main+0x27b) [0x8076c7b] 4: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7d20030] 5: /usr/bin/X11/X(FontFileCompleteXLFD+0x1ed) [0x80761b1] Is that backtrace because of a possible bug in the less strict filter? It seems to me that an available 1280x1024 mode of the video card should be able to be masked off as a portal into a 1280x800 display, or am I just being silly? -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 log and then you re sent back to console? -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 on macbook pro with no problems at all. Come on, give me some good news, it's summer! -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 xserver-xorg, even accepting all default choices, solves the problem. Now, this is no more true, because an xserver-xorg reconfigure doens't help at all. You can check out attached Xorg.conf and Xorg.log after the reconfigure. The only solution is to connect to the Internet and download the fglrx driver (a simple apt-get install xorg-driver-fglrx). After that, a dpkg- reconfigure xserver-xorg, accepting all default values (except regarding the resolution), solves to problem¹. My hardware isn't changed from the original report for this bug (a Dell Inspiron 6400 with an Ati Mobility Radeon X1400 and 1280x800 LCD panel). [1] After installing fglrx, when I reconfigure xserver-xorg, I can't choose Monitor autodetection, otherwise screen goes black and system is no more usable - need to reboot) ** Attachment added: xorg.conf AFTER sudo dpkg-reconfigure xserver-xorg http://launchpadlibrarian.net/8532233/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 the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
** 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 Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 card said it would accept 1280x1024, but made no mention 1280x800, and so the X server concluded it could not work. It looks like you're running an ATI Radeon X1400 on a widescreen laptop. -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 was actually transferred correctly. If you look through all the xorg.0.log files you will see that is the case. I would suggest, if you have not already done so, that you open a separate bug report. This way the developers can focus on fixing these issues separately. -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 support, you will lose. In the Xorg.log file you attached on 3/9/2007, indeed there's a good EDID transfer. A detailed modeline is supplied for 1280x800, but then there are no 1280x800 configurations offered by the BIOS. (If I've understood how the log file works, and my assumption that the detailed mode specs are from the BIOS, whereas the 1280x800 spec is from the monitor.) I have also been tracking my symptom in another bug. I apologize for inadvertently hijacking your bug. -Bill -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 pointed out that one can do on the x86 platform what is done on the other platforms, use x86emu. So HERE is the bottom line: The definitive symptom here is if the EDID hex output in Xorg.0.log is missing, or mostly zeros. If you don't have this symptom, you're being bit by a different bug. The definitive work-around until the vm86.c kernel bug is fixed, or a more clever approach to getting the EDID data is added to the X server, is to add the line: Option Int10Backend x86emu to the ServerLayout section of 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 the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [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 of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
** 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 kernel problem. It seems to affect the VESA EDID fetch under Red Hat, Ubuntu, and perhaps SLED 10.1. I've never before submitted a bug to kernel.org, but that seems like the next step. Can anyone advise me the polite way to move this forward? Note that a stand alone utility, get-edid (which is actually available as the Debian read-edid package) is always 100% successful in the EDID transfer, and so part of the mystery is, Why does X fail whereas the small stand-alone utility succeed? Who wants to help resolve this mystery? Or are people going to say, The reverse engineered Radeon Server is going to take care of this so we don't need to care. and wait for some OTHER manifestation of this bug to hurt people? -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 series, (and probably related cards) because the DVI configuration carefully ignores any xorg.conf input, and goes with what is returned by the EDID BIOS transfer. The root cause here is flaky EDID BIOS transfer. My friend and I have posted up-to-date work on fault isolation on that EDID BIOS tranfer in Red Hat Bugzilla bug 236416 at: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=236416 By adding in a sleep(2) just before the EDID BIOS read, we get a partial or complete fetch of the monitor data. Apparently the latest 7.2 X server in use by Ubuntu 7.04 is able to time things differently by fiddling with the module load order. (I have Xorg.0.log file output showing failed or successful EDID transfers depending on the addition or deletion of a module load i2c line.) I've searched the x.org bug tree and found a relevant bug: https://bugs.freedesktop.org/show_bug.cgi?id=10238 But the understanding is not as detailed as what my friend and I have recorded n the Red Hat Bugzilla bug. I think that even the Fedora folks working this bug think the remedy is code to set explicit HorizSync and VertRefresh values, because that seems to be what is in the patch for Fedora 7 test3 which some people report as helpful. -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 600 pixels down the page. The dialog cannot be resized any smaller. Now it seems irrelevant, but you can always move the windows so that the buttons are clickable. You can press Alt and simultaneously click in any point of the window, and move the mouse without releasing the mouse button. I had to install in 640x480 mode and it worked. After instalation I switched to fglrx and everything worked fine (except AIGLX, of course). -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 600 pixels down the page. The dialog cannot be resized any smaller. According to the Xorg.0.log file the DDC transfer that would ordinarily enable the X server to configure at higher resolution got NO data (but a successful transfer?). So Feisty is install is DEAD IN THE WATER on the popular Optiplex 745 line until this bug is fixed. (MIT was hoping to standardize on that Optiplex configuration but if we can't get past step one of the Ubuntu 7.04 install, it's bad both for the Dell config, and the support of Ubuntu at MIT. Attached is the Xorg.0.log I got. How can I help move this forward? William Cattey Linux Platform Coordinator Massachusetts Institute of Technology Cambridge, MA, USA ** Attachment added: Xorg.0.log-ubuntu-7.04 http://librarian.launchpad.net/7731486/Xorg.0.log-ubuntu-7.04 -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 reconfigure. THe ones called old are the ones from before running dpkg-reconfigure. (Presuming that the reconfigure made a backup file, and that the file xorg.conf.200705214138 is the backup. It appears so.) I note the following possibly very interesting observation: The Xorg.0.log file shows a SUCCESSFUL DDC transfer this time around. The xorg.conf file DELETES the line load i2c. Does anyone else think this is significant? ** Attachment added: Log of failed startup. http://librarian.launchpad.net/7731700/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 Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 attach may not be the old one. Sigh. ** Attachment added: Successful startup after dpkg-reconfigure http://librarian.launchpad.net/7731728/Xorg.0.log-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 Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
** 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 Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
** 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 Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 Windows and Linux use. MIT buys a LOT of Dell and a LOT of Optiplex, to the extent that at our recent Hardware Core Team meeting the discussion was, Well, if Linux doesn't work on the Dell hardware we're buying this year, we'll just tell people to wait until next year to buy new desktop hardware. I.E. I don't get much choice about what hardwaqre we standardize upon. My job is Make it work whatever it is. -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 Aspire 5021 Wlmi, res: 1280x800, Ati radeon x700, the same problem. I cannot boot the live cd so I cannot install ubuntu. I tried that above (but a bit different), I did reconfigure -- ati -- horizsync, vertsync, res: 1280x800. Then startx. Then it said that one panel (panel 0) is already running (the one that crashed on ctrl+alt+f7) and that I could delete the /tmp/.X0-lock and then try to startx again if the panel is not running. When I delete it and startx, it manages to bring x up and then I get a message (in gui, so nice resolution and all) that it will shut down because some other panel is already running (of course). The point is that it got in x with 1280x800 running. I will download now the alternate disc and try that. mail: [EMAIL PROTECTED] Thanks in advance. btw any word of an ubuntu installation disc that works, :D -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 (Desktop unusable). I just dont know if somebody has experience this issue and i just dont know if this has something to do with VESA driver. CPU: AMD Sempron 2600+ MotherBoard / Chipset: ASROCK MBoard K7VM3 with VIA KM266Pro and VIA VT8235 North Bridge and south bridge Chipset controller respectively. HDisks: (Primary Maxtor) 40GB partition into 2 (1st partition is windowsXP, 2nd partition UBUNTu Feisty) (Secondary Seagate) 40GB partition into 2 (1st partition is FAT32, 2nd partition is NTFS) Video: Asrock Built-in Memory: 256 -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 using vesa_drv.so compiled without the patch, it also started automatically 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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: http://users.tkk.fi/~tjaalton/dpkg/xserver-xorg-video- vesa_1.3.0-1ubuntu4.2_i386.deb -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 a Thinkpad Z61p since it has a R5xx-series graphics chip, but vesa worked with it.. duh! -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [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 is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 The horizontal and vertical refresh workaround doesn't work for me, and simply reconfiguring xserver-xorg doesn't work either. I have found a workaround. Hope it helps somebody. (See this: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/103945/comments/1) I got to start X with a resolution of 640x480, by deleting all the other modes in xorg.conf (or by sudo dpkg-reconfe xserver-xorg, and choosing only the 640x480 mode). With this, I reached the live CD desktop and I managed to complete the installation. After that (and with wifi internet working), I installed the propietary fglrx, and choose the 1280x800 native resolution). -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 Rey's workaround and tell you. I'm afraid of the possibile consequences of this bug, thinking about people just moving from their old operating system to Feisty. -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 Feisty to automatically replace the restricted driver with Vesa, but instead I experienced... Server aborting and X not loading. Reconfiguring xserver-xorg did not work unless all resolutions but 640x480 were removed. As S. Rey has mentioned above. I then get back into GDM and can reinstall the prop ATI driver. So steps to get it to work: At command line after failure: 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 In GDM 6) sudo apt-get install xorg-driver-fglrx (or latest from ATI) 7) sudo aticonfig -initial 8) see to it that /etc/X11/xorg.conf really gets changed after aticonfig 9) should be up and running (my native resolution 1680x1050, ATI x1600 on HP nx9420) My question is why allow a user the option of removing a functioning driver if it is not going to be replaced by another? It's one thing for us handy guys to experience problems. But a newbie, like the ones we want to start using Ubuntu instead of Windows don't want to experience anything of the sort. They're really not interested whether their computer is fitted with an Nvidia or ATI card! My opinion is that the Restricted driver manager should not have the option of un-enabling a working ATI driver. If it works let it work! Those who want to can do this via the terminal instead. Just my humble opinion. -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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: http://users.tkk.fi/~tjaalton/dpkg/xserver-xorg-core_1.2.0-3ubuntu7.4_i386.deb http://users.tkk.fi/~tjaalton/dpkg/xserver-xorg-video-vesa_1.3.0-1ubuntu4.1_i386.deb Thanks! -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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 CD? Just so I can get access to the network and/or modify the xorg.conf from a terminal... -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89853] Re: [regression] 7.2 broke vesa: No matching modes found
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] If, like me, you have the need to use the Live CD instead of an alternate installation and you can't because you have a Dell Inspiron 6400 with an ATI X1400... I found a workaround: Note: I have only confirmed this with the Kubuntu 7.04 Live CD, not Ubuntu... if someone would test it with Ubuntu and post results, that'd be great... 1. Boot the Live CD as normal 2. When the screen goes blank and the CD spins down, press CTRL+ALT+F6 3. Then type: sudo apt-get update sudo apt-get install xorg-driver-fglrx sudo depmod -a sudo aticonfig --initialize sudo aticonfig --overlay-type=Xv sudo startx 4. X should restart and load the KDM desktop -- [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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
