linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 118401] Lenovo A740 gave up waiting for root device with kernels >= 4.3
Date: Wed, 01 Jun 2016 15:26:21 +0000	[thread overview]
Message-ID: <bug-118401-13602-WHKkuMLJHF@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-118401-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=118401

--- Comment #10 from Kevin Brubeck Unhammer <unhammer+dill@mm.st> ---
Sorry for the late reply – I still haven't been able to get keyboard working in
initramfs, so not much more useful information :(


I did try running blkid from an initramfs script:


$ cat /etc/initramfs-tools/scripts/init-premount/kbu-blkid
#!/bin/sh
PREREQ=""
prereqs()
{
     echo "$PREREQ"
}
case $1 in
prereqs)
     prereqs
     exit 0
     ;;
esac
echo "KBU"
blkid
echo "/KBU"
$ sudo  update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.6.0-040600rc6-generic


but that just shows

   running /scripts/init-premount ... KBU
   /KBU

as if the "blkid" command had no output. Is there something more useful I could
put in there? 

Would it be useful at all to compile a kernel with debug symbols as in
https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel#Debug_Symbols or if I change
some other configuration options? (I don't really know what I should change
though, since CONFIG_EXT4_USE_FOR_EXT2 is already tested as per the config
diff).

-- 
You are receiving this mail because:
You are watching the assignee of the bug.--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2016-06-01 15:26 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-18 11:41 [Bug 118401] New: Lenovo A740 gave up waiting for root device with kernels >= 4.3 bugzilla-daemon
2016-05-18 16:02 ` [Bug 118401] " bugzilla-daemon
2016-05-19  8:40 ` bugzilla-daemon
2016-05-19  8:42 ` bugzilla-daemon
2016-05-19  8:43 ` bugzilla-daemon
2016-05-19  8:56 ` bugzilla-daemon
2016-05-24 13:07 ` bugzilla-daemon
2016-05-24 14:37 ` bugzilla-daemon
2016-05-24 17:46 ` bugzilla-daemon
2016-05-31  5:51 ` bugzilla-daemon
2016-06-01 15:26 ` bugzilla-daemon [this message]
2016-06-01 16:02 ` bugzilla-daemon
2016-06-01 18:53 ` bugzilla-daemon
2016-06-01 21:50 ` bugzilla-daemon
2016-06-02 10:28 ` bugzilla-daemon
2016-06-02 12:52 ` bugzilla-daemon
2016-06-02 18:19 ` bugzilla-daemon
2016-06-03 19:03 ` bugzilla-daemon
2016-06-03 19:04 ` bugzilla-daemon
2016-06-03 19:07 ` bugzilla-daemon
2016-06-03 19:08 ` bugzilla-daemon
2016-06-04  6:28 ` bugzilla-daemon
2016-06-04  9:36 ` bugzilla-daemon
2016-06-04 13:45 ` bugzilla-daemon
2016-06-04 22:05 ` bugzilla-daemon
2016-06-05  1:46 ` bugzilla-daemon
2016-06-05 11:12 ` bugzilla-daemon
2016-06-05 11:14 ` bugzilla-daemon
2016-06-05 12:21 ` bugzilla-daemon
2016-06-05 13:43 ` bugzilla-daemon
2016-06-06  7:27 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-118401-13602-WHKkuMLJHF@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).