1
Instalação e Atualização / Re:Problemas no apt-get update
« Online: 11 de Janeiro de 2017, 21:02 »
creto!
Fucionou!! Muito obrigado!
Fucionou!! Muito obrigado!
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
bruno@TP301UA:~$ sudo apt-get update
[sudo] senha para bruno:
Atingido:1 http://br.archive.ubuntu.com/ubuntu yakkety InRelease
Obter:2 http://br.archive.ubuntu.com/ubuntu yakkety-updates InRelease [102 kB]
Ign:3 http://dl.google.com/linux/chrome/deb stable InRelease
Atingido:4 http://dl.google.com/linux/chrome/deb stable Release
Obter:5 http://security.ubuntu.com/ubuntu yakkety-security InRelease [102 kB]
Atingido:7 http://archive.canonical.com/ubuntu yakkety InRelease
Obter:8 http://br.archive.ubuntu.com/ubuntu yakkety-backports InRelease [102 kB]
Obter:9 http://br.archive.ubuntu.com/ubuntu yakkety-updates/main i386 Packages [142 kB]
Obter:10 http://br.archive.ubuntu.com/ubuntu yakkety-updates/main amd64 Packages [144 kB]
Obter:11 http://br.archive.ubuntu.com/ubuntu yakkety-updates/main amd64 DEP-11 Metadata [111 kB]
Obter:12 http://br.archive.ubuntu.com/ubuntu yakkety-updates/main DEP-11 64x64 Icons [69,1 kB]
Obter:13 http://br.archive.ubuntu.com/ubuntu yakkety-updates/universe amd64 DEP-11 Metadata [83,4 kB]
Obter:14 http://br.archive.ubuntu.com/ubuntu yakkety-updates/universe DEP-11 64x64 Icons [94,2 kB]
Obter:15 http://br.archive.ubuntu.com/ubuntu yakkety-updates/multiverse amd64 DEP-11 Metadata [212 B]
Obter:16 http://br.archive.ubuntu.com/ubuntu yakkety-backports/main amd64 DEP-11 Metadata [212 B]
Obter:17 http://br.archive.ubuntu.com/ubuntu yakkety-backports/universe amd64 DEP-11 Metadata [216 B]
Obter:18 http://br.archive.ubuntu.com/ubuntu yakkety-backports/multiverse amd64 DEP-11 Metadata [216 B]
Baixados 665 kB em 2s (224 kB/s)
Lendo listas de pacotes... Pronto
bruno@TP301UA:~$
Veja se consegue na cmdline de boot usar novamente aquele parâmetro "text" (sem as aspas), abordado no post #13 e com ele se vai parar num prompt usável e com conexão internet.
sudo apt-add-repository ppa:oibaf/graphics-drivers
sudo apt update
sudo apt-get dist-upgrade
bruno@bruno-TP301UA:/etc/default$ sudo sensors-detect
# sensors-detect revision 6284 (2015-05-31 14:00:33 +0200)
# System: ASUSTeK COMPUTER INC. TP301UA [1.0] (laptop)
# Kernel: 4.9.0-040900rc8-generic x86_64
# Processor: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz (6/78/3)
This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): y
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
AMD Family 12h and 14h thermal sensors... No
AMD Family 15h thermal sensors... No
AMD Family 16h thermal sensors... No
AMD Family 15h power sensors... No
AMD Family 16h power sensors... No
Intel digital thermal sensor... Success!
(driver `coretemp')
Intel AMB FB-DIMM thermal sensor... No
Intel 5500/5520/X58 thermal sensor... No
VIA C7 thermal sensor... No
VIA Nano thermal sensor... No
Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): y
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No
Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no): y
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No
Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): y
Found unknown SMBus adapter 8086:9d23 at 0000:00:1f.4.
Sorry, no supported PCI bus adapters found.
Next adapter: i915 gmbus dpc (i2c-0)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: i915 gmbus dpb (i2c-1)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: i915 gmbus dpd (i2c-2)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: DPDDC-A (i2c-3)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: Synopsys DesignWare I2C adapter (i2c-4)
Do you want to scan it? (YES/no/selectively): y
Adapter doesn't support all probing functions.
Some addresses won't be probed.
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `coretemp':
* Chip `Intel digital thermal sensor' (confidence: 9)
To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
coretemp
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!
Do you want to add these lines automatically to /etc/modules? (yes/NO)y
Successful!
Monitoring programs won't work until the needed modules are
loaded. You may want to run '/etc/init.d/kmod start'
to load them.
bruno@bruno-TP301UA:/etc/default$
bruno@bruno-TP301UA:/etc/default$ sensors
asus-isa-0000
Adapter: ISA adapter
cpu_fan: 3000 RPM
temp1: +37.0°C
acpitz-virtual-0
Adapter: Virtual device
temp1: +37.0°C (crit = +103.0°C)
coretemp-isa-0000
Adapter: ISA adapter
Physical id 0: +38.0°C (high = +100.0°C, crit = +100.0°C)
Core 0: +35.0°C (high = +100.0°C, crit = +100.0°C)
Core 1: +35.0°C (high = +100.0°C, crit = +100.0°C)
pch_skylake-virtual-0
Adapter: Virtual device
temp1: +36.5°C
bruno@bruno-TP301UA:/etc/default$
bruno@bruno-TP301UA:/etc/default$ sudo hddtemp /dev/sda
/dev/sda: HGST HTS541010A7E630: 35°C
Eu mexi em algumas coisas na Bios sim, mas teria que reiniciar o sistema para eu consultar e te dizer especificamente cada modificação que fiz. Pelo que lembro foram três modificações que fiz para poder fazer rodar o pendrive
Não, não é disso que estou falando e sim do setup da máquina (conhecido como o antigo BIOS que agora na sua máquina se chama UEFI), enfim, o firmware do hardware.
Se a renderização através da gpu estiver funcionando corretamente vai aparecer as "famosas" três engrenagens azul, verde e vermelha rodando sincronizadamente e no terminal e indicação FPS (frames por segundo).
bruno@bruno-TP301UA:/etc/default$ glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
302 frames in 5.0 seconds = 60.230 FPS
300 frames in 5.0 seconds = 59.970 FPS
300 frames in 5.0 seconds = 59.977 FPS
300 frames in 5.0 seconds = 59.984 FPS
300 frames in 5.0 seconds = 59.971 FPS
300 frames in 5.0 seconds = 59.959 FPS
300 frames in 5.0 seconds = 59.976 FPS
300 frames in 5.0 seconds = 59.978 FPS
Indo adiante: como essa máquina é nova e a gpu é um modelo recente (520), estava pensando em experimentar um Xorg mais turbinado, isto é, também mais recente, com os últimos drivers (ou quase) da Intel, ou seja a ppa Oibaf, talvez isso pudesse resultar em algo melhor para o sistema, inclusive a estabilidade.
Não sei o que dá instalando o Oibaf junto com o kernel 4.9RC8, certamente não previsto, mas só experimentando mesmo para ver o resultado.
Um detalhe importante: estamos supondo que você consertou aquele chaveamento anteriormente feito do CSM, desabilitando a opção e ainda que nenhum outro parâmetro do setup foi alterado, está conforme veio de fábrica, exceto se souber explicar coerentemente o que fez e porque fez, certo?
Caso contrário fica tudo errático, porque uma alteração no setup sem que se saiba exatamente o que se está fazendo e porque está fazendo pode levar a resultados imprevisíveis de comportamento do sistema.
#GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
bruno@bruno-TP301UA:/etc/default$ lspci | grep -i vga
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07)
00:13.0 Non-VGA unclassified device: Intel Corporation Device 9d35 (rev 21)
bruno@bruno-TP301UA:/etc/default$ sudo lshw -c display
*-display
descrição: VGA compatible controller
produto: HD Graphics 520
fabricante: Intel Corporation
ID físico: 2
informações do barramento: pci@0000:00:02.0
versão: 07
largura: 64 bits
clock: 33MHz
capacidades: pciexpress msi pm vga_controller bus_master cap_list rom
configuração: driver=i915 latency=0
recursos: irq:125 memória:de000000-deffffff memória:c0000000-cfffffff porta de E/S:f000(tamanho=64) memória:c0000-dffff
bruno@bruno-TP301UA:/etc/default$ sudo apt install mesa-utils
Lendo listas de pacotes... Pronto
Construindo árvore de dependências
Lendo informação de estado... Pronto
mesa-utils is already the newest version (8.3.0-2).
mesa-utils configurado para instalar manualmente.
Os seguintes pacotes foram instalados automaticamente e já não são necessários:
linux-headers-4.8.0-22 linux-headers-4.8.0-22-generic
linux-image-4.8.0-22-generic linux-image-extra-4.8.0-22-generic
Utilize 'sudo apt autoremove' para os remover.
0 pacotes atualizados, 0 pacotes novos instalados, 0 a serem removidos e 0 não atualizados.
bruno@bruno-TP301UA:/etc/default$
bruno@bruno-TP301UA:/etc/default$ glxinfo | grep render
direct rendering: Yes
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
Extended renderer info (GLX_MESA_query_renderer):
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 520 (Skylake GT2)
GL_ARB_conditional_render_inverted, GL_ARB_conservative_depth,
GL_MESA_texture_signed_rgba, GL_NV_conditional_render, GL_NV_depth_clamp,
GL_ARB_compute_shader, GL_ARB_conditional_render_inverted,
GL_NV_conditional_render, GL_NV_depth_clamp, GL_NV_light_max_exponent,
GL_OES_element_index_uint, GL_OES_fbo_render_mipmap,
bruno@bruno-TP301UA:/etc/default$ glxinfo | grep -i OpenGL
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 520 (Skylake GT2)
OpenGL core profile version string: 4.3 (Core Profile) Mesa 12.0.3
OpenGL core profile shading language version string: 4.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 12.0.3
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 12.0.3
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
OpenGL ES profile extensions:
bruno@bruno-TP301UA:/etc/default$ /usr/lib/nux/unity_support_test -p
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 520 (Skylake GT2)
OpenGL version string: 3.0 Mesa 12.0.3
Not software rendered: yes
Not blacklisted: yes
GLX fbconfig: yes
GLX texture from pixmap: yes
GL npot or rect textures: yes
GL vertex program: yes
GL fragment program: yes
GL vertex buffer object: yes
GL framebuffer object: yes
GL version is 1.4+: yes
Unity 3D supported: yes
bruno@bruno-TP301UA:/etc/default$