[NTLUG:Discuss] Messed modules_install

[Jack Snodgrass]

On Sat, 09 Aug 2003 12:48:16 -0500, Stephen Davidson wrote:
> That was that problem.
> 
> Now, the kernel is failing during boot.
> 
> As my / is ext3, I compiled EXT3 support into the kernel (rather than a module).  However, the kernel is loading / as ext2, not reading the partition table, and then segfaulting a few milliseconds later.
> 
> So, how do I tell it that / is EXT3?  Weirder, it has no problem with detecting this when booting the Stock Kernel????
> 
> Thanks,
> Steve

you 110% sure that your booting with your kernel that is set up for ext3?

FYI: you can change your /etc/fstab file and make / ext2 instead of ext3.
There isn't a lot of difference between ext2 and ext3. The main setup is 
ext2... ext3 adds some additional things that are separate. So.. you can 
go back to ext2 and then back to ext3 pretty easily. 

I don't know how the kernel decides / is ext2 or ext3 when it first 
loads. After it loads, it reads the /etc/fstab file and reads the 
partition types from that. It may load it up the first time as ext2
and do the ext3 stuff later... not 100% sure. 

this is from my startup messages:
TCP: Hash tables configured (established 262144 bind 65536)
Linux IP multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 148k freed
VFS: Mounted root (ext2 filesystem).
Journalled Block Device driver loaded
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Freeing unused kernel memory: 156k freed

it too mounts root at ext2 first... then it does the ext3 stuff....


So... make 110% sure that your kernel does ext3. 

If your kernel doesn't do ext3... and it's a module, then you 
can make an initrd image and load your modules that way. 

jack