From: Bryan Brattlof <hello@bryanbrattlof.com>
To: Yashodhan Joshi <yjdoc2@gmail.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Compiled Kernel stuck in booting
Date: Wed, 29 Jul 2020 21:02:39 +0000 [thread overview]
Message-ID: <87lfj2f314.fsf@bryanbrattlof.com> (raw)
In-Reply-To: <20200729085148.GA6481@yj-ideapad>
On 2020-07-29T04:51:48-0400 Yashodhan Joshi <yjdoc2@gmail.com> wrote:
> Hello,
>
Hi Yashodhan:
Sorry to send this to you again, somehow I dropped the mailing list from
the email
>
> I use a dual boot laptop with windows and Ubuntu,with grub2.
>
> I Followed the instruction in https://kernelnewbies.org/OutreachyfirstpatchSetup to clone the source code and compile the kernel, which was done without any errors.
> When I tried to install the kernel using 'sudo make modules_install install' it showed a warning when updating initramfs, that it will attempt to resume from UUID, which is my SWAP space,
> but other than that it showed no other errors.
>
> When I tried to boot into it from the grub menu after restarting, it showed message of loading the kernel and then 'setting up intitial ramdisk', after which nothing further happend.
> The default kernel that came with ubuntu is still working and boots up into desktop environment withing 2-3 minutes after the 'ramdisk' message,
> but even though I kept the system running for 20 minutes after the 'ramdisk' message for the compiled kernel, niether any further proccess seems to be happening nor any error messages are shown.
> Can someone help me figuring out what is wrong and how can I run the kernel?
>
> Thank You.
>
I'm fairly new to this myself, however with my Debian/Ubuntu based
system, I have had success using:
$ make -j `getconf _NPROCESSORS_ONLN` deb-pkg
to compile the kernel into a few debian package that we can then install
using something like:
$ sudo dpkg -i *.deb
>
> Also can someone point me in right direction to send suggestions about updating the information on kernelnewbies website?
> The information about connecting mutt to Gmail is quite outdated, and I would like to help updating it.
>
>
Sorry I can't help you here
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Hope this helps
--
~Bryan
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2020-07-29 21:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 8:51 Compiled Kernel stuck in booting Yashodhan Joshi
2020-07-29 21:02 ` Bryan Brattlof [this message]
2020-09-23 0:17 ` jim.cromie
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=87lfj2f314.fsf@bryanbrattlof.com \
--to=hello@bryanbrattlof.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=yjdoc2@gmail.com \
/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).