linux-fbdev-users Mailing List for Linux Frame Buffer Device Development

Thanks Tony.
It seems I'm wanting too much out of my machine. I might go into it when I
have more spare time.
Till then
Lynx

Thanks Tony.
It seems I'm wanting too much out of my machine. I might go into it when I
have more spare time.
Till then
Lynx

Andrew Hill wrote:
> Ville et al.
> 
> Many thanks for that, it looks promising; I'll have a
> play around and see what gives.
> 
> Can anyone give me a clue as to how to get the radeonfb
> module to recognise the video memory without first
> starting x on the card. I'm assuming that something's
> not been fully initiated so I'm having a hunt around
> X11R6.8.2-src\xc\programs\Xserver\hw\xfree86\drivers\ati
> but no luck as yet. Are there any BIOS settings that
> might be worth a tweak?
If this is not the primary card, you need to POST it.
Try vbetool.
http://www.srcf.ucam.org/~mjg59/vbetool/
Tony

Ville et al.
Many thanks for that, it looks promising; I'll have a
play around and see what gives.
Can anyone give me a clue as to how to get the radeonfb
module to recognise the video memory without first
starting x on the card. I'm assuming that something's
not been fully initiated so I'm having a hunt around
X11R6.8.2-src\xc\programs\Xserver\hw\xfree86\drivers\ati
but no luck as yet. Are there any BIOS settings that
might be worth a tweak?
It's a CGA-9258PYVD (so an RV280) PCI card with 128Mb
that I'm trying to get working on a VIA Mini-itx board.
dmesg said:
radeonfb_pci_register BEGIN
PCI: Enabling device .&checktime(0000,00,14,':').0 (0000 -> 0003)
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10
PCI: setting IRQ 10 as level-triggered
ACPI: PCI Interrupt .&checktime(0000,00,14,':').0[A] -> Link [LNKB] -> GSI 10 (level, 
low) -> IRQ 10
radeonfb (.&checktime(0000,00,14,':').0): Found 0k of SDRAM 64 bits wide videoram
radeonfb (.&checktime(0000,00,14,':').0): found 0Kb video memory
ACPI: PCI interrupt for device .&checktime(0000,00,14,':').0 disabled
radeonfb: probe of .&checktime(0000,00,14,':').0 failed with error -5
Regards,
 Andy.
Ville Syrjälä wrote:
> On Mon, Dec 12, 2005 at 04:08:00PM +0000, Andrew Hill wrote:
> 
>>Hi,
>>
>>Sorry if this is a noob boob, but are there any patches
>>that will add FBIO_WAITFORVSYNC functionality to ioctl
>>in radeon_base.c?
> 
> 
> http://thread.gmane.org/gmane.linux.fbdev.devel/6462
> 

On Mon, Dec 12, 2005 at 04:08:00PM +0000, Andrew Hill wrote:
> Hi,
>=20
> Sorry if this is a noob boob, but are there any patches
> that will add FBIO_WAITFORVSYNC functionality to ioctl
> in radeon_base.c?
http://thread.gmane.org/gmane.linux.fbdev.devel/6462
--=20
Ville Syrj=E4l=E4
sy...@sc...
http://www.sci.fi/~syrjala/

lyn...@fr... wrote:
> Hallo!
> 
> 
> I would like to get my external TFT-monitor connected to my laptop to use a
> full 1280x1024 resolution, at least when the laptop monitor is off. I posted
> my problem before
> (http://sourceforge.net/mailarchive/forum.php?thread_id=8971327&forum_id=2358)
> but didn't get any replies yet, so I fear nobody has an idea, and I have to
> change the panel-probing in the radeonfb-driver to force it to 1280 and see
> what it does. What would I have to change? What variable stores the resolution
> that is actually taken for displaying?
> So far I also tried vesafb-tng but that needs VBE3 (I have VBE2, and it seems
> one cannot change that) to be able to change to 1280x1024.
> 
> Any help and hint appreciated also replies telling me it is not possible at
> any means.
Will forward your message to the radeonfb maintainer.
Tony

Hallo!
I would like to get my external TFT-monitor connected to my laptop to use a
full 1280x1024 resolution, at least when the laptop monitor is off. I posted
my problem before
(http://sourceforge.net/mailarchive/forum.php?thread_id=8971327&forum_id=2358)
but didn't get any replies yet, so I fear nobody has an idea, and I have to
change the panel-probing in the radeonfb-driver to force it to 1280 and see
what it does. What would I have to change? What variable stores the resolution
that is actually taken for displaying?
So far I also tried vesafb-tng but that needs VBE3 (I have VBE2, and it seems
one cannot change that) to be able to change to 1280x1024.
Any help and hint appreciated also replies telling me it is not possible at
any means.
Thanks a lot
Lynx

Hi,
Sorry if this is a noob boob, but are there any patches
that will add FBIO_WAITFORVSYNC functionality to ioctl
in radeon_base.c?
I'm hoping to use the framebuffer in an embedded pc and
need as much mapped video ram as possible with the
ability to pan on a vsync. Would I be better off looking
at another manufacturer? It seemed that the Radeons give
a good Mb per buck ratio.
I got myself a 9250 128Mb PCI and so far found that I
can map all the memory to user space; but only after
I've started X on the device first and then closed it
down again. Otherwise I get "Found 0k...videoram" in
dmesg?
Any advice would be greatly appreciated?
Cheers, Andy.

Antonino A. Daplas <ad...@gm...> wrote:
> Miernik wrote:
>> Antonino A. Daplas <ad...@gm...> wrote:
>>> Miernik wrote:
>>>> (II) ATI(0): Maximum clock: 123.00 MHz
>>> Your mode requires 162Mhz but the driver limits the clock to 123 Mhz.
>>> I don't have an ATI card, but perhaps this maximum clock can be
>>> overridden?
> But if the framebuffer driver can do 162 MHz, then there must be a way
> to make Xorg use that too...
Changing DefaultDepth from 24 to 16 fixed the problem. Now it shows:
(II) ATI(0): Maximum clock: 230.00 MHz
For framebuffer I use 8 bit color.
Besides that setting "DACSpeed 210" in the Device section does not have
any effect. xorg.conf(5) says that it should override max clock.
-- 
Miernik _________________________ xmpp:mi...@am...
___________________/_______________________/ mailto:mi...@ff...
Protect Europe from a legal disaster. Petition against software patents
http://www.noepatents.org/index_html?LANG=en

Miernik wrote:
> Antonino A. Daplas <ad...@gm...> wrote:
>> Miernik wrote:
>>> (II) ATI(0): Maximum clock: 123.00 MHz
>> Your mode requires 162Mhz but the driver limits the clock to 123 Mhz.
>> I don't have an ATI card, but perhaps this maximum clock can be
>> overridden?
> 
> But up here the log says my max clock is 210 MHz:
> 
> (II) ATI(0): Supported additional Video Mode:
> (II) ATI(0): clock: 162.0 MHz Image Size: 408 x 306 mm
> (II) ATI(0): h_active: 1600 h_sync: 1664 h_sync_end 1856 h_blank_end 2160 h_border: 0
> (II) ATI(0): v_active: 1200 v_sync: 1201 v_sync_end 1204 v_blanking: 1250 v_border: 0
> (II) ATI(0): Ranges: V min: 48 V max: 85 Hz, H min: 30 H max: 94 kHz, PixClock max 210 MHz
> 
> What is trying to limit it to 123 MHz, the card or the monitor or just
> some buggy software driver?
> 
The 210 Mhz is the maximum dotclock supported by the monitor, the 123 Mhz is
the graphics adapter's maximum (or that's what the driver thinks). So
the driver will use the lesser of the two.
But if the framebuffer driver can do 162 MHz, then there must be a way
to make Xorg use that too...
Tony

Antonino A. Daplas <ad...@gm...> wrote:
> Miernik wrote:
>> (II) ATI(0): Maximum clock: 123.00 MHz
> 
> Your mode requires 162Mhz but the driver limits the clock to 123 Mhz.
> I don't have an ATI card, but perhaps this maximum clock can be
> overridden?
But up here the log says my max clock is 210 MHz:
(II) ATI(0): Supported additional Video Mode:
(II) ATI(0): clock: 162.0 MHz Image Size: 408 x 306 mm
(II) ATI(0): h_active: 1600 h_sync: 1664 h_sync_end 1856 h_blank_end 2160 h_border: 0
(II) ATI(0): v_active: 1200 v_sync: 1201 v_sync_end 1204 v_blanking: 1250 v_border: 0
(II) ATI(0): Ranges: V min: 48 V max: 85 Hz, H min: 30 H max: 94 kHz, PixClock max 210 MHz
What is trying to limit it to 123 MHz, the card or the monitor or just
some buggy software driver?
-- 
Miernik _________________________ xmpp:mi...@am...
___________________/_______________________/ mailto:mi...@ff...
Protect Europe from a legal disaster. Petition against software patents
http://www.noepatents.org/index_html?LANG=en

Miernik wrote:
> (II) ATI(0): Maximum clock: 123.00 MHz
Your mode requires 162Mhz but the driver limits the clock to 123 Mhz.
I don't have an ATI card, but perhaps this maximum clock can be
overridden?
Tony

Miernik <mi...@ff...> wrote:
> With framebuffer console I get the full resolution, like this:
> 
> czernica:~$ /usr/sbin/fbset
> 
> mode "1600x1200-60"
> # D: 162.022 MHz, H: 75.010 kHz, V: 60.008 Hz
> geometry 1600 1200 1600 5232 8
> timings 6172 304 64 46 1 192 3
> hsync high
> vsync high
> accel true
> rgba 8/0,8/0,8/0,0/0
> endmode
> 
> Can I somehow convert that to a X Modeline, so it uses exactly the same
> mode in X?
Now I found this option and it says:
czernica:~$ /usr/sbin/fbset --xfree86
Mode "1600x1200"
 # D: 162.022 MHz, H: 75.010 kHz, V: 60.008 Hz
 DotClock 162.023
 HTimings 1600 1664 1856 2160
 VTimings 1200 1201 1204 1250
 Flags "+HSync" "+VSync" # Warning: XFree86 doesn't support accel
EndMode
czernica:~$
But it doesn't help at all, I pasted exactly that in my xorg.conf,
deleting all other mode definitions, and it still says "bad mode
clock/interlace/doublescan".
-- 
Miernik _________________________ xmpp:mi...@am...
___________________/_______________________/ mailto:mi...@ff...
 Save Europe from Software Patents
 http://www.gnu.org/philosophy/savingeurope.html

With framebuffer console I get the full resolution, like this:
czernica:~$ /usr/sbin/fbset
mode "1600x1200-60"
 # D: 162.022 MHz, H: 75.010 kHz, V: 60.008 Hz
 geometry 1600 1200 1600 5232 8
 timings 6172 304 64 46 1 192 3
 hsync high
 vsync high
 accel true
 rgba 8/0,8/0,8/0,0/0
endmode
Can I somehow convert that to a X Modeline, so it uses exactly the same
mode in X?
I tried this, but I cannot get X to use it:
,----- relevant part of /etc/X11/xorg.conf --------------------------------------------------
| Section "Device"
| Identifier "Generic Video Card"
| Driver "ati"
| BusID "PCI:0:13:0"
| Option "UseFBDev" "true"
| EndSection
| 
| Section "Monitor"
| Identifier "hp L2035"
| Option "DPMS"
| HorizSync 30-94
| VertRefresh 48-85
| ModeLine "1600x1200a" 162.00 1600 1664 1856 2160 1200 1201 1204 1250
| ModeLine "1600x1200b" 140.00 1600 1632 2024 2052 1200 1200 1208 1216
| ModeLine "1600x1200c" 169.28 1600 1704 1880 2160 1200 1201 1204 1244
| ModeLine "1600x1200d" 173.38 1600 1712 1888 2176 1200 1201 1204 1245
| ModeLine "1600x1200e" 140.00 1600 1632 2024 2052 1200 1200 1208 1216
| EndSection
| 
| Section "Screen"
| Identifier "Default Screen"
| Device "Generic Video Card"
| Monitor "hp L2035"
| DefaultDepth 24
| SubSection "Display"
| Depth 24
| Modes "1600x1200a" "1400x1050"
| EndSubSection
| EndSection
`--------------------------------------------------------------------------------------------
This is what shows in /var/log/Xorg.0.log (ommited irrelevant beginning and end):
(II) ATI(0): VESA BIOS detected
(II) ATI(0): VESA VBE Version 2.0
(II) ATI(0): VESA VBE Total Mem: 8128 kB
(II) ATI(0): VESA VBE OEM: ATI MACH64
(II) ATI(0): VESA VBE OEM Software Rev: 1.0
(II) ATI(0): VESA VBE OEM Vendor: ATI Technologies Inc.
(II) ATI(0): VESA VBE OEM Product: MACH64GM
(II) ATI(0): VESA VBE OEM Product Rev: 01.00
(II) ATI(0): VESA VBE DDC supported
(II) ATI(0): VESA VBE DDC Level 2
(II) ATI(0): VESA VBE DDC transfer in appr. 2 sec.
(II) ATI(0): VESA VBE DDC read successfully
(II) ATI(0): Manufacturer: HWP Model: 2612 Serial#: 16843009
(II) ATI(0): Year: 2005 Week: 4
(II) ATI(0): EDID Version: 1.3
(II) ATI(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V
(II) ATI(0): Sync: Separate Composite SyncOnGreenSerration on. V.Sync Pulse req. if CompSync or SyncOnGreen
(II) ATI(0): Max H-Image Size [cm]: horiz.: 41 vert.: 31
(II) ATI(0): Gamma: 2.20
(II) ATI(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
(II) ATI(0): First detailed timing is preferred mode
(II) ATI(0): redX: 0.638 redY: 0.342 greenX: 0.293 greenY: 0.609
(II) ATI(0): blueX: 0.147 blueY: 0.068 whiteX: 0.313 whiteY: 0.329
(II) ATI(0): Supported VESA Video Modes:
(II) ATI(0): 720x400@70Hz
(II) ATI(0): 640x480@60Hz
(II) ATI(0): 640x480@75Hz
(II) ATI(0): 800x600@60Hz
(II) ATI(0): 800x600@75Hz
(II) ATI(0): 832x624@75Hz
(II) ATI(0): 1024x768@60Hz
(II) ATI(0): 1024x768@70Hz
(II) ATI(0): 1024x768@75Hz
(II) ATI(0): 1280x1024@75Hz
(II) ATI(0): 1152x870@75Hz
(II) ATI(0): Manufacturer's mask: 0
(II) ATI(0): Supported Future Video Modes:
(II) ATI(0): #0: hsize: 640 vsize 480 refresh: 85 vid: 22833
(II) ATI(0): #1: hsize: 800 vsize 600 refresh: 85 vid: 22853
(II) ATI(0): #2: hsize: 1024 vsize 768 refresh: 85 vid: 22881
(II) ATI(0): #3: hsize: 1280 vsize 960 refresh: 60 vid: 16513
(II) ATI(0): #4: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
(II) ATI(0): #5: hsize: 1280 vsize 1024 refresh: 85 vid: 39297
(II) ATI(0): #6: hsize: 1600 vsize 1200 refresh: 60 vid: 16553
(II) ATI(0): #7: hsize: 1600 vsize 1200 refresh: 75 vid: 20393
(II) ATI(0): Supported additional Video Mode:
(II) ATI(0): clock: 162.0 MHz Image Size: 408 x 306 mm
(II) ATI(0): h_active: 1600 h_sync: 1664 h_sync_end 1856 h_blank_end 2160 h_border: 0
(II) ATI(0): v_active: 1200 v_sync: 1201 v_sync_end 1204 v_blanking: 1250 v_border: 0
(II) ATI(0): Ranges: V min: 48 V max: 85 Hz, H min: 30 H max: 94 kHz, PixClock max 210 MHz
(II) ATI(0): Monitor name: hp L2035
(II) ATI(0): Serial No: CNP504Y2ST
(II) ATI(0): BIOS Data: BIOSSize=0x8000, ROMTable=0x0114.
(II) ATI(0): BIOS Data: ClockTable=0x097C, FrequencyTable=0x0956.
(II) ATI(0): BIOS Data: LCDTable=0x0000, LCDPanelInfo=0x0000.
(II) ATI(0): BIOS Data: VideoTable=0x0000, HardwareTable=0x015E.
(II) ATI(0): BIOS Data: I2CType=0x0F, Tuner=0x00, Decoder=0x00, Audio=0x0F.
(--) ATI(0): ATI 3D Rage XL or XC graphics controller detected.
(--) ATI(0): Chip type 4752 "GR", version 7, foundry TSMC, class 0, revision 0x00.
(--) ATI(0): PCI bus interface detected; block I/O base is 0xD000.
(--) ATI(0): ATI Mach64 adapter detected.
(!!) ATI(0): For information on using the multimedia capabilities
 of this adapter, please see http://gatos.sf.net.
(--) ATI(0): Internal RAMDAC (subtype 1) detected.
(==) ATI(0): RGB weight 888
(==) ATI(0): Default visual is TrueColor
(==) ATI(0): Using gamma correction (1.0, 1.0, 1.0)
(II) ATI(0): Using Mach64 accelerator CRTC.
(II) ATI(0): Storing hardware cursor image at 0xE07FFC00.
(II) ATI(0): Using 8 MB linear aperture at 0xE0000000.
(!!) ATI(0): Virtual resolutions will be limited to 8191 kB
 due to linear aperture size and/or placement of hardware cursor image area.
(II) ATI(0): Using Block 0 MMIO aperture at 0xE2100400.
(II) ATI(0): Using Block 1 MMIO aperture at 0xE2100000.
(II) ATI(0): MMIO write caching enabled.
(--) ATI(0): 8192 kB of SGRAM (2:1) 32-bit detected (using 8191 kB).
(WW) ATI(0): Cannot shadow an accelerated frame buffer.
(II) ATI(0): Engine XCLK 61.810 MHz; Refresh rate code 1.
(--) ATI(0): Internal programmable clock generator detected.
(--) ATI(0): Reference clock 29.500 MHz.
(II) ATI(0): hp L2035: Using hsync range of 30.00-94.00 kHz
(II) ATI(0): hp L2035: Using vrefresh range of 48.00-85.00 Hz
(II) ATI(0): Maximum clock: 123.00 MHz
(II) ATI(0): Not using mode "1600x1200a" (bad mode clock/interlace/doublescan)
(II) ATI(0): Not using mode "1600x1200b" (bad mode clock/interlace/doublescan)
(II) ATI(0): Not using mode "1600x1200c" (bad mode clock/interlace/doublescan)
(II) ATI(0): Not using mode "1600x1200d" (bad mode clock/interlace/doublescan)
(II) ATI(0): Not using mode "1600x1200e" (bad mode clock/interlace/doublescan)
(II) ATI(0): Not using default mode "1024x768" (vrefresh out of range)
(II) ATI(0): Not using default mode "512x384" (vrefresh out of range)
(II) ATI(0): Not using default mode "1280x960" (bad mode clock/interlace/doublescan)
(II) ATI(0): Not using default mode "1280x1024" (bad mode clock/interlace/doublescan)
(II) ATI(0): Not using default mode "1280x1024" (bad mode clock/interlace/doublescan)
(II) ATI(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan)
(II) ATI(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan)
(II) ATI(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan)
(II) ATI(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan)
(II) ATI(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan)
(II) ATI(0): Not using default mode "800x600" (hsync out of range)
(II) ATI(0): Not using default mode "1792x1344" (insufficient memory for mode)
(II) ATI(0): Not using default mode "1792x1344" (insufficient memory for mode)
(II) ATI(0): Not using default mode "896x672" (bad mode clock/interlace/doublescan)
(II) ATI(0): Not using default mode "1856x1392" (insufficient memory for mode)
(II) ATI(0): Not using default mode "1856x1392" (insufficient memory for mode)
(II) ATI(0): Not using default mode "928x696" (bad mode clock/interlace/doublescan)
(II) ATI(0): Not using default mode "1920x1440" (insufficient memory for mode)
(II) ATI(0): Not using default mode "1920x1440" (insufficient memory for mode)
(II) ATI(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan)
(II) ATI(0): Not using default mode "1400x1050" (bad mode clock/interlace/doublescan)
(II) ATI(0): Not using default mode "1400x1050" (bad mode clock/interlace/doublescan)
(II) ATI(0): Not using default mode "1400x1050" (bad mode clock/interlace/doublescan)
(II) ATI(0): Not using default mode "1680x1050" (bad mode clock/interlace/doublescan)
(II) ATI(0): Not using default mode "1920x1200" (insufficient memory for mode)
(II) ATI(0): Not using default mode "1920x1200" (insufficient memory for mode)
(II) ATI(0): Not using default mode "1920x1440" (insufficient memory for mode)
(II) ATI(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan)
(II) ATI(0): Not using default mode "2048x1536" (insufficient memory for mode)
(II) ATI(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
(II) ATI(0): Not using default mode "2048x1536" (insufficient memory for mode)
(II) ATI(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
(II) ATI(0): Not using default mode "2048x1536" (insufficient memory for mode)
(II) ATI(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
(II) ATI(0): Not using mode "1600x1200a" (no mode of this name)
(II) ATI(0): Not using default mode "1440x900" (width too large for virtual size)
(--) ATI(0): Virtual size is 1400x1050 (pitch 1408)
(**) ATI(0): *Default mode "1400x1050": 122.0 MHz, 64.9 kHz, 60.0 Hz
(II) ATI(0): Modeline "1400x1050" 122.00 1400 1488 1640 1880 1050 1052 1064 1082 +hsync +vsync
How can I get anything about why it doesn't like my more, more specific
than "bad mode clock/interlace/doublescan"?
-- 
Miernik _________________________ xmpp:mi...@am...
___________________/_______________________/ mailto:mi...@ff...
Protect Europe from a legal disaster. Petition against software patents
http://www.noepatents.org/index_html?LANG=en

Antonino A. Daplas <ad...@gm...> wrote:
>> CONFIG_FB_ATY_XL_INIT=y
>> CONFIG_FB_ATY_GX=y
>> czernica:~$
>> 
>> So I guess I need to recompile?
> 
> Yes.
Changing CONFIG_FB_ATY_XL_INIT to n fixed it, thanks.
>> If this option is broken, maybe set it by default to n?
> 
> It should default to n. But I think it's better to remove it.
Please at least default to n in kernel.org sources and ask debian
maintainer do to it in their .config
-- 
Miernik _________________________ xmpp:mi...@am...
___________________/_______________________/ mailto:mi...@ff...
Why software shouldn't be covered by patents
http://bladeenc.mp3.no/articles/software_patents.html