[prev in list] [next in list] [prev in thread] [next in thread] 

List:       grub-help
Subject:    Re: chainload windows10 after using nativedisk
From:       Pascal Hambourg <pascal () plouf ! fr ! eu ! org>
Date:       2018-11-23 20:32:56
Message-ID: 260f471d-6a9f-0e6e-eebb-49b6b692de11 () plouf ! fr ! eu ! org
[Download RAW message or body]

Le 23/11/2018 à 15:12, Fi ps a écrit  :
> 
> Hello, search a way to use a serial connection to control Grub2, but my efi
> don't support a USB/Serial or any other serial connection. So I tried to
> use a FTDI Usb/Seial dongle in Grub. To access the device in the grub
> console i  run:
> 
> nativedisk
> insmod ehci

Why do you switch to native *disk* drivers when you only want to use the 
USB-serial port ?

> At this point i can use the serial connection or boot linux but cant boot
> windows anymore.
> If i try to use the chainloader, he get back: "not a valid root device".

When you switch to native disk drivers, drive names change, e.g. from 
(hd0) to (ahci0). You must adjust the $root and $prefix variables.
Also, native disk drivers may leave the hardware in a state not 
compatible with the firmware drivers, and the chainloaded program relies 
on firmware support for disk access.

>   now my questions are:
> - is it possible to bypass the use of the native diskdriver and use the usb
> dongle without break the efi stuff to boot over hd0... and not over
> ahci0... ?
> 
> - or is if possible to go back, after the serial connection was active, to
> the point where all disks are efi disks?

I'm afraid not.

> - or bring the chainloader  to work with
> "(ahci1,gpt1)/efi/Microsoft/Boot/bootmgfw.efi"

I'm afraid not.

_______________________________________________
Help-grub mailing list
Help-grub@gnu.org
https://lists.gnu.org/mailman/listinfo/help-grub

[prev in list] [next in list] [prev in thread] [next in thread]