#26 Le 05/04/2017, à 19:36
- Bougron
Re : [Résolu] Pas de boot ASPIRE ES1 331
Voici le début de la référence du bios de ce portable https://www.acer.com/ac/fr/FR/content/s … t/6956?b=1
J'ai noté que c'est la version V2.10 du 23 novembre 2016 Peut-être a-t-elle aussi un autre nom
Bien sur installation avec windows. J'espère que ta version de bios va être bonne.
Dernière modification par Bougron (Le 05/04/2017, à 19:40)
Hors ligne
#27 Le 05/04/2017, à 21:00
- fazpedro
Re : [Résolu] Pas de boot ASPIRE ES1 331
Je commence à désespérer...
voici ce que ça donne :
root@xubuntu:/# mkdir /EFI/linux
mkdir: cannot create directory ‘/EFI/linux’: No such file or directory
root@xubuntu:/# cp /EFI/ubuntu/grubx64.efi /EFI/linux/BOOTX64.efi
cp: cannot stat '/EFI/ubuntu/grubx64.efi': No such file or directory
root@xubuntu:/# efibootmgr --create --disk /dev/mmcblk0 --part 1 --label "ubuntu" --loader "\EFI\linux\BOOTX64.efi"
** Warning ** : Boot0004 has same label ubuntu
BootCurrent: 0003
Timeout: 0 seconds
BootOrder: 0005,0001,2001,2002,2003
Boot0000* Unknown Device:
Boot0001* Windows Boot Manager
Boot0002* Unknown Device:
Boot0003* USB HDD: SanDisk SanDisk Cruzer
Boot0004* ubuntu
Boot2001* EFI USB Device
Boot2002* EFI DVD/CDROM
Boot2003* EFI Network
Boot0005* ubuntu
root@xubuntu:/#
sudo dmidecode -s bios-version
sudo: unable to resolve host xubuntu
V1.08
root@xubuntu:/#
Dernière modification par fazpedro (Le 05/04/2017, à 21:03)
Hors ligne
#28 Le 05/04/2017, à 21:37
- fazpedro
Re : [Résolu] Pas de boot ASPIRE ES1 331
Alors on avance...
j'ai refait ta commande ci-dessus
j'ai rebooté et là ...presque...
Choix du refind_x64..
un beau menu... choix du dernier à droite..Boot from ext4 vmzlunz...
et là enfin le logo xubuntu !
Mais... ensuite plus rien ne se passe...
je te mets les commandes ci-dessous qui peuvent aider ?
encore merci
xubuntu@xubuntu:~$ uname -a
Linux xubuntu 4.8.0-36-generic #36~16.04.1-Ubuntu SMP Sun Feb 5 09:39:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
xubuntu@xubuntu:~$ dpkg -l | grep -Ei "linux-(g|h|i|lo|si|t)"
ii linux-generic-hwe-16.04 4.8.0.36.8 amd64 Complete Generic Linux kernel and headers
ii linux-headers-4.8.0-36 4.8.0-36.36~16.04.1 all Header files related to Linux kernel version 4.8.0
ii linux-headers-4.8.0-36-generic 4.8.0-36.36~16.04.1 amd64 Linux kernel headers for version 4.8.0 on 64 bit x86 SMP
ii linux-headers-generic-hwe-16.04 4.8.0.36.8 amd64 Generic Linux kernel headers
ii linux-image-4.8.0-36-generic 4.8.0-36.36~16.04.1 amd64 Linux kernel image for version 4.8.0 on 64 bit x86 SMP
ii linux-image-extra-4.8.0-36-generic 4.8.0-36.36~16.04.1 amd64 Linux kernel extra modules for version 4.8.0 on 64 bit x86 SMP
ii linux-image-generic-hwe-16.04 4.8.0.36.8 amd64 Generic Linux kernel image
ii linux-signed-generic-hwe-16.04 4.8.0.36.8 amd64 Complete Signed Generic Linux kernel and headers
ii linux-signed-image-4.8.0-36-generic 4.8.0-36.36~16.04.1 amd64 Signed kernel image generic
ii linux-signed-image-generic-hwe-16.04 4.8.0.36.8 amd64 Signed Generic Linux kernel image
xubuntu@xubuntu:~$ ls -l /boot
total 47928
-rw-r--r-- 1 root root 1407843 Feb 5 12:32 abi-4.8.0-36-generic
-rw-r--r-- 1 root root 199575 Feb 5 12:32 config-4.8.0-36-generic
drwxr-xr-x 2 root root 4096 Apr 2 16:47 efi
drwxr-xr-x 2 root root 4096 Apr 3 18:17 grub
-rw-r--r-- 1 root root 42798326 Apr 2 12:19 initrd.img-4.8.0-36-generic
-rw-r--r-- 1 root root 182704 Jan 28 2016 memtest86+.bin
-rw-r--r-- 1 root root 184380 Jan 28 2016 memtest86+.elf
-rw-r--r-- 1 root root 184840 Jan 28 2016 memtest86+_multiboot.bin
-rw------- 1 root root 4060748 Feb 5 12:32 System.map-4.8.0-36-generic
xubuntu@xubuntu:~$
Hors ligne
#29 Le 05/04/2017, à 21:45
- Bougron
Re : [Résolu] Pas de boot ASPIRE ES1 331
C'est toujours de l'incompréhension...
Ma phrase commençait par "plus tard" Ce qui sous-entendait que c'était lorsque cela fonctionnerait
Comme tu veux le faire dès maintenant, en live USB, il est absolument nécessaire de monter la partition avec la commande
sudo umount /dev/mmcblk0p1
sudo mount /dev/mmcblk0p1 /mnt
La copie se faisant alors avec les commandes
sudo mkdir /mnt/EFI/linux
sudo cp /mnt/EFI/ubuntu/grubx64.efi /mnt/EFI/linux/BOOTX64.efi
J'ai noté que la codification de la commande efibootmgr a été acceptée
J'ai noté la réponse de la version du bios "V1.08" j'aurais préféré "V2.0"
Je ne sais toujours pas si le message d'erreur "Kernel panic... CPU not tainted.." n'a pas quelques mots de plus. Soit un peu avant. Soit au milieu. Soit après.
Si c'est aussi sec que cela, installes windows et mets le bios à jour..
Comme je note que ton EMMC dispose seulement de 32 Go d'espace, je crains que cela soit dur d'installer windows en dual boot,
Cependant, essaies quand même.
=> En live USB, avec GPARTED, supprimes la partition swap et diminues au maxima la partition / (5 Go) et essaies de voir si windows s'installe dans 27 go... Je ne sais pas mais c'est peut-être possible.
En fait, je ne sais pas trop les précautions que tu as prises avant d'installer windows
Dernière modification par Bougron (Le 05/04/2017, à 21:55)
Hors ligne
#30 Le 05/04/2017, à 21:49
- fazpedro
Re : [Résolu] Pas de boot ASPIRE ES1 331
xubuntu@xubuntu:~$ sudo umount /dev/sda1
umount: /cdrom: target is busy
(In some cases useful info about processes that
use the device is found by lsof(8) or fuser(1).)
xubuntu@xubuntu:~$ sudo mount /dev/sda1 /mnt
xubuntu@xubuntu:~$ sudo mkdir /mnt/EFI/linux
xubuntu@xubuntu:~$ sudo cp /mnt/EFI/ubuntu/grubx64.efi /mnt/EFI/linux/BOOTX64.efi
cp: cannot stat '/mnt/EFI/ubuntu/grubx64.efi': No such file or directory
xubuntu@xubuntu:~$
PS : Je n'ai plus Windows !
Hors ligne
#31 Le 05/04/2017, à 21:59
- Bougron
Re : [Résolu] Pas de boot ASPIRE ES1 331
J'ai rectifié mon erreur.
Au besoin, on ira analyser la trace de démarrage et tu feras un rapport de bug https://lists.debian.org/debian-kernel/ … 00710.html
Mais pour ubuntu c'est https://doc.ubuntu-fr.org/launchpad
Pour windows, c'est bête, Télécharges-le https://www.microsoft.com/fr-fr/softwar … ndows10ISO
Voici la codif pour la trace du démarrage raté.
=============
Pour récupérer quelques traces du vrai démarrage qui plante par le message "Kernel panic... CPU not tainted"
Tu peux le faire dès maintenant, en live USB, il est absolument nécessaire de monter la partition avec la commande racine ( / )
sudo umount /dev/mmcblk0p2
sudo mount /dev/mmcblk0p2 /mnt
gedit /mnt/var/log/syslog
Tu posteras le résultat.
gedit /mnt/var/log/kern.log
Tu posteras le résultat.
Dernière modification par Bougron (Le 05/04/2017, à 22:10)
Hors ligne
#32 Le 05/04/2017, à 22:05
- fazpedro
Re : [Résolu] Pas de boot ASPIRE ES1 331
Hourra
Avec les commandes
sudo mkdir /mnt/EFI/linux
sudo cp /mnt/EFI/ubuntu/grubx64.efi /mnt/EFI/linux/BOOTX64.efi
Nickel !
juste une chose : au démarrage, il faut choisir Linux(BJNB4R) puis ensuite *Ubuntu...
est-ce que l'on peut le mettre par défaut ? sans tout casser bien sûr...
Hors ligne
#33 Le 05/04/2017, à 22:12
- Bougron
Re : [Résolu] Pas de boot ASPIRE ES1 331
Cela veut-il dire que tu es dans la session de ubuntu et qu'il fonctionne?
C'est toi qui m'apprend le mot BJNB4R
Dernière modification par Bougron (Le 05/04/2017, à 22:18)
Hors ligne
#34 Le 05/04/2017, à 22:34
- fazpedro
Re : [Résolu] Pas de boot ASPIRE ES1 331
Cela veut-il dire que tu es dans la session de ubuntu et qu'il fonctionne?
C'est toi qui m'apprend le mot BJNB4R
Oui c'est bien cela
le seul souci c'est qu'il faur que j'appuie sur la touche F12 au démarrage sinon on revient sur le menu refind...
merci
Hors ligne
#35 Le 05/04/2017, à 22:39
- Bougron
Re : [Résolu] Pas de boot ASPIRE ES1 331
C'est une bonne surprise pour moi, car je craignais.
peux-tu donner le résultat de la commande
sudo efibootmgr -v
C'est peut-être un peu d'ordre à mettre dans cette structure
ainsi que le retour des commandes
sudo ls -Rls /boot/efi/EFI/ubuntu
sudo ls -Rls /boot/efi/EFI/linux
Dernière modification par Bougron (Le 05/04/2017, à 22:41)
Hors ligne
#36 Le 06/04/2017, à 17:04
- fazpedro
Re : [Résolu] Pas de boot ASPIRE ES1 331
Et voici :
Aspire-ES1-332:~$ sudo efibootmgr -v
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0001,0002,2001,2002,2003
Boot0000* Unknown Device: HD(1,GPT,3f7264e6-734a-4f82-bc2a-daaa0a94d631,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)RC
Boot0001* Windows Boot Manager HD(1,GPT,3f7264e6-734a-4f82-bc2a-daaa0a94d631,0x800,0x100000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)RC
Boot0002* Linux HD(1,GPT,3f7264e6-734a-4f82-bc2a-daaa0a94d631,0x800,0x100000)/File(\EFI\Linux\BOOTX64.efi)RC
Boot0003* Unknown Device: HD(1,GPT,3f7264e6-734a-4f82-bc2a-daaa0a94d631,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)RC
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RC
Aspire-ES1-332:~$ sudo ls -Rls /boot/efi/EFI/ubuntu
/boot/efi/EFI/ubuntu:
total 2552
72 -rwxr-xr-x 1 root root 72144 avril 4 22:54 fbx64.efi
4 drwxr-xr-x 2 root root 4096 avril 4 17:54 fw
64 -rwxr-xr-x 1 root root 64352 avril 4 17:54 fwupx64.efi
4 -rwxr-xr-x 1 root root 117 avril 4 22:54 grub.cfg
120 -rwxr-xr-x 1 root root 120832 avril 5 18:56 grubx64.efi
1144 -rwxr-xr-x 1 root root 1168464 avril 4 22:54 mmx64.efi
1144 -rwxr-xr-x 1 root root 1169992 avril 4 22:54 shimx64.efi
/boot/efi/EFI/ubuntu/fw:
total 0
Aspire-ES1-332:~$ sudo ls -Rls /boot/efi/EFI/linux
/boot/efi/EFI/linux:
total 120
120 -rwxr-xr-x 1 root root 120832 avril 5 21:51 BOOTX64.efi
Hors ligne
#37 Le 06/04/2017, à 20:53
- Bougron
Re : [Résolu] Pas de boot ASPIRE ES1 331
Bonsoir.
Si ton bios EFI réagit classiquement, on va remettre ´linux' en premier avec la commande
sudo efibootmgr -o 2,1
Dernière modification par Bougron (Le 06/04/2017, à 20:54)
Hors ligne
#38 Le 06/04/2017, à 21:05
- fazpedro
Re : [Résolu] Pas de boot ASPIRE ES1 331
Réponse :
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0002,0001
Boot0000* Unknown Device:
Boot0001* Windows Boot Manager
Boot0002* Linux
Boot0003* Unknown Device:
Boot2001* EFI USB Device
Boot2002* EFI DVD/CDROM
Boot2003* EFI Network
J'ai fait un reboot mais cela n'a rien changé...
Dernière modification par fazpedro (Le 06/04/2017, à 21:12)
Hors ligne
#39 Le 06/04/2017, à 21:54
- Bougron
Re : [Résolu] Pas de boot ASPIRE ES1 331
Je pense qu'il faut en rester là. Il n'utilise pas le contenu de la nvram.
Si tu pouvais faire une photo de tes deux grilles nécessaires pour booter, cela serait bien car j'ai du mal à appréhender leur contenu.
et faire la commande permettant de connaitre le noyau
uname -a
Merci.
Dernière modification par Bougron (Le 07/04/2017, à 00:43)
Hors ligne
#40 Le 07/04/2017, à 17:07
- fazpedro
Re : [Résolu] Pas de boot ASPIRE ES1 331
Voici les images dans l'ordre :
Choix 1, 5 et 6 : bloque sur grub...
Choix 3 : menuy shim
Choix 4 : menu refind
Si choix vmz.. avec menu refind : bloque sur le logo xubuntu
Noyau :
Aspire-ES1-332 4.8.0-46-generic #49~16.04.1-Ubuntu SMP Fri Mar 31 14:51:03 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Images :
http://hpics.li/0c70f8e
http://hpics.li/87fc5b8
http://hpics.li/4641dfb
http://hpics.li/0b6ac27
http://hpics.li/5bb2fd1
http://hpics.li/7a91ed0
Hors ligne
#41 Le 07/04/2017, à 18:24
- Bougron
Re : [Résolu] Pas de boot ASPIRE ES1 331
Bonjour
Je n'ai pas trop compris toute ta liste de choix.
Sur mon micro, La première grille qui s'affiche est celle qui correspond à la 4eme de ta liste http://www.hostingpics.net/viewer.php?i … 020871.jpg
et lorsque je choisis l'icône qui correspond au grub, cela boote bien tout comme chez toi.
Mais pour le démarrage suivant, refind est directement positionné sur mon dernier choix. Il ne me reste qu'à valider ou d'attendre le time-out.
Je pense que c'est un problème de paramétrage... Mais je n'ai pas encore trouvé lesquels.
sudo gedit /boot/efi/EFI/refind/refind.conf
Notes qu'au lieu de valider, je peux appuyer sur la touche F2 pour avoir la liste des noyaux. Puis en ayant choisi un noyau je peux encore appuyer sur la touche F2 pour modifier directement le paramétrage de la ligne de commande.
Mais, en suivant une autre discussion, Je pense que lorsque je t'ai fais déplacer refind pour mettre le programme de démarrage dans la structure de windows, ce n'était pas suffisant, il faillait certainement en mettre plus.
Il faudrait donc que tu refasses la commande suivante pour voir s'il y a une évolution.
sudo mvrefind /boot/efi/EFI/refind /boot/efi/EFI/linux
puis
sudo mv /boot/efi/EFI/linux/refind_x64.efi /boot/efi/EFI/linux/BOOTX64.efi
Dernière modification par Bougron (Le 07/04/2017, à 19:28)
Hors ligne
#42 Le 07/04/2017, à 20:38
- fazpedro
Re : [Résolu] Pas de boot ASPIRE ES1 331
Aspire-ES1-332:~$ sudo mvrefind /boot/efi/EFI/refind /boot/efi/EFI/linux
/boot/efi/EFI/linux isn't empty! Aborting!
Aspire-ES1-332:~$ sudo mv /boot/efi/EFI/linux/refind_x64.efi /boot/efi/EFI/linux/BOOTX64.efi
mv: impossible d'évaluer '/boot/efi/EFI/linux/refind_x64.efi': Aucun fichier ou dossier de ce type
sudo gedit /boot/efi/EFI/refind/refind.conf
#
# refind.conf
# Configuration file for the rEFInd boot menu
#
# Timeout in seconds for the main menu screen. Setting the timeout to 0
# disables automatic booting (i.e., no timeout). Setting it to -1 causes
# an immediate boot to the default OS *UNLESS* a keypress is in the buffer
# when rEFInd launches, in which case that keypress is interpreted as a
# shortcut key. If no matching shortcut is found, rEFInd displays its
# menu with no timeout.
#
timeout 20
# Screen saver timeout; the screen blanks after the specified number of
# seconds with no keyboard input. The screen returns after most keypresses
# (unfortunately, not including modifier keys such as Shift, Control, Alt,
# or Option). Setting a value of "-1" causes rEFInd to start up with its
# screen saver active. The default is 0, which disables the screen saver.
#screensaver 300
# Hide user interface elements for personal preference or to increase
# security:
# banner - the rEFInd title banner (built-in or loaded via "banner")
# label - boot option text label in the menu
# singleuser - remove the submenu options to boot Mac OS X in single-user
# or verbose modes; affects ONLY MacOS X
# safemode - remove the submenu option to boot Mac OS X in "safe mode"
# hwtest - the submenu option to run Apple's hardware test
# arrows - scroll arrows on the OS selection tag line
# hints - brief command summary in the menu
# editor - the options editor (+, F2, or Insert on boot options menu)
# badges - device-type badges for boot options
# all - all of the above
# Default is none of these (all elements active)
#
#hideui singleuser
#hideui all
# Set the name of a subdirectory in which icons are stored. Icons must
# have the same names they have in the standard directory. The directory
# name is specified relative to the main rEFInd binary's directory. If
# an icon can't be found in the specified directory, an attempt is made
# to load it from the default directory; thus, you can replace just some
# icons in your own directory and rely on the default for others.
# Default is "icons".
#
#icons_dir myicons
#icons_dir icons/snowy
# Use a custom title banner instead of the rEFInd icon and name. The file
# path is relative to the directory where refind.efi is located. The color
# in the top left corner of the image is used as the background color
# for the menu screens. Currently uncompressed BMP images with color
# depths of 24, 8, 4 or 1 bits are supported, as well as PNG images.
#
#banner hostname.bmp
#banner mybanner.png
#banner icons/snowy/banner-snowy.png
# Specify how to handle banners that aren't exactly the same as the screen
# size:
# noscale - Crop if too big, show with border if too small
# fillscreen - Fill the screen
# Default is noscale
#
#banner_scale fillscreen
# Icon sizes. All icons are square, so just one value is specified. The
# big icons are used for OS selectors in the first row and the small
# icons are used for tools on the second row. Drive-type badges are 1/4
# the size of the big icons. Legal values are 32 and above. If the icon
# files do not hold icons of the proper size, the icons are scaled to
# the specified size. The default values are 48 and 128 for small and
# big icons, respectively.
#
#small_icon_size 96
#big_icon_size 256
# Custom images for the selection background. There is a big one (144 x 144)
# for the OS icons, and a small one (64 x 64) for the function icons in the
# second row. If only a small image is given, that one is also used for
# the big icons by stretching it in the middle. If only a big one is given,
# the built-in default will be used for the small icons.
#
# Like the banner option above, these options take a filename of an
# uncompressed BMP image file with a color depth of 24, 8, 4, or 1 bits,
# or a PNG image. The PNG format is required if you need transparency
# support (to let you "see through" to a full-screen banner).
#
#selection_big selection-big.bmp
#selection_small selection-small.bmp
# Set the font to be used for all textual displays in graphics mode.
# The font must be a PNG file with alpha channel transparency. It must
# contain ASCII characters 32-126 (space through tilde), inclusive, plus
# a glyph to be displayed in place of characters outside of this range,
# for a total of 96 glyphs. Only monospaced fonts are supported. Fonts
# may be of any size, although large fonts can produce display
# irregularities.
# The default is rEFInd's built-in font, Luxi Mono Regular 12 point.
#
#font myfont.png
# Use text mode only. When enabled, this option forces rEFInd into text mode.
# Passing this option a "0" value causes graphics mode to be used. Pasing
# it no value or any non-0 value causes text mode to be used.
# Default is to use graphics mode.
#
#textonly
# Set the EFI text mode to be used for textual displays. This option
# takes a single digit that refers to a mode number. Mode 0 is normally
# 80x25, 1 is sometimes 80x50, and higher numbers are system-specific
# modes. Mode 1024 is a special code that tells rEFInd to not set the
# text mode; it uses whatever was in use when the program was launched.
# If you specify an invalid mode, rEFInd pauses during boot to inform
# you of valid modes.
# CAUTION: On VirtualBox, and perhaps on some real computers, specifying
# a text mode and uncommenting the "textonly" option while NOT specifying
# a resolution can result in an unusable display in the booted OS.
# Default is 1024 (no change)
#
#textmode 2
# Set the screen's video resolution. Pass this option either:
# * two values, corresponding to the X and Y resolutions
# * one value, corresponding to a GOP (UEFI) video mode
# Note that not all resolutions are supported. On UEFI systems, passing
# an incorrect value results in a message being shown on the screen to
# that effect, along with a list of supported modes. On EFI 1.x systems
# (e.g., Macintoshes), setting an incorrect mode silently fails. On both
# types of systems, setting an incorrect resolution results in the default
# resolution being used. A resolution of 1024x768 usually works, but higher
# values often don't.
# Default is "0 0" (use the system default resolution, usually 800x600).
#
#resolution 1024 768
#resolution 1440 900
#resolution 3
# Enable touch screen support. If active, this feature enables use of
# touch screen controls (as on tablets). Note, however, that not all
# tablets' EFIs provide the necessary underlying support, so this
# feature may not work for you. If it does work, you should be able
# to launch an OS or tool by touching it. In a submenu, touching
# anywhere launches the currently-selection item; there is, at present,
# no way to select a specific submenu item.
#
#enable_touch
# Launch specified OSes in graphics mode. By default, rEFInd switches
# to text mode and displays basic pre-launch information when launching
# all OSes except OS X. Using graphics mode can produce a more seamless
# transition, but displays no information, which can make matters
# difficult if you must debug a problem. Also, on at least one known
# computer, using graphics mode prevents a crash when using the Linux
# kernel's EFI stub loader. You can specify an empty list to boot all
# OSes in text mode.
# Valid options:
# osx - Mac OS X
# linux - A Linux kernel with EFI stub loader
# elilo - The ELILO boot loader
# grub - The GRUB (Legacy or 2) boot loader
# windows - Microsoft Windows
# Default value: osx
#
#use_graphics_for osx,linux
# Which non-bootloader tools to show on the tools line, and in what
# order to display them:
# shell - the EFI shell (requires external program; see rEFInd
# documentation for details)
# memtest - the memtest86 program, in EFI/tools, EFI/memtest86,
# EFI/memtest, EFI/tools/memtest86, or EFI/tools/memtest
# gptsync - the (dangerous) gptsync.efi utility (requires external
# program; see rEFInd documentation for details)
# gdisk - the gdisk partitioning program
# apple_recovery - boots the Apple Recovery HD partition, if present
# windows_recovery - boots an OEM Windows recovery tool, if present
# (see also the windows_recovery_files option)
# mok_tool - makes available the Machine Owner Key (MOK) maintenance
# tool, MokManager.efi, used on Secure Boot systems
# csr_rotate - adjusts Apple System Integrity Protection (SIP)
# policy. Requires "csr_values" to be set.
# about - an "about this program" option
# exit - a tag to exit from rEFInd
# shutdown - shuts down the computer (a bug causes this to reboot
# many UEFI systems)
# reboot - a tag to reboot the computer
# firmware - a tag to reboot the computer into the firmware's
# user interface (ignored on older computers)
# fwupdate - a tag to update the firmware; launches the fwupx64.efi
# (or similar) program
# netboot - launch the ipxe.efi tool for network (PXE) booting
# Default is shell,memtest,gdisk,apple_recovery,windows_recovery,mok_tool,about,shutdown,reboot,firmware,fwupdate
#
#showtools shell, gdisk, memtest, mok_tool, apple_recovery, windows_recovery, about, reboot, exit, firmware, fwupdate
# Boot loaders that can launch a Windows restore or emergency system.
# These tend to be OEM-specific.
# Default is LRS_ESP:/EFI/Microsoft/Boot/LrsBootmgr.efi
#
#windows_recovery_files LRS_ESP:/EFI/Microsoft/Boot/LrsBootmgr.efi
# Directories in which to search for EFI drivers. These drivers can
# provide filesystem support, give access to hard disks on plug-in
# controllers, etc. In most cases none are needed, but if you add
# EFI drivers and you want rEFInd to automatically load them, you
# should specify one or more paths here. rEFInd always scans the
# "drivers" and "drivers_{arch}" subdirectories of its own installation
# directory (where "{arch}" is your architecture code); this option
# specifies ADDITIONAL directories to scan.
# Default is to scan no additional directories for EFI drivers
#
#scan_driver_dirs EFI/tools/drivers,drivers
# Which types of boot loaders to search, and in what order to display them:
# internal - internal EFI disk-based boot loaders
# external - external EFI disk-based boot loaders
# optical - EFI optical discs (CD, DVD, etc.)
# netboot - EFI network (PXE) boot options
# hdbios - BIOS disk-based boot loaders
# biosexternal - BIOS external boot loaders (USB, eSATA, etc.)
# cd - BIOS optical-disc boot loaders
# manual - use stanzas later in this configuration file
# Note that the legacy BIOS options require firmware support, which is
# not present on all computers.
# The netboot option is experimental and relies on the ipxe.efi and
# ipxe_discover.efi program files.
# On UEFI PCs, default is internal,external,optical,manual
# On Macs, default is internal,hdbios,external,biosexternal,optical,cd,manual
#
#scanfor internal,external,optical,manual
# By default, rEFInd relies on the UEFI firmware to detect BIOS-mode boot
# devices. This sometimes doesn't detect all the available devices, though.
# For these cases, uefi_deep_legacy_scan results in a forced scan and
# modification of NVRAM variables on each boot. Adding "0", "off", or
# "false" resets to the default value. This token has no effect on Macs or
# when no BIOS-mode options are set via scanfor.
# Default is unset (or "uefi_deep_legacy_scan false")
#
#uefi_deep_legacy_scan
# Delay for the specified number of seconds before scanning disks.
# This can help some users who find that some of their disks
# (usually external or optical discs) aren't detected initially,
# but are detected after pressing Esc.
# The default is 0.
#
#scan_delay 5
# When scanning volumes for EFI boot loaders, rEFInd always looks for
# Mac OS X's and Microsoft Windows' boot loaders in their normal locations,
# and scans the root directory and every subdirectory of the /EFI directory
# for additional boot loaders, but it doesn't recurse into these directories.
# The also_scan_dirs token adds more directories to the scan list.
# Directories are specified relative to the volume's root directory. This
# option applies to ALL the volumes that rEFInd scans UNLESS you include
# a volume name and colon before the directory name, as in "myvol:/somedir"
# to scan the somedir directory only on the filesystem named myvol. If a
# specified directory doesn't exist, it's ignored (no error condition
# results). The default is to scan the "boot" directory in addition to
# various hard-coded directories.
#
#also_scan_dirs boot,ESP2:EFI/linux/kernels
# Partitions (or whole disks, for legacy-mode boots) to omit from scans.
# For EFI-mode scans, you must specify a volume by its label, which you
# can obtain in an EFI shell by typing "vol", from Linux by typing
# "blkid /dev/{devicename}", or by examining the disk's label in various
# OSes' file browsers.
# For legacy-mode scans, you can specify any subset of the boot loader
# description shown when you highlight the option in rEFInd.
# The default is "LRS_ESP".
#
#dont_scan_volumes "Recovery HD"
# Directories that should NOT be scanned for boot loaders. By default,
# rEFInd doesn't scan its own directory, the EFI/tools directory, the
# EFI/memtest directory, the EFI/memtest86 directory, or the
# com.apple.recovery.boot directory. Using the dont_scan_dirs option
# enables you to "blacklist" other directories; but be sure to use "+"
# as the first element if you want to continue blacklisting existing
# directories. You might use this token to keep EFI/boot/bootx64.efi out
# of the menu if that's a duplicate of another boot loader or to exclude
# a directory that holds drivers or non-bootloader utilities provided by
# a hardware manufacturer. If a directory is listed both here and in
# also_scan_dirs, dont_scan_dirs takes precedence. Note that this
# blacklist applies to ALL the filesystems that rEFInd scans, not just
# the ESP, unless you precede the directory name by a filesystem name,
# as in "myvol:EFI/somedir" to exclude EFI/somedir from the scan on the
# myvol volume but not on other volumes.
#
#dont_scan_dirs ESP:/EFI/boot,EFI/Dell,EFI/memtest86
# Files that should NOT be included as EFI boot loaders (on the
# first line of the display). If you're using a boot loader that
# relies on support programs or drivers that are installed alongside
# the main binary or if you want to "blacklist" certain loaders by
# name rather than location, use this option. Note that this will
# NOT prevent certain binaries from showing up in the second-row
# set of tools. Most notably, various Secure Boot and recovery
# tools are present in this list, but may appear as second-row
# items.
# The file may be specified as a bare name (e.g., "notme.efi"), as
# a complete filename (e.g., "/EFI/somedir/notme.efi"), or as a
# complete filename with volume (e.g., "SOMEDISK:/EFI/somedir/notme.efi").
# The default is shim.efi,shim-fedora.efi,shimx64.efi,PreLoader.efi,
# TextMode.efi,ebounce.efi,GraphicsConsole.efi,MokManager.efi,HashTool.efi,
# HashTool-signed.efi,bootmgr.efi
#
#dont_scan_files shim.efi,MokManager.efi
# Scan for Linux kernels that lack a ".efi" filename extension. This is
# useful for better integration with Linux distributions that provide
# kernels with EFI stub loaders but that don't give those kernels filenames
# that end in ".efi", particularly if the kernels are stored on a
# filesystem that the EFI can read. When set to "1", "true", or "on", this
# option causes all files in scanned directories with names that begin with
# "vmlinuz" or "bzImage" to be included as loaders, even if they lack ".efi"
# extensions. Passing this option a "0", "false", or "off" value causes
# kernels without ".efi" extensions to NOT be scanned.
# Default is "true" -- to scan for kernels without ".efi" extensions.
#
#scan_all_linux_kernels false
# Combine all Linux kernels in a given directory into a single entry.
# When so set, the kernel with the most recent time stamp will be launched
# by default, and its filename will appear in the entry's description.
# To launch other kernels, the user must press F2 or Insert; alternate
# kernels then appear as options on the sub-menu.
# Default is "true" -- kernels are "folded" into a single menu entry.
#
#fold_linux_kernels false
# Set the maximum number of tags that can be displayed on the screen at
# any time. If more loaders are discovered than this value, rEFInd shows
# a subset in a scrolling list. If this value is set too high for the
# screen to handle, it's reduced to the value that the screen can manage.
# If this value is set to 0 (the default), it's adjusted to the number
# that the screen can handle.
#
#max_tags 0
# Set the default menu selection. The available arguments match the
# keyboard accelerators available within rEFInd. You may select the
# default loader using:
# - A digit between 1 and 9, in which case the Nth loader in the menu
# will be the default.
# - A "+" symbol at the start of the string, which refers to the most
# recently booted loader.
# - Any substring that corresponds to a portion of the loader's title
# (usually the OS's name, boot loader's path, or a volume or
# filesystem title).
# You may also specify multiple selectors by separating them with commas
# and enclosing the list in quotes. (The "+" option is only meaningful in
# this context.)
# If you follow the selector(s) with two times, in 24-hour format, the
# default will apply only between those times. The times are in the
# motherboard's time standard, whether that's UTC or local time, so if
# you use UTC, you'll need to adjust this from local time manually.
# Times may span midnight as in "23:30 00:30", which applies to 11:30 PM
# to 12:30 AM. You may specify multiple default_selection lines, in which
# case the last one to match takes precedence. Thus, you can set a main
# option without a time followed by one or more that include times to
# set different defaults for different times of day.
# The default behavior is to boot the previously-booted OS.
#
#default_selection 1
#default_selection Microsoft
#default_selection "+,bzImage,vmlinuz"
#default_selection Maintenance 23:30 2:00
#default_selection "Maintenance,OS X" 1:00 2:30
# Enable VMX bit and lock the CPU MSR if unlocked.
# On some Intel Apple computers, the firmware does not lock the MSR 0x3A.
# The symptom on Windows is Hyper-V not working even if the CPU
# meets the minimum requirements (HW assisted virtualization and SLAT)
# DO NOT SET THIS EXCEPT ON INTEL CPUs THAT SUPPORT VMX! See
# http://www.thomas-krenn.com/en/wiki/Activating_the_Intel_VT_Virtualization_Feature!
# for more on this subject.
# The default is false: Don't try to enable and lock the MSR.
#
#enable_and_lock_vmx false
# Tell a Mac's EFI that OS X is about to be launched, even when it's not.
# This option causes some Macs to initialize their hardware differently than
# when a third-party OS is launched normally. In some cases (particularly on
# Macs with multiple video cards), using this option can cause hardware to
# work that would not otherwise work. On the other hand, using this option
# when it is not necessary can cause hardware (such as keyboards and mice) to
# become inaccessible. Therefore, you should not enable this option if your
# non-Apple OSes work correctly; enable it only if you have problems with
# some hardware devices. When needed, a value of "10.9" usually works, but
# you can experiment with other values. This feature has no effect on
# non-Apple computers.
# The default is inactive (no OS X spoofing is done).
#
#spoof_osx_version 10.9
# Set the CSR values for Apple's System Integrity Protection (SIP) feature.
# Values are one-byte (two-character) hexadecimal numbers. These values
# define which specific security features are enabled. Below are the codes
# for what the values mean. Add them up (in hexadecimal!) to set new values.
# Apple's "csrutil enable" and "csrutil disable" commands set values of 10
# and 77, respectively.
# CSR_ALLOW_UNTRUSTED_KEXTS 0x01
# CSR_ALLOW_UNRESTRICTED_FS 0x02
# CSR_ALLOW_TASK_FOR_PID 0x04
# CSR_ALLOW_KERNEL_DEBUGGER 0x08
# CSR_ALLOW_APPLE_INTERNAL 0x10
# CSR_ALLOW_UNRESTRICTED_DTRACE 0x20
# CSR_ALLOW_UNRESTRICTED_NVRAM 0x40
#
#csr_values 10,77
# Include a secondary configuration file within this one. This secondary
# file is loaded as if its options appeared at the point of the "include"
# token itself, so if you want to override a setting in the main file,
# the secondary file must be referenced AFTER the setting you want to
# override. Note that the secondary file may NOT load a tertiary file.
#
#include manual.conf
# Sample manual configuration stanzas. Each begins with the "menuentry"
# keyword followed by a name that's to appear in the menu (use quotes
# if you want the name to contain a space) and an open curly brace
# ("{"). Each entry ends with a close curly brace ("}"). Common
# keywords within each stanza include:
#
# volume - identifies the filesystem from which subsequent files
# are loaded. You can specify the volume by filesystem
# label, by partition label, or by partition GUID number
# (but NOT yet by filesystem UUID number).
# loader - identifies the boot loader file
# initrd - Specifies an initial RAM disk file
# icon - specifies a custom boot loader icon
# ostype - OS type code to determine boot options available by
# pressing Insert. Valid values are "MacOS", "Linux",
# "Windows", and "XOM". Case-sensitive.
# graphics - set to "on" to enable graphics-mode boot (useful
# mainly for MacOS) or "off" for text-mode boot.
# Default is auto-detected from loader filename.
# options - sets options to be passed to the boot loader; use
# quotes if more than one option should be passed or
# if any options use characters that might be changed
# by rEFInd parsing procedures (=, /, #, or tab).
# disabled - use alone or set to "yes" to disable this entry.
#
# Note that you can use either DOS/Windows/EFI-style backslashes (\)
# or Unix-style forward slashes (/) as directory separators. Either
# way, all file references are on the ESP from which rEFInd was
# launched.
# Use of quotes around parameters causes them to be interpreted as
# one keyword, and for parsing of special characters (spaces, =, /,
# and #) to be disabled. This is useful mainly with the "options"
# keyword. Use of quotes around parameters that specify filenames is
# permissible, but you must then use backslashes instead of slashes,
# except when you must pass a forward slash to the loader, as when
# passing a root= option to a Linux kernel.
# Below are several sample boot stanzas. All are disabled by default.
# Find one similar to what you need, copy it, remove the "disabled" line,
# and adjust the entries to suit your needs.
# A sample entry for a Linux 3.13 kernel with EFI boot stub support
# on a partition with a GUID of 904404F8-B481-440C-A1E3-11A5A954E601.
# This entry includes Linux-specific boot options and specification
# of an initial RAM disk. Note uses of Linux-style forward slashes.
# Also note that a leading slash is optional in file specifications.
menuentry Linux {
icon EFI/refind/icons/os_linux.png
volume 904404F8-B481-440C-A1E3-11A5A954E601
loader bzImage-3.3.0-rc7
initrd initrd-3.3.0.img
options "ro root=UUID=5f96cafa-e0a7-4057-b18f-fa709db5b837"
disabled
}
# Below is a more complex Linux example, specifically for Arch Linux.
# This example MUST be modified for your specific installation; if nothing
# else, the PARTUUID code must be changed for your disk. Because Arch Linux
# does not include version numbers in its kernel and initrd filenames, you
# may need to use manual boot stanzas when using fallback initrds or
# multiple kernels with Arch. This example is modified from one in the Arch
# wiki page on rEFInd (https://wiki.archlinux.org/index.php/rEFInd).
menuentry "Arch Linux" {
icon /EFI/refind/icons/os_arch.png
volume "Arch Linux"
loader /boot/vmlinuz-linux
initrd /boot/initramfs-linux.img
options "root=PARTUUID=5028fa50-0079-4c40-b240-abfaf28693ea rw add_efi_memmap"
submenuentry "Boot using fallback initramfs" {
initrd /boot/initramfs-linux-fallback.img
}
submenuentry "Boot to terminal" {
add_options "systemd.unit=multi-user.target"
}
disabled
}
# A sample entry for loading Ubuntu using its standard name for
# its GRUB 2 boot loader. Note uses of Linux-style forward slashes
menuentry Ubuntu {
loader /EFI/ubuntu/grubx64.efi
icon /EFI/refind/icons/os_linux.png
disabled
}
# A minimal ELILO entry, which probably offers nothing that
# auto-detection can't accomplish.
menuentry "ELILO" {
loader \EFI\elilo\elilo.efi
disabled
}
# Like the ELILO entry, this one offers nothing that auto-detection
# can't do; but you might use it if you want to disable auto-detection
# but still boot Windows....
menuentry "Windows 7" {
loader \EFI\Microsoft\Boot\bootmgfw.efi
disabled
}
# EFI shells are programs just like boot loaders, and can be
# launched in the same way. You can pass a shell the name of a
# script that it's to run on the "options" line. The script
# could initialize hardware and then launch an OS, or it could
# do something entirely different.
menuentry "Windows via shell script" {
icon \EFI\refind\icons\os_win.png
loader \EFI\tools\shell.efi
options "fs0:\EFI\tools\launch_windows.nsh"
disabled
}
# Mac OS is normally detected and run automatically; however,
# if you want to do something unusual, a manual boot stanza may
# be the way to do it. This one does nothing very unusual, but
# it may serve as a starting point. Note that you'll almost
# certainly need to change the "volume" line for this example
# to work.
menuentry "My Mac OS X" {
icon \EFI\refind\icons\os_mac.png
volume "OS X boot"
loader \System\Library\CoreServices\boot.efi
disabled
}
il y a pas de fichier refind dans le répertoire non ?
/boot/efi/EFI/linux$ ls
BOOTX64.efi
/boot/efi/EFI/ubuntu$ ls
fbx64.efi fw fwupx64.efi grub.cfg grubx64.efi mmx64.efi shimx64.efi
/boot$ ls
abi-4.4.0-72-generic config-4.8.0-36-generic grub.bak memtest86+.bin System.map-4.4.0-72-generic vmlinuz-4.8.0-36-generic
abi-4.8.0-36-generic config-4.8.0-46-generic initrd.img-4.4.0-72-generic memtest86+.elf System.map-4.8.0-36-generic vmlinuz-4.8.0-46-generic
abi-4.8.0-46-generic efi initrd.img-4.8.0-36-generic memtest86+_multiboot.bin System.map-4.8.0-46-generic
config-4.4.0-72-generic grub initrd.img-4.8.0-46-generic refind_linux.conf vmlinuz-4.4.0-72-generic
dans le menu refind,
j'ai le dernier choix :
Boot boot\vmlinuz-4.8.0-36-generic from 24 Gib ext4 volume
mais dans le répertoire boot, je n'ai pas le même vmlinuz, c'est pas ça ?
Dernière modification par fazpedro (Le 07/04/2017, à 20:59)
Hors ligne
#43 Le 07/04/2017, à 22:31
- Bougron
Re : [Résolu] Pas de boot ASPIRE ES1 331
Je te propose cela: Renommer le répertoire afin de pouvoir revenir en arrière si besoin. Puis de le recréer vide.
sudo mv /boot/efi/EFI/linux /boot/efi/EFI/linux.old
sudo mkdir /boot/efi/EFI/linux
Puis refaire la commande
sudo mvrefind /boot/efi/EFI/refind /boot/efi/EFI/linux
Car je pense qu'en plus de déplacer les fichiers, certains fichiers sont modifiés afin de prendre en compte les nouveaux noms. Par exemple cela
menuentry Linux {
icon EFI/refind/icons/os_linux.png
volume 904404F8-B481-440C-A1E3-11A5A954E601
loader bzImage-3.3.0-rc7
initrd initrd-3.3.0.img
options "ro root=UUID=5f96cafa-e0a7-4057-b18f-fa709db5b837"
disabled
}
puis
sudo mv /boot/efi/EFI/linux/refind_x64.efi /boot/efi/EFI/linux/BOOTX64.efi
car ce bios ne sait booter que sur ce fichier. C'est pour cela qu'il n'y a plus de fichier refind_x64.efi
Dans le répertoire boot, tu as les fichiers de boot suivants:
vmlinuz-4.8.0-46-generic
vmlinuz-4.8.0-36-generic
vmlinuz-4.4.0-72-generic
En standard, Refind, te propose le dernier (c'est comme grub) Mais si tu ne fais pas "return" et que tu appuies sur F2, il te proposera la liste des trois.
c'est intéressant à utiliser uniquement lorsque le dernier ne fonctionne plus pour une raison inconnue.
Dernière modification par Bougron (Le 07/04/2017, à 22:48)
Hors ligne
#44 Le 07/04/2017, à 22:36
- fazpedro
Re : [Résolu] Pas de boot ASPIRE ES1 331
Aspire-ES1-332:~$ sudo mv /boot/efi/EFI/linux /boot/efi/EFI/linux.old
Aspire-ES1-332:~$ sudo mkdir /boot/efi/EFI/linux
Aspire-ES1-332:~$ sudo mvrefind /boot/efi/EFI/refind /boot/efi/EFI/linux
ALERT: There were problems running the efibootmgr program! Your moved rEFInd
might not run!
Aspire-ES1-332:~$ sudo mv /boot/efi/EFI/linux/refind_x64.efi /boot/efi/EFI/linux/BOOTX64.efi
Je reboote...
Hors ligne
#45 Le 07/04/2017, à 23:29
- fazpedro
Re : [Résolu] Pas de boot ASPIRE ES1 331
J'ai rebooté mais c'est toujours pareil...
pas de boot correct via le menu refind..
donc toujours en démarrage via la touche F12..
je ne comprends pas
Hors ligne
#46 Le 07/04/2017, à 23:37
- Bougron
Re : [Résolu] Pas de boot ASPIRE ES1 331
Aspire-ES1-332:~$ sudo mv /boot/efi/EFI/linux /boot/efi/EFI/linux.old Aspire-ES1-332:~$ sudo mkdir /boot/efi/EFI/linux Aspire-ES1-332:~$ sudo mvrefind /boot/efi/EFI/refind /boot/efi/EFI/linux ALERT: There were problems running the efibootmgr program! Your moved rEFInd might not run! Aspire-ES1-332:~$ sudo mv /boot/efi/EFI/linux/refind_x64.efi /boot/efi/EFI/linux/BOOTX64.efi
Je reboote...
En fait, il semble y avoir un problème dans la commande car en théorie
u16041@u16041:~$ sudo mkdir /boot/efi/EFI/linux
[sudo] Mot de passe de u16041 :
u16041@u16041:~$ sudo mvrefind /boot/efi/EFI/refind /boot/efi/EFI/linux
u16041@u16041:~$
Peux-tu faire un rapport bisnext Mais je ne regarderais qu'en milieu semaine prochaine
Dernière modification par Bougron (Le 07/04/2017, à 23:38)
Hors ligne
#47 Le 07/04/2017, à 23:47
- fazpedro
Re : [Résolu] Pas de boot ASPIRE ES1 331
Voici le rapport :
bisnext report id 6bc6d also available at http://paste.openstack.org/show/605790
bisnext 0.01
============================= Boot Info Summary: ===============================
mmcblk0: _______________________________________________________________________
File system:
Boot sector type: -
Boot sector info:
Mounting failed: mount: unknown filesystem type ''
============================ Drive/Partition Info: =============================
no valid partition table found
"blkid" output: ________________________________________________________________
Device UUID TYPE LABEL
/dev/mmcblk0
/dev/mmcblk0p1 EC40-9E26 vfat
/dev/mmcblk0p2 40b4639a-1132-4f38-b82b-04aeeddbd878 ext4
/dev/mmcblk0p3 9882a717-f77c-40ec-8168-436693d84acb swap
========================= "ls -l /dev/disk/by-id" output: ======================
total 0
lrwxrwxrwx 1 root root 13 avril 7 23:41 mmc-BJNB4R_0x3d4f4dd2 -> ../../mmcblk0
lrwxrwxrwx 1 root root 15 avril 7 23:41 mmc-BJNB4R_0x3d4f4dd2-part1 -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 15 avril 7 23:41 mmc-BJNB4R_0x3d4f4dd2-part2 -> ../../mmcblk0p2
lrwxrwxrwx 1 root root 15 avril 7 23:41 mmc-BJNB4R_0x3d4f4dd2-part3 -> ../../mmcblk0p3
================================ Mount points: =================================
Device Mount_Point Type Options
/dev/mmcblk0p2 / ext4 (rw,relatime,errors=remount-ro,data=ordered)
/dev/mmcblk0p1 /boot/efi vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
=============================== Free disk space: ===============================
Filesystem Mounted on Type Size Used Avail Use% IUse%
/dev/mmcblk0p1 /boot/efi vfat 511M 5.1M 506M 1% -
/dev/mmcblk0p2 / ext4 25G 5.2G 18G 23% 15%
==================================== inxi report: ==============================
System: Kernel: 4.8.0-46-generic x86_64 (64 bit gcc: 5.4.0)
Desktop: Xfce 4.12.3 (Gtk 2.24.28) dm: lightdm
Distro: Ubuntu 16.04.2 LTS
Machine: Device: laptop System: Acer product: Aspire ES1-332 v: V1.08
Mobo: Acer model: Ankylo_AP v: V1.08
UEFI: Insyde v: V1.08 date: 10/21/2016
Chassis: type: 10
Battery BAT1: charge: 9.6 Wh 29.4% condition: 32.7/32.7 Wh (100%)
volts: 11.1/11.4
model: SANYO AC14B13J status: Discharging
CPU: Dual core Intel Celeron N3350 (-MCP-) cache: 1024 KB bmips: 4377
clock speeds: min/max: 800/2400 MHz 1: 1102 MHz 2: 1098 MHz
CPU Flags: 3dnowprefetch acpi aes aperfmperf apic arat arch_perfmon
art bts clflush clflushopt cmov constant_tsc cx16 cx8 de ds_cpl
dtes64 dtherm dts eagerfpu ept erms est flexpriority fpu fsgsbase
fxsr ht ida intel_pt lahf_lm lm mca mce mmx monitor movbe mpx msr
mtrr nonstop_tsc nopl nx pae pat pbe pclmulqdq pdcm pdpe1gb pebs
pge pln pni popcnt pse pse36 pts rdrand rdseed rdtscp rep_good sdbg
sep sha_ni smap smep ss sse sse2 sse4_1 sse4_2 ssse3 syscall tm tm2
tpr_shadow tsc tsc_adjust tsc_deadline_timer vme vmx vnmi vpid
x2apic xgetbv1 xsave xsavec xsaveopt xsaves xtopology xtpr
Memory: Array-1 capacity: 16 GB devices: 2 EC: None
Device-1: ChannelA-DIMM0 size: 4 GB speed: 1600 MHz type: DDR3
manufacturer: 0420 part: AO1L16BC4R1-BQSS
Device-2: N/A size: N/A speed: N/A type: N/A
manufacturer: N/A part: N/A
Device-3: N/A size: N/A speed: N/A type: N/A
manufacturer: N/A part: N/A
Device-4: N/A size: N/A speed: N/A type: N/A
manufacturer: N/A part: N/A
Graphics: Card: Intel Device 5a85 bus-ID: 00:02.0 chip-ID: 8086:5a85
Display Server: X.Org 1.18.4 drivers: modesetting (unloaded: fbdev,vesa)
tty size: 1366x768@60.01hz
GLX Renderer: Mesa DRI Intel HD Graphics (Broxton 2x6)
GLX Version: 3.0 Mesa 12.0.6 Direct Rendering: Yes
Audio: Card Intel Device 5a98
driver: snd_hda_intel bus-ID: 00:0e.0 chip-ID: 8086:5a98
Sound: Advanced Linux Sound Architecture v: k4.8.0-46-generic
Network: Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
driver: r8169 v: 2.3LK-NAPI port: 1000
bus-ID: 02:00.0 chip-ID: 10ec:8168
IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Card-2: Intel Device 24fb
driver: iwlwifi bus-ID: 03:00.0 chip-ID: 8086:24fb
IF: wlp3s0 state: down mac: <filter>
Drives: HDD Total Size: NA (-)
ID-1: /dev/mmcblk0 model: N/A size: 31.3GB
Optical: No optical drives detected.
Partition: ID-1: / size: 25G used: 5.2G (23%) fs: ext4 dev: /dev/mmcblk0p2
label: N/A uuid: 40b4639a-1132-4f38-b82b-04aeeddbd878
ID-2: /boot/efi size: 511M used: 5.1M (1%) fs: vfat dev: /dev/mmcblk0p1
label: N/A uuid: EC40-9E26
ID-3: swap-1 size: 4.11GB used: 0.00GB (0%) fs: swap dev: /dev/mmcblk0p3
label: N/A uuid: 9882a717-f77c-40ec-8168-436693d84acb
RAID: System: supported: N/A
No RAID devices: /proc/mdstat, md_mod kernel module present
Unused Devices: none
Unmounted: ID-1: /dev/mmcblk0 size: 31.27G label: N/A uuid: N/A
ID-2: /dev/mmcblk0boot1 size: 0.00G label: N/A uuid: N/A
ID-3: /dev/mmcblk0boot0 size: 0.00G label: N/A uuid: N/A
Sensors: System Temperatures: cpu: 44.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Repos: Active apt sources in file: /etc/apt/sources.list
deb http://fr.archive.ubuntu.com/ubuntu/ xenial main restricted
deb http://fr.archive.ubuntu.com/ubuntu/ xenial-updates main restricted
deb http://fr.archive.ubuntu.com/ubuntu/ xenial universe
deb http://fr.archive.ubuntu.com/ubuntu/ xenial-updates universe
deb http://fr.archive.ubuntu.com/ubuntu/ xenial multiverse
deb http://fr.archive.ubuntu.com/ubuntu/ xenial-updates multiverse
deb http://fr.archive.ubuntu.com/ubuntu/ xenial-backports main restricted universe multiverse
deb http://security.ubuntu.com/ubuntu xenial-security main restricted
deb http://security.ubuntu.com/ubuntu xenial-security universe
deb http://security.ubuntu.com/ubuntu xenial-security multiverse
Active apt sources in file: /etc/apt/sources.list.d/rodsmith-ubuntu-refind-xenial.list
deb http://ppa.launchpad.net/rodsmith/refind/ubuntu xenial main
Processes: CPU: % used - Memory: MB / % used - top 10 active
1: cpu: 20.3% command: firefox pid: 1517 mem: 416.82MB (11.0%)
2: cpu: 4.5% command: Xorg pid: 902 mem: 67.07MB (1.7%)
3: cpu: 2.0% daemon: ~mmcqd/0~ pid: 167 mem: 0.00MB (0.0%)
4: cpu: 1.2% command: init pid: 1 mem: 5.77MB (0.1%)
5: cpu: 1.1% command: bash pid: 2961 mem: 4.39MB (0.1%)
6: cpu: 0.7% command: xfwm4 pid: 1251 mem: 22.60MB (0.5%)
7: cpu: 0.3% command: xfce4-terminal pid: 1605 mem: 24.80MB (0.6%)
8: cpu: 0.2% command: dbus-daemon pid: 703 mem: 4.66MB (0.1%)
9: cpu: 0.1% command: applet.py (started by: python3) pid: 1306 mem: 30.53MB (0.8%)
10: cpu: 0.1% command: nm-applet pid: 1298 mem: 36.45MB (0.9%)
Memory: MB / % used - CPU: % used - top 10 active
1: mem: 416.82MB (11.0%) command: firefox pid: 1517 cpu: 20.3%
2: mem: 67.07MB (1.7%) command: Xorg pid: 902 cpu: 4.5%
3: mem: 36.45MB (0.9%) command: nm-applet pid: 1298 cpu: 0.1%
4: mem: 31.69MB (0.8%) command: update-notifier pid: 1303 cpu: 0.0%
5: mem: 30.53MB (0.8%) command: xfdesktop pid: 1263 cpu: 0.1%
6: mem: 30.53MB (0.8%) command: applet.py (started by: python3) pid: 1306 cpu: 0.1%
7: mem: 24.80MB (0.6%) command: xfce4-terminal pid: 1605 cpu: 0.3%
8: mem: 24.46MB (0.6%) command: xfce4-panel pid: 1254 cpu: 0.1%
9: mem: 23.30MB (0.6%) command: libwhiskermenu.so (started by: wrapper-1.0) pid: 1282 cpu: 0.0%
10: mem: 23.10MB (0.6%) command: light-locker pid: 1302 cpu: 0.0%
Info: Processes: 185 Uptime: 3 min Memory: 678.7/3779.8MB
Init: systemd v: 229 runlevel: 5 default: 2 Gcc sys: 5.4.0
Client: Shell (bash 4.3.461 running in bash) inxi: 2.3.8
=================================== rfkill: ===================================
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: yes
2: acer-wireless: Wireless LAN
Soft blocked: yes
Hard blocked: no
3: acer-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
=================================== lsusb: ====================================
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 003: ID 0408:a010 Quanta Computer, Inc.
Bus 001 Device 002: ID 8087:0aa7 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/7p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
|__ Port 5: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
|__ Port 5: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 7: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M
|__ Port 7: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M
|__ Port 8: Dev 4, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 480M
=================================== cmdline: ==================================
BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=UUID=40b4639a-1132-4f38-b82b-04aeeddbd878 ro quiet splash vt.handoff=7
==================================== dmesg: ===================================
[ 0.000000] efi: EFI v2.50 by INSYDE Corp.
[ 0.000000] efi: ACPI 2.0=0x7affe014 ESRT=0x78566158 SMBIOS=0x78565000 SMBIOS 3.0=0x78563000 PROP=0x6723f258
[ 0.000000] ACPI: UEFI 0x000000007AFE8000 000042 (v01 ACRSYS ACRPRDCT 00000002 1025 00040000)
[ 0.000000] ACPI: UEFI 0x000000007AFFD000 000236 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
[ 0.269963] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 0.289986] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge
[ 0.300478] pci 0000:02:00.0: can't set Max Payload Size to 256; if necessary, use "pci=pcie_bus_safe" and report a bug
[ 0.310875] pci 0000:03:00.0: can't set Max Payload Size to 256; if necessary, use "pci=pcie_bus_safe" and report a bug
[ 0.401870] pci 0000:00:15.0: xHCI BIOS handoff failed (BIOS bug ?) 00012201
[ 2.043471] efifb: probing for efifb
[ 2.043506] efifb: framebuffer at 0x80000000, using 4160k, total 4160k
[ 2.043509] efifb: mode is 1366x768x32, linelength=5504, pages=1
[ 2.043510] efifb: scrolling: redraw
[ 2.043513] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[ 2.043822] fb0: EFI VGA frame buffer device
[ 2.180069] EFI Variables Facility v0.08 2004-May-17
[ 2.482105] fb: switching to inteldrmfb from EFI VGA
[ 2.498361] [drm] GuC firmware load skipped
[ 3.941588] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro
[ 4.404364] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-3168-24.ucode failed with error -2
[ 4.404401] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-3168-23.ucode failed with error -2
[ 4.419958] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.8.10-fw-22.50.19.14.f.bseq
[ 4.426132] iwlwifi 0000:03:00.0: loaded firmware version 22.361476.0 op_mode iwlmvm
[ 4.698089] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
============================= boot-up statistics: =============================
Startup finished in 10.267s (firmware) + 11.466s (loader) + 3.469s (kernel) + 10.617s (userspace) = 35.821s
blame, first 10:
NetworkManager-wait-online.service 7.105s
apparmor.service 1.379s
plymouth-read-write.service 1.270s
dev-mmcblk0p2.device 1.267s
plymouth-start.service 1.032s
lightdm.service 587ms
networking.service 576ms
ModemManager.service 515ms
systemd-rfkill.service 434ms
systemd-logind.service 387ms
critical-chain:
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
1 graphical.target @10.597s
2 multi-user.target @10.597s
3 hddtemp.service @10.554s +36ms
4 network-online.target @10.537s
5 NetworkManager-wait-online.service @3.431s +7.105s
6 NetworkManager.service @3.122s +293ms
7 dbus.service @3.070s
8 basic.target @3.021s
9 sockets.target @3.021s
10 snapd.socket @3.001s +18ms
11 sysinit.target @2.999s
12 apparmor.service @1.619s +1.379s
13 local-fs.target @1.615s
14 run-user-1000-gvfs.mount @9.141s
15 run-user-1000.mount @5.919s
16 local-fs-pre.target @415ms
17 systemd-remount-fs.service @406ms +7ms
18 systemd-journald.socket @193ms
19 -.slice @188ms
================================== locales: ===================================
locale command output:
LANG=fr_FR.UTF-8
LANGUAGE=fr_FR
LC_CTYPE="fr_FR.UTF-8"
LC_NUMERIC="fr_FR.UTF-8"
LC_TIME="fr_FR.UTF-8"
LC_COLLATE="fr_FR.UTF-8"
LC_MONETARY="fr_FR.UTF-8"
LC_MESSAGES="fr_FR.UTF-8"
LC_PAPER="fr_FR.UTF-8"
LC_NAME="fr_FR.UTF-8"
LC_ADDRESS="fr_FR.UTF-8"
LC_TELEPHONE="fr_FR.UTF-8"
LC_MEASUREMENT="fr_FR.UTF-8"
LC_IDENTIFICATION="fr_FR.UTF-8"
LC_ALL=
/etc/default/locale:
# File generated by update-locale
LANG="fr_FR.UTF-8"
Active keyboard layout:
rules: evdev
model: pc105
layout: fr
Default keyboard layout:
XKBMODEL="pc105"
XKBLAYOUT="fr"
XKBVARIANT="latin9"
XKBOPTIONS=""
BACKSPACE="guess"
====================================== Modules: ================================
Module Size Used by
ablk_helper 16384 1 aesni_intel
ac97_bus 16384 1 snd_soc_core
acer_wmi 20480 0
aesni_intel 167936 0
aes_x86_64 20480 1 aesni_intel
ahci 36864 0
arc4 16384 2
autofs4 40960 2
bluetooth 557056 26 btrtl,btintel,bnep,btbcm,btusb
bnep 20480 2
btbcm 16384 1 btusb
btintel 16384 1 btusb
btrtl 16384 1 btusb
btusb 45056 0
cfg80211 581632 3 iwlmvm,iwlwifi,mac80211
coretemp 16384 0
crc32_pclmul 16384 0
crct10dif_pclmul 16384 0
cryptd 24576 3 ablk_helper,ghash_clmulni_intel,aesni_intel
drm 368640 8 i915,drm_kms_helper
drm_kms_helper 167936 1 i915
fb_sys_fops 16384 1 drm_kms_helper
fjes 28672 0
ghash_clmulni_intel 16384 0
glue_helper 16384 1 aesni_intel
hid 122880 1 i2c_hid
i2c_algo_bit 16384 1 i915
i2c_designware_core 20480 1 i2c_designware_platform
i2c_designware_platform 16384 0
i2c_hid 20480 0
i915 1310720 7
idma64 20480 0
input_leds 16384 0
intel_lpss 16384 1 intel_lpss_pci
intel_lpss_pci 16384 0
intel_pmc_ipc 20480 1 intel_telemetry_pltdrv
intel_powerclamp 16384 0
intel_punit_ipc 16384 1 intel_telemetry_pltdrv
intel_rapl 20480 0
intel_telemetry_core 20480 1 intel_telemetry_pltdrv
intel_telemetry_pltdrv 20480 0
irqbypass 16384 1 kvm
iwlmvm 360448 0
iwlwifi 229376 1 iwlmvm
joydev 20480 0
kvm 598016 1 kvm_intel
kvm_intel 192512 0
libahci 32768 1 ahci
lp 20480 0
lrw 16384 1 aesni_intel
mac80211 761856 1 iwlmvm
mac_hid 16384 0
media 40960 2 uvcvideo,videodev
mei 102400 1 mei_me
mei_me 40960 0
memstick 20480 1 rtsx_usb_ms
mii 16384 1 r8169
mmc_block 40960 4
nls_iso8859_1 16384 1
parport 49152 3 lp,parport_pc,ppdev
parport_pc 32768 0
pinctrl_broxton 40960 0
pinctrl_intel 20480 1 pinctrl_broxton
ppdev 20480 0
psmouse 139264 0
r8169 81920 0
rtsx_usb 24576 2 rtsx_usb_sdmmc,rtsx_usb_ms
rtsx_usb_ms 20480 0
rtsx_usb_sdmmc 28672 0
sdhci 45056 1 sdhci_pci
sdhci_pci 28672 0
serio_raw 16384 0
shpchp 36864 0
snd 86016 19 snd_compress,snd_hda_intel,snd_hwdep,snd_seq,snd_hda_codec,snd_timer,snd_rawmidi,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_seq_device,snd_hda_codec_realtek,snd_soc_core,snd_pcm
snd_compress 20480 1 snd_soc_core
snd_hda_codec 135168 4 snd_hda_intel,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek
snd_hda_codec_generic 73728 1 snd_hda_codec_realtek
snd_hda_codec_hdmi 45056 1
snd_hda_codec_realtek 86016 1
snd_hda_core 86016 7 snd_hda_intel,snd_hda_codec,snd_hda_ext_core,snd_soc_skl,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek
snd_hda_ext_core 28672 1 snd_soc_skl
snd_hda_intel 36864 3
snd_hwdep 16384 1 snd_hda_codec
snd_pcm 110592 8 snd_hda_intel,snd_hda_codec,snd_pcm_dmaengine,snd_hda_ext_core,snd_hda_core,snd_soc_skl,snd_hda_codec_hdmi,snd_soc_core
snd_pcm_dmaengine 16384 1 snd_soc_core
snd_rawmidi 32768 1 snd_seq_midi
snd_seq 69632 2 snd_seq_midi_event,snd_seq_midi
snd_seq_device 16384 3 snd_seq,snd_rawmidi,snd_seq_midi
snd_seq_midi 16384 0
snd_seq_midi_event 16384 1 snd_seq_midi
snd_soc_core 233472 1 snd_soc_skl
snd_soc_skl 65536 0
snd_soc_skl_ipc 45056 1 snd_soc_skl
snd_soc_sst_dsp 32768 1 snd_soc_skl_ipc
snd_soc_sst_ipc 16384 1 snd_soc_skl_ipc
snd_soc_sst_match 16384 1 snd_soc_skl
snd_timer 32768 2 snd_seq,snd_pcm
soundcore 16384 1 snd
sparse_keymap 16384 1 acer_wmi
syscopyarea 16384 1 drm_kms_helper
sysfillrect 16384 1 drm_kms_helper
sysimgblt 16384 1 drm_kms_helper
tpm_crb 16384 0
uvcvideo 90112 0
video 40960 2 acer_wmi,i915
videobuf2_core 40960 2 uvcvideo,videobuf2_v4l2
videobuf2_memops 16384 1 videobuf2_vmalloc
videobuf2_v4l2 24576 1 uvcvideo
videobuf2_vmalloc 16384 1 uvcvideo
videodev 180224 3 uvcvideo,videobuf2_core,videobuf2_v4l2
virt_dma 16384 1 idma64
wmi 16384 1 acer_wmi
x86_pkg_temp_thermal 16384 0
==================================== xorg: ===================================
xinput:
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=12 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Power Button id=8 [slave keyboard (3)]
↳ Sleep Button id=9 [slave keyboard (3)]
↳ VGA Webcam id=10 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=11 [slave keyboard (3)]
↳ Acer WMI hotkeys id=13 [slave keyboard (3)]
xrandr:
Screen 0: minimum 320 x 200, current 1366 x 768, maximum 8192 x 8192
eDP-1 connected 1366x768+0+0 (normal left inverted right x axis y axis) 293mm x 164mm
1366x768 60.01*+
1360x768 59.80 59.96
1024x768 60.04 60.00
960x720 60.00
928x696 60.05
896x672 60.01
960x600 60.00
960x540 59.99
800x600 60.00 60.32 56.25
840x525 60.01 59.88
800x512 60.17
700x525 59.98
640x512 60.02
720x450 59.89
640x480 60.00 59.94
680x384 59.80 59.96
576x432 60.06
512x384 60.00
400x300 60.32 56.34
320x240 60.05
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
HDMI-2 disconnected (normal left inverted right x axis y axis)
============================== Additional drivers: =============================
== cpu-microcode.py ==
driver : intel-microcode - distro non-free
============================= Upgradable packages: =============================
None
================================ Broken packages: ==============================
aptitude program not available on this system.
======================== Package configuration pending: ========================
None
========================== Package install interrupted: ========================
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
========================= kernel packages installed: ==========================
Package Version
linux-generic 4.4.0.72.78
linux-generic-hwe-16.04 4.8.0.46.18
linux-headers-4.4.0-72 4.4.0-72.93
linux-headers-4.4.0-72-generic 4.4.0-72.93
linux-headers-4.8.0-36 4.8.0-36.36~16.04.1
linux-headers-4.8.0-36-generic 4.8.0-36.36~16.04.1
linux-headers-4.8.0-46 4.8.0-46.49~16.04.1
linux-headers-4.8.0-46-generic 4.8.0-46.49~16.04.1
linux-headers-generic 4.4.0.72.78
linux-headers-generic-hwe-16.04 4.8.0.46.18
linux-image-4.4.0-72-generic 4.4.0-72.93
linux-image-4.8.0-36-generic 4.8.0-36.36~16.04.1
linux-image-4.8.0-46-generic 4.8.0-46.49~16.04.1
linux-image-extra-4.4.0-72-generic 4.4.0-72.93
linux-image-extra-4.8.0-36-generic 4.8.0-36.36~16.04.1
linux-image-extra-4.8.0-46-generic 4.8.0-46.49~16.04.1
linux-image-generic 4.4.0.72.78
linux-image-generic-hwe-16.04 4.8.0.46.18
========================= UEFI Boot Manager settings: ==========================
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0001,0000,2001,2002,2003
Boot0000* Linux HD(1,GPT,3f7264e6-734a-4f82-bc2a-daaa0a94d631,0x800,0x100000)/File(\EFI\Linux\BOOTX64.efi)RC
Boot0001* Windows Boot Manager HD(1,GPT,3f7264e6-734a-4f82-bc2a-daaa0a94d631,0x800,0x100000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)RC
Boot0002* Unknown Device: HD(1,GPT,3f7264e6-734a-4f82-bc2a-daaa0a94d631,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)RC
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RC
================================== Secure Boot: ================================
Secure Boot disabled or not supported on this system.
============================= md5sum of EFI files: =============================
EFI files in /dev/mmcblk0p1:
d73bbea8b6c047d2a706472f87d3ccdb /EFI/ubuntu/fwupx64.efi
20041fb0390b3f10e19c3596fd2f17e9 /EFI/ubuntu/grubx64.efi
3aef9c72ad50faa8db576c01f85a0915 /EFI/ubuntu/shimx64.efi
bf39cf9416a9403d40a9b69541486e74 /EFI/ubuntu/mmx64.efi
61c7898dd613614b15cee0081226572c /EFI/ubuntu/fbx64.efi
20041fb0390b3f10e19c3596fd2f17e9 /EFI/linux/BOOTX64.efi
b13aa2d7cd24d99c0d7158fffcc3b64b /EFI/linux/drivers_x64/ext4_x64.efi
20041fb0390b3f10e19c3596fd2f17e9 /EFI/Boot/bootx64.efi
20041fb0390b3f10e19c3596fd2f17e9 /EFI/Boot/Grubx64.efi
88e9318e530adb68963d35c8b328299c /EFI/Microsoft/Boot/bootmgfw.efi
20041fb0390b3f10e19c3596fd2f17e9 /EFI/Microsoft/Boot/bootx64.efi
20041fb0390b3f10e19c3596fd2f17e9 /EFI/Microsoft/Boot/Grubx64.efi
20041fb0390b3f10e19c3596fd2f17e9 /EFI/linux.old/BOOTX64.efi
b13aa2d7cd24d99c0d7158fffcc3b64b /EFI/linux.old/linux/drivers_x64/ext4_x64.efi
88e9318e530adb68963d35c8b328299c /EFI/linux.old/linux/BOOTX64.efi
============================ Disks SMART attributes: ===========================
### MMC disks: mmcblk0
# Drive mmcblk0:
smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.8.0-46-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
/dev/mmcblk0: Unable to detect device type
Please specify device type with the -d option.
Use smartctl -h to get a usage summary
Hors ligne
#48 Le 07/04/2017, à 23:52
- Bougron
Re : [Résolu] Pas de boot ASPIRE ES1 331
Je crois que tu as un problème avec ton wifi
1: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: yes
2: acer-wireless: Wireless LAN
Soft blocked: yes
On va supprimer la ligne de boot de windows
sudo efibootmgr -B -b 1
Puis la recréer
sudo efibootmgr --create --disk /dev/mmcblk0 --Part 1 --label "Windows Boot Manager" --loader "\EFI\linux\BOOTX64.efi"
On va aussi supprimer la ligne unknown
sudo efibootmgr -B -b 2
et je regarde tout cela : EFI files in /dev/mmcblk0p1:
d73bbea8b6c047d2a706472f87d3ccdb /EFI/ubuntu/fwupx64.efi
20041fb0390b3f10e19c3596fd2f17e9 /EFI/ubuntu/grubx64.efi
3aef9c72ad50faa8db576c01f85a0915 /EFI/ubuntu/shimx64.efi
bf39cf9416a9403d40a9b69541486e74 /EFI/ubuntu/mmx64.efi
61c7898dd613614b15cee0081226572c /EFI/ubuntu/fbx64.efi
20041fb0390b3f10e19c3596fd2f17e9 /EFI/linux/BOOTX64.efi
b13aa2d7cd24d99c0d7158fffcc3b64b /EFI/linux/drivers_x64/ext4_x64.efi
20041fb0390b3f10e19c3596fd2f17e9 /EFI/Boot/bootx64.efi
20041fb0390b3f10e19c3596fd2f17e9 /EFI/Boot/Grubx64.efi
88e9318e530adb68963d35c8b328299c /EFI/Microsoft/Boot/bootmgfw.efi
20041fb0390b3f10e19c3596fd2f17e9 /EFI/Microsoft/Boot/bootx64.efi
20041fb0390b3f10e19c3596fd2f17e9 /EFI/Microsoft/Boot/Grubx64.efi
20041fb0390b3f10e19c3596fd2f17e9 /EFI/linux.old/BOOTX64.efi
b13aa2d7cd24d99c0d7158fffcc3b64b /EFI/linux.old/linux/drivers_x64/ext4_x64.efi
88e9318e530adb68963d35c8b328299c /EFI/linux.old/linux/BOOTX64.efi
Tu mettras aussi à jour le fichier de démarrage officiel de windows
sudo cp /boot/efi/EFI/linux/BOOTX64.efi /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi
et tu supprimeras la copie de sécurité qui semble maintenant inutile
sudo rm -Rvs /boot/efi/linux.old
Puis tu supprimer aussi quelques versions devenues inutiles
sudo apt autoremove --purge
Dernière modification par Bougron (Le 08/04/2017, à 18:40)
Hors ligne
#49 Le 08/04/2017, à 11:33
- fazpedro
Re : [Résolu] Pas de boot ASPIRE ES1 331
-Aspire-ES1-332:~$ sudo efibootmgr -B -b 1
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0000,2001,2002,2003
Boot0000* Linux
Boot0002* Unknown Device:
Boot2001* EFI USB Device
Boot2002* EFI DVD/CDROM
Boot2003* EFI Network
-Aspire-ES1-332:~$ sudo efibootmgr --create --disk /dev/mmcblk0 --p 1 --label "Windows Boot Manager" --loader "\\EFI\linux\BOOTX64.efi"
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0001,0000,2001,2002,2003
Boot0000* Linux
Boot0002* Unknown Device:
Boot2001* EFI USB Device
Boot2002* EFI DVD/CDROM
Boot2003* EFI Network
Boot0001* Windows Boot Manager
-Aspire-ES1-332:~$ sudo efibootmgr -B -b 2
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0001,0000,2001,2002,2003
Boot0000* Linux
Boot0001* Windows Boot Manager
Boot2001* EFI USB Device
Boot2002* EFI DVD/CDROM
Boot2003* EFI Network
-Aspire-ES1-332:~$ sudo cp /boot/efi/EFI/linux/BOOTX64.efi /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi
-Aspire-ES1-332:~$ sudo rm -R /boot/efi/EFI/linux.old
-Aspire-ES1-332:~$ sudo apt autoremove --purge
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
-Aspire-ES1-332:~$
après reboot :
plus de menu Refind,
il reste bloqué sur le logo ACER...
donc redémarrage et toujours la touche F12 pour accéder au menu UBUNTU...
mince alors
Dernière modification par fazpedro (Le 08/04/2017, à 11:38)
Hors ligne
#50 Le 08/04/2017, à 18:45
- Bougron
Re : [Résolu] Pas de boot ASPIRE ES1 331
Bonjour.
J'ai commis une erreur de frappe dans la ligne créant le bootloader windows.
Si tu peux le ressupprimer et le recréer.
c'est certainement encore le numero 1.
Hors ligne