From: Nick Papadonis <nick@coelacanth.com>
To: Dave Morgan <daves_spam_account@yahoo.com>
Cc: acpi@phobos.fachschaften.tu-muenchen.de, linux-kernel@vger.kernel.org
Subject: AGP support locks X - was Re: sony vaio, crude workaround
Date: 17 Aug 2001 21:20:33 -0400 [thread overview]
Message-ID: <m3itfmrwny.fsf@coelacanth.com> (raw)
In-Reply-To: <20010817124100.12469.qmail@web20304.mail.yahoo.com>
In-Reply-To: <20010817124100.12469.qmail@web20304.mail.yahoo.com> (Dave Morgan's message of "Fri, 17 Aug 2001 05:41:00 -0700 (PDT)")
This solved the problem. Apparently AGP has to be built as a module
in kernels v2.4.8 or X will lock up? Anyone else experience this?
> I'm not sure that this is the problem you are having,
> but I had a problem with X when I was playing with the
> ACPI stuff and recompiling the kernel on my vaio. Try
> setting CONFIG_AGP=m (i.e. make AGP support a module,
> as opposed to being compiled in-kernel.) if it isn't.
> Once I did that, X started up just fine. Good luck.
>
> Dave
Dave Morgan <daves_spam_account@yahoo.com> writes:
> >> I tried this and it doesn't disable the console.
> The /proc/acpi
> >> represents the correct power status. When I tried
> to
> >> start up X the following error occurs:
> >>
> >> I810 Dma Initialization Failed
> >> XIO: fatal IO error 104 (Connection reset by peer)
> >on X server
> >":0.0"
> >> after 0 requests (0 known processed) with 0
> >events remaining.
> >>
> >> So the work around must break something else?
>
> >Follup:
>
> >This isn't because of the ACPI code. It's something
> >that happens in
> >my 2.4.8 kernel wo ACPI compiled in. This behavior
> is >not shown with
> >the 2.2.16 kernel.
>
next parent reply other threads:[~2001-08-18 1:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010817124100.12469.qmail@web20304.mail.yahoo.com>
2001-08-18 1:20 ` Nick Papadonis [this message]
2001-08-18 1:56 ` AGP support locks X - was Re: sony vaio, crude workaround Paul G. Allen
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=m3itfmrwny.fsf@coelacanth.com \
--to=nick@coelacanth.com \
--cc=acpi@phobos.fachschaften.tu-muenchen.de \
--cc=daves_spam_account@yahoo.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox