Age and the art of making a EXT3 File System Kernel
Gaddsss, I really must be aging. I have successfully built a working EXT3 kernel in the past and have forgotten the requirements. I have selected in the "file systems" Yes for the ext2 and Module for the ext3 journal file systems. There is something else in the back of my mind that saying that I am missing something. Currently the attempts that I have built do a kernel panic right at the point where it mounts the root partition. LABEL=/ "cant be found". I have tried both module and hard select for the ext3 file systems with the same results.
I am using RH8.0 with formatted scsi ext3 file system. The canned 2.4.18-14 loads just fine but it lacks the dmascc0 drivers that I need to ax25. I was attempting to build a 2.4.19 smp kernel.
Could some kind sole refresh my memory with the ext3 file system requirements.
Thank you in advance. John
Quoted 5 lines · John
Gaddsss, I really must be aging. I have successfully built a working EXT3 kernel in the past and have forgotten the requirements. I have selected in the "file systems" Yes for the ext2 and Module for the ext3 journal file systems. There is something else in the back of my mind that saying that I am missing something. Currently the attempts that I have built do a kernel panic right at the point where it mounts the root partition. LABEL=/ "cant be found". I have tried both module and hard select for the ext3 file systems with the same results.
I am using RH8.0 with formatted scsi ext3 file system. The canned 2.4.18-14 loads just fine but it lacks the dmascc0 drivers that I need to ax25. I was attempting to build a 2.4.19 smp kernel.
Could some kind sole refresh my memory with the ext3 file system requirements.
Just compiled the dmascc driver here for a RH8.0 machine, but I used the
default config file from the RH kernel rpm (in directory/usr/src/linux-2.4/configs) as my base config and just added the dmascc module to the build. Works fine.
I haven't tried it before, but you may be able to grab the appropriate config file from an official kernel rpm and just apply it to the build of a complete kernel source tree from kernel.org.
BTW, what kind of card are you using (using PI2's here)
... Niall (VE7HEX)
Quoted 17 lines · John
Gaddsss, I really must be aging. I have successfully built a working EXT3 kernel in the past and have forgotten the requirements. I have selected in the "file systems" Yes for the ext2 and Module for the ext3 journal file systems. There is something else in the back of my mind that saying that I am missing something. Currently the attempts that I have built do a kernel panic right at the point where it mounts the root partition. LABEL=/ "cant be found". I have tried both module and hard select for the ext3 file systems with the same results.
I am using RH8.0 with formatted scsi ext3 file system. The canned 2.4.18-14 loads just fine but it lacks the dmascc0 drivers that I need to ax25. I was attempting to build a 2.4.19 smp kernel.
Could some kind sole refresh my memory with the ext3 file system requirements.
Quoted 6 lines
Thank you in advance. John
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
John,
ext3 filesystem have to be buit in the kernel, not as module otherwise you will never be able to boot on your ext3 partition.
---
Regards and 73
Jean-Luc f5ibh
Quoted 17 lines · John
Gaddsss, I really must be aging. I have successfully built a working EXT3 kernel in the past and have forgotten the requirements. I have selected in the "file systems" Yes for the ext2 and Module for the ext3 journal file systems. There is something else in the back of my mind that saying that I am missing something. Currently the attempts that I have built do a kernel panic right at the point where it mounts the root partition. LABEL=/ "cant be found". I have tried both module and hard select for the ext3 file systems with the same results.
I am using RH8.0 with formatted scsi ext3 file system. The canned 2.4.18-14 loads just fine but it lacks the dmascc0 drivers that I need to ax25. I was attempting to build a 2.4.19 smp kernel.
Could some kind sole refresh my memory with the ext3 file system requirements.
Quoted 6 lines
Thank you in advance. John
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Don't forget to set the filesystem to ext3 in /etc/fstab
----
jean-Luc
Hi,
in general everything you need for booting must be comipiled into the kernel and NOT being modules. This includes scsi drivers, file-systems (ext3) etc in your case.
BR
/Thomas, SM0KBD
Citerar Jean-Luc <[email protected]>:
Quoted 26 lines
Quoted 17 lines · John
Gaddsss, I really must be aging. I have successfully built a working EXT3 kernel in the past and have forgotten the requirements. I have selected in the "file systems" Yes for the ext2 and Module for the ext3 journal file systems. There is something else in the back of my mind that saying that I am missing something. Currently the attempts that I have built do a kernel panic right at the point where it mounts the root partition. LABEL=/ "cant be found". I have tried both module and hard select for the ext3 file systems with the same results.
I am using RH8.0 with formatted scsi ext3 file system. The canned 2.4.18-14 loads just fine but it lacks the dmascc0 drivers that I need to ax25. I was attempting to build a 2.4.19 smp kernel.
Could some kind sole refresh my memory with the ext3 file system requirements.
Quoted 6 lines
Thank you in advance. John
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.htmlDon't forget to set the filesystem to ext3 in
/etc/fstab
Signature · 2 lines
Thomas "Thuben" Nilsson E-mail: Thomas<dot>Nilsson <at> bahnhof<dot>se
Quoted 3 lines · John
Gaddsss, I really must be aging. I have successfully built a working EXT3 kernel in the past and have forgotten the requirements. I have selected in the "file systems" Yes for the ext2 and Module for the ext3
Are you trying to boot off the ext3 partition?
if so, try building ext3 into the kernel, as opposed to having it as a module. This may avoid the chicken/egg problem....
<snip>
Quoted 3 lines
that saying that I am missing something. Currently the attempts that I have built do a kernel panic right at the point where it mounts the root partition. LABEL=/ "cant be found". I have tried both module and hard
Wilbert, ZL2BSJ
Quoted 1 line · John
partition. LABEL=/ "cant be found".
... have you included an 'hdx=scsi' statement in lilo/grub ...
Signature · 2 lines
73 , de WD0FPC Pacific Nowthwest 2M Repeaters
aka: terry http://www.aniota.com/~wd0fpc---
Quoted 10 lines · John
Gaddsss, I really must be aging. I have successfully built a working EXT3 kernel in the past and have forgotten the requirements. I have selected in the "file systems" Yes for the ext2 and Module for the ext3 journal file systems. There is something else in the back of my mind that saying that I am missing something. Currently the attempts that I have built do a kernel panic right at the point where it mounts the root partition. LABEL=/ "cant be found". I have tried both module and hard select for the ext3 file systems with the same results.
Quoted 6 lines
I am using RH8.0 with formatted scsi ext3 file system. The canned 2.4.18-14 loads just fine but it lacks the dmascc0 drivers that I need to ax25. I was attempting to build a 2.4.19 smp kernel.
Could some kind sole refresh my memory with the ext3 file system requirements.
You should have ext3 support built into the kernel, unless you use the initrd way, that lets you load it as a module. I think you should have ext2 too.
In order to mount the root filesystem as ext3, you have to set that in fstab. Remember you can still mount your ext3 as ext2. Also you can turn an ext2 into ext3, and vice-versa, using tune2fs.
Quoted 10 lines · John
Gaddsss, I really must be aging. I have successfully built a working EXT3 kernel in the past and have forgotten the requirements. I have selected in the "file systems" Yes for the ext2 and Module for the ext3 journal file systems. There is something else in the back of my mind that saying that I am missing something. Currently the attempts that I have built do a kernel panic right at the point where it mounts the root partition. LABEL=/ "cant be found". I have tried both module and hard select for the ext3 file systems with the same results.
Quoted 3 lines
I am using RH8.0 with formatted scsi ext3 file system. The canned 2.4.18-14 loads just fine but it lacks the dmascc0 drivers that I need to ax25. I was attempting to build a 2.4.19 smp kernel.
I had the same problem few months ago. I think the LABEL=/ stuff requires some kind of disk label support option (which may be RedHat's extension to the kernel). I didn't manage to find any elegant solution within almost a day of work so I decided to use brute force.
My method was editing /etc/fstab manually while running the old kernel. I just replaced "LABEL=/" with the /dev/hda# partition that contained the root fs. If there are any other LABEL= strings they need to be replaced in the same way. The easiest way to find out the right device names is the "df" command.
Also the original RH's kernel works after this modification. However you should be very very carefull because making a mistake here makes the system unbootable forever. Don't do this kind of changes unless you are familiar with the /etc/fstab format.
Best regards,
Hannu
-----
Hannu Savolainen ([email protected])
http://www.opensound.com (Open Sound System (OSS))
http://www.compusonic.fi (Finnish OSS pages) OH2GLH QTH: Karkkila, Finland LOC: KP20CM
Quoted 5 lines · On Wed, 7 May 2003, Hannu Savolainen, oh2glh wrote:
My method was editing
/etc/fstabmanually while running the old kernel. I just replaced "LABEL=/" with the /dev/hda# partition that contained the root fs. If there are any other LABEL= strings they need to be replaced in the same way. The easiest way to find out the right device names is the "df" command.
I did the same in /boot/grub/grub.conf after similar effort to try to make it work...
Doing it in grub/lilo has the advantage of not breaking anything for the stock distribution kernel.
Signature · 3 lines
Tomi Manninen Internet: [email protected] OH2BNS AX.25: [email protected] KP20ME04 Amprnet: [email protected]