From: jiangning 39481 <jiangnuts@huawei.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: Problem about FB on an iBook G4
Date: Sat, 02 Oct 2004 11:07:18 +0000 (GMT) [thread overview]
Message-ID: <3535634202.3420235356@huawei.com> (raw)
> The radeonfb in that kernel may be too old for your Radeon. What
> does `lspci
> -v' say?
>
Part of 'lspci -v' I think useful are as follows:
00:0b.0 Host bridge:Apple Computer Inc.UniNarth 2 AGP
Flags:bus master,66Mhz,medium devsel,latency 16
00:10.0 VGA compatible controller:ATI Technologies Inc:Unknown devce 5c63 (rev 01) (prog-if 00 [VGA])
Subsystem:ATI Technologies Inc:Unknown device 5c63
Memory at 90000000 (32bit,non-prefetchable)[siu=6k]
Expansion ROM at 90020000[disabled][size=128k]
Capabilities:[58] AGP version 2.0
Capabilities:[50] Power Management version 2
'mplayer -vo cvidix xxx.avi' output:
[radeon] Found chip:RV250 5c63 [Radeon Mobility 9200 M9+]
[radeon] Device is disabled,ignoring
vosub_vidix:Couldn't find working VIDIX driver
'mplayer -vo fbdev xxx.avi' output:
Can't put VSCREENINFO
'fbset -i' output:
...
Frame buffer device information:
Name:OFfb ATY,Via_A
Address:0x9c008000
size:789432
Type:Packed PiXELS
Visual:PSEUDOCOLOR
...
ACCELERATOR:NO
And I tried 'video=offb:off video=radeon:1024x768-32',I only got a frazed screen and I could type 'reboot' just to reboot.
Is this caused by someting in Open Firmware or old kernel as you said?
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
next reply other threads:[~2004-10-02 14:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-02 11:07 jiangning 39481 [this message]
2004-10-02 14:59 ` Problem about FB on an iBook G4 Geert Uytterhoeven
[not found] <c854a4.54a4c8@huawei.com>
2004-09-30 10:29 ` Geert Uytterhoeven
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=3535634202.3420235356@huawei.com \
--to=jiangnuts@huawei.com \
--cc=geert@linux-m68k.org \
--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).