Re: Bug#255439: Bug#255689: Bug#255439: d-i report
On Thu, Aug 19, 2004 at 11:59:49AM -0500, Branden Robinson wrote:
> On Wed, Aug 18, 2004 at 08:41:52AM +0200, Sven Luther wrote:
> > On Tue, Aug 17, 2004 at 07:31:23PM -0700, Daniel Stone wrote:
> > > On Tue, Jul 13, 2004 at 11:08:58AM -0500, Branden Robinson wrote:
> > > > There's the problem. "radeon" is not a legal value.
> > > >
> > > > Use "ati" instead.
> > > >
> > > > Do not use "atimisc", "r128", or "radeon".
> > >
> > > 'radeon' should be perfectly legal, and just sedded to 'ati' in the
> > > XFree86 scripts if they really want to enforce this whole 'only ever use
> > > the wrapper' thingo.
> > Problem seems to be that the ati wrapper has some troubles for some of the
> > Radoen 9200 cards, and doesn't load the radeon module appropriately in these
> > cases.
> That sounds like a bug.
> > I will recheck with both my 5961 and 5964 cards again and confirm this.
> Okay. Please do, and file a bug if you can still reproduce the problem.
Am checking with the 5964 (Radeon 9200 SE) right now on a cleanly installed
d-i install without any of the extra tasksel desktop stuff. A first few comments :
1) i still get proposed a macintosh keyboard by default. i need an pc105
one. Maybe it would be possible to check the subarch, if it is a pmac, then
propose macintosh, if not, then propose pcXXX stuff.
2) it proposed me the us keyboard. Maybe this could be taken from the chosen
language used for the console and found in the debconf database ?
3) it is not possible to propose an empty monitor lines. I have a DVI
connected LCD flat panel, and comenting out the monitor frequencies works
Ok, apart from that, the 9200 SE (5964) worked fine, will check the pure 9200
(5961) later and report back.
That said, killing X from the console messes up the console, but this is
probably a kernel issue, or a radeonfb<->X radeon driver interaction.