Another kernel 2.6.3 issue

[LiNuts]

I am using Mandrake 9.1 >kernel 2.4.21-0.13mdk, but could not get my cd-burner to work ( scsi emulation) So i got hold of kernel 2.6.3 ( from a pc mag ) because of its ATAPI-IDE support.

Read the req infos about the kernel, compiled it, and re-booted. boots o.k. but with a heap of issues.

1) when booting says fs vfat not supported by kernel ( compiled as a module ) ( re-compiled built into kernel - same result ).

2} will not recognise my pci ens1370 sound card ( compiled as a module ) re-compiled built into kernel - same result )

3) complains about "QM_MODULES" (?) modprobe QM_MODULES not found.

4) installed kernel in my /home/newkernel dir ( for permissions ) only used sudo to do "make modules_install" and to copy /arch/i386/boot/bzImage to the /boot/2.6.3 dir. but when i want to run Mandrakes Control center - and put my root psswd in it says " su not found" make sure its in your PATH.

checked my ./bash/profile and $HOME/bin is there. (thats where su resides).

my lilo.conf entry for 2.6.3 is as follows:

image=/boot/2.6.3/bzImage
root=/dev/hdc1
label=new-2.6.3
read-only

I have never had trouble compiling a new kernel before, but as i have been away from linux for a while, i guess things change:rolleyes:

any help appreciated

cheers
LiNuts

edit: This new kernel compiles a lot easier than the old kernels, if only i can get the bugger up and running right.:D

[mdwatts]

Did you read the 2.6 kernel changelog to find out what other packages are required such as module-init-tools?

Are any modules loaded (lsmod)?

Did you enable FAT_FS and MSDOS_FS besides VFAT support?

Have you copied System.map to the kernel directory?

There are a few 2.6 kernel guides posted in the 'How I did it' forum that may help you to troubleshoot.

[hard candy]

And it may help after you have everything installed and set, run "/sbin/ldconfig" to update any paths.

[LiNuts]

mdwatts No i didn't read the changelog (/me kicks myself) Got hold of module-init-tools-3.0, but now have conflict probs with my modutils. says that modutils <2.4.22-10mdk conflicts with moules-init-tools-3.0. also says devfsd <1.3.25-31mdk conflicts with modules-init-tools-3.0.

I enabled FAT_FS and MS_DOS FS as well as VFAT (tried as both module and built into the kernel).

copied the System.map into /boot/2.6.3.


hard candy Thats one thing i forgot to do :eek:

cheers
LiNuts

edit: spelling

[Dark Ninja]

I use the same sound card/module that you have and I was able to set it up after following the guide over at Gentoo. (Check out documentation>ALSA sound setup.)

Maybe that's too simplistic of a solution, but, the most difficult problems usually have simple solutions.

[LiNuts]

Thanks fellas, after doing a google, i gather that my problem is the module-init-tools-3.0 . unless i can get that installed i cannot do a kernel-2.6.3 compile. (well i can, but no modules will be loaded).

I tried urpmi to get it to install, but it wanted to un-install most of my O.S.

I shall keep on perseveering with it. If any one knows how i can install the module-init-tools-3.0 without having to decimate my system, i will be grateful for the knowledge.

Cheers
LiNuts

[Stween]

As far as I know, when you're installing module-init-tools, there's a make command that keeps the old versions of the tools, which are called by the newer versions when required.

I recall being caught out by that initially because, quite frankly, the readme's at the time were crap. There's a little more information about it in this document (http://www.linux.org.uk/~davej/docs/post-halloween-2.6.txt), and within the README of the module-init-tools source tar.gz if you're compiling afresh.

[LiNuts]

Stween: thanks for the link to the doc, read it, very informative, there was a link to kernel.org for a backward compatible modutils 4.23-20 binary. so i dloaded it and installed it, after reading ALL the info in the README and INSTALL.

Went to reboot and everything was messed up per modules. couldn.t get anything working.

Just got my system back to normal now. i will keep on perseveering with this linux-2.6.3 kernel.

One thing i did note: it recommends to just do "make" instead of "make bzImage" So i tried that, but it (2.6.3) wouldn.t boot. So i ran "make bzImage" and at least i could boot it ( sort off ). i still thinf that module-init-tools-3.0 is the answer to my problems.

Cheers
LiNuts

[kevinalm]

I would suggest downloading module-init-tools as source and compiling it yourself. (But then I have come to detest rpm systems ;)) _Very_ important: Read and understand the instructions (README, INSTALL, etc.) very carefully. There is an important step necessary in order to preserve 2.4.x compatability. Backward compatability is maintained by saving and renaming your current mod tools, the new tools call the old ones as needed.

[LiNuts]

kevinalm I did use the source in the 1st dload, and read the README and INSTALL re either to link or copy the old mod tools. but got an error when i chose the copy method. So i checked the dir, and my mod tools had "insmod.old modprobe.old" etc etc.

Thats when i dloaded the binary and installed with the result of a comletely fsckd modutils.

Cheers
LiNuts

[kevinalm]

Originally posted by LiNuts
kevinalm
Thats when i dloaded the binary and installed with the result of a comletely fsckd modutils.



That makes sense. The first attempt at module-init-tools renamed your old mod tools and installed new ones. Then you tried again with the binary and it overwrote the .old with the new (compiled from source) versions. Sound of system crashing. Ouch! ;) It's very important to only convert once.