Loading Initial Ramdisk... and my boot freezes
Hey Guys!!
I updated my grub in my ubuntu 20.04 after building my new kernel which is version 5.8.18. After this process, I checked my /boot directory the initrd.img-5.8.18 was also present. But once I boot into this kernel. I get "Loading Initial RamDisk ..." and my boot freezes. Anybody can help me out please.. I have been held up here for more than a week. I tried building around 5 kernels. Every time I build it, boot freezes and same issue pertains. Thanks in advance . My mail id is sudesh.skofficial@gmail.com
Comments
-
one possibility is you do not have the proper disk drivers. This is particularly true if you are building in a hypervisor as they have various ideas of what to use. Building from your own custom kernel can be a non-trivial process. If you are lucky enough to get it right the first time or two, great. Otherwise, you should start from a working configuration and then try to get rid of stuff you don't need.
If you boot into the Ubuntu stock kernel and then go to the custom kernel building directory, I would do:
cp .config .config_MINETOSAVE
make localmodconfig
(answer all questions asked, usually just take the default by hitting return)and then whatever you do to compile and install, such as:
make -j 4 && make modules_install && make install
(or whatever your procedure is).The make localmodconfig should make sure you are getting all the modules built you currently are running.
0 -
make that "mv .config .config_MINETOSAVE" so you are clearly starting over, and once it works you can add and subtract tot he
configuration0 -
@coop said:
make that "mv .config .config_MINETOSAVE" so you are clearly starting over, and once it works you can add and subtract tot he
configuration@coop said:
one possibility is you do not have the proper disk drivers. This is particularly true if you are building in a hypervisor as they have various ideas of what to use. Building from your own custom kernel can be a non-trivial process. If you are lucky enough to get it right the first time or two, great. Otherwise, you should start from a working configuration and then try to get rid of stuff you don't need.If you boot into the Ubuntu stock kernel and then go to the custom kernel building directory, I would do:
cp .config .config_MINETOSAVE
make localmodconfig
(answer all questions asked, usually just take the default by hitting return)and then whatever you do to compile and install, such as:
make -j 4 && make modules_install && make install
(or whatever your procedure is).The make localmodconfig should make sure you are getting all the modules built you currently are running.
Hello Coop!
Actually before using the commands, 1. make -j 4 2. make modules_install and 3. make install, I did "cp /boot/config-uname -r
.config" to copy the old configurations and then did "yes ' ' | make oldconfig" After this I may need make menuconfig to customize my kernel because I don't need so many drivers, etc. Once after all this is done, I am doing 1. , 2. and 3. I also went into my "grub.cfg" to see if something is different for the custom built kernel from the one which is perfectly booting. Everything is the same. I also checked /boot directory. All the necessary files are created for boot say for eg, 1. vmlinuz-5.8.18, 2.initrd.img-5.8.18, 3. System.map-5.8.18 and 4. config-5.8.18. I will also try the above steps that you have mentioned and check if it works. What does the "cp .config .config_MINETOSAVE" mean? Am I copying my current .config file, and where should I move or copy it to? Thanks a ton, Coop! Have a great day0 -
the .config_MINETOSAVE just means keep a copy of your old config in case you want to resurrect it, nothing special about the name. You did indeed follow a good procedure. The only suggestion I would make is:
1) Starting with the Ubuntu working kernel config, do not customize the kernel to eliminate un-needed drivers before you recompile. Yes it will take infinity to compile, but this makes sure you did not inadvertently excise something needed. This approach rarely fails.
2) You could also try starting with NO config file at all and do "make localmodconfig" which should compile only drivers in current use. You might try this first as it is faster
Also you have not said if this is a VM or an actual physical machine. The kind of errors you report often happen with VirtualBox in particular which sometimes makes funny choices for disk drivers.
Sometimes the new distros are a little weird. Fedora 33 now requires you have "zram" enabled in the kernel configuration as it uses it by default for swap. I found this out the hard way, with configurations that had always worked before refusing to boot.
Hope this is helpful. Good luck!
1 -
@coop said:
the .config_MINETOSAVE just means keep a copy of your old config in case you want to resurrect it, nothing special about the name. You did indeed follow a good procedure. The only suggestion I would make is:1) Starting with the Ubuntu working kernel config, do not customize the kernel to eliminate un-needed drivers before you recompile. Yes it will take infinity to compile, but this makes sure you did not inadvertently excise something needed. This approach rarely fails.
2) You could also try starting with NO config file at all and do "make localmodconfig" which should compile only drivers in current use. You might try this first as it is faster
Also you have not said if this is a VM or an actual physical machine. The kind of errors you report often happen with VirtualBox in particular which sometimes makes funny choices for disk drivers.
Sometimes the new distros are a little weird. Fedora 33 now requires you have "zram" enabled in the kernel configuration as it uses it by default for swap. I found this out the hard way, with configurations that had always worked before refusing to boot.
Hope this is helpful. Good luck!
My entire procedure is mentioned below, sir.
I updated my grub in my ubuntu 20.04 after building my new kernel which is version 5.8.18. After this process, I checked my /boot directory the following were present,
vmlinuz-5.8.18
initrd.img-5.8.18
System.map-5.8.18 and
config-5.8.18.
In /var/lib/initramfs-tools/ my 5.8.18 file is present. So I don't know where am doing wrong.
But once I boot into this kernel. I get "Loading Initial RamDisk ..." and my boot freezes. Anybody can help me out please.. I have been held up here for more than a week. I tried building around 5 kernels. Every time I build it, boot freezes and same issue pertains.
Do the linux-headers-version play a vital role in loading the temporary root file system into the initial ramdisk during the boot process. Because my current working kernel which is "5.4.0-53-generic" has a "linux-headers-5.4.0-53-generic directory" in the /usr/src location.
I used the following commands to build my kernel,
mkdir kernel
cd kernel
git clone -b linux-5.8.y git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
cd linux-stable/
make mrproper
cp /boot/config-uname -r .config
yes '' | make oldconfig
make menuconfig
make -j 4
make modules_install
make install
cd /boot; mkinitramfs -k 5.8.18 -o initrd.img-5.8.18
sudo update-grub
My mail id is sudesh.skofficial@gmail.com Thanks in advance .
I am using Mi Notebook 14 from Xaomi which is an Intel Core i5 system and it is not a Virtual Machine, sir.
0 -
Check and see if you have CONFIG_DECOMPRESS_LZ4 compiled static. If you see CONFIG_DECOMPRESS_LZ4=y - you are good. You might have to recompile your older kernels with CONFIG_DECOMPRESS_LZ4 as a static.
0
Categories
- All Categories
- 212 LFX Mentorship
- 212 LFX Mentorship: Linux Kernel
- 753 Linux Foundation IT Professional Programs
- 345 Cloud Engineer IT Professional Program
- 169 Advanced Cloud Engineer IT Professional Program
- 72 DevOps Engineer IT Professional Program
- 136 Cloud Native Developer IT Professional Program
- 136 Express Training Courses
- 136 Express Courses - Discussion Forum
- 6.1K Training Courses
- 44 LFC110 Class Forum - Discontinued
- 70 LFC131 Class Forum
- 42 LFD102 Class Forum
- 225 LFD103 Class Forum
- 18 LFD110 Class Forum
- 36 LFD121 Class Forum
- 18 LFD133 Class Forum
- 7 LFD134 Class Forum
- 18 LFD137 Class Forum
- 71 LFD201 Class Forum
- 4 LFD210 Class Forum
- 5 LFD210-CN Class Forum
- 2 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum - Discontinued
- 2 LFD233 Class Forum
- 4 LFD237 Class Forum
- 24 LFD254 Class Forum
- 692 LFD259 Class Forum
- 111 LFD272 Class Forum
- 4 LFD272-JP クラス フォーラム
- 12 LFD273 Class Forum
- 133 LFS101 Class Forum
- 1 LFS111 Class Forum
- 3 LFS112 Class Forum
- 2 LFS116 Class Forum
- 4 LFS118 Class Forum
- 4 LFS142 Class Forum
- 5 LFS144 Class Forum
- 4 LFS145 Class Forum
- 2 LFS146 Class Forum
- 3 LFS147 Class Forum
- LFS148 Class Forum
- 15 LFS151 Class Forum
- 2 LFS157 Class Forum
- 23 LFS158 Class Forum
- 6 LFS162 Class Forum
- 2 LFS166 Class Forum
- 4 LFS167 Class Forum
- 3 LFS170 Class Forum
- 2 LFS171 Class Forum
- 3 LFS178 Class Forum
- 3 LFS180 Class Forum
- 2 LFS182 Class Forum
- 5 LFS183 Class Forum
- 31 LFS200 Class Forum
- 737 LFS201 Class Forum - Discontinued
- 3 LFS201-JP クラス フォーラム
- 18 LFS203 Class Forum
- 125 LFS207 Class Forum
- 2 LFS207-DE-Klassenforum
- 1 LFS207-JP クラス フォーラム
- 302 LFS211 Class Forum
- 56 LFS216 Class Forum
- 52 LFS241 Class Forum
- 48 LFS242 Class Forum
- 38 LFS243 Class Forum
- 15 LFS244 Class Forum
- 2 LFS245 Class Forum
- LFS246 Class Forum
- 48 LFS250 Class Forum
- 2 LFS250-JP クラス フォーラム
- 1 LFS251 Class Forum
- 150 LFS253 Class Forum
- 1 LFS254 Class Forum
- 1 LFS255 Class Forum
- 7 LFS256 Class Forum
- 1 LFS257 Class Forum
- 1.2K LFS258 Class Forum
- 10 LFS258-JP クラス フォーラム
- 117 LFS260 Class Forum
- 159 LFS261 Class Forum
- 42 LFS262 Class Forum
- 82 LFS263 Class Forum - Discontinued
- 15 LFS264 Class Forum - Discontinued
- 11 LFS266 Class Forum - Discontinued
- 24 LFS267 Class Forum
- 21 LFS268 Class Forum
- 30 LFS269 Class Forum
- 201 LFS272 Class Forum
- 2 LFS272-JP クラス フォーラム
- 1 LFS274 Class Forum
- 4 LFS281 Class Forum
- 9 LFW111 Class Forum
- 259 LFW211 Class Forum
- 181 LFW212 Class Forum
- 13 SKF100 Class Forum
- 1 SKF200 Class Forum
- 1 SKF201 Class Forum
- 795 Hardware
- 199 Drivers
- 68 I/O Devices
- 37 Monitors
- 102 Multimedia
- 174 Networking
- 91 Printers & Scanners
- 85 Storage
- 757 Linux Distributions
- 82 Debian
- 67 Fedora
- 16 Linux Mint
- 13 Mageia
- 23 openSUSE
- 148 Red Hat Enterprise
- 31 Slackware
- 13 SUSE Enterprise
- 353 Ubuntu
- 468 Linux System Administration
- 39 Cloud Computing
- 71 Command Line/Scripting
- Github systems admin projects
- 93 Linux Security
- 78 Network Management
- 102 System Management
- 47 Web Management
- 61 Mobile Computing
- 18 Android
- 31 Development
- 1.2K New to Linux
- 1K Getting Started with Linux
- 369 Off Topic
- 114 Introductions
- 173 Small Talk
- 21 Study Material
- 741 Programming and Development
- 301 Kernel Development
- 422 Software Development
- 1.8K Software
- 236 Applications
- 182 Command Line
- 3 Compiling/Installing
- 985 Games
- 316 Installation
- 92 All In Program
- 92 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)