On 13/10/16 22:17, Robin Laing wrote:
On 07/10/16 00:09, Robin Laing wrote:
On 04/10/16 19:53, Robin Laing wrote:
On 04/10/16 00:21, Nicolas Chauvet wrote:
2016-10-04 8:20 GMT+02:00 Nicolas Chauvet :
2016-10-04 5:33 GMT+02:00 Robin Laing :
[...]
you
On 07/10/16 00:09, Robin Laing wrote:
On 04/10/16 19:53, Robin Laing wrote:
On 04/10/16 00:21, Nicolas Chauvet wrote:
2016-10-04 8:20 GMT+02:00 Nicolas Chauvet :
2016-10-04 5:33 GMT+02:00 Robin Laing :
[...]
you did the *mandatory* "grub2-mkconfig -o
On 04/10/16 19:53, Robin Laing wrote:
On 04/10/16 00:21, Nicolas Chauvet wrote:
2016-10-04 8:20 GMT+02:00 Nicolas Chauvet :
2016-10-04 5:33 GMT+02:00 Robin Laing :
[...]
you did the *mandatory* "grub2-mkconfig -o /boot/grub2/grub.cfg" after
changing
On 04/10/16 00:21, Nicolas Chauvet wrote:
2016-10-04 8:20 GMT+02:00 Nicolas Chauvet :
2016-10-04 5:33 GMT+02:00 Robin Laing :
[...]
you did the *mandatory* "grub2-mkconfig -o /boot/grub2/grub.cfg" after
changing that file?
Yes I did.
Made no
On 01/10/16 19:16, Joseph D. Wagner wrote:
I will report a bug when I can confirm.
I have blacklisted the module to test.
Interesting thing. Grubby has not put the blacklist command on any
kernel since I updated on Aug 25. with 4.6.5 and everything worked well.
This file does exist.
On 03/10/16 03:18, Reindl Harald wrote:
Am 03.10.2016 um 01:26 schrieb Robin Laing:
On 01/10/16 17:43, Reindl Harald wrote:
what about fix your /etc/default/grub and get rid of stuff which mangles
your boot configuration?
This is the /etc/default/grub after adding the blacklist yesterday.
>
GRUB_CMDLINE_LINUX="rd.luks.uuid=luks-2e0ad798-4e73-4b78-a902-7e8d02cf124e
nomodeset rhgb quiet rd.driver.blacklist=nouveau video=vesa:off "
Could you try changing "nomodeset" to "nouveau.modeset=0"? It's a long
shot, but that's what mine has.
Don't forget to rerun "dracut -f"
On 01/10/16 17:43, Reindl Harald wrote:
Am 02.10.2016 um 01:40 schrieb Robin Laing:
On 01/10/16 12:40, Reindl Harald wrote:
./4.7.5-200.fc24.x86_64/extra/nvidia/nvidia-uvm.ko
./4.7.5-200.fc24.x86_64/extra/nvidia/nvidia-drm.ko
./4.7.5-200.fc24.x86_64/extra/nvidia/nvidia.ko
On 01/10/16 13:27, Nicolas Chauvet wrote:
Please report any log you have about akmods on bugzilla.rpmfusion.org
You might need to run depmod -ae from Your Kernel. But the reason why you
would need to re-run this need to be investivated.
There must have a race condition here...
Thx for the
Am 02.10.2016 um 01:40 schrieb Robin Laing:
On 01/10/16 12:40, Reindl Harald wrote:
./4.7.5-200.fc24.x86_64/extra/nvidia/nvidia-uvm.ko
./4.7.5-200.fc24.x86_64/extra/nvidia/nvidia-drm.ko
./4.7.5-200.fc24.x86_64/extra/nvidia/nvidia.ko
./4.7.5-200.fc24.x86_64/extra/nvidia/nvidia-modeset.ko
All
On 01/10/16 12:40, Reindl Harald wrote:
Am 01.10.2016 um 20:29 schrieb Robin Laing:
Hello,
Latest F24 kernel update with akmods. The kernel modules were created
by akmods but when trying to boot the system, the kernel module is not
found.
Even trying to run modprobe nvidia fails.
sudo
On 01/10/16 15:55, Joseph D. Wagner wrote:
Do you have the nouveau driver blacklisted in your kernel boot parameters?
rd.driver.blacklist=nouveau video=vesa:off
If not, you'll need to rerun dracut after configuring.
That's the only thing I can think of. It appears to be working for me.
$
Am 01.10.2016 um 20:29 schrieb Robin Laing:
Hello,
Latest F24 kernel update with akmods. The kernel modules were created
by akmods but when trying to boot the system, the kernel module is not
found.
Even trying to run modprobe nvidia fails.
sudo modprobe nvidia
password:
modprobe: FATAL:
13 matches
Mail list logo