Subject: Re: XFree86 4.1 problem
From: Iain Stevenson (iain@iainstevenson.com)
Date: Sun Sep 09 2001 - 14:57:10 MDT
... just a thought - are you sure it's using the same XF86Config as before?
When YDL2 boots it calls Xautoconfig4 - thus overwriting any changes you may
have entered into the configuration.
Iain
on 9/9/01 2:55 am, Paul J. Lucas at pauljlucas@mac.com wrote:
> So I compiled XFree86 4.1 myself. When I tried to run it on my
> Lombard Powerbook (using the same config file that worked fine
> for 4.0.2 that comes with YDL 2.0), it dies complaining as
> attached. Any ideas?
>
> - Paul
>
> (==) ATI(0): Chipset: "ati".
> (**) ATI(0): Depth 24, (--) framebuffer bpp 32
> (--) ATI(0): ATI 3D Rage LT Pro graphics controller detected.
> (--) ATI(0): Chip type 4C49 "LI", version 4, foundry UMC, class 0, revision
> 0x03.
> (--) ATI(0): PCI bus interface detected; block I/O base is 0x0000.
> (--) ATI(0): ATI Mach64 adapter detected.
> (--) ATI(0): Internal RAMDAC (subtype 1) detected.
> (==) ATI(0): RGB weight 888
> (==) ATI(0): Default visual is TrueColor
> (**) ATI(0): Using gamma correction (1.1, 1.1, 1.1)
> (II) ATI(0): Using Mach64 accelerator CRTC.
> (--) ATI(0): 1024x768 panel (ID 0) detected.
> (--) ATI(0): Panel clock is 31.500 MHz.
> (II) ATI(0): Using digital flat panel interface.
> (II) ATI(0): Storing hardware cursor image at 0x817FFC00.
> (II) ATI(0): Using 8 MB linear aperture at 0x81800000.
> (!!) 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 0x80881400.
> (II) ATI(0): Using Block 1 MMIO aperture at 0x80881000.
> (II) ATI(0): MMIO write caching enabled.
> (--) ATI(0): 8192 kB of SDRAM (1:1) detected (using 8191 kB).
> (WW) ATI(0): Cannot shadow an accelerated frame buffer.
> (--) ATI(0): Internal programmable clock generator detected.
> (--) ATI(0): Reference clock 157.5/11 (14.318) MHz.
> (II) ATI(0): Maximum clock: 96.00 MHz
> (II) ATI(0): Not using mode "1024x768" (hsync out of range)
> (II) ATI(0): Not using built-in mode "Native panel mode" (hsync out of range)
> (WW) ATI(0): Mode pool is empty
> (II) UnloadModule: "ati"
> (II) UnloadModule: "atimisc"
> (II) Unloading /usr/local/X11R6/lib/modules/drivers/atimisc_drv.o
> (EE) Screen(s) found, but none have a usable configuration.
>
> Fatal server error:
> no screens found
This archive was generated by hypermail 2a24 : Sun Sep 09 2001 - 14:10:28 MDT