From: Venkatesh Srinivas <me@acm.jhu.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] ctrl radeon: not working for ATI Radeon 9600 Mobility?
Date: Thu, 29 Apr 2010 08:44:37 -0400 [thread overview]
Message-ID: <t2jf75780241004290544reb54e94n977f8c5b26c82a38@mail.gmail.com> (raw)
In-Reply-To: <a47a9c58032ed6739d30176923170669@kw.quanstro.net>
On Thu, Apr 29, 2010 at 7:17 AM, erik quanstrom <quanstro@quanstro.net> wrote:
>> I added two lines of code to /sys/src/cmd/aux/vga/radeon.h; compiled
>> vga and kernel; added line to /lib/vgadb.
>> Now kernel sees the device (and I see it too: cat /dev/vgactl), but
>> attempt to start framebuffer gives blank screen. Pointers are
>> appreciated!
>
> it didn't work for me, either. i added a bit of
> code to support the newer "atom bios" but
> ran out of patience and the vesa driver works.
ATOM BIOS should be unnecessary for the R9600; it is an r300-era card.
I've not ever tried with a mobility (is it an m10?) r9600, but the
desktop variant works when its PCI IDs are added... I forget whether I
had to enable r300hack, though, for it...
-- vs
next prev parent reply other threads:[~2010-04-29 12:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d7a540d6-2751-4e30-8766-e3511bb8c202@g11g2000yqe.googlegroups.co>
2010-04-26 13:15 ` erik quanstrom
2010-04-29 9:58 ` Anton.Pavlovetsky
[not found] ` <7caa7a0a-fb6d-4ffa-81ef-ad3256100f2c@g21g2000yqk.googlegroups.co>
2010-04-29 11:17 ` erik quanstrom
2010-04-29 12:44 ` Venkatesh Srinivas [this message]
2010-04-30 8:53 ` Anton.Pavlovetsky
2010-04-30 8:53 ` Anton.Pavlovetsky
[not found] ` <9e5fc5ec-43d5-4cf3-be92-3fc8c4829ba0@l32g2000yqm.googlegroups.co>
2010-04-30 12:07 ` erik quanstrom
2010-04-30 12:30 ` Gabriel Díaz
2010-05-01 13:53 ` Venkatesh Srinivas
2010-05-01 14:08 ` erik quanstrom
2010-05-01 19:05 ` Venkatesh Srinivas
2010-05-01 22:48 ` Venkatesh Srinivas
2010-05-02 0:42 ` erik quanstrom
2010-05-04 8:47 ` Anton.Pavlovetsky
2010-04-26 11:17 Anton.Pavlovetsky
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=t2jf75780241004290544reb54e94n977f8c5b26c82a38@mail.gmail.com \
--to=me@acm.jhu.edu \
--cc=9fans@9fans.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).