On Thu, 2005-09-08 at 10:22 +0200, Sven Luther wrote:
> On Thu, Sep 08, 2005 at 01:52:47AM -0500, Branden Robinson / Debian Project
> Leader wrote:
> > The Debian Sarge release uses a program called "discover1" to discern what
> > hardware is on the system, so I would encourage you to file a bug report
> > against that package describing your problem.
> >
> > Ubuntu and Debian both use the same installer (debian-installer), which in
> > turn uses discover1, so I am not sure why your hardware was detected on one
> > but not the other. Perhaps Ubuntu has made additions to the discover
> > hardware database (in the discover-data package) that they haven't
> > contributed back yet, or which Debian did not get included in the package
> > in time for a sarge release.
debian-installer does not use any version of discover in any way, shape
or form. Perhaps you were thinking of hotplug?
In any case, the maintainer scripts, which you authored originally
(xserver-xorg.{config,postinst}), do call discover if they can. In
Ubuntu's case, they call discover1, which uses the dataset from
discover1-data (as distinct from discover-data, which is only used by
version 2 of discover -- which is not used in either Ubuntu or Debian by
default, to my knowledge). Ubuntu's version of discover1-data has
indeed been pretty heavily augmented to properly deal with new video
cards. But the original database was reasonably solid as regards old
entries, so we haven't really changed anything there.
I think you've sent the submitter chasing a red herring on this one.
> I think from past experience, that this has nothing to do with the installer,
> since the only time the graphic card is of interest is during the xfree86
> configuration, and i have had similar experience with the ati wrapper not
> recognizing my radeon 9200SE cards due to them matching the second head. I
> don't rememebr the bug report about this out of hand, but it is over a year
> old or so, and was never fixed.
>
> It is well possible that a similar detection problem is present in the XFree86
> package, and the fact that it works fine in ubuntu is probably due to them
> using X.org, where this bug is absent.
>
> So, the bug is an xfree86 bug, and thus CCing debian-x.
Yes, Sven is mostly right here.
If you're using a Mach64/atimisc card, then there are no problems with
the ati module handing off properly, despite the similar problems that
continue to plague Radeon/radeon users with the ati module being forced
upon them.
Likely, the problem stems from myriad other problems with the X
configuration that have been fixed in Ubuntu, to the point where it is
extremely rare to see a site with custom X configurations for Ubuntu,
because it almost always works out of the box. I dare suggest that,
with the import of Ubuntu's xorg packages into Debian, that this problem
is resolved within Debian already (also with Otavio Salvador's import of
the Ubuntu 'xresprobe' tool, which does a pretty sterling job of working
things out).
So, in summary:
* not discover1, nor discover(1)-data;
* not the ati wrapper in the XFree86/Xorg DDX, problematic though it
is;
* but the configuration from the server's maintainer scripts.
Hope that helps,
Daniel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
