Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
UEFI boot and sanhook
2018-09-18, 18:24
Post: #2
RE: UEFI boot and sanhook
What exactly is it that you want to do?
iPXE san* devices in EFI is exposed via the efi_block interface.
Booting from this works fine as you wrote.
(sanboot is just sanhook with the extra "tell firmware to boot it", so should be no difference)

When these block devices is connected it is up to mostly the efi firmware to do the right thing.
In the case of the shell it should be available there as block device, partitions and EFI compatible filesystems, if there are any that is.

I would also suggest to listen to the wire (tcpdump or wireshark) and see what is going on there.
One possible reason could be that when you start your applications the network layer is interrupted.

You might also want to provide more details on what you are doing and using (exact commands) in such a way that someone else would be able to reproduce this.

Use GitHub Discussions
VRAM bin
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
UEFI boot and sanhook - parthy - 2018-09-18, 15:27
RE: UEFI boot and sanhook - NiKiZe - 2018-09-18 18:24
RE: UEFI boot and sanhook - NiKiZe - 2018-09-19, 12:40
RE: UEFI boot and sanhook - parthy - 2018-09-19, 13:06
RE: UEFI boot and sanhook - NiKiZe - 2018-09-19, 13:16
RE: UEFI boot and sanhook - parthy - 2018-09-20, 09:24
RE: UEFI boot and sanhook - NiKiZe - 2018-09-20, 20:32



User(s) browsing this thread: 1 Guest(s)