| 1 |
Some suggestions which you probably know, or follow, but just in case: |
| 2 |
|
| 3 |
On Monday 01 May 2006 21:05, maxim wexler wrote: |
| 4 |
|
| 5 |
> Ok, here's where it gets weird, at least to me: |
| 6 |
> |
| 7 |
> The symlink points to the new sources. When I cd |
| 8 |
> /usr/src/linux that's where I end up. |
| 9 |
|
| 10 |
I assume that you first check: |
| 11 |
|
| 12 |
# ls -la /usr/src |
| 13 |
|
| 14 |
where the symlink points to, because after you cd into it you can't readily |
| 15 |
see what directory you've descended into. |
| 16 |
|
| 17 |
> I run make |
| 18 |
> menuconfig, then make && make modules_install. Then I |
| 19 |
> copy bzImage to /boot/vmlinuz as always; take a quick |
| 20 |
> look around; check that the new /lib/modules dir(there |
| 21 |
> are now two, natch) is full of modular goodness, and |
| 22 |
> reboot. |
| 23 |
|
| 24 |
I don't use make install, because my set up (on the laptop is rather |
| 25 |
complicated) and so I always manually copy the kernel image. I use cp -i -v |
| 26 |
to get some feedback on what's happening and make sure that I overwrite only |
| 27 |
the files I choose to. Also, my modules have to be manually entered |
| 28 |
in /etc/modules.autoload.d/kernel-2.6, at least these modules which I always |
| 29 |
want installed automatically at boot. |
| 30 |
|
| 31 |
I first modprobe -v <module_name> one at a time to make sure that they do load |
| 32 |
without errors. Then enter their name in /etc/modules.autoload.d/kernel-2.6 |
| 33 |
and finally run modules-update. |
| 34 |
|
| 35 |
> At the grub prompt I run >root, >kernel /vmlinuz #the |
| 36 |
> *new* kernel and >boot as I always do. |
| 37 |
|
| 38 |
Don't you have a menu.lst or grub.conf to set up your grub menu so that you |
| 39 |
don't have to make manual entries at boot time? |
| 40 |
|
| 41 |
> CERTAIN modules load. CERTAIN modules don't, |
| 42 |
> predominantly having to do with communications |
| 43 |
> hardware. |
| 44 |
|
| 45 |
Anything in /etc/modules.autoload.d/kernel-2.6 should load automatically or |
| 46 |
print an error. Latest changes in udev slightly complicate matters - see |
| 47 |
other concurrent thread on this topic. |
| 48 |
|
| 49 |
> The thing makes it to the prompt. I log in. Run uname. |
| 50 |
> Yikes! It *is* _running_ the old kernel. |
| 51 |
> |
| 52 |
> BUT, it's _booting_ from the new! I checked! |
| 53 |
|
| 54 |
There's a bit of a contradiction in terms here! I suggest that you are |
| 55 |
inadvertently booting the old kernel image and that's what's shown. |
| 56 |
|
| 57 |
If you check the /usr/src/linux symlink after reboot where does it lead you? |
| 58 |
|
| 59 |
HTH. |
| 60 |
|
| 61 |
-- |
| 62 |
Regards, |
| 63 |
Mick |
Archives