linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Rui Santos <rsantos@grupopie.com>
Cc: Linux FB-Devel <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: radeonfb cannot map FB
Date: Wed, 26 Aug 2009 19:54:25 +1000	[thread overview]
Message-ID: <1251280465.1379.64.camel@pasglop> (raw)
In-Reply-To: <4A92EDDB.6040806@grupopie.com>

On Mon, 2009-08-24 at 20:45 +0100, Rui Santos wrote:
> Dear Benjamin Herrenschmidt, dear mailing list subscribers,
> 
>      I'm trying to load radeonfb for an RV100 QY chipset. Whatever I
> type in the modprobe I always get:
>        radeonfb (0000:01:0c.0): cannot map FB
>        radeonfb: probe of 0000:01:0c.0 failed with error -5

I suspect your BIOS isn't initializing the secondary card, radeonfb is
thus unable to use it.

However, you probably don't need radeonfb. X.org should be able to get
it going as a secondary just fine, but your text consoles will have to
remain on the intel.

In the long run (though it might already work with latest upstream), the
new radeon KMS should be able to initialize those.

Cheers,
Ben.

>     I've tried latest 2.6.27.x and 2.6.30.x kernels. This a secondary
> video card that I would like to connect a monitor to. The first video
> card is an Intel 915G, which is working with vesafb.
> 
>     Here is the output of lspci -vvv
>     01:0c.0 VGA compatible controller: ATI Technologies Inc Radeon RV100
> QY [Radeon 7000/VE] (prog-if 00 [VGA controller])
>             Subsystem: ATI Technologies Inc Device 013b
>             Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping+ SERR- FastB2B- DisINTx-
>             Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
> >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
>             Interrupt: pin A routed to IRQ 18
>             Region 0: Memory at d8000000 (32-bit, prefetchable) [size=128M]
>             Region 1: I/O ports at dc00 [size=256]
>             Region 2: Memory at fdee0000 (32-bit, non-prefetchable)
> [size=64K]
>             [virtual] Expansion ROM at fde00000 [disabled] [size=128K]
>             Capabilities: [50] Power Management version 2
>                     Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
> PME(D0-,D1-,D2-,D3hot-,D3cold-)
>                     Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
>             Kernel modules: radeonfb
> 
>     Can you or anyone give a hint on what I might be doing wrong:
> modprobe radeonfb mode_option=800x600-16 panel_yres=600
>     Or could this be some kind of hardware issue ?
> 
>     Thanks a lot for your help,
> 
> Regards,
> 
> Rui Santos
> http://www.ruisantos.com/
> 
> Veni, vidi, Linux!
> 


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july

  parent reply	other threads:[~2009-08-26  9:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-24 19:45 radeonfb cannot map FB Rui Santos
2009-08-24 20:20 ` Alex Deucher
2009-08-26  9:54 ` Benjamin Herrenschmidt [this message]
2009-08-27 11:04   ` Rui Santos
2009-08-27 14:01     ` Alex Deucher
2009-08-27 15:00       ` Rui Santos

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=1251280465.1379.64.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=rsantos@grupopie.com \
    /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).