From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id E808F158086 for ; Wed, 17 Nov 2021 23:24:55 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A83702BC00A; Wed, 17 Nov 2021 23:24:50 +0000 (UTC) Received: from mail-qv1-f42.google.com (mail-qv1-f42.google.com [209.85.219.42]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 92A16E0922 for ; Wed, 17 Nov 2021 23:24:49 +0000 (UTC) Received: by mail-qv1-f42.google.com with SMTP id b11so3216988qvm.7 for ; Wed, 17 Nov 2021 15:24:49 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:subject:to:mime-version:references :in-reply-to:message-id:content-disposition :content-transfer-encoding; bh=filNI5UNj7Gggx91yYpPGOwE+BU/CROxb9+hI0M/lzY=; b=JGbNV8r5iV8unmYNKpoPaHy5HPCbCmyEXKYdZ/USQkhb8mEsJVADkGkjUnos2UA+Yu bxa2jw1MSkR5Rke8XgIbLVSk25tCGujV99sdt2VqXKjfi1/unUZBmYiS943XC3DhjW2u VEVeUYxCZBWty1hdhW3MXlpz34FMqgqGgU5ZhhCMf2nczfqJjcOBMMn8XG71gl7+o34d i2UrNp/EMpFEYkU8vFQg9JOMUcwVMDtKN/t8RSjThe4xeQF1IizhHKZVNlUZzgBAbGMO LxStmk8fJxw5eTbam5epxqvHoWNuOrNuonfM3A8nLc2JuRnS1Pk+OgCyqfsqT44AM9Nx BeIQ== X-Gm-Message-State: AOAM5309c2u0kwmiWW29PjCaiZ1/ex/wipT5slAm/VysHckLTlbeRa/C QEkRWoN0AupsgfVxJLWHfj4lT2O54PqsHXvt X-Google-Smtp-Source: ABdhPJyku6VM5edbAkd2MEn37jkIfdXxNH+JMSMmusj/FD+ol/o+3uMT0yfvEtyylXoS6KW7FeMEkA== X-Received: by 2002:a0c:fa07:: with SMTP id q7mr59596519qvn.18.1637191488312; Wed, 17 Nov 2021 15:24:48 -0800 (PST) Received: from ffortso9 (c-76-23-130-96.hsd1.ct.comcast.net. [76.23.130.96]) by smtp.gmail.com with ESMTPSA id l2sm707928qtk.41.2021.11.17.15.24.47 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 17 Nov 2021 15:24:48 -0800 (PST) Date: Wed, 17 Nov 2021 18:24:46 -0500 From: Jack Subject: Re: [gentoo-user] Why has genkernel initramfs changed behaviour!? To: gentoo-user@lists.gentoo.org Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 References: In-Reply-To: X-Mailer: Balsa 2.6.3-real-16-g1a34f0517 Message-Id: Content-Type: text/plain; charset=us-ascii; DelSp=Yes; Format=Flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable X-Archives-Salt: a5513e00-efa5-4d10-9b2a-2bd98598c571 X-Archives-Hash: 92a450fdff4f5cebd8c8ef1dec578fe3 On 2021.11.17 18:15, Wol wrote: > Just filed bug 824282. >=20 > In the past, I've always done "make kernel, make kernel_modules, make =20 > install, make modules_install, genkernel initramfs ...". >=20 > This worked fine, and I then ran grub-mkconfig, sorted out grub.cfg, =20 > and all was well. >=20 > My new setup, I have a /boot WHICH I WANT TO SORT OUT MYSELF! I got =20 > thoroughly confused because genkernel was finding /boot in fstab, =20 > mounting it by default, and sticking the initramfs there. So of =20 > course, grub-mkconfig screwed up because the kernel was in the /boot =20 > directory, but the initramfs was in the /boot partition! >=20 > So I told genkernel not to mount the boot partition ... >=20 > WAH WAH WAH FATAL ERROR YOU WON'T LET ME MOUNT BOOT SULK SULK SULK. >=20 > If I tell it not to mount boot then that's my lookout, not for =20 > genconfig to nanny me and sulk! >=20 >=20 > And it gets worse. I've always done "make modules_install, genkernel =20 > initramfs". Which now seems to be an unsupported option. genkernel is =20 > now looking in /var/tmp/genkernel/... for the modules - no surprise =20 > the modules aren't there! The error says "did you forget to compile =20 > the kernel" - no I didn't - it is compiled, the modules are =20 > installed, I just didn't use genkernel to do it. >=20 > Why oh why does everything change ... for the worse ... now let's see =20 > if allowing it to mount the boot partition makes it work properly ... >=20 > and allowing it to mount boot made everything work perfectly afaict =20 > ... what a mess ... >=20 > Cheers, > Wol I have no problem telling genkernel not to mount ./boot, but then I =20 always have /boot mounted, so I suppose it might not complain only =20 because it's set up the way it wants it anyway. I also use genkernel to compile the kernel and modules, but I do "make =20 xconfig" to set my own choice of options, and tell genkernel to skip =20 any of that configuring. I've had no problems with doing it that way. =20 if you want, I can send you a copy of my genkernel.conf. I launch it =20 with "genkernel --no-gpg --lvm --firmware --microcode =20 --kernel-append-localversion=3D$1 all | tee genkern.log 2>&1" so I can =20 have multiple versions of the same kernel version (usually because I =20 want to test some different setting, but don't want the original to be =20 overwritten in case the new version doesn't work or just doesn't do =20 what I want. Jack