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
*** This bug is a duplicate of bug 89853 ***
https://bugs.launchpad.net/bugs/89853
** This bug is no longer a duplicate of bug 96533
X server crashes starting live installation
** This bug has been marked a duplicate of bug 89853
[regression] 7.2 broke vesa: No matching modes found
--
tried todays build (on a DVD) and still no good.
Please see this comment:
https://launchpad.net/ubuntu/+source/xserver-xorg-video-vesa/+bug/89853/comments/30
There could be two bugs here. I would suggest getting Xorg.0.log from
bug 95253 and checking if the error message is 'No matching modes'
I think the Fedora patch is wrong, or is fixing a different problem. The
Fedora patch is never even reach in the failure case presented in this bug
report.
See my analysis here:
== Cut from Vesa.c =
pScrn-modePool = VBEGetModePool (pScrn, pVesa-pVbe, pVesa-vbeInfo,
I just tested this one:
feisty-desktop-i386.iso 26-Mar-2007 07:44 697M
83ae247bdc59e701b91792322a37 *feisty-desktop-i386.iso
Did not work unfortunately. I did not check if the latest vesa driver
made it into this image.
--
[regression] X broken in Feisty Herd 5 Live
Fedora has a new driver out in the last few days that attempts to
address (probably) the same problem. This is now at 1.3.0-5.fc7
As an experiment I extracted vesa_drv.so from the fedora package. Then
I booted into an alpha version of the Ubuntu Feisty livecd, and copied
over the vesa driver.
Great and thanks for the follow up. Please let me know when the fix
makes it to a test CD and will try it out and report back.
--
[regression] X broken in Feisty Herd 5 Live
https://launchpad.net/bugs/89853
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Maybe some bad news on this one. The new vesa driver (1.3) will
probably not fix the problem.
The fedora guys already have 1.3 and the problem is still there. From
what I can tell, the problem comes from changes in the xserver that went
into 7.2.
This is a me too. Same machine, same graphics card. Xorg does not
start, so install is impossible.
The graphics card is not supported by X, so vesa is the correct driver
in this case. I tried copying the xorg.conf from 6.10 and that did not
help.
This is quite a popular laptop by the way, so
** Attachment added: xorg.conf
http://librarian.launchpad.net/6718807/xorg.conf
--
[regression] X broken in Feisty Herd 5 Live
https://launchpad.net/bugs/89853
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: Xorg.0.log when X fails to start
http://librarian.launchpad.net/6718840/Xorg.0.log
--
[regression] X broken in Feisty Herd 5 Live
https://launchpad.net/bugs/89853
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: lspci -vv
http://librarian.launchpad.net/6718847/lspcivv
--
[regression] X broken in Feisty Herd 5 Live
https://launchpad.net/bugs/89853
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: lspci -nvv
http://librarian.launchpad.net/6718850/lspcinvv
--
[regression] X broken in Feisty Herd 5 Live
https://launchpad.net/bugs/89853
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
More information:
I tried Andrea's fix for the HorizSync and VertRefresh and it worked
for me too.
I dont think the problem is in the xorg.conf however, but probably
something going wrong with the ddc probe. Just a guess.
--
[regression] X broken in Feisty Herd 5 Live
** Attachment added: sudo xresprobe vesa
http://librarian.launchpad.net/6719071/xresprobe
--
[regression] X broken in Feisty Herd 5 Live
https://launchpad.net/bugs/89853
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: ddcprobe
http://librarian.launchpad.net/6719072/logddcprobe
--
[regression] X broken in Feisty Herd 5 Live
https://launchpad.net/bugs/89853
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Ok here is something else interesting.
Here is a Xorg.0.log from the 6.10 bootdisk (which works properly).
Some bug in X 7.2??
** Attachment added: Xorg.0.log from 6.10
http://librarian.launchpad.net/6719289/Xorg.0.log.6.10
--
[regression] X broken in Feisty Herd 5 Live
** Attachment added: Xorg.conf from 6.10 livecd
http://librarian.launchpad.net/6722596/xorg.conf.6.10
--
[regression] X broken in Feisty Herd 5 Live
https://launchpad.net/bugs/89853
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
This line is extra in the failing Xorg.0.log
(II) VESA(0): Modeline 1280x800 71.11 1280 1328 1360 1440 800 802
808 823 -hsync -vsync
Dont ask me what it means though :-)
--
[regression] X broken in Feisty Herd 5 Live
https://launchpad.net/bugs/89853
--
ubuntu-bugs mailing list
Maybe upstream bug:
https://bugs.freedesktop.org/show_bug.cgi?id=10238
--
[regression] X broken in Feisty Herd 5 Live
https://launchpad.net/bugs/89853
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
ok, so what happens now? Do I drive a bugfix from upstream?
Or can you do that?
The other option is to hack up the autodetection to work around the
problem.
--
[regression] X broken in Feisty Herd 5 Live
https://launchpad.net/bugs/89853
--
ubuntu-bugs mailing list
21 matches
Mail list logo
