Menu
▾
▴
linux-fbdev-users
|
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: 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 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: 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: 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-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/ |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X