From: Ryan Boder <icanoop@bitwiser.org>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Trouble with 2.6.0-test1 on ibook2
Date: Fri, 18 Jul 2003 13:02:58 -0400 [thread overview]
Message-ID: <20030718170258.GE6596@bitwiser.org> (raw)
In-Reply-To: <1058517715.23548.71.camel@thor.holligenstrasse29.lan>
On Fri, Jul 18, 2003 at 10:41:55AM +0200, Michel Dänzer wrote:
> What graphics chip does the machine have, and have you built OFfb into
> the kernel?
Rage Mobility M3 AGP 2x (rev 02).
Yes, I did. I'll try again without that as soon as my iso finished
downloading. I figure I might as well move to YDL 3.0 while I'm
reinstalling.
Thanks for the advice,
--
Ryan Boder
http://www.bitwiser.org/icanoop
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-07-18 17:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-18 1:46 Trouble with 2.6.0-test1 on ibook2 Ryan Boder
2003-07-18 8:41 ` Michel Dänzer
2003-07-18 17:02 ` Ryan Boder [this message]
2003-07-19 12:25 ` Michel Dänzer
[not found] ` <1058740445.31388.89.camel@teron.lan.stampflee.com>
2003-07-21 1:14 ` Ryan Boder
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=20030718170258.GE6596@bitwiser.org \
--to=icanoop@bitwiser.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=michel@daenzer.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).