[F25, KDE] Cannot start login manager anymore

[Frédéric Bron]

Hi,

I am using a fresh updated install with kernel 4.9.11.
The system starts but comes to a black screen. I am only able to login
in text mode with Ctrl+Alt+F2.

I tried to start with older kernels since I started to have some
issues with 4.9.9 but I have now only 4.9.9, 4.9.10 and 4.9.11 and all
give the same black screen. I have not 4.9.8 anymore in the list.

I am using the nvidia driver.

What should I do?

Frédéric

[Earl A Ramirez]

>  I am using the nvidia driver.
>
>  
Did you blacklist the nouveau drivers from the kernel argument?
-- 
Kind Regards
Earl Ramirez

[Frédéric Bron]

>  Did you blacklist the nouveau drivers from the kernel argument?
I do not know how to do that.

Frédéric

[Ed Greshko]

On 02/28/17 01:00, Frédéric Bron wrote:
>  I am using a fresh updated install with kernel 4.9.11.
>  The system starts but comes to a black screen. I am only able to login
>  in text mode with Ctrl+Alt+F2.
>
>  I tried to start with older kernels since I started to have some
>  issues with 4.9.9 but I have now only 4.9.9, 4.9.10 and 4.9.11 and all
>  give the same black screen. I have not 4.9.8 anymore in the list.
>
>  I am using the nvidia driver.
>
>  What should I do? 
What versions of the plasma-* and kf5-* packages are you running?

If you check over at the KDE mailing list you'll find a discussion on
the issue you describe. 

Updates to plasma 5.8.6-2 and 5.8.6-3  as well as kf5 16.12.2-1 has
cleared up the problem for most, if not all, who have run into it.

Not sure if these have been pushed to stable as of yet.  But you could
enable updates-testing and they should be there.

-- 
Fedora Users List - The place to go to get others to do the work for you

[Frédéric Bron]

>  Updates to plasma 5.8.6-2 and 5.8.6-3  as well as kf5 16.12.2-1 has
>  cleared up the problem for most, if not all, who have run into it. 
How do I get those from -testing?
When everything will be cleaned, how will I switch back to standard repository?
Regards,

Frédéric

[Ed Greshko]

On 02/28/17 14:12, Frédéric Bron wrote:
> > Updates to plasma 5.8.6-2 and 5.8.6-3  as well as kf5 16.12.2-1
> has
> > cleared up the problem for most, if not all, who have run into it.
>  How do I get those from -testing?
>  When everything will be cleaned, how will I switch back to standard repository?
>  Regards, 
First make sure it isn't an selinux issue before going this route.  See
if you have an AVC record as indicated in another post.

-- 
Fedora Users List - The place to go to get others to do the work for you

[Alex Gurenko]

Yes, I don't see them in testing as well and I've installed manually
*-11.fc25 packages and problems are resolved now.

*---*

*Yours truly, Alex*


On Tue, Feb 28, 2017 at 8:17 AM, Ed Greshko <ed.greshko(a)greshko.com&gt; wrote:

>  On 02/28/17 14:12, Frédéric Bron wrote:
>  >> Updates to plasma 5.8.6-2 and 5.8.6-3  as well as kf5 16.12.2-1 has
>  >> cleared up the problem for most, if not all, who have run into it.
>  > How do I get those from -testing?
>  > When everything will be cleaned, how will I switch back to standard
>  repository?
>  > Regards,
>
>  First make sure it isn't an selinux issue before going this route.  See
>  if you have an AVC record as indicated in another post.
>
>  --
>  Fedora Users List - The place to go to get others to do the work for you
>  _______________________________________________
>  users mailing list -- users(a)lists.fedoraproject.org
>  To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
>

[Frédéric Bron]

this time, I get something:

ausearch -c 'modprobe' --raw

type=AVC msg=audit(1488267562.486:426): avc:  denied  { module_load }
for  pid=2330 comm="modprobe"
path="/usr/lib/modules/4.9.11-200.fc25.x86_64/extra/nvidia/nvidia.ko"
dev="sda2" ino=5528689
scontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
tcontext=system_u:object_r:modules_object_t:s0 tclass=system
permissive=0
type=AVC msg=audit(1488267578.701:427): avc:  denied  { module_load }
for  pid=2332 comm="modprobe"
path="/usr/lib/modules/4.9.11-200.fc25.x86_64/extra/nvidia/nvidia.ko"
dev="sda2" ino=5528689
scontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
tcontext=system_u:object_r:modules_object_t:s0 tclass=system
permissive=0

2017-02-28 7:17 GMT+01:00 Ed Greshko <ed.greshko(a)greshko.com&gt;:
>  On 02/28/17 14:12, Frédéric Bron wrote:
> >> Updates to plasma 5.8.6-2 and 5.8.6-3  as well as kf5 16.12.2-1 has
> >> cleared up the problem for most, if not all, who have run into it.
> > How do I get those from -testing?
> > When everything will be cleaned, how will I switch back to standard repository?
> > Regards,
>
>  First make sure it isn't an selinux issue before going this route.  See
>  if you have an AVC record as indicated in another post.
>
>  --
>  Fedora Users List - The place to go to get others to do the work for you
>  _______________________________________________
>  users mailing list -- users(a)lists.fedoraproject.org
>  To unsubscribe send an email to users-leave(a)lists.fedoraproject.org 


-- 
Frédéric Bron

-----------------------------------------------------------
Frédéric Bron (frederic.bron(a)m4x.org)
Villa des 4 chemins, Centre Hospitalier, BP 208
38506 Voiron Cedex
tél. fixe : [phone], tél. port.: [phone]

[Frédéric Bron]

I downloaded selinux-policy 3.13.1-225.11 and tried to install it but
I get an error:

# dnf install selinux-policy-3.13.1-225.11.fc25.noarch.rpm
Vérification de l'expiration des métadonnées effectuée il y a 2:42:17
sur Tue Feb 28 07:00:09 2017.
Erreur : package selinux-policy-targeted-3.13.1-225.10.fc25.noarch
requires selinux-policy = 3.13.1-225.10.fc25, but none of the
providers can be installed

Stange because .10 is installed:
# dnf info selinux-policy
Vérification de l'expiration des métadonnées effectuée il y a 2:48:31
sur Tue Feb 28 07:00:09 2017.
Paquets installés
Nom         : selinux-policy
Architectur : noarch
Époque      : 0
Version     : 3.13.1
Révision    : 225.10.fc25
Taille      : 20 k
Dépôt       : @System
Depuis le d : updates

[Ed Greshko]

On 02/28/17 16:49, Frédéric Bron wrote:
>  I downloaded selinux-policy 3.13.1-225.11 and tried to install it
> but
>  I get an error:
>
>  # dnf install selinux-policy-3.13.1-225.11.fc25.noarch.rpm
>  Vérification de l'expiration des métadonnées effectuée il y a 2:42:17
>  sur Tue Feb 28 07:00:09 2017.
>  Erreur : package selinux-policy-targeted-3.13.1-225.10.fc25.noarch
>  requires selinux-policy = 3.13.1-225.10.fc25, but none of the
>  providers can be installed 
You need to find out all of the selinux-policy packages you have
installed and update them all....

[egreshko@meimei akmods]$ rpm -qa | grep selinux-pol
selinux-policy-devel-3.13.1-225.11.fc25.noarch
selinux-policy-targeted-3.13.1-225.11.fc25.noarch
selinux-policy-doc-3.13.1-225.11.fc25.noarch
selinux-policy-sandbox-3.13.1-225.11.fc25.noarch
selinux-policy-3.13.1-225.11.fc25.noarch

Are the 5 on my system that need to be updated


-- 
Fedora Users List - The place to go to get others to do the work for you

[Frédéric Bron]

Thanks, eventually, it works again!
I had to install manually both selinux-policy and
selinux-policy-targeted in version 3.13.1-225.11 downloaded from
https://dl.fedoraproject.org/pub/fedora/linux/updates/testing/25/x86_64/s/.

Thanks a lot for your support.

Frédéric

[Ed Greshko]

On Feb 28, 2017 6:50 PM, "Frédéric Bron" <frederic.bron(a)m4x.org&gt; wrote:

Thanks, eventually, it works again!
I had to install manually both selinux-policy and
selinux-policy-targeted in version 3.13.1-225.11 downloaded from
https://dl.fedoraproject.org/pub/fedora/linux/updates/testing/25/x86_64/s/.

Thanks a lot for your support.

You're welcome. Happy to hear everything is working again.

[Ed Greshko]

On 02/28/17 16:20, Frédéric Bron wrote:
>  this time, I get something:
>
>  ausearch -c 'modprobe' --raw
>
>  type=AVC msg=audit(1488267562.486:426): avc:  denied  { module_load }
>  for  pid=2330 comm="modprobe"
>  path="/usr/lib/modules/4.9.11-200.fc25.x86_64/extra/nvidia/nvidia.ko"
>  dev="sda2" ino=5528689
>  scontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
>  tcontext=system_u:object_r:modules_object_t:s0 tclass=system
>  permissive=0
>  type=AVC msg=audit(1488267578.701:427): avc:  denied  { module_load }
>  for  pid=2332 comm="modprobe"
>  path="/usr/lib/modules/4.9.11-200.fc25.x86_64/extra/nvidia/nvidia.ko"
>  dev="sda2" ino=5528689
>  scontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
>  tcontext=system_u:object_r:modules_object_t:s0 tclass=system
>  permissive=0 

Yep....

So.....  go get and install the selinux-policy packages and you will be
fine.

-- 
Fedora Users List - The place to go to get others to do the work for you

[Ed Greshko]

On 02/28/17 01:00, Frédéric Bron wrote:
>  I am using the nvidia driver. 

You also may have been bitten by an selinux bug.  Check to see if the
nvidia module has been loaded...

lsmod | grep nvidia

If not...see https://bugzilla.redhat.com/show_bug.cgi?id=1426906 and get
the latest selinux policy packages

-- 
Fedora Users List - The place to go to get others to do the work for you

[Alex Gurenko]

 I have similar issues, with all latest packages selinux still gives all
kind of errors including error in building module, modprobe and switching
to nvidia graphics with bumblebee.
 setenforce 0 allows to do all these things, but when I set it back, it
unloads module...

*---*

*Yours truly, Alex*


On Tue, Feb 28, 2017 at 4:31 AM, Ed Greshko <ed.greshko(a)greshko.com&gt; wrote:

>  On 02/28/17 01:00, Frédéric Bron wrote:
>  > I am using the nvidia driver.
>
>
>  You also may have been bitten by an selinux bug.  Check to see if the
>  nvidia module has been loaded...
>
>  lsmod | grep nvidia
>
>  If not...see https://bugzilla.redhat.com/show_bug.cgi?id=1426906 and get
>  the latest selinux policy packages
>
>  --
>  Fedora Users List - The place to go to get others to do the work for you
>  _______________________________________________
>  users mailing list -- users(a)lists.fedoraproject.org
>  To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
>

[Ed Greshko]

On 02/28/17 13:52, Alex Gurenko wrote:
>   I have similar issues, with all latest packages selinux still gives
>  all kind of errors including error in building module, modprobe and
>  switching to nvidia graphics with bumblebee.
>   setenforce 0 allows to do all these things, but when I set it back,
>  it unloads module...
>  
Are these the versions you have installed?


selinux-policy-devel-3.13.1-225.11.fc25.noarch
selinux-policy-targeted-3.13.1-225.11.fc25.noarch
selinux-policy-doc-3.13.1-225.11.fc25.noarch
selinux-policy-sandbox-3.13.1-225.11.fc25.noarch
selinux-policy-3.13.1-225.11.fc25.noarch

-- 
Fedora Users List - The place to go to get others to do the work for you

[Frédéric Bron]

>  Are these the versions you have installed?
>  selinux-policy-devel-3.13.1-225.11.fc25.noarch
>  selinux-policy-targeted-3.13.1-225.11.fc25.noarch
>  selinux-policy-doc-3.13.1-225.11.fc25.noarch
>  selinux-policy-sandbox-3.13.1-225.11.fc25.noarch
>  selinux-policy-3.13.1-225.11.fc25.noarch 
not exactly: they are all 3.13.1-225.10.

Frédéric

[Ed Greshko]

On 02/28/17 14:06, Frédéric Bron wrote:
> > Are these the versions you have installed?
> > selinux-policy-devel-3.13.1-225.11.fc25.noarch
> > selinux-policy-targeted-3.13.1-225.11.fc25.noarch
> > selinux-policy-doc-3.13.1-225.11.fc25.noarch
> > selinux-policy-sandbox-3.13.1-225.11.fc25.noarch
> > selinux-policy-3.13.1-225.11.fc25.noarch
>  not exactly: they are all 3.13.1-225.10.
>  
OK....

It is supposed to be in updates-testing but I don't see them there as of
yet.

You can manually download and then install from here....

https://koji.fedoraproject.org/koji/buildinfo?buildID=862494

-- 
Fedora Users List - The place to go to get others to do the work for you

[Frédéric Bron]

> > I am using the nvidia driver.
>  You also may have been bitten by an selinux bug.  Check to see if the
>  nvidia module has been loaded...
>
>  lsmod | grep nvidia 
lsmod | grep nvidia
gives nothing...

[Ed Greshko]

On 02/28/17 14:02, Frédéric Bron wrote:
> >> I am using the nvidia driver.
> > You also may have been bitten by an selinux bug.  Check to see if the
> > nvidia module has been loaded...
> >
> > lsmod | grep nvidia
>  lsmod | grep nvidia
>  gives nothing...
>  _______________________________________________ 
OK....  Sounds like you're getting the selinux issue....

If you do "ausearch -c 'modprobe' --raw" you would see something
*similar* to this....

type=AVC msg=audit(1488120127.660:812): avc:  denied  { module_load }
for  pid=19921 comm="modprobe"
path="/usr/lib/modules/4.9.11-200.fc25.x86_64/misc/vboxdrv.ko"
dev="sda2" ino=2508326
scontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
tcontext=system_u:object_r:modules_object_t:s0 tclass=system permissive=0

but with nvidia instead of vboxdrv being flagged.

See my other post for where to download the latest selinux policy packages.

-- 
Fedora Users List - The place to go to get others to do the work for you

[Frédéric Bron]

>  If you do "ausearch -c 'modprobe' --raw" you would
> see something
>  *similar* to this.... 
ausearch -c 'modprobe' --raw

outputs nothing.

Frédéric

[Ed Greshko]

On 02/28/17 15:10, Frédéric Bron wrote:
> > If you do "ausearch -c 'modprobe' --raw" you
> would see something
> > *similar* to this....
>  ausearch -c 'modprobe' --raw
>
>  outputs nothing.
>  
OK....

So, you've said you are using the nVidia driver.  How did you install it?

And you've said "lsmod | grep nvidia" shows nothing?  

What happens if you do

modprobe nvidia?


-- 
Fedora Users List - The place to go to get others to do the work for you

[Frédéric Bron]

>  modprobe nvidia? 
modprobe: FATAL: Module nvidia not found in directory
/lib/modules/4.9.11-200.fc25.x86_64

[Frédéric Bron]

> > modprobe nvidia?
>
>  modprobe: FATAL: Module nvidia not found in directory
>  /lib/modules/4.9.11-200.fc25.x86_64 
sorry, I was on the wrong computer. This is the right output:

modprobe: ERROR: could not insert 'nvidia': Permission denied

[Ed Greshko]

On 02/28/17 15:40, Frédéric Bron wrote:
> >> modprobe nvidia?
> > modprobe: FATAL: Module nvidia not found in directory
> > /lib/modules/4.9.11-200.fc25.x86_64
>  sorry, I was on the wrong computer. This is the right output:
>
>  modprobe: ERROR: could not insert 'nvidia': Permission denied 
OK....

That is a symptom of not having the selinux-policy-3.13.1-225.11
packages installed.

So you need to do that...

And, now that you are on the right computer, the

"ausearch -c 'modprobe' --raw"

will probably show the AVC


-- 
Fedora Users List - The place to go to get others to do the work for you

[Frédéric Bron]

>  So, you've said you are using the nVidia driver.  How did you
> install it? 
dnf install kernel-devel kernel-headers gcc dkms acpid
dnf install akmod-nvidia xorg-x11-drv-nvidia "kernel-devel-uname-r ==
$(uname -r)"

[Ed Greshko]

On 02/28/17 15:39, Frédéric Bron wrote:
> > So, you've said you are using the nVidia driver.  How did you
> install it?
>  dnf install kernel-devel kernel-headers gcc dkms acpid
>  dnf install akmod-nvidia xorg-x11-drv-nvidia "kernel-devel-uname-r ==
>  $(uname -r)" 
Well, the nvidia modules should be in

/usr/lib/modules/4.9.11-200.fc25.x86_64/extra/nvidia/nvidia.ko

It should have been build automatically....

Check /var/cache/akmods/akmods.log for any errors.

.....

I'm sending this even though you've now said you're on the wrong
system....  I figured I typed enough so don't want to waste the
keystrokes.   :-) :-)

-- 
Fedora Users List - The place to go to get others to do the work for you

[Frédéric Bron]

>  Check /var/cache/akmods/akmods.log for any errors. 
This seems OK:

2017/02/25 07:34:28 akmods: Checking kmods exist for 4.9.11-200.fc25.x86_64
2017/02/25 07:34:28 akmods: Building and installing nvidia-kmod
2017/02/25 07:34:28 akmods: Building RPM using the command
'/sbin/akmodsbuild --target x86_64 --kernels 4.9.11-200.fc25.x86_64
/usr/src/akmods/nvidia-kmod.latest'
2017/02/25 07:35:14 akmods: Checking kmods exist for 4.9.11-200.fc25.x86_64
2017/02/25 07:35:14 akmods: Building and installing nvidia-kmod
2017/02/25 07:35:14 akmods: Building RPM using the command
'/sbin/akmodsbuild --target x86_64 --kernels 4.9.11-200.fc25.x86_64
/usr/src/akmods/nvidia-kmod.latest'
2017/02/25 07:36:14 akmods: Installing newly built rpms

>  /usr/lib/modules/4.9.11-200.fc25.x86_64/extra/nvidia/nvidia.ko
# ls -la /usr/lib/modules/4.9.11-200.fc25.x86_64/extra/nvidia/
total 18336
drwxr-xr-x. 2 root root     4096 25 févr. 07:36 ./
drwxr-xr-x. 6 root root     4096 25 févr. 07:36 ../
-rw-r--r--. 1 root root    78840 25 févr. 07:36 nvidia-drm.ko
-rw-r--r--. 1 root root 16310280 25 févr. 07:36 nvidia.ko
-rw-r--r--. 1 root root  1083128 25 févr. 07:36 nvidia-modeset.ko
-rw-r--r--. 1 root root  1285696 25 févr. 07:36 nvidia-uvm.ko

Frédéric

[Ed Greshko]

On 02/28/17 16:15, Frédéric Bron wrote:
>  This seems OK:
>
>  2017/02/25 07:34:28 akmods: Checking kmods exist for 4.9.11-200.fc25.x86_64
>  2017/02/25 07:34:28 akmods: Building and installing nvidia-kmod
>  2017/02/25 07:34:28 akmods: Building RPM using the command
>  '/sbin/akmodsbuild --target x86_64 --kernels 4.9.11-200.fc25.x86_64
>  /usr/src/akmods/nvidia-kmod.latest'
>  2017/02/25 07:35:14 akmods: Checking kmods exist for 4.9.11-200.fc25.x86_64
>  2017/02/25 07:35:14 akmods: Building and installing nvidia-kmod
>  2017/02/25 07:35:14 akmods: Building RPM using the command
>  '/sbin/akmodsbuild --target x86_64 --kernels 4.9.11-200.fc25.x86_64
>  /usr/src/akmods/nvidia-kmod.latest'
>  2017/02/25 07:36:14 akmods: Installing newly built rpms 
Yes...  But just be aware that it isn't really done until you see

2017/02/28 15:28:20 akmods: Installing newly built rpms
2017/02/28 15:28:20 akmods: DNF detected
2017/02/28 15:28:43 akmods: Successful.

And you should not be too quick to reboot until you see that.  Otherwise
it will be built again on reboot and will seem to be taking too much time.


-- 
Fedora Users List - The place to go to get others to do the work for you

[Frédéric Bron]

>  Yes...  But just be aware that it isn't really done until you
> see
>
>  2017/02/28 15:28:20 akmods: Installing newly built rpms
>  2017/02/28 15:28:20 akmods: DNF detected
>  2017/02/28 15:28:43 akmods: Successful. 

I have that too.

>  And you should not be too quick to reboot until you see that. 
> Otherwise
>  it will be built again on reboot and will seem to be taking too much time. 
I have noticed that once. Thanks for the advice.

Frédéric