well none of mine match. ll initrd*smp* -rw-r--r-- 1 root root 496401 Dec 1 16:22 initrd-2.6.9-1.667smp.img -rw-r--r-- 1 root root 494295 Dec 2 12:37 initrd-2.6.9-1.681_FC3smp.img
md5sum initrd*smp* 8423d673cc5cd6172bdc4ac793c2cf99 initrd-2.6.9-1.667smp.img a4fcf890e395fa4bf0d85c8c933dc7b2 initrd-2.6.9-1.681_FC3smp.img
Yours look to not be compressed based on the size.
-----Original Message----- From: fedora-list-bounces@redhat.com [mailto:fedora-list-bounces@redhat.com]On Behalf Of Terry Polzin Sent: Thursday, December 02, 2004 2:35 PM To: For users of Fedora Core releases Subject: Re: FC3 SMP builds do NOT contain ext3 drivers in the build!!!!
On Thursday 02 December 2004 14:22, William Hooper wrote:
Fred Skrotzki said:
I've even run up2date and using the latest 2.6.9-1.681_FC3 it still panics when booting. Thanks to the lack of ext3 drivers being built in.
Ext3 has never been built in. The module is loaded as part of the initrd.
You do have a point here that I also tried to make, if the initrd is bad the mods aren't going to load right. Here's the sizes and md5sums of my initrd files.
ll initrd*smp* -rw-r--r-- 1 root root 1065392 Nov 15 08:36 initrd-2.6.9-1.667smp.img -rw-r--r-- 1 root root 1065514 Nov 17 13:03 initrd-2.6.9-1.678_FC3smp.img -rw-r--r-- 1 root root 1064459 Nov 22 08:19 initrd-2.6.9-1.681_FC3smp.img
md5sum initrd*smp* 63e5a7024d015fe15ffefb9806102589 initrd-2.6.9-1.667smp.img fbcd978df7311bd866fb3ec27e22761f initrd-2.6.9-1.678_FC3smp.img ebe0beb1e8e48030db035f3f74d80aad initrd-2.6.9-1.681_FC3smp.img
Fred Skrotzki wrote:
well none of mine match. ll initrd*smp* -rw-r--r-- 1 root root 496401 Dec 1 16:22 initrd-2.6.9-1.667smp.img -rw-r--r-- 1 root root 494295 Dec 2 12:37 initrd-2.6.9-1.681_FC3smp.img
md5sum initrd*smp* 8423d673cc5cd6172bdc4ac793c2cf99 initrd-2.6.9-1.667smp.img a4fcf890e395fa4bf0d85c8c933dc7b2 initrd-2.6.9-1.681_FC3smp.img
Yours look to not be compressed based on the size.
Mine look like this:
[root@dude boot]# ls -l init*smp* -rw-r--r-- 1 root root 439802 Dec 1 14:49 initrd-2.6.9-1.667smp.img -rw-r--r-- 1 root root 439861 Dec 1 15:33 initrd-2.6.9-1.681_FC3smp.img
[root@dude boot]# md5sum init*smp* 86061cc6c2de5eb38f4ec9da0c01990b initrd-2.6.9-1.667smp.img 2e84fb3a5c0bc28983c2c27d10ca5817 initrd-2.6.9-1.681_FC3smp.img
Should these be the same or are they build dynamically at install time?
R.
On Thursday 02 December 2004 14:41, Fred Skrotzki wrote:
well none of mine match. ll initrd*smp* -rw-r--r-- 1 root root 496401 Dec 1 16:22 initrd-2.6.9-1.667smp.img -rw-r--r-- 1 root root 494295 Dec 2 12:37 initrd-2.6.9-1.681_FC3smp.img
md5sum initrd*smp* 8423d673cc5cd6172bdc4ac793c2cf99 initrd-2.6.9-1.667smp.img a4fcf890e395fa4bf0d85c8c933dc7b2 initrd-2.6.9-1.681_FC3smp.img
Yours look to not be compressed based on the size.
Whatever ot built by the install. I'd try in single user mode to rebuild the initrd if you haven't tried that allready. Of course, save the originals...
Fred Skrotzki said:
well none of mine match. ll initrd*smp* -rw-r--r-- 1 root root 496401 Dec 1 16:22 initrd-2.6.9-1.667smp.img -rw-r--r-- 1 root root 494295 Dec 2 12:37 initrd-2.6.9-1.681_FC3smp.img
Not surprising. The initrd is created as part of the post install RPM script so that it matches your hardware. A better thing to try would be to rebuild the initrd for the kernel version that isn't working and set grub to use it.