From: Paul Drynoff <pauldrynoff@gmail.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.6.18-rc1-mm1: as usual can not boot
Date: Wed, 12 Jul 2006 12:17:04 +0400 [thread overview]
Message-ID: <20060712121704.def30154.pauldrynoff@gmail.com> (raw)
In-Reply-To: <1152690358.3217.20.camel@laptopd505.fenrus.org>
On Wed, 12 Jul 2006 09:45:58 +0200
Arjan van de Ven <arjan@infradead.org> wrote:
> On Wed, 2006-07-12 at 11:37 +0400, Paul Drynoff wrote:
> > On Wed, 12 Jul 2006 00:12:32 -0700
> > Andrew Morton <akpm@osdl.org> wrote:
> >
> > > On Wed, 12 Jul 2006 09:59:33 +0400
> > > Paul Drynoff <pauldrynoff@gmail.com> wrote:
> > >
>
> Hi, I havent followed your saga much, but in the past I've seen cases
> where such kind of thing went away when AGP was set to be built into the
> kernel, rather than as a module or not even built at all.
>
> I don't know what your AGP setting is but if it's not built in it's
> worth a shot to set it to be built in.
>
thanks for reply,
At now I build all in kernel (without modules) for debuging purposes,
I have
$ grep -i AGP .config
CONFIG_AGP=y
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
# CONFIG_AGP_INTEL is not set
# CONFIG_AGP_NVIDIA is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_VIA is not set
# CONFIG_AGP_EFFICEON is not set
But still get error
next prev parent reply other threads:[~2006-07-12 8:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 5:59 [BUG] 2.6.18-rc1-mm1: as usual can not boot Paul Drynoff
2006-07-12 7:12 ` Andrew Morton
2006-07-12 7:37 ` Paul Drynoff
[not found] ` <1152690358.3217.20.camel@laptopd505.fenrus.org>
2006-07-12 8:17 ` Paul Drynoff [this message]
2006-07-12 12:46 ` Arjan van de Ven
2006-07-12 14:28 ` Paul Drynoff
2006-07-12 9:27 ` [BUG] 2.6.18-rc1-mm1: the simple way to reproduce it Paul Drynoff
2006-07-13 3:49 ` Andrew Morton
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=20060712121704.def30154.pauldrynoff@gmail.com \
--to=pauldrynoff@gmail.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.