linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miernik <miernik@ctnet.pl>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: vesafb on Savage4
Date: Tue, 3 Aug 2004 10:43:36 +0000 (UTC)	[thread overview]
Message-ID: <cenq8o$lkv$1@sea.gmane.org> (raw)


I have got a video card which identifies itself (before BIOS boots) as
S3 86C395/396/397. 

My lspci -vv output is:

0000:01:00.0 VGA compatible controller: S3 Inc. Savage 4 (rev 02) (prog-if 00 [VGA])
        Subsystem: S3 Inc. 86C394-397 Savage4
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 248 (1000ns min, 63750ns max), Cache Line Size: 0x08 (32 bytes)
        Interrupt: pin A routed to IRQ 11
        Region 0: Memory at d9000000 (32-bit, non-prefetchable) [size=512K]
        Region 1: Memory at d0000000 (32-bit, prefetchable) [size=128M]
        Capabilities: [dc] Power Management version 1
                Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [80] AGP version 2.0
                Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA- ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4
                Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none>

The kernel is installed from a binary:
http://ftp.pl.debian.org/debian/pool/main/k/kernel-image-2.6.7-i386/kernel-image-2.6.7-1-k7_2.6.7-2_i386.deb

When the system is booted, in /var/log/kern.log there is:

Aug  3 13:52:19 localhost kernel: vesafb: probe of vesafb0 failed with error -6

przehyba:~# modprobe vesafb
przehyba:~# lsmod | grep vesafb
vesafb                  6688  0
cfbcopyarea             3776  1 vesafb
cfbimgblt               3072  1 vesafb
cfbfillrect             3712  1 vesafb
przehyba:~# cat /proc/fb
przehyba:~# fbset
open /dev/fb0: No such device
przehyba:~# ls -l /dev/fb0
crw-rw----  1 root video 29, 0 Aug  2 23:45 /dev/fb0
przehyba:~#

From these posts I can see that vesafb does work on Savage cards:

http://www.directfb.org/mailinglists/directfb-dev/2003/06-2003/msg00007.html
http://www.ussg.iu.edu/hypermail/linux/kernel/0011.0/0263.html

If I try savagefb, I get the same error that is decribed here:

http://www.directfb.org/mailinglists/directfb-dev/2003/09-2003/msg00044.html

How can I get any framebuffer working on this card?

-- 
    Miernik         ________________________   xmpp:miernik@amessage.info
___________________/__ tel: +48888299997 __/      mailto:miernik@ctnet.pl
http://www.miernik.ctnet.pl/                               GPG:0xABC292D1



-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com

             reply	other threads:[~2004-08-03 10:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-03 10:43 Miernik [this message]
2004-08-03 12:22 ` vesafb on Savage4 Antonino A. Daplas
2004-08-03 12:53   ` Miernik
2004-08-03 21:26     ` Antonino A. Daplas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='cenq8o$lkv$1@sea.gmane.org' \
    --to=miernik@ctnet.pl \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).