Re: Obtaining the UUID of the system for a PXE boot

2013-07-23 Thread Holger Goetz
Hi, looks i could need some help here. I've moved the smbios module from commands/i386 to commands and added some casts to make the compiler happy. As I need a x86_64-efi grub. What i see now is that the _SM_ signature is not found: Failed to locate entry point structure some added

Re: Obtaining the UUID of the system for a PXE boot

2013-07-23 Thread Andrey Borzenkov
В Tue, 23 Jul 2013 18:24:55 +0200 Holger Goetz holg...@hgsys.de пишет: Hi, looks i could need some help here. I've moved the smbios module from commands/i386 to commands and added some casts to make the compiler happy. As I need a x86_64-efi grub. What i see now is that the _SM_

Re: Obtaining the UUID of the system for a PXE boot

2013-07-20 Thread Holger Goetz
On 19.07.2013 18:31, David Michael wrote: Hi, On Fri, Jul 19, 2013 at 10:24 AM, Holger Goetz holg...@hgsys.de wrote: Yes it's towards the right direction. But it is 32bit only if i understand correctly, and it basically is a memory access to fixed/hardcoded MEMORY address (0x8001). to

Re: Obtaining the UUID of the system for a PXE boot

2013-07-20 Thread Vladimir 'φ-coder/phcoder' Serbinenko
If the module isn't salvageable on UEFI, maybe I can send out an updated version whenever I upgrade to such a system. Change to retrieve SMBIOS on EFI is minor. See ACPI for comparison. ___ Grub-devel mailing list Grub-devel@gnu.org

Re: Obtaining the UUID of the system for a PXE boot

2013-07-19 Thread Holger Goetz
Hi, ok posting on grub-devel list now. Further answer(s) at the bottom. On 18.07.2013 17:35, Andrey Borzenkov wrote: I guess further discussion should be really moved to grub-devel В Thu, 18 Jul 2013 12:39:44 +0200 Holger Goetz holg...@hgsys.de пишет: On 17.07.2013 16:31, Andrey Borzenkov

Re: Obtaining the UUID of the system for a PXE boot

2013-07-19 Thread David Michael
Hi, On Fri, Jul 19, 2013 at 10:24 AM, Holger Goetz holg...@hgsys.de wrote: Yes it's towards the right direction. But it is 32bit only if i understand correctly, and it basically is a memory access to fixed/hardcoded MEMORY address (0x8001). to pick the veondor id and machine info. It's