#1 Le 14/05/2020, à 19:34
- Nico_ldl
[Résolu] Dual boot Legacy/UEFI - problème de connection
Bonjour,
J'ai installé Ubuntu 20.04 en dual boot de Windows 10 sur mon ordinateur (UEFI). cependant lors de l'installation, j'ai rencontré de nombreuses difficultés : l'installation plantait sans raison -> j'ai inséré l'option 'acpi=off' et surtout, en fin d'installation j'avais l'erreur : "grub-install/dev/sda failed". J'ai essayé plusieurs techniques, notamment au niveau des partitions du disque en laissant un espace pour les fichiers Ext4, Swap et Bios mais rien à faire.
Le secure boot était bien désactivé.
La seule solution que j'ai trouvé est d'installer Ubuntu en ayant en boot mode LEGACY, et non pas UEFI comme Windows. Pour passer d'un OS à l'autre, je suis obligé de changer le boot mode LEGACY(linux) / UEFI(windows).
Avec cela, l'installation a bien marché et je peux utiliser Linux, ce qui beaucoup mieux pour coder .. mais j'imagine qu'il doit y avoir des problèmes. J'ai actuellement surtout des problèmes de réseau, je n'arrive pas à me connecter à certains sites et j'ai d'autres problèmes de réseau qui rendent l'utilisation d'Ubuntu impossible .. Je suis actuellement en partage de connexion filaire. Je n'ai aucun problème sur Windows. Je peux aussi ajouter que quand je fais un speedtest, j'ai un upload de 0 ..
Dans l'idéal, j'aimerais gardé la configuration actuelle et résoudre ces problèmes de réseau, j'ai déjà pas mal parcouru les forums, sans succès .. et je n'arrive pas à identifier le problème.
Voici mon boot-info actuel :
boot-info-4ppa118 [20200514_1905]
============================== Boot Info Summary ===============================
=> Grub2 (v2.00) is installed in the MBR of /dev/sda and looks at sector
1003708416 of the same hard drive for core.img. core.img is at this
location and looks for (,gpt8)/boot/grub. It also embeds following
components:
```
modules
---------------------------------------------------------------------------
fshelp ext2 part_gpt biosdisk
---------------------------------------------------------------------------
```
sda1: __________________________________________________________________________
```
File system: vfat
Boot sector type: Windows 8/2012: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /efi/Boot/bootx64.efi /efi/Boot/fbx64.efi
/efi/Boot/mmx64.efi /efi/ubuntu/grubx64.efi
/efi/ubuntu/mmx64.efi /efi/ubuntu/shimx64.efi
/efi/ubuntu/grub.cfg /efi/Microsoft/Boot/bootmgfw.efi
/efi/Microsoft/Boot/bootmgr.efi
/efi/Microsoft/Boot/memtest.efi
/efi/MSI/Boot/bootmgfw.efi /efi/MSI/Boot/bootmgr.efi
/efi/MSI/Boot/memtest.efi
```
sda2: __________________________________________________________________________
```
File system: ntfs
Boot sector type: Windows 8/2012: NTFS
Boot sector info: According to the info in the boot sector, sda2 starts
at sector 0. But according to the info from fdisk,
sda2 starts at sector 25251840.
Operating System: Windows 10
Boot files: /bootmgr /Windows/System32/winload.exe
```
sda3: __________________________________________________________________________
```
File system: ntfs
Boot sector type: Windows 8/2012: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
```
sda4: __________________________________________________________________________
```
File system: ntfs
Boot sector type: Windows 8/2012: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
```
sda5: __________________________________________________________________________
```
File system: ntfs
Boot sector type: Windows 8/2012: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
```
sda6: __________________________________________________________________________
```
File system: swap
Boot sector type: -
Boot sector info:
```
sda7: __________________________________________________________________________
```
File system: BIOS Boot partition
Boot sector type: Grub2's core.img
Boot sector info:
```
sda8: __________________________________________________________________________
```
File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 20.04 LTS
Boot files: /boot/grub/grub.cfg /etc/fstab /etc/default/grub
/boot/grub/i386-pc/core.img
```
================================ 2 OS detected =================================
OS#1: L'OS actuellement utilisé - Ubuntu 20.04 LTS CurrentSession on sda8
OS#2: Windows 10 on sda2
============================ Architecture/Host Info ============================
CPU architecture: 64-bit
BOOT_IMAGE of the installed session in use:
/boot/vmlinuz-5.4.0-29-generic root=UUID=77e27e09-1232-4c22-b8ae-53ffdca1b6ff ro quiet splash vt.handoff=7
===================================== UEFI =====================================
BIOS is EFI-compatible, but it is not setup in EFI-mode for this installed-session.
EFI in dmesg.
[ 0.011194] ACPI: UEFI 0x000000007C342D00 000042 (v01 MSI_NB MEGABOOK 00000002 01000013)
f7a57b08bc7c1c85417ae4cea582d1d4 sda1/Boot/bootx64.efi
bed45d1c9554cea09924d3814cb7c446 sda1/Boot/fbx64.efi
4487628005555bfd4a4c0a47211e0700 sda1/Boot/mmx64.efi
98bea152fadd26c4e9136916f6cc32a8 sda1/ubuntu/grubx64.efi
4487628005555bfd4a4c0a47211e0700 sda1/ubuntu/mmx64.efi
f7a57b08bc7c1c85417ae4cea582d1d4 sda1/ubuntu/shimx64.efi
cb8e4284804d56f058c0e1cf111eeedd sda1/Microsoft/Boot/bootmgfw.efi
3df357ffd0654bb80f2a575485e6e0cc sda1/Microsoft/Boot/bootmgr.efi
18a3724224b0f82a36941982259339b6 sda1/MSI/Boot/bootmgfw.efi
4e3a2ee37111132b1bb95323dfc123d2 sda1/MSI/Boot/bootmgr.efi
============================= Drive/Partition Info =============================
Disks info: ____________________________________________________________________
sda : is-GPT, hasBIOSboot, has---ESP, not-usb, not-mmc, has-os, 2048 sectors * 512 bytes
Partitions info (1/3): _________________________________________________________
sda8 : is-os, 64, apt-get, grub-pc , grub2, grub-install, grubenv-ng, update-grub, farbios
sda1 : no-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, not-far
sda2 : is-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, farbios
sda3 : no-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, farbios
sda4 : no-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, farbios
sda5 : no-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, farbios
Partitions info (2/3): _________________________________________________________
sda8 : isnotESP, fstab-without-efi, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
sda1 : is---ESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
sda2 : isnotESP, part-has-no-fstab, no-nt, haswinload, no-recov-nor-hid, bootmgr, notwinboot
sda3 : isnotESP, part-has-no-fstab, no-nt, no-winload, recovery-or-hidden, no-bmgr, notwinboot
sda4 : isnotESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
sda5 : isnotESP, part-has-no-fstab, no-nt, no-winload, recovery-or-hidden, no-bmgr, notwinboot
Partitions info (3/3): _________________________________________________________
sda8 : not-sepboot, with-boot, fstab-without-boot, not-sep-usr, with--usr, fstab-without-usr, std-grub.d, sda
sda1 : not-sepboot, no-boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, std-grub.d, sda
sda2 : not-sepboot, no-boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, std-grub.d, sda
sda3 : not-sepboot, no-boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, std-grub.d, sda
sda4 : not-sepboot, no-boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, std-grub.d, sda
sda5 : not-sepboot, no-boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, std-grub.d, sda
fdisk -l (filtered): ___________________________________________________________
Disk sda: 931.53 GiB, 1000204886016 bytes, 1953525168 sectors
Disk identifier: B9197F3D-7E30-47C7-933F-B52C02D17A7A
Start End Sectors Size Type
sda1 2048 616447 614400 300M EFI System
sda2 25251840 991709183 966457344 460.9G Microsoft basic data
sda3 1172989952 1174833151 1843200 900M Windows recovery environment
sda4 1174833152 1799813119 624979968 298G Microsoft basic data
sda5 1918412800 1953523711 35110912 16.8G Windows recovery environment
sda6 991709184 1003708415 11999232 5.7G Linux swap
sda7 1003708416 1016739839 13031424 6.2G BIOS boot
sda8 1016739840 1172989951 156250112 74.5G Linux filesystem
Partition table entries are not in disk order.
parted -lm (filtered): _________________________________________________________
sda:1000GB:scsi:512:4096:gpt:ATA ST1000LM048-2E71:;
1:1049kB:316MB:315MB:fat32:EF:boot, esp;
2:12.9GB:508GB:495GB:ntfs::msftdata;
6:508GB:514GB:6144MB:linux-swap(v1)::swap;
7:514GB:521GB:6672MB:::bios_grub;
8:521GB:601GB:80.0GB:ext4::;
3:601GB:602GB:944MB:ntfs:Ba:hidden, diag;
4:602GB:922GB:320GB:ntfs:Ba:msftdata;
5:982GB:1000GB:18.0GB:ntfs:Ba:hidden, diag;
blkid (filtered): ______________________________________________________________
NAME FSTYPE UUID PARTUUID LABEL PARTLABEL
sda
├─sda1 vfat 4C3B-5289 5b59b24d-d508-4e29-9da5-75576ceed718 SYSTEM EF
├─sda2 ntfs 01D6209CB807E340 822c531f-704d-468f-862f-b9f59f5f9dea Windows
├─sda3 ntfs D8523D49523D2D9E 6a1c09e4-331c-40b8-8438-782993c729d0 WinRE tools Ba
├─sda4 ntfs 3862409D624061AC ea0bb657-ce93-439a-86d2-ade27ed8eb6b Data Ba
├─sda5 ntfs C0BA41E8BA41DC12 d4acf54b-4fb6-41b5-8f74-fc0284273ce8 BIOS_RVY Ba
├─sda6 swap 4fdf0921-badd-4220-829b-5df29772124d 820731c1-ea7f-44e9-a5a0-5e49d474471f
├─sda7 8bd32868-e34e-4df3-afba-bfa183ce18ff
└─sda8 ext4 77e27e09-1232-4c22-b8ae-53ffdca1b6ff 2dc51abb-9c46-4c05-ab74-de3daa9725e9
df (filtered): _________________________________________________________________
```
Avail Use% Mounted on
```
sda1 238.8M 19% /mnt/boot-sav/sda1
sda2 201.6G 56% /mnt/boot-sav/sda2
sda3 401.1M 55% /mnt/boot-sav/sda3
sda4 283.7G 5% /mnt/boot-sav/sda4
sda5 1.2G 93% /mnt/boot-sav/sda5
sda8 56.1G 18% /
Mount options: __________________________________________________________________
sda1 rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
sda2 rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
sda3 rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
sda4 rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
sda5 rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
sda8 rw,relatime,errors=remount-ro
===================== sda1/efi/ubuntu/grub.cfg (filtered) ======================
search.fs_uuid f489a195-d466-4372-8bf3-26ddd1b6083a root hd0,gpt9
set prefix=($root)'/boot/grub'
configfile $prefix/grub.cfg
====================== sda8/boot/grub/grub.cfg (filtered) ======================
Ubuntu 77e27e09-1232-4c22-b8ae-53ffdca1b6ff
Ubuntu, avec Linux 5.4.0-29-generic 77e27e09-1232-4c22-b8ae-53ffdca1b6ff
Ubuntu, avec Linux 5.4.0-26-generic 77e27e09-1232-4c22-b8ae-53ffdca1b6ff
### END /etc/grub.d/30_os-prober
### END /etc/grub.d/30_uefi-firmware
========================== sda8/etc/fstab (filtered) ===========================
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda8 during installation
UUID=77e27e09-1232-4c22-b8ae-53ffdca1b6ff / ext4 errors=remount-ro 0 1
# swap was on /dev/sda6 during installation
UUID=4fdf0921-badd-4220-829b-5df29772124d none swap sw 0 0
======================= sda8/etc/default/grub (filtered) =======================
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=0
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=off"
GRUB_CMDLINE_LINUX=""
==================== sda8: Location of files loaded by Grub ====================
```
GiB - GB File Fragment(s)
```
550,999511719 = 591,631220736 boot/grub/grub.cfg 2
540,953350067 = 580,844236800 boot/grub/i386-pc/core.img 1
550,306755066 = 590,887378944 boot/vmlinuz 1
486,283317566 = 522,142736384 boot/vmlinuz-5.4.0-26-generic 1
550,306755066 = 590,887378944 boot/vmlinuz-5.4.0-29-generic 1
486,283317566 = 522,142736384 boot/vmlinuz.old 1
550,701316833 = 591,311036416 boot/initrd.img 2
549,493999481 = 590,014689280 boot/initrd.img-5.4.0-26-generic 5
550,701316833 = 591,311036416 boot/initrd.img-5.4.0-29-generic 2
549,493999481 = 590,014689280 boot/initrd.img.old 5
===================== sda8: ls -l /etc/grub.d/ (filtered) ======================
-rwxr-xr-x 1 root root 17123 avril 15 13:31 10_linux
-rwxr-xr-x 1 root root 42128 avril 15 13:31 10_linux_zfs
-rwxr-xr-x 1 root root 12894 avril 15 13:31 20_linux_xen
-rwxr-xr-x 1 root root 12059 avril 15 13:31 30_os-prober
-rwxr-xr-x 1 root root 1424 avril 15 13:31 30_uefi-firmware
-rwxr-xr-x 1 root root 214 avril 15 13:31 40_custom
-rwxr-xr-x 1 root root 216 avril 15 13:31 41_custom
Suggested repair: ______________________________________________________________
The default repair of the Boot-Repair utility would purge (in order to fix packages) and reinstall the grub-efi-amd64-signed of
sda8,
using the following options: sda1/boot/efi,
Additional repair would be performed: unhide-bootmenu-10s win-legacy-basic-fix use-standard-efi-file
Blockers in case of suggested repair: __________________________________________
WindowsEFI detected. Please disable BIOS-compatibility/CSM/Legacy mode in your UEFI firmware, and use this software from a live-CD (or live-USB) that is compatible with UEFI booting mode. For example, use a live-USB of Boot-Repair-Disk-64bit ([www.sourceforge.net/p/boot-repair-cd](http://www.sourceforge.net/p/boot-repair-cd)), after making sure your BIOS is set up to boot USB in EFI mode.
Final advice in case of suggested repair: ______________________________________
Please do not forget to make your UEFI firmware boot on sda1/efi/**/shim**.efi (**** will be updated in the final message) file!
If your computer reboots directly into Windows, try to change the boot order in your UEFI firmware.
If your UEFI firmware does not allow to change the boot order, change the default boot entry of the Windows bootloader.
For example you can boot into Windows, then type the following command in an admin command prompt:
bcdedit /set {bootmgr} path \EFI\**\shim**.efi (**** will be updated in the final message)
The boot of your PC is in BIOS-compatibility/CSM/Legacy mode. You may want to retry after changing it to UEFI mode.Voici mes info réseau :
➜ ~ ifconfig
br-1a4660b737c1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.19.0.1 netmask 255.255.0.0 broadcast 172.19.255.255
ether 02:42:58:65:d1:d5 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
br-1f27191b5567: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.21.0.1 netmask 255.255.0.0 broadcast 172.21.255.255
ether 02:42:3a:86:96:2e txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
br-6e9e4879c49f: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.18.0.1 netmask 255.255.0.0 broadcast 172.18.255.255
ether 02:42:cc:90:5b:c7 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
br-d06574b23cf2: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.22.0.1 netmask 255.255.0.0 broadcast 172.22.255.255
ether 02:42:04:40:ce:54 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
ether 02:42:91:a2:31:bf txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
enp3s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 4c:cc:6a:e1:2e:db txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 17
enp3s0:avahi: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 169.254.10.67 netmask 255.255.0.0 broadcast 169.254.255.255
ether 4c:cc:6a:e1:2e:db txqueuelen 1000 (Ethernet)
device interrupt 17
enxde415fe1006f: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.20.10.4 netmask 255.255.255.240 broadcast 172.20.10.15
inet6 fe80::8ecb:562a:57bf:8832 prefixlen 64 scopeid 0x20<link>
ether de:41:5f:e1:00:6f txqueuelen 1000 (Ethernet)
RX packets 15823 bytes 11533851 (11.5 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 21648 bytes 6519581 (6.5 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Boucle locale)
RX packets 5831 bytes 869931 (869.9 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 5831 bytes 869931 (869.9 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
teredo: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1280
inet6 fe80::d238:418b:5000:67a3 prefixlen 64 scopeid 0x20<link>
inet6 2001:0:53aa:64c:2c0b:76fc:b232:baff prefixlen 32 scopeid 0x0<global>
inet6 fe80::ffff:ffff:ffff prefixlen 64 scopeid 0x20<link>
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 500 (UNSPEC)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 10 bytes 480 (480.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.20.10.2 netmask 255.255.255.240 broadcast 172.20.10.15
inet6 fe80::b85e:efab:60f8:8e3e prefixlen 64 scopeid 0x20<link>
ether a0:af:bd:55:a6:c7 txqueuelen 1000 (Ethernet)
RX packets 28302 bytes 19612654 (19.6 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 19120 bytes 7179098 (7.1 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0➜ ~ lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 02)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1)
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1)
00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point LPC Controller/eSPI Controller (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
01:00.0 3D controller: NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] (rev a1)
02:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] (rev 10)
03:00.0 Ethernet controller: Qualcomm Atheros QCA8171 Gigabit Ethernet (rev 10)En espérant avoir fourni les informations nécessaires,
Merci d'avance et bonne journée
Dernière modification par Nico_ldl (Le 15/05/2020, à 09:15)
Hors ligne
#2 Le 15/05/2020, à 09:24
- Nico_ldl
Re : [Résolu] Dual boot Legacy/UEFI - problème de connection
Bonjour,
Désolé si quelqu'un a commencé les recherches à ce sujet, concernant mon problème il a pas mal évolué. J'ai essayé de switcher Ubuntu de boot mode Legacy à UEFI en suivant la méthode 1 de ce tutoriel https://askubuntu.com/questions/913397/ … cy-to-uefi (repartir sur la clé bootable en mode UEFI, lancer le boot-repair et espérer que ça marche).
Résultat, ça ne fonctionne toujours pas, que ce soit en boot mode UEFI ou en Legacy. J'arrive dans les deux cas sur un terminal noir Grub. Je peux toujours accéder à Windows en changeant l'ordre des OS au niveau du BIOS, en étant dans le boot mode UEFI.
J'envisage donc d'abandonner cette idée de dual boot pour l'instant (j'y ai passé une semaine :'( ). Je réessayerai quand j'en aurai de nouveau marre de windows.
Bonne journée
Hors ligne
#3 Le 16/05/2020, à 00:41
- Bigjim97115
Re : [Résolu] Dual boot Legacy/UEFI - problème de connection
Bonjour Nico_ldl
Ton expérience m'intéresse, car j'ai posté un soucis pour l'install d'ubuntu (ici: https://forum.ubuntu-fr.org/viewtopic.php?id=2052922) et je voulais savoir si tu étais passé par des changements dans le registre ou par les commandes indiquées ici : https://doc.ubuntu-fr.org/cohabitation_ubuntu_windows
Cordialement.
Hors ligne
#4 Le 17/05/2020, à 22:47
- Nico_ldl
Re : [Résolu] Dual boot Legacy/UEFI - problème de connection
Hello Bigjim97115,
J'ai lu ton poste mais je ne vais pas vraiment pouvoir t'aider. J'ai un problème assez différent du tiens. J'ai le problème 7.2 du lien que tu as partagé: https://doc.ubuntu-fr.org/cohabitation_ubuntu_windows
A l'heure actuelle je n'ai pas de solution pour mon problème.
Bon courage pour ton installation et bonne soirée !
Hors ligne