From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Herminio Hernandez, Jr." <herminio.hernandezjr@gmail.com>,
Mike <michael.heltne@gmail.com>
Cc: Pranith Kumar <bobby.prani@gmail.com>,
"open list:LINUX FOR POWERPC..." <linuxppc-dev@lists.ozlabs.org>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
"debian-powerpc@lists.debian.org"
<debian-powerpc@lists.debian.org>
Subject: Re: PowerPC agpmode issues
Date: Mon, 19 Sep 2016 20:38:56 +1000 [thread overview]
Message-ID: <1474281536.2857.15.camel@kernel.crashing.org> (raw)
In-Reply-To: <CAJRA9dwyJ+5XuD7i0ktwvx3Md9p_Z9tiVZCWvO_gK1kfG-+ccA@mail.gmail.com>
On Mon, 2016-09-19 at 02:13 -0700, Herminio Hernandez, Jr. wrote:
>
> I noticed the GPU was set to PCI mode however I did not set
> radeon.agpmode=-1 in yaboot. I then installed Lubuntu 16.10 along
> side Debian. I noticed that GPU was working and it was not set to
> force PCI mode. Has there been a change to kernel in Debian to force
> this by default? If so it looks like it is breaking on certain G5
> machines. I am attaching bothe dmesg files for review.
>
> Thanks and sorry for the previous garbled email.
Hrm... this is odd. I would expect PCI mode to work and AGP to be
busted to be honest. Can you provide the complete log ? I wonder
if it's trying to enable the PCIe bypass high aperture and hits the
Radeon address limit...
Ben.
next prev parent reply other threads:[~2016-09-19 10:39 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 2:47 PowerPC agpmode issues Mike
2016-02-05 7:49 ` Denis Kirjanov
2016-02-05 14:42 ` Mike
2016-02-05 14:32 ` Herminio Hernandez Jr.
2016-02-05 14:44 ` Mike
2016-02-05 17:51 ` Herminio Hernandez, Jr.
2016-02-05 18:06 ` Mike
2016-02-05 18:08 ` Herminio Hernandez, Jr.
2016-02-05 19:44 ` Mike
2016-02-05 19:46 ` Herminio Hernandez, Jr.
2016-02-05 19:59 ` Mike
2016-02-05 20:10 ` Herminio Hernandez, Jr.
2016-08-25 3:09 ` Mike
2016-08-25 5:34 ` Mathieu Malaterre
2016-08-25 10:54 ` Benjamin Herrenschmidt
[not found] ` <57DF23C4.20508@gmail.com>
2016-09-19 9:13 ` Herminio Hernandez, Jr.
2016-09-19 10:38 ` Benjamin Herrenschmidt [this message]
2016-09-19 19:30 ` Herminio Hernandez, Jr.
2016-09-19 12:36 ` Mathieu Malaterre
2016-09-20 3:05 ` Michel Dänzer
2016-09-20 3:43 ` Herminio Hernandez, Jr.
2016-09-20 6:20 ` Michel Dänzer
2016-09-21 6:20 ` Herminio Hernandez, Jr.
2016-10-08 19:05 ` Herminio Hernandez, Jr.
2016-10-09 7:49 ` Benjamin Herrenschmidt
2016-02-08 9:53 ` Michel Dänzer
2016-02-08 12:09 ` Mike
2016-02-08 12:41 ` Boris Reinhard
2016-02-08 13:28 ` Mike
2016-02-09 1:41 ` Michel Dänzer
2016-02-09 2:27 ` Mike
2016-02-09 11:52 ` Gerhard Pircher
2016-02-09 12:15 ` luigi burdo
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=1474281536.2857.15.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=bobby.prani@gmail.com \
--cc=debian-powerpc@lists.debian.org \
--cc=herminio.hernandezjr@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=michael.heltne@gmail.com \
/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).