<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Stuporglue.org &#187; drivers</title>
	<atom:link href="http://stuporglue.org/tag/drivers/feed/" rel="self" type="application/rss+xml" />
	<link>http://stuporglue.org</link>
	<description>Programming, Rambling and More!</description>
	<lastBuildDate>Tue, 24 Jan 2012 04:18:54 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Creating a custom initrd.img</title>
		<link>http://stuporglue.org/creating-a-custom-initrd-img/</link>
		<comments>http://stuporglue.org/creating-a-custom-initrd-img/#comments</comments>
		<pubDate>Sun, 14 Mar 2010 13:44:26 +0000</pubDate>
		<dc:creator>stuporglue</dc:creator>
				<category><![CDATA[Computers]]></category>
		<category><![CDATA[busybox]]></category>
		<category><![CDATA[drivers]]></category>
		<category><![CDATA[initrd]]></category>
		<category><![CDATA[ubuntu]]></category>

		<guid isPermaLink="false">http://stuporglue.org/?p=11</guid>
		<description><![CDATA[If Ubuntu installed, tries to boot, but fails, you probably are missing some important driver. To have a driver available at boot time, you'll need to rebuild initrd.img. It's a gzipped cpio file now, and this is how to build it on Ubuntu. Any tutorial that you find using ramfs or cramfs doesn't apply to the Ubuntu initrd! <a href="http://stuporglue.org/creating-a-custom-initrd-img/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>If Ubuntu installed, tries to boot, but fails, you probably are missing some important driver. To have a driver available at boot time, you&#8217;ll need to rebuild initrd.img. It&#8217;s a gzipped cpio file now, and this is how to build it on Ubuntu. Any tutorial that you find using ramfs or cramfs doesn&#8217;t apply to the Ubuntu initrd!</p>
<p><span style="color: #ff0000;">This page is OLD and probably contains errors, out of date information, security flaws or other problems. I am keeping it around because it might be helpful to someone.</span></p>
<p>This assumes your boot failed, and you landed in busbox. Busybox is a mini all-in-one shell. It&#8217;s good enough for our purposes.  1) From the busybox shell, check if the device you can&#8217;t access shows up in /dev. If it doesn&#8217;t, this tutorial is what you&#8217;re looking for. Figgure out what modules you need to load. Alternate between modprobing and starting udev again until the devices show up.</p>
<p>For OldWorld Macs, try these modules: mesh, mace, sd_mod, mac53c94.</p>
<p># modprobe mesh<br />
# modprobe sd_mod<br />
# udevstart<br />
# ls /dev</p>
<p>2) mount the root partition and chroot to it</p>
<p>mkdir /mount<br />
mount -t ext3 /dev/YourRootPartition /mount<br />
mount -o bind /dev /mount/dev<br />
chroot /mount /bin/bash<br />
cd</p>
<p>3) Edit the text file /etc/mkinitrd/modules and enter the names of the modules you had to probe to get the devices to show up.</p>
<p>4) Run &#8220;dpkg-reconfigure linux-image-`uname -r`</p>
<p>If you don&#8217;t have an OldWorld Mac, exit the chroot, exit busybox and reboot.</p>
<p>Good luck!</p>
<p>The rest is OldWorld Mac specific!</p>
<p>5) Mount the MacOS partition.<br />
modprobe hfs<br />
mkdir /mnt/hfs<br />
mount -t hfs /dev/MacOSPartition /mnt/hfs</p>
<p>6) Copy /boot/initrd.img-kernel-name to /mnt/hfs and put it in the Linux Kernels folder.</p>
<p>7) Unmount the hfs partition<br />
umount /mnt/hfs</p>
<p>8) Reboot into MacOS and try with the new initrd.</p>
]]></content:encoded>
			<wfw:commentRss>http://stuporglue.org/creating-a-custom-initrd-img/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

