Re: [lfs-support] Step 5.4.1 Installation of Cross Binutils errors
Le 16/11/2013 00:46, Ken Moffat a écrit : On Fri, Nov 15, 2013 at 01:20:06PM +, Vasco Almeida wrote: OK, I did as instructed in your recommendations above, and tried to be as extra careful as ignorance allows. So I am attaching the four logs collected during the 5.4.1 step, for your kind inspection. But when I invoked make install, I got a raft of This is not dpkg install-info anymore, but GNU install-info See the man page for ginstall-info for command line arguments [...] which are perhaps not that surprising. They are certainly surprising to _me_, and I don't see them in any of the gzipped logs you attached. [...] I do have them in my logs. Debian's install-info is a wrapper to GNU's install-info, for backward compatibility with another install-info they used to ship with dpkg. Those warnings are sent to stderr, that the OP did not capture in the logs. Those warnings are normal on a Debian system (although maybe in this case, the Debian system is not totally normal). Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
[lfs-support] Help with Installing to UEFI Motherboard
Hi, After getting the stock LFS system installed, with an MBR type boot installation, I'm experimenting with installing to a UEFI type boot location on a brand new hard drive. I've been reading a lot of online documentation, and have tried a first-cut installation, but am not having success in installing. While I can install the entire set of LFS programs, and a lot of BLFS programs, when I try to boot up, Linux fires up but quickly generates a fatal error. Is there any possibility of advice from the LFS staff? Please note that my goal here is not just to get an LFS system going, but to learn as much as I can about this kind of Linux installation. Alan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Help with Installing to UEFI Motherboard
On Sat, Nov 16, 2013 at 02:04:31PM -0500, Alan Feuerbacher wrote: Hi, After getting the stock LFS system installed, with an MBR type boot installation, I'm experimenting with installing to a UEFI type boot location on a brand new hard drive. I've been reading a lot of online documentation, and have tried a first-cut installation, but am not having success in installing. While I can install the entire set of LFS programs, and a lot of BLFS programs, when I try to boot up, Linux fires up but quickly generates a fatal error. Is there any possibility of advice from the LFS staff? http://www.mail-archive.com/lfs-support@linuxfromscratch.org/ See the posts from Dan McGhee - most recently on 13th November, but starting on 28th October. Four threads, titles mentioning GRUB or EFI. At the moment they are all on the first page at that link, at least in firefox. Our best advice / guesses is in those threads. Dan hasn't cracked it yet, but your hardware might be different. ĸen -- das eine Mal als Tragödie, dieses Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Help with Installing to UEFI Motherboard
On 17/11/2013 10:10 AM, Dan McGhee wrote: On 11/16/2013 03:40 PM, Ken Moffat wrote: On Sat, Nov 16, 2013 at 02:04:31PM -0500, Alan Feuerbacher wrote: Hi, After getting the stock LFS system installed, with an MBR type boot installation, I'm experimenting with installing to a UEFI type boot location on a brand new hard drive. I've been reading a lot of online documentation, and have tried a first-cut installation, but am not having success in installing. While I can install the entire set of LFS programs, and a lot of BLFS programs, when I try to boot up, Linux fires up but quickly generates a fatal error. Is there any possibility of advice from the LFS staff? http://www.mail-archive.com/lfs-support@linuxfromscratch.org/ See the posts from Dan McGhee - most recently on 13th November, but starting on 28th October. Four threads, titles mentioning GRUB or EFI. At the moment they are all on the first page at that link, at least in firefox. Our best advice / guesses is in those threads. Dan hasn't cracked it yet, but your hardware might be different. ĸen I thought I was going to be able to report success this afternoon, but as yet no joy. My efforts so far have resulted in the following conclusions: 1. There is something wrong in my grub set-up. 2. My kernel is not bootable. 3. I have missed something in the EFI info. At this point, all I want is some indication that my kernel is booting. As long as I get only one message from the kernel and the system freezes I can conclude that all else is fine except my kernel. I'm writing this e-mail on the fly and don't have my EFI sources at hand. I read last night that from the EFI partition the bootloader--in this case GRUB--doesn't know where the file system is even though it can read the partition table. Therefore, and initramfs is called for. I know nothing about these. I've read what the BLFS book has and have tried it with no success. At this point, I don't know enough to solve any gotcha's that the initramfs hint gives. Gonna try dracut. If I can't make any head-way in the next few days, I'm going to install a minimal ArchLinux system and try the various GRUB options. I don't think they sign their kernels--see last paragraph--and that will test the GRUB stuff. I cannot verify this in any documentation. It's just a hunch I have. When it comes to booting using an EFI partition, we must ignore everything we've learned about booting and using GRUB. It may be that using GRUB in a multiboot environment we cannot use the linux /boot/vmliz* root=/dev/xxx ro to get to another distro. We may have to use grub's chainloader to do that. I say this because, I have not been able to get Ubuntu to boot from my LFS-7.4 system in the old way. I was successful using the chainloader. If all this is true, then the easiest way to accomplish this is to use 'efibootmgr' or 'gummiboot' and boot everything thing we have from the EFI partition. My goal is to be able to be able to answer these questions when my testing is over. @Alan Did you remove GRUB from your MBR Protected Layer or are you still using it? Do you use an initrd or initramfs? Did you boot your kernel successfully before you started these EFI experiments? Does your failure message come from the kernel or from the LFS bootscripts? What does it say? Must you do a hard reset to start over or can you use ALT-CTRL-DEL? There is only one other option that's keeping me from booting in this environment. It's so distasteful that I don't even want to write it. But, at least in my firmware, it may be necessary for me to sign my kernel. That's not even for secure boot. I hope that's not true. Dan Dan, I could not get EFI and Grub2 to co-operate so I went for the Linux EFI image route instead and eliminated the boot manager. It is not really necessary unless you want to select from different kernels on the system. The kernel must be compiled with the EFI settings: CONFIG_EFI=y CONFIG_RELOCATABLE=y CONFIG_FB_EFI=y CONFIG_FRAMEBUFFER_CONSOLE=y CONFIG_EFI_PARTITION=y CONFIG_EFI_VARS=y CONFIG_EFI_STUB=y and also the kernel parameters built-in: CONFIG_CMDLINE=root=/dev/sda3 ro --verbose then use efibootmgr to register the new kernel image with the BIOS, so it can be selected at boot time. Geoff -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Help with Installing to UEFI Motherboard
On 11/16/2013 05:44 PM, Geoff Swan wrote: On 17/11/2013 10:10 AM, Dan McGhee wrote: On 11/16/2013 03:40 PM, Ken Moffat wrote: On Sat, Nov 16, 2013 at 02:04:31PM -0500, Alan Feuerbacher wrote: Hi, After getting the stock LFS system installed, with an MBR type boot installation, I'm experimenting with installing to a UEFI type boot location on a brand new hard drive. I've been reading a lot of online documentation, and have tried a first-cut installation, but am not having success in installing. While I can install the entire set of LFS programs, and a lot of BLFS programs, when I try to boot up, Linux fires up but quickly generates a fatal error. Is there any possibility of advice from the LFS staff? http://www.mail-archive.com/lfs-support@linuxfromscratch.org/ See the posts from Dan McGhee - most recently on 13th November, but starting on 28th October. Four threads, titles mentioning GRUB or EFI. At the moment they are all on the first page at that link, at least in firefox. Our best advice / guesses is in those threads. Dan hasn't cracked it yet, but your hardware might be different. ?en I thought I was going to be able to report success this afternoon, but as yet no joy. My efforts so far have resulted in the following conclusions: 1. There is something wrong in my grub set-up. 2. My kernel is not bootable. 3. I have missed something in the EFI info. At this point, all I want is some indication that my kernel is booting. As long as I get only one message from the kernel and the system freezes I can conclude that all else is fine except my kernel. I'm writing this e-mail on the fly and don't have my EFI sources at hand. I read last night that from the EFI partition the bootloader--in this case GRUB--doesn't know where the file system is even though it can read the partition table. Therefore, and initramfs is called for. I know nothing about these. I've read what the BLFS book has and have tried it with no success. At this point, I don't know enough to solve any gotcha's that the initramfs hint gives. Gonna try dracut. If I can't make any head-way in the next few days, I'm going to install a minimal ArchLinux system and try the various GRUB options. I don't think they sign their kernels--see last paragraph--and that will test the GRUB stuff. I cannot verify this in any documentation. It's just a hunch I have. When it comes to booting using an EFI partition, we must ignore everything we've learned about booting and using GRUB. It may be that using GRUB in a multiboot environment we cannot use the linux /boot/vmliz* root=/dev/xxx ro to get to another distro. We may have to use grub's chainloader to do that. I say this because, I have not been able to get Ubuntu to boot from my LFS-7.4 system in the old way. I was successful using the chainloader. If all this is true, then the easiest way to accomplish this is to use 'efibootmgr' or 'gummiboot' and boot everything thing we have from the EFI partition. My goal is to be able to be able to answer these questions when my testing is over. @Alan Did you remove GRUB from your MBR Protected Layer or are you still using it? Do you use an initrd or initramfs? Did you boot your kernel successfully before you started these EFI experiments? Does your failure message come from the kernel or from the LFS bootscripts? What does it say? Must you do a hard reset to start over or can you use ALT-CTRL-DEL? There is only one other option that's keeping me from booting in this environment. It's so distasteful that I don't even want to write it. But, at least in my firmware, it may be necessary for me to sign my kernel. That's not even for secure boot. I hope that's not true. Dan Dan, I could not get EFI and Grub2 to co-operate so I went for the Linux EFI image route instead and eliminated the boot manager. It is not really necessary unless you want to select from different kernels on the system. The kernel must be compiled with the EFI settings: CONFIG_EFI=y CONFIG_RELOCATABLE=y CONFIG_FB_EFI=y CONFIG_FRAMEBUFFER_CONSOLE=y CONFIG_EFI_PARTITION=y CONFIG_EFI_VARS=y CONFIG_EFI_STUB=y and also the kernel parameters built-in: CONFIG_CMDLINE=root=/dev/sda3 ro --verbose then use efibootmgr to register the new kernel image with the BIOS, so it can be selected at boot time. Geoff Geoff, your comments are giving me a break from answering questions in make oldconfig :) Just so I understand. You got your kernel--3.10.10 (?)--to boot from the EFI partition? And without initrd or initramfs? The answer to this question is important to me. As I said before, I don't have my references close right now, but you may want to consider reconfiguring your kernel with CONFIG_EFI_VARS=n and enabling evifarfs. efivars is going away. I'll check my references and post later with the appropriate one. I have been using efivarfs mounted at /sys/firmware/efi/efivars with great success. Otherwise, I have been
Re: [lfs-support] Help with Installing to UEFI Motherboard
On 11/16/2013 05:44 PM, Geoff Swan wrote: On 17/11/2013 10:10 AM, Dan McGhee wrote: On 11/16/2013 03:40 PM, Ken Moffat wrote: On Sat, Nov 16, 2013 at 02:04:31PM -0500, Alan Feuerbacher wrote: Hi, After getting the stock LFS system installed, with an MBR type boot installation, I'm experimenting with installing to a UEFI type boot location on a brand new hard drive. I've been reading a lot of online documentation, and have tried a first-cut installation, but am not having success in installing. While I can install the entire set of LFS programs, and a lot of BLFS programs, when I try to boot up, Linux fires up but quickly generates a fatal error. Is there any possibility of advice from the LFS staff? http://www.mail-archive.com/lfs-support@linuxfromscratch.org/ See the posts from Dan McGhee - most recently on 13th November, but starting on 28th October. Four threads, titles mentioning GRUB or EFI. At the moment they are all on the first page at that link, at least in firefox. Our best advice / guesses is in those threads. Dan hasn't cracked it yet, but your hardware might be different. ?en I thought I was going to be able to report success this afternoon, but as yet no joy. My efforts so far have resulted in the following conclusions: 1. There is something wrong in my grub set-up. 2. My kernel is not bootable. 3. I have missed something in the EFI info. At this point, all I want is some indication that my kernel is booting. As long as I get only one message from the kernel and the system freezes I can conclude that all else is fine except my kernel. I'm writing this e-mail on the fly and don't have my EFI sources at hand. I read last night that from the EFI partition the bootloader--in this case GRUB--doesn't know where the file system is even though it can read the partition table. Therefore, and initramfs is called for. I know nothing about these. I've read what the BLFS book has and have tried it with no success. At this point, I don't know enough to solve any gotcha's that the initramfs hint gives. Gonna try dracut. If I can't make any head-way in the next few days, I'm going to install a minimal ArchLinux system and try the various GRUB options. I don't think they sign their kernels--see last paragraph--and that will test the GRUB stuff. I cannot verify this in any documentation. It's just a hunch I have. When it comes to booting using an EFI partition, we must ignore everything we've learned about booting and using GRUB. It may be that using GRUB in a multiboot environment we cannot use the linux /boot/vmliz* root=/dev/xxx ro to get to another distro. We may have to use grub's chainloader to do that. I say this because, I have not been able to get Ubuntu to boot from my LFS-7.4 system in the old way. I was successful using the chainloader. If all this is true, then the easiest way to accomplish this is to use 'efibootmgr' or 'gummiboot' and boot everything thing we have from the EFI partition. My goal is to be able to be able to answer these questions when my testing is over. @Alan Did you remove GRUB from your MBR Protected Layer or are you still using it? Do you use an initrd or initramfs? Did you boot your kernel successfully before you started these EFI experiments? Does your failure message come from the kernel or from the LFS bootscripts? What does it say? Must you do a hard reset to start over or can you use ALT-CTRL-DEL? There is only one other option that's keeping me from booting in this environment. It's so distasteful that I don't even want to write it. But, at least in my firmware, it may be necessary for me to sign my kernel. That's not even for secure boot. I hope that's not true. Dan Dan, I could not get EFI and Grub2 to co-operate so I went for the Linux EFI image route instead and eliminated the boot manager. It is not really necessary unless you want to select from different kernels on the system. The kernel must be compiled with the EFI settings: CONFIG_EFI=y CONFIG_RELOCATABLE=y CONFIG_FB_EFI=y CONFIG_FRAMEBUFFER_CONSOLE=y CONFIG_EFI_PARTITION=y CONFIG_EFI_VARS=y CONFIG_EFI_STUB=y and also the kernel parameters built-in: CONFIG_CMDLINE=root=/dev/sda3 ro --verbose then use efibootmgr to register the new kernel image with the BIOS, so it can be selected at boot time. Geoff I think efivarfs is new in 3.10.10 CONFIG_EFIVAR_FS=(y or m) is what I recommend if you're using 3.10.10 Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
[lfs-support] Shadow
This is the first time I've attempted to do an LFS in several years, and of course I can't get ONE package. Apparently Alioth had a catastrophic drive failure about a week ago, thus making Shadow unavailable. I would love it if someone could post a link to a mirror or send me the package directly. Thanks in advance for any help. Nate Jones -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Help with Installing to UEFI Motherboard
On 11/16/2013 7:36 PM, Dan McGhee wrote: I think efivarfs is new in 3.10.10 CONFIG_EFIVAR_FS=(y or m) is what I recommend if you're using 3.10.10 The information I've gotten so far about setting these CONFIG variables, from Arch Linux, rodsbooks.com and other places, is summarized here, from my incomplete notes from the last several weeks: *** # For UEFI booting, according to ArchLinux you also need to ensure that the following # https://wiki.archlinux.org/index.php/Unified_Extensible_Firmware_Interface # kernel configuration options are set: ## CONFIG_RELOCATABLE=y CONFIG_EFI=y CONFIG_EFI_STUB=y CONFIG_EFI=y CONFIG_EFI_STUB=y CONFIG_FB_EFI=y CONFIG_FRAMEBUFFER_CONSOLE=y # UEFI Runtime Variables Support (efivarfs filesystem - /sys/firmware/efi/efivars). This option is important as this is required to manipulate UEFI Runtime Variables using tools like /usr/bin/efibootmgr. The below config option has been added in kernel 3.10 and above. CONFIG_EFIVAR_FS=y # UEFI Runtime Variables Support (old efivars sysfs interface - /sys/firmware/efi/vars). This option should be disabled. CONFIG_EFI_VARS=n # GUID Partition Table GPT config option - mandatory for UEFI support CONFIG_EFI_PARTITION=y # Note: All of the above options are required to boot Linux via UEFI, and are enabled in Archlinux kernels in official repos. ## # # ALSO need to set this: ## CONFIG_CMDLINE_BOOL=y CONFIG_CMDLINE= ## # See # and in make menuconfig set these with Processor Type and Features - Built-in kernel command line # # Also, in installing Cups-1.6.3 the BLFS book states: # # Kernel Configuration # Note # # There is a conflict between the Cups libusb backend and the usblp kernel driver. If you want to use Cups with libusb, do not enable USB Printer support in your kernel. # # If you want to use the kernel usblp driver, enable the following options in your kernel configuration and recompile the kernel: # # If you want to use the kernel usblp driver, enable the following options in your kernel configuration and recompile the kernel: # # Device Drivers --- # [*] USB support --- # .. # In make menuconfig, get rid of the * in USB support *** Since I have not yet been successful in booting Linux 3.10.10 with UEFI, I can't comment on the above. For what it's worth. Alan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Shadow
On 11/16/2013 7:43 PM, Nathanial Jones wrote: I would love it if someone could post a link to a mirror or send me the package directly. Check your mail. Alan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Shadow
On Sat, Nov 16, 2013 at 07:57:36PM -0500, Alan Feuerbacher wrote: On 11/16/2013 7:43 PM, Nathanial Jones wrote: I would love it if someone could post a link to a mirror or send me the package directly. Check your mail. Alan More generally, http://anduin.linuxfromscratch.org/sources/LFS/lfs-packages/ ĸen -- das eine Mal als Tragödie, dieses Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Shadow
Thanks -Original Message- From: lfs-support-boun...@linuxfromscratch.org [mailto:lfs-support-boun...@linuxfromscratch.org] On Behalf Of Alan Feuerbacher Sent: Saturday, November 16, 2013 7:58 PM To: LFS Support List Subject: Re: [lfs-support] Shadow On 11/16/2013 7:43 PM, Nathanial Jones wrote: I would love it if someone could post a link to a mirror or send me the package directly. Check your mail. Alan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Help with Installing to UEFI Motherboard
On 11/16/2013 06:51 PM, Alan Feuerbacher wrote: On 11/16/2013 7:36 PM, Dan McGhee wrote: I think efivarfs is new in 3.10.10 CONFIG_EFIVAR_FS=(y or m) is what I recommend if you're using 3.10.10 The information I've gotten so far about setting these CONFIG variables, from Arch Linux, rodsbooks.com and other places, is summarized here, from my incomplete notes from the last several weeks: *** # For UEFI booting, according to ArchLinux you also need to ensure that the following # https://wiki.archlinux.org/index.php/Unified_Extensible_Firmware_Interface # kernel configuration options are set: ## CONFIG_RELOCATABLE=y CONFIG_EFI=y CONFIG_EFI_STUB=y CONFIG_EFI=y CONFIG_EFI_STUB=y CONFIG_FB_EFI=y CONFIG_FRAMEBUFFER_CONSOLE=y # UEFI Runtime Variables Support (efivarfs filesystem - /sys/firmware/efi/efivars). This option is important as this is required to manipulate UEFI Runtime Variables using tools like /usr/bin/efibootmgr. The below config option has been added in kernel 3.10 and above. CONFIG_EFIVAR_FS=y # UEFI Runtime Variables Support (old efivars sysfs interface - /sys/firmware/efi/vars). This option should be disabled. CONFIG_EFI_VARS=n # GUID Partition Table GPT config option - mandatory for UEFI support CONFIG_EFI_PARTITION=y # Note: All of the above options are required to boot Linux via UEFI, and are enabled in Archlinux kernels in official repos. ## # # ALSO need to set this: ## CONFIG_CMDLINE_BOOL=y CONFIG_CMDLINE= ## # See # and in make menuconfig set these with Processor Type and Features - Built-in kernel command line # # Also, in installing Cups-1.6.3 the BLFS book states: # # Kernel Configuration # Note # # There is a conflict between the Cups libusb backend and the usblp kernel driver. If you want to use Cups with libusb, do not enable USB Printer support in your kernel. # # If you want to use the kernel usblp driver, enable the following options in your kernel configuration and recompile the kernel: # # If you want to use the kernel usblp driver, enable the following options in your kernel configuration and recompile the kernel: # # Device Drivers --- # [*] USB support --- # .. # In make menuconfig, get rid of the * in USB support *** Since I have not yet been successful in booting Linux 3.10.10 with UEFI, I can't comment on the above. For what it's worth. Alan Alan, thank you for validating my research. Let me validate yours. Those recommendations work. Did you see the questions I asked you earlier? I hope you will answer them. They are important to my research. I'm so close to success, I can smell it. Hopefully it won't be long and I can post everything here. It will be quite long. Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Help with Installing to UEFI Motherboard
On 11/16/2013 8:17 PM, Dan McGhee wrote: Alan, thank you for validating my research. Let me validate yours. Those recommendations work. Good! Did you see the questions I asked you earlier? I hope you will answer them. They are important to my research. Yeah, I saw them. I'm in the process of answering them, but I have to revisit a lot of stuff first, so it will take awhile. I'm so close to success, I can smell it. Hopefully it won't be long and I can post everything here. It will be quite long. We can compare notes. I've got a LOT of stuff as well. And a lot of holes left to fill. Alan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Help with Installing to UEFI Motherboard
On 11/16/2013 07:26 PM, Alan Feuerbacher wrote: On 11/16/2013 8:17 PM, Dan McGhee wrote: Alan, thank you for validating my research. Let me validate yours. Those recommendations work. Good! Did you see the questions I asked you earlier? I hope you will answer them. They are important to my research. Yeah, I saw them. I'm in the process of answering them, but I have to revisit a lot of stuff first, so it will take awhile. No rush. I'm so close to success, I can smell it. Hopefully it won't be long and I can post everything here. It will be quite long. We can compare notes. I've got a LOT of stuff as well. And a lot of holes left to fill. I have holes too. I'm looking forward to the exchange of info. Earlier on this list Geoff Swan posted. I want to verify from him that he got kernel 3.10.10 to boot from using the system Boot Manager. I'm trying to verify the need for an initrd or initramfs. Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Help with Installing to UEFI Motherboard
On 17/11/2013 11:26 AM, Dan McGhee wrote: On 11/16/2013 05:44 PM, Geoff Swan wrote: On 17/11/2013 10:10 AM, Dan McGhee wrote: On 11/16/2013 03:40 PM, Ken Moffat wrote: On Sat, Nov 16, 2013 at 02:04:31PM -0500, Alan Feuerbacher wrote: Hi, After getting the stock LFS system installed, with an MBR type boot installation, I'm experimenting with installing to a UEFI type boot location on a brand new hard drive. I've been reading a lot of online documentation, and have tried a first-cut installation, but am not having success in installing. While I can install the entire set of LFS programs, and a lot of BLFS programs, when I try to boot up, Linux fires up but quickly generates a fatal error. Is there any possibility of advice from the LFS staff? http://www.mail-archive.com/lfs-support@linuxfromscratch.org/ See the posts from Dan McGhee - most recently on 13th November, but starting on 28th October. Four threads, titles mentioning GRUB or EFI. At the moment they are all on the first page at that link, at least in firefox. Our best advice / guesses is in those threads. Dan hasn't cracked it yet, but your hardware might be different. ?en I thought I was going to be able to report success this afternoon, but as yet no joy. My efforts so far have resulted in the following conclusions: 1. There is something wrong in my grub set-up. 2. My kernel is not bootable. 3. I have missed something in the EFI info. At this point, all I want is some indication that my kernel is booting. As long as I get only one message from the kernel and the system freezes I can conclude that all else is fine except my kernel. I'm writing this e-mail on the fly and don't have my EFI sources at hand. I read last night that from the EFI partition the bootloader--in this case GRUB--doesn't know where the file system is even though it can read the partition table. Therefore, and initramfs is called for. I know nothing about these. I've read what the BLFS book has and have tried it with no success. At this point, I don't know enough to solve any gotcha's that the initramfs hint gives. Gonna try dracut. If I can't make any head-way in the next few days, I'm going to install a minimal ArchLinux system and try the various GRUB options. I don't think they sign their kernels--see last paragraph--and that will test the GRUB stuff. I cannot verify this in any documentation. It's just a hunch I have. When it comes to booting using an EFI partition, we must ignore everything we've learned about booting and using GRUB. It may be that using GRUB in a multiboot environment we cannot use the linux /boot/vmliz* root=/dev/xxx ro to get to another distro. We may have to use grub's chainloader to do that. I say this because, I have not been able to get Ubuntu to boot from my LFS-7.4 system in the old way. I was successful using the chainloader. If all this is true, then the easiest way to accomplish this is to use 'efibootmgr' or 'gummiboot' and boot everything thing we have from the EFI partition. My goal is to be able to be able to answer these questions when my testing is over. @Alan Did you remove GRUB from your MBR Protected Layer or are you still using it? Do you use an initrd or initramfs? Did you boot your kernel successfully before you started these EFI experiments? Does your failure message come from the kernel or from the LFS bootscripts? What does it say? Must you do a hard reset to start over or can you use ALT-CTRL-DEL? There is only one other option that's keeping me from booting in this environment. It's so distasteful that I don't even want to write it. But, at least in my firmware, it may be necessary for me to sign my kernel. That's not even for secure boot. I hope that's not true. Dan Dan, I could not get EFI and Grub2 to co-operate so I went for the Linux EFI image route instead and eliminated the boot manager. It is not really necessary unless you want to select from different kernels on the system. The kernel must be compiled with the EFI settings: CONFIG_EFI=y CONFIG_RELOCATABLE=y CONFIG_FB_EFI=y CONFIG_FRAMEBUFFER_CONSOLE=y CONFIG_EFI_PARTITION=y CONFIG_EFI_VARS=y CONFIG_EFI_STUB=y and also the kernel parameters built-in: CONFIG_CMDLINE=root=/dev/sda3 ro --verbose then use efibootmgr to register the new kernel image with the BIOS, so it can be selected at boot time. Geoff Geoff, your comments are giving me a break from answering questions in make oldconfig :) Just so I understand. You got your kernel--3.10.10 (?)--to boot from the EFI partition? And without initrd or initramfs? The answer to this question is important to me. Yes. 3.10.10. Selectable in the BIOS efi boot manager and boots directly, fast. No initrd or initramfs is needed, I built all the drivers required for the server hardware into the kernel. If you build modules required for
Re: [lfs-support] Help with Installing to UEFI Motherboard
On 11/16/2013 07:56 PM, Geoff Swan wrote: Just so I understand. You got your kernel--3.10.10 (?)--to boot from the EFI partition? And without initrd or initramfs? The answer to this question is important to me. Yes. 3.10.10. Selectable in the BIOS efi boot manager and boots directly, fast. No initrd or initramfs is needed, I built all the drivers required for the server hardware into the kernel. If you build modules required for boot then you have to make them available in the EFI partition too. I found it easier to build everything into the kernel. Available in a directory on the EFI partition? This might be why many, many people use initramfs. Thanks for the info, Geoff. Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
