radeonfb almost there.. but not quite! :)
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 8 lines · Alessandro Suardi
Radeonfb works better for me in 2.5.58, same card but on a
Dell Latitude C640 - 1024x768 though, and xclk=16600.I say "better" and not simply "works" because
- the gpm cursor positioned on characters shows different ones (eg. hovering on a 'd' it shows a highlighted 'B')
This works for me.
Quoted 2 lines
- the pre-penguin display is garbage. The console though gets to recover right after the penguin display
Same here. I see the same garbage when switching resolutions with fbset.
I also have a small problem when switching to and from X. Most of the time everything is fine, but sometimes it is unreadable and I have to switch back and forth again.
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 videoramradeon_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
Quoted 4 lines · Arnd Bergmann
I also have a small problem when switching to and from X. Most of the time everything is fine, but sometimes it is unreadable and I have to switch back and forth again.
Quoted 11 lines
This is on an IBM Thinkpad A30p with 1600x1200 local display.
radeonfb_pci_registerBEGIN
radeonfb: ref_clk=2700, ref_div=60, xclk=16600 from BIOS
radeonfb: probed DDR SGRAM 32768k videoramradeon_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 connectedradeonfb_pci_registerEND
Do you have CONFIG_DRM=y ?
I'd _really_ like to have some feedback from James Simmons on this.
../Paulo
Quoted 1 line · Paulo Andre
Do you have
CONFIG_DRM=y?
Yes:
[drm] AGP 0.99 on Unknown @ 0xd0000000 256MB [drm] Initialized radeon 1.6.0 20020828 on minor 0
Arnd <><
Could you disable it and see if everything works then.
Quoted 15 lines · Paulo Andre
Quoted 2 lines
Do you have
CONFIG_DRM=y?Yes:
[drm] AGP 0.99 on Unknown @0xd0000000256MB [drm] Initialized radeon 1.6.0 20020828 on minor 0Arnd <><-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Quoted 13 lines
Quoted 12 lines
This is on an IBM Thinkpad A30p with 1600x1200 local display.
radeonfb_pci_registerBEGIN
radeonfb: ref_clk=2700, ref_div=60, xclk=16600 from BIOS
radeonfb: probed DDR SGRAM 32768k videoramradeon_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 connectedradeonfb_pci_registerEND
Quoted 3 lines
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?
Quoted 12 lines · James Simmons
Quoted 12 lines
This is on an IBM Thinkpad A30p with 1600x1200 local display.
Quoted 10 lines
radeonfb_pci_registerBEGIN
radeonfb: ref_clk=2700, ref_div=60, xclk=16600 from BIOS
radeonfb: probed DDR SGRAM 32768k videoramradeon_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 connectedradeonfb_pci_registerEND
Quoted 7 lines
Quoted 3 lines
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_DRMwork?
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