Problema dopo update kernel di fedora 21

Guarda, se non sbaglio:

[code]# yum install http://install.linux.ncsu.edu/pub/yum/itecs/public/bumblebee/fedora21/noarch/bumblebee-release-1.2-1.noarch.rpm

yum install bbswitch bumblebee

yum install bumblebee-nvidia[/code]

N.B. Il cancelletto (#) all’inizio di ogni riga non va digitato; vuol dire che il comando che segue va eseguito come root: ovvero, dopo aver digitato in un terminale

su

Volendo, puoi consultare https://fedoraproject.org/wiki/Bumblebee#Fedora_21 guida.[/quote]

Ciao, ho seguito quanto hai consigliato leggendo anche i passi dalla guida.
Solo che nel momento in cui lancio il comando per il test ovvero: optirun glxgears -info | grep “GL_VENDOR” mi genera il seguete errore:

1597.766910] [ERROR]The Bumblebee daemon has not been started yet or the socket path /var/run/bumblebee.socket was incorrect. 1597.766948] [ERROR]Could not connect to bumblebee daemon - is it running?

Ho provato a startare il servizio. come propone ma nulla.

esce questo

Redirecting to /bin/systemctl start bumblebee.service Failed to start bumblebee.service: Unit bumblebee.service failed to load: No such file or directory.

Scusa non avevo fatto caso per nvidia guarda https://ask.fedoraproject.org/en/question/59949/bumblebee-not-working-fedora-21/ che dovresti risolvere :slight_smile:

Ciao ho provato a seguire quella guida , però il problema è rimasto uguale.
Non è cambiato nulla :confused:

Ciao , purtroppo il problema del freez al desktop con il kernel 4 si è ripresentato , non ho assolutamente modificato nulla, infatti non capisco perché debba fare così senza motivo.

Ti posto adesso il boot.log , vediamo se salta fuori qualcosa.

[code] OK ] Found device HGST_HTS721010A9E630 8.
OK ] Found device HGST_HTS721010A9E630 9.
OK ] Found device HGST_HTS721010A9E630 EFI\x20System\x20Partition.
Starting File System Check on /dev/disk/by-uuid/669401e9-68fd-4f77-9060-00cc0f51c92d…
2.349654] systemd-fsck[331]: /dev/sda9: recovering journal
2.760715] systemd-fsck[331]: /dev/sda9: clean, 234888/6127616 files, 4577667/24487424 blocks
OK ] Started File System Check on /dev/disk/by-uuid/669401e9-68fd-4f77-9060-00cc0f51c92d.
OK ] Started dracut initqueue hook.
Starting dracut pre-mount hook…
OK ] Reached target Remote File Systems (Pre).
OK ] Reached target Remote File Systems.
OK ] Started dracut pre-mount hook.
Mounting /sysroot…
OK ] Started Show Plymouth Boot Screen.
OK ] Reached target Paths.
OK ] Reached target Basic System.
OK ] Mounted /sysroot.
OK ] Reached target Initrd Root File System.
Starting Reload Configuration from the Real Root…
OK ] Started Reload Configuration from the Real Root.
OK ] Reached target Initrd File Systems.
OK ] Reached target Initrd Default Target.
Starting dracut pre-pivot and cleanup hook…
OK ] Started dracut pre-pivot and cleanup hook.
Starting Cleaning Up and Shutting Down Daemons…
Stopping Cleaning Up and Shutting Down Daemons…
OK ] Stopped target Timers.
Starting Plymouth switch root service…
OK ] Stopped Cleaning Up and Shutting Down Daemons.
Stopping dracut pre-pivot and cleanup hook…
OK ] Stopped dracut pre-pivot and cleanup hook.
OK ] Stopped target Remote File Systems.
OK ] Stopped target Remote File Systems (Pre).
Stopping dracut pre-mount hook…
OK ] Stopped dracut pre-mount hook.
Stopping dracut initqueue hook…
OK ] Stopped dracut initqueue hook.
OK ] Stopped target Initrd Default Target.
OK ] Stopped target Basic System.
OK ] Stopped target Slices.
OK ] Stopped target Paths.
OK ] Stopped target Sockets.
OK ] Stopped target System Initialization.
Stopping udev Coldplug all Devices…
OK ] Stopped udev Coldplug all Devices.
Stopping Apply Kernel Variables…
OK ] Stopped Apply Kernel Variables.
OK ] Stopped target Swap.
OK ] Stopped target Local File Systems.
Stopping udev Kernel Device Manager…
OK ] Stopped udev Kernel Device Manager.
Stopping dracut pre-udev hook…
OK ] Stopped dracut pre-udev hook.
Stopping dracut cmdline hook…
OK ] Stopped dracut cmdline hook.
Stopping Create Static Device Nodes in /dev…
OK ] Stopped Create Static Device Nodes in /dev.
Stopping Create list of required static device nodes for the current kernel…
OK ] Stopped Create list of required static device nodes for the current kernel.
OK ] Closed udev Control Socket.
OK ] Closed udev Kernel Socket.
Starting Cleanup udevd DB…
OK ] Started Cleanup udevd DB.
OK ] Reached target Switch Root.
OK ] Started Plymouth switch root service.
Starting Switch Root…

Welcome to Fedora 21 (Twenty One)!

OK ] Stopped Switch Root.
OK ] Stopped target Switch Root.
OK ] Stopped target Initrd File Systems.
Stopping File System Check on /dev/disk/by-uuid/669401e9-68fd-4f77-9060-00cc0f51c92d…
OK ] Stopped File System Check on /dev/disk/by-uuid/669401e9-68fd-4f77-9060-00cc0f51c92d.
OK ] Removed slice system-systemd\x2dfsck.slice.
OK ] Stopped target Initrd Root File System.
OK ] Reached target User and Group Name Lookups.
Starting Collect Read-Ahead Data…
Starting Replay Read-Ahead Data…
OK ] Created slice system-getty.slice.
OK ] Reached target Login Prompts.
OK ] Created slice User and Session Slice.
Mounting RPC Pipe File System…
OK ] Reached target Slices.
OK ] Listening on /dev/initctl Compatibility Named Pipe.
OK ] Listening on Delayed Shutdown Socket.
OK ] Set up automount Arbitrary Executable File Formats File System Automount Point.
Mounting Debug File System…
OK ] Stopped Flush Journal to Persistent Storage.
Stopping Journal Service…
OK ] Stopped Journal Service.
Starting Journal Service…
Starting Create list of required static device nodes for the current kernel…
Mounting Huge Pages File System…
Mounting POSIX Message Queue File System…
OK ] Listening on udev Kernel Socket.
OK ] Listening on udev Control Socket.
Starting udev Coldplug all Devices…
OK ] Listening on LVM2 metadata daemon socket.
OK ] Listening on Device-mapper event daemon FIFOs.
Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling…
Expecting device dev-disk-by\x2duuid-e289e2c9\x2db1a0\x2d453c\x2d923e\x2da742f3046e09.device…
Expecting device dev-sda8.device…
Mounting Temporary Directory…
Expecting device dev-disk-by\x2duuid-F0DF\x2d2C4D.device…
OK ] Started Collect Read-Ahead Data.
OK ] Started Create list of required static device nodes for the current kernel.
OK ] Started Replay Read-Ahead Data.
Starting File System Check on Root Device…
Starting Apply Kernel Variables…
Starting Set Up Additional Binary Formats…
OK ] Mounted Debug File System.
OK ] Mounted Huge Pages File System.
OK ] Mounted POSIX Message Queue File System.
OK ] Mounted Temporary Directory.
OK ] Started Apply Kernel Variables.
Mounting Arbitrary Executable File Formats File System…
OK ] Started udev Coldplug all Devices.
Starting udev Wait for Complete Device Initialization…
Starting LVM2 metadata daemon…
OK ] Started LVM2 metadata daemon.
OK ] Started File System Check on Root Device.
Starting Remount Root and Kernel File Systems…
OK ] Started Remount Root and Kernel File Systems.
Starting Configure read-only root support…
Starting Load/Save Random Seed…
Starting Create Static Device Nodes in /dev…
Starting Import network configuration from initramfs…
OK ] Started Configure read-only root support.
OK ] Started Load/Save Random Seed.
OK ] Started Create Static Device Nodes in /dev.
Starting udev Kernel Device Manager…
OK ] Reached target Local File Systems (Pre).
Mounting NFSD configuration filesystem…
OK ] Mounted Arbitrary Executable File Formats File System.
OK ] Started Set Up Additional Binary Formats.
OK ] Started Import network configuration from initramfs.
OK ] Started Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
OK ] Mounted RPC Pipe File System.
OK ] Mounted NFSD configuration filesystem.
OK ] Started Journal Service.
Starting Flush Journal to Persistent Storage…
16.874081] systemd-fsck[440]: /dev/sda9: Super-blocco last write time is in the future.
16.874263] systemd-fsck[440]: (by less than a day, probably due to the hardware clock being incorrectly set)
16.874352] systemd-fsck[440]: /dev/sda9: clean, 234888/6127616 files, 4577667/24487424 blocks
OK ] Started udev Kernel Device Manager.
OK ] Created slice system-systemd\x2dbacklight.slice.
Starting Load/Save Screen Backlight Brightness of backlight:intel_backlight…
OK ] Started Load/Save Screen Backlight Brightness of backlight:intel_backlight.
OK ] Started Flush Journal to Persistent Storage.
OK ] Created slice system-systemd\x2drfkill.slice.
Starting Load/Save RF Kill Switch Status of rfkill1…
Starting Load/Save RF Kill Switch Status of rfkill0…
Starting Load/Save Screen Backlight Brightness of leds:asus::kbd_backlight…
OK ] Started Load/Save RF Kill Switch Status of rfkill1.
OK ] Started Load/Save Screen Backlight Brightness of leds:asus::kbd_backlight.
OK ] Started Load/Save RF Kill Switch Status of rfkill0.
OK ] Reached target Sound Card.
OK ] Found device HGST_HTS721010A9E630 EFI\x20System\x20Partition.
Mounting /boot/efi…
OK ] Found device HGST_HTS721010A9E630 8.
OK ] Found device HGST_HTS721010A9E630 8.
Activating swap Swap Partition…
Activating swap /dev/disk/by-uuid/e289e2c9-b1a0-453c-923e-a742f3046e09…
OK ] Mounted /boot/efi.
OK ] Activated swap Swap Partition.
OK ] Activated swap /dev/disk/by-uuid/e289e2c9-b1a0-453c-923e-a742f3046e09.
OK ] Reached target Swap.
Starting Load/Save RF Kill Switch Status of rfkill2…
OK ] Started Load/Save RF Kill Switch Status of rfkill2.
OK ] Started udev Wait for Complete Device Initialization.
Starting Activation of DM RAID sets…
OK ] Started Activation of DM RAID sets.
OK ] Reached target Local File Systems.
Starting Create Volatile Files and Directories…
Starting Tell Plymouth To Write Out Runtime Data…
OK ] Reached target Encrypted Volumes.
OK ] Started Tell Plymouth To Write Out Runtime Data.
OK ] Started Create Volatile Files and Directories.
Starting Security Auditing Service…
OK ] Started Security Auditing Service.
Starting Update UTMP about System Boot/Shutdown…
OK ] Started Update UTMP about System Boot/Shutdown.
OK ] Reached target System Initialization.
OK ] Listening on CUPS Printing Service Sockets.
OK ] Listening on Open-iSCSI iscsid Socket.
OK ] Listening on Open-iSCSI iscsiuio Socket.
OK ] Reached target Paths.
OK ] Listening on RPCbind Server Activation Socket.
OK ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
OK ] Listening on D-Bus System Message Bus Socket.
OK ] Reached target Sockets.
OK ] Reached target Timers.
Starting Manage Sound Card State (restore and store)…
OK ] Started Manage Sound Card State (restore and store).
OK ] Reached target Basic System.
Starting RealtimeKit Scheduling Policy Service…
Starting Accounts Service…
Starting Rollback uncommitted netcf network config change transactions…
Starting Machine Check Exception Logging Daemon…
Starting Modem Manager…
Starting Hardware Monitoring Sensors…
Starting Preprocess NFS configuration…
Starting GSSAPI Proxy Daemon…
Starting Hardware RNG Entropy Gatherer Daemon…
OK ] Started Hardware RNG Entropy Gatherer Daemon.
Starting NTP client/server…
Starting Avahi mDNS/DNS-SD Stack…
Starting Login Service…
Starting D-Bus System Message Bus…
OK ] Started D-Bus System Message Bus.
OK ] Started Avahi mDNS/DNS-SD Stack.
OK ] Started RealtimeKit Scheduling Policy Service.
Starting firewalld - dynamic firewall daemon…
Starting LSB: Init script for live image…
OK ] Started Rollback uncommitted netcf network config change transactions.
OK ] Started Machine Check Exception Logging Daemon.
OK ] Started Preprocess NFS configuration.
OK ] Started GSSAPI Proxy Daemon.
OK ] Started LSB: Init script for live image…
OK ] Started Hardware Monitoring Sensors.
OK ] Started NTP client/server.
OK ] Started Modem Manager.
Starting Load/Save RF Kill Switch Status of rfkill3…
Starting ABRT Automated Bug Reporting Tool…
OK ] Started ABRT Automated Bug Reporting Tool.
Starting Install ABRT coredump hook…
Starting ABRT kernel log watcher…
OK ] Started ABRT kernel log watcher.
Starting SYSV: Late init script for live image…
Starting Bluetooth service…
OK ] Started Load/Save RF Kill Switch Status of rfkill3.
OK ] Started Login Service.
OK ] Started Bluetooth service.
OK ] Reached target Bluetooth.
Starting Authorization Manager…
OK ] Started SYSV: Late init script for live image…
OK ] Started Install ABRT coredump hook.
Starting Hostname Service…
OK ] Started Authorization Manager.
OK ] Started Accounts Service.
OK ] Started Hostname Service.
OK ] Started firewalld - dynamic firewall daemon.
Starting Network Manager…
OK ] Started Network Manager.
Starting Network Manager Wait Online…
Starting WPA Supplicant daemon…
OK ] Started WPA Supplicant daemon.
Starting Network Manager Script Dispatcher Service…
OK ] Started Network Manager Script Dispatcher Service.
OK ] Started Network Manager Wait Online.
OK ] Reached target Network.
Starting Notify NFS peers of a restart…
Starting Virtualization daemon…
OK ] Reached target Network is Online.
Starting TeamViewer remote control daemon…
OK ] Started Notify NFS peers of a restart.
OK ] Reached target NFS client services.
OK ] Reached target Remote File Systems (Pre).
OK ] Reached target Remote File Systems.
Starting Permit User Sessions…
OK ] Started Permit User Sessions.
Starting GNOME Display Manager…
Starting Job spooling tools…
OK ] Started Job spooling tools.
Starting Command Scheduler…
OK ] Started Command Scheduler.
Starting Wait for Plymouth Boot Screen to Quit…
OK ] Started GNOME Display Manager.
[/code]

16.874081] systemd-fsck[440]: /dev/sda9: Super-blocco last write time is in the future. 16.874263] systemd-fsck[440]: (by less than a day, probably due to the hardware clock being incorrectly set) 16.874352] systemd-fsck[440]: /dev/sda9: clean, 234888/6127616 files, 4577667/24487424 blocks

questo l ho risolto così :

timedatectl set-local-rtc 0

però il problema del freeze del desktop è rimasto e non mi fa accedere al kernel 4.

Prova intanto a togliere questi servizi :

#systemctl disable livesys.service 
#systemctl disable livesys-late.service

poi con il kernel vecchio più bumblebee-nvidia parte senza problemi ?

edit: guardando bene la scritta che dice che è meno di un giorno probabilmente a causa dell’orologio hardware che è errato mi viene anche da pensare per caso non è che la batteria tampone sia scarica ? :slight_smile:

[quote=edmondo]Prova intanto a togliere questi servizi :

#systemctl disable livesys.service 
#systemctl disable livesys-late.service

poi con il kernel vecchio più bumblebee-nvidia parte senza problemi ?

edit: guardando bene la scritta che dice che è meno di un giorno probabilmente a causa dell’orologio hardware che è errato mi viene anche da pensare per caso non è che la batteria tampone sia scarica ? :)[/quote]

Ciao scusami per il ritardo ma sono stato fuori nel week.

Cmq difficile che sia la batteria tampone perché il pc è nuovo e ha meno di un mese, poi su windows non mi da problemi di questo genere e neanche il vecchio kernel di linux quindi escludo ( ma non lo dico per certo ) che possa essere un problema legato a questo.

Per quanto riguarda quei due servizi li ho disabilitati come hai suggerito. ma nulla è cambiato.

Non riesco proprio a capire cosa possa essere.

Si il kernel vecchio più bumblebee parte senza nessun problema.