From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id CF21A1381F4 for ; Sun, 9 Dec 2012 23:22:03 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 086D521C06F; Sun, 9 Dec 2012 23:21:44 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 4077D21C00B for ; Sun, 9 Dec 2012 23:21:08 +0000 (UTC) Received: from [192.168.178.26] (e178077189.adsl.alicedsl.de [85.178.77.189]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: chithanh) by smtp.gentoo.org (Postfix) with ESMTPSA id E294333DBDC for ; Sun, 9 Dec 2012 23:21:06 +0000 (UTC) Message-ID: <50C51CF9.9080201@gentoo.org> Date: Mon, 10 Dec 2012 00:21:29 +0100 From: =?UTF-8?B?Q2jDrS1UaGFuaCBDaHJpc3RvcGhlciBOZ3V54buFbg==?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Firefox/17.0 SeaMonkey/2.14 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] borked release media References: <4nm3duwfogrmr8l1fiioxotg.1355073688356@email.android.com> <50C4DCA3.6010402@gentoo.org> <20121209185719.GA6595@kroah.com> In-Reply-To: <20121209185719.GA6595@kroah.com> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Archives-Salt: 15aef2a9-bda0-4f4a-a377-ec92e832ba9d X-Archives-Hash: c6657a861efbe0cd21b3b74b663f72ea Greg KH schrieb: >> No, all we need is to enable EFI stub support in the kernel, and >> integrate the initramfs using CONFIG_INITRAMFS_SOURCE and place it in >> some location where UEFI looks for it (/efi/boot/bootx64.efi). >> >> This has the disadvantage of not allowing to pass additional kernel >> parameters during boot. But it might still be an acceptable stopgap >> measure if the alternative is to not boot at all. > > No, don't do that for an "install" kernel, that way is madness, just use > a real UEFI bootloader which can handle an initrd and the like properly Can you explain what problems you see with that? How does CONFIG_INITRAMFS_SOURCE handle initrd improperly? > Only boot a kernel directly from UEFI if you build your own and have > customized it for your hardware. I booted genkernel generated non-customized kernels as well as customized hand-configured kernels using that method. Best regards, Chí-Thanh Christopher Nguyễn