Accepted xresprobe 0.4.24ubuntu1 (source)
jerone at gmail.com
Sun Apr 8 17:15:06 BST 2007
This is a bit off topic. Post feisty xrespose should be totally
eliminated and replaced. I've seen your proposal for this here:
The elimination of xrespose would be great as it would resolve
problems as seen here for example:
Distros such as Suse do not seem to have these problems with monitor
detection. While Fedora/Redhat is now totally dependent on X to detect
optimal resolutions for the monitor.
This just seems to be one of those issues in Ubuntu that can easily go
away by replacing xrespose with something more common and up to date.
On 3/15/07, Matt Zimmerman <mdz at ubuntu.com> wrote:
> On Thu, Mar 15, 2007 at 09:10:35PM +0200, Timo Aaltonen wrote:
> > On Thu, 15 Mar 2007, Matt Zimmerman wrote:
> > > Do you mean to say that the modes reported by the BIOS are not accurate, but
> > > they are useful? e.g., if the panel is 1920x1200, it will provide larger
> > > modes than if the panel is 1024x768?
> > BIOS doesn't say what size the panel is, other drivers usually can probe
> > that (and panel data is what xprobe.sh greps from the log for the other
> > drivers).
> I think we're talking past each other. The BIOS doesn't know the size of
> the panel, so I'm asking why you're asking the BIOS which mode to use. It
> sounds like you're saying that it still provides hints at which modes might
> be compatible with the panel, but I'm asking you to confirm that.
> > > That seems reasonable. Note that this now requires a beta freeze exception
> > > to change. Your original changes have now been in the archive for over a
> > > week; have you received any feedback, especially from laptops which were
> > > being detected correctly in the past?
> > Not that I remember, no. But there probably hasn't been that many testers
> > since the ix86 daily-livecd has been oversized all that time ;)
> Eek. All the more reason to be conservative, then.
> > > Right. The problem is only with the vesa driver, but the config change
> > > affects *all* drivers, even those which have been working correctly. It's
> > > those cases we want to avoid changing when we are approaching the release.
> > Yes, I'll make the changes to narrow the impact and ask for a
> > freeze-exception.
> - mdz
> ubuntu-devel mailing list
> ubuntu-devel at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
More information about the ubuntu-devel