On Tue, Jan 22, 2019 at 10:19:35AM +0100, Alexander Graf wrote:
>
>
> On 22.01.19 02:38, AKASHI Takahiro wrote:
> > Alex,
> >
> > On Mon, Jan 21, 2019 at 02:34:43PM +0100, Alexander Graf wrote:
> >> On 01/21/2019 08:49 AM, AKASHI Takahiro wrote:
> >>> "devices" command prints all the uefi variab
On 22.01.19 02:38, AKASHI Takahiro wrote:
> Alex,
>
> On Mon, Jan 21, 2019 at 02:34:43PM +0100, Alexander Graf wrote:
>> On 01/21/2019 08:49 AM, AKASHI Takahiro wrote:
>>> "devices" command prints all the uefi variables on the system.
>>>
>>> => efi devices
>>> Scanning disk ahci_scsi.id0lun0...
Alex,
On Mon, Jan 21, 2019 at 02:34:43PM +0100, Alexander Graf wrote:
> On 01/21/2019 08:49 AM, AKASHI Takahiro wrote:
> >"devices" command prints all the uefi variables on the system.
> >
> >=> efi devices
> >Scanning disk ahci_scsi.id0lun0...
> >Scanning disk ahci_scsi.id1lun0...
> >Found 4 disk
On 01/21/2019 08:49 AM, AKASHI Takahiro wrote:
"devices" command prints all the uefi variables on the system.
=> efi devices
Scanning disk ahci_scsi.id0lun0...
Scanning disk ahci_scsi.id1lun0...
Found 4 disks
D
e
vDevice Path
Why the weird formatting of "Dev"?
Alex
__
"devices" command prints all the uefi variables on the system.
=> efi devices
Scanning disk ahci_scsi.id0lun0...
Scanning disk ahci_scsi.id1lun0...
Found 4 disks
D
e
vDevice Path
7ef3bfa0 /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)
5 matches
Mail list logo