[gentoo-user] NIC not detected after Kernel upgrade

[gentoo-user] NIC not detected after Kernel upgrade

[Guillermo Garron]

Hi,

I am new to Gentoo, and yes I am also new to compiling kernels.

Well after that introduction, I will give you the details.
I am running now

uname -a

Linux gentoo 2.6.25-gentoo-r8 #7 SMP Sun Nov 16 16:29:29 BOT 2008 i686
Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz GenuineIntel GNU/Linux

lspci

00:00.0 Host bridge: Intel Corporation 82P965/G965 Memory Controller
Hub (rev 02)
00:01.0 PCI bridge: Intel Corporation 82P965/G965 PCI Express Root Port (rev 02)
00:03.0 Communication controller: Intel Corporation 82P965/G965 HECI
Controller (rev 02)
00:19.0 Ethernet controller: Intel Corporation 82566DC Gigabit Network
Connection (rev 02)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB
UHCI Controller #4 (rev 02)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB
UHCI Controller #5 (rev 02)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2
EHCI Controller #2 (rev 02)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio
Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express
Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express
Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express
Port 3 (rev 02)
00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express
Port 4 (rev 02)
00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express
Port 5 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB
UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB
UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB
UHCI Controller #3 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2
EHCI Controller #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev f2)
00:1f.0 ISA bridge: Intel Corporation 82801HB/HR (ICH8/R) LPC
Interface Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801HB (ICH8) 4 port SATA
AHCI Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation G72 [GeForce
7300 SE] (rev a1)
03:00.0 IDE interface: Marvell Technology Group Ltd. 88SE6101
single-port PATA133 interface (rev b1)
07:03.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A
IEEE-1394a-2000 Controller (PHY/Link)


lsmod

Module                  Size  Used by
snd_seq                38000  0
snd_seq_device          8332  1 snd_seq
snd_hda_intel         314132  0
nvidia               6894516  26
snd_pcm                49028  1 snd_hda_intel
snd_timer              17032  2 snd_seq,snd_pcm
snd_page_alloc         10120  2 snd_hda_intel,snd_pcm
snd_hwdep               8708  1 snd_hda_intel
snd                    32308  6
snd_seq,snd_seq_device,snd_hda_intel,snd_pcm,snd_timer,snd_hwdep

this is my /etc/make.conf (if case there is any relevant info there)

# These settings were set by the catalyst build script that automatically
# built this stage.
# Please consult /etc/make.conf.example for a more detailed example.
CFLAGS="-O2 -march=i686 -pipe"
CXXFLAGS="-O2 -march=i686 -pipe"
# WARNING: Changing your CHOST is not something that should be done lightly.
# Please consult http://www.gentoo.org/doc/en/change-chost.xml before changing.
CHOST="i686-pc-linux-gnu"
MAKEOPTS="-j3"
GENTOO_MIRRORS="http://ftp.ucsb.edu/pub/mirrors/linux/gentoo/
http://distfiles.gentoo.org
http://www.ibiblio.org/pub/Linux/distributions/gentoo"
# USE="-qt3 -qt4 -arts -kde -ipv6 X dbus gtk gnome hal avahi dvd alsa
cdr firefox"
USE="-qt3 -qt4 -arts -kde dbus hal avahi mdnsresponder-compat X midi
gtk mp3 alsa"
INPUT_DEVICES="keyboard mouse"
VIDEO_CARDS="nvidia"


Here you can find the config file for my current kernel.

http://www.go2linux.org/pics/other_files/gentoo/guille.config.txt

And the used to generate the new kernel (where NIC is not detected)

http://www.go2linux.org/pics/other_files/gentoo/guille1.config.txt

Please help me with this problem.

If you would like to view a formated version of this info, please go to:

http://www.go2linux.org/forums/recompiling-gentoo-kernel-no-nic-after-that-t-14.html

best regards and thanks a lot in advance for your time.




-- 
Guillermo Garron
"Linux IS user friendly... It's just selective about who its friends are."
(Using Ubuntu, Debian, Gentoo)
http://feeds.feedburner.com/go2linux
http://www.go2linux.org

Re: [gentoo-user] NIC not detected after Kernel upgrade

[Dirk Heinrichs]

[-- Attachment #1: Type: text/plain, Size: 483 bytes --]

Am Sonntag, 15. Februar 2009 22:31:40 schrieb Guillermo Garron:

> Here you can find the config file for my current kernel.

This has CONFIG_E1000=y

> And the used to generate the new kernel (where NIC is not detected)

This has both CONFIG_E1000=y and CONFIG_E1000E=y, maybe that's the problem.

What does lspci -v tell about the used driver? Anything useful in the dmesg 
output?

BTW: There are also some other NICs enabled in both your configs.

HTH...

	Dirk

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

Re: [gentoo-user] NIC not detected after Kernel upgrade

[Kenneth Prugh]

[-- Attachment #1: Type: text/plain, Size: 173 bytes --]

I think you need just E1000E for your NIC.

I use E1000E <*> for my intel:

00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network
Connection (rev 03)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [gentoo-user] NIC not detected after Kernel upgrade

[Guillermo Garron]

On Sun, Feb 15, 2009 at 5:40 PM, Dirk Heinrichs
<dirk.heinrichs@online.de> wrote:
> Am Sonntag, 15. Februar 2009 22:31:40 schrieb Guillermo Garron:
>
>> Here you can find the config file for my current kernel.
>
> This has CONFIG_E1000=y
>
>> And the used to generate the new kernel (where NIC is not detected)
>
> This has both CONFIG_E1000=y and CONFIG_E1000E=y, maybe that's the problem.
>
> What does lspci -v tell about the used driver? Anything useful in the dmesg
> output?

Hi,
Thanks for your prompt response.

Here is the output of this command

sudo lspci -v | grep Ether

00:19.0 Ethernet controller: Intel Corporation 82566DC Gigabit Network
Connection (rev 02)

>
> BTW: There are also some other NICs enabled in both your configs.

Yes, that is because I am not good a compiling kernels and did not
know how to discover what NIC I have to enable only that driver or
module. :(

>
> HTH...
>
>        Dirk
>



-- 
Guillermo Garron
"Linux IS user friendly... It's just selective about who its friends are."
(Using Ubuntu, Debian, Gentoo)
http://feeds.feedburner.com/go2linux
http://www.go2linux.org

Re: [gentoo-user] NIC not detected after Kernel upgrade

[Guillermo Garron]

On Sun, Feb 15, 2009 at 5:50 PM, Kenneth Prugh <ken69267@gmail.com> wrote:
> I think you need just E1000E for your NIC.
>
> I use E1000E <*> for my intel:
>
> 00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network
> Connection (rev 03)
Hi,

I think that is the one I should use! cause it seems I have the same card.

I will try and let you know.

regards.

>



-- 
Guillermo Garron
"Linux IS user friendly... It's just selective about who its friends are."
(Using Ubuntu, Debian, Gentoo)
http://feeds.feedburner.com/go2linux
http://www.go2linux.org

Re: [gentoo-user] NIC not detected after Kernel upgrade

[Guillermo Garron]

On Sun, Feb 15, 2009 at 5:54 PM, Guillermo Garron
<guillermo.fedora@gmail.com> wrote:
> On Sun, Feb 15, 2009 at 5:50 PM, Kenneth Prugh <ken69267@gmail.com> wrote:
>> I think you need just E1000E for your NIC.
>>
>> I use E1000E <*> for my intel:
>>
>> 00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network
>> Connection (rev 03)
> Hi,
>
> I think that is the one I should use! cause it seems I have the same card.
>
> I will try and let you know.

I think I talked to fast, I have that enabled.

I will try to disable the other one, and lets see.

regards,
Guillermo.

>
> regards.
>
>>
>
>
>
> --
> Guillermo Garron
> "Linux IS user friendly... It's just selective about who its friends are."
> (Using Ubuntu, Debian, Gentoo)
> http://feeds.feedburner.com/go2linux
> http://www.go2linux.org
>



-- 
Guillermo Garron
"Linux IS user friendly... It's just selective about who its friends are."
(Using Ubuntu, Debian, Gentoo)
http://feeds.feedburner.com/go2linux
http://www.go2linux.org

[gentoo-user] Re: NIC not detected after Kernel upgrade

[Nikos Chantziaras]

Guillermo Garron wrote:
> On Sun, Feb 15, 2009 at 5:50 PM, Kenneth Prugh <ken69267@gmail.com> wrote:
>> I think you need just E1000E for your NIC.
>>
>> I use E1000E <*> for my intel:
>>
>> 00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network
>> Connection (rev 03)
> Hi,
> 
> I think that is the one I should use! cause it seems I have the same card.
> 
> I will try and let you know.

e1000 is for the PCI version.  e1000e is for the PCI Express version. 
It can be that there's a conflict if both are enabled.

Re: [gentoo-user] Re: NIC not detected after Kernel upgrade

[Guillermo Garron]

On Sun, Feb 15, 2009 at 6:09 PM, Nikos Chantziaras <realnc@arcor.de> wrote:
> Guillermo Garron wrote:
>>
>> On Sun, Feb 15, 2009 at 5:50 PM, Kenneth Prugh <ken69267@gmail.com> wrote:
>>>
>>> I think you need just E1000E for your NIC.
>>>
>>> I use E1000E <*> for my intel:
>>>
>>> 00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network
>>> Connection (rev 03)
>>
>> Hi,
>>
>> I think that is the one I should use! cause it seems I have the same card.
>>
>> I will try and let you know.
>
> e1000 is for the PCI version.  e1000e is for the PCI Express version. It can
> be that there's a conflict if both are enabled.

Hi,
thanks a lot for your help, I have tried both of them and no success, :(.
I have also disabled all other NICs in the kernel.

Here is my new config file

http://www.go2linux.org/pics/other_files/gentoo/guille4.config.txt

>
>
>



-- 
Guillermo Garron
"Linux IS user friendly... It's just selective about who its friends are."
(Using Ubuntu, Debian, Gentoo)
http://feeds.feedburner.com/go2linux
http://www.go2linux.org

Re: [gentoo-user] NIC not detected after Kernel upgrade

[Stroller]

On 15 Feb 2009, at 21:31, Guillermo Garron wrote:
> ...
> I am running now
>
> uname -a
>
> Linux gentoo 2.6.25-gentoo-r8 #7 SMP Sun Nov 16 16:29:29 BOT 2008 i686
> Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz GenuineIntel GNU/Linux
>
> ...
> And the used to generate the new kernel (where NIC is not detected)
>
> http://www.go2linux.org/pics/other_files/gentoo/guille1.config.txt

I'm inclined to sumbit to the expertise of others when choosing kernel  
compilation options, and so I generally boot a recent liveCD and take  
a copy of the kernel .config from there (`zcat /proc/config.gz`)

System Rescue CD uses a kernel of about the same vintage as the one  
you're trying to upgrade to. I suggest you boot with it & see if your  
NIC works. If so, copy the kernel config & `make oldconfig`.
http://www.sysresccd.org/Main_Page

Stroller.

Re: [gentoo-user] NIC not detected after Kernel upgrade

[Guillermo Garron]

On Sun, Feb 15, 2009 at 9:17 PM, Stroller
<stroller@stellar.eclipse.co.uk> wrote:
>
> On 15 Feb 2009, at 21:31, Guillermo Garron wrote:
>>
>> ...
>> I am running now
>>
>> uname -a
>>
>> Linux gentoo 2.6.25-gentoo-r8 #7 SMP Sun Nov 16 16:29:29 BOT 2008 i686
>> Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz GenuineIntel GNU/Linux
>>
>> ...
>> And the used to generate the new kernel (where NIC is not detected)
>>
>> http://www.go2linux.org/pics/other_files/gentoo/guille1.config.txt
>
> I'm inclined to sumbit to the expertise of others when choosing kernel
> compilation options, and so I generally boot a recent liveCD and take a copy
> of the kernel .config from there (`zcat /proc/config.gz`)
>
> System Rescue CD uses a kernel of about the same vintage as the one you're
> trying to upgrade to. I suggest you boot with it & see if your NIC works. If
> so, copy the kernel config & `make oldconfig`.

Thanks a lot, did not know about that I will try to make it that way.

best regards,

Guillermo.

> http://www.sysresccd.org/Main_Page
>
> Stroller.
>
>
>



-- 
Guillermo Garron
"Linux IS user friendly... It's just selective about who its friends are."
(Using Ubuntu, Debian, Gentoo)
http://feeds.feedburner.com/go2linux
http://www.go2linux.org

Re: [gentoo-user] NIC not detected after Kernel upgrade

[Dirk Heinrichs]

[-- Attachment #1: Type: text/plain, Size: 312 bytes --]

Am Sonntag, 15. Februar 2009 22:52:42 schrieb Guillermo Garron:

> sudo lspci -v | grep Ether
>
> 00:19.0 Ethernet controller: Intel Corporation 82566DC Gigabit Network
> Connection (rev 02)

Where did I write "|grep Ether"? That's pretty much useless as there is 
nothing new in it.

Bye...

	Dirk

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

Re: [gentoo-user] NIC not detected after Kernel upgrade

[Dirk Heinrichs]

[-- Attachment #1: Type: text/plain, Size: 382 bytes --]

Am Montag, 16. Februar 2009 02:17:36 schrieb Stroller:

> System Rescue CD uses a kernel of about the same vintage as the one  
> you're trying to upgrade to. I suggest you boot with it & see if your  
> NIC works. If so, copy the kernel config & `make oldconfig`.

Or even better: use lspci -v while running from CD, and enable the driver it 
tells you.

Bye...

	Dirk

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

Re: [gentoo-user] NIC not detected after Kernel upgrade

[daid kahl]

[-- Attachment #1: Type: text/plain, Size: 1717 bytes --]

2009/2/16 Guillermo Garron <guillermo.fedora@gmail.com>

> Hi,
>
> I am new to Gentoo, and yes I am also new to compiling kernels.
>
>
I recently got in to configuring my own kernel (I'm not sure if you're at
this level or using other people's .config files); it's a bit lazy and maybe
risky not to configure it yourself, but you have to start somewhere.

In any case, the two things I found most helpful are kccmp and
http://cateee.net.  The first is a program to compare two kernel
configurations, and tell you the differences between them, and so on,
displayed in a nice table in X; you can find it in the portage tree.  Before
I found that, I was literally like comparing the files by hand on print outs
and stuff...what a nightmare.  The other is a Debian developer's site, but
there is a large part on kernel configuration (specifically at
http://cateee.net/lkddb/).  I didn't actually find a really easy way to
search the site besides doing a google site-limited query (CONFIG_BLAH_BLAH
site:cateee.net), but once you get to a config page, at the bottom there is
also a google bar with a radio button for just searching that site.  There
could be better places to look for kernel configuration options, but that's
what I was using, and obviously, if you want to configure your kernel, you
should have a place to look up the options, and that database has a basic
description of most (but not all) configurations at least for up to 2.6.26
(maybe later, but that's what I'm using right now).  Maybe other people can
point to other resources?

Also, you should avoid using oldconfig except for really minor kernel
upgrades.  I know this is mentioned in documentation elsewhere, but just a
useful reminder.

~daid

[-- Attachment #2: Type: text/html, Size: 2196 bytes --]

Re: [gentoo-user] NIC not detected after Kernel upgrade

[Guillermo Garron]

On Tue, Feb 17, 2009 at 11:37 AM, daid kahl <daidxor@gmail.com> wrote:
>
>
> 2009/2/16 Guillermo Garron <guillermo.fedora@gmail.com>
>>
>> Hi,
>>
>> I am new to Gentoo, and yes I am also new to compiling kernels.
>>
>
> I recently got in to configuring my own kernel (I'm not sure if you're at
> this level or using other people's .config files); it's a bit lazy and maybe
> risky not to configure it yourself, but you have to start somewhere.
>
> In any case, the two things I found most helpful are kccmp and
> http://cateee.net.  The first is a program to compare two kernel
> configurations, and tell you the differences between them, and so on,
> displayed in a nice table in X; you can find it in the portage tree.  Before
> I found that, I was literally like comparing the files by hand on print outs
> and stuff...what a nightmare.  The other is a Debian developer's site, but
> there is a large part on kernel configuration (specifically at
> http://cateee.net/lkddb/).  I didn't actually find a really easy way to
> search the site besides doing a google site-limited query (CONFIG_BLAH_BLAH
> site:cateee.net), but once you get to a config page, at the bottom there is
> also a google bar with a radio button for just searching that site.  There
> could be better places to look for kernel configuration options, but that's
> what I was using, and obviously, if you want to configure your kernel, you
> should have a place to look up the options, and that database has a basic
> description of most (but not all) configurations at least for up to 2.6.26
> (maybe later, but that's what I'm using right now).  Maybe other people can
> point to other resources?
>
> Also, you should avoid using oldconfig except for really minor kernel
> upgrades.  I know this is mentioned in documentation elsewhere, but just a
> useful reminder.

Thanks a lot friend, I am trying to configure my Kernel myself (I am
not that lazy :)).

I will try all the advices here, and will come back to tell you which
was the one which works, it will take me some time, As I can only work
on this briefly at nights and on weekends.

regards.

>
> ~daid
>



-- 
Guillermo Garron
"Linux IS user friendly... It's just selective about who its friends are."
(Using Ubuntu, Debian, Gentoo)
http://feeds.feedburner.com/go2linux
http://www.go2linux.org

Re: [gentoo-user] NIC not detected after Kernel upgrade

[Guillermo Garron]

On Mon, Feb 16, 2009 at 5:36 PM, Dirk Heinrichs
<dirk.heinrichs@online.de> wrote:
> Am Sonntag, 15. Februar 2009 22:52:42 schrieb Guillermo Garron:
>
>> sudo lspci -v | grep Ether
>>
>> 00:19.0 Ethernet controller: Intel Corporation 82566DC Gigabit Network
>> Connection (rev 02)
>
> Where did I write "|grep Ether"? That's pretty much useless as there is
> nothing new in it.

Sorry pal.

I did no realize I was giving the same info twice, but using the full
version of the output with no greps. on the working kernel I got that
the driver that is working is E1000 but when I activate it on the new
kernel, it does not work either.

>
> Bye...
>
>        Dirk
>



-- 
Guillermo Garron
"Linux IS user friendly... It's just selective about who its friends are."
(Using Ubuntu, Debian, Gentoo)
http://feeds.feedburner.com/go2linux
http://www.go2linux.org

Re: [gentoo-user] NIC not detected after Kernel upgrade

[Guillermo Garron]

On Mon, Feb 16, 2009 at 5:40 PM, Dirk Heinrichs
<dirk.heinrichs@online.de> wrote:
> Am Montag, 16. Februar 2009 02:17:36 schrieb Stroller:
>
>> System Rescue CD uses a kernel of about the same vintage as the one
>> you're trying to upgrade to. I suggest you boot with it & see if your
>> NIC works. If so, copy the kernel config & `make oldconfig`.
>
> Or even better: use lspci -v while running from CD, and enable the driver it
> tells you.
>
> Bye...

Hi,

I have run lspci -v on a Crunchbang Linux live CD, here is the output

00:19.0 Ethernet controller: Intel Corporation 82566DC Gigabit Network
Connection (rev 02)
	Subsystem: Intel Corporation Device 0001
	Flags: bus master, fast devsel, latency 0, IRQ 216
	Memory at 92200000 (32-bit, non-prefetchable) [size=128K]
	Memory at 92224000 (32-bit, non-prefetchable) [size=4K]
	I/O ports at 20e0 [size=32]
	Capabilities: <access denied>
	Kernel driver in use: e1000e
	Kernel modules: e1000e

I will go to gentoo and configure the kernel that way.

>
>        Dirk
>



-- 
Guillermo Garron
"Linux IS user friendly... It's just selective about who its friends are."
(Using Ubuntu, Debian, Gentoo)
http://feeds.feedburner.com/go2linux
http://www.go2linux.org

Re: [gentoo-user] NIC not detected after Kernel upgrade

[Guillermo Garron]

Hi, I am top posting because it is solved.

I want to help you all for your help, I am not sure about the problem
but here are some hints, you will realize what it was.

As I said before, I used this info for the new configuration.

00:19.0 Ethernet controller: Intel Corporation 82566DC Gigabit Network
Connection (rev 02)
       Subsystem: Intel Corporation Device 0001
       Flags: bus master, fast devsel, latency 0, IRQ 216
       Memory at 92200000 (32-bit, non-prefetchable) [size=128K]
       Memory at 92224000 (32-bit, non-prefetchable) [size=4K]
       I/O ports at 20e0 [size=32]
       Capabilities: <access denied>
       Kernel driver in use: e1000e
       Kernel modules: e1000e

That info comes from

lspci -v

run on the Crunchbang Linux live CD.

But I have also realized that I always was saving my configurations as.
guille1.config, guille2.config, and so on. but this time I also did this.

cp guille5.config .config

and then compiled the kernel, I am almost sure that matters.

thanks again for your help and time.

regards,

Guillermo Garron


On Tue, Feb 17, 2009 at 8:40 PM, Guillermo Garron
<guillermo.fedora@gmail.com> wrote:
> On Mon, Feb 16, 2009 at 5:40 PM, Dirk Heinrichs
> <dirk.heinrichs@online.de> wrote:
>> Am Montag, 16. Februar 2009 02:17:36 schrieb Stroller:
>>
>>> System Rescue CD uses a kernel of about the same vintage as the one
>>> you're trying to upgrade to. I suggest you boot with it & see if your
>>> NIC works. If so, copy the kernel config & `make oldconfig`.
>>
>> Or even better: use lspci -v while running from CD, and enable the driver it
>> tells you.
>>
>> Bye...
>
> Hi,
>
> I have run lspci -v on a Crunchbang Linux live CD, here is the output
>
> 00:19.0 Ethernet controller: Intel Corporation 82566DC Gigabit Network
> Connection (rev 02)
>        Subsystem: Intel Corporation Device 0001
>        Flags: bus master, fast devsel, latency 0, IRQ 216
>        Memory at 92200000 (32-bit, non-prefetchable) [size=128K]
>        Memory at 92224000 (32-bit, non-prefetchable) [size=4K]
>        I/O ports at 20e0 [size=32]
>        Capabilities: <access denied>
>        Kernel driver in use: e1000e
>        Kernel modules: e1000e
>
> I will go to gentoo and configure the kernel that way.
>
>>
>>        Dirk
>>
>
>
>
> --
> Guillermo Garron
> "Linux IS user friendly... It's just selective about who its friends are."
> (Using Ubuntu, Debian, Gentoo)
> http://feeds.feedburner.com/go2linux
> http://www.go2linux.org
>



-- 
Guillermo Garron
"Linux IS user friendly... It's just selective about who its friends are."
(Using Ubuntu, Debian, Gentoo)
http://feeds.feedburner.com/go2linux
http://www.go2linux.org

Re: [gentoo-user] NIC not detected after Kernel upgrade

[Dale]

daid kahl wrote:
>
>
> Also, you should avoid using oldconfig except for really minor kernel
> upgrades.  I know this is mentioned in documentation elsewhere, but
> just a useful reminder.
>
> ~daid

This has been discussed on this list before.  Running make oldconfig
works fine.  I, and a lot of others, have said this many times.  I
configed one kernel about 5 years ago and have used oldconfig ever
since.  It is faster and less prone to problems than starting from scratch.

If you are going from 2.4 to 2.6, then you should start fresh.  I
recently went from 2.6.23 to a 2.6.28 with no problem, other than trying
to figure out that new group stuff. 

Dale

:-)  :-) 

Re: [gentoo-user] NIC not detected after Kernel upgrade

[daid kahl]

[-- Attachment #1: Type: text/plain, Size: 1369 bytes --]

> > Also, you should avoid using oldconfig except for really minor kernel
> > upgrades.  I know this is mentioned in documentation elsewhere, but
> > just a useful reminder.
> >
> > ~daid
>
> This has been discussed on this list before.  Running make oldconfig
> works fine.  I, and a lot of others, have said this many times.  I
> configed one kernel about 5 years ago and have used oldconfig ever
> since.  It is faster and less prone to problems than starting from scratch.
>
> If you are going from 2.4 to 2.6, then you should start fresh.  I
> recently went from 2.6.23 to a 2.6.28 with no problem, other than trying
> to figure out that new group stuff.
>
> Dale
>
>
Huh.  I was going from 2.6.23 to 2.6.26 about 2 weeks ago and using
oldconfig was giving me some major trouble as I recall.  Not sure
specifically now, but I know CONFIG_HPET_TIMER had to be turned off later
during manual configuration, or my machine was hanging after some ACPI
scripts.  This behavior is replicated elsewhere for similar hardware, though
the author claimed it was fixed after 2.6.25 which I found to clearly not be
the case.  I had also not manually configured my own kernel either, so I
thought it's worth the experience.

I could save my current configuration for 2.6.26 and try oldconfig again
from 2.6.23.9 to make another 2.6.26 kernel and see what the problem was.

~daid

[-- Attachment #2: Type: text/html, Size: 1748 bytes --]

Re: [gentoo-user] NIC not detected after Kernel upgrade

[daid kahl]

[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]

>
> I'm inclined to sumbit to the expertise of others when choosing kernel
> compilation options, and so I generally boot a recent liveCD and take a copy
> of the kernel .config from there (`zcat /proc/config.gz`)
>
> System Rescue CD uses a kernel of about the same vintage as the one you're
> trying to upgrade to. I suggest you boot with it & see if your NIC works. If
> so, copy the kernel config & `make oldconfig`.
> http://www.sysresccd.org/Main_Page
>
> Stroller.
>

I'm pretty sure the kernels used for LiveCDs are absolutely huge because
they just assume you have basically every piece of hardware available, and
thus take much longer to boot (comparing a LiveCD on my machine to my
kernel, maybe 4 to 5 times longer).  So, sure this will make your computer
work, but it doesn't really seem like a good way to go about things, at
least not other than for the first boot and a backup kernel.

Come to think of it, this sounds like an amazing way to make a backup kernel
for when something goes wrong so I don't have to throw in the Live CD
(assuming grub is still booting at that point).  But not for your primary
kernel for daily use.

~daid

[-- Attachment #2: Type: text/html, Size: 1517 bytes --]

Re: [gentoo-user] NIC not detected after Kernel upgrade

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 647 bytes --]

On Wed, 18 Feb 2009 19:59:38 +0900, daid kahl wrote:

> I'm pretty sure the kernels used for LiveCDs are absolutely huge because
> they just assume you have basically every piece of hardware available,
> and thus take much longer to boot (comparing a LiveCD on my machine to
> my kernel, maybe 4 to 5 times longer).

The kernel itself isn't that large, all the drivers are compiled as
modules and anyneeded for booting are stuffed into an initrd.

The slow boot times are due to the whole filesystem being stored as a
compressed image on a slow medium.


-- 
Neil Bothwick

Obscenity is the crutch of inarticulate motherfuckers.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] NIC not detected after Kernel upgrade

[Evgeniy Bushkov]

[-- Attachment #1: Type: text/plain, Size: 1896 bytes --]

daid kahl пишет:
>
>     > Also, you should avoid using oldconfig except for really minor
>     kernel
>     > upgrades. I know this is mentioned in documentation elsewhere, but
>     > just a useful reminder.
>     >
>     > ~daid
>
>     This has been discussed on this list before. Running make oldconfig
>     works fine. I, and a lot of others, have said this many times. I
>     configed one kernel about 5 years ago and have used oldconfig ever
>     since. It is faster and less prone to problems than starting from
>     scratch.
>
>     If you are going from 2.4 to 2.6, then you should start fresh. I
>     recently went from 2.6.23 to a 2.6.28 with no problem, other than
>     trying
>     to figure out that new group stuff.
>
>     Dale
>
>
> Huh. I was going from 2.6.23 to 2.6.26 about 2 weeks ago and using 
> oldconfig was giving me some major trouble as I recall. Not sure 
> specifically now, but I know CONFIG_HPET_TIMER had to be turned off 
> later during manual configuration, or my machine was hanging after 
> some ACPI scripts. This behavior is replicated elsewhere for similar 
> hardware, though the author claimed it was fixed after 2.6.25 which I 
> found to clearly not be the case. I had also not manually configured 
> my own kernel either, so I thought it's worth the experience.
>
> I could save my current configuration for 2.6.26 and try oldconfig 
> again from 2.6.23.9 to make another 2.6.26 kernel and see what the 
> problem was.
>
> ~daid
Hm, may be it's off-topic but I've seen such behavior on one of my 
servers - some ACPI events were hanging server with last kernels. The 
only thing I had to be done is to turn off ACPI in BIOS. Now service 
local isn't working and CPU frequency is not scaling also. Is this 
normal or can this parameter (CONFIG_HPET_TIMER) help me?

Best regards,
Evgeniy B.


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 5581 bytes --]