[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: r128 driver still borked in XF4.0.1-9pre10



On Wed, Dec 06, 2000 at 05:11:50PM +0100, Michel Dänzer wrote:
> Michael Flaig wrote:
> 
> > I´ve got the Problem: "no screens found" where can I get the working
> > packages ?
> 
> "no screens found" is not a problem, it's the last error message of the server
> which can be caused by a zillion problems. We can't tell what the actual
> problem is without more information.
Hm ... OK ... 
> 
> 
> Anyway, I had to learn the hard way last night that 4.0.1-8 doesn't work on my
> Pismo either (the infamous cannot read V_BIOS), which version should the patch
> for that be in?
I've the same Problem. I think it is the same ...

(II) R128(0): PCI bus 0 card 16 func 0
(**) R128(0): Depth 16, (--) framebuffer bpp 16
(II) R128(0): Pixel depth = 16 bits stored in 2 bytes (16 bpp pixmaps)
(==) R128(0): Default visual is TrueColor
(==) R128(0): RGB weight 565
(II) R128(0): Using 6 bits per RGB (8 bit DAC)
(II) R128(0): initializing int10
(EE) R128(0): Cannot read V_BIOS (4)
(--) R128(0): Chipset: "ATI Rage 128 Mobility LF (AGP)" (ChipID = 0x4c46)
(--) R128(0): Linear framebuffer at 0xa4000000
(--) R128(0): MMIO registers at 0xa0000000
(--) R128(0): BIOS at 0xa0020000
(--) R128(0): VideoRAM: 8192 kByte (128-bit SDR SGRAM 1:1)
(II) R128(0): Using flat panel for display
(WW) R128(0): Video BIOS not detected in PCI space!
(WW) R128(0): Attempting to read Video BIOS from legacy ISA space!
(WW) R128(0): Video BIOS not found!
(II) R128(0): PLL parameters: rf=9216 rd=33153 min=142346240 max=1639687683; xclk=50047
(II) R128(0): initializing int10
(EE) R128(0): Cannot read V_BIOS (4)
(II) Unloading /usr/X11R6/lib/modules/libvgahw.a
(EE) Screen(s) found, but none have a usable configuration.

Greets,

mfl

> 
> 
> Michel
> 
> 
> -- 
> Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
> Debian GNU/Linux (powerpc,i386) user \   member of XFree86 and the DRI project

-- 
Michael Flaig ... PROLinux



Reply to: