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 6DD3413888F for ; Wed, 7 Oct 2015 21:00:35 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8FEC8E0855; Wed, 7 Oct 2015 21:00:24 +0000 (UTC) Received: from smtp16.openmailbox.org (smtp16.openmailbox.org [62.4.1.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 68E8EE0807 for ; Wed, 7 Oct 2015 21:00:23 +0000 (UTC) Received: by mail2.openmailbox.org (Postfix, from userid 1002) id A59517C0F68; Wed, 7 Oct 2015 23:00:21 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=openmailbox.org; s=openmailbox; t=1444251620; bh=BilaZPdM01/g+jhttuitF9sy08kJOU5OyUlXy28ZfI4=; h=Date:From:To:Subject:References:In-Reply-To:From; b=Co/UiYsptn8arBDutEq4YWH0JmmJ0d9I1Rpa8yn4cbve58eav8oiu6Yt4wz07PWKI c41BitObKoJVuwKIZe5XtEQjTK0a7tIPkgTdFc0t7OwSL/spruRtMnNLjNoXhpppnE L3IkS6g9AqZW53w9itfHiTR09+4O7ZPWyXk+KPw8= X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on openmailbox-b1 X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,NO_RECEIVED,NO_RELAYS autolearn=no autolearn_force=no version=3.4.0 Date: Wed, 7 Oct 2015 22:00:01 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=openmailbox.org; s=openmailbox; t=1444251610; bh=BilaZPdM01/g+jhttuitF9sy08kJOU5OyUlXy28ZfI4=; h=Date:From:To:Subject:References:In-Reply-To:From; b=egIMTTyo0lz8oPEYNSvoaJH4HtKVG3UXtW2T9rHiFMF4C1+IpgulU19GgI3fksHDV j5ZHh/D7qw3ZstzSm9TkpLfdLdJ5s13KfvnpqHPZLHJU8eWR6pChwRPFYkEQ3PZbv1 GQ0Lm1NpExGwJO3MV4/JMc+zhsMmyBZzLCwkjbyU= From: =?utf-8?B?Sm/Do28=?= Miguel To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Root device as UUID not properly detected Message-ID: <20151007210001.GA4785@jmcf125-Acer-Arch.home> References: <20151006155925.GC2629@jmcf125-Acer-Arch.home> <1859238.rYv69SYfrM@andromeda> <20151006220304.GF2629@jmcf125-Acer-Arch.home> <4419537.08q3Ys9htG@andromeda> 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 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <4419537.08q3Ys9htG@andromeda> X-Archives-Salt: 8e82977f-ebd4-4d5c-9acc-7cf53c85546e X-Archives-Hash: 2ec89d8a2c3bdc1f8867b52e0b7ad16b On Wed, Oct 07, 2015 at 12:17:51PM +0200, J. Roeleveld wrote: > > > > > 2. USB port is not supported by kernel > > > > I'm not sure what you mean. Is there any option I should enable for > > > > genkernel? I read on the Wiki page that > > > It works with Arch, are you using the same kernel options now with Gentoo? > > Yeah, I tried many more here actually, with Arch I only need APPEND root=... > > (no rootfstype, ro, rw, rootdelay, etc.). > What about kernel config? I was not sure about this, but https://wiki.archlinux.org/index.php/Kernel_parameters says: There are three ways to pass options to the kernel and thus control its behaviour: 1. When building the kernel. See Kernel Compilation for details. 2. When starting the kernel (usually, when invoked from a boot loader). 3. At runtime (through the files in /proc and /sys). See sysctl for details. So I'm using 2. > > > > > 3. You don't use root_delay as boot option > > > > If that's what I think it is, I tell syslinux to wait 5 seconds. > > (turns out it's not what I thought it was, though I did try root_delay, it > > is actually rootdelay...) > > > How do you tell it that? > > Here's my syslinux.cfg with more comments: > > PROMPT 1 > > TIMEOUT 50 # <-- here > That timeout is for the prompt, eg. how long the bootloader waits. Yes, but I do tell it to wait (and as I said, I didn't know what rootdelay was). > It will not have any effect for the drivers in the kernel to finish detecting > the USB devices. > > APPEND rootdelay=5 root=UUID="6fc386ff-8342-42a2-be02-51a6eccf8430" rootfstype=ext4 No, but this ------^^^^^^^^^^^-- should. > Did you test with the PARTUUID value ("9c...") instead of the other one? > > Also, I always ended up setting the rootdelay to 10 or higher. (It's in > seconds, not minutes) New append line: APPEND rootdelay=15 root=PARTUUID="9c4f6479-9dd7-4a8f-86f2-f1320cc15aa5" rootfstype=ext4 Again, I see no difference using rootdelay. With PARTUUID though, I get "Could not find the root device in ." right away, rather than "Could not find the root device in UUID=...". With PARTUUID, I can't boot it anywhere without manually writing the UUID (not PARTUUID) or device file. Though on my system, the following works: # mount PARTUUID="9c4f6479-9dd7-4a8f-86f2-f1320cc15aa5" /mnt/pen So now I'm even more confused. Everything about this pen works, as does everything in the PCs I tried. Syslinux also works. It's somewhere after loading the modules, in the initrd. Thinking of it now, I remember the PC that never finds the root device requires intel microcode early, which is loaded along with the initrd. Because of this problem I need to turn many PCs on and off a few times in a row, and I noticed that the pendrive blinks at least on BIOS, when syslinux is finding initrd and the kernel, and when the machine finds the root device. Now, what I noticed is that in the VM, it blinks right away (as it finds root right away); in many PCs it takes a while to blink, only blinking after the 1st attempt on mounting to newroot has been done; and in some others it never blinks. > > > I never used an initrd when building my own USB sticks. > > I don't know, I always used an initrd. Though I must say, that is the > > phase of starting the PC I understand the worst. > On the machines where I use an initrd, I write my own scripts as I find the > creators (genkernel, dracut) to not be intelligent enough. The thing is, I'm less intelligent than those creators. I'm not very familiar with the way that early boot phase works, much less with writing scripts to make it work. Unless you have an idea of how I can use the scripts to solve this problem. In Arch I use mkinitcpio. I'm aware it is available for Gentoo as well, nonetheless using genkernel is killing two birds with one stone, it should be a simpler solution, so I'd like to go with that one. If it works for a Gentoo recovery drive, why shouldn't it work for this one? > > > I was talking about: > > > rootdelay= [KNL] Delay (in seconds) to pause before > > > attempting to > > > mount the root filesystem > > > (See the file "kernel-parameters.txt" in the kernel Documentation) > > (I'm guessing I'm not supposed to include this in the boot loader config...) > The "rootdelay=..." part needs to be added to the boot loader config. Ah, then I'm glad I did. Although it seems to do nothing really... Sorry for the large response. I probably forgot something, took a while amidst writing and testing. João Miguel