I guess recompiling te kernel could be looked at as installing, so I'd give it a try here.

I installed slack from the 4 cd set I ordered. I comes with the 2.4.22 kernel and a xfs patch set. I installed the patch against the kernel tree and made a 'make xconfig', after selecting te xfs filesystem (set to y like ntfs and ext3, not module) I made a 'make dep' followed by 'make modules' and make bzImage. Installation went smooth with 'make modules_install' and 'make install'. I finished with 'make clean' and 'lilo -v' to get all working.

Strangly enough when I boot it still doesn't work. A 'mount -t xfs dev/hdb8 linux/r' gives an out put of: 'xfs not supported by kernel'. If I go to usr/src and do a make xconfig again the XFS filesystem is allready selected. Even in KDE configcenter under kernel the XFS filesystem is listed the same way as ntfs (which does work). So I'm kinda clueless of what is wrong. Compiling went fine, the kernel list XFS as being selected but mounting doesn't work. What went wrong and how to fix this?

Regards

did you make it a module? if so do a modprobe xfs.

you may have kernel dependency problems and the xfs isnt working. umm kinda like trying to play a record and forgetting to put the needle in the arm. records there it goes around and the arm is there but no music.

try lsmod and see if xfs is loaded as a module.
if its not try modprobe xfs to see if you can load it.
try depmod and see if you get messages about dependencies.

if you built the xfs into the kernel make sure you are loading the correct kernel.

I build it into the kernel. Since it's a recompile I guess I don't have to select another kernel to load (only kernel on the system is the original 2.4.22 with the patch, that I recompiled)? I could do another recompile and build it as a module and see if that works. Bit pointless it seems, it should work this way I guess. Are there any commands I can try to see what's wrong since I build it into the kernel?

Regards

not really. but if its built into the kernel you shouldnt have to specify the file system when you are mounting the partition.

mount -t xfs dev/hdb8 linux/r
you sure you meant to leave out the leading / seems odd

but just try

mount /dev/hdb8 /linux/r
i put the / in ... well anyways check without specifying the filesystem the "-t xfs" part ... if xfs is built in and its working you wont need to specify the fs because it is loaded and linux will be able to tell what it is when you try to mount it.

I give it a go when I get home. If nothing works I could always recompile it to a module and see if I get more results.

Thanx so far!

I really don't get it. All is looking like working but I can't mount it so there should be something wrong somewhere. I know you guys won't be able to help with this kind of info but I have no clue left what to look for. I recompiled again with no errors but xfs is just not loading.

I'm going for a module version that should do it. After compile, how should I enable the module? Where can I find it (if it is actualy made)?

Regards

it will be under /lib/2.4.22/kernel

you can find it with "find /lib/2.4.22 -name xfs*"

but just try "modprobe xfs"

"Strangly enough when I boot it still doesn't work."

You may still be booting the old kernel. You can find out what kernel you are running on with:
uname -r

___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html

Steve Stites

4.2.22 but it was a recompile so that shouldn't make a difference? make install does install the image doesn't it?

make install install the kernel?

i believe so ... i dont install my kernel that way ... i have read the 1st post in the slack forum and it does explain how that can work if you edit a file i dont remember which though.



what happened when you tried xfs as a module?

"make install does install the image doesn't it?"

No. You are still running on your old kernel. I just checked the kernel HOWTO link that I normally post and it is down for revision. You have to copy the new kernel to /boot and you have to create the kernel modules in /lib/modules.

You also have to allow for the new kernel not working. Either set the two kernels up as dual boot or save the old kernel somewhere where you can restore it using a rescue CD (which is what I do, but I always recommend dual booting).

Since I cannot quickly find a kernel HOWTO here is my install plan for kernel 2.4.22-ac4. Keep in mind that when I wrote this out it was notes to myself, not a generalized HOWTO.

--------------------------------------------------------------------------------------------------------------------------
How to compile and install a new kernel

Save the entire old boot directory to /boot.old.

The old kernel configuration is kept at /boot/vmlinuz.config
The new kernel source is at /usr/src/linux -> linux-2.4.22-ac4.
The new kernel configuration is kept at
/usr/src/linux-2.4.22-ac4/.config

Change to the Linux source directory:
cd /usr/src/linux

Configure Linux with the command:
make xconfig

Compile bzImage with these commands:
make dep
make clean
make bzImage

Compile modules with this command:
make modules

Install the modules with this command:
make modules_install

Save the entire old boot directory.

Copy the new kernel to /boot with these commands:
cp arch/i386/boot/bzImage /boot/vmlinuz-2.4.22
cp System.map /boot/System.map-2.4.22

Change to root directory:
cd

If using initrd then create the new initrd with these commands:
depmod -a 2.4.22 -F /boot/System.map
mkinitrd -k "vmlinuz-2.4.22" -i "initrd-2.4.22" -d "/dev/hdc3"

Make any necessary changes to /etc/lilo.config.
Run lilo:
lilo

Shutdown the system.
Boot the new system.

Create boot floppys:
Create a zero delay boot floppy.
Create a ten second multiple choice boot floppy.

Create rescue CD

remove /boot.old, kernel, /lib/modules/2.4.20, /etc/lilo.conf.old,
/etc/lilo.conf.new
--------------------------------------------------------------------------------------------------------------------------

I can rely on the rescue CD to pull me out of trouble because I have used LifeBoat to create a highly customized rescue CD. Once I get a new kernel working I then create another rescue CD for that particular kernel. You can find LifeBoat here.

http://users.rcn.com/srstites/LifeBo...home.page.html

----------------------
Steve Stites

make install can install the kernel for you read the 1st post in the slack forum author is daone.

that sounds like redhat stuff jailbait.

Well it's done. Stupid me! I didn't edit the make file so the new kernel wasn't located in /boot. Now it is and it work brilliant (after re-using the nvidia driver install). I gues the size of the thing 1,4 mb is way to big so next step is to cut it done to just what I need!
Thanx for the help!

woohoo good job ... and good luck.