New 2.4.3 kernel and various problems...

[[Mystik_Cool]]

Hi,

I just downloaded the new kernel 2.4.3 (available on www.kernel.org). (http://www.kernel.org).) When I unzip it, it works but after some time it stops and print :
tar: shipping to next header
gzip: stdin: invalid compressed data --crc error
tar: child returned status 1
tar : Error exit delayed from previous errors.

I don't understand anything about that :-) What does it mean ? Could someone help me ?

And afterwoods, when I want to configure this new kernel, I type : make menuconfig (in the kernel directory) and it doesn't work. The message is :
Makefile 229 : arch/i386/Makefile : No suck file or directory
make : *** No rule to make target 'arch/i396/makefile'. Stop.
What's wrong there ? Is it due to the precedent problem ?

Thanx if u could help me...

PS : another small problem (arf, it's not problems which are missing :-)) : when I want to patch smthg to this kernel (for example a PPPoA patch), I have to type : "patch -p1 -s -E < /path/to/pppoatm-1"
Is the "<" necessary ? Could someone give me an example of using this command with real names of directories ?
The problem is that my keyboard is not properly configurable (anyway I didn't succeed, I tried a lot of different configuration but it never worked correctly) and I can't type the caracter "<" (or ">").
Is there any solution ?

Many thanx, I begin in the linux world so... I have many many questions and problems :rolleyes:

[Bradmont]

Hmmm... your download may have been corrupted, so you might want to try re-downloading it. Also, that crc error is kinda suspicious... I did a bit of research on those when I at one point was getting them during boot... it meant that there was interferance in the IDE cables that was corrupting data flow. It's often caused by having the cables jammed all together too tightly. You may wanna try opening up your case, spreading out your IDE cables, and trying again. (tho I don't know if a crc error would be the same thing in this context)

[[Mystik_Cool]]

I'll try to load it again... My computer is very clean, normally the problem is not in the cables... I hope !
I'm going to try another version (2.4.2 should be enough to install my modem), and I'll see what happen...

Thanx for your help !
How about adding a patch and the keyboard's problem ? (with the "<"). :confused:

[Unruly]

CRC errors are checksum errors that occur when a couple of bytes are missing from a file, and when the decompression program compares the checksum values of the newly extracted file, and the table that the compressed file comes with, and finds a problem, then it *****es about a CRC error.

The most common occurance is when you download a file (larger it is, the better the chance of CRC errors) or when you move them across networks or drives...

[Tyr-7BE]

Originally posted by [Mystik_Cool]:

Thanx for your help !
How about adding a patch and the keyboard's problem ? (with the "<"). :confused:

Well you're typing it here, so you obviously know where it is on the kb :p. Ummm...what sort of terminal are you using to compile the kernel? Standard Console? Xterm within XFree86? ETerm? Is this keyboard problem system-wide, or just in the terminal window? If it's system wide then maybe you specified the wrong character set when you installed the keyboard. Try this: back up your existing /etc/X11/XF86Config file (XF86Config-4 if it's X 4.0.x), and run xf86config (CAPS count!!). See if that helps any. If X won't work after that, just replace the XF86Config file with the old one.

[[Mystik_Cool]]

Ok, so, firt, it's a problem everywhere in Linux. IMPOSSIBLE to type "<" !!!!!!
I tried to edit XF86 but, this "<" caracter doesn't work on any keyboard description !
I think I have a special keyboard, only know by me ! lolll
I'm happy : it's my last problem (for the moment)! Version 2.4.2 of the kernel works perfectly !!! Now I have to add some patches for USB DSL modem, but to add them I NEED this @#!*^ù£ "<" caracter ! lol :mad:
Isn't it possible to make a "copy" from a document and "paste" in a console ?
Else, I'll have to buy another keayboard ! lol

[PLBlaze]

You could patch another way :)
gzip or bzip the patch file and then do gzip or bzip2 -dc filename.bz2 or filename.gz | patch -p1

Now don't tell me your keyboard don't have pipe (shift+back slash) key.Hope this helps.

[[Mystik_Cool]]

Yeah, when I was going to bed yestersday, I though they were certainly another way to patch... I didn't knew how, but now I know ! :)
Thank you, I'm going to try this ! (I hope I have this "|" key under linux... lol)

[[Mystik_Cool]]

Thanx very much, it works !!!

I have a last question (erm, I hope it's the last ! lol) : to reboot with my new kernel, have I to rename the precedent kernel ? (for example, I was using a 2.2.14, have I to rename this directory to "linux.old" for example ?)
Or, maybe the instructions that I type to build the new one are enough ? The instructions I type are :
make dep
make bzImage
make modules
make install
make install_modules

But when I reboot after that linux uses still my old kernel (I'm not sure, but it seems to be like that ! lol)

[[Mystik_Cool]]

So erm, my question is, when I configured my new kernel, how to install it in place of the old one and how to make linux run on this one ?...

[PLBlaze]

Well it's always good to keep the older kernel tree under /usr/src.I keep this naming scheme linux-2.4.0,linux-2.4.1,2.4.2 for the kernels i've used and the new kernel just points to linux.

At this ponit you read the kernel compling NHF or do a search no the forums this question been asked many,many times (how many to come?) but basically you need to copy the bzImage to /boot/vmlinuz-2.4.3 or whatever is your kernel version and keep the previous around just in case.I don't know what bootloader you use but if LILO then edit /etc/lilo.conf and append the new kernel image then rerun /sbin/lilo to update the bootloader reboot and you're ready to use newly build kernel (if all went well).Hope this helps again.

[[Mystik_Cool]]

Thanx again, and sorry, I didn't take the time to read other messages... I'll do it next time, I promise :)