On Tue, 2008-10-28 at 15:18 -0400, Massimo Savino wrote:
> Hi JP,
> Thank you for this -- you refer to a .config from 2.6.27.x -- do you
> mean that you create the .config new and you have to rebuild it
> totally from scratch? Normally when I uncompress the tarball I just
> import (copy over) the config from another kernel build -- I'd really
> not do all that again if I can avoid it. I've even run both an old
> (2.6.25.x or 184.108.40.206
) config against a new config from 2.6.27 through
> diff -y and none of the changes seem significant enough to justify
> having to do it again from scratch .... :(
> Come to think of it I noticed the same problem with 220.127.116.11
> On Tue, Oct 28, 2008 at 2:05 PM, firstname.lastname@example.org
> I do have some problems with the 2.6.27 kernel and I have to
> the .config
> from scratch using the 2.6.27 .config and putting all my
> things in.
> After tthat it works !
> JP Pozzi
> On Mon, 2008-10-27 at 23:51 -0400, Massimo Savino wrote:
> > Hi all,
> > I'm having a bit of trouble with my latest kernel source
> > 18.104.22.168
. It compiles without problem, but when I boot, I
> lose all
> > network capability, and it even throws my Windows box off
> > network.
> > Normally I have a DHCP internal router, and I usually end up
> with an
> > IP of 192.168.2.X . However on the new kernel I have an
> > address assigned of 169.x.x.x, and of course I can't
> > The thing I can't figure out is how this happened. Usually I
> just take
> > my old config, re-run it, and save it with a new name
> (version), and
> > that's the end of that.
> > I'm wondering though -- does this 2.6.27 kernel have
> something new I
> > should be aware of? Otherwise I really can't think of what
> might be
> > causing the non-connectivity...
> > I am using an eVGA 132-CK-NF78-A1 board, with built-in
> > (forcedeth??). If anyone would like to see some configs,
> just let me
> > know and I'll attach.
> > Thank you in advance for any help you can suggest.
> > Mass