atyfb makes the screen black

atyfb makes the screen black

Post by Nico Schotteliu » Sat, 23 Mar 2002 17:50:06


I tried to get a nice fbdev running with my card, but when I load aty_fb
from kernel 2.4.17 or 2.5.6 it just makes my screen black and forces me to
reboot so I can see anything again.
It looks like it is supported in aty/atyfb_base.c, but
Q: Is my card supported ?
Q: Will it ever be supported ?

Here's my lspci output, so you can see what I use...

01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage P/M Mobility AGP        Subsystem: Acer Incorporated [ALI]: Unknown device 1010
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort        Latency: 32 (2000ns min), cache line size 08
        Interrupt: pin A routed to IRQ 11
        Region 0: Memory at 81000000 (32-bit, non-prefetchable) [size=16M]
        Region 1: I/O ports at 8000 [size=256]
        Region 2: Memory at 80600000 (32-bit, non-prefetchable) [size=4K]
        Expansion ROM at 80620000 [disabled] [size=128K]
        Capabilities: [50] AGP version 1.0
                Status: RQ=255 SBA+ 64bit- FW- Rate=x1,x2
                Command: RQ=0 SBA- AGP- 64bit- FW- Rate=<none>
        Capabilities: [5c] Power Management version 1
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

Thanks in advance!


p.s.: hopefully i hit the maintainer (who is not in the MAINTAINERS file)
with this mail...

Nico Schottelius

Please send your messages pgp-signed or pgp-encrypted.
If you don't know what pgp is visit
(public pgp key:

< 1K Download

1. ati mach64vt, atyfb.c, fbcon and black screens

i'm running 2.4.3, and attempting to use the ati mach64 framebuffer
driver (atyfb.c) in place of the slooow vesa fb.  my card is an ati
mach64 vt4 according to lspci, claimed in atyfb.c line 555 to be
supported.  on startup, however, i get kernel decompression, followed
by a black screen.  it appears the boot sequence does not complete, as i
can't even ssh into the box, although the case may be that init is
hitting a point where it needs interaction somewhere.

i've compiled my kernel with:
        vga console
        vga mode selection support
        framebuffer->ati mach64 support,

all as builtins.  as explained in Documentation/fb/modedb.txt, the atyfb
driver is supported by modedb, and i've placed


in my lilo.conf.  it is probably worth noting that i also still have
vga=791 in my lilo.conf from the vesafb days; i'm considering that
this (as it, for one, specifies a different resolution) may be the
culprit, but the box is at home.

any ideas?  if i simply need to rtfm, please direct me; i've been
searching for an answer to this since 2.2.


  head developer, trellis network security
"one of god's own prototypes, some kind of high-powered mutant never even
considered for mass-production...too weird to live, and too rare to die."
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at
Please read the FAQ at

2. SCO, GDB --- Help

3. making screen go black

4. Parallel Port SCSI Adaptor

5. screen blanker makes w32i board _white_, not black

6. named: Lame Server message

7. Console-Screen-Blanking: black chars on white screen

8. Multiple Pipe

9. Disable screen-saver and low-power standby (monitor black screen)

10. This makes me proud to be a black man

11. Screensavers crash or black screen

12. wine and Warcraft 3 gives me a black screen

13. Trident 9440, XF86 3.1.2b = black screen