| 1 |
On Sat, 31 Oct 2009 20:00:35 +0200, Nikos Chantziaras wrote: |
| 2 |
|
| 3 |
> So, to sum it up, when you update to a new kernel, first update the |
| 4 |
> symlink (or let the ebuild take care of it), build the kernel, boot it, |
| 5 |
> *then* rebuild external modules (like ati-drivers). If you know what |
| 6 |
> you're doing, you don't need to reboot before rebuilding external |
| 7 |
> modules, for example I do: |
| 8 |
> |
| 9 |
> ebuild /usr/portage/x11-drivers/ati-drivers/ati-drivers-N.ebuild compile |
| 10 |
> mkdir /lib/modules/KERNEL_VERSION/video |
| 11 |
> cp |
| 12 |
> /var/tmp/portage/x11-drivers/ati-drivers-N/work/common/lib/modules/fglrx/build_mod/2.6.x/fglrx.ko |
| 13 |
> /lib/modules/KERNEL_VERSION/video/ |
| 14 |
|
| 15 |
I don't use ati, but with other modules, this is not necessary. As long |
| 16 |
as /usr/srx/linux contains a valid .config, you can build modules against |
| 17 |
that kernel without running or even compiling it. |
| 18 |
|
| 19 |
|
| 20 |
-- |
| 21 |
Neil Bothwick |
| 22 |
|
| 23 |
Thesaurus: ancient reptile with an excellent vocabulary |
Archives