The uploads I did today have disabled the aliases in
nvidia-modprobe.conf again to better investigate this issue without
breaking to many systems out there ...
That also means co-installation of current and legacy packages is not
working as intended because the wrong kernel module will be loaded.
A proper solution will probably include patching nv-reg.h to set our
preferred defaults.
Andreas
On Wed, 2015-10-14 at 12:29 +0200, Andreas Beckmann wrote:
> On 2015-10-14 00:25, Luca Boccassi wrote:
> > loading the module. As you suspected, it's udev. More precisely, it's
> > this systemd unit at boot:
> >
> > /lib/systemd/system/systemd-udev-trigger.service
> >
> > And even more precisely,
On 14 October 2015 at 11:29, Andreas Beckmann wrote:
> On 2015-10-14 00:25, Luca Boccassi wrote:
>> loading the module. As you suspected, it's udev. More precisely, it's
>> this systemd unit at boot:
>>
>> /lib/systemd/system/systemd-udev-trigger.service
>>
>> And even more precisely, this udevadm
On 2015-10-14 00:25, Luca Boccassi wrote:
> loading the module. As you suspected, it's udev. More precisely, it's
> this systemd unit at boot:
>
> /lib/systemd/system/systemd-udev-trigger.service
>
> And even more precisely, this udevadm call by that unit:
>
> udevadm trigger --type=devices --ac
On Tue, 2015-10-13 at 09:17 +0100, Luca Boccassi wrote:
> On Oct 12, 2015 12:09, "Andreas Beckmann" wrote:
> >
> > Thanks for finding some of the missing pieces :-)
> >
> > I assume the module nowadays gets loaded by udev ... is there any
> way to
> > get some more verbose log out of udev to see w
6 matches
Mail list logo
