Ubuntu nao volta da suspensao ou volta com tela preta, suspende mas retorna?

platao · 22 de Maio de 2016, 22:31

Ola pessoal uma dica interessante para o pessoal que estava com problemas na suspensao do ubuntu, que suspende e ao voltar volta mas fica com a tela preta, e as vezes desligada e tbm para aqueles como eu, que o ubuntu suspende certinho, mas logo em seguida ele volta da suspensao novamente, no mesmo instante.

Essa dica funcionou para mim e agora suspende e fica suspenso e pode funcionar tbm para quem esta com o problema, nao esquecer de deixar aqui anotado se deu certo.

sudo gedit /etc/default/grub

Edite a linha;

GRUB_CMDLINE_LINUX=""

e deixe assim entre as aspas;

GRUB_CMDLINE_LINUX="acpi_sleep=nonvs"

Salve o arquivo e em seguida:

sudo update-grub

Reinicie agora e teste.

**hardware testado; Ubuntu 16.04 x64 h97n-wifi - i3 - 750Ti

Platao

galactus · 23 de Maio de 2016, 16:33

Oi platão. Ótima dica. Posso falar mais uma coisa?

No Xubuntu 16.04, ele está com um Bug chato que quando volta da suspensão a seta do mouse desaparece da tela, mas ele funciona! É chato pra burro. Ainda não tem concerto, precisam mexer em alguns pacotes, o bug é oficial no Launchpad. De qualquer maneira, pra quem já passou por isso, basta um

CRTL + ALT + F1 seguido de um CRTL + ALT + F7 para voltar a parte gráfica com a seta do mouse.

Era isso.

platao · 23 de Maio de 2016, 19:15

Eu encontrei alguns relatos tbm http://askubuntu.com/questions/761229/mouse-trouble-in-16-04 e https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1568604 e aqui tbm de modo mais abrangente http://askubuntu.com/search?q=16.04++mouse+ eu acho que o Ubuntu 16 esta bastante cheio de problemas ,mais que os outros lançamentos das outras versoes. No postagem #54 em diante parece que tem uma dica, gostaria de ter esse "bug" aqui para ver como resolver, sera que se criar um xorg.conf manualmente e tentar adicionar algum parametro nele resolve?

Aqui eu deixo a placa onboard de video intel desabilitada no bios, so uso a Nvidia.

Dei uma procurada e talvez se vc puder adicionar um comando nos scripts de suspensao em /usr/sbin/pm-suspend e so uma ideia.

platao@platao-H97N-WIFI:~$ locate pm-suspend
/usr/sbin/pm-suspend
/usr/sbin/pm-suspend-hybrid
/usr/share/bash-completion/completions/pm-suspend
/usr/share/bash-completion/completions/pm-suspend-hybrid
/usr/share/man/man8/pm-suspend-hybrid.8.gz
/usr/share/man/man8/pm-suspend.8.gz
/var/log/pm-suspend.log

aqui a suspensao funciona com o comando;

sudo /usr/sbin/pm-suspend

**se eu quero suspender sem ficar dependendo de programa eu entro como root(sudo su) e depois coloco o tempo que eu quero, por exemplo 3600 segundos = 1hora

sleep 3600 ; /usr/sbin/pm-suspend

Galactus vc esta usando o compiz no Xubuntu? Aqui eu deixo o proposed habilitado e as atualizaçoes esses dias atras estava frenetica, mas deu uma parada, pelo menos 2 dias sem atualizar aqui nenhum pacote, eu acho que isso vai ser acertado rapido.

galactus · 23 de Maio de 2016, 21:30

platão eu deixei o proposed desabilitado no 16.04. Nas minhas máquinas eu procuro desligar todos os efeitos do compiz.

No momento eu tirei o Xubuntu 16.04 do Notebook. Muitos probleminhas! Estou testando o Fedora 23 com MATE.

platao · 24 de Maio de 2016, 00:12

Eu estou testando o Ubuntu Mate aqui e confesso que tenho gostado bastante dele alem da praticidade do gnome2.

Aqui eu estou deixando ativo o proposed mesmo sabendo do pepino que deu a algum tempo atras com o network manager para ver como andam as atualizaçoes.

O network manager anda meio rebelde...confunde icone da internet cabeada com a wireless, se desativa ela e reativa novamente varias vezes o sistema nao reestabelece mais a conexao....no 14.04 estava ok tudo funcionava muito bem mas no 16 tem se mostrado problematico esse pacote.

Eu acho que e remoto a possibilidade do compiz estar afetando a questao do mouse mas....aqui no 16.04 eu desligo quase tudo, o driver livre que vem por padrao no ubuntu estava muito ruim aqui nvidia750...as letras ficavam falhando e tela preta, acho que nao tem relação com o mouse.

Outra coisa que esta me desagradando e que esta ao clicar em desligar e aparecer a tela do ubuntu das "bolinhas" esta vazando""" um pouco de texto na tela de finalização do ubuntu...da para ver o sistema desligando os serviços.

Do resto esta legal....melhorou em alguns quesitos e piorou em outros...como o software center meia boca...

platao · 08 de Novembro de 2016, 03:24

Bom...estava tudo as mil maravilhas com o ubuntu ate a atualização de algum pacote ou o proprio kernel e a suspensao nao funciona como deveria....as vezes suspende.....e fica suspenso e as vezes suspende e trava e fica tela preta** e as vezes suspende mas volta logo em seguida! Cabuloso isso!!

As vezes eu quero ficar deitado escutando alguma musica,documentario e deixo o computador ligado e agendo para que fique 2 horas por exemplo e depois suspenda;

sudo su

sleep 6600 ; /usr/sbin/pm-suspend

e ok, estava funcionando como descrito nesse topico, suspendia com o comando adicionado la no grub....agora depois da atualização do kernel voltou o problema novamente!!! resolvi olhar mais a fundo!!!

Pesquisei alguns sites e treads https://wiki.archlinux.org/index.php/Power_management/Suspend_and_hibernate

olha que interessante;

Instantaneous wakeups from suspend

For some Intel Haswell systems with the LynxPoint and LynxPoint-LP chipset, instantaneous wakeups after suspend are reported. They are linked to erroneous BIOS ACPI implementations and how the xhci_hcd module interprets it during boot. As a work-around reported affected systems are added to a blacklist (named XHCI_SPURIOUS_WAKEUP) by the kernel case-by-case.[1]
Instantaneous resume may happen, for example, if a USB device is plugged during suspend and ACPI wakeup triggers are enabled. A viable work-around for such a system, if it is not on the blacklist yet, is to disable the wakeup triggers. An example to disable wakeup through USB is described as follows.[2]

To view the current configuration:

$ cat /proc/acpi/wakeup

Device S-state Status Sysfs node
...
EHC1 S3 *enabled pci:0000:00:1d.0
EHC2 S3 *enabled pci:0000:00:1a.0
XHC S3 *enabled pci:0000:00:14.0
...

The relevant devices are EHC1, EHC1 and XHC (for USB 3.0). To toggle their state you have to echo the device name to the file as root.
# echo EHC1 > /proc/acpi/wakeup
# echo EHC2 > /proc/acpi/wakeup
# echo XHC > /proc/acpi/wakeup

This should result in suspension working again. However, this settings are only temporary and would have to be set at every reboot. To automate this take a look at systemd#Writing unit files. See BBS thread for a possible solution and more information.

Ao que parece e que o gerenciamento de energia nao deixa o sistema entrar em suspensao, olhando nos logs do sistema o kernel esta fazendo tudo certo**

Nov 8 00:41:09 H97N-WIFI kernel: [ 761.746652] PM: Syncing filesystems ... done.
Nov 8 00:41:09 H97N-WIFI kernel: [ 761.749235] PM: Preparing system for sleep (mem)
Nov 8 00:41:09 H97N-WIFI kernel: [ 761.749661] Freezing user space processes ... (elapsed 0.001 seconds) done.
Nov 8 00:41:09 H97N-WIFI kernel: [ 761.751579] Double checking all user space processes after OOM killer disable... (elapsed 0.000 seconds)
Nov 8 00:41:09 H97N-WIFI kernel: [ 761.751674] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Nov 8 00:41:09 H97N-WIFI kernel: [ 761.752907] PM: Suspending system (mem)
Nov 8 00:41:09 H97N-WIFI kernel: [ 761.752934] Suspending console(s) (use no_console_suspend to debug)
Nov 8 00:41:09 H97N-WIFI kernel: [ 761.753068] wlp4s0: deauthenticating from 48:83:c7:97:93:32 by local choice (Reason: 3=DEAUTH_LEAVING)
Nov 8 00:41:09 H97N-WIFI kernel: [ 761.753247] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
Nov 8 00:41:09 H97N-WIFI kernel: [ 761.753357] sd 1:0:0:0: [sdb] Stopping disk
Nov 8 00:41:09 H97N-WIFI kernel: [ 761.753450] serial 00:05: disabled
Nov 8 00:41:09 H97N-WIFI kernel: [ 761.753605] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Nov 8 00:41:09 H97N-WIFI kernel: [ 761.753909] e1000e: EEE TX LPI TIMER: 00000011
Nov 8 00:41:09 H97N-WIFI kernel: [ 761.756062] sd 0:0:0:0: [sda] Stopping disk
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.248981] PM: suspend of devices complete after 495.855 msecs
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.249240] PM: late suspend of devices complete after 0.256 msecs
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.249753] e1000e 0000:00:19.0: System wakeup enabled by ACPI
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.261340] PM: noirq suspend of devices complete after 12.096 msecs
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.261509] ACPI: Preparing to enter system sleep state S3
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.261794] PM: Saving platform NVS memory
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.261804] Disabling non-boot CPUs ...
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.271121] Broke affinity for irq 30
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.272144] smpboot: CPU 1 is now offline
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.288088] Broke affinity for irq 23
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.288091] Broke affinity for irq 28
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.288093] Broke affinity for irq 30
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.288094] Broke affinity for irq 33
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.289284] smpboot: CPU 2 is now offline
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.300066] Broke affinity for irq 16
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.300069] Broke affinity for irq 23
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.300072] Broke affinity for irq 28
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.300073] Broke affinity for irq 30
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.300074] Broke affinity for irq 33
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.300074] Broke affinity for irq 34
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.301087] smpboot: CPU 3 is now offline
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.310036] ACPI: Low-level resume complete
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.310078] PM: Restoring platform NVS memory
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.311975] Enabling non-boot CPUs ...
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.321266] x86: Booting SMP configuration:
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.321267] smpboot: Booting Node 0 Processor 1 APIC 0x2
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.324564] cache: parent cpu1 should not be sleeping
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.324718] CPU1 is up
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.335287] smpboot: Booting Node 0 Processor 2 APIC 0x1
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.337629] cache: parent cpu2 should not be sleeping
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.337762] CPU2 is up
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.347259] smpboot: Booting Node 0 Processor 3 APIC 0x3
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.349676] cache: parent cpu3 should not be sleeping
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.349819] CPU3 is up
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.352124] ACPI: Waking up from system sleep state S3
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.365279] PM: noirq resume of devices complete after 12.567 msecs
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.365821] PM: early resume of devices complete after 0.517 msecs
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.365955] e1000e 0000:00:19.0: System wakeup disabled by ACPI
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.366029] rtc_cmos 00:02: System wakeup disabled by ACPI
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.366920] serial 00:05: activated
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.369244] sd 0:0:0:0: [sda] Starting disk
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.370247] sd 1:0:0:0: [sdb] Starting disk
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.371274] iwlwifi 0000:04:00.0: L1 Disabled - LTR Enabled
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.371501] iwlwifi 0000:04:00.0: L1 Disabled - LTR Enabled
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.568480] iwlwifi 0000:04:00.0: L1 Disabled - LTR Enabled
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.568712] iwlwifi 0000:04:00.0: L1 Disabled - LTR Enabled
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.673260] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.703732] ata1.00: configured for UDMA/133
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.732512] PM: resume of devices complete after 366.637 msecs
Nov 8 00:41:09 H97N-WIFI kernel: [ 762.732720] PM: Finishing wakeup.

**kernel 4.8 e kernel padrao ubuntu mais antigo, mesmo problema

mas olhando na acpi;

cat /proc/acpi/wakeup

GLAN     S4   *enabled pci:0000:00:19.0
EHC1     S4   *enabled pci:0000:00:1d.0
EHC2     S4   *enabled pci:0000:00:1a.0
XHC     S4   *enabled pci:0000:00:14.0
PWRB     S3   *enabled

esses dispositivos nao deixam entrar em suspensao pelo que entendi, tentei entao desligando todos e funciona bem a suspensao.......

echo EHC1 > /proc/acpi/wakeup

Entao encontrei esse script em https://bbs.archlinux.org/viewtopic.php?pid=1575617#p1575617 mensagem do usiario Bernie99;

--------------------------------------------------------------------------------------------------------------------------------------------------

Of course, the triggers can be explicitly enabled or disabled by first checking the current status.

An example script to do this would be e.g.:

---- disable_acpi_wakeup.sh

#! /usr/bin/sh
# Add your candidates below but make sure that no pattern matches more than one device in /proc/acpi/wakeup
CANDIDATES="EHC1 EHC2 XHC"
for ACPIDEV in $CANDIDATES; do
ACTIVE=$(grep enabled /proc/acpi/wakeup | cut -f 1 | grep "$ACPIDEV")
if [ -n "$ACTIVE" ]; then
echo "$ACTIVE" > /proc/acpi/wakeup
echo "DEBUG: disabled -$ACTIVE-" >&2
else
echo "DEBUG: no active -$ACPIDEV- found." >&2
fi
done

I have similar issues with a Lenovo ThinkPad Yoga S1, on which only the XHC trigger exists, and causes wakeup issues. I have no EHC1/2.

I know UNIX but am a newbie to Arch (actually the Manjaro spinoff; I hope the forum tolerates).
Therefore I am not sure where the script above would be best placed to run with each startup.
Any idea?

--------------------------------------------------------------------------------------------------------------------

Fiz uma modificação para adicionar o PWRB e GLAN tbm, coloquei o script esta em /etc/cron/hourly(nao sei se e mais adequado, mas fica por enquanto) -

disable_acpi_wakeup.sh

#!/bin/sh
# Add your candidates below but make sure that no pattern matches more than one device in /proc/acpi/wakeup
CANDIDATES="EHC1 EHC2 XHC GLAN PWRB"
for ACPIDEV in $CANDIDATES; do
ACTIVE=$(grep enabled /proc/acpi/wakeup | cut -f 1 | grep "$ACPIDEV")
if [ -n "$ACTIVE" ]; then
echo "$ACTIVE" > /proc/acpi/wakeup
echo "DEBUG: disabled -$ACTIVE-" >&2
else
echo "DEBUG: no active -$ACPIDEV- found." >&2
fi
done

Esta colocado para ser executado no /etc/rc.local.

#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.
/etc/cron.hourly/disable_acpi_wakeup.sh
exit 0

aparentemente funcionou nao sei as consequencias disso no sistema!!!!

platao@H97N-WIFI:~$ cat /proc/acpi/wakeup
Device   S-state     Status Sysfs node
PEG0     S4   *disabled pci:0000:00:01.0
PEGP     S4   *disabled pci:0000:01:00.0
PEG1     S4   *disabled
PEGP     S4   *disabled
PEG2     S4   *disabled
PEGP     S4   *disabled
PS2K     S3   *disabled
PS2M     S3   *disabled
RP01     S4   *disabled pci:0000:00:1c.0
PXSX     S4   *disabled
RP02     S4   *disabled
PXSX     S4   *disabled
RP03     S4   *disabled
PXSX     S4   *disabled
RP04     S4   *disabled pci:0000:00:1c.3
PXSX     S4   *disabled pci:0000:03:00.0
RP05     S4   *disabled pci:0000:00:1c.4
PXSX     S4   *disabled pci:0000:04:00.0
RP06     S4   *disabled
PXSX     S4   *disabled
RP07     S4   *disabled
PXSX     S4   *disabled
RP08     S4   *disabled
PXSX     S4   *disabled
GLAN     S4   *enabled pci:0000:00:19.0
EHC1     S4   *disabled pci:0000:00:1d.0
EHC2     S4   *disabled pci:0000:00:1a.0
XHC     S4   *disabled pci:0000:00:14.0
TPD4     S4   *disabled
TPD7     S0   *disabled
TPD8     S0   *disabled
HDEF     S4   *disabled pci:0000:00:1b.0
PWRB     S3   *disabled platform:PNP0C0C:00
platao@H97N-WIFI:~$

Por enquanto esta tudo ok!!!quem quiser testar!!!!

http://i.imgur.com/ZvHKpar.png

http://i.imgur.com/uOsUJ7r.png

Platao

platao · 14 de Janeiro de 2017, 15:01

Ola pessoal para aqueles que estao ainda com problemas de suspender no ubuntu;

sudo pm-suspend --store-quirks-as-lkw

Esse comando salva as peculiaridades da placa de vídeo exigida pelo pm-suspend ou pm-suspend-hybrid em um arquivo .quirkdb especifico para o seu sistema.

O arquivo será salvo em /var/cache/pm-utils/last_known_working.quirkdb

match system.firmware.version compare_eq F2
match system.firmware.vendor compare_eq American Megatrends Inc.
match system.firmware.release_date compare_eq 04/24/2014
match system.hardware.vendor compare_eq Gigabyte Technology Co., Ltd.
match system.hardware.product compare_eq H97N-WIFI
match system.hardware.version compare_eq To be filled by O.E.M.
match system.board.product compare_eq H97N-WIFI
match system.board.version compare_eq x.x
match system.board.vendor compare_eq Gigabyte Technology Co., Ltd.
match system.hardware.primary_video.vendor compare_eq 0x10de
match system.hardware.primary_video.product compare_eq 0x1380
match system.hardware.primary_video.driver compare_eq nvidia
match system.hardware.primary_video.using_kms compare_eq false
match system.kernel.version compare_eq 4.4.0-59-lowlatency
addquirk --quirk-none
endmatch
endmatch
endmatch
endmatch
endmatch
endmatch
endmatch
endmatch
endmatch
endmatch
endmatch
endmatch
endmatch

Este parâmetro salva as peculiaridades reais que foram utilizados com êxito ao retornar ou suspender e será específico para o seu sistema, incluindo o hardware de vídeo,driver, e se é necessario ou não kernel modesetting. Apos a atualização do kernel o arquivo sera subistituido sendo necessario rodar o comando novamente.

Funcionou muito bem aqui e desativei os outros workarounds que eu tinha feito, aparentemente esta funcionando 100% vou testar mais!

uname -a
Linux H97N-Wifi 4.4.0-59-lowlatency #80-Ubuntu SMP PREEMPT Fri Jan 6 21:04:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

kernel padrao ubuntu.

Outra coisa que eu notei e que quando voltava da suspensao a wireles desativava....tendo que reiniciar o network-manager ,,,,,encontrei esse post e esta funciona muito bem no 16.04!!

https://igtek.tk/index.php/2016/05/11/fix-ubuntu-16-04-no-wireless-connection-after-suspend/

FIX UBUNTU 16.04 NO WIRELESS CONNECTION AFTER SUSPEND
MAY 11, 2016 BRAM   LEAVE A COMMENT
Ubuntu has a ongoing problem. When you put your computer to sleep, and wake it up again, you might find that you are not connected to WiFi anymore. Or you are, but the list of available WiFi access points has disappeared.

This issue persists on Ubuntu 14.04, 14.10, 15.04, 15.10 and on 16.04. The workaround I will be showing here will work on any Ubuntu version that has systemd. In other words, this will only work on versions 15.04 and above.

As found in this post, the problems go away after you do "sudo service network-manager restart" after waking up from suspend. However, to manually reset the Network Manager every time you wake up the computer is quite annoying, so we are going to automate this by creating a script that runs every time the computer wakes up.

Step 1: Create a new script in the systemd system-sleep folder.
sudo nano /lib/systemd/system-sleep/reset_network.sh

Step 2: Copy and paste the following into the newly created script.
#!/bin/bash
if [ $1 = post ] && [ $2 = suspend ]
then service network-manager restart
fi

Step 3: Exit nano by pressing "Ctrl + X" and save it.

Step 4: Make the script executable.
sudo chmod +x /lib/systemd/system-sleep/reset_network.sh

I hope this helped!

FONTES https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450396

Martin Pitt (pitti) wrote on 2015-06-02: Re: Gigabyte P35-DS3: needs suspend quirks   #3
The main difference here is that under upstart we still run pm-suspend with its quirks, while under systemd there are no quirks being run any more. As suspend quirks have supposed to be obsolete for many years and should be fixed properly in drivers/kernel, I add a linux task.

To find out which quirks you need, can you please run

sudo pm-suspend --store-quirks-as-lkw

confirm that this actually still works properly (i. e. leave it suspended for a few minuts), and then attach /var/cache/pm-utils/last_known_working.quirkdb ? Thanks!

summary:   - Gigabyte P35-DS3: needs suspend quirks
+ Gigabyte P35-DS3: does not stay suspended

platao · 29 de Abril de 2017, 11:13

O problema foi resolvido com o driver Nvidia mais recente o 381!!!

loco abreu · 17 de Julho de 2018, 21:17

No Ubuntu 14.04 (um pouco antigo) a dica do platão foi muito bem sucedida.

lucascpsc · 27 de Agosto de 2019, 18:27

Muito obrigado, a dica do GRUB funcionou perfeitamente no meu Debian 10.

felipe_77 · 18 de Julho de 2023, 14:31

funcionou aqui na 22.04