| 1 |
Hello Dirk, |
| 2 |
|
| 3 |
Thanks for taking the time to reply. The combination of gentoo-sources |
| 4 |
and genkernel has been working quite well for the 2 yrs I've been |
| 5 |
running Gentoo. It's convenient to have grub.conf auto-magically |
| 6 |
updated and that's not been an issue. |
| 7 |
|
| 8 |
When upgrading from one kernel revision to another, oldconfig is nice |
| 9 |
because it makes the new kernel options obvious. Using menuconfig |
| 10 |
hides that information. Of course, as you point out, diff can be used |
| 11 |
after either tool to see exactly what has been changed. |
| 12 |
|
| 13 |
The messages I mentioned, i.e. "Loading modules" and "Activating mdev" |
| 14 |
appear during the boot process before /etc/init.d scripts are run (and, |
| 15 |
yes, it's "mdev", not "udev"). However, I don't know which program is |
| 16 |
running and printing these messages. |
| 17 |
|
| 18 |
'Tis good to hear that 2.6.27.4 is working for you. However my hardware |
| 19 |
(AMD64x2, IDE drive, etc) and kernel options are, I wager, different |
| 20 |
than yours and _something_ in 2.6.27 is unhappy. The question of the |
| 21 |
day is "What?". |
| 22 |
|
| 23 |
Regards, |
| 24 |
|
| 25 |
David |
| 26 |
|
| 27 |
On Tue, 4 Nov 2008 22:27:40 +0100 |
| 28 |
Dirk Heinrichs wrote: |
| 29 |
|
| 30 |
> Am Dienstag, 4. November 2008 20:51:10 schrieb David Relson: |
| 31 |
> |
| 32 |
> > Due to problems experienced with 2.6.25-gentoo-r7, I've built |
| 33 |
> > 2.6.27-gentoo-r2. I started with the 2.6.25-r7 .config file, ran |
| 34 |
> > "make oldconfig", then "genkernel all". |
| 35 |
> |
| 36 |
> Don't know if that helps, but anyway, here's what I usually do: |
| 37 |
> |
| 38 |
> I only use kernel.org kernels (vanilla-sources in Gentoo). They're |
| 39 |
> the same no matter the distro. |
| 40 |
> |
| 41 |
> I have a copy of my kernel config (in /etc/kernel/config). If you |
| 42 |
> configured your kernel appropriately, you can also find the config of |
| 43 |
> the running kernel in /proc/config(.gz). Upon a major kernel upgrade, |
| 44 |
> I run make menuconfig, load my old config file and check all the |
| 45 |
> important options, eventually switching on/off new options which I |
| 46 |
> find useful. |
| 47 |
> |
| 48 |
> I never ever ran make oldconfig. I also never ran genkernel. Why |
| 49 |
> should I? After leaving menuconfig it's just make, make |
| 50 |
> modules_install, make install (or copy the appropriate kernel file |
| 51 |
> to /boot manually). |
| 52 |
> |
| 53 |
> Then I run a self-written script which updates some symlinks in /boot |
| 54 |
> (so that I don't need to edit grub.conf) and cleans /lib/modules, |
| 55 |
> leaving only the currently running kernel and the new one arround, |
| 56 |
> together with their modules. |
| 57 |
> |
| 58 |
> I didn't have a kernel related boot problem since a very long time |
| 59 |
> now. But even if I had, I still have the old one. |
| 60 |
> |
| 61 |
> > The new 2.6.27 kernel appears |
| 62 |
> > to load modules OK, then hangs. The old 2.6.25-r7 kernel displays |
| 63 |
> > "Activating mdev" after it finishes loading modules. |
| 64 |
> |
| 65 |
> Don't know what mdev is (or is this a typo: udev), so I can't help |
| 66 |
> with this. |
| 67 |
> |
| 68 |
> > Any suggestions of what to check for or change? |
| 69 |
> |
| 70 |
> Try to diff both kernel configs. Look wether there's something |
| 71 |
> missing in the new one that was there in the old. Maybe try again |
| 72 |
> with the method described above. |
| 73 |
> |
| 74 |
> BTW: I'm running 2.6.27.4 w/o any problem. |
| 75 |
> |
| 76 |
> Bye... |
| 77 |
> |
| 78 |
> Dirk |
Archives