All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aditya Gupta <adityag@linux.ibm.com>
To: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
Cc: Soumya Negi <soumya.negi97@gmail.com>,
	Dileep Sankhla <dileepsankhla.ds@gmail.com>,
	kernelnewbies@kernelnewbies.org
Subject: Re: Boot stucks at "Loading initial ramdisk"
Date: Fri, 5 Jan 2024 15:18:42 +0530	[thread overview]
Message-ID: <a3fa2813-3bcd-420b-a12e-ac2bc83d22c2@linux.ibm.com> (raw)
In-Reply-To: <349166.1704447165@turing-police>

On 05/01/24 15:02, Valdis Klētnieks wrote:

> On Fri, 05 Jan 2024 10:42:53 +0530, Aditya Gupta said:
>
>> It's a good start to use the distro config for building a kernel.
>> PS. I have been able to successfully boot by building with defconfig, then
>> manually enabling some drivers according to error messages during boot,
> 'make localmodconfig' is your friend.
>
> Make sure to plug in all your various USB or bluetooth  etc devices first,
> so their driver modules get loaded.

Yes, I use it. Thanks for suggesting that Valdis.

Thanks,
Aditya Gupta


_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2024-01-05  9:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-21 12:28 Boot stucks at "Loading initial ramdisk" Dileep Sankhla
2023-12-22  5:22 ` Valdis Klētnieks
2023-12-22 11:21   ` Dileep Sankhla
2023-12-22  6:54 ` Bagas Sanjaya
2023-12-22 11:32   ` Dileep Sankhla
2023-12-22  8:54 ` Soumya Negi
2023-12-22 11:37   ` Dileep Sankhla
2024-01-01 11:16     ` Dileep Sankhla
2024-01-05  5:12       ` Aditya Gupta
2024-01-05  8:16         ` Dileep Sankhla
2024-01-05  9:32         ` Valdis Klētnieks
2024-01-05  9:48           ` Aditya Gupta [this message]
2024-01-05  9:58           ` Dileep Sankhla

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=a3fa2813-3bcd-420b-a12e-ac2bc83d22c2@linux.ibm.com \
    --to=adityag@linux.ibm.com \
    --cc=dileepsankhla.ds@gmail.com \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=soumya.negi97@gmail.com \
    --cc=valdis.kletnieks@vt.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.