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
w
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
>
> 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
> tryi
> > 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,
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 o
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 Net
On Mon, Feb 16, 2009 at 5:40 PM, Dirk Heinrichs
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 con
On Mon, Feb 16, 2009 at 5:36 PM, Dirk Heinrichs
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 p
On Tue, Feb 17, 2009 at 11:37 AM, daid kahl wrote:
>
>
> 2009/2/16 Guillermo Garron
>>
>> 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);
2009/2/16 Guillermo Garron
> 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 y
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 whil
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...
On Sun, Feb 15, 2009 at 9:17 PM, Stroller
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
>>
>
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)
htt
On Sun, Feb 15, 2009 at 5:54 PM, Guillermo Garron
wrote:
> On Sun, Feb 15, 2009 at 5:50 PM, Kenneth Prugh 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)
>
On Sun, Feb 15, 2009 at 5:50 PM, Kenneth Prugh 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 th
On Sun, Feb 15, 2009 at 5:40 PM, Dirk Heinrichs
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 b
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)
signature.asc
Description: PGP signature
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.
W
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
lspc
20 matches
Mail list logo
