On Jo, 24 iul 14, 20:15:43, Gary Dale wrote:
>
> Shouldn't each module be a self-contained configuration? If a module is
> needed, why should the configuration of a non-used module interfere? This
> strikes me as a design flaw, not a feature.
This is not really about modules, but about packages.
On 24/07/14 08:00 PM, Michael Biebl wrote:
Am 25.07.2014 01:24, schrieb Gary Dale:
As it stands, instead of the .conf files telling you how to configure
the system for that module, you have to look at all the .confs to figure
out what will happen. This kind of defeats the purpose of breaking the
Am 25.07.2014 01:24, schrieb Gary Dale:
> As it stands, instead of the .conf files telling you how to configure
> the system for that module, you have to look at all the .confs to figure
> out what will happen. This kind of defeats the purpose of breaking the
> configuration into separate files for
On 24/07/14 04:48 PM, Michael Biebl wrote:
Am 24.07.2014 21:45, schrieb Gary Dale:
On 24/07/14 03:05 PM, Sven Joachim wrote:
On 2014-07-24 20:42 +0200, Gary Dale wrote:
I think you missed the point. The blacklist was in fglrx.conf where it
makes sense to not load the radeon module if I'm load
Am 24.07.2014 21:45, schrieb Gary Dale:
> On 24/07/14 03:05 PM, Sven Joachim wrote:
>> On 2014-07-24 20:42 +0200, Gary Dale wrote:
>>
>>> I think you missed the point. The blacklist was in fglrx.conf where it
>>> makes sense to not load the radeon module if I'm loading the fglrx
>>> proprietary one
On 24/07/14 03:05 PM, Sven Joachim wrote:
On 2014-07-24 20:42 +0200, Gary Dale wrote:
I think you missed the point. The blacklist was in fglrx.conf where it
makes sense to not load the radeon module if I'm loading the fglrx
proprietary one. Again, this was necessary back when I was playing
arou
On 2014-07-24 20:42 +0200, Gary Dale wrote:
> I think you missed the point. The blacklist was in fglrx.conf where it
> makes sense to not load the radeon module if I'm loading the fglrx
> proprietary one. Again, this was necessary back when I was playing
> around with the fglrx driver. I would hav
On 24/07/14 02:21 PM, Sven Joachim wrote:
On 2014-07-24 19:49 +0200, Gary Dale wrote:
OK, that did it. Removing /etc/modprobe.d/fglrx.conf allowed the
radeon kernel module to load.
You don't need to list it in /etc/modules anymore then, since udev will
load it automatically for you.
The joys
On 2014-07-24 19:49 +0200, Gary Dale wrote:
> OK, that did it. Removing /etc/modprobe.d/fglrx.conf allowed the
> radeon kernel module to load.
You don't need to list it in /etc/modules anymore then, since udev will
load it automatically for you.
> I have no idea why this just started
> happening
On 24/07/14 01:21 PM, Gary Dale wrote:
On 24/07/14 12:57 PM, Michael Biebl wrote:
Am 24.07.2014 18:39, schrieb Gary Dale:
On 24/07/14 08:56 AM, Michael Biebl wrote:
Am 24.07.2014 12:42, schrieb Gary Dale:
After the latest round of upgrades in Jessie, I rebooted. That's when
the problems start
On 24/07/14 01:21 PM, Gary Dale wrote:
On 24/07/14 12:57 PM, Michael Biebl wrote:
Am 24.07.2014 18:39, schrieb Gary Dale:
On 24/07/14 08:56 AM, Michael Biebl wrote:
Am 24.07.2014 12:42, schrieb Gary Dale:
After the latest round of upgrades in Jessie, I rebooted. That's when
the problems start
11 matches
Mail list logo
