Re: [ipxe-devel] November wimboot patches for Syslinux

2018-12-31 Thread Max
Your first configuration actually works for me, both EFI and BIOS(because
they have different starting directories).
Than you so much!

I was trying to boot wimboot directly as a kernel.



On Mon, Dec 31, 2018 at 7:38 PM Alif M. Ahmad  wrote:

> On Mon, Dec 31, 2018 at 11:26:03PM +, Alif M. Ahmad wrote:
> > I encountered the same problem booting wimboot using syslinux
> > 'linux.c32' module[1] on bios qemu instance.
> >
> > Current workaround is to append 'rawwim' on the kernel command line
> >
> 'initrdfile' cannot be appended.
> ```
> label wimboot
> com32 linux.c32 /wimboot initrdfile=bcd,boot.sdi,boot.wim
> append rawwim
> ```
> >
> > [1] https://www.syslinux.org/wiki/index.php?title=Linux.c32
> ___
> ipxe-devel mailing list
> ipxe-devel@lists.ipxe.org
> https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
>
>
___
ipxe-devel mailing list
ipxe-devel@lists.ipxe.org
https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel


Re: [ipxe-devel] November wimboot patches for Syslinux

2018-12-31 Thread Alif M. Ahmad
On Mon, Dec 31, 2018 at 11:26:03PM +, Alif M. Ahmad wrote:
> I encountered the same problem booting wimboot using syslinux
> 'linux.c32' module[1] on bios qemu instance.
> 
> Current workaround is to append 'rawwim' on the kernel command line
> 
'initrdfile' cannot be appended.
```
label wimboot
com32 linux.c32 /wimboot initrdfile=bcd,boot.sdi,boot.wim
append rawwim
```
> 
> [1] https://www.syslinux.org/wiki/index.php?title=Linux.c32
___
ipxe-devel mailing list
ipxe-devel@lists.ipxe.org
https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel


Re: [ipxe-devel] November wimboot patches for Syslinux

2018-12-31 Thread Alif M. Ahmad
On Mon, Dec 31, 2018 at 02:57:25PM -0500, Max wrote:
> Update booting with Syslinux does not work either.
> From this screen with a loading bar I get:
> Patched WIM header boot metadata 0x137adea 5 ->0x1674da80
> Patched WIM header boot index 2->3
> 
> and before reboot I get:
> Could not set file position: 0x80035
> Failed to exit
> 
> It immediately reboots. I had to film the sequence and move through the
> frames to get the error.
> 

I encountered the same problem booting wimboot using syslinux
'linux.c32' module[1] on bios qemu instance.

Current workaround is to append 'rawwim' on the kernel command line

```
label wimboot
com32 linux.c32
append /wimboot initrdfile=bcd,boot.sdi,boot.wim rawwim
```

[1] https://www.syslinux.org/wiki/index.php?title=Linux.c32

___
ipxe-devel mailing list
ipxe-devel@lists.ipxe.org
https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel


Re: [ipxe-devel] November wimboot patches for Syslinux

2018-12-31 Thread Max
Update booting with Syslinux does not work either.
>From this screen with a loading bar I get:
Patched WIM header boot metadata 0x137adea 5 ->0x1674da80
Patched WIM header boot index 2->3

and before reboot I get:
Could not set file position: 0x80035
Failed to exit

It immediately reboots. I had to film the sequence and move through the
frames to get the error.

If you are interested in seeing the pictures I put those two screens on
imgur:
https://imgur.com/a/YWYk3Pi

I would be interested in getting this to work and testing this further.

Thanks in advance and I hope everyone has a happy new year!

-Max

On Sun, Dec 30, 2018 at 11:35 AM Max  wrote:

> Hello all,
>
> I have just joined the list. I am familiar with compiling things in *nix
> and some C, but have never done any real programming in C.
>
> I have been trying to get wimboot to work in or via Grub2 EFI.
>
> I downloaded the patches sent to this list in November from Friedemann.
> It may have been the way I downloaded them, but for every one of the search
> lines, I had to remove a leading space.  Additionally, it looks like the
> second email/patch has the patch text 2x separated by a shell prompt.
>
> After that, the additional function efi_add_file in efifile.c was not also
> added to the header file.  I don't know if that is something that I should
> just know to run a command to auto regenerate or just an oversight.
>
> The addition of efi_add_file includes a line directly above which only
> contains "int".  Comparing that function to the functions around it made me
> think int should begin the same line as the function efi_add_file.
>
> After adding the function to efifile.h :
> extern int efi_add_file ( const char *name, void *data, size_t len);
>
> I got farther, however my system did not understand the -liberty flag to
> gcc/cc .  I looked around a bit, but did not find a reference to the flag
> in the documentation so I removed it.
>
> The binary then compiles and boots via normal methods.  It did not improve
> booting via grub2 from USB.
>
> The patch was designed for Syslinux though, so I will test that next.
>
> If anyone can fill me in on the -liberty flag or what should have been
> done with headers file that would be appreciated.  Any other suggestions
> and comments are also appreciated, but I suspect out of the scope of this
> list.
>
>
> Thank you in advance,
>   Max
>
> Ah, almost forgot I'm compiling on 64-bit Ubuntu 18.04.1 .
> gcc (Ubuntu 7.3.0-27ubuntu1~18.04) 7.3.0
> Wimboot was cloned from the git repo on the iPXE domain and is up-to-date.
>
>
___
ipxe-devel mailing list
ipxe-devel@lists.ipxe.org
https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel