12:08 p.m.
(sending from the correct address this time)
On Mon, Jul 06, 2015 at 12:56:31PM +0100, Christopher Ross wrote:
On 06/07/15 12:41, Suvayu Ali wrote:
>On Mon, Jul 06, 2015 at 10:05:51AM +0100, Christopher Ross wrote:
>>
>>[ 13.476] (==) Matched nouveau as autoconfigured driver 0
>>[ 13.476] (==) Matched nv as autoconfigured driver 1
>>[ 13.476] (==) Matched modesetting as autoconfigured driver 2
>>[ 13.476] (==) Matched fbdev as autoconfigured driver 3
>>[ 13.476] (==) Matched vesa as autoconfigured driver 4
>
>I think this bit illustrates the problem. The nvidia drivers are not
>recognised at all. Of course loading fails later on. I do not know how
>it is supposed to look though, I don't have any nvidia cards.
>
>I would guess something went wrong installing kmod-nvidia. Maybe look
>at the transaction log with dnf history.
I have repeated the experiment several times, always with the same result.
I would not expect repetition to change anything unless the problem is
something random. Did you look if kmod-nvidia installed correctly?
Were there messages (e.g. scriptlet failures) during (re)installation?
IIUC, references to the driver needs to be present in the initramfs. I
suspect this is going wrong and you booting with the old initramfs which
still references nouveau.
--
Suvayu
Open source is the future. It sets us free.
1:18 p.m.
New subject: F22 Black Screen with nVidia drivers
On 06/07/15 13:08, Suvayu Ali wrote:
(sending from the correct address this time)
On Mon, Jul 06, 2015 at 12:56:31PM +0100, Christopher Ross wrote:
> On 06/07/15 12:41, Suvayu Ali wrote:
>> On Mon, Jul 06, 2015 at 10:05:51AM +0100, Christopher Ross wrote:
>>>
>>> [ 13.476] (==) Matched nouveau as autoconfigured driver 0
>>> [ 13.476] (==) Matched nv as autoconfigured driver 1
>>> [ 13.476] (==) Matched modesetting as autoconfigured driver 2
>>> [ 13.476] (==) Matched fbdev as autoconfigured driver 3
>>> [ 13.476] (==) Matched vesa as autoconfigured driver 4
>>
>> I think this bit illustrates the problem. The nvidia drivers are not
>> recognised at all. Of course loading fails later on. I do not know how
>> it is supposed to look though, I don't have any nvidia cards.
>>
>> I would guess something went wrong installing kmod-nvidia. Maybe look
>> at the transaction log with dnf history.
>
>
> I have repeated the experiment several times, always with the same result.
I would not expect repetition to change anything unless the problem is
something random. Did you look if kmod-nvidia installed correctly?
Were there messages (e.g. scriptlet failures) during (re)installation?
IIUC, references to the driver needs to be present in the initramfs. I
suspect this is going wrong and you booting with the old initramfs which
still references nouveau.
Retrying just now with akmod instead of kmod I got the following result:
root@snoopy 14:10:21 ~ # dnf install xorg-x11-drv-nvidia
Last metadata expiration check performed 0:41:29 ago on Mon Jul 6
13:28:58 2015.
Dependencies resolved.
===================================================================================================================================
Package Arch Version
Repository Size
===================================================================================================================================
Installing:
akmod-nvidia x86_64
1:346.72-2.fc22.1 rpmfusion-nonfree 68 k
akmods noarch
0.5.2-1.fc22 rpmfusion-free 24 k
cpp x86_64
5.1.1-4.fc22 updates 8.3 M
gcc x86_64
5.1.1-4.fc22 updates 19 M
glibc-devel x86_64
2.21-5.fc22 fedora 902 k
glibc-headers x86_64
2.21-5.fc22 fedora 493 k
isl x86_64
0.14-3.fc22 fedora 490 k
kernel-debug-devel x86_64
4.0.6-300.fc22 updates 9.5 M
kernel-headers x86_64
4.0.6-300.fc22 updates 996 k
kmodtool noarch 1-23.fc22
rpmfusion-free 17 k
libmpc x86_64
1.0.2-3.fc22 fedora 55 k
xorg-x11-drv-nvidia x86_64
1:346.72-1.fc22 rpmfusion-nonfree 4.0 M
xorg-x11-drv-nvidia-kmodsrc x86_64
1:346.72-1.fc22 rpmfusion-nonfree 3.5 M
xorg-x11-drv-nvidia-libs x86_64
1:346.72-1.fc22 rpmfusion-nonfree 16 M
Transaction Summary
===================================================================================================================================
Install 14 Packages
Total download size: 63 M
Installed size: 227 M
Is this ok [y/N]: y
Downloading Packages:
(1/14): akmod-nvidia-346.72-2.fc22.1.x86_64.rpm
199 kB/s | 68 kB 00:00
(2/14): kmodtool-1-23.fc22.noarch.rpm
135 kB/s | 17 kB 00:00
(3/14): akmods-0.5.2-1.fc22.noarch.rpm
44 kB/s | 24 kB 00:00
(4/14): xorg-x11-drv-nvidia-kmodsrc-346.72-1.fc22.x86_64.rpm
775 kB/s | 3.5 MB 00:04
(5/14): xorg-x11-drv-nvidia-346.72-1.fc22.x86_64.rpm
531 kB/s | 4.0 MB 00:07
(6/14): libmpc-1.0.2-3.fc22.x86_64.rpm
183 kB/s | 55 kB 00:00
(7/14): xorg-x11-drv-nvidia-libs-346.72-1.fc22.x86_64.rpm
1.9 MB/s | 16 MB 00:08
(8/14): glibc-devel-2.21-5.fc22.x86_64.rpm
1.0 MB/s | 902 kB 00:00
(9/14): isl-0.14-3.fc22.x86_64.rpm
1.2 MB/s | 490 kB 00:00
(10/14): cpp-5.1.1-4.fc22.x86_64.rpm
1.0 MB/s | 8.3 MB 00:08
(11/14): glibc-headers-2.21-5.fc22.x86_64.rpm
373 kB/s | 493 kB 00:01
(12/14): kernel-headers-4.0.6-300.fc22.x86_64.rpm
665 kB/s | 996 kB 00:01
(13/14): kernel-debug-devel-4.0.6-300.fc22.x86_64.rpm
1.0 MB/s | 9.5 MB 00:09
(14/14): gcc-5.1.1-4.fc22.x86_64.rpm
1.1 MB/s | 19 MB 00:16
-----------------------------------------------------------------------------------------------------------------------------------
Total
2.4 MB/s | 63 MB 00:26
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Installing : libmpc-1.0.2-3.fc22.x86_64
1/14
Installing : kmodtool-1-23.fc22.noarch
2/14
Installing : cpp-5.1.1-4.fc22.x86_64
3/14
Installing : kernel-headers-4.0.6-300.fc22.x86_64
4/14
Installing : glibc-headers-2.21-5.fc22.x86_64
5/14
Installing : glibc-devel-2.21-5.fc22.x86_64
6/14
Installing : kernel-debug-devel-4.0.6-300.fc22.x86_64
7/14
Installing : isl-0.14-3.fc22.x86_64
8/14
Installing : gcc-5.1.1-4.fc22.x86_64
9/14
Installing : akmods-0.5.2-1.fc22.noarch
10/14
Installing : xorg-x11-drv-nvidia-kmodsrc-1:346.72-1.fc22.x86_64
11/14
Installing : xorg-x11-drv-nvidia-libs-1:346.72-1.fc22.x86_64
12/14
Installing : akmod-nvidia-1:346.72-2.fc22.1.x86_64
13/14
Installing : xorg-x11-drv-nvidia-1:346.72-1.fc22.x86_64
14/14
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.0.6-300.fc22.x86_64
Found initrd image: /boot/initramfs-4.0.6-300.fc22.x86_64.img
Found linux image: /boot/vmlinuz-4.0.5-300.fc22.x86_64
Found initrd image: /boot/initramfs-4.0.5-300.fc22.x86_64.img
Found linux image: /boot/vmlinuz-4.0.4-303.fc22.x86_64
Found initrd image: /boot/initramfs-4.0.4-303.fc22.x86_64.img
Found linux image: /boot/vmlinuz-0-rescue-78d35fd9338c44f992ad2301a737fcaa
Found initrd image:
/boot/initramfs-0-rescue-78d35fd9338c44f992ad2301a737fcaa.img
done
Verifying : xorg-x11-drv-nvidia-1:346.72-1.fc22.x86_64
1/14
Verifying : xorg-x11-drv-nvidia-libs-1:346.72-1.fc22.x86_64
2/14
Verifying : akmod-nvidia-1:346.72-2.fc22.1.x86_64
3/14
Verifying : kmodtool-1-23.fc22.noarch
4/14
Verifying : akmods-0.5.2-1.fc22.noarch
5/14
Verifying : xorg-x11-drv-nvidia-kmodsrc-1:346.72-1.fc22.x86_64
6/14
Verifying : gcc-5.1.1-4.fc22.x86_64
7/14
Verifying : libmpc-1.0.2-3.fc22.x86_64
8/14
Verifying : cpp-5.1.1-4.fc22.x86_64
9/14
Verifying : glibc-devel-2.21-5.fc22.x86_64
10/14
Verifying : isl-0.14-3.fc22.x86_64
11/14
Verifying : kernel-debug-devel-4.0.6-300.fc22.x86_64
12/14
Verifying : glibc-headers-2.21-5.fc22.x86_64
13/14
Verifying : kernel-headers-4.0.6-300.fc22.x86_64
14/14
Installed:
akmod-nvidia.x86_64 1:346.72-2.fc22.1
akmods.noarch 0.5.2-1.fc22
cpp.x86_64 5.1.1-4.fc22
gcc.x86_64 5.1.1-4.fc22
glibc-devel.x86_64 2.21-5.fc22
glibc-headers.x86_64 2.21-5.fc22
isl.x86_64 0.14-3.fc22
kernel-debug-devel.x86_64 4.0.6-300.fc22
kernel-headers.x86_64 4.0.6-300.fc22
kmodtool.noarch 1-23.fc22
libmpc.x86_64 1.0.2-3.fc22
xorg-x11-drv-nvidia.x86_64 1:346.72-1.fc22
xorg-x11-drv-nvidia-kmodsrc.x86_64 1:346.72-1.fc22
xorg-x11-drv-nvidia-libs.x86_64 1:346.72-1.fc22
Complete!
root@snoopy 14:11:45 ~ # systemctl enable akmods.service
root@snoopy 14:11:49 ~ # systemctl enable akmods-shutdown.service
root@snoopy 14:11:52 ~ # akmods --force
Checking kmods exist for 4.0.6-300.fc22.x86_64 [ OK ]
Files needed for building modules against kernel
4.0.6-300.fc22.x86_64 could not be found as the following
directories are missing:
/usr/src/kernels/4.0.6-300.fc22.x86_64/
/usr/lib/modules/4.0.6-300.fc22.x86_64/build/Is the correct[FAILED]devel
package installed?
So, even manually forcing the rebuild of the kernel module failed. It
complains that it needs the headers / devel package even though it was
clearly installed by dnf along with the akmod package?
Thanks,
Chris R.
1:20 p.m.
New subject: F22 Black Screen with nVidia drivers
kernel-devel != kernel-debug-devel
Am 06.07.2015 um 15:18 schrieb Christopher Ross:
kernel-debug-devel x86_64
4.0.6-300.fc22 updates 9.5 M
kernel-headers x86_64
4.0.6-300.fc22 updates 996 k
So, even manually forcing the rebuild of the kernel module failed. It
complains that it needs the headers / devel package even though it was
clearly installed by dnf along with the akmod package?
1:24 p.m.
New subject: F22 Black Screen with nVidia drivers
Picking up the akmod failure I find this:
root@snoopy 14:11:52 ~ # akmods --force
Checking kmods exist for 4.0.6-300.fc22.x86_64 [ OK ]
Files needed for building modules against kernel
4.0.6-300.fc22.x86_64 could not be found as the following
directories are missing:
/usr/src/kernels/4.0.6-300.fc22.x86_64/
/usr/lib/modules/4.0.6-300.fc22.x86_64/build/Is the correct[FAILED]devel
package installed?
root@snoopy 14:12:53 ~ #
root@snoopy 14:20:05 ~ # la /usr/src/kernels/4.0.6-300.fc22.x86_64/
ls: cannot access /usr/src/kernels/4.0.6-300.fc22.x86_64/: No such file
or directory
root@snoopy 14:20:17 ~ # la /usr/src/kernels/
total 4.0K
drwxr-xr-x. 22 root root 4.0K Jul 6 14:11 4.0.6-300.fc22.x86_64+debug
So it cannot build the modules because there is no
/usr/src/kernels/4.0.6-300.fc22.x86_64/
But there is a 4.0.6-300.fc22.x86_64+debug
Does this mean I installed the wrong kernel and/or headers? If so, it
wasn't on purpose. I've never told dnf which kernels to install, it's
always chosen that by itself.
Thanks,
Chris R.
1:31 p.m.
New subject: F22 Black Screen with nVidia drivers
On Mon, Jul 6, 2015 at 8:24 AM, Christopher Ross <fdra6390(a)tebibyte.org>
wrote:
Picking up the akmod failure I find this:
root@snoopy 14:11:52 ~ # akmods --force
Checking kmods exist for 4.0.6-300.fc22.x86_64 [ OK ]
Files needed for building modules against kernel
4.0.6-300.fc22.x86_64 could not be found as the following
directories are missing:
/usr/src/kernels/4.0.6-300.fc22.x86_64/
/usr/lib/modules/4.0.6-300.fc22.x86_64/build/Is the correct[FAILED]devel
package installed?
root@snoopy 14:12:53 ~ #
root@snoopy 14:20:05 ~ # la /usr/src/kernels/4.0.6-300.fc22.x86_64/
ls: cannot access /usr/src/kernels/4.0.6-300.fc22.x86_64/: No such file or
directory
root@snoopy 14:20:17 ~ # la /usr/src/kernels/
total 4.0K
drwxr-xr-x. 22 root root 4.0K Jul 6 14:11 4.0.6-300.fc22.x86_64+debug
So it cannot build the modules because there is no
/usr/src/kernels/4.0.6-300.fc22.x86_64/
But there is a 4.0.6-300.fc22.x86_64+debug
Does this mean I installed the wrong kernel and/or headers? If so, it
wasn't on purpose. I've never told dnf which kernels to install, it's
always chosen that by itself.
I think you've been bitten by a recent bug that's cropped up with dnf. Yum
chose the shorted name by default that met a particular requirement so
kernel-devel was chosen over kernel-debug-devel, but dnf doesn't do this.
Dnf isn't "wrong" but it does create a serious inconvenience.
To make matters worse (I ran into this on a F21 laptop) if the debug kernel
is installed and loaded you can't uninstall it. You have to boot to a
previous kernel first.
Try this:
$ rpm -qa | grep kernel
If you see a bunch of debug packages then that's what's going on. You need
to reboot to a previous kernel, uninstall them, reboot to the new kernel
and install "kernel-devel".
Since I've gotten the question multiple times I'll reiterate here, I can't
just add "Requires: kernel-devel" to the akmods package because it doesn't
cover kernel variants such as a PAE kernel, etc.
The problem is both kernel-devel and kernel-debug-devel provide the same
capability and dnf chooses the debug package whereas yum chose the
non-debug package. I'm considering add a conflict with the debug package to
akmods but that means if you really WANT to install it and you have the
akmods package installed you can't have both at the same time.
Thanks,
Richard
1:36 p.m.
New subject: F22 Black Screen with nVidia drivers
On 06/07/15 14:31, Richard Shaw wrote:
I think you've been bitten by a recent bug that's cropped up
with dnf.
Yum chose the shorted name by default that met a particular requirement
so kernel-devel was chosen over kernel-debug-devel, but dnf doesn't do
this. Dnf isn't "wrong" but it does create a serious inconvenience.
To make matters worse (I ran into this on a F21 laptop) if the debug
kernel is installed and loaded you can't uninstall it. You have to boot
to a previous kernel first.
Try this:
$ rpm -qa | grep kernel
I get this:
root@snoopy 14:34:08 ~ # rpm -qa | grep kernel
kernel-modules-4.0.4-303.fc22.x86_64
kernel-modules-extra-4.0.6-300.fc22.x86_64
kernel-modules-4.0.5-300.fc22.x86_64
kernel-debug-devel-4.0.6-300.fc22.x86_64
kernel-4.0.5-300.fc22.x86_64
kernel-headers-4.0.6-300.fc22.x86_64
kernel-4.0.4-303.fc22.x86_64
kernel-core-4.0.5-300.fc22.x86_64
kernel-4.0.6-300.fc22.x86_64
abrt-addon-kerneloops-2.6.0-1.fc22.x86_64
kernel-modules-extra-4.0.5-300.fc22.x86_64
kernel-modules-extra-4.0.4-303.fc22.x86_64
kernel-modules-4.0.6-300.fc22.x86_64
libreport-plugin-kerneloops-2.6.0-1.fc22.x86_64
kernel-core-4.0.4-303.fc22.x86_64
kernel-core-4.0.6-300.fc22.x86_64
So presumably I need to 'dnf remove kernel-debug-devel-4.0.6-300'
Is that correct?
Thanks,
Chris R.
1:41 p.m.
New subject: F22 Black Screen with nVidia drivers
Am 06.07.2015 um 15:31 schrieb Richard Shaw:
I think you've been bitten by a recent bug that's cropped up
with dnf.
Yum chose the shorted name by default that met a particular requirement
so kernel-devel was chosen over kernel-debug-devel, but dnf doesn't do
this. Dnf isn't "wrong" but it does create a serious inconvenience
DNF *is wrong* because it is a behavior change resulting in *completly*
wrong packages got installed and there is *zero excuse* to pull
kernel-devel-debug without having kernel-devel installed
1:42 p.m.
New subject: F22 Black Screen with nVidia drivers
Am 06.07.2015 um 15:41 schrieb Reindl Harald:
Am 06.07.2015 um 15:31 schrieb Richard Shaw:
> I think you've been bitten by a recent bug that's cropped up with dnf.
> Yum chose the shorted name by default that met a particular requirement
> so kernel-devel was chosen over kernel-debug-devel, but dnf doesn't do
> this. Dnf isn't "wrong" but it does create a serious inconvenience
DNF *is wrong* because it is a behavior change resulting in *completly*
wrong packages got installed and there is *zero excuse* to pull
kernel-devel-debug without having kernel-devel installed
- without having kernel-devel installed
+ without having kernel-debug installed
1:56 p.m.
New subject: F22 Black Screen with nVidia drivers
On 06/07/15 14:31, Richard Shaw wrote:
I think you've been bitten by a recent bug that's cropped up
with dnf.
Yum chose the shorted name by default that met a particular requirement
so kernel-devel was chosen over kernel-debug-devel, but dnf doesn't do
this. Dnf isn't "wrong" but it does create a serious inconvenience.
In my case the machine is running the non-debug kernel but installing
xorg-x11-drv-nvidia brought in the debug headers. I installed the
non-debug headers too and now the module builds.
root@snoopy 14:51:53 ~ # dnf install kernel-devel
Last metadata expiration check performed 1:23:10 ago on Mon Jul 6
13:28:58 2015.
Dependencies resolved.
===================================================================================================================================
Package Arch Version
Repository Size
===================================================================================================================================
Installing:
kernel-devel x86_64
4.0.6-300.fc22 updates 9.4 M
Transaction Summary
===================================================================================================================================
Install 1 Package
Total download size: 9.4 M
Installed size: 35 M
Is this ok [y/N]: y
Downloading Packages:
kernel-devel-4.0.6-300.fc22.x86_64.rpm
996 kB/s | 9.4 MB 00:09
-----------------------------------------------------------------------------------------------------------------------------------
Total
864 kB/s | 9.4 MB 00:11
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Installing : kernel-devel-4.0.6-300.fc22.x86_64
1/1
Verifying : kernel-devel-4.0.6-300.fc22.x86_64
1/1
Installed:
kernel-devel.x86_64 4.0.6-300.fc22
Complete!
root@snoopy 14:52:34 ~ # !la
la /usr/src/kernels/
total 8.0K
drwxr-xr-x. 22 root root 4.0K Jul 6 14:11 4.0.6-300.fc22.x86_64+debug
drwxr-xr-x. 22 root root 4.0K Jul 6 14:52 4.0.6-300.fc22.x86_64
root@snoopy 14:52:39 ~ # !ak
akmods --force
Checking kmods exist for 4.0.6-300.fc22.x86_64 [ OK ]
Building and installing nvidia-kmod [ OK ]
Sadly, I can't check right now whether X can now happily use the nVidia
drivers.
Thanks,
Chris R.
2:13 p.m.
New subject: F22 Black Screen with nVidia drivers
On Mon, Jul 06, 2015 at 03:42:26PM +0200, Reindl Harald wrote:
Am 06.07.2015 um 15:41 schrieb Reindl Harald:
>Am 06.07.2015 um 15:31 schrieb Richard Shaw:
>>I think you've been bitten by a recent bug that's cropped up with dnf.
>>Yum chose the shorted name by default that met a particular requirement
>>so kernel-devel was chosen over kernel-debug-devel, but dnf doesn't do
>>this. Dnf isn't "wrong" but it does create a serious inconvenience
>
>DNF *is wrong* because it is a behavior change resulting in *completly*
>wrong packages got installed and there is *zero excuse* to pull
>kernel-devel-debug without having kernel-devel installed
- without having kernel-devel installed
+ without having kernel-debug installed
Agreed. Is the BZ somewhere, I think this is a valid bug.
--
Suvayu
Open source is the future. It sets us free.
9:09 a.m.
New subject: F22 Black Screen with nVidia drivers
On 06/07/15 14:56, Christopher Ross wrote:
On 06/07/15 14:31, Richard Shaw wrote:
> I think you've been bitten by a recent bug that's cropped up with dnf.
> Yum chose the shorted name by default that met a particular requirement
> so kernel-devel was chosen over kernel-debug-devel, but dnf doesn't do
> this. Dnf isn't "wrong" but it does create a serious inconvenience.
>
In my case the machine is running the non-debug kernel but installing
xorg-x11-drv-nvidia brought in the debug headers. I installed the
non-debug headers too and now the module builds.
[... snip ...]
akmods --force
Checking kmods exist for 4.0.6-300.fc22.x86_64 [ OK ]
Building and installing nvidia-kmod [ OK ]
Sadly, I can't check right now whether X can now happily use the nVidia
drivers.
OK, so I have had opportunity to reboot the machine but now it is coming
up in text mode.
The nVidia modules exist now
root@snoopy 10:03:29 ~ # locate nvidia_drv
/usr/lib64/dri/nvidia_drv_video.so
/usr/lib64/xorg/modules/drivers/nvidia_drv.so
But X is still trying to use nouveau. What is the missing step to tell X
to use the nVidia drivers instead?
[107131.379] (II) "glx" will be loaded by default.
[107131.379] (II) LoadModule: "glx"
[107131.379] (II) Loading /usr/lib64/nvidia/xorg/libglx.so
[107131.384] (II) Module glx: vendor="NVIDIA Corporation"
[107131.384] compiled for 4.0.2, module version = 1.0.0
[107131.384] Module class: X.Org Server Extension
[107131.384] (II) NVIDIA GLX Module 346.72 Tue May 5 17:11:15 PDT 2015
[107131.384] (==) Matched nouveau as autoconfigured driver 0
[107131.384] (==) Matched nv as autoconfigured driver 1
[107131.384] (==) Matched nouveau as autoconfigured driver 2
[107131.384] (==) Matched nv as autoconfigured driver 3
[107131.384] (==) Matched modesetting as autoconfigured driver 4
[107131.384] (==) Matched fbdev as autoconfigured driver 5
[107131.384] (==) Matched vesa as autoconfigured driver 6
[107131.384] (==) Assigned the driver to the xf86ConfigLayout
[107131.384] (II) LoadModule: "nouveau"
[107131.384] (II) Loading /usr/lib64/xorg/modules/drivers/nouveau_drv.so
[107131.384] (II) Module nouveau: vendor="X.Org Foundation"
[107131.384] compiled for 1.17.1, module version = 1.0.11
[107131.384] Module class: X.Org Video Driver
[107131.384] ABI class: X.Org Video Driver, version 19.0
[107131.384] (II) LoadModule: "nv"
[107131.384] (WW) Warning, couldn't open module nv
[107131.384] (II) UnloadModule: "nv"
[107131.384] (II) Unloading nv
[107131.384] (EE) Failed to load module "nv" (module does not exist, 0)
[107131.384] (II) LoadModule: "modesetting"
[107131.384] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
[107131.384] (II) Module modesetting: vendor="X.Org Foundation"
[107131.384] compiled for 1.17.2, module version = 1.17.2
[107131.384] Module class: X.Org Video Driver
[107131.384] ABI class: X.Org Video Driver, version 19.0
[107131.384] (II) LoadModule: "fbdev"
[107131.384] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so
[107131.384] (II) Module fbdev: vendor="X.Org Foundation"
[107131.384] compiled for 1.17.1, module version = 0.4.3
[107131.384] Module class: X.Org Video Driver
[107131.384] ABI class: X.Org Video Driver, version 19.0
[107131.384] (II) LoadModule: "vesa"
[107131.384] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
[107131.384] (II) Module vesa: vendor="X.Org Foundation"
[107131.384] compiled for 1.17.1, module version = 2.3.2
[107131.384] Module class: X.Org Video Driver
[107131.384] ABI class: X.Org Video Driver, version 19.0
[107131.384] (II) NOUVEAU driver
[107131.384] (II) NOUVEAU driver for NVIDIA chipset families :
[107131.384] RIVA TNT (NV04)
[107131.384] RIVA TNT2 (NV05)
[107131.384] GeForce 256 (NV10)
[107131.384] GeForce 2 (NV11, NV15)
[107131.384] GeForce 4MX (NV17, NV18)
[107131.384] GeForce 3 (NV20)
[107131.384] GeForce 4Ti (NV25, NV28)
[107131.384] GeForce FX (NV3x)
[107131.385] GeForce 6 (NV4x)
[107131.385] GeForce 7 (G7x)
[107131.385] GeForce 8 (G8x)
[107131.385] GeForce GTX 200 (NVA0)
[107131.385] GeForce GTX 400 (NVC0)
[107131.385] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[107131.385] (II) FBDEV: driver for framebuffer: fbdev
[107131.385] (II) VESA: driver for VESA chipsets: vesa
[107131.385] (++) using VT number 1
[107131.385] (II) [drm] nouveau interface version: 1.2.1
[107131.385] (WW) Falling back to old probe method for modesetting
[107131.385] (WW) Falling back to old probe method for fbdev
[107131.385] (II) Loading sub module "fbdevhw"
[107131.385] (II) LoadModule: "fbdevhw"
[107131.385] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
[107131.385] (II) Module fbdevhw: vendor="X.Org Foundation"
[107131.385] compiled for 1.17.2, module version = 0.0.2
[107131.385] ABI class: X.Org Video Driver, version 19.0
[107131.385] (WW) Falling back to old probe method for vesa
[107131.385] (II) Loading sub module "dri2"
[107131.385] (II) LoadModule: "dri2"
[107131.385] (II) Module "dri2" already built-in
[107131.385] (--) NOUVEAU(0): Chipset: "NVIDIA NVE4"
[107131.385] (II) NOUVEAU(0): Creating default Display subsection in
Screen section
"Default Screen Section" for depth/fbbpp 24/32
[107131.385] (==) NOUVEAU(0): Depth 24, (--) framebuffer bpp 32
[107131.385] (==) NOUVEAU(0): RGB weight 888
[107131.385] (==) NOUVEAU(0): Default visual is TrueColor
[107131.385] (==) NOUVEAU(0): Using HW cursor
[107131.385] (==) NOUVEAU(0): GLX sync to VBlank enabled.
[107131.385] (==) NOUVEAU(0): Page flipping enabled
[107131.386] (==) NOUVEAU(0): Swap limit set to 1 [Max allowed 2]
[107131.386] (==) NOUVEAU(0): Page flipping synced to vblank by kernel.
[107131.386] (II) NOUVEAU(0): Initializing outputs ...
[107131.397] (II) NOUVEAU(0): Output DVI-I-1 has no monitor section
[107131.454] (II) NOUVEAU(0): Output DVI-D-1 has no monitor section
[107131.456] (II) NOUVEAU(0): Output HDMI-1 has no monitor section
[107131.488] (II) NOUVEAU(0): Output DP-1 has no monitor section
[107131.488] (II) NOUVEAU(0): 4 crtcs needed for screen.
[107131.490] (II) NOUVEAU(0): Allocated crtc nr. 0 to this screen.
[107131.490] (II) NOUVEAU(0): Allocated crtc nr. 1 to this screen.
[107131.490] (II) NOUVEAU(0): Allocated crtc nr. 2 to this screen.
[107131.490] (II) NOUVEAU(0): Allocated crtc nr. 3 to this screen.
[107131.501] (II) NOUVEAU(0): EDID for output DVI-I-1
[107131.559] (II) NOUVEAU(0): EDID for output DVI-D-1
[107131.559] (II) NOUVEAU(0): Manufacturer: APP Model: 9221 Serial#:
33702996
[107131.559] (II) NOUVEAU(0): Year: 2009 Week: 37
[107131.559] (II) NOUVEAU(0): EDID Version: 1.3
[107131.559] (II) NOUVEAU(0): Digital Display Input
[107131.559] (II) NOUVEAU(0): Max Image Size [cm]: horiz.: 64 vert.: 40
[107131.559] (II) NOUVEAU(0): Gamma: 2.20
[107131.559] (II) NOUVEAU(0): DPMS capabilities: Off
[107131.559] (II) NOUVEAU(0): Supported color encodings: RGB 4:4:4 YCrCb
4:4:4
[107131.559] (II) NOUVEAU(0): First detailed timing not preferred mode
in violation of standard!
[107131.559] (II) NOUVEAU(0): redX: 0.640 redY: 0.343 greenX: 0.292
greenY: 0.611
[107131.559] (II) NOUVEAU(0): blueX: 0.146 blueY: 0.074 whiteX: 0.313
whiteY: 0.329
[107131.559] (II) NOUVEAU(0): Manufacturer's mask: 0
[107131.559] (II) NOUVEAU(0): Supported detailed timing:
[107131.559] (II) NOUVEAU(0): clock: 71.0 MHz Image Size: 641 x 401 mm
[107131.559] (II) NOUVEAU(0): h_active: 1280 h_sync: 1328 h_sync_end
1360 h_blank_end 1440 h_border: 0
[107131.559] (II) NOUVEAU(0): v_active: 800 v_sync: 803 v_sync_end 809
v_blanking: 823 v_border: 0
[107131.559] (II) NOUVEAU(0): Supported detailed timing:
[107131.559] (II) NOUVEAU(0): clock: 268.0 MHz Image Size: 641 x 401 mm
[107131.559] (II) NOUVEAU(0): h_active: 2560 h_sync: 2608 h_sync_end
2640 h_blank_end 2720 h_border: 0
[107131.559] (II) NOUVEAU(0): v_active: 1600 v_sync: 1603 v_sync_end
1609 v_blanking: 1646 v_border: 0
[107131.559] (II) NOUVEAU(0): Serial No: CY937028XMP
[107131.559] (II) NOUVEAU(0): Monitor name: Cinema HD
[107131.559] (II) NOUVEAU(0): Number of EDID sections to follow: 1
[107131.559] (II) NOUVEAU(0): EDID (in hex):
[107131.559] (II) NOUVEAU(0): 00ffffffffffff000610219254440202
[107131.559] (II) NOUVEAU(0): 251301038040287828fe85a3574a9c25
[107131.559] (II) NOUVEAU(0): 13505400000001010101010101010101
[107131.559] (II) NOUVEAU(0): 010101010101bc1b00a0502017303020
[107131.559] (II) NOUVEAU(0): 360081912100001ab06800a0a0402e60
[107131.559] (II) NOUVEAU(0): 3020360081912100001a000000ff0043
[107131.559] (II) NOUVEAU(0): 59393337303238584d500a00000000fc
[107131.559] (II) NOUVEAU(0): 0043696e656d612048440a00000001bd
[107131.559] (II) NOUVEAU(0): 40010300000000c84801a500a5000102
[107131.559] (II) NOUVEAU(0): 031919a8000000000000400000000000
[107131.559] (II) NOUVEAU(0): 00000000000000000000000000000000
[107131.559] (II) NOUVEAU(0): 00000000000000000000000000000000
[107131.559] (II) NOUVEAU(0): 00000000000000000000000000000000
[107131.559] (II) NOUVEAU(0): 00000000000000000000000000000000
[107131.559] (II) NOUVEAU(0): 00000000000000000000000000000000
[107131.559] (II) NOUVEAU(0): 00000000000000000000000000000041
[107131.559] (II) NOUVEAU(0): Printing probed modes for output DVI-D-1
[107131.559] (II) NOUVEAU(0): Modeline "2560x1600"x59.9 268.00 2560
2608 2640 2720 1600 1603 1609 1646 +hsync -vsync (98.5 kHz e)
[107131.559] (II) NOUVEAU(0): Modeline "1280x800"x59.9 71.00 1280
1328 1360 1440 800 803 809 823 +hsync -vsync (49.3 kHz e)
[107131.560] (II) NOUVEAU(0): EDID for output HDMI-1
[107131.592] (II) NOUVEAU(0): EDID for output DP-1
[107131.592] (II) NOUVEAU(0): Output DVI-I-1 disconnected
[107131.592] (II) NOUVEAU(0): Output DVI-D-1 connected
[107131.592] (II) NOUVEAU(0): Output HDMI-1 disconnected
[107131.592] (II) NOUVEAU(0): Output DP-1 disconnected
[107131.592] (II) NOUVEAU(0): Using exact sizes for initial modes
[107131.592] (II) NOUVEAU(0): Output DVI-D-1 using initial mode
2560x1600 +0+0
[107131.592] (II) NOUVEAU(0): Using default gamma of (1.0, 1.0, 1.0)
unless otherwise stated.
[107131.592] (--) NOUVEAU(0): Virtual size is 2560x1600 (pitch 0)
[107131.592] (**) NOUVEAU(0): Driver mode "2560x1600": 268.0 MHz
(scaled from 0.0 MHz), 98.5 kHz, 59.9 Hz
[107131.592] (II) NOUVEAU(0): Modeline "2560x1600"x59.9 268.00 2560
2608 2640 2720 1600 1603 1609 1646 +hsync -vsync (98.5 kHz e)
[107131.592] (**) NOUVEAU(0): Driver mode "1280x800": 71.0 MHz (scaled
from 0.0 MHz), 49.3 kHz, 59.9 Hz
[107131.592] (II) NOUVEAU(0): Modeline "1280x800"x59.9 71.00 1280
1328 1360 1440 800 803 809 823 +hsync -vsync (49.3 kHz e)
[107131.592] (==) NOUVEAU(0): DPI set to (96, 96)
[107131.592] (II) Loading sub module "fb"
[107131.592] (II) LoadModule: "fb"
[107131.592] (II) Loading /usr/lib64/xorg/modules/libfb.so
[107131.592] (II) Module fb: vendor="X.Org Foundation"
[107131.592] compiled for 1.17.2, module version = 1.0.0
[107131.592] ABI class: X.Org ANSI C Emulation, version 0.4
[107131.592] (II) Loading sub module "shadowfb"
[107131.592] (II) LoadModule: "shadowfb"
[107131.592] (II) Loading /usr/lib64/xorg/modules/libshadowfb.so
[107131.592] (II) Module shadowfb: vendor="X.Org Foundation"
[107131.592] compiled for 1.17.2, module version = 1.0.0
[107131.592] ABI class: X.Org ANSI C Emulation, version 0.4
[107131.592] (II) UnloadModule: "modesetting"
[107131.592] (II) Unloading modesetting
[107131.592] (II) UnloadModule: "fbdev"
[107131.592] (II) Unloading fbdev
[107131.592] (II) UnloadSubModule: "fbdevhw"
[107131.592] (II) Unloading fbdevhw
[107131.592] (II) UnloadModule: "vesa"
[107131.592] (II) Unloading vesa
[107131.592] (--) Depth 24 pixmap format is 32 bpp
[107131.597] (II) NOUVEAU(0): Channel setup complete.
[107131.598] (II) NOUVEAU(0): [COPY] async initialised.
[107131.598] (II) NOUVEAU(0): [DRI2] Setup complete
[107131.598] (II) NOUVEAU(0): [DRI2] DRI driver: nouveau
[107131.598] (II) NOUVEAU(0): [DRI2] VDPAU driver: nouveau
Thanks,
Chris R.
9:12 a.m.
New subject: F22 Black Screen with nVidia drivers
Am 07.07.2015 um 11:09 schrieb Christopher Ross:
OK, so I have had opportunity to reboot the machine but now it is
coming
up in text mode.
But X is still trying to use nouveau. What is the missing step to tell X
to use the nVidia drivers instead?
every instruction how to install the nivida driver explains the
blacklisting like
http://askubuntu.com/questions/481414/install-nvidia-driver-instead-nouveau
9:13 a.m.
New subject: F22 Black Screen with nVidia drivers
On 07/07/15 17:09, Christopher Ross wrote:
But X is still trying to use nouveau. What is the missing step to
tell X to use the nVidia drivers instead?
Check the kernel parameters for the kernel being booted. It should look something like
this....
linux /vmlinuz-4.0.6-300.fc22.x86_64 root=UUID=5c59b39b-3c31-480a-9265
-5b25551eb64b ro rd.lvm.lv=fedora/swap rd.md=0 rd.dm=0 rd.luks=0 rhgb quiet nou
veau.modeset=0 rd.driver.blacklist=nouveau video=vesa:off LANG=en_US.UTF-8
9:30 a.m.
New subject: F22 Black Screen with nVidia drivers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/07/15 17:12, Reindl Harald wrote:
Am 07.07.2015 um 11:09 schrieb Christopher Ross:
> OK, so I have had opportunity to reboot the machine but now it is coming
> up in text mode.
>
> But X is still trying to use nouveau. What is the missing step to tell X
> to use the nVidia drivers instead?
every instruction how to install the nivida driver explains the blacklisting like
http://askubuntu.com/questions/481414/install-nvidia-driver-instead-nouveau
FWIW, I'm running F22 with the nVidia drivers and the file
/etc/modprobe.d/blacklist-nouveau.conf does not exist on my system.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlWbnD0ACgkQ4JnKjVbCBvp97wCfXd9Y/uDYKdyn2Sag9QsVOmp6
cd4An0vBYpj4SJbjlCdvk698TvmlPOu8
=3V5X
-----END PGP SIGNATURE-----
9:38 a.m.
New subject: F22 Black Screen with nVidia drivers
Am 07.07.2015 um 11:30 schrieb Ed Greshko:
On 07/07/15 17:12, Reindl Harald wrote:
> Am 07.07.2015 um 11:09 schrieb Christopher Ross:
>> OK, so I have had opportunity to reboot the machine but now it is coming
>> up in text mode.
>>
>> But X is still trying to use nouveau. What is the missing step to tell X
>> to use the nVidia drivers instead?
> every instruction how to install the nivida driver explains the blacklisting like
http://askubuntu.com/questions/481414/install-nvidia-driver-instead-nouveau
FWIW, I'm running F22 with the nVidia drivers and the file
/etc/modprobe.d/blacklist-nouveau.conf does not exist on my system.
the you have blacklisted it on the kernel line or the file just has a
different name, the point is that you need to blacklist it somehow
9:38 a.m.
New subject: F22 Black Screen with nVidia drivers
On 07/07/15 10:13, Ed Greshko wrote:
On 07/07/15 17:09, Christopher Ross wrote:
> But X is still trying to use nouveau. What is the missing step to tell X to use the
nVidia drivers instead?
Check the kernel parameters for the kernel being booted. It should look something like
this....
linux /vmlinuz-4.0.6-300.fc22.x86_64 root=UUID=5c59b39b-3c31-480a-9265
-5b25551eb64b ro rd.lvm.lv=fedora/swap rd.md=0 rd.dm=0 rd.luks=0 rhgb quiet nou
veau.modeset=0 rd.driver.blacklist=nouveau video=vesa:off LANG=en_US.UTF-8
Simply installing the nvidia modules has set that automagically in the past.
root@snoopy 10:37:34 grub2 # grep "nouveau" /boot/grub2/grub.cfg
linux16 /vmlinuz-4.0.6-300.fc22.x86_64
root=/dev/mapper/fedora_snoopy-root ro rd.lvm.lv=fedora_snoopy/swap
rd.lvm.lv=fedora_snoopy/root rhgb quiet nouveau.modeset=0
rd.driver.blacklist=nouveau video=vesa:off
Regards,
Chris R.
9:47 a.m.
New subject: F22 Black Screen with nVidia drivers
On 07/07/15 17:38, Christopher Ross wrote:
On 07/07/15 10:13, Ed Greshko wrote:
> On 07/07/15 17:09, Christopher Ross wrote:
>> But X is still trying to use nouveau. What is the missing step to tell X to use
the nVidia drivers instead?
>
> Check the kernel parameters for the kernel being booted. It should look something
like this....
>
> linux /vmlinuz-4.0.6-300.fc22.x86_64 root=UUID=5c59b39b-3c31-480a-9265
> -5b25551eb64b ro rd.lvm.lv=fedora/swap rd.md=0 rd.dm=0 rd.luks=0 rhgb quiet nou
> veau.modeset=0 rd.driver.blacklist=nouveau video=vesa:off LANG=en_US.UTF-8
>
Simply installing the nvidia modules has set that automagically in the past.
root@snoopy 10:37:34 grub2 # grep "nouveau" /boot/grub2/grub.cfg
linux16 /vmlinuz-4.0.6-300.fc22.x86_64 root=/dev/mapper/fedora_snoopy-root ro
rd.lvm.lv=fedora_snoopy/swap rd.lvm.lv=fedora_snoopy/root rhgb quiet nouveau.modeset=0
rd.driver.blacklist=nouveau video=vesa:off
Yes, and it continues to do so.
Not having that set would seem to indicate that the install by the OP failed in some why.
9:48 a.m.
New subject: F22 Black Screen with nVidia drivers
On 07/07/15 10:38, Reindl Harald wrote:
Am 07.07.2015 um 11:30 schrieb Ed Greshko:
> On 07/07/15 17:12, Reindl Harald wrote:
>
>> Am 07.07.2015 um 11:09 schrieb Christopher Ross:
>>> But X is still trying to use nouveau. What is the missing step to
>>> tell X
>>> to use the nVidia drivers instead?
>
>> every instruction how to install the nivida driver explains the
>> blacklisting like
>> http://askubuntu.com/questions/481414/install-nvidia-driver-instead-nouveau
>>
>
>
> FWIW, I'm running F22 with the nVidia drivers and the file
> /etc/modprobe.d/blacklist-nouveau.conf does not exist on my system.
the you have blacklisted it on the kernel line or the file just has a
different name, the point is that you need to blacklist it somehow
I created the /etc/modprobe.d/blacklist-nouveau as per your suggestion,
checked the kernel command line, and rebooted.
The command line is clearly listed at the top of Xorg.0.log as
[ 13.863] Current Operating System: Linux snoopy.tebibyte.org
4.0.6-300.fc22.x86_64 #1 SMP Tue Jun 23 13:58:53 UTC 2015 x86_64
[ 13.863] Kernel command line:
BOOT_IMAGE=/vmlinuz-4.0.6-300.fc22.x86_64
root=/dev/mapper/fedora_snoopy-root ro rd.lvm.lv=fedora
_snoopy/swap rd.lvm.lv=fedora_snoopy/root rhgb quiet nouveau.modeset=0
rd.driver.blacklist=nouveau video=vesa:off
[
But X is still loading nouveau as per my earlier message.
Previously I found that when I uninstall nouveau completely, X still
tries to load it but fails (see log in my earlier message).
Thanks,
Chris R.
3210
days inactive
3211
days old
rpmfusion-users@lists.rpmfusion.org
17 comments
5 participants
participants (5)
-
Christopher Ross -
Ed Greshko -
Reindl Harald -
Richard Shaw -
Suvayu Ali