Hey Thetargos, just a follow up...
I got ALSA to work for the new kernel by just compiling and installing the alsa-driver tarball. I just compiled it with support for my soundcard and the new drivers worked fine with the already installed libs, utilities, etc. Thanks again, meeshka |
Good to hear you got it right :)
|
First of all, Thetargos, thanks for the (amazingly clear) instructions on how to compile the kernel. Apparently I am the only one who has had problems with this, and I hope you can help me with this:
After following your instructions and running the 'make install' command, I got this error: md5sum: WARNING: 1 of 13 computed checksums did NOT match md5sum: WARNING: 1 of 13 computed checksums did NOT match setup.S: Assembler messages: setup.S:230: Warning: indirect lcall without `*' Root device is (3, 2) Boot sector 512 bytes. Setup is 4767 bytes. System is 890 kB + '[' -x /root/bin/installkernel ']' + '[' -x /sbin/installkernel ']' + exec /sbin/installkernel 2.4.22 bzImage /root/kernel/linux-2.4.22/System.map '' /lib/modules/2.4.22 is not a directory. mkinitrd failed make[1]: *** [install] Error 1 make: *** [install] Error 2 What does this all mean? Thanks in advance for taking your time to answer a newbie's questions. |
Hey Thetargos,
Just a question, in your original instructions you had: $ su password: # make install # make modules_install should make modules_install come before make install? |
I figured make modules_install had to come first too, and I ran that command then, and I got this nifty error (this is the redirected makemodules_install.err file):
md5sum: WARNING: 1 of 13 computed checksums did NOT match md5sum: WARNING: 1 of 13 computed checksums did NOT match setup.S: Assembler messages: setup.S:230: Warning: indirect lcall without `*' Root device is (3, 2) Boot sector 512 bytes. Setup is 4767 bytes. System is 890 kB + '[' -x /root/bin/installkernel ']' + '[' -x /sbin/installkernel ']' + exec /sbin/installkernel 2.4.22 bzImage /root/kernel/linux-2.4.22/System.map '' depmod: *** Unresolved symbols in /lib/modules/2.4.22/kernel/crypto/autoload.o depmod: crypto_alg_lookup depmod: *** Unresolved symbols in /lib/modules/2.4.22/kernel/crypto/proc.o depmod: crypto_alg_sem depmod: crypto_alg_list I got the same errors with make install afterwards... So I go back to see if the problem lies within the earlier steps, I ran make bzImage 2> bzImage.err, whose output was: md5sum: WARNING: 1 of 13 computed checksums did NOT match md5sum: WARNING: 1 of 13 computed checksums did NOT match setup.S: Assembler messages: setup.S:230: Warning: indirect lcall without `*' Root device is (3, 2) Boot sector 512 bytes. Setup is 4767 bytes. System is 890 kB I also ran make modules 2> modules.err, and its output was this: md5sum: WARNING: 1 of 13 computed checksums did NOT match make[2]: Circular /root/kernel/linux-2.4.22/include/linux/netfilter_ipv4/ip_conntrack_helper.h <- /root/kernel/linux-2.4.22/include/linux/netfilter_ipv4/ip_conntrack.h dependency dropped. So far I can see that this 1 of 13 computed checksums error is consistent within all the error log files I've made... coincidence? I sure wish I wasn't a newbie. |
Yes, indeed, you are both right. I assumed make install would only make the base bzImage and then install it (but learned latter that it needs /lib/modules/<kernver> to do its job). As I said at the end of the guide, I noramally use the compressed method:
Code:
# make clean dep modules modules_install install |
About what I posted previously, the kernel did compile, in spite of the errors. After running it on my laptop thru grub (I compiled the kernel in my laptop and in my desktop, both got the exact same errors), I was distraught to see that my ethernet card didn't work (but fear not I just made it work... it seemed that since I had compiled the drivers for my previous kernel, it wouldn't work on this one.
The real problem is that it doesn't recognize my mouse. It's a kensington usb pocketmouse, which it recognizes perfectly in my previous kernel installation. The touchpad works fine though. I had both working fine on my 2.4.20-8 kernel. Also, I have a few games installed, and they run terribly slow now... I checked my video card config and it's just fine (the enable 3d hardware acceleration checkbox is checked). In the kernel configuration (i ran menuconfig), i enabled all the usb devices, as well as mouse and keyboard usb support... I don't know what could be the problem... And if that wasn't enough, at bootup, it still gives me that error that says *** Unresolved symbols in lib/modules/2.4.22/kernel/crypto/autoload.o *** Unresolved symbols in /lib/modules/2.4.22/kernel/crypto/proc.o I truly have no idea what any of it means. |
ok, I tried running insmod manually to install the autoload.o file, and this is the error that I got:
root]# insmod /lib/modules/2.4.22/kernel/crypto/autoload.o /lib/modules/2.4.22/kernel/crypto/autoload.o: unresolved symbol crypto_alg_lookup /lib/modules/2.4.22/kernel/crypto/autoload.o: Hint: You are trying to load a module without a GPL compatible license and it has unresolved symbols. The module may be trying to access GPLONLY symbols but the problem is more likely to be a coding or user error. Contact the module supplier for assistance, only they can help you. I assume I am getting closer to the answer, though I dunno who the module supplier is, or what in the world GPL is. |
Hello,
firstly THANK YOU sooo much for writing this guide. I had no installtion problem. But after I rebootet GRUB showed me 3 Kernels 1.---2-4.20-8smp 2.---2-4.20-8 3.---2-4.22 Which is ok, #1 #2 work fine. But #3 says after a while, Kernel Panic unable to mount "vfs" It cant find the root file system. Do you have any tips for me :D Thanks -Florian |
Quote:
Regarding the problem you [b]did[b] compile with cryptographic support into the kernel. This was one of the reasons I never could re-compile an official Red Hat kernel (and hence decided to go on my own with a plain vanilla kenrel) try to compile [b]without[b] cryptographic support. |
Quote:
Tip: I usually compile with ext3 support and ext2 (second extended) directly into the kernel. To me it sounds like a network file system problem verify that too.. |
Hello after running in one problem I am now facing the second :p
I finally got it to read the .config file from the original 9.0 kernel. Upon editing some stuff, I get the following error in booting mount: error 19 mounting ext3 (maybe not a file sys suppport) umount /initrd/proc failed:2 Kernel Panic= no init found Thanks Florian PS: Altough I am a :newbie: I will not give up :-) :Pengy: FOREVER |
ok I see what you're telling me... since recompiling a redhat kernel is such a hassle, is there a way i can remove the kernel i just installed?
btw, thanks for your answer. |
Quote:
|
Quote:
Code:
$ su |
All times are GMT -5. The time now is 09:13 PM. |