Issue during compiling a kernel

ilkyest · 2010-02-13 03:33:23

Hello pals. I'm new on arch. I'm user of debian based distros, an I am trying compile a kernel. Well. Here in Brazil, one pal made a very fast, lite, and goor kernel. the name is 2.6.30-omnislash1. It combines the patches from ck and good ideas to make the kernel faster.

But, during the make, after 3 minutes, I receive this message

arch/x86/kernel/ioport.c: In function 'sys_ioperm':
arch/x86/kernel/ioport.c:52: error: implicit declaration of function 'sched_privileged_task'
make[1]: ** [arch/x86/kernel/ioport.o] Error 1
make: ** [arch/x86/kernel] Error 2

The way I'm folowing is this
http://wiki.archlinux.org/index.php/Ker … sers_Guide

I say you that, by, exactly, this way, I could compile the 2.6.32.8 kernel, but, what I'm trying ( solve the pci colision resources) with a regression patch, I couldn't. The issue continue, and, I forgot put the soundcard module active. What means a good kernel, with resource colision issue, and without sound.

What of mistake may I'm doing.

And excuse my english, its a little poor.

I'm using the 2.6.30-ARCH kernel. And about the "regression issue" that I'm trying have good news is this. look my dmesg

pci 0000:01:07.0: BAR 6: address space collision on of device [0x
dbfc0000-0xdbfdffff]

Peasantoid · 2010-02-13 04:21:28

As for the first issue, normally implicit declarations aren't errors. I expect the compilation is passing the -Werror option to gcc. Perhaps you can work around this.

ilkyest · 2010-02-15 22:32:07

No it stops. When I receive the second error, it stops. How can I arround this?

pyther · 2010-02-15 22:51:05

Sounds like some faulty code.

Why aren't you using 2.6.32?

ilkyest · 2010-02-15 23:03:01

'cause the error I noticed in up

pci 0000:01:07.0: BAR 6: address space collision on of device [0x
dbfc0000-0xdbfdffff]

'cause it, my temperature readings aren't good. On debian lenny I read 40ºC and in arch 55º And I've tried compile the last one 2.6.32.8 with pci regression patch, but not succesfull. The kernel i've put to you (the omnislash one) combines the con kolivas solution with a speed more better, and without "recourses colision"

What surprised to me is that kernel newer than mine, good. compiles at all, but oldest than mine don't compile. It sounds so strange to me

pyther · 2010-02-15 23:08:08

You aren't being very clear.

Why can't you use a newer kernel? Is it because you want to use this omnislash patch?

The temp difference might be because of cpu scaling. I'm guessing it was enabled on debian and you likely did not configure scaling for arch.

ilkyest · 2010-02-15 23:16:13

No. The problem that I'm trying solve is the colision one. Ok?

Well. I tried compile the 2.6.32.8 kernel, with the patch I've mentioned. Ok? Well, the compiling were good. But, the colision issue persists.

Ok. I know so much the "omnislash kernel" and, as the colision problem persists, I tried, so, compile the omnislash one, that I know that this problem (resource colision) don't exist. I've looked in another forum, and those users say me that this problem (the colision one) affects the kernel 2.6.32 and newer than this. a lot of ubuntu users are experiencing problems with.

Because it, I am trying compile the omnislash one, that I've not the colision problem, and I could have a faster kernel than now. But 'cause the error above, I just can't compile this.

Now I've been understood?

Excuse-me if just now, but 8 years without conversation in english are so bad to me

Arch Linux

#1 2010-02-13 03:33:23

Issue during compiling a kernel

#2 2010-02-13 04:21:28

Re: Issue during compiling a kernel

#3 2010-02-15 22:32:07

Re: Issue during compiling a kernel

#4 2010-02-15 22:51:05

Re: Issue during compiling a kernel

#5 2010-02-15 23:03:01

Re: Issue during compiling a kernel

#6 2010-02-15 23:08:08

Re: Issue during compiling a kernel

#7 2010-02-15 23:16:13

Re: Issue during compiling a kernel

Board footer