From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ati-drivers:legacy fail to build with kernel 3.12
Date: Wed, 02 Oct 2013 09:06:42 +0200 [thread overview]
Message-ID: <524BC602.9030105@gmail.com> (raw)
In-Reply-To: <1380697370.31512.0@numa-i.igpm.rwth-aachen.de>
On 02/10/2013 09:02, Helmut Jarausch wrote:
> On 10/01/2013 08:16:23 PM, Volker Armin Hemmann wrote:
>> Am 01.10.2013 10:00, schrieb Helmut Jarausch:
>> > Hi,
>> >
>> > in "good" tradition the new 3.12 Linux kernel breaks ati-drivers
>> > again (as always in the past).
>> > Does anybody know about a patch to make
>> > x11-drivers/ati-drivers:legacy
>> > compile with linux-3.12-rc3 ?
>> >
>> > Trying to emerge ati-drivers-13.1_pre897 (currently the only legacy
>> > driver)
>> > with 3.12-rc3 gives
>> >
>> > MODPOST 1 modules
>> > FATAL: modpost: GPL-incompatible module fglrx.ko uses GPL-only symbol
>> > 'acpi_bus_get_device'
>> >
>> > Many thanks for a hint,
>> > Helmut
>> >
>>
>> so you are using a driver meant for stable (old) systems, with a pre
>> release kernel - and you don't even know what do do with that message?
>
> I'm quite sure there are a lot of things which you don't known either.
>
>> Does that do no seem a bit silly? hm?
>
> Thanks for this compliment!
>
>> acpi_bus_get_device is gpl only. You can undo that. If you want.
>>
>> But seriously, what is wrong with using stable releases like 3.10.x? If
>> you use ati-drivers, you don't need the amd driver improvements in 3.11
>> or 3.12.
>
> There are two points here:
> - first I consider it as my contribution to GenToo to help testing.
> The problem with the 3.12 prerelease will definitely continue with the
> main release
> coming in about 4 weeks.
>
> - This 3.12 prerelease has a lot of BTRFS pataches. Since I'm using
> BTRFS for most of
> my file systems, I like to have the most recent fixes.
Calm down boys.
Helmut, the problem is that you are trying to use ATI's proprietary code
with GPL code in the kernel.
The kernel devs do not want you to do that and that is their right.
What you should have done in your mail is indicate that you read the
error message and understand it, and why you want to continue
regradless. Then you should have mentioned what Google told you about
the problem, or something to show what you already did to help yourself.
As it stands you post is really just asking someone else to do your
homework for you and that you are too lazy to do it yourself. I'm sure
that's not want you are really doing, it just looks that way.
--
Alan McKinnon
alan.mckinnon@gmail.com
next prev parent reply other threads:[~2013-10-02 7:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 8:00 [gentoo-user] ati-drivers:legacy fail to build with kernel 3.12 Helmut Jarausch
2013-10-01 18:16 ` Volker Armin Hemmann
2013-10-02 7:02 ` Helmut Jarausch
2013-10-02 7:06 ` Alan McKinnon [this message]
2013-10-02 12:19 ` Helmut Jarausch
2013-10-03 9:30 ` Alan McKinnon
2013-10-03 7:08 ` Mick
2013-10-03 11:29 ` Helmut Jarausch
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=524BC602.9030105@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.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