[Bug 148231] Re: [gutsy] bad modes in xorg.conf

2008-09-05 Thread Brian Murray
** Tags added: valid-xorg-conf -- [gutsy] bad modes in xorg.conf https://bugs.launchpad.net/bugs/148231 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

[Bug 148231] Re: [gutsy] bad modes in xorg.conf

2007-10-16 Thread Tormod Volden
parren, does Gutsy RC have the 0.4.24ubuntu6 version? -- [gutsy] bad modes in xorg.conf https://bugs.launchpad.net/bugs/148231 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list

Re: [Bug 148231] Re: [gutsy] bad modes in xorg.conf

2007-10-16 Thread parren
Ah, in filesystem.manifest on the CD I find xresprobe 0.4.24ubuntu5 so it would seem to be too old in the RC. -peo On 10/16/07, Tormod Volden [EMAIL PROTECTED] wrote: parren, does Gutsy RC have the 0.4.24ubuntu6 version? -- [gutsy] bad modes in xorg.conf

[Bug 148231] Re: [gutsy] bad modes in xorg.conf

2007-10-15 Thread parren
It still happens in the Gutsy RC. -- [gutsy] bad modes in xorg.conf https://bugs.launchpad.net/bugs/148231 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

[Bug 148231] Re: [gutsy] bad modes in xorg.conf

2007-10-12 Thread Daniel Holbach
Was uploaded and accepted. ** Changed in: xresprobe (Ubuntu) Status: Triaged = Fix Released -- [gutsy] bad modes in xorg.conf https://bugs.launchpad.net/bugs/148231 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. --

[Bug 148231] Re: [gutsy] bad modes in xorg.conf

2007-10-10 Thread Steve Langasek
** Changed in: xresprobe (Ubuntu) Status: Incomplete = Triaged -- [gutsy] bad modes in xorg.conf https://bugs.launchpad.net/bugs/148231 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list

[Bug 148231] Re: [gutsy] bad modes in xorg.conf

2007-10-10 Thread Timo Aaltonen
I don't think it is necessary to touch the other entries than vesa, at least not for gutsy. For instance the current SEDLINE for savage works just fine. I'll upload a new version with the vesa-change. -- [gutsy] bad modes in xorg.conf https://bugs.launchpad.net/bugs/148231 You received this bug

[Bug 148231] Re: [gutsy] bad modes in xorg.conf

2007-10-10 Thread Tormod Volden
I agree with Timo. Only vesa has any bugs reported on this. For the other drivers it's just an improvement and not critical. -- [gutsy] bad modes in xorg.conf https://bugs.launchpad.net/bugs/148231 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug

[Bug 148231] Re: [gutsy] bad modes in xorg.conf

2007-10-10 Thread Bryce Harrington
Here is a proposed xresprobe upload with just the VESA line fix, along with a fix for 127008. Thoughts? ** Attachment added: debdiff of changes http://launchpadlibrarian.net/9943152/xresprobe_0.4.24ubuntu6.debdiff -- [gutsy] bad modes in xorg.conf https://bugs.launchpad.net/bugs/148231 You

[Bug 148231] Re: [gutsy] bad modes in xorg.conf

2007-10-08 Thread Daniel Holbach
Hum, where is (0.4.24ubuntu6)? ** Changed in: xresprobe (Ubuntu) Target: None = ubuntu-7.10-rc -- [gutsy] bad modes in xorg.conf https://bugs.launchpad.net/bugs/148231 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. --

[Bug 148231] Re: [gutsy] bad modes in xorg.conf

2007-10-08 Thread Daniel Holbach
** Changed in: xresprobe (Ubuntu) Status: Fix Committed = Incomplete -- [gutsy] bad modes in xorg.conf https://bugs.launchpad.net/bugs/148231 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list

[Bug 148231] Re: [gutsy] bad modes in xorg.conf

2007-10-08 Thread Tormod Volden
Hum, where is (0.4.24ubuntu6)? Sorry, the second patch was made on top of the first patch, hence the two versions in the changelog. -- [gutsy] bad modes in xorg.conf https://bugs.launchpad.net/bugs/148231 You received this bug notification because you are a member of Ubuntu Bugs, which is the

Re: [Bug 148231] Re: [gutsy] bad modes in xorg.conf

2007-10-07 Thread parren
On 10/6/07, Bryce Harrington [EMAIL PROTECTED] wrote: I'm surprised we hadn't run into more issues due to this bug. Blind luck I guess. Well, everyone probably switches away from VESA as quickly as possible. So no one really notices. -- [gutsy] bad modes in xorg.conf

[Bug 148231] Re: [gutsy] bad modes in xorg.conf

2007-10-06 Thread Tormod Volden
Can you please also attach the xorg.conf from /tmp/xprobe.* ? -- [gutsy] bad modes in xorg.conf https://bugs.launchpad.net/bugs/148231 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list

[Bug 148231] Re: [gutsy] bad modes in xorg.conf

2007-10-06 Thread Tormod Volden
Got it. lcdsize would grep for Virtual Size ?x? in the server log, and in filtering out ?x? it would also keep whatever was on the rest of the line. This patch fixes it for the vesa case, but the regexps for all the drivers have the same issue and should probably be corrected. ** Attachment

Re: [Bug 148231] Re: [gutsy] bad modes in xorg.conf

2007-10-06 Thread parren
Tormod, do you still need the xorg.conf? I would have to reinstall because I clobbered the partition again testing some other things. -- [gutsy] bad modes in xorg.conf https://bugs.launchpad.net/bugs/148231 You received this bug notification because you are a member of Ubuntu Bugs, which is the

[Bug 148231] Re: [gutsy] bad modes in xorg.conf

2007-10-06 Thread Tormod Volden
Fixed for other drivers as well. Comments: r128: seems bad, but I don't touch it savage: must be typo, changed [^x] to [^ ] NV, first match: match [0-9]* instead NV, second match: I removed pitch from the regexp, so it will work with and without it. trident: I removed found so that anything

[Bug 148231] Re: [gutsy] bad modes in xorg.conf

2007-10-06 Thread Tormod Volden
parren, no thanks, it's not needed anylonger. -- [gutsy] bad modes in xorg.conf https://bugs.launchpad.net/bugs/148231 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

[Bug 148231] Re: [gutsy] bad modes in xorg.conf

2007-10-06 Thread Bryce Harrington
I'm surprised we hadn't run into more issues due to this bug. Blind luck I guess. Yes, I agree we should get this fix in for xresprobe. ** Changed in: xresprobe (Ubuntu) Importance: Undecided = High Status: Confirmed = Fix Committed -- [gutsy] bad modes in xorg.conf

Re: [Bug 148231] Re: [gutsy] bad modes in xorg.conf

2007-10-05 Thread parren
I tried. But the screen just went blank and never came back (and, yes, I did wait for it quite a while). Sorry. But I did, meanwhile, update the system with all the latest patches, so maybe that's got something to do with it. Might go and reinstall later on. -- [gutsy] bad modes in xorg.conf

[Bug 148231] Re: [gutsy] bad modes in xorg.conf

2007-10-05 Thread Tormod Volden
I still don't understand how it was installed. Can you please try: XRESPROBE_DEBUG=1 xresprobe vesa -- [gutsy] bad modes in xorg.conf https://bugs.launchpad.net/bugs/148231 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. --

[Bug 148231] Re: [gutsy] bad modes in xorg.conf

2007-10-05 Thread parren
Here's the output from xresprobe vesa: laptop: yes; ddc: attempting an X probe forking Xorg id: res: 1280x1024 (pitch 1280) freq: disptype: lcd/lvds id: res: 1280x1024 (pitch 1280) freq: disptype: lcd/lvds I have attached the complete log. ** Attachment added: xorg-vesa.log

[Bug 148231] Re: [gutsy] bad modes in xorg.conf

2007-10-05 Thread parren
OK, I reinstalled Gutsy from scratch. Right after install, the xorg.conf looks like this. Shall now try xresprobe vesa. ** Attachment added: xorg.conf.after-install http://launchpadlibrarian.net/9831721/xorg.conf.after-install -- [gutsy] bad modes in xorg.conf

[Bug 148231] Re: [gutsy] bad modes in xorg.conf

2007-10-05 Thread Tormod Volden
Thanks, that will explain the issue. ** Changed in: xresprobe (Ubuntu) Assignee: Tormod Volden (tormodvolden) = (unassigned) Status: Incomplete = Confirmed -- [gutsy] bad modes in xorg.conf https://bugs.launchpad.net/bugs/148231 You received this bug notification because you are a

[Bug 148231] Re: [gutsy] bad modes in xorg.conf

2007-10-03 Thread parren
It returns: id: res: freq: disptype: lcd/lvds (which is actually the same if I run it from within a windowed terminal). Here's the output of ddcprobe, too: vbe: VESA 3.0 detected. oem: ATI ATOMBIOS vendor: (C) 1988-2005, ATI Technologies Inc. product: M56P 01.00 memory: 16384kb mode:

[Bug 148231] Re: [gutsy] bad modes in xorg.conf

2007-10-03 Thread Tormod Volden
I guess xresprobe is using xprobe.sh instead of ddcprobe. There is an option to xresprobe that makes it leave the Xorg log from running xprobe.sh back in /tmp so you can look at it. Can you find it and attach the log here? -- [gutsy] bad modes in xorg.conf https://bugs.launchpad.net/bugs/148231

[Bug 148231] Re: [gutsy] bad modes in xorg.conf

2007-10-03 Thread parren
Here's the 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 (xorg-server 2:1.3.0.0.dfsg-12ubuntu8) Current Operating System: Linux pearwood 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007

[Bug 148231] Re: [gutsy] bad modes in xorg.conf

2007-10-03 Thread Tormod Volden
Was just going to tell the trick was: XRESPROBE_DEBUG=1 xresprobe fglrx but you figured it out obviously. I note it here for myself :) Please use Attachment next time. The only pitch in this log is this line: Virtual size is 1024x768 (pitch 0) But that is not 1280x1024, so I don't think this log

[Bug 148231] Re: [gutsy] bad modes in xorg.conf

2007-10-02 Thread Tormod Volden
Thanks for your report. Yes, that looks wrong. This is similar to bug 136981. Can you please try: sudo xresprobe fglrx (on a virtual console) to see what's returned from the monitor detection? ** Changed in: xresprobe (Ubuntu) Assignee: (unassigned) = Tormod Volden (tormodvolden)