Menu
▾
▴
linux-fbdev-users — Generic mailing list for users of frame buffers
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(8) |
Nov
(9) |
Dec
(3) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(12) |
Feb
(10) |
Mar
|
Apr
(5) |
May
(3) |
Jun
|
Jul
(5) |
Aug
(7) |
Sep
(15) |
Oct
(4) |
Nov
(3) |
Dec
(7) |
| 2003 |
Jan
(5) |
Feb
(30) |
Mar
(5) |
Apr
(13) |
May
(12) |
Jun
(11) |
Jul
(1) |
Aug
(7) |
Sep
(2) |
Oct
|
Nov
(2) |
Dec
(7) |
| 2004 |
Jan
(4) |
Feb
(9) |
Mar
(16) |
Apr
(42) |
May
(5) |
Jun
(11) |
Jul
(3) |
Aug
(39) |
Sep
(5) |
Oct
(32) |
Nov
(27) |
Dec
|
| 2005 |
Jan
(11) |
Feb
(8) |
Mar
(22) |
Apr
(26) |
May
(9) |
Jun
(10) |
Jul
(7) |
Aug
(43) |
Sep
(23) |
Oct
(18) |
Nov
(15) |
Dec
(15) |
| 2006 |
Jan
(7) |
Feb
(16) |
Mar
(10) |
Apr
(1) |
May
(16) |
Jun
(8) |
Jul
(3) |
Aug
(35) |
Sep
(7) |
Oct
(4) |
Nov
(5) |
Dec
(1) |
| 2007 |
Jan
(2) |
Feb
(30) |
Mar
(6) |
Apr
(7) |
May
(5) |
Jun
|
Jul
(15) |
Aug
(12) |
Sep
(22) |
Oct
(48) |
Nov
(9) |
Dec
(7) |
| 2008 |
Jan
(3) |
Feb
(1) |
Mar
(1) |
Apr
|
May
(4) |
Jun
(1) |
Jul
(5) |
Aug
(4) |
Sep
(4) |
Oct
(2) |
Nov
(5) |
Dec
(1) |
| 2009 |
Jan
(3) |
Feb
|
Mar
|
Apr
(4) |
May
(2) |
Jun
(2) |
Jul
|
Aug
(1) |
Sep
(3) |
Oct
(2) |
Nov
(2) |
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
|
From: <sn...@ut...> - 2006-01-08 13:55:37
|
Hi I've been given an assignement to write the fb driver to S3 Tio 64 PCI card, which should work under linux kernel 2.6. I read the basic concepts about fb drivers but haven't found any clues an tutorials how to start writing the code and how to test it. I'm also not very familiar with compiling kernel from source and adding moules to kernel. Has anyone already written some code for this piece or does a fb driver already exist for this device under 2.6 or previous linux kernel versions? All hints are welcome :) |
|
From: <lyn...@fr...> - 2005-12-15 19:24:24
|
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 |
|
From: RHG <rom...@st...> - 2005-12-15 19:19:38
|
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 |
|
From: Antonino A. D. <ad...@gm...> - 2005-12-15 11:36:17
|
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 |
|
From: Andrew H. <a....@ca...> - 2005-12-15 11:04:15
|
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 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 0000:00:14.0[A] -> Link [LNKB] -> GSI 10 (level, low) -> IRQ 10 radeonfb (0000:00:14.0): Found 0k of SDRAM 64 bits wide videoram radeonfb (0000:00:14.0): found 0Kb video memory ACPI: PCI interrupt for device 0000:00:14.0 disabled radeonfb: probe of 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 > |
|
From: Ville <sy...@sc...> - 2005-12-15 10:29:50
|
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/ |
|
From: Antonino A. D. <ad...@gm...> - 2005-12-13 15:41:44
|
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 |
|
From: <lyn...@fr...> - 2005-12-13 10:37:36
|
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 |
|
From: Andrew H. <a....@ca...> - 2005-12-12 16:08:51
|
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. |
|
From: Miernik <mi...@ff...> - 2005-12-12 08:18:04
|
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 |
|
From: Antonino A. D. <ad...@gm...> - 2005-12-12 01:58:06
|
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 |
|
From: Miernik <mi...@ff...> - 2005-12-12 01:51:17
|
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 |
|
From: Antonino A. D. <ad...@gm...> - 2005-12-12 01:32:41
|
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 |
|
From: Miernik <mi...@ff...> - 2005-12-12 01:21:08
|
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
|
|
From: Miernik <mi...@ff...> - 2005-12-12 01:03:15
|
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
|
|
From: Miernik <mi...@ff...> - 2005-12-04 05:26:38
|
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 |
|
From: Ville <sy...@sc...> - 2005-11-23 17:38:51
|
On Wed, Nov 23, 2005 at 06:14:20PM +0100, Miernik wrote: > Antonino A. Daplas <ad...@gm...> wrote: > > Also, make sure that CONFIG_FB_ATY_XL_INIT is set to n. >=20 > It's a standard Debian sid kernel: >=20 > czernica:~$ cat /boot/config-2.6.14-2-686 | grep FB_ATY > CONFIG_FB_ATY128=3Dm > CONFIG_FB_ATY=3Dm > CONFIG_FB_ATY_CT=3Dy > CONFIG_FB_ATY_GENERIC_LCD=3Dy > CONFIG_FB_ATY_XL_INIT=3Dy > CONFIG_FB_ATY_GX=3Dy > czernica:~$ >=20 > So I guess I need to recompile? > If this option is broken, maybe set it by default to n? The default is 'n' but whoever configured the debian kernel enabled it. Can we at least mark it BROKEN? --=20 Ville Syrj=E4l=E4 sy...@sc... http://www.sci.fi/~syrjala/ |
|
From: Antonino A. D. <ad...@gm...> - 2005-11-23 17:32:05
|
Miernik wrote: > Antonino A. Daplas <ad...@gm...> wrote: >> Also, make sure that CONFIG_FB_ATY_XL_INIT is set to n. > > It's a standard Debian sid kernel: > > czernica:~$ cat /boot/config-2.6.14-2-686 | grep FB_ATY > CONFIG_FB_ATY128=m > CONFIG_FB_ATY=m > CONFIG_FB_ATY_CT=y > CONFIG_FB_ATY_GENERIC_LCD=y > CONFIG_FB_ATY_XL_INIT=y > CONFIG_FB_ATY_GX=y > czernica:~$ > > So I guess I need to recompile? Yes. > 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. Tony |
|
From: Miernik <mi...@ff...> - 2005-11-23 17:20:02
|
Antonino A. Daplas <ad...@gm...> wrote: > Also, make sure that CONFIG_FB_ATY_XL_INIT is set to n. It's a standard Debian sid kernel: czernica:~$ cat /boot/config-2.6.14-2-686 | grep FB_ATY CONFIG_FB_ATY128=m CONFIG_FB_ATY=m CONFIG_FB_ATY_CT=y CONFIG_FB_ATY_GENERIC_LCD=y CONFIG_FB_ATY_XL_INIT=y CONFIG_FB_ATY_GX=y czernica:~$ So I guess I need to recompile? If this option is broken, maybe set it by default to n? -- 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 |
|
From: Miernik <mi...@ff...> - 2005-11-23 17:11:44
|
Ville Syrjälä <sy...@sc...> wrote: > On Sat, Nov 19, 2005 at 06:19:24PM +0100, Miernik wrote: >> I have a HP t5500 system with a Transmeta Crusoe TM5800 CPU and a video >> chip ATI Mach64GM >> >> (--) 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 62.688 MHz; Refresh rate code 1. > > Hmm, one more board with 32bit memory and the BIOS uses a slow XCLK. > > Try 'modprobe atyfb xclk=63' Doesn't help, also total hang. > What exactly is printed on your board's memory chip(s)? +-----------------+ | 0412 3-2 | | MT 48LC2M32B2 | | TG -6 F | +-----------------+ -- 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 |
|
From: Antonino A. D. <ad...@gm...> - 2005-11-23 16:02:45
|
Miernik wrote: > I have a HP t5500 system with a Transmeta Crusoe TM5800 CPU and a video > chip ATI Mach64GM > > lspci says: > > 0000:00:0d.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27) > > > on the chip it says: > > ATI > RAGE XL > 215R3LASB41 > DE5541.00 > 0340AA > TAIWAN > > Also, make sure that CONFIG_FB_ATY_XL_INIT is set to n. Tony If no one is going to update this option, it might just be safer to remove it from atyfb. Tony |
|
From: Ville <sy...@sc...> - 2005-11-23 13:01:38
|
On Sat, Nov 19, 2005 at 06:19:24PM +0100, Miernik wrote: > I have a HP t5500 system with a Transmeta Crusoe TM5800 CPU and a video > chip ATI Mach64GM >=20 > (--) 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 62.688 MHz; Refresh rate code 1. Hmm, one more board with 32bit memory and the BIOS uses a slow XCLK. Try 'modprobe atyfb xclk=3D63' What exactly is printed on your board's memory chip(s)? I'm wondering if we should always cut the XCLK in half when we see a=20 board with 32bit memory. The only counter example are my own XL boards=20 that seemed perfectly happy with 125MHz XCLK. The memory chip is a 7 ns=20 part so it should go up to 143 MHz. Of course there is the possibility=20 that the chip does two memory accesses per XCLK with 32bit memory and I=20 was just lucky in overclocking my memory to 250 MHz :) I'll have to=20 check what XCLK the BIOS uses on my boards... --=20 Ville Syrj=E4l=E4 sy...@sc... http://www.sci.fi/~syrjala/ |
|
From: Miernik <mi...@ff...> - 2005-11-23 11:31:44
|
I have a HP t5500 system with a Transmeta Crusoe TM5800 CPU and a video
chip ATI Mach64GM
lspci says:
0000:00:0d.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
on the chip it says:
ATI
RAGE XL
215R3LASB41
DE5541.00
0340AA
TAIWAN
My kernel is a 2.6.12 from Debian.
Doing "modprobe atyfb" completely hangs the system, keyboard doesn't
work, Ctrl+Alt+Del doesn't work, Caps Lock doesn't work, only switching
off the power works.
When running X /var/log/Xorg.0.log says:
(II) Primary Device is: PCI 00:0d:0
(II) ATI: Candidate "Device" section "ATI Technologies, Inc. Rage XL".
(II) ATI: Shared PCI/AGP Mach64 in slot 0:13:0 detected.
(II) ATI: Shared PCI/AGP Mach64 in slot 0:13:0 assigned to active "Device" section "ATI Technologies, Inc. Rage XL".
and later:
(II) Setting vga for screen 0.
(==) ATI(0): Chipset: "ati".
(**) ATI(0): Depth 24, (--) framebuffer bpp 32
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Reloading /usr/X11R6/lib/modules/linux/libint10.a
(II) ATI(0): Primary V_BIOS segment is: 0xc000
(WW) System lacks support for changing MTRRs
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Reloading /usr/X11R6/lib/modules/libddc.a
(II) Loading sub module "vbe"
(II) LoadModule: "vbe"
(II) Reloading /usr/X11R6/lib/modules/libvbe.a
(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 62.688 MHz; Refresh rate code 1.
(--) ATI(0): Internal programmable clock generator detected.
(--) ATI(0): Reference clock 29.500 MHz.
(II) ATI(0): Generic Monitor: Using default hsync range of 30.00-94.00 kHz
(II) ATI(0): Generic Monitor: Using default vrefresh range of 48.00-85.00 Hz
(II) ATI(0): Maximum clock: 125.00 MHz
What can I do to make framebuffer work on it?
I mean the dedicated framebuffer driver, vesafb works, but that won't
give me accelerated DirectFB.
Anyone had this chipset working? If so, what kernel?
--
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
|
|
From: Komal S. <kom...@ya...> - 2005-11-16 09:53:28
|
--- Ri...@so... wrote: > > Hi all, > > I am trying to understand frame buffer driver for Linux. Where can I > get > information about starting it. Also How frame buffer console is > structured and works. Is there any book available for the same. > Also I am new to VGA Controllers. Where can I get information about > the > terminologies used like pallete, pan, etc. linux/Documentation/fb ---Komal Shah http://komalshah.blogspot.com/ __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com |
|
From: <Ri...@so...> - 2005-11-16 08:34:21
|
Hi all, I am trying to understand frame buffer driver for Linux. Where can I get information about starting it. Also How frame buffer console is structured and works. Is there any book available for the same.=0D Also I am new to VGA Controllers. Where can I get information about the terminologies used like pallete, pan, etc. Rishabh Kumar Goel The information contained in this e-mail message and in any annexure is confidential to the recipient and may contain privileged information. If= you are not the intended recipient, please notify the sender and delete the message= along with any annexure. You should not disclose, copy or otherwise use the= information contained in the message or any annexure. Any views expressed in this e-mail are= those of the individual sender except where the sender specifically states them to be= the views of SoCrates Software India Pvt Ltd., Bangalore. |
6 messages has been excluded from this view by a project administrator.
