I'm on dual boot with XP and FC1(default homeuser install plus all development packages).Switched to FC1 when I got it as a gift and just getting familier with the command line.My comp is:

Duron 750
Asus A7V
Radeon 32DDR(first generation)
Soundblaster live! value
256 megs of RAM
realtek 10Mbit LAN card
Sony 8X DVD drive

I tried to compile the 2.4 kernel(from /usr/src/liux2.4 on this computer) some time back but that didnt work and I couldnt find any answers on google so I gave up.Now though I got 2.2.6(from kernel.org)extarted to a directory on my home.

I did "make clean"(later on make mrproper with no difference) then configured it(first with menucofig then on later attempts with xconfig).First time I used no networking,no SCSI and no modules.On later attempts I used just the default and compiling as root but it made no diferent. I got the following for all of the times I did "make bzImage" or "make zdisk"(/home/anyone is my home directory I copied it to and working in):

/home/anyone/linux/include/asm/string.h: In function `memscan':
/home/anyone/linux/include/asm/string.h:477: error: syntax error before "repnz"
/home/anyone/linux/include/asm/string.h:478: error: `scasb' undeclared (first use in this function)
/home/anyone/linux/include/asm/string.h:478: error: (Each undeclared identifier is reported only once
/home/anyone/linux/include/asm/string.h:478: error: for each function it appears in.)
/home/anyone/linux/include/asm/string.h:478:21: invalid suffix "f" on integer constant
/home/anyone/linux/include/asm/string.h:480:17: missing terminating " character
In file included from /home/anyone/linux/include/linux/sched.h:23,
from /home/anyone/linux/include/linux/mm.h:4,
from /home/anyone/linux/include/linux/slab.h:14,
from /home/anyone/linux/include/linux/malloc.h:4,
from /home/anyone/linux/include/linux/proc_fs.h:5,
from init/main.c:15:
/home/anyone/linux/include/linux/signal.h: In function `siginitset':
/home/anyone/linux/include/linux/signal.h:193: warning: deprecated use of label at end of compound statement
/home/anyone/linux/include/linux/signal.h: In function `siginitsetinv':
/home/anyone/linux/include/linux/signal.h:205: warning: deprecated use of label at end of compound statement
In file included from /home/anyone/linux/include/linux/mm.h:4,
from /home/anyone/linux/include/linux/slab.h:14,
from /home/anyone/linux/include/linux/malloc.h:4,
from /home/anyone/linux/include/linux/proc_fs.h:5,
from init/main.c:15:
/home/anyone/linux/include/linux/sched.h: In function `add_free_taskslot':
/home/anyone/linux/include/linux/sched.h:398: warning: dereferencing type-punned pointer will break strict-aliasing rules
/home/anyone/linux/include/linux/sched.h:401: warning: dereferencing type-punned pointer will break strict-aliasing rules
/home/anyone/linux/include/linux/sched.h: In function `get_free_taskslot':
/home/anyone/linux/include/linux/sched.h:408: warning: dereferencing type-punned pointer will break strict-aliasing rules
/home/anyone/linux/include/linux/sched.h:411: warning: dereferencing type-punned pointer will break strict-aliasing rules
In file included from /home/anyone/linux/include/linux/smp_lock.h:13,
from init/main.c:22:
/home/anyone/linux/include/asm/smplock.h: In function `lock_kernel':
/home/anyone/linux/include/asm/smplock.h:46: warning: dereferencing type-punned pointer will break strict-aliasing rules
/home/anyone/linux/include/asm/smplock.h: In function `unlock_kernel':
/home/anyone/linux/include/asm/smplock.h:57: warning: dereferencing type-punned pointer will break strict-aliasing rules
init/main.c:199:8: warning: extra tokens at end of #endif directive
init/main.c:203:8: warning: extra tokens at end of #endif directive
init/main.c:206:8: warning: extra tokens at end of #endif directive
init/main.c:209:8: warning: extra tokens at end of #endif directive
init/main.c:212:8: warning: extra tokens at end of #endif directive
init/main.c:215:8: warning: extra tokens at end of #endif directive
init/main.c:218:8: warning: extra tokens at end of #endif directive
init/main.c:221:8: warning: extra tokens at end of #endif directive
init/main.c:224:8: warning: extra tokens at end of #endif directive
init/main.c:227:8: warning: extra tokens at end of #endif directive
init/main.c:230:8: warning: extra tokens at end of #endif directive
init/main.c:233:8: warning: extra tokens at end of #endif directive
init/main.c:242:8: warning: extra tokens at end of #endif directive
init/main.c:729:8: warning: extra tokens at end of #endif directive
init/main.c:732:8: warning: extra tokens at end of #endif directive
init/main.c:735:8: warning: extra tokens at end of #endif directive
init/main.c:738:8: warning: extra tokens at end of #endif directive
init/main.c:741:8: warning: extra tokens at end of #endif directive
init/main.c:744:8: warning: extra tokens at end of #endif directive
init/main.c:747:8: warning: extra tokens at end of #endif directive
init/main.c:750:8: warning: extra tokens at end of #endif directive
init/main.c:753:8: warning: extra tokens at end of #endif directive
init/main.c:756:8: warning: extra tokens at end of #endif directive
init/main.c:759:8: warning: extra tokens at end of #endif directive
make: *** [init/main.o] Error 1

I googled for about a day but to no avail.I'm very new to this and have never made anything on linux more than a hello world program in C.Greatly apreciated any help.

Welcome to LQ!

You shouldn't compile a kernel in your home directory.
Use one of these two guides for compiling your kernel
http://www.digitalhermit.com/linux/K...ild-HOWTO.html
http://www.linuxquestions.org/questi...threadid=73436

You noticed that too huh?

Chinaman is right. Put the sources in /usr/src/ and make the /usr/src/linux link to them, then compile away.

Hey, I been there. It took me a while to get my first one to do right to.

If you are using grub as your boot loader, save the old kernel as a fall back. Just name the new one somthing different then point grub to as a extra line in grub.conf. Call it Linux-test or something. If the one you make doesn't work, you can fall back to the old one to make a new one. Nothing worse than having a install with no good kernel. Been there, done that too. Don't be suprised if the first one stinks. Mine did. Wouldn't boot at all.

Later

Now this is a very outdated ancient kernel version. It probably won't even compile with a recent version of gcc (compiler). If you really need this old kernel version, get some older gcc, e.g. 2.95 or even 2.77.

But I suggest that you get a new kernel version - 2.6.8.1 or some 2.6.9rc and it will compile with any reasonable gcc version.

And it is possible to compile kernel anywhere, even in your home directory, contary to what our friends said before.

Never said it's not possible, just you shouldn't which is an opinion.

I tried to to compile the kernel with fedora already in the /usr/src directory(2.4.22).Used Xconfig and saved without changing anything and then made BzImage but I get this error:

arch/i386/kernel/kernel.o(.text.init+0x5328): In function `acpi_parse_lapic':
: undefined reference to `acpi_table_print_madt_entry'
arch/i386/kernel/kernel.o(.text.init+0x5398): In function `acpi_parse_lapic_nmi':
: undefined reference to `acpi_table_print_madt_entry'
arch/i386/kernel/kernel.o(.text.init+0x548f): In function `acpi_boot_init':
: undefined reference to `acpi_table_init'
arch/i386/kernel/kernel.o(.text.init+0x54a7): In function `acpi_boot_init':
: undefined reference to `acpi_table_parse'
arch/i386/kernel/kernel.o(.text.init+0x54d2): In function `acpi_boot_init':
: undefined reference to `acpi_table_parse_madt'
arch/i386/kernel/kernel.o(.text.init+0x5507): In function `acpi_boot_init':
: undefined reference to `acpi_table_parse_madt'
arch/i386/kernel/kernel.o(.text.init+0x5525): In function `acpi_boot_init':
: undefined reference to `acpi_table_parse_madt'
make[1]: *** [kallsyms] Error 1
make[1]: Leaving directory `/usr/src/linux-2.4.22-1.2115.nptl'
make: *** [vmlinux] Error 2

Thank you all very much!

Well not much idea about Fedora but i can tell somethings about kernel compiling

When u re making a new config file using make config there are some things in the menu that need to be checked and some that need to be unchecked.........

pls look into the redhat kernel compilation in this site for more details..... in the redhat forums or search the forum, the steps given here for kernel compilation are very good they should fetch u some answers........

I got the bundled kernel to work from copying the config file form /boot I'mg oing to make the 2.6 kernel next but is there any way the 2.2.26 can be compiled?(I'm hoping to make a small linux distro for an old pentium 1 computer)

Hi there,

I also wanted to add something to this post. I have FC1 2.4.22 kernel. But I have a pctel modem. The author of the driver says that he has a working driver for 2.2 kernels. He told me to install the 2.2.26 kernel and install his driver and let him know some modem chip details that would assist him in developing driver for 2.4 and 2.6 kernels. I got the 2.2.26 kernel from kernel.org.

I went through the kernel compiling steps with the help of some kernel HOWTO docs. I received the same error message as given by begining....when I tried to make bzImage or any other image..

I tried as stated copied the whole src file in /usr/src/linux-2.2.26 and made a symbolic link linux-2.2. Still it gave me errors...

Can anybody please help me on how about setting up this 2.2.26 kernel successfully on FC1....

Since I am farely new to Kernel compiling, step by step explaination would be of great help.

thank you
aruran

Interesting... you're doing this to get support for your pctel modem? The main driver has been working under 2.4 for some time, and 2.6 starting about two weeks ago - unless this is a special type of PCTel modem?

Can you post the output of this:

/sbin/lspci -vv -n -d 134d:

I should be able to tell from that whether the driver I know of is compatible with your modem.

Cheers,
Jeff
PS: Refer to http://linmodems.technion.ac.il/pcte...x/welcome.html for more info.

Yes, this is a special type of modem I think.... The author said it is a 688T type. Anyway I have copied the command output you asked...

[root@localhost root]# /sbin/lspci -vv -n -d 134d:
03:06.0 Class 0703: 134d:2189 (rev 04)
Subsystem: 134d:1002
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping+ SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (250ns min, 15500ns max), cache line size 08
Interrupt: pin A routed to IRQ 5
Region 0: Memory at dfdfe000 (32-bit, non-prefetchable) [size=4K]
Region 1: I/O ports at c400 [size=256]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-



regards
aruran

Ah, you are totally right, you need a different driver. I'm glad one exists. Is it publicly available anywhere? I'm curious to see how different it is... Sorry I couldn't be more help.

Regards,
Jeff