Probelm in building kernel

uthra · 05-08-2007, 02:57 PM

Hello

I installed Fedora Core 1 yesterday and am trying to build Kernel 2.4.34.4. I downloaded it from http://www.kernel.org/
and executed

# tar xvfj linux-2.4.34.4.tar.bz2

This is what I get

bzip2: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzip2: Inappropriate ioctl for device
Input file = (stdin), output file = (stdout)

It is possible that the compressed file(s) have been corrupted.
You can use the -tvv option to test the integrity of such files.

You can use the 'bzip2recover' program to attemot to recover date from undamaged sections of corrupted files.

linux-2.4.34.4/driver/usb/emi26_fw.h
tar: unexpected EOF in archive
tar: unexpected EOF in archive
tar: Error is not recoverable: exiting now

What should I do ? Is the file really corrupted or is something wrong with my system and I need to change settings ???
Please help. Thank you !!!

Berto · 05-08-2007, 04:51 PM

I think the "f" part should only go at the end of the tar command (tar xvjf). That might cause some problems. Other than that, you could try re-downloading the kernel.

uthra · 05-08-2007, 05:05 PM

Berto,
Thanks. But it didnt work.
I tried "tar xvjf".. gives the same error.
I have tried downloading the kernel from 2 different locations. Will try other locations too. In the meantime if anyone knows how to trouble shoot this. Please let me know.

Thank you.

dxqcanada · 05-08-2007, 05:13 PM

Try bunzip first ...
then tar without the j.

uthra · 05-08-2007, 05:20 PM

dxqcanada ... I tried "bunzip file.tar.bz2"
Gives out bunzip: command not found.

Please advice .. thank you for your time

dxqcanada · 05-08-2007, 05:33 PM

Maybe you should install bunzip

samstar · 05-08-2007, 06:58 PM

Hi

Quote:

I tried "bunzip file.tar.bz2"

The command is "bunzip2"

Well I just downloaded it and extracted it fine with the command: "tar -jzvf linux-. . ."

It could be traffic on your internet connection that is corrupting it. Try again after stopping any other downloads/programs etc.

Sam

uthra · 05-09-2007, 10:52 AM

Thank you. I downloaded from another link and was able to extract it successfully.

Here are the steps that I followed. Am getting an error in "make xconfig". Can someone please explain ????

# tar xvfj linux-2.4.32.tar.bz2
# ln -s linux-2.4.32 linux
# cd /boot
# ls config*
config-2.4.22-1.2115.nptl
# cp config-2.4.22-1.2115.nptl /usr/src/linux/.config
# cd /usr/src/linux
# make xconfig
rm -f include/asm
(cd include ; ln -sf asm-i386 asm)
make -C scripts kconfig.tk
make[1]: Entering directory '/usr/src/linux-2.4.32/scripts'
scc -Wall -Wstrict-prototypes -02 -fomit-frame-pointer -c -o tkparse.o tkparse.c
make[1]: scc:Command not found
make[1]: *** [tkparse.o] Error 127
make[1]: Leaving directory 'usr/src/linux-2.4.32/scripts'
make: *** [xconfig] Error 2

uthra · 05-09-2007, 01:58 PM

Can someone please help me with this problem ???
Where am I going wrong ???

Emerson · 05-09-2007, 02:20 PM

Quote:

scc -Wall -Wstrict-prototypes -02 -fomit-frame-pointer -c -o tkparse.o tkparse.c
make[1]: scc:Command not found

What on the earth is scc? I assume it should be gcc, in that case you do not have a compiler installed. Use the package manager to install it. Can't tell you how to do it in RH, sorry.

uthra · 05-09-2007, 02:32 PM

Am sorry. Yes it is "gcc" and not scc.

I am using Fedora Core 1. Do you think it would help if I reinstall FC ??

samstar · 05-09-2007, 06:55 PM

Quote:

Am sorry. Yes it is "gcc" and not scc

Ahh, that's what got me confused. I thought I was out of my league for a moment

You just seem to be missing some development files. Just install gcc, and if you are using "make xconfig", make sure your qt-devel package is installed. If it gives you another error, asking for another program, it's very simple to google the program name and find out what you have to install. When in doubt, also install the "<program name>-devel" package.

Sam

uthra · 05-10-2007, 11:43 AM

Thank you Samstar.

I got it working. Had to install the packages and then it worked.