<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Boot on Siddharth Mishra</title><link>http://brightprogrammer.in/tags/boot/</link><description>Recent content in Boot on Siddharth Mishra</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 13 Jun 2026 09:04:24 -0700</lastBuildDate><atom:link href="http://brightprogrammer.in/tags/boot/index.xml" rel="self" type="application/rss+xml"/><item><title>System Boot</title><link>http://brightprogrammer.in/posts/system-boot/</link><pubDate>Sat, 08 Jan 2022 00:00:00 +0000</pubDate><guid>http://brightprogrammer.in/posts/system-boot/</guid><description>&lt;p>This will be a post on what actually happens when a system boots up.&lt;/p>
&lt;p>When system boots up motherboard first checks if all necessary components are attached or not. If they are not then it shows it&amp;rsquo;s tantrums that one needs to debug. Motherboard first initialises it&amp;rsquo;s firmware, i.e the chipset and other things needed for normal startup.&lt;/p>
&lt;p>Then the control is sent to the bootloader that is responsible for further initialisation of kernel which ultimately loads the complete OS. If on a multicore processor, one of the core is chosen dynamically (the bootstrap processor : BSP) and is given the responsibility to run the code for bootloader and kernel. The remaining cores remain halted unless being used explicitly by kernel or bootloader.&lt;/p></description></item></channel></rss>