Re: Radeon 9000 Pro and Framebuffer

[Jan Tammen <jan.tammen@ewido.net>]

Elimar Riesebieter schrob:

> > 127MB HIGHMEM available.
> > 896MB LOWMEM available.
> I'm not shure, but there is a similar higmem-bug in radeonfb as in
> vesafb. Try booting with mem=845M or something like that.

Ah, well, this seemed to be the problem. Now I got still some other 
annoying problem:

In my lilo.conf I got now: append="mem=840M video=radeonfb:1280x1024@60"

My display (17" TFT) is capable of this resolution but when I boot now, 
I get a blank screen and a "Out of range"-message on my OSD. I can then
log in "blindly" and use 

$ fbset 1280x1024-60

to set the display to the wanted resolution. Anyone knows why the 
resolution cannot be set on system boot (I can use e.g. 1024x768, but 
that's not what my display is made for)?

dmesg says:

Kernel command line: BOOT_IMAGE=Debian ro root=302 mem=840M video=radeonfb:1280x1024@60
[...]
radeonfb_pci_register BEGIN
radeonfb: ref_clk=2700, ref_div=12, xclk=20000 from BIOS
radeonfb: probed DDR SGRAM 131072k videoram
radeon_get_moninfo: bios 4 scratch = 2000002
radeonfb: ATI Radeon 9000 If DDR SGRAM 128 MB
radeonfb: DVI port no monitor connected
radeonfb: CRT port CRT monitor connected
radeonfb_pci_register END
hStart = 1296, hEnd = 1512, hTotal = 1568
vStart = 1025, vEnd = 1037, vTotal = 1165
h_total_disp = 0x9f00c3    hsync_strt_wid = 0x9b051a
v_total_disp = 0x3ff048c   vsync_strt_wid = 0x8c0400
post div = 0x4
fb_div = 0x8e
ppll_div_3 = 0x2008e
ron = 1136, roff = 17948
vclk_freq = 7988, per = 641
Console: switching to colour frame buffer device 160x64

Thanks again.