| 1 |
2008/6/3 Konrad Okurowski <dm.konrad@×××××.com>: |
| 2 |
|
| 3 |
> Hi, |
| 4 |
> IMO when performing "make" after make clean and make menuconfig (assuming |
| 5 |
> you want to change something in kernel) builds kernel image and modules as |
| 6 |
> well. After that I run rm -rf /lib/modules/<kernel dir> and make && make |
| 7 |
> modules_install. Then there shouldn't be any problem. (also [emerge -av |
| 8 |
> $(qdepends -CNQ virtual/linux-sources)] would be nice). |
| 9 |
> |
| 10 |
> Kfiaciarka |
| 11 |
> |
| 12 |
> 2008/6/3 Duncan <1i5t5.duncan@×××.net>: |
| 13 |
> |
| 14 |
> Beso <givemesugarr@×××××.com> posted |
| 15 |
>> d257c3560806030201y23df89fdy1cf12ae0bb3b772a@××××××××××.com, excerpted |
| 16 |
>> below, on Tue, 03 Jun 2008 09:01:04 +0000: |
| 17 |
>> |
| 18 |
>> > the problem is that with the old normal config the kernel detects one |
| 19 |
>> > processor and one core and it works, loading the modules, but when |
| 20 |
>> > enabling simetric multiprocessing the kernel detects just one processor |
| 21 |
>> > and one core and then it fails to load modules because of a different |
| 22 |
>> > executable format in the modules. |
| 23 |
>> |
| 24 |
>> This indicates that the modules and the kernel aren't matched. IOW, you |
| 25 |
>> apparently compiled the new kernel but failed to compile the matching |
| 26 |
>> modules, so it's trying to use the old ones, which don't match the new |
| 27 |
>> kernel, so it won't load them. |
| 28 |
>> |
| 29 |
>> Even if it's the exact same kernel you compiled, if you change options, |
| 30 |
>> particularly something as big as SMP, you'll need to recompile the kernel |
| 31 |
>> modules as well. |
| 32 |
>> |
| 33 |
>> Also note that if you use an initrd/initramfs, you'll need to redo it, |
| 34 |
>> loading the new modules as appropriate into it as well as placing them in |
| 35 |
>> the normal /lib/modules/<kern-ver>/ dir. I don't run an initramfs/ |
| 36 |
>> initrd, so have never learned the technical intricacies thereof, but |
| 37 |
>> wherever it's trying to load them from, you don't have the right ones |
| 38 |
>> there for it to load. |
| 39 |
>> |
| 40 |
>> One way or the other, with or without the initrd/initramfs, the kernel is |
| 41 |
>> trying to load modules that don't match the kernel, and failing. Correct |
| 42 |
>> that, and you will have fixed at least that problem, altho it's possible |
| 43 |
>> you'll then have others to fix as well. |
| 44 |
>> |
| 45 |
>> -- |
| 46 |
>> Duncan - List replies preferred. No HTML msgs. |
| 47 |
>> "Every nonfree program has a lord, a master -- |
| 48 |
>> and if you use the program, he is your master." Richard Stallman |
| 49 |
>> |
| 50 |
>> -- |
| 51 |
>> gentoo-amd64@l.g.o mailing list |
| 52 |
>> |
| 53 |
>> |
| 54 |
> |
| 55 |
> |
| 56 |
> -- |
| 57 |
> pozdrawiam |
| 58 |
> Konrad Okurowski <dm.konrad@×××××.com> |
| 59 |
> Key Fingerprint = D993 3823 F20D 3B8D 2719 3012 2FE8 |
| 60 |
> |
| 61 |
|
| 62 |
i've found out the problem: i'm using a /boot not on the /partition and on |
| 63 |
the new pc i've set the partition table in a different way, so boot didn't |
| 64 |
mount at startup. the make modules_install && make install would put the |
| 65 |
right stuff in the right place, but when restarting the kernel image read |
| 66 |
was the old one (the one without smp support) and so the different |
| 67 |
executable file format errror, using the new smp modules and the old |
| 68 |
single-core kernel image. i'm really feeling really stupid for not having |
| 69 |
noticed this earlier, but maybe since the issue got out at about 23.00 after |
| 70 |
a full day of work maybe it's plausible. |
| 71 |
thanks to all of you who have answered to my question. |
| 72 |
|
| 73 |
ps. duncan, when you've got some spare time could you please post the |
| 74 |
scripts for the kernel automation build if it's not bothersome. thanks |
| 75 |
again. |
| 76 |
|
| 77 |
-- |
| 78 |
dott. ing. beso |
Archives