Menu
▾
▴
efidevkit-devel — EFI Dev Kit (EDK) developer discussions
You can subscribe to this list here.
| 2010 |
Jan
|
Feb
(1) |
Mar
(3) |
Apr
(1) |
May
(8) |
Jun
(11) |
Jul
(5) |
Aug
(1) |
Sep
|
Oct
(12) |
Nov
(5) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2011 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(3) |
Jun
(1) |
Jul
(13) |
Aug
(17) |
Sep
(9) |
Oct
(6) |
Nov
(6) |
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
(3) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(1) |
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Daniel M. <dan...@er...> - 2011-07-14 10:32:04
|
I have found another problem. When trying to load the tcpipv4.efi driver and when I reach this line on efi_netiface.c: Status = pIface->Receive (pIface, NULL, &len, Frame, NULL, NULL, NULL); Which calls the receive function of the Simple Network Protocol UEFI protocol, I get TPL assertions generated by my BIOS. Always 2 assertions on: CoreRaiseTpl and then in CoreRestoreTpl The driver successfully loads and then the assertions take control of the CPU which enters in an infinite raise-restore TPL assertions loop. Any idea on what might be happening? Thanks ________________________________ From: Daniel Moral [mailto:dan...@er...] Sent: den 14 juli 2011 10:52 To: edk...@li...; efi...@li... Subject: [edk2] EFI TOOLKIT ASSERTION BUG Hi, I have a problem loading the DHCP driver of the EFI toolkit. I get this error: assertion "tmp != NULL" failed: file "sys\open.c", line 171 load: Image fs0:\GEP4MIN\DHCLIENT.EFI loaded at 33CC000 - Warning Unknown Glyph Which I seems happens to be the same as: http://sourceforge.net/tracker/?func=detail&aid=2959886&group_id=289014&atid=1223910 I tried their fix, indeed I tried with: #define MAX_ENVIRONMENT_DATA 4098 #define MAX_ENVIRONMENT_DATA 36882 #define MAX_ENVIRONMENT_DATA 100000 #define MAX_ENVIRONMENT_DATA 1000000 None of them solved the problem, I still get that assert. Any ideas on how can I solve this? I think it is a known bug because there exists on the proyect tracker but the solution did not work for me so does anyone figured out on how to solve it? |
|
From: Daniel M. <dan...@er...> - 2011-07-14 08:52:33
|
Hi, I have a problem loading the DHCP driver of the EFI toolkit. I get this error: assertion "tmp != NULL" failed: file "sys\open.c", line 171 load: Image fs0:\GEP4MIN\DHCLIENT.EFI loaded at 33CC000 - Warning Unknown Glyph Which I seems happens to be the same as: http://sourceforge.net/tracker/?func=detail&aid=2959886&group_id=289014&atid=1223910 I tried their fix, indeed I tried with: #define MAX_ENVIRONMENT_DATA 4098 #define MAX_ENVIRONMENT_DATA 36882 #define MAX_ENVIRONMENT_DATA 100000 #define MAX_ENVIRONMENT_DATA 1000000 None of them solved the problem, I still get that assert. Any ideas on how can I solve this? I think it is a known bug because there exists on the proyect tracker but the solution did not work for me so does anyone figured out on how to solve it? |
|
From: Daniel M. <dan...@er...> - 2011-07-13 08:43:21
|
Hi all, I am following the instructions to set up the network stack using EFI Toolkit, so I first load the TCPIP driver, which goes ok: fs0:\> load TCPIPV4.EFI Interface attached to lo0 Interface attached to sni0 Interface attached to sni1 Interface attached to ppp0 Timecounter "TcpIpv4" frequency 18 Hz Network protocol loaded and initialized load: Image fs0:\TCPIPV4.EFI loaded at 251E000 - Success But then I got this fs0:\> load DHCLIENT.EFI \dcsVLtpLi.nsh> echo -off add host 255.255.255.255: gateway sni1 \dcsQqRtfz.nsh> echo -off ifconfig: ioctl (SIOCAIFADDR): File exists add host 255.255.255.255: gateway sni0 Listening on Socket/sni1 Sending on Socket/sni1 The standard socket API can only support hosts with a single network interface. exiting. load: Image fs0:\DHCLIENT.EFI error - Unload Image Anyone knows what could be the problem? I have 2 ethernet interfaces, the one conected to the DHCP server is eth0 (sni0) and I do not know what is the problem. Thank you |
|
From: Daniel M. <dan...@er...> - 2011-07-12 16:10:08
|
You are right, it works :) In fact I think that the problem with the 2GB limit in FAT16 can be circumvected because using efifmt.efi you can format it later to FAT32, so I think I would be able to use any value. I cannot prove this yet because I only have a 2GB RAM board, but I will tell you when I try it. Thank you ________________________________ From: Carsey, Jaben [mailto:jab...@in...] Sent: den 12 juli 2011 17:09 To: edk...@li...; efi...@li... Subject: Re: [edk2] Memory mapped file system on RAM used by EDK shell Did you verify that the 'fat16tbl' has the entries that you need? I noticed that the size2spc function that parses the table has it's return value checked with an ASSERT. Hence if this fails the program will halt. -Jaben From: Daniel Moral [mailto:dan...@er...] Sent: Tuesday, July 12, 2011 7:54 AM To: edk...@li...; efi...@li... Subject: Re: [edk2] Memory mapped file system on RAM used by EDK shell Yes, I already changed it to 1024 but when running the application it frozes. I think there might be a reason why they did that, I just do not know what is it. But I think I will have to touch more code. The system it generates is FAT16 which as far as I know works fairly well for 512MB< disks. But the FAT16 limit is 2GB in theory and some times 4GB in practice. I was also thinking on creating several disks and doing some kind of "raid" system or so, but I have no idea on how to do it. ________________________________ From: Carsey, Jaben [mailto:jab...@in...] Sent: den 12 juli 2011 16:50 To: edk...@li...; efi...@li... Subject: Re: [edk2] Memory mapped file system on RAM used by EDK shell Looks in the code like there is just a maximum size defined. Maybe you can upgrade the ramdisk driver? Search for MAX_DISK_SIZE in ramdisk.c. -Jaben From: Daniel Moral [mailto:dan...@er...] Sent: Tuesday, July 12, 2011 6:22 AM To: edk...@li...; efi...@li... Subject: Re: [edk2] Memory mapped file system on RAM used by EDK shell Hi Joe, Thank you for telling me from where dide the GUID came. I have found the problem, in the changelog of the toolkit: Changes from Release 1.02.12.38 to Release 1.10.14.62 Fixed a bug where Mkramdisk.efi needed ramdisk.efi to be located in the root directory. Ramdisk.efi now will accommodate RAM disk sizes down to 2 MB (the previous version would allow minimum RAM disk sizes down only to 5 MB). The maximum RAM disk size (assuming memory is available) is 512 MB. Does anybody know why is this? Can this size be increased? Is there any way to create several 512RAM Disks and merge them? Thank you very much. BR Daniel ________________________________ From: Joe Thomas [mailto:Joe...@do...] Sent: den 12 juli 2011 14:16 To: efi...@li...; edk...@li... Subject: Re: [edk2] Memory mapped file system on RAM used by EDK shell Daniel, The name 'f0agonennapphibbndlnmeaakamjeafdnb' is an encoding of the GUID value from the Vendor Message type of device that is created by the driver (VenMsg(06ED4DD0-FF78-11D3-BDC4-00A0C94053D1)) As to the size, I'm not certain but is the 'size=xxxx' parameter in your DISKPART create in blocks or MB? [I would suspect that it's in block and if so, try size=100000 as shown in the 'list' command...] -Joe Thomas |
|
From: Daniel M. <dan...@er...> - 2011-07-12 14:53:57
|
Yes, I already changed it to 1024 but when running the application it frozes. I think there might be a reason why they did that, I just do not know what is it. But I think I will have to touch more code. The system it generates is FAT16 which as far as I know works fairly well for 512MB< disks. But the FAT16 limit is 2GB in theory and some times 4GB in practice. I was also thinking on creating several disks and doing some kind of "raid" system or so, but I have no idea on how to do it. ________________________________ From: Carsey, Jaben [mailto:jab...@in...] Sent: den 12 juli 2011 16:50 To: edk...@li...; efi...@li... Subject: Re: [edk2] Memory mapped file system on RAM used by EDK shell Looks in the code like there is just a maximum size defined. Maybe you can upgrade the ramdisk driver? Search for MAX_DISK_SIZE in ramdisk.c. -Jaben From: Daniel Moral [mailto:dan...@er...] Sent: Tuesday, July 12, 2011 6:22 AM To: edk...@li...; efi...@li... Subject: Re: [edk2] Memory mapped file system on RAM used by EDK shell Hi Joe, Thank you for telling me from where dide the GUID came. I have found the problem, in the changelog of the toolkit: Changes from Release 1.02.12.38 to Release 1.10.14.62 Fixed a bug where Mkramdisk.efi needed ramdisk.efi to be located in the root directory. Ramdisk.efi now will accommodate RAM disk sizes down to 2 MB (the previous version would allow minimum RAM disk sizes down only to 5 MB). The maximum RAM disk size (assuming memory is available) is 512 MB. Does anybody know why is this? Can this size be increased? Is there any way to create several 512RAM Disks and merge them? Thank you very much. BR Daniel ________________________________ From: Joe Thomas [mailto:Joe...@do...] Sent: den 12 juli 2011 14:16 To: efi...@li...; edk...@li... Subject: Re: [edk2] Memory mapped file system on RAM used by EDK shell Daniel, The name 'f0agonennapphibbndlnmeaakamjeafdnb' is an encoding of the GUID value from the Vendor Message type of device that is created by the driver (VenMsg(06ED4DD0-FF78-11D3-BDC4-00A0C94053D1)) As to the size, I'm not certain but is the 'size=xxxx' parameter in your DISKPART create in blocks or MB? [I would suspect that it's in block and if so, try size=100000 as shown in the 'list' command...] -Joe Thomas |
|
From: Daniel M. <dan...@er...> - 2011-07-12 13:25:02
|
Hi Joe, Thank you for telling me from where dide the GUID came. I have found the problem, in the changelog of the toolkit: Changes from Release 1.02.12.38 to Release 1.10.14.62 Fixed a bug where Mkramdisk.efi needed ramdisk.efi to be located in the root directory. Ramdisk.efi now will accommodate RAM disk sizes down to 2 MB (the previous version would allow minimum RAM disk sizes down only to 5 MB). The maximum RAM disk size (assuming memory is available) is 512 MB. Does anybody know why is this? Can this size be increased? Is there any way to create several 512RAM Disks and merge them? Thank you very much. BR Daniel From: Joe Thomas [mailto:Joe...@do...] Sent: den 12 juli 2011 14:16 To: efi...@li...; edk...@li... Subject: Re: [edk2] Memory mapped file system on RAM used by EDK shell Daniel, The name 'f0agonennapphibbndlnmeaakamjeafdnb' is an encoding of the GUID value from the Vendor Message type of device that is created by the driver (VenMsg(06ED4DD0-FF78-11D3-BDC4-00A0C94053D1)) As to the size, I'm not certain but is the 'size=xxxx' parameter in your DISKPART create in blocks or MB? [I would suspect that it's in block and if so, try size=100000 as shown in the 'list' command...] -Joe Thomas |
|
From: Joe T. <Joe...@do...> - 2011-07-12 12:50:04
|
Daniel,
The name 'f0agonennapphibbndlnmeaakamjeafdnb' is an encoding of the GUID value from the Vendor Message type of device that is created by the driver (VenMsg(06ED4DD0-FF78-11D3-BDC4-00A0C94053D1))
As to the size, I'm not certain but is the 'size=xxxx' parameter in your DISKPART create in blocks or MB? [I would suspect that it's in block and if so, try size=100000 as shown in the 'list' command...]
-Joe Thomas
From: Daniel Moral [mailto:dan...@er...]
Sent: Monday, July 11, 2011 9:08 AM
To: edk...@li...
Cc: efi...@li...
Subject: Re: [edk] [edk2] Memory mapped file system on RAM used by EDK shell
Thanks both for your help.
Here is what I am doing. In the toolkit there is an application called mkramdisk which installs the ramdisk driver and you can specify the number of bytes, for example:
fs0:\> mkramdisk.efi -s 2000 f
Device mapping table
f :BlockDevice - Alias (null)
VenMsg(06ED4DD0-FF78-11D3-BDC4-00A0C94053D1)
Done: RAM Disk [ f ] with size [ 2000MB ]
That creates a 2000MB ram disk called f. Nevertheless it appears to be some problem with the name cause I get:
fs0:\> map -r
Device mapping table
fs0 :BlockDevice - Alias f0agonennapphibbndlnmeaakamjeafdnb blk0
VenMsg(06ED4DD0-FF78-11D3-BDC4-00A0C94053D1)
fs1 :Removeable BlockDevice - Alias f40c0 blk1
Acpi(PNP0A03,0)/Pci(1D|7)/Usb(2, 0)
blk0 :BlockDevice - Alias f0agonennapphibbndlnmeaakamjeafdnb fs0
VenMsg(06ED4DD0-FF78-11D3-BDC4-00A0C94053D1)
blk1 :Removeable BlockDevice - Alias f40c0 fs1
Acpi(PNP0A03,0)/Pci(1D|7)/Usb(2, 0)
f0agonennapphibbndlnmeaakamjeafdnb :BlockDevice - Alias fs0 blk0
VenMsg(06ED4DD0-FF78-11D3-BDC4-00A0C94053D1)
f40c0 :Removeable BlockDevice - Alias fs1 blk1
Acpi(PNP0A03,0)/Pci(1D|7)/Usb(2, 0)
Where f0agonen... is a strange name.
There is a set of tools called EFI Disk utilities which I employed to format: http://www.intel.com/technology/efi/diskutil_overview.htm
First I tried using efifmt.efi directly on the created device, but it did not work:
fs1:\> EFIFMT.EFI blk0
EfiFmt Version 1.2. Based on EFI Version 2.10
IFSUTIL: Can't open drive. Status returned = C0000001.
Cannot determine file system of drive blk0.
Unable to determine file system type.
Cannot open volume for direct access.
What I do is first create a partition in the disk and then format it this way:
fs1:\> DISKPART.EFI
DiskPart Version 1.2. Based on EFI Version 2.10
DiskPart> list
### BlkSize BlkCount
--- ------- ----------------
0 200 100000
DiskPart> select 0
Selected Disk = 0
DiskPart> clean all
About to CLEAN (DESTROY) disk 0, are you SURE [y/n]?
CLEAN>> y
If you are REALLY SURE, type '$C'
CLEAN>> $C
DiskPart> new gpt
DiskPart> create name=partition type=efisys size=2000
DiskPart> exit
Exiting....
fs1:\> map -r
Device mapping table
fs0 :Removeable BlockDevice - Alias f40c0 blk0
Acpi(PNP0A03,0)/Pci(1D|7)/Usb(2, 0)
blk0 :Removeable BlockDevice - Alias f40c0 fs0
Acpi(PNP0A03,0)/Pci(1D|7)/Usb(2, 0)
blk1 :HardDisk - Alias (null)
VenMsg(06ED4DD0-FF78-11D3-BDC4-00A0C94053D1)/HD(Part1,Sig301D7800-1DD2-1000-9620-001A4B6FDBCA)
blk2 :BlockDevice - Alias (null)
VenMsg(06ED4DD0-FF78-11D3-BDC4-00A0C94053D1)
f40c0 :Removeable BlockDevice - Alias fs0 blk0
Shell> EFIFMT.EFI blk1 /FS:FAT32
EfiFmt Version 1.2. Based on EFI Version 2.10
WARNING, ALL DATA ON EFI DEVICE
blk1 WILL BE LOST!
Proceed with Format (Y/N)? y
Formatting 511M
Initializing the File Allocation Table (FAT)...
Volume label (11 characters, ENTER for none)? ramdisk
Format complete.
535769088 bytes total disk space.
535764992 bytes available on disk.
4096 bytes in each allocation unit.
130802 allocation units available on disk.
32 bits in each FAT entry.
Volume Serial Number is 000040B3-00004A89
Then everything goes fine I can read, write, mkdir etc.. on that volume and when using dblk the output seems correct:
Shell> dblk blk0
LBA 0000000000000000 Size 00000200 bytes BlkIo 01F14F18
00000000: EB 58 90 4D 53 44 4F 53-35 2E 30 00 02 08 26 00 *.X.MSDOS5.0...&.*
00000010: 02 00 00 00 00 F8 00 00-01 00 01 00 00 00 00 00 *................*
00000020: 00 00 79 00 31 1E 00 00-00 00 00 00 02 00 00 00 *..y.1...........*
00000030: 01 00 06 00 00 00 00 00-00 00 00 00 00 00 00 00 *................*
00000040: 00 00 29 27 7A 7B C4 4E-4F 20 4E 41 4D 45 20 20 *..)'z..NO NAME *
00000050: 20 20 46 41 54 33 32 20-20 20 33 C9 8E D1 BC F4 * FAT32 3.....*
00000060: 7B 8E C1 8E D9 BD 00 7C-88 4E 02 8A 56 40 B4 08 *.........N..V@..*<mailto:*.........N..V@..*>
00000070: CD 13 73 05 B9 FF FF 8A-F1 66 0F B6 C6 40 66 0F *..s......f...@f<mailto:*..s......f...@f>.*
00000080: B6 D1 80 E2 3F F7 E2 86-CD C0 ED 06 41 66 0F B7 *....?.......Af..*
00000090: C9 66 F7 E1 66 89 46 F8-83 7E 16 00 75 38 83 7E *.f..f.F.....u8..*
000000A0: 2A 00 77 32 66 8B 46 1C-66 83 C0 0C BB 00 80 B9 **.w2f.F.f.......*
000000B0: 01 00 E8 2B 00 E9 48 03-A0 FA 7D B4 7D 8B F0 AC *...+..H.........*
000000C0: 84 C0 74 17 3C FF 74 09-B4 0E BB 07 00 CD 10 EB *..t.<.t.........*
000000D0: EE A0 FB 7D EB E5 A0 F9-7D EB E0 98 CD 16 CD 19 *................*
000000E0: 66 60 66 3B 46 F8 0F 82-4A 00 66 6A 00 66 50 06 *f`f;F...J.fj.fP.*
000000F0: 53 66 68 10 00 01 00 80-7E 02 00 0F 85 20 00 B4 *Sfh.......... ..*
00000100: 41 BB AA 55 8A 56 40 CD-13 0F 82 1C 00 81 FB 55 *A..U.V@........U<mailto:*A..U.V@........U>*
00000110: AA 0F 85 14 00 F6 C1 01-0F 84 0D 00 FE 46 02 B4 *.............F..*
00000120: 42 8A 56 40 8B F4 CD 13-B0 F9 66 58 66 58 66 58 *B.V@......fXfXfX<mailto:*B.V@......fXfXfX>*
00000130: 66 58 EB 2A 66 33 D2 66-0F B7 4E 18 66 F7 F1 FE *fX.*f3.f..N.f...*
00000140: C2 8A CA 66 8B D0 66 C1-EA 10 F7 76 1A 86 D6 8A *...f..f....v....*
00000150: 56 40 8A E8 C0 E4 06 0A-CC B8 01 02 CD 13 66 61 *V@............fa<mailto:*V@............fa>*
00000160: 0F 82 54 FF 81 C3 00 02-66 40 49 0F 85 71 FF C3 *..T.....f@I..q<mailto:*..T.....f@I..q>..*
00000170: 4E 54 4C 44 52 20 20 20-20 20 20 00 00 00 00 00 *NTLDR .....*
00000180: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 *................*
00000190: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 *................*
000001A0: 00 00 00 00 00 00 00 00-00 00 00 00 0D 0A 4E 54 *..............NT*
000001B0: 4C 44 52 20 69 73 20 6D-69 73 73 69 6E 67 FF 0D *LDR is missing..*
000001C0: 0A 44 69 73 6B 20 65 72-72 6F 72 FF 0D 0A 50 72 *.Disk error...Pr*
000001D0: 65 73 73 20 61 6E 79 20-6B 65 79 20 74 6F 20 72 *ess any key to r*
000001E0: 65 73 74 61 72 74 0D 0A-00 00 00 00 00 00 00 00 *estart..........*
000001F0: 00 00 00 00 00 00 00 00-00 AC BF CC 00 00 55 AA *..............U.*
But there is something that I do not understand. Why if I am reserving 2000MB when I format it it only recognizes 511MB?
Formatting 511M
I tried several times but I only got it to recognize the 511MB.
Thank you very much for your help again :)
BR
Daniel
________________________________
From: Andrew Fish [mailto:af...@ap...]
Sent: den 8 juli 2011 19:08
To: edk...@li...
Cc: efi...@li...
Subject: Re: [edk2] Memory mapped file system on RAM used by EDK shell
Daniel,
I think there is a RAM Disk driver in the toolkit.... It produces the Block IO protocol. The only problem is you have to format the Block IO partition to put a file system on it. There is an EFI application to do that. If the Block IO protocol abstracts blocks that contain a FAT file system then when you connect that handle the file system driver will bind and you will get a Simple File System Protocol that would show up at the shell prompt.
It would be possible to write a Simple File System Driver that just treated files as linked lists. I've never seen this done, but it is quite possible.
These two chunks work together to make Simple File System on top of ANSI C APIs:
https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2/EmulatorPkg/EmuSimpleFileSystemDxe/EmuSimpleFileSystem.c
https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2/EmulatorPkg/Unix/Host/PosixFileSystem.c
Maybe this would be a good GSOC project at some point.
Andrew Fish
On Jul 8, 2011, at 9:28 AM, Daniel Moral wrote:
Hi!
I want to build a memory mapped file system in order to use it with EDK1 Shell. What I want is to create a temporal file system using the RAM memory
of my board in order to store there files downloaded from a tftp server without needing an external flash memory. Therefore I could use the files
I download in other applications.
I am a bit lost on how I could do this. Would it be possible to create a virtual drive using the RAM memory and "trick" the shell so it thinks it is
just another volume? Or should I think in other possibilities?
Thank you very much.
BR
Daniel
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2_______________________________________________
edk2-devel mailing list
edk...@li...<mailto:edk...@li...>
https://lists.sourceforge.net/lists/listinfo/edk2-devel
|
|
From: Daniel M. <dan...@er...> - 2011-07-11 16:27:41
|
I have found that the problem is not on efifmt.efi. I have this memory map:
reserved : 47 Pages (192,512)
LoaderCode: 120 Pages (491,520)
LoaderData: 278 Pages (1,138,688)
BS_code : 723 Pages (2,961,408)
BS_data : 4,845 Pages (19,845,120)
RT_code : 74 Pages (303,104)
RT_data : 44 Pages (180,224)
available : 515,343 Pages (2,110,844,928)
ACPI_recl : 11 Pages (45,056)
ACPI_NVS : 659 Pages (2,699,264)
MemMapIO : 69,636 Pages (285,229,056)
Total Memory: 2,039 MB (2,138,509,312) Bytes
Which means more or less 2000MB free then I do:
fs0:\> mkramdisk.efi -s 2000 l
Device mapping table
l :BlockDevice - Alias (null)
VenMsg(06ED4DD0-FF78-11D3-BDC4-00A0C94053D1)
Done: RAM Disk [ l ] with size [ 2000MB ]
But when I do partition:
fs0:\> DISKPART.EFI
DiskPart Version 1.2. Based on EFI Version 2.10
DiskPart> list
### BlkSize BlkCount
--- ------- ----------------
0 200 100000
DiskPart> select 0
Selected Disk = 0
DiskPart> clean all
About to CLEAN (DESTROY) disk 0, are you SURE [y/n]?
CLEAN>> y
If you are REALLY SURE, type '$C'
CLEAN>> $C
DiskPart> new gpt
DiskPart> create name=partition type=efisys ver
CmdCreate arguments:
SelectedDisk = 0
Name=PARTITION
TypeGuid = C12A7328-F81F-11D2-BA4B-00A0C93EC93B
TypeName = EFISYS
Requested OffsetInBlocks = 0
Requested SizeInMegaBytes = 0
Attributes = 0
Requested SizeInMegaBytes = 0
Resulting size in Blocks = 1048509
Results size in Bytes = 536836608
Any idea?
________________________________
From: Daniel Moral [mailto:dan...@er...]
Sent: den 11 juli 2011 16:08
To: edk...@li...
Cc: efi...@li...
Subject: Re: [edk2] Memory mapped file system on RAM used by EDK shell
Thanks both for your help.
Here is what I am doing. In the toolkit there is an application called mkramdisk which installs the ramdisk driver and you can specify the number of bytes, for example:
fs0:\> mkramdisk.efi -s 2000 f
Device mapping table
f :BlockDevice - Alias (null)
VenMsg(06ED4DD0-FF78-11D3-BDC4-00A0C94053D1)
Done: RAM Disk [ f ] with size [ 2000MB ]
That creates a 2000MB ram disk called f. Nevertheless it appears to be some problem with the name cause I get:
fs0:\> map -r
Device mapping table
fs0 :BlockDevice - Alias f0agonennapphibbndlnmeaakamjeafdnb blk0
VenMsg(06ED4DD0-FF78-11D3-BDC4-00A0C94053D1)
fs1 :Removeable BlockDevice - Alias f40c0 blk1
Acpi(PNP0A03,0)/Pci(1D|7)/Usb(2, 0)
blk0 :BlockDevice - Alias f0agonennapphibbndlnmeaakamjeafdnb fs0
VenMsg(06ED4DD0-FF78-11D3-BDC4-00A0C94053D1)
blk1 :Removeable BlockDevice - Alias f40c0 fs1
Acpi(PNP0A03,0)/Pci(1D|7)/Usb(2, 0)
f0agonennapphibbndlnmeaakamjeafdnb :BlockDevice - Alias fs0 blk0
VenMsg(06ED4DD0-FF78-11D3-BDC4-00A0C94053D1)
f40c0 :Removeable BlockDevice - Alias fs1 blk1
Acpi(PNP0A03,0)/Pci(1D|7)/Usb(2, 0)
Where f0agonen... is a strange name.
There is a set of tools called EFI Disk utilities which I employed to format: http://www.intel.com/technology/efi/diskutil_overview.htm
First I tried using efifmt.efi directly on the created device, but it did not work:
fs1:\> EFIFMT.EFI blk0
EfiFmt Version 1.2. Based on EFI Version 2.10
IFSUTIL: Can't open drive. Status returned = C0000001.
Cannot determine file system of drive blk0.
Unable to determine file system type.
Cannot open volume for direct access.
What I do is first create a partition in the disk and then format it this way:
fs1:\> DISKPART.EFI
DiskPart Version 1.2. Based on EFI Version 2.10
DiskPart> list
### BlkSize BlkCount
--- ------- ----------------
0 200 100000
DiskPart> select 0
Selected Disk = 0
DiskPart> clean all
About to CLEAN (DESTROY) disk 0, are you SURE [y/n]?
CLEAN>> y
If you are REALLY SURE, type '$C'
CLEAN>> $C
DiskPart> new gpt
DiskPart> create name=partition type=efisys size=2000
DiskPart> exit
Exiting....
fs1:\> map -r
Device mapping table
fs0 :Removeable BlockDevice - Alias f40c0 blk0
Acpi(PNP0A03,0)/Pci(1D|7)/Usb(2, 0)
blk0 :Removeable BlockDevice - Alias f40c0 fs0
Acpi(PNP0A03,0)/Pci(1D|7)/Usb(2, 0)
blk1 :HardDisk - Alias (null)
VenMsg(06ED4DD0-FF78-11D3-BDC4-00A0C94053D1)/HD(Part1,Sig301D7800-1DD2-1000-9620-001A4B6FDBCA)
blk2 :BlockDevice - Alias (null)
VenMsg(06ED4DD0-FF78-11D3-BDC4-00A0C94053D1)
f40c0 :Removeable BlockDevice - Alias fs0 blk0
Shell> EFIFMT.EFI blk1 /FS:FAT32
EfiFmt Version 1.2. Based on EFI Version 2.10
WARNING, ALL DATA ON EFI DEVICE
blk1 WILL BE LOST!
Proceed with Format (Y/N)? y
Formatting 511M
Initializing the File Allocation Table (FAT)...
Volume label (11 characters, ENTER for none)? ramdisk
Format complete.
535769088 bytes total disk space.
535764992 bytes available on disk.
4096 bytes in each allocation unit.
130802 allocation units available on disk.
32 bits in each FAT entry.
Volume Serial Number is 000040B3-00004A89
Then everything goes fine I can read, write, mkdir etc.. on that volume and when using dblk the output seems correct:
Shell> dblk blk0
LBA 0000000000000000 Size 00000200 bytes BlkIo 01F14F18
00000000: EB 58 90 4D 53 44 4F 53-35 2E 30 00 02 08 26 00 *.X.MSDOS5.0...&.*
00000010: 02 00 00 00 00 F8 00 00-01 00 01 00 00 00 00 00 *................*
00000020: 00 00 79 00 31 1E 00 00-00 00 00 00 02 00 00 00 *..y.1...........*
00000030: 01 00 06 00 00 00 00 00-00 00 00 00 00 00 00 00 *................*
00000040: 00 00 29 27 7A 7B C4 4E-4F 20 4E 41 4D 45 20 20 *..)'z..NO NAME *
00000050: 20 20 46 41 54 33 32 20-20 20 33 C9 8E D1 BC F4 * FAT32 3.....*
00000060: 7B 8E C1 8E D9 BD 00 7C-88 4E 02 8A 56 40 B4 08 *.........N..V@..*
00000070: CD 13 73 05 B9 FF FF 8A-F1 66 0F B6 C6 40 66 0F *..s......f...@f<mailto:*..s......f...@f>.*
00000080: B6 D1 80 E2 3F F7 E2 86-CD C0 ED 06 41 66 0F B7 *....?.......Af..*
00000090: C9 66 F7 E1 66 89 46 F8-83 7E 16 00 75 38 83 7E *.f..f.F.....u8..*
000000A0: 2A 00 77 32 66 8B 46 1C-66 83 C0 0C BB 00 80 B9 **.w2f.F.f.......*
000000B0: 01 00 E8 2B 00 E9 48 03-A0 FA 7D B4 7D 8B F0 AC *...+..H.........*
000000C0: 84 C0 74 17 3C FF 74 09-B4 0E BB 07 00 CD 10 EB *..t.<.t.........*
000000D0: EE A0 FB 7D EB E5 A0 F9-7D EB E0 98 CD 16 CD 19 *................*
000000E0: 66 60 66 3B 46 F8 0F 82-4A 00 66 6A 00 66 50 06 *f`f;F...J.fj.fP.*
000000F0: 53 66 68 10 00 01 00 80-7E 02 00 0F 85 20 00 B4 *Sfh.......... ..*
00000100: 41 BB AA 55 8A 56 40 CD-13 0F 82 1C 00 81 FB 55 *A..U.V@........U<mailto:*A..U.V@........U>*
00000110: AA 0F 85 14 00 F6 C1 01-0F 84 0D 00 FE 46 02 B4 *.............F..*
00000120: 42 8A 56 40 8B F4 CD 13-B0 F9 66 58 66 58 66 58 *B.V@......fXfXfX<mailto:*B.V@......fXfXfX>*
00000130: 66 58 EB 2A 66 33 D2 66-0F B7 4E 18 66 F7 F1 FE *fX.*f3.f..N.f...*
00000140: C2 8A CA 66 8B D0 66 C1-EA 10 F7 76 1A 86 D6 8A *...f..f....v....*
00000150: 56 40 8A E8 C0 E4 06 0A-CC B8 01 02 CD 13 66 61 *V@............fa<mailto:*V@............fa>*
00000160: 0F 82 54 FF 81 C3 00 02-66 40 49 0F 85 71 FF C3 *..T.....f@I..q<mailto:*..T.....f@I..q>..*
00000170: 4E 54 4C 44 52 20 20 20-20 20 20 00 00 00 00 00 *NTLDR .....*
00000180: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 *................*
00000190: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 *................*
000001A0: 00 00 00 00 00 00 00 00-00 00 00 00 0D 0A 4E 54 *..............NT*
000001B0: 4C 44 52 20 69 73 20 6D-69 73 73 69 6E 67 FF 0D *LDR is missing..*
000001C0: 0A 44 69 73 6B 20 65 72-72 6F 72 FF 0D 0A 50 72 *.Disk error...Pr*
000001D0: 65 73 73 20 61 6E 79 20-6B 65 79 20 74 6F 20 72 *ess any key to r*
000001E0: 65 73 74 61 72 74 0D 0A-00 00 00 00 00 00 00 00 *estart..........*
000001F0: 00 00 00 00 00 00 00 00-00 AC BF CC 00 00 55 AA *..............U.*
But there is something that I do not understand. Why if I am reserving 2000MB when I format it it only recognizes 511MB?
Formatting 511M
I tried several times but I only got it to recognize the 511MB.
Thank you very much for your help again :)
BR
Daniel
________________________________
From: Andrew Fish [mailto:af...@ap...]
Sent: den 8 juli 2011 19:08
To: edk...@li...
Cc: efi...@li...
Subject: Re: [edk2] Memory mapped file system on RAM used by EDK shell
Daniel,
I think there is a RAM Disk driver in the toolkit.... It produces the Block IO protocol. The only problem is you have to format the Block IO partition to put a file system on it. There is an EFI application to do that. If the Block IO protocol abstracts blocks that contain a FAT file system then when you connect that handle the file system driver will bind and you will get a Simple File System Protocol that would show up at the shell prompt.
It would be possible to write a Simple File System Driver that just treated files as linked lists. I've never seen this done, but it is quite possible.
These two chunks work together to make Simple File System on top of ANSI C APIs:
https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2/EmulatorPkg/EmuSimpleFileSystemDxe/EmuSimpleFileSystem.c
https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2/EmulatorPkg/Unix/Host/PosixFileSystem.c
Maybe this would be a good GSOC project at some point.
Andrew Fish
On Jul 8, 2011, at 9:28 AM, Daniel Moral wrote:
Hi!
I want to build a memory mapped file system in order to use it with EDK1 Shell. What I want is to create a temporal file system using the RAM memory
of my board in order to store there files downloaded from a tftp server without needing an external flash memory. Therefore I could use the files
I download in other applications.
I am a bit lost on how I could do this. Would it be possible to create a virtual drive using the RAM memory and "trick" the shell so it thinks it is
just another volume? Or should I think in other possibilities?
Thank you very much.
BR
Daniel
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2_______________________________________________
edk2-devel mailing list
edk...@li...<mailto:edk...@li...>
https://lists.sourceforge.net/lists/listinfo/edk2-devel
|
|
From: Daniel M. <dan...@er...> - 2011-07-11 14:08:23
|
Thanks both for your help.
Here is what I am doing. In the toolkit there is an application called mkramdisk which installs the ramdisk driver and you can specify the number of bytes, for example:
fs0:\> mkramdisk.efi -s 2000 f
Device mapping table
f :BlockDevice - Alias (null)
VenMsg(06ED4DD0-FF78-11D3-BDC4-00A0C94053D1)
Done: RAM Disk [ f ] with size [ 2000MB ]
That creates a 2000MB ram disk called f. Nevertheless it appears to be some problem with the name cause I get:
fs0:\> map -r
Device mapping table
fs0 :BlockDevice - Alias f0agonennapphibbndlnmeaakamjeafdnb blk0
VenMsg(06ED4DD0-FF78-11D3-BDC4-00A0C94053D1)
fs1 :Removeable BlockDevice - Alias f40c0 blk1
Acpi(PNP0A03,0)/Pci(1D|7)/Usb(2, 0)
blk0 :BlockDevice - Alias f0agonennapphibbndlnmeaakamjeafdnb fs0
VenMsg(06ED4DD0-FF78-11D3-BDC4-00A0C94053D1)
blk1 :Removeable BlockDevice - Alias f40c0 fs1
Acpi(PNP0A03,0)/Pci(1D|7)/Usb(2, 0)
f0agonennapphibbndlnmeaakamjeafdnb :BlockDevice - Alias fs0 blk0
VenMsg(06ED4DD0-FF78-11D3-BDC4-00A0C94053D1)
f40c0 :Removeable BlockDevice - Alias fs1 blk1
Acpi(PNP0A03,0)/Pci(1D|7)/Usb(2, 0)
Where f0agonen... is a strange name.
There is a set of tools called EFI Disk utilities which I employed to format: http://www.intel.com/technology/efi/diskutil_overview.htm
First I tried using efifmt.efi directly on the created device, but it did not work:
fs1:\> EFIFMT.EFI blk0
EfiFmt Version 1.2. Based on EFI Version 2.10
IFSUTIL: Can't open drive. Status returned = C0000001.
Cannot determine file system of drive blk0.
Unable to determine file system type.
Cannot open volume for direct access.
What I do is first create a partition in the disk and then format it this way:
fs1:\> DISKPART.EFI
DiskPart Version 1.2. Based on EFI Version 2.10
DiskPart> list
### BlkSize BlkCount
--- ------- ----------------
0 200 100000
DiskPart> select 0
Selected Disk = 0
DiskPart> clean all
About to CLEAN (DESTROY) disk 0, are you SURE [y/n]?
CLEAN>> y
If you are REALLY SURE, type '$C'
CLEAN>> $C
DiskPart> new gpt
DiskPart> create name=partition type=efisys size=2000
DiskPart> exit
Exiting....
fs1:\> map -r
Device mapping table
fs0 :Removeable BlockDevice - Alias f40c0 blk0
Acpi(PNP0A03,0)/Pci(1D|7)/Usb(2, 0)
blk0 :Removeable BlockDevice - Alias f40c0 fs0
Acpi(PNP0A03,0)/Pci(1D|7)/Usb(2, 0)
blk1 :HardDisk - Alias (null)
VenMsg(06ED4DD0-FF78-11D3-BDC4-00A0C94053D1)/HD(Part1,Sig301D7800-1DD2-1000-9620-001A4B6FDBCA)
blk2 :BlockDevice - Alias (null)
VenMsg(06ED4DD0-FF78-11D3-BDC4-00A0C94053D1)
f40c0 :Removeable BlockDevice - Alias fs0 blk0
Shell> EFIFMT.EFI blk1 /FS:FAT32
EfiFmt Version 1.2. Based on EFI Version 2.10
WARNING, ALL DATA ON EFI DEVICE
blk1 WILL BE LOST!
Proceed with Format (Y/N)? y
Formatting 511M
Initializing the File Allocation Table (FAT)...
Volume label (11 characters, ENTER for none)? ramdisk
Format complete.
535769088 bytes total disk space.
535764992 bytes available on disk.
4096 bytes in each allocation unit.
130802 allocation units available on disk.
32 bits in each FAT entry.
Volume Serial Number is 000040B3-00004A89
Then everything goes fine I can read, write, mkdir etc.. on that volume and when using dblk the output seems correct:
Shell> dblk blk0
LBA 0000000000000000 Size 00000200 bytes BlkIo 01F14F18
00000000: EB 58 90 4D 53 44 4F 53-35 2E 30 00 02 08 26 00 *.X.MSDOS5.0...&.*
00000010: 02 00 00 00 00 F8 00 00-01 00 01 00 00 00 00 00 *................*
00000020: 00 00 79 00 31 1E 00 00-00 00 00 00 02 00 00 00 *..y.1...........*
00000030: 01 00 06 00 00 00 00 00-00 00 00 00 00 00 00 00 *................*
00000040: 00 00 29 27 7A 7B C4 4E-4F 20 4E 41 4D 45 20 20 *..)'z..NO NAME *
00000050: 20 20 46 41 54 33 32 20-20 20 33 C9 8E D1 BC F4 * FAT32 3.....*
00000060: 7B 8E C1 8E D9 BD 00 7C-88 4E 02 8A 56 40 B4 08 *.........N..V@..*
00000070: CD 13 73 05 B9 FF FF 8A-F1 66 0F B6 C6 40 66 0F *..s......f...@f<mailto:*..s......f...@f>.*
00000080: B6 D1 80 E2 3F F7 E2 86-CD C0 ED 06 41 66 0F B7 *....?.......Af..*
00000090: C9 66 F7 E1 66 89 46 F8-83 7E 16 00 75 38 83 7E *.f..f.F.....u8..*
000000A0: 2A 00 77 32 66 8B 46 1C-66 83 C0 0C BB 00 80 B9 **.w2f.F.f.......*
000000B0: 01 00 E8 2B 00 E9 48 03-A0 FA 7D B4 7D 8B F0 AC *...+..H.........*
000000C0: 84 C0 74 17 3C FF 74 09-B4 0E BB 07 00 CD 10 EB *..t.<.t.........*
000000D0: EE A0 FB 7D EB E5 A0 F9-7D EB E0 98 CD 16 CD 19 *................*
000000E0: 66 60 66 3B 46 F8 0F 82-4A 00 66 6A 00 66 50 06 *f`f;F...J.fj.fP.*
000000F0: 53 66 68 10 00 01 00 80-7E 02 00 0F 85 20 00 B4 *Sfh.......... ..*
00000100: 41 BB AA 55 8A 56 40 CD-13 0F 82 1C 00 81 FB 55 *A..U.V@........U<mailto:*A..U.V@........U>*
00000110: AA 0F 85 14 00 F6 C1 01-0F 84 0D 00 FE 46 02 B4 *.............F..*
00000120: 42 8A 56 40 8B F4 CD 13-B0 F9 66 58 66 58 66 58 *B.V@......fXfXfX<mailto:*B.V@......fXfXfX>*
00000130: 66 58 EB 2A 66 33 D2 66-0F B7 4E 18 66 F7 F1 FE *fX.*f3.f..N.f...*
00000140: C2 8A CA 66 8B D0 66 C1-EA 10 F7 76 1A 86 D6 8A *...f..f....v....*
00000150: 56 40 8A E8 C0 E4 06 0A-CC B8 01 02 CD 13 66 61 *V@............fa<mailto:*V@............fa>*
00000160: 0F 82 54 FF 81 C3 00 02-66 40 49 0F 85 71 FF C3 *..T.....f@I..q<mailto:*..T.....f@I..q>..*
00000170: 4E 54 4C 44 52 20 20 20-20 20 20 00 00 00 00 00 *NTLDR .....*
00000180: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 *................*
00000190: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 *................*
000001A0: 00 00 00 00 00 00 00 00-00 00 00 00 0D 0A 4E 54 *..............NT*
000001B0: 4C 44 52 20 69 73 20 6D-69 73 73 69 6E 67 FF 0D *LDR is missing..*
000001C0: 0A 44 69 73 6B 20 65 72-72 6F 72 FF 0D 0A 50 72 *.Disk error...Pr*
000001D0: 65 73 73 20 61 6E 79 20-6B 65 79 20 74 6F 20 72 *ess any key to r*
000001E0: 65 73 74 61 72 74 0D 0A-00 00 00 00 00 00 00 00 *estart..........*
000001F0: 00 00 00 00 00 00 00 00-00 AC BF CC 00 00 55 AA *..............U.*
But there is something that I do not understand. Why if I am reserving 2000MB when I format it it only recognizes 511MB?
Formatting 511M
I tried several times but I only got it to recognize the 511MB.
Thank you very much for your help again :)
BR
Daniel
________________________________
From: Andrew Fish [mailto:af...@ap...]
Sent: den 8 juli 2011 19:08
To: edk...@li...
Cc: efi...@li...
Subject: Re: [edk2] Memory mapped file system on RAM used by EDK shell
Daniel,
I think there is a RAM Disk driver in the toolkit.... It produces the Block IO protocol. The only problem is you have to format the Block IO partition to put a file system on it. There is an EFI application to do that. If the Block IO protocol abstracts blocks that contain a FAT file system then when you connect that handle the file system driver will bind and you will get a Simple File System Protocol that would show up at the shell prompt.
It would be possible to write a Simple File System Driver that just treated files as linked lists. I've never seen this done, but it is quite possible.
These two chunks work together to make Simple File System on top of ANSI C APIs:
https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2/EmulatorPkg/EmuSimpleFileSystemDxe/EmuSimpleFileSystem.c
https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2/EmulatorPkg/Unix/Host/PosixFileSystem.c
Maybe this would be a good GSOC project at some point.
Andrew Fish
On Jul 8, 2011, at 9:28 AM, Daniel Moral wrote:
Hi!
I want to build a memory mapped file system in order to use it with EDK1 Shell. What I want is to create a temporal file system using the RAM memory
of my board in order to store there files downloaded from a tftp server without needing an external flash memory. Therefore I could use the files
I download in other applications.
I am a bit lost on how I could do this. Would it be possible to create a virtual drive using the RAM memory and "trick" the shell so it thinks it is
just another volume? Or should I think in other possibilities?
Thank you very much.
BR
Daniel
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2_______________________________________________
edk2-devel mailing list
edk...@li...<mailto:edk...@li...>
https://lists.sourceforge.net/lists/listinfo/edk2-devel
|
|
From: Daniel M. <dan...@er...> - 2011-07-08 16:29:06
|
Hi! I want to build a memory mapped file system in order to use it with EDK1 Shell. What I want is to create a temporal file system using the RAM memory of my board in order to store there files downloaded from a tftp server without needing an external flash memory. Therefore I could use the files I download in other applications. I am a bit lost on how I could do this. Would it be possible to create a virtual drive using the RAM memory and "trick" the shell so it thinks it is just another volume? Or should I think in other possibilities? Thank you very much. BR Daniel |
|
From: Daniel M. <dan...@er...> - 2011-07-08 13:45:02
|
Hi!
Although I was unable to build the Nshell.efi application which I needed to get the DHCP client on the EFI Toolkit to work I found it in the Toolkit binaries and it seems to work but I do not get the expected results, here is what I do:
load tcpipv4.efi
load dhclient.efi
And the output is:
fs0:\Toolkit> load DHCLIENT.EFI
\dcsIlpjSy.nsh> echo -off
'\etc\dhclient-script.nsh' is not recognized as an internal or external command, operable program or batch file
\dcsluuRyX.nsh> echo -off
'\etc\dhclient-script.nsh' is not recognized as an internal or external command, operable program or batch file
Then it hangs
What am I doing wrong?
Then I tried another thing: Using ifconfig to set the address and then modify it with DHCP, it is a bit stupid but I wanted to know if I could get DHCP to work.
load tcpipv4.efi
ifconfig.efi sni0 inet 192.168.1.4 netmask 255.255.255.0 up
route.efi add default 192.168.1.4
load dhclient.efi
In this case the output was:
fs0:\Toolkit> load DHCLIENT.EFI
\dcsMapVJM.nsh> echo -off
'\etc\dhclient-script.nsh' is not recognized as an internal or external command, operable program or batch file
\dcsTBCsCT.nsh> echo -off
'\etc\dhclient-script.nsh' is not recognized as an internal or external command, operable program or batch file
Listening on Socket/sni0
Sending on Socket/sni0
DHCPDISCOVER on sni0 to 255.255.255.255 port 67 interval 4
DHCPOFFER from 192.168.1.1
\dcsKXGmJp.nsh> echo -off
'\etc\dhclient-script.nsh' is not recognized as an internal or external command, operable program or batch file
\dcsmZfGuN.nsh> echo -off
'\etc\dhclient-script.nsh' is not recognized as an internal or external command, operable program or batch file
DHCPREQUEST on sni0 to 255.255.255.255 port 67
DHCPACK from 192.168.1.1
\dcsVwhxSU.nsh> echo -off
'\etc\dhclient-script.nsh' is not recognized as an internal or external command, operable program or batch file
bound to 192.168.1.6 -- renewal in 1800 seconds.
load: Image fs0:\ftpthesis\Toolkit\DHCLIENT.EFI loaded at 27A1000 - Success
And I checked it using DHCP and it worked, nevertheless it did not change the ifconfig IP:
fs0:\Toolkit> IFCONFIG.EFI sni0
sni0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 192.168.1.4 netmask 0xffffff00 broadcast 192.168.1.255
ether 00:1a:4b:6f:db:ca
So I do not really know what is the problem. I have been reading the related EFI Toolkit documentation but I get nothing.
It is only a DHCP problem because I got an FTP client working and it also pings ok.
Thank you very much.
|
|
From: Daniel M. <dan...@er...> - 2011-07-08 13:38:33
|
Hi! I am having some trouble to build the newshell (Nshell.efi) as an external application. I need it so I can use the DHCP client utility present on the EDK Toolkit. When I try to build I get this error: GuidLib.lib /ENTRY:InitializeShell C:\EDK\Sample\Platform\X64\Build\X64\Other\Maintained\Applic ation\Shell\newshell\NShellLocal.lib /OUT:C:\EDK\Sample\Platform\X64\Build\X64\NShell.dll /MAP:C :\EDK\Sample\Platform\X64\Build\X64\NShell.map /PDB:C:\EDK\Sample\Platform\X64\Build\X64\NShell .pdb NShellLocal.lib(init.obj) : error LNK2001: unresolved external symbol ShellStrings NShellLocal.lib(init.obj) : error LNK2019: unresolved external symbol InitializeShellEnvironment referenced in function _EnableShellEnv NShellLocal.lib(init.obj) : error LNK2019: unresolved external symbol UnInstallShellEnvironment referenced in function _CleanUpOnExit C:\EDK\Sample\Platform\X64\Build\X64\NShell.dll : fatal error LNK1120: 3 unresolved externals NMAKE : fatal error U1077: 'C:\WINDDK\3790.1830\bin\win64\x86\amd64\link' : return code '0x460' Stop. ProcessDsc : error E0000: Multi-thread build components 0 failure NMAKE : fatal error U1077: 'C:\EDK\Sample\Platform\X64\Build\Tools\ProcessDsc' : return code '0x 2' Stop. And I do not really know what to do because that symbols are present in the source files. Any ideas on how could I solve this? Thank you very much. |
|
From: Daniel J. G. M. <na...@gm...> - 2011-07-05 16:37:38
|
Hi! I am trying to build an TFTP client application using the MTFTP4 driver on EDK 1. I am getting the configuration parameters for my client using DHCP (through MTFTP4 driver). My question is: how can I select the interface on which I want the TFTP client to work? My problem is that if I connect my client to the server on the Ethernet0 interface everything goes fine. But if I connect it in for example Ethernet1, it does not work, it still tries to configure Ethernet0 (which cannot be configured because in this case the server is connected to Ethernet1). How can I tell the driver to work on a different interface? Thank you very much. BR Daniel |
|
From: Vijay M. <vij...@gm...> - 2011-06-20 23:34:32
|
Hi All, I am new to EDK and just started learning about it. I was intrigued by python interpreter in the EFI toolkit and wanted to explore more options available in the interpreter as that provided more scripting options than the shell. However, I noted that the python available is dated and not complete. Could anyone point me or help me with these queries I have: 1. Where can i find the proper Build instructions for python on EDK. 2. How to go about porting python 2.7.1. Are there any resources that I can read, learn about it more et al 3. Is it possible to completely port 2.7.1 python? I know there are some shared libraries in python and I am not really aware if the EDK platform is equipped to support it as the current version also lacks these modules. It would be great if someone helped me with these queries and point me in the right direction. Thanks Vijay |
|
From: t k <kar...@gm...> - 2011-05-04 19:42:34
|
Hi Jordon, Thanks for the reply. I am actually using a back ported CryptoLib to EDK1.06. So I am using EdkIIGlueBaseMemoryLib. For the gRT error, I was able to get rid of it after including EdkIIGlueUefiRuntimeServicesTableLib in my inf file Thanks On Tue, May 3, 2011 at 7:09 PM, Jordan Justen <jlj...@gm...> wrote: > (Adding edk2-devel.) > > On Tue, May 3, 2011 at 09:41, t k <kar...@gm...> wrote: > > > >> I am trying to build a driver that makes use of the CryptoLib (from UDK > >> 2010). But I am seeing the following error messages: > >> > >> LINK64 : warning LNK4108: /ALIGN specified without /DRIVER; image may > not > >> run > >> LINK64 : warning LNK4001: no object files specified; libraries used > >> BaseCryptLib.lib(sha256.obj) : MSIL .netmodule or module compiled with > /GL > >> found; restarting link with /LTCG; add /LTCG to the link command line to > >> improve > >> linker performance > >> LINK64 : warning LNK4108: /ALIGN specified without /DRIVER; image may > not > >> run > >> LINK64 : warning LNK4001: no object files specified; libraries used > >> BaseCryptLib.lib(sha256.obj) : error LNK2001: unresolved external symbol > >> CopyMem > >> BaseCryptLib.lib(sha256.obj) : error LNK2001: unresolved external symbol > >> SetMem > >> BaseCryptLib.lib(rsa_oaep.obj) : error LNK2001: unresolved external > symbol > >> CompareMem > >> BaseCryptLib.lib(TimerWrapper.obj) : error LNK2001: unresolved external > >> symbol gRT > > Hmm, CryptoPkg/Library/BaseCryptLib/BaseCryptLib.inf lists > BaseMemoryLib, which should take care of the *Mem externals. What > does your dsc list for BaseMemoryLib? > > It looks like UefiRuntimeServicesTableLib should be added for the gRT > usage in SysCall/TimerWrapper.c. > > -Jordan > > > ------------------------------------------------------------------------------ > WhatsUp Gold - Download Free Network Management Software > The most intuitive, comprehensive, and cost-effective network > management toolset available today. Delivers lowest initial > acquisition cost and overall TCO of any competing solution. > http://p.sf.net/sfu/whatsupgold-sd > _______________________________________________ > efidevkit-devel mailing list > efi...@li... > https://lists.sourceforge.net/lists/listinfo/efidevkit-devel > |
|
From: Jordan J. <jlj...@gm...> - 2011-05-04 00:09:44
|
(Adding edk2-devel.) On Tue, May 3, 2011 at 09:41, t k <kar...@gm...> wrote: > >> I am trying to build a driver that makes use of the CryptoLib (from UDK >> 2010). But I am seeing the following error messages: >> >> LINK64 : warning LNK4108: /ALIGN specified without /DRIVER; image may not >> run >> LINK64 : warning LNK4001: no object files specified; libraries used >> BaseCryptLib.lib(sha256.obj) : MSIL .netmodule or module compiled with /GL >> found; restarting link with /LTCG; add /LTCG to the link command line to >> improve >> linker performance >> LINK64 : warning LNK4108: /ALIGN specified without /DRIVER; image may not >> run >> LINK64 : warning LNK4001: no object files specified; libraries used >> BaseCryptLib.lib(sha256.obj) : error LNK2001: unresolved external symbol >> CopyMem >> BaseCryptLib.lib(sha256.obj) : error LNK2001: unresolved external symbol >> SetMem >> BaseCryptLib.lib(rsa_oaep.obj) : error LNK2001: unresolved external symbol >> CompareMem >> BaseCryptLib.lib(TimerWrapper.obj) : error LNK2001: unresolved external >> symbol gRT Hmm, CryptoPkg/Library/BaseCryptLib/BaseCryptLib.inf lists BaseMemoryLib, which should take care of the *Mem externals. What does your dsc list for BaseMemoryLib? It looks like UefiRuntimeServicesTableLib should be added for the gRT usage in SysCall/TimerWrapper.c. -Jordan |
|
From: t k <kar...@gm...> - 2011-05-03 16:41:39
|
> I am trying to build a driver that makes use of the CryptoLib (from UDK > 2010). But I am seeing the following error messages: > > LINK64 : warning LNK4108: /ALIGN specified without /DRIVER; image may not > run > LINK64 : warning LNK4001: no object files specified; libraries used > BaseCryptLib.lib(sha256.obj) : MSIL .netmodule or module compiled with /GL > found; restarting link with /LTCG; add /LTCG to the link command line to > improve > linker performance > LINK64 : warning LNK4108: /ALIGN specified without /DRIVER; image may not > run > LINK64 : warning LNK4001: no object files specified; libraries used > BaseCryptLib.lib(sha256.obj) : error LNK2001: unresolved external symbol > CopyMem > BaseCryptLib.lib(sha256.obj) : error LNK2001: unresolved external symbol > SetMem > BaseCryptLib.lib(rsa_oaep.obj) : error LNK2001: unresolved external symbol > CompareMem > BaseCryptLib.lib(TimerWrapper.obj) : error LNK2001: unresolved external > symbol gRT > DriverRuntimeDxe.dll : fatal error LNK1120: 4 unresolved externals > NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio > 9.0\VC\bin\x86_amd64\link64.EXE"' : return code '0x460' > Stop. > ProcessDsc : error E0000: Multi-thread build libraries failure > NMAKE : fatal error U1077: '\Tools\Build\ProcessDsc.EXE' : return code > '0x2' > Stop. > > I checked my code, but couldn't find any possible unresolved symbols. My > code has the <OpenSslSupport.h> header file. I also modified the > 'BaseMemoryLib.h' to include 'EdkIIGlueBaseMemoryLib.h'. > > I have come across a previous posting ( > http://feishare.com/efimail/messages/20090320-0913-Re__EDK_DEV__Building_module_for_X64_generates_unresolved_references_to_memset_and_memcpy-_Gao__Liming_.html) > with similar issue, but it was memcpy (not CopyMem) that the compiler uses > to optimize the code. So I am exactly sure what am I missing here. > > Any ideas? > > Thanks > |
|
From: jean-francois s. <jf...@th...> - 2011-02-07 21:58:35
|
Hi, First of all i hope this is the right place for asking this: i'd like to compile a new shell with a higher level support. ideally i would like to include commands like "bcfg". But i am not sure where to specify the level support, as explained below: Different Levels Of Shell Support • Different levels of support for different usage scenarios and space constraints: – Level 0: No Command-line Interface (CLI). No shell commands. Only shell API. – Level 1: Adds basic scripting support – Level 2: Adds basic commands (cd, cp, mv) – Level 3: Adds interactive CLI • Shell support level can be detected using an environment variable. • Beyond level 3, additional command “profiles” are defined for debug, networking and driver support. thx a lot -- _______________________________________ jean-francois simon - www.themis.com ph: +1 (925)271-7716 |
|
From: Jordan J. <jlj...@gm...> - 2010-11-02 16:04:54
|
On Mon, Nov 1, 2010 at 22:39, Rodrigo Lemes dos Santos <Rod...@at...> wrote: > My question is: "How can vmware and these guys run's the original Apple's > boot.efi?" It seems like it would be fairly easy to modify the DXE Core to support loading these image types. But, I don't think you will see that done in edk/edk2 unless the image format becomes part of the UEFI specification. Otherwise it would create some functionality that you could not depend on having available on all UEFI systems. -Jordan |
|
From: Rodrigo L. d. S. <Rod...@at...> - 2010-11-02 05:40:00
|
Yes, I know! I can edit boot.efi, with a binary editor using assembly (efi applications are pe dlls :-P)., but I don't know ANYTHING about asm/hexadecimal programming. http://x86asm.net/articles/uefi-programming-first-steps/ My question is: "How can vmware and these guys run's the original Apple's boot.efi?" I think something like this in their DUET code: "if shows Apple headers, execute like x86 architecture." But is'nt only this, I can't start graphic refit too! Well, is too late! 03:38 in here (Brazil). I need rest, tomorrow I'll make some tests, thanx 4 all! Att. Rodrigo Lemes dos Santos Ramais: 48259 / 59455 / 59534 Sup. Tiago Faria de Oliveira Atento do Brasil |Gerenciamento Estratégico e Desenvolvimento Operacional ________________________________ De: Adhyas Avasthi [mailto:ad...@gm...] Enviada: seg 1/11/2010 16:58 Para: efi...@li... Assunto: Re: [edk] RES: RES: Mac OS X Boot.efi, what's up? reverse engineering :-) Apple put's its own headers (they are simple enough to reverse engineer). I cannot disclose the details, even though I don't work for VMware anymore, but the header has simple information like architecture for the target and the binary etc. Rest of the image is EFI after you strip the header apart. Note that Apple has a single loader image and both 32/64 bit images concatenated within it. - Adhyas On Mon, Nov 1, 2010 at 9:50 PM, Rodrigo Lemes dos Santos <Rod...@at...> wrote: Well, this is the problem, the headers... How VMWare put this compatibility in VMware Fusion? And iPhoneTom with XPC_UEFI and OS_Ninja with his duet? http://osx86.co/f36/new-duet-based-efi-bootloader-t6383/ http://www.youtube.com/watch?v=yCczLe4qYsI http://media.photobucket.com/image/vmware%20fusion%20efi/saivert/th_vmware-efi-bootscreen.png Well, tomorrow I'will make some tests... Att. Rodrigo Lemes dos Santos Ramais: 48259 / 59455 / 59534 Sup. Tiago Faria de Oliveira Atento do Brasil |Gerenciamento Estratégico e Desenvolvimento Operacional ________________________________ De: Jordan Justen [mailto:jlj...@gm...] Enviada: seg 1/11/2010 08:35 Para: efi...@li... Assunto: Re: [edk] RES: Mac OS X Boot.efi, what's up? On Sun, Oct 31, 2010 at 07:51, Rodrigo Lemes dos Santos <Rod...@at...> wrote: > No... > Old rEFIt versions (text mode) work fine. I downloaded refit.efi (0.14), and I saw this: $ file refit.efi refit.efi: Universal EFI binary with 2 architectures, i386, x86_64 $ objdump --file-headers refit.efi objdump: refit.efi: File format not recognized As opposed to this for, for the X64 Full Shell: $ file EdkShellBinPkg/FullShell/X64/Shell_Full.efi EdkShellBinPkg/FullShell/X64/Shell_Full.efi: MS-DOS executable $ objdump --file-header EdkShellBinPkg/FullShell/X64/Shell_Full.efi EdkShellBinPkg/FullShell/X64/Shell_Full.efi: file format pei-x86-64 architecture: i386:x86-64, flags 0x0000012f: HAS_RELOC, EXEC_P, HAS_LINENO, HAS_DEBUG, HAS_LOCALS, D_PAGED start address 0x00000000000656c0 This clearly shows that refit.efi is not a UEFI compatible executable. It is using Apple's 'Universal' efi binary format. -Jordan ------------------------------------------------------------------------------ Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev _______________________________________________ efidevkit-devel mailing list efi...@li... https://lists.sourceforge.net/lists/listinfo/efidevkit-devel ------------------------------------------------------------------------------ Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev _______________________________________________ efidevkit-devel mailing list efi...@li... https://lists.sourceforge.net/lists/listinfo/efidevkit-devel -- Adhyas ******************************************************************** Two types have compatible type if their types are the same. - ANSI C Standard, 3.1.2.6. ******************************************************************** |
|
From: Adhyas A. <ad...@gm...> - 2010-11-02 04:58:38
|
reverse engineering :-) Apple put's its own headers (they are simple enough to reverse engineer). I cannot disclose the details, even though I don't work for VMware anymore, but the header has simple information like architecture for the target and the binary etc. Rest of the image is EFI after you strip the header apart. Note that Apple has a single loader image and both 32/64 bit images concatenated within it. - Adhyas On Mon, Nov 1, 2010 at 9:50 PM, Rodrigo Lemes dos Santos < Rod...@at...> wrote: > Well, this is the problem, the headers... > How VMWare put this compatibility in VMware Fusion? And iPhoneTom with > XPC_UEFI and OS_Ninja with his duet? > http://osx86.co/f36/new-duet-based-efi-bootloader-t6383/ > > http://www.youtube.com/watch?v=yCczLe4qYsI > > > http://media.photobucket.com/image/vmware%20fusion%20efi/saivert/th_vmware-efi-bootscreen.png > > Well, tomorrow I'will make some tests... > > Att. > *Rodrigo Lemes dos Santos* > Ramais: 48259 / 59455 / 59534 > Sup. Tiago Faria de Oliveira > *Atento do Brasil |Gerenciamento Estratégico e Desenvolvimento Operacional > * > > ** > > ------------------------------ > *De:* Jordan Justen [mailto:jlj...@gm...] > *Enviada:* seg 1/11/2010 08:35 > *Para:* efi...@li... > *Assunto:* Re: [edk] RES: Mac OS X Boot.efi, what's up? > > On Sun, Oct 31, 2010 at 07:51, Rodrigo Lemes dos Santos > <Rod...@at...> wrote: > > No... > > Old rEFIt versions (text mode) work fine. > > I downloaded refit.efi (0.14), and I saw this: > > $ file refit.efi > refit.efi: Universal EFI binary with 2 architectures, i386, x86_64 > > $ objdump --file-headers refit.efi > objdump: refit.efi: File format not recognized > > As opposed to this for, for the X64 Full Shell: > > $ file EdkShellBinPkg/FullShell/X64/Shell_Full.efi > EdkShellBinPkg/FullShell/X64/Shell_Full.efi: MS-DOS executable > > $ objdump --file-header EdkShellBinPkg/FullShell/X64/Shell_Full.efi > EdkShellBinPkg/FullShell/X64/Shell_Full.efi: file format pei-x86-64 > architecture: i386:x86-64, flags 0x0000012f: > HAS_RELOC, EXEC_P, HAS_LINENO, HAS_DEBUG, HAS_LOCALS, D_PAGED > start address 0x00000000000656c0 > > This clearly shows that refit.efi is not a UEFI compatible executable. > It is using Apple's 'Universal' efi binary format. > > -Jordan > > > ------------------------------------------------------------------------------ > Nokia and AT&T present the 2010 Calling All Innovators-North America > contest > Create new apps & games for the Nokia N8 for consumers in U.S. and Canada > $10 million total in prizes - $4M cash, 500 devices, nearly $6M in > marketing > Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store > http://p.sf.net/sfu/nokia-dev2dev > _______________________________________________ > efidevkit-devel mailing list > efi...@li... > https://lists.sourceforge.net/lists/listinfo/efidevkit-devel > > > ------------------------------------------------------------------------------ > Nokia and AT&T present the 2010 Calling All Innovators-North America > contest > Create new apps & games for the Nokia N8 for consumers in U.S. and Canada > $10 million total in prizes - $4M cash, 500 devices, nearly $6M in > marketing > Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store > http://p.sf.net/sfu/nokia-dev2dev > _______________________________________________ > efidevkit-devel mailing list > efi...@li... > https://lists.sourceforge.net/lists/listinfo/efidevkit-devel > > -- Adhyas ******************************************************************** Two types have compatible type if their types are the same. — ANSI C Standard, 3.1.2.6. ******************************************************************** |
|
From: Rodrigo L. d. S. <Rod...@at...> - 2010-11-02 04:51:02
|
Well, this is the problem, the headers... How VMWare put this compatibility in VMware Fusion? And iPhoneTom with XPC_UEFI and OS_Ninja with his duet? http://osx86.co/f36/new-duet-based-efi-bootloader-t6383/ http://www.youtube.com/watch?v=yCczLe4qYsI http://media.photobucket.com/image/vmware%20fusion%20efi/saivert/th_vmware-efi-bootscreen.png Well, tomorrow I'will make some tests... Att. Rodrigo Lemes dos Santos Ramais: 48259 / 59455 / 59534 Sup. Tiago Faria de Oliveira Atento do Brasil |Gerenciamento Estratégico e Desenvolvimento Operacional ________________________________ De: Jordan Justen [mailto:jlj...@gm...] Enviada: seg 1/11/2010 08:35 Para: efi...@li... Assunto: Re: [edk] RES: Mac OS X Boot.efi, what's up? On Sun, Oct 31, 2010 at 07:51, Rodrigo Lemes dos Santos <Rod...@at...> wrote: > No... > Old rEFIt versions (text mode) work fine. I downloaded refit.efi (0.14), and I saw this: $ file refit.efi refit.efi: Universal EFI binary with 2 architectures, i386, x86_64 $ objdump --file-headers refit.efi objdump: refit.efi: File format not recognized As opposed to this for, for the X64 Full Shell: $ file EdkShellBinPkg/FullShell/X64/Shell_Full.efi EdkShellBinPkg/FullShell/X64/Shell_Full.efi: MS-DOS executable $ objdump --file-header EdkShellBinPkg/FullShell/X64/Shell_Full.efi EdkShellBinPkg/FullShell/X64/Shell_Full.efi: file format pei-x86-64 architecture: i386:x86-64, flags 0x0000012f: HAS_RELOC, EXEC_P, HAS_LINENO, HAS_DEBUG, HAS_LOCALS, D_PAGED start address 0x00000000000656c0 This clearly shows that refit.efi is not a UEFI compatible executable. It is using Apple's 'Universal' efi binary format. -Jordan ------------------------------------------------------------------------------ Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev _______________________________________________ efidevkit-devel mailing list efi...@li... https://lists.sourceforge.net/lists/listinfo/efidevkit-devel |
|
From: Jordan J. <jlj...@gm...> - 2010-11-01 20:35:41
|
On Sun, Oct 31, 2010 at 07:51, Rodrigo Lemes dos Santos <Rod...@at...> wrote: > No... > Old rEFIt versions (text mode) work fine. I downloaded refit.efi (0.14), and I saw this: $ file refit.efi refit.efi: Universal EFI binary with 2 architectures, i386, x86_64 $ objdump --file-headers refit.efi objdump: refit.efi: File format not recognized As opposed to this for, for the X64 Full Shell: $ file EdkShellBinPkg/FullShell/X64/Shell_Full.efi EdkShellBinPkg/FullShell/X64/Shell_Full.efi: MS-DOS executable $ objdump --file-header EdkShellBinPkg/FullShell/X64/Shell_Full.efi EdkShellBinPkg/FullShell/X64/Shell_Full.efi: file format pei-x86-64 architecture: i386:x86-64, flags 0x0000012f: HAS_RELOC, EXEC_P, HAS_LINENO, HAS_DEBUG, HAS_LOCALS, D_PAGED start address 0x00000000000656c0 This clearly shows that refit.efi is not a UEFI compatible executable. It is using Apple's 'Universal' efi binary format. -Jordan |
|
From: Rodrigo L. d. S. <Rod...@at...> - 2010-10-31 15:01:49
|
No... Old rEFIt versions (text mode) work fine. Here the original Apple's boot.efi: www.hackosx.com.br/boot.efi Can somebody test it? Att. Rodrigo Lemes dos Santos Ramais: 48259 / 59455 / 59534 Sup. Tiago Faria de Oliveira Atento do Brasil |Gerenciamento Estratégico e Desenvolvimento Operacional -----Mensagem original----- De: Jordan Justen [mailto:jlj...@gm...] Enviada: sáb 30/10/2010 17:35 Para: efi...@li... Assunto: Re: [edk] Mac OS X Boot.efi, what's up? On Sat, Oct 30, 2010 at 15:55, Rodrigo Lemes dos Santos <Rod...@at...> wrote: > Well, my duet has an "issue" with Apple's boot.efi. > > I can boot 10.4 boot.efi (it crashes later, LoL), but, I can't do the same > with 10.5/.6 boot.efi. > > The same happens with the graphical rEFIt (refit.efi). > > I'm using EDK 1.x. > > The error says the executable is not valid. > Sounds like you may be encountering these UEFI incompatible image types associated with OS X. http://refit.sourceforge.net/info/fat_binary.html -Jordan ------------------------------------------------------------------------------ Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev _______________________________________________ efidevkit-devel mailing list efi...@li... https://lists.sourceforge.net/lists/listinfo/efidevkit-devel |
|
From: Jordan J. <jlj...@gm...> - 2010-10-31 05:35:39
|
On Sat, Oct 30, 2010 at 15:55, Rodrigo Lemes dos Santos <Rod...@at...> wrote: > Well, my duet has an “issue” with Apple’s boot.efi. > > I can boot 10.4 boot.efi (it crashes later, LoL), but, I can’t do the same > with 10.5/.6 boot.efi. > > The same happens with the graphical rEFIt (refit.efi). > > I’m using EDK 1.x. > > The error says the executable is not valid. > Sounds like you may be encountering these UEFI incompatible image types associated with OS X. http://refit.sourceforge.net/info/fat_binary.html -Jordan |
3 messages has been excluded from this view by a project administrator.
