You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(6) |
Sep
|
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(7) |
Sep
|
Oct
|
Nov
|
Dec
|
2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2007 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
(7) |
Jul
(12) |
Aug
(9) |
Sep
(1) |
Oct
(5) |
Nov
(1) |
Dec
|
2008 |
Jan
|
Feb
(14) |
Mar
(3) |
Apr
(10) |
May
(14) |
Jun
(54) |
Jul
(14) |
Aug
|
Sep
|
Oct
(4) |
Nov
(3) |
Dec
(11) |
2009 |
Jan
(2) |
Feb
(2) |
Mar
(2) |
Apr
(4) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2010 |
Jan
|
Feb
|
Mar
(3) |
Apr
(9) |
May
(2) |
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2011 |
Jan
(4) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(7) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
2012 |
Jan
(3) |
Feb
|
Mar
(1) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2013 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(4) |
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
|
From: <nar...@gm...> - 2014-11-07 10:18:37
|
Hi, nar...@gm... wants to follow you. ****** Is nar...@gm... you friend? ****** If Yes please follow the link below: http://invites.info-emailer.com/signup_e.html?fullname=&email=eli...@li...&invitername=nareshgbhat&inviterid=33954123&userid=0&token=0&emailmasterid=50c46100-3023-44da-ac29-f5eba4424d07&from=nar...@gm...&src=txt_yes If No please follow the link below: http://invites.info-emailer.com/signup_e.html?fullname=&email=eli...@li...&invitername=nareshgbhat&inviterid=33954123&userid=0&token=0&emailmasterid=50c46100-3023-44da-ac29-f5eba4424d07&from=nar...@gm...&src=txt_no Follow the link below to remove yourself from all such emails http://invites.info-emailer.com/uns_inviter.jsp?email=eli...@li...&iid=50c46100-3023-44da-ac29-f5eba4424d07&from=nar...@gm... |
From: Keshav P. A. <the...@gm...> - 2013-10-16 03:19:31
|
On 16 October 2013 01:57, jfly <fle...@us...> wrote: > Hi Keshav, > > thanks for your note. > >Hi, > > Can you guys please switch from CVS to GIT (or another DVCS) so > >that it is easy for users to track development of ELILO. Currently it > >is difficult to track using CVS. Thanks in advance. > GIT is great (and intended) for really large projects with 100's of > contributors. As elilo is neither of those, and that status wont change, > I dont see the benefits warrant the time and effort. There is nothing > that prevents you from pulling the source into your own local git > repository and working on it within git and sending patches for > consideration and elilo will stay on sourceforge. That being said, I > hear you, I work with git for the kernel and Ive thought about switching > this source over to git now and then. Git is superior to CVS so I'll > consider it again. you are the first to raise a complaint. no really. This is the exact same reply you gave at http://sourceforge.net/mailarchive/message.php?msg_id=26920372 . Just because git was designed with Linux Kernel in mind doesn't mean it shouldn't be used for smaller projects. There are users in github who use git for managing 10-line scripts and git is working perfectly fine without any overhead in such cases. It is difficult to visualize commit log and diff using CVS but that is a breeze with git. If you are referring to "git cvsimport", it is still not a proper solution to converting to GIT server-side. Using GIT to manage development is not going to any more difficult for you compared to using CVS, but using CVS is definitely difficult for downstream users. I am just asking you to host the ELILO code in GIT in the sourceforge project instead of CVS. This should be a one-time change and I suppose sourceforge itself will take care of the conversion. I am not bothered about lack of new development in elilo. My interest is academic and ease of accessing the code. I want to study the code commit-wise and per-file diffs to understand how the code evolves. This is much easier in GIT and much difficult in CVS. Even if you completely stop updating elilo in the future, just leave the code in GIT so that anyone who wants to restart development can do so easily. If you definitely don't want to switch to any distributed VCS (can't think of any reason why), at least switch to SVN. Using SVN is still easier than CVS. At this point, when many projects are moving from SVN to GIT/HG/BZR etc., I don't understand why you are refusing to migrate from CVS! >Off-note: Is ELILO still under active development? Because there seems > >to be no update after v3.16 which was released in March 2013 (8 months > >ago). Even if it is no longer actively maintained, providing the > >sources via GIT will allow contributors to fork the code and maintain > >it in github/gitorious/bitbucket etc.. > Elilo is still actively maintained solely by me but no longer in active > development. Elilo was designed in the early 2000's for EFI and Itanium, > thats why it exists. As neither of those are very relevant any more It > is legacy code at the end of its life cycle naturally. Im really not > accepting new features or new feature requests. New releases are for > major bug fixes for people that just cant live without elilo and > thats about it and I have no bugs waiting to release. Even though Itanium may no longer be relevant, EFI itself is very much in use today and complete migration to (U)EFI is happening, so ELILO is very much relevant in that regard. > > New bootloader efforts and contributions should rightfully go to Grub2. > It is in active development, has many active contributors and is > accepting new features and it supports UEFI and secure boot now and is > finally fairly well positioned to fulfill its original intention of > being the "GRand Unified Bootloader". It could be so if it supported > network booting and really if elilo didnt exist anymore Im sure that > somebody wouldve contributed the feature by now, most likely from a > cloud team. > > I agree that GRUB2 (or Gummiboot/rEFInd/Syslinux etc.) can be used instead of ELILO, but many people do not like the all-powerful GRUB and like some simplicity and ELILO with its small codebase and small size fits the bill. With Best Regards, Keshav |
From: jfly <fle...@us...> - 2013-10-15 21:28:30
|
Hi Keshav, thanks for your note. >Hi, > Can you guys please switch from CVS to GIT (or another DVCS) so >that it is easy for users to track development of ELILO. Currently it >is difficult to track using CVS. Thanks in advance. GIT is great (and intended) for really large projects with 100's of contributors. As elilo is neither of those, and that status wont change, I dont see the benefits warrant the time and effort. There is nothing that prevents you from pulling the source into your own local git repository and working on it within git and sending patches for consideration and elilo will stay on sourceforge. That being said, I hear you, I work with git for the kernel and Ive thought about switching this source over to git now and then. Git is superior to CVS so I'll consider it again. you are the first to raise a complaint. no really. >Off-note: Is ELILO still under active development? Because there seems >to be no update after v3.16 which was released in March 2013 (8 months >ago). Even if it is no longer actively maintained, providing the >sources via GIT will allow contributors to fork the code and maintain >it in github/gitorious/bitbucket etc.. Elilo is still actively maintained solely by me but no longer in active development. Elilo was designed in the early 2000's for EFI and Itanium, thats why it exists. As neither of those are very relevant any more It is legacy code at the end of its life cycle naturally. Im really not accepting new features or new feature requests. New releases are for major bug fixes for people that just cant live without elilo and thats about it and I have no bugs waiting to release. New bootloader efforts and contributions should rightfully go to Grub2. It is in active development, has many active contributors and is accepting new features and it supports UEFI and secure boot now and is finally fairly well positioned to fulfill its original intention of being the "GRand Unified Bootloader". It could be so if it supported network booting and really if elilo didnt exist anymore Im sure that somebody wouldve contributed the feature by now, most likely from a cloud team. >With Best Regards, >Keshav And to you as well, Jason |
From: Keshav P. A. <the...@gm...> - 2013-10-15 19:24:01
|
Hi, Can you guys please switch from CVS to GIT (or another DVCS) so that it is easy for users to track development of ELILO. Currently it is difficult to track using CVS. Thanks in advance. Off-note: Is ELILO still under active development? Because there seems to be no update after v3.16 which was released in March 2013 (8 months ago). Even if it is no longer actively maintained, providing the sources via GIT will allow contributors to fork the code and maintain it in github/gitorious/bitbucket etc.. With Best Regards, Keshav |
From: jfly <fle...@us...> - 2013-04-04 23:10:47
|
Elilo 3-16 Released 3/29/13 QUICK CHANGE SUMMARY ==================== * Adds native x86x crossbuild functionality build 32bit or 64bit versions from either environment via make ARCH=ia32|x86_64 (the ARCH IS case sensitive). make by itself will default to the native host arch. * Add console reset call during initialization. thanks A. Steinmetz * simplify output of no GOP warning text so it no longer looks like an error. * MAJOR: Fixed Fault crash when EFI memory map changes from under elilo. (from an outside interrupt in this case). When the EFI Memory map changes after elilo has already built boot params to pass to the kernel the EFI call to ExitBootSvcs just prior to boot will fail because elilo has the old map key. This is valid EFI behavior, elilo retries to pick up the new memory map and key but had already freed the start params portion of boot params resulting in a NULL DEREF crash reset once it hands the now bogus boot params to the kernel on the 2nd successful call to exit efi and boot. Thanks to Jerry Hoemann @ HP for reporting this bug. * minor bugfix, fixed -m option broken. thanks Allan-lsk. BUILD NOTES ==================== You will need the following toolchain to build elilo-3.16 from source the elilo build environment is optimized for Debian and Debian based distros. elilo-3.16 was built in the squeeze+(ubuntu 11.x) build environments except for itanium which is unchanged to best support legacy enterprise configs. Toolchain versions for this release were: x86x(32 & 64bit versions) * gnu-efi --> 3.0i-3 * gcc ------> 4:4.4.4-1ubuntu2 * binutils -> 2.20.51.20100908-0ubuntu2 ia64 * gnu-efi --> 3.0e-2 * gcc ------> 4.3.2-2 * binutils -> 2.18.1~cvs20080103-7 2013-03-29 13:12:41 PDT by fleischli |
From: Lentak B. <len...@ya...> - 2012-04-02 15:45:23
|
<a href="http://alemdaquadra.com.br/blog.old/wp-content/plugins/extended-comment-options/02efpk.html"> http://alemdaquadra.com.br/blog.old/wp-content/plugins/extended-comment-options/02efpk.html</a> |
From: Posen C. <bib...@gm...> - 2012-03-29 05:48:50
|
I tried to use elilo-3.14 build ia32 elilo.efi and put it in an Usb dongle and then test it on clover trail but it failed and, here's the message and elilo.conf elilo.conf: timeout=50 verbose=3 #debug image=kernel label=linux root=/dev/sdb1 initrd=ramdisk.img read-only append="debug console=ttyS0,115200n8r" fileops.c (line525): No devname schemes worked, using builtin read_config = Success EDD30 variable forced to TRUE, You should reboot to take advantage of EDD30.0 selected chosser simple kernel is 'kernel' argument are 'root=/dev/sdb1 debug console=ttyS0,115200n8r,ro' initrd is 'ramdisk.img' ELILO v3.14 for EFI/IA32 Probing loader: gzip_ia32 Probing loader: plain_efl32 Probing loader: bzImage_loader kernel header sggest kernel start at address 0x100000 allocator: AllocatePage(2,2, 1024, 0x100000) failed (Not Found) kernel_start: 0x100000 kernel size: 4194304 loading at: 0x9BE80 Using bzImage_loader loader kernel loaded in [0x100000-0x500000] entry=0x100000 kstart=0x100000 kentry=0x100000 kend=0x5000 initrd start_addr=0x500000 pgcnt=0 ramdisk.img image: total_size: 1748990 bytes bade:0x500000 pages427 Loading file ramdisk.img...done final cmdline(0): BOOT_IMAGE=dev000\kernel root/dev/sdb1 debug console=ttyS0 115200n8r ro .............. _ |
From: J K. <jp...@gm...> - 2012-01-10 22:40:06
|
With a little debugging, I solved my problem. The actual option needed in the config file is 'text-mode', without any '=1'. Also, the option must be placed after the 'image=' option, on a line of its own. John On Mon, Jan 9, 2012 at 12:57 PM, J Keller <jp...@gm...> wrote: > Jason, > > This is x86_64. > I also tried placing the 'text-mode=1' in the append line > with no success. > > ... > kernel is '/opt/tftpboot/bzImage > arguments are ' text-mode=1 earlyprintk=serial,115200 load_ramdisk=1 ... > initrd is '/opt/tftpboot/initrd > ELILO v3.14 for EFI/x86_64 > ... > > John > > > > On Mon, Jan 9, 2012 at 9:55 AM, Jason Fleischli > <fle...@us...> wrote: >> Hello John, >> >> it applies only to x86_64. >> and I believe being a sysdep option, i.e. a kernel directive >> it goes on your append=line >> append="vga=normal text-mode=1 console=ttyS0,115200n8, etc, etc" >> or in the elilo command line. >> elilo text-mode=1 "$yourlabel" >> which you can store in your boot directive. >> >> not sure that error output is entirely correct, >> or as helpful as intended. >> i'll look into that. >> >> thnx >> -jason >> >>> Hello, >>> >>> How does one use the "text-mode" variable in elilo.conf? >>> I'm trying to eliminate this error. >>> >>> >>> ...........LocateHandle GopProtocol failed. >>> --Either no graphics head is installed, >>> --efi console is set to serial, or, >>> --the EFI firmware version of this machine is >>> --older than UEFI 2.0. and does not support GOP >>> you can SAFELY IGNORE this error. elilo will >>> default to text-mode. >>> Alternatively you can now force text mode by setting config variable >>> text_mode=1 for x86 in elilo.conf or via cmdline. >>> >>> >>> If I try adding "text-mode=1" (or "text_mode=1") to the >>> config file it does not recognize the option. >>> (ELILO v3.14 for EFI/x86_64) >>> >>> >>> near line 3: Unkown option .�.�.�.�.0.0.�.�.�.�.�.�.�.�.�.�.�.�.�. >>> >>> >>> elilo config file: >>> >>> verbose=5 >>> default=aries-linux >>> text-mode=1 >>> ... >>> >>> >>> John >>> >>> elilo-discuss mailing list >>> eli...@li... >>> https://lists.sourceforge.net/lists/listinfo/elilo-discuss >> >> >> |
From: J K. <jp...@gm...> - 2012-01-09 18:57:24
|
Jason, This is x86_64. I also tried placing the 'text-mode=1' in the append line with no success. ... kernel is '/opt/tftpboot/bzImage arguments are ' text-mode=1 earlyprintk=serial,115200 load_ramdisk=1 ... initrd is '/opt/tftpboot/initrd ELILO v3.14 for EFI/x86_64 ... John On Mon, Jan 9, 2012 at 9:55 AM, Jason Fleischli <fle...@us...> wrote: > Hello John, > > it applies only to x86_64. > and I believe being a sysdep option, i.e. a kernel directive > it goes on your append=line > append="vga=normal text-mode=1 console=ttyS0,115200n8, etc, etc" > or in the elilo command line. > elilo text-mode=1 "$yourlabel" > which you can store in your boot directive. > > not sure that error output is entirely correct, > or as helpful as intended. > i'll look into that. > > thnx > -jason > >> Hello, >> >> How does one use the "text-mode" variable in elilo.conf? >> I'm trying to eliminate this error. >> >> >> ...........LocateHandle GopProtocol failed. >> --Either no graphics head is installed, >> --efi console is set to serial, or, >> --the EFI firmware version of this machine is >> --older than UEFI 2.0. and does not support GOP >> you can SAFELY IGNORE this error. elilo will >> default to text-mode. >> Alternatively you can now force text mode by setting config variable >> text_mode=1 for x86 in elilo.conf or via cmdline. >> >> >> If I try adding "text-mode=1" (or "text_mode=1") to the >> config file it does not recognize the option. >> (ELILO v3.14 for EFI/x86_64) >> >> >> near line 3: Unkown option .�.�.�.�.0.0.�.�.�.�.�.�.�.�.�.�.�.�.�. >> >> >> elilo config file: >> >> verbose=5 >> default=aries-linux >> text-mode=1 >> ... >> >> >> John >> >> elilo-discuss mailing list >> eli...@li... >> https://lists.sourceforge.net/lists/listinfo/elilo-discuss > > > |
From: J K. <jp...@gm...> - 2012-01-09 14:49:17
|
Hello, How does one use the "text-mode" variable in elilo.conf? I'm trying to eliminate this error. ...........LocateHandle GopProtocol failed. --Either no graphics head is installed, --efi console is set to serial, or, --the EFI firmware version of this machine is --older than UEFI 2.0. and does not support GOP you can SAFELY IGNORE this error. elilo will default to text-mode. Alternatively you can now force text mode by setting config variable text_mode=1 for x86 in elilo.conf or via cmdline. If I try adding "text-mode=1" (or "text_mode=1") to the config file it does not recognize the option. (ELILO v3.14 for EFI/x86_64) near line 3: Unkown option .�.�.�.�.0.0.�.�.�.�.�.�.�.�.�.�.�.�.�. elilo config file: verbose=5 default=aries-linux text-mode=1 ... John |
From: Radu M. <tai...@ya...> - 2011-09-02 13:58:49
|
Hello everyone, I need to pass arguments to elilo when i boot over the network, and i noticed in the code that they are ignored, using the function fixupargs(). I have removed this from elilo and recompiled, and it worked fine in the attempts that i made. What is the risk of running elilo.efi this way? Do you guys have more info on this EFI bug? Thank you, Radu |
From: Jarrod B J. <jbj...@us...> - 2011-08-16 17:50:18
|
So I'm working on implementing support in netfs for IPXE download protocol, if available. The thing I'm hitting is that when iPXE goes to invoke the callback, the argument list seems reversed. I know how to kind of brute force this scenario, but was wondering if there was some more sane looking way to cope. For example, assume: iPXE calls data callback with: *context, *buffer, length, offset 0xaddf, 0xcdde, 1024, 0 And if I have elilo print out the arguments in order, I get: 0, 1024, 0xcdde, 0xaddf I see quite a bit of dancing in gnu-efi to have code call into uefi provided functions, but wasn't clear on the converse... |
From: KESHAV P.R. <sko...@gm...> - 2011-01-19 08:02:06
|
On Wed, Jan 19, 2011 at 02:46, Jason Fleischli <jas...@hp...> wrote: > Git is great for large projects and scales for thousands of contributors > which is why it was created by Torvalds,... for the linux kernel. cvs > works just fine for a little project like elilo with one guy with write > access to the source tree. Git has great features, and patch tools I > know but just because elilo is in cvs doesnt prevent you from pulling > elilo source into your git tree, creating your own git project with it, > and using your git env... Anyway, I know of GIT's use and value and > will probably move elilo to it but am not in a hurry to do so. (thanks > for the tailor tip, didnt know about that one.) > > I dont think gnu-efi is dead, but regardless this is "elilo-discuss" > and the wrong list for gnu-efi requests or discussions... separate > project. > I tried using tailor to convert from cvs to git (this is the first time I am trying cvs). There no direct or a 2 way git <-> cvs bridge like git-svn does for svn or like bzr does for many other vcs systems (but i prefer git). I have uploaded the converted repo to my github account at https://github.com/skodabenz/elilo_cvs_to_git_temp . The commit messages simply contain the date of commit and not the actual commit messages present in cvs. . I have attached the tailor config file I used. gnu-efi doesn't have any mailing list to talk about this. I thought gnu-efi is attached to elilo. Its cvs repo simply has the tar.gz files without the actual commit logs like elilo does. Do you know how I can communicate cvs to git info to them. Currently I use elilo, Fedora's grub-legacy efi and grub2 (x86_64-efi config) to boot Archlinux x86_64 system. Running GCC multilib 4.5.2 and binutils 2.21 . Thanks for elilo update. It boots Archlinux perfectly in tianocore edk2 duet (uefi 2.3 x86_64 firmware). Regards. Keshav |
From: Jason F. <jas...@hp...> - 2011-01-18 21:23:33
|
On Tue, 2011-01-18 at 15:53 +0530, KESHAV P.R. wrote: > Thanks for elilo update, can you please upgrade from cvs to some > other better vcs like git or bzr for elilo, it is easier to maintain > patches and develop using distributed vcs (you can use tailor to > convert from cvs to git/bzr directly). Also gnu-efi seems to be dead. > Can the same be done for gnu-efi. Thanks in advance. Git is great for large projects and scales for thousands of contributors which is why it was created by Torvalds,... for the linux kernel. cvs works just fine for a little project like elilo with one guy with write access to the source tree. Git has great features, and patch tools I know but just because elilo is in cvs doesnt prevent you from pulling elilo source into your git tree, creating your own git project with it, and using your git env... Anyway, I know of GIT's use and value and will probably move elilo to it but am not in a hurry to do so. (thanks for the tailor tip, didnt know about that one.) I dont think gnu-efi is dead, but regardless this is "elilo-discuss" and the wrong list for gnu-efi requests or discussions... separate project. |
From: KESHAV P.R. <sko...@gm...> - 2011-01-18 10:23:55
|
Hi, Thanks for elilo update, can you please upgrade from cvs to some other better vcs like git or bzr for elilo, it is easier to maintain patches and develop using distributed vcs (you can use tailor to convert from cvs to git/bzr directly). Also gnu-efi seems to be dead. Can the same be done for gnu-efi. Thanks in advance. Regards. Keshav |
From: Jason F. <jas...@hp...> - 2011-01-13 18:26:09
|
* This should be the most x86_64 reliable release to date, this version boots x86_64 UEFI platforms that havent even hit the market yet. I dont anticipate needing to update elilo again this year(2011). Distros please pick up this release version and get it into testing for your next release. 3 . 1 4 R E L E A S E N O T E S =================================== QUICK CHANGE SUMMARY ==================== * Fixes for newly emerging x86_64 UEFI-2 boxes where long standing old assumptions are borked. * Uptake of SUSE and community patches - add sysfs support for efi vars (formerly /proc/efi/vars) - fix strncpy overflow - fix bzimage alloc - cleanups - support longer command line - yet some more mac fixes - align elilo with latest kernel boot protocol format. - new memory management strategy for initrd and kernel image loading. * add text-mode command line option, force text-mode (bypass graphics probes). * replace error output on GOP handle failed, downgraded to normal print status with more informative output. * Fix ia32 build issue with new gcc due to stack protector enforcement. BUILD NOTES ==================== You will need the following toolchain to build elilo-3.14 from source the elilo build environment is optimized for Debian and Debian based distros. elilo-3.14 was built in the Debian Lenny (Ubuntu 10.04) build environment. Toolchain versions for this release were: x86x(32 &64) * gnu-efi --> 3.0i-2ubuntu1 * gcc ------> 4.4.3-1ubuntu1 * binutils -> 2.20.1-3ubuntu7 ia64 * gnu-efi --> 3.0e-2 * gcc ------> 4.3.2-2 * binutils -> 2.18.1~cvs20080103-7 * if you use a debian based (lenny)build environment you will have no problems and setting it up is simple. you will be able to build elilo in 3 steps: 1. apt-get install gnu-efi, gcc, binutils 2. apt-get source elilo (or download elilo-3.14.tar.gz from SourceForge.) 3. extract source tarball and cd ./elilo and type $> make ** If you use the upstream toolchain tarballs(i.e. pre distro) you will need to move some files around for elilo build to work. GNU-EFI (provides the efi 1.10 and uefi 2.x libraries & api) ------- gnu-efi libraries are installed to /usr/local/lib by the upstream gnu-efi source package. elilo expects them to be in system location /usr/lib. efi includes may be located in /usr/local/include/efi. elilo expects them to be in system location /usr/include/efi. [ The reason is LSB compliance ]. BINUTILS (provides the elf conversion utility to produce efi bins) -------- binutils provides objcopy which is installed to /usr/local/bin by binutils, elilo source expects it to be in /usr/bin. again this LSB compliance is taken care of by the distro's that fix the toolchains to install to the correct compliant system locations instead of the "user optional" location. ELILO ON EFI X86_64 ===================== HARD REQUIREMENTS EFI + x86_64 REQUIRES an efi64 enabled linux kernel i.e. 2.6.21 or newer nothing earlier will work, 2.6.21 was the earliest kernel that efi64 support went into. You need to compile the kernel with CONFIG_EFI kernel option ON. x86_64 platforms with UEFI 2.0 firmware deprecate UGA protocol and therefore only the Graphics Output Protocol (GOP) is supported. For such platforms, the kernel must be compiled with EFI_FB option ON. This will enable early boot messages on the console. Elilo for x86_64 attempts to query EFI for GOP support and if it fails it defaults to text mode which may or may not show you early console ouput depends on your efi console settings and physical setup. Elilo has no way to know if your console settings are messed up. WORKING ELILO.CONF FOR EFI X86_64 EXAMPLE Here is my elilo.conf from my UEFI2.0/x86_64 (with nvidia pcie add on card, i.e. your vga= kernel param may be different) workstation which uses GOP. Here is a partial kernel vga table I was able to find and add here. Colours 640x400 640x480 800x600 1024x768 1152x864 1280x1024 1600x1200 -------+-------------------------------------------------------------- 4 bits | ? ? 0x302 ? ? ? ? 8 bits | 0x300 0x301 0x303 0x305 0x161 0x307 0x31C 15 bits | ? 0x310 0x313 0x316 0x162 0x319 0x31D 16 bits | ? 0x311 0x314 0x317 0x163 0x31A 0x31E decimal | d785 d788 d791 24 bits | ? 0x312 0x315 0x318 ? 0x31B 0x31F Additionally from ...kernel-source/Documentation/Boot.txt... vga=<mode> <mode> here is either an integer (in C notation, either decimal, octal, or hexadecimal) or one of the strings "normal" (meaning 0xFFFF), "ext" (meaning 0xFFFE) or "ask" (meaning 0xFFFD). This value should be entered into the vid_mode field, as it is used by the kernel before the command line is parsed. example below shows me console output, what elilo is doing, and kernel boot. vga=normal with efi console input output directed to graphics card should work as well. default=UBUNTU chooser=simple verbose=5 delay=30 append="root=/dev/sda3 vga=0x31e splash showopts" image=/vmlinuz-2.6.32-27-generic label="UBUNTU" description="Ubuntu 2.6.32-27-generic kernel" initrd=/initrd.img-2.6.32-27-generic |
From: Adhyas A. <ad...@gm...> - 2010-11-12 22:57:04
|
I am using qemu-kvm-0.13.0 and OVMF based EFI BIOS to boot to openSUSE 11.3 ISO image. I can see the linux and initrd images as part of the boot fat filesystem itself (placed along side eliloX64.efi). The boot loader loads and runs fine, it also loads the kernel and initrd images fine, and jumps to the kernel, soon after that my VM restarts. This is 100% reproducible. I am trying to work more on this issue. I would appreciate if someone can see that it reproduces and give me some pointers on how to proceed and where the issue may lie. Thanks, Adhyas ******************************************************************** Two types have compatible type if their types are the same. — ANSI C Standard, 3.1.2.6. ******************************************************************** |
From: Thomas E. <tho...@gm...> - 2010-06-02 08:18:46
|
Hi! But does it have to? Doesn't elilo support headless systems? The GOP is probably not installed but the elilo documentation clearly states in elilo.txt at section "XIII/ Booting on EFI/x86_64 platforms" that "The elilo for x86_64 attempts to query the firmware for GOP and if it fails it defaults to text mode." Which my sort of "printf debugging" with ERR_PRT confirms. That elilo continues to execute until ExitBootServices and then it is gone. Does anyone have any experience with PXE booting elilo ? How can I be certain that elilo executes the start_kernel() call ? /Thomas 2010/6/1 <Stu...@de...> > > Perhaps your uEFI firmware doesn't support graphics output > protocol (gop)...? > > > ------------------------------ > *From:* Thomas Ekstrand [mailto:tho...@gm...] > *Sent:* Monday, May 31, 2010 3:31 AM > *To:* eli...@li... > *Subject:* [elilo-discuss] Trouble netbooting elilo 3.12 > > Hi! > > I'm having trouble netbooting elilo. I have a x86_64 EFI system booting > elilo.efi off of a tftp boot server. > I think it goes as far as calling ExitBootServices but never returns from > there. > > After "create_boot_params" it just stops dead. > > Kernel is 2.6.27 and compiled with CONFIG_EFI=y > > Any ideas or hints is appreciated. > > > Thanks! > Thomas > > > > This is the ouput in verbose=5 mode: > > trying chooser simple > trying chooser textmenu > selected chooser simple > kernel is 'vmlinuz.x86_64_2' > arguments are ' rw root=/dev/ram0 acpi=off nosplash text noapic isolcpus=1 > console=ttyS0,115200n8r loglevel=7 crashkernel=60M@16M bb=1M@15Mramdisk_size=60000 sm=2500 cm iommu=merge' > initrd is 'gsdi_uabmagj5.cpio' > ELILO v3.12 for EFI/x86_64 > downloading gep4/vmlinuz.x86_64_2 from 192.168.1.1... > setting default buffer size of 16777216 for gep4/vmlinuz.x86_64_2, no > filesize recd from tftp server > Done > Probing loader: gzip_x86_64 > Probing loader: plain_elf64 > plain_probe: kname=vmlinuz.x86_64_2 > Probing loader: bzImage_loader > kernel header suggests kernel start at address 0x100000 > allocator: AllocatePages(2, 2, 2048, 0x100000) failed (Not Found) > kernel_start: 0x100000 kernel_size: 8388608 loading at: 0x3807000 > Using bzImage_loader loader > kernel loaded in [0x100000-0x900000] entry=0x100000 > kstart=0x100000 kentry=0x100000 kend=0x900000 > initrd start_addr=0x900000 pgcnt=0 > downloading gep4/gsdi_uabmagj5.cpio from 192.168.1.1... > setting default buffer size of 16777216 for gep4/gsdi_uabmagj5.cpio, no > filesize recd from tftp server > buffer too small, need netbuf_size=61597139 > setting default buffer size of 61597139 for gep4/gsdi_uabmagj5.cpio, no > filesize recd from tftp server > Done > gsdi_uabmagj5.cpio image: total_size: 61597139 bytes base: 0xF113000 pages > 15039 > Loading file > gsdi_uabmagj5.cpio...|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\| > "cut some out" > > |/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\| > done > final cmdline(0): BOOT_IMAGE=net0:gep4/vmlinuz.x86_64_2 rw root=/dev/ram0 > acpi=off nosplash text noapic isolcpus=1 console=ttyS0,115200n8r loglevel=7 > crashkernel=60M@16M bb=1M@15M ramdisk_size=60000 sm=2500 cm iommu=merge > ............... > system.c(line 212):LocateHandle GopProtocol failed. > > |
From: <Stuart_Hayes@Dell.com> - 2010-06-01 16:18:51
|
Perhaps your uEFI firmware doesn't support graphics output protocol (gop)...? ________________________________ From: Thomas Ekstrand [mailto:tho...@gm...] Sent: Monday, May 31, 2010 3:31 AM To: eli...@li... Subject: [elilo-discuss] Trouble netbooting elilo 3.12 Hi! I'm having trouble netbooting elilo. I have a x86_64 EFI system booting elilo.efi off of a tftp boot server. I think it goes as far as calling ExitBootServices but never returns from there. After "create_boot_params" it just stops dead. Kernel is 2.6.27 and compiled with CONFIG_EFI=y Any ideas or hints is appreciated. Thanks! Thomas This is the ouput in verbose=5 mode: trying chooser simple trying chooser textmenu selected chooser simple kernel is 'vmlinuz.x86_64_2' arguments are ' rw root=/dev/ram0 acpi=off nosplash text noapic isolcpus=1 console=ttyS0,115200n8r loglevel=7 crashkernel=60M@16M bb=1M@15M ramdisk_size=60000 sm=2500 cm iommu=merge' initrd is 'gsdi_uabmagj5.cpio' ELILO v3.12 for EFI/x86_64 downloading gep4/vmlinuz.x86_64_2 from 192.168.1.1... setting default buffer size of 16777216 for gep4/vmlinuz.x86_64_2, no filesize recd from tftp server Done Probing loader: gzip_x86_64 Probing loader: plain_elf64 plain_probe: kname=vmlinuz.x86_64_2 Probing loader: bzImage_loader kernel header suggests kernel start at address 0x100000 allocator: AllocatePages(2, 2, 2048, 0x100000) failed (Not Found) kernel_start: 0x100000 kernel_size: 8388608 loading at: 0x3807000 Using bzImage_loader loader kernel loaded in [0x100000-0x900000] entry=0x100000 kstart=0x100000 kentry=0x100000 kend=0x900000 initrd start_addr=0x900000 pgcnt=0 downloading gep4/gsdi_uabmagj5.cpio from 192.168.1.1... setting default buffer size of 16777216 for gep4/gsdi_uabmagj5.cpio, no filesize recd from tftp server buffer too small, need netbuf_size=61597139 setting default buffer size of 61597139 for gep4/gsdi_uabmagj5.cpio, no filesize recd from tftp server Done gsdi_uabmagj5.cpio image: total_size: 61597139 bytes base: 0xF113000 pages 15039 Loading file gsdi_uabmagj5.cpio...|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\| "cut some out" |/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\| done final cmdline(0): BOOT_IMAGE=net0:gep4/vmlinuz.x86_64_2 rw root=/dev/ram0 acpi=off nosplash text noapic isolcpus=1 console=ttyS0,115200n8r loglevel=7 crashkernel=60M@16M bb=1M@15M ramdisk_size=60000 sm=2500 cm iommu=merge ............... system.c(line 212):LocateHandle GopProtocol failed. |
From: Thomas E. <tho...@gm...> - 2010-05-31 08:30:49
|
Hi! I'm having trouble netbooting elilo. I have a x86_64 EFI system booting elilo.efi off of a tftp boot server. I think it goes as far as calling ExitBootServices but never returns from there. After "create_boot_params" it just stops dead. Kernel is 2.6.27 and compiled with CONFIG_EFI=y Any ideas or hints is appreciated. Thanks! Thomas This is the ouput in verbose=5 mode: trying chooser simple trying chooser textmenu selected chooser simple kernel is 'vmlinuz.x86_64_2' arguments are ' rw root=/dev/ram0 acpi=off nosplash text noapic isolcpus=1 console=ttyS0,115200n8r loglevel=7 crashkernel=60M@16M bb=1M@15Mramdisk_size=60000 sm=2500 cm iommu=merge' initrd is 'gsdi_uabmagj5.cpio' ELILO v3.12 for EFI/x86_64 downloading gep4/vmlinuz.x86_64_2 from 192.168.1.1... setting default buffer size of 16777216 for gep4/vmlinuz.x86_64_2, no filesize recd from tftp server Done Probing loader: gzip_x86_64 Probing loader: plain_elf64 plain_probe: kname=vmlinuz.x86_64_2 Probing loader: bzImage_loader kernel header suggests kernel start at address 0x100000 allocator: AllocatePages(2, 2, 2048, 0x100000) failed (Not Found) kernel_start: 0x100000 kernel_size: 8388608 loading at: 0x3807000 Using bzImage_loader loader kernel loaded in [0x100000-0x900000] entry=0x100000 kstart=0x100000 kentry=0x100000 kend=0x900000 initrd start_addr=0x900000 pgcnt=0 downloading gep4/gsdi_uabmagj5.cpio from 192.168.1.1... setting default buffer size of 16777216 for gep4/gsdi_uabmagj5.cpio, no filesize recd from tftp server buffer too small, need netbuf_size=61597139 setting default buffer size of 61597139 for gep4/gsdi_uabmagj5.cpio, no filesize recd from tftp server Done gsdi_uabmagj5.cpio image: total_size: 61597139 bytes base: 0xF113000 pages 15039 Loading file gsdi_uabmagj5.cpio...|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\| "cut some out" |/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\| done final cmdline(0): BOOT_IMAGE=net0:gep4/vmlinuz.x86_64_2 rw root=/dev/ram0 acpi=off nosplash text noapic isolcpus=1 console=ttyS0,115200n8r loglevel=7 crashkernel=60M@16M bb=1M@15M ramdisk_size=60000 sm=2500 cm iommu=merge ............... system.c(line 212):LocateHandle GopProtocol failed. |
From: explore.life.forever <exp...@gm...> - 2010-05-18 09:48:06
|
hi all, this is my first time using email list...hope you can help me. i encounted a problem, actually two problems. ---------------------------------- hardware: MSI P45D3 Platinum, UEFI, directories: -live initrd1.img vmlinuz1 filesystem.squashfs ... -elilo elilo.efi elilo.conf ---------------------------------- 1. i made a USB Live stick, but it can't boot from this motherboard (when select "USB Hotplug FDD", then the error message is "Boot Failure, Press any key to continue..."). Howerver, in the Legacy BIOS, it works. Why? 2. this one is about elilo.efi and elilo.conf, i copy the elilo.efi (x86_64 edition, only this edition can work in the UEFI Shell) to the USB, and create a elilo.conf, content: ----------------------------- prompt timeout=50 default=live image=/live/vmlinuz1 label=live initrd=/live/initrd1.img read-only root=/dev/sdb append="console=ttyS0" ---------------------------- but as i run this command in the UEFI Shell "elilo.efi -v" in the Filesystem of the USB stick, i saw the error: --------------------------------------------------------------- kernel is '/live/vmlinuz1' arguments are 'root=/dev/sdb console=ttyS0 ro' initrd is '/live/initrd1.img' allocator: AllocatePages(2, 2, 0x100000) failed (Not Found) . Using bzImage_loader loader Loding file \live\initrd1.img...done ................... (!died here!) --------------------------------------------------------------- anyone can help me ? thank you. 2010-05-18 explore.life.forever |
From: Naresh B. <nar...@gm...> - 2010-04-09 11:24:45
|
Hi Jason, Thanks a lot for the information. Please, keep myself also in loop when you file a bug. Here is one more information I have downloaded and tried all the available versions of the elilo-3.*-ia32.elf binaries. But no luck..-:( getting the same "LocateHandle GopProtocol failed" error. I have few questions 1. If it is back word compatibility issue, I assume at-least one version of elilo-3.*-ia32.elf (between elilo-3.5pre1 to elilo-3.12) binary should be working. I am not understanding why not all binaries? Is it because of following reason? Reason: On platform x86/IA32 EFI 10.1 firmware does not have the GOP handler call implementation (in UEFI 2.0 firmware GOP handler call exists) and It is required to write a different handler, by looking in to x86/IA32 EFI 10.1 Firmware specification? 2. When can I expect the next version release of elilo ? * Thanks and Regards -Naresh Bhat* On Fri, Apr 9, 2010 at 1:02 AM, Jason Fleischli <jas...@hp...>wrote: > On Thu, 2010-04-08 at 13:29 -0600, Jason Fleischli wrote: > > and I mean with elilo-3.12 > > I see your response that 3.6 gets passed the GOP query, ah just looked > > its not there in 3.6, wondering if the GOP query is invalid on EFI > > 1.10 > > It was introduced with the INTEL UEFI patches for 3.8. I'll look at > > the > > EFI spec. > So this is the issue, backwards compatibility issue, that handle is not > defined in EFI 1.10 so the query is invalid. I'll file a bug, thnx > > -jason > > |
From: Naresh B. <nar...@gm...> - 2010-04-09 11:20:57
|
Hi Jason, Thanks a lot for the information. Please, keep myself also in loop when you file a bug. Here is one more information I have downloaded and tried all the available versions of the elilo-3.*-ia32.elf binaries. But no luck..-:( getting the same "LocateHandle GopProtocol failed" error. I have few questions 1. If it is back word compatibility issue, I assume at-least one version of elilo-3.*-ia32.elf (between elilo-3.5pre1 to elilo-3.12) binary should be working. I am not understanding why not all binaries? Is it because of following reason? Reason: On platform x86/IA32 EFI 10.1 firmware does not have the GOP handler call implementation (in UEFI 2.0 firmware GOP handler call exists) and It is required to write a different handler, by looking in to x86/IA32 EFI 10.1 Firmware specification? 2. When can I expect the next version release of elilo ? * Thanks and Regards -Naresh Bhat* On Fri, Apr 9, 2010 at 1:02 AM, Jason Fleischli <jas...@hp...>wrote: > On Thu, 2010-04-08 at 13:29 -0600, Jason Fleischli wrote: > > and I mean with elilo-3.12 > > I see your response that 3.6 gets passed the GOP query, ah just looked > > its not there in 3.6, wondering if the GOP query is invalid on EFI > > 1.10 > > It was introduced with the INTEL UEFI patches for 3.8. I'll look at > > the > > EFI spec. > So this is the issue, backwards compatibility issue, that handle is not > defined in EFI 1.10 so the query is invalid. I'll file a bug, thnx > > -jason > > |
From: Jason F. <jas...@hp...> - 2010-04-08 19:35:51
|
On Thu, 2010-04-08 at 13:29 -0600, Jason Fleischli wrote: > and I mean with elilo-3.12 > I see your response that 3.6 gets passed the GOP query, ah just looked > its not there in 3.6, wondering if the GOP query is invalid on EFI > 1.10 > It was introduced with the INTEL UEFI patches for 3.8. I'll look at > the > EFI spec. So this is the issue, backwards compatibility issue, that handle is not defined in EFI 1.10 so the query is invalid. I'll file a bug, thnx -jason |
From: Jason F. <jas...@hp...> - 2010-04-08 19:32:37
|
On Thu, 2010-04-08 at 12:44 -0600, Jason Fleischli wrote: > On Thu, 2010-04-08 at 23:36 +0530, Naresh Bhat wrote: > > Hi Jason, > > > > Thank you very much for responding. Here are my comments and > > questions > > > > 1. NO, I have not tried the pre-compiled binaries. I have > downloaded > > the latest elilo and gnu-efi source code from sourceforge.net and > > compiled. > > > > 2. What does this mean "There was code that went into 3.12 to force > > text output mode for ia32 macs" ? > forget it, its not your problem, the problem is your platform EFI is > not providing elilo the graphics output protocol while elilo is > setting > up the boot parameters to pass to your kernel. at that line, elilo > is simply querying your EFI for the handle, your EFI is returning an > error on that query. Since your on IA32 non-mac and efi 1.10 try > setting > option "legacy-free" an IA32 specific option and get your elilo.conf > fixed up, see elilo-source/docs/elilo.txt > for documentation on the config file setup and this "legacy-free" > option. you might check your EFI console settings too and make sure > everything in EFI is setup to go to the PCI or AGP default that you > intend to make sure EFI is not set to serial only or something for > which no graphics output is supported especially if you have multiple > graphics interfaces in your system. and I mean with elilo-3.12 I see your response that 3.6 gets passed the GOP query, ah just looked its not there in 3.6, wondering if the GOP query is invalid on EFI 1.10 It was introduced with the INTEL UEFI patches for 3.8. I'll look at the EFI spec. -- ___________________________________ JASON FLEISCHLI HP - Linux Telco R&D | Support Ft. Collins CO (970)898-0874 |