[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#255439: d-i report



Hola,


On Thu, Jul 08, 2004 at 04:09:46PM -0500, Branden Robinson wrote:
>
> The XFree86 X server used the driver it was told to use.
>
> There are only two ways you can tell the XFree86 X server which driver to
> use in the d-i environment:
>
> 1) Answer a debconf question.
> 2) Have the question pre-answered by discover.
Actually, the question was answered by discover (from config script):

mob:/# /sbin/discover --disable=serial,parallel --format="%V %M\t%S\t%D\n" video
ATI Technologies, Inc. Radeon Mobility U1       XFree86 radeon

>
> Consequently, this looks like a discover-data bug to me.
Well, it seems to me that it is not.

>
> Reassigning.
>
> Discover-data maintainers,
>
> If discover-data doesn't actually report "apm" as the XFree86 4.x X server
> driver for the ATI Radeon Mobility U1 (that's "Class 0300: 1002:4336"),
> then this must have been user error.
>
What puzzled me is that the user answered *yes* to autodetection...

In /var/cache/debconf/config.dat:

[snip]
Name: xserver-xfree86/autodetect_video_card
Template: xserver-xfree86/autodetect_video_card
Value: true
Owners: xserver-xfree86
Flags: seen

Name: xserver-xfree86/config/device/bus_id
Template: xserver-xfree86/config/device/bus_id
Owners: xserver-xfree86

Name: xserver-xfree86/config/device/bus_id_error
Template: xserver-xfree86/config/device/bus_id_error
Owners: xserver-xfree86

Name: xserver-xfree86/config/device/driver
Template: xserver-xfree86/config/device/driver
Value: apm
Owners: xserver-xfree86
Variables:
 choices = apm, ark, ati, chips, cirrus, cyrix, fbdev, glide, glint, i128, i740, i810,
+imstt, mga, neomagic, newport, nsc, nv, rendition, s3, s3virge, savage, siliconmotion,
+sis, tdfx, tga, trident, tseng, vesa, vga, via, vmware

Name: xserver-xfree86/config/device/identifier
Template: xserver-xfree86/config/device/identifier
Value: ATI Technologies, Inc. Radeon Mobility U1
Owners: xserver-xfree86
[snip]

Anyway, the radeon driver has a different treatment in the config script, doesn't it?

Anything you think could help?
I can reproduce the error any time you like. 
If you think it is worth, for sure.
Maybe is there a log somewhere?

-- 
[]'                  | Google is my friend.
Cristian Escalante   | Well, usually...



Reply to: