From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 152C6C41535 for ; Fri, 22 Dec 2023 08:56:34 +0000 (UTC) Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.96.2) (envelope-from ) id 1rGbJK-0003NI-1e; Fri, 22 Dec 2023 03:55:14 -0500 Received: from mail-oi1-x233.google.com ([2607:f8b0:4864:20::233]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96.2) (envelope-from ) id 1rGbJI-0003Mw-1o for kernelnewbies@kernelnewbies.org; Fri, 22 Dec 2023 03:55:12 -0500 Received: by mail-oi1-x233.google.com with SMTP id 5614622812f47-3bb7376957eso1199149b6e.1 for ; Fri, 22 Dec 2023 00:55:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1703235292; x=1703840092; darn=kernelnewbies.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=eoI/SH18Oyx98zlOt4sDltvGNbj0a7lLSMnmBw7+3X8=; b=F76smJ1tbxXHPQQfS2X14dY+x22hodEQc9Ah8sR65EDMFXoE2kfR4EynZxdBBVCOUW VV/DkJ6zkqtANLFLM5G2rbUuxtwo/va6qr/jOgG/CY564MCre3fVFN3jCvzG4tC80cqQ HhPgMZQmIFDXO9BJahqTQRLASpRb7MRw7YVCG+d+ulbXUSOvDH0pNIJYw6n3Po4eQ/R9 tZZta141qeZnq9596+tywVWjD3fCoctdf7W7ickkkssGV78+ty3X7hUOGpidgeXytN9o GH5lj/+f9UED1lwg6f5MDhjgMgn3FfXELNrYsTdLtnbcuK132Qp5fvZNZ9g5sXZzmJv5 7smg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1703235292; x=1703840092; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=eoI/SH18Oyx98zlOt4sDltvGNbj0a7lLSMnmBw7+3X8=; b=v5fGuh1dgFvuzZzL2vXRxWGa97iHSljmBoXtbjeqjh2qiTwChzsOZRJvv9jfMsxLi9 AkKVgnb6ZlG4B1sP+CevZFzqE6xhihu0jsqnuBXiR69oOUVUnRoK31NNDIKBqvRFc+JL F06bpftBWVwu+tpt+cdQlgHZ9lqVJBdGnh/b3AAF+B1Lvt1PgRwFK1OOvp6MvarziOgp VJrO7APVo2zW9c9f6omcTLU8pAFuT3RbrH5B9tuaKkbeppXObrkvXram7do6eQvy5BOE BkC7H5bjvwedgIrFfcsa+YGG+hyYe4dYgugpML4QSp5YIGFLCwPZlHyC3wM0g/axErE7 N8ZA== X-Gm-Message-State: AOJu0YyqT0O+fnR4vMUj1h3uWXBmOq+2rpS+/VmagmmADQO9Kc4fbmqu Hjo6afTzdD2ygLSX7//wvbADerKXEDE= X-Google-Smtp-Source: AGHT+IENABqDJxAcakMdojhAAC+fFr/nmZcf/ezbt+TY+VwweG/OQfv0ry92PU5NuODTKUAXhkbkhw== X-Received: by 2002:a05:6808:3c91:b0:3b9:ef5a:e307 with SMTP id gs17-20020a0568083c9100b003b9ef5ae307mr1047638oib.24.1703235292097; Fri, 22 Dec 2023 00:54:52 -0800 (PST) Received: from negi (2603-8000-b93d-20a0-529d-8252-9670-0982.res6.spectrum.com. [2603:8000:b93d:20a0:529d:8252:9670:982]) by smtp.gmail.com with ESMTPSA id k4-20020aa792c4000000b006ce5da5956csm2898974pfa.24.2023.12.22.00.54.51 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 22 Dec 2023 00:54:51 -0800 (PST) Date: Fri, 22 Dec 2023 00:54:49 -0800 From: Soumya Negi To: Dileep Sankhla Subject: Re: Boot stucks at "Loading initial ramdisk" Message-ID: References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: Cc: kernelnewbies@kernelnewbies.org X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kernelnewbies-bounces@kernelnewbies.org Hi Dileep, On Thu, Dec 21, 2023 at 05:58:23PM +0530, Dileep Sankhla wrote: > Hello, > > I have cloned and built the latest rc kernel using the default config but > on boot, it stucks at "Loading initial ramdisk". I have tried booting after > removing the "quiet" option from the kernel parameters just before > selecting the kernel from the grub menu. I have also tried adding > "dis_ucode_ldr" parameter to the initial parameters but all in vain. > > How to look for the underlying issue and solve it? > > Regards, > Dileep I had this issue as well. I found a solution on stackexchange(..I think) that I wanted to link here.. but can't seem to find it now. For reference, I was using Ubuntu. This was my case: * Possible reason - initrd.img file is too large I checked the size of initrd.img- at /boot. The file was ~500mb, much larger than the initrd for the kernel that came with Ubuntu(~40mb) * Possible solution - Before installing the kernel, change MODULES=most to MODULES=dep in /etc/initramfs-tools/initramfs.conf to generate smaller initrd.img files. The new initrd's for all other kernels I have installed afterwards have been ~55MB. Regards, Soumya Negi _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies