lkml.org 
[lkml]   [2003]   [Jan]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: radeonfb almost there.. but not quite! :)
From
Date
On Fri, 2003-01-17 at 16:01, James Simmons wrote:
> > This is on an IBM Thinkpad A30p with 1600x1200 local display.
> > > radeonfb_pci_register BEGIN
> > > radeonfb: ref_clk=2700, ref_div=60, xclk=16600 from BIOS
> > > radeonfb: probed DDR SGRAM 32768k videoram
> > > radeon_get_moninfo: bios 4 scratch = 1000004
> > > radeonfb: panel ID string: 1600x1200
> > > radeonfb: detected DFP panel size from BIOS: 1600x1200
> > > radeonfb: ATI Radeon M6 LY DDR SGRAM 32 MB
> > > radeonfb: DVI port LCD monitor connected
> > > radeonfb: CRT port no monitor connected
> > > radeonfb_pci_register END
> >
> > Do you have CONFIG_DRM=y ?
> >
> > I'd _really_ like to have some feedback from James Simmons on this.
>
> I'm here. I see the radeon fbdev driver is detected and it works :-) The
> issue is a X conflict. Does disabling CONFIG_DRM work?
>
Doesn't solve my problem. To tell you the truth I already use CONFIG_DRM=n
for a while now considering it keeps me from switching from console to X
(either in 2.4 or 2.5). It just locks hard if I do so.

Anyway, it can't be an X conflict, as far as I'm concerned because the
problems happen on the framebuffer console, not X related. Please refer
to my first email, which I sent to you directly and to this list, for
details.

And thanks for your reply.

../Paulo

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:32    [W:0.069 / U:2.616 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site