9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Philippe Anel <philippe.anel@noos.fr>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] radeon driver doesn't work: bad VGA control  message "type radeon"
Date: Thu, 18 Mar 2004 11:08:28 +0100	[thread overview]
Message-ID: <6.0.0.22.0.20040318110210.0a8120b0@pop.noos.fr> (raw)
In-Reply-To: <7186c.846424$X%5.462229@pd7tw2no>

At 10:48 18/03/04, you wrote:
>On Monday, March 15th, Phillipe Anel wrote:
>
> > It seems you forgot to build/use a new kernel with the radeon driver.
> > At least, the kernel part didn't find the card. It could be a pciid
> > problem.
>
>I've mk install'd the whole OS for good measure. (It's pretty fast at
>compiling, eh?)

Ok. Remember to copy you compiled kernel to 9fat, and to update
your plan9.ini if needed.
9load doesn't boot kernels copied in /386 (at least when fossil is
the main filesystem).


> > Could you execute aux/vga -v and send me the result ?
>
>% aux/vga -v
>main->snarf
>vga->snarf
>radeon->snarf
>+vgactlw type radeon
>sequencer->enter on
>sequencer->leave on
>vgactlw: <type radeon>: bad VGA control message "type radeon"

The kernel you boot on doesn't have radeon support compiled in.
Could you send me your kernel configuration file ?

>I'll try installing the update tomorrow.

I still haven't fixed the bug I have with my radeon8500.

         Regards,
         Philippe. 



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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-15 10:44 Thomas Covello
2004-03-15 11:35 ` Philippe Anel
2004-03-15 13:24 ` andrey mirtchovski
2004-03-15 14:34   ` andrey mirtchovski
2004-03-18  9:48 ` Thomas Covello
2004-03-18 10:08   ` Philippe Anel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-03-15 10:43 [9fans] radeon driver doesn't work: bad vga " TPC

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=6.0.0.22.0.20040318110210.0a8120b0@pop.noos.fr \
    --to=philippe.anel@noos.fr \
    --cc=9fans@cse.psu.edu \
    /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).