| 1 |
On Mon, 4 Dec 2006 18:32:39 +0000 (UTC), james wrote: |
| 2 |
|
| 3 |
> > Re-install the kernel with "cd /usr/src/linux && make install". |
| 4 |
|
| 5 |
> 1] Well I used what I usually use to build a kernel: |
| 6 |
> make && make install_modules |
| 7 |
> cp System.map /boot/System.map-2.6.18-gentoo-r3 |
| 8 |
> cp arch/x86_64/boot/bzImage /boot/kernel-2.6.18-gentoo-r3 |
| 9 |
> cp .config /boot/config-2.6.18-gentoo-r3 |
| 10 |
|
| 11 |
You didn't need to make the kernel again, or install the modules. All |
| 12 |
you needed to do was copy the relevant files to /boot, which make |
| 13 |
install takes care of. |
| 14 |
|
| 15 |
> > Re-emerge grub |
| 16 |
> |
| 17 |
> 2] emerge -v grub |
| 18 |
> |
| 19 |
> |
| 20 |
> Something really weird is going on. I building a kernel all I had in |
| 21 |
> /boot was the 2.6.18-gentoo-r3 files listed above. After running |
| 22 |
> 'emerge -v grub' |
| 23 |
> all of the previous files and including the System.map, kernel |
| 24 |
> and config files suddenly appeared under /boot. I keep old kernels |
| 25 |
> around for 4 or 5 generations back. |
| 26 |
|
| 27 |
That seems weird, unless /boot wasn't mounted before. |
| 28 |
|
| 29 |
> > Install GRUB to the MBR again (this step may not be necessary, but |
| 30 |
> > it's best to be safe). |
| 31 |
> |
| 32 |
> 3] from the handbook: |
| 33 |
> grub-install /dev/hda |
| 34 |
> |
| 35 |
> That's it? |
| 36 |
|
| 37 |
I prefer to do it manually |
| 38 |
|
| 39 |
grub |
| 40 |
root (hdx,y) |
| 41 |
setup (hdx) |
| 42 |
quit |
| 43 |
|
| 44 |
|
| 45 |
-- |
| 46 |
Neil Bothwick |
| 47 |
|
| 48 |
Top Oxymorons Number 20: Synthetic natural gas |
Archives