fedora 25 não inicializa após a atualização

0

Eu tenho tido problemas para inicializar com versões do Fedora 25 maiores que 4.5.5-300. Eu já tentei modificar a política de selinux como sugerido em respostas a perguntas semelhantes, mas sem sucesso.

Ouput do journalctl -xb -p3:

    -- Logs begin at dom 2016-10-09 16:14:16 CDT, end at dom 2016-12-18 06:30:04 CST. --
    dic 18 05:59:10 localhost.localdomain kernel: kvm: disabled by bios
    dic 18 05:59:11 localhost.localdomain kernel: Support for cores revisions 0x17 and 0x18 disabled by module param allhwsupport=0. Try b43.allhwsupport=
    dic 18 05:59:20 localhost.localdomain avahi-daemon[916]: chroot.c: open() failed: No such file or directory
    dic 18 05:59:42 localhost.localdomain kernel: brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false (implement)
    dic 18 05:59:42 localhost.localdomain kernel: brcmsmac bcma0:1: brcms_ops_config: change power-save mode: false (implement)
    dic 18 05:59:46 localhost.localdomain kernel: brcmsmac bcma0:1: brcmsmac: brcms_ops_bss_info_changed: associated
    dic 18 05:59:46 localhost.localdomain kernel: brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: true (implement)
    dic 18 05:59:53 localhost.localdomain kernel: brcmsmac bcma0:1: brcms_ops_bss_info_changed: arp filtering: 1 addresses (implement)
    dic 18 06:00:20 localhost.localdomain spice-vdagent[1323]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
    dic 18 06:03:05 localhost.localdomain kernel: [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream !
    dic 18 06:03:18 localhost.localdomain spice-vdagent[1706]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
    dic 18 06:03:35 localhost.localdomain pulseaudio[1606]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Saída do sestatus:

SELinux status:                 enabled
SELinuxfs mount:                /sys/fs/selinux
SELinux root directory:         /etc/selinux
Loaded policy name:             targeted
Current mode:                   permissive
Mode from config file:          permissive
Policy MLS status:              enabled
Policy deny_unknown status:     allowed
Max kernel policy version:      30

Alguma idéia de como corrigir isso?

    
por Enrique Cuervo Guzman 18.12.2016 / 14:02

0 respostas

Tags