From: Dave Jones <davej-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Joshua Wise <joshua-NtISFavHD68j5TC/SZClsA@public.gmane.org>
Cc: hgfelger-9nAOAgdJVo4b1SvskN2V4Q@public.gmane.org,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ACPI on hp tc1100
Date: Sun, 26 Dec 2004 02:31:13 -0500 [thread overview]
Message-ID: <20041226073113.GA919@redhat.com> (raw)
In-Reply-To: <41CE656C.1050500-NtISFavHD68j5TC/SZClsA@public.gmane.org>
On Sun, Dec 26, 2004 at 02:17:00AM -0500, Joshua Wise wrote:
> Joshua Wise wrote:
> >Hm. First, I tried just setting Option "NvAGP" "1" in my XF86Config
> >without downgrading, and that seemed to do the trick! I am running the
> >latest NVidia drivers: 6629. However, when the system 'comes back to
> >life', the wireless is non-functional, as described below. The
> >wacom-acpi driver also seems to need to be reloaded: on resume, dmesg
> >reports that ttyS4 failed the LSR safety check.
>
> Well, digging this out of the archive.... I figured out why NvAGP 1
> "fixed" the problem. It seems that the tc1100's AGP host bridge is in
> fact unsupported by the NVIDIA AGP driver, so when we force the NVIDIA
> driver's AGP mode, we effectively disable AGP and only use PCI. I wonder
> if kernel AGPGART is not doing some sort of appropriate AGP magic before
> the NVIDIA driver comes back up?
What does lspci say about the host/pci bridge ?
Dave
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-12-26 7:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-05 4:40 ACPI on hp tc1100 Joshua Wise
[not found] ` <41B2912D.8020105-NtISFavHD68j5TC/SZClsA@public.gmane.org>
2004-12-05 11:24 ` liste-9nAOAgdJVo4b1SvskN2V4Q
[not found] ` <Pine.LNX.4.60.0412051210070.990-KnfdeQs3A3X/9pzu0YdTqQ@public.gmane.org>
2004-12-05 21:03 ` Joshua Wise
[not found] ` <41B377AE.7080108-NtISFavHD68j5TC/SZClsA@public.gmane.org>
2004-12-05 21:14 ` Stefan Dösinger
[not found] ` <200412052214.25733.stefandoesinger-RbZlAiThDcE@public.gmane.org>
2004-12-05 23:32 ` Joshua Wise
2004-12-26 7:17 ` Joshua Wise
[not found] ` <41CE656C.1050500-NtISFavHD68j5TC/SZClsA@public.gmane.org>
2004-12-26 7:31 ` Dave Jones [this message]
[not found] ` <20041226073113.GA919-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2004-12-26 20:24 ` Joshua Wise
[not found] ` <41CF1DF0.60504-NtISFavHD68j5TC/SZClsA@public.gmane.org>
2004-12-26 20:36 ` Dave Jones
[not found] ` <20041226203637.GB26474-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2004-12-26 20:52 ` Joshua Wise
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=20041226073113.GA919@redhat.com \
--to=davej-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=hgfelger-9nAOAgdJVo4b1SvskN2V4Q@public.gmane.org \
--cc=joshua-NtISFavHD68j5TC/SZClsA@public.gmane.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