From: Peter Tenenbaum on
I just finished building a new computer around the Intel DH55TC motherboard.
I would like to configure the computer to use DHCP via its built-in
ethernet tap, but the ethernet was not detected or configured on
installation. There is no eth0 entry in /etc/network/interfaces, no eth0
entry displayed by ifconfig, no dhcpd.conf file is present, and dhcpd is not
listed in inetd.conf.

I suspect that the problem is that the motherboard is so new that it's not
supported in the 2.6.26 version of the kernel: when I looked at the Intel
webpage relevant to the board,
http://www.intel.com/support/motherboards/desktop/dh55tc/sb/CS-031186.htm,
it suggests that a LAN driver may be needed for Linux, and I infer from
their table of information that this is more likely to be the case for
kernel versions prior to about 2.6.31.

So what I think I need to do is the following:

1. Download and install the LAN driver
2. Manually configure the system so that it recognizes the Ethernet tap
3. Add eth0 to /etc/network/interfaces
4. add a dhcpd.conf file
5. add dhcpd to inetd.conf.

Does that sound about right, or is the reality simpler / less simple than
that?

Assuming I've got it right: how do I accomplish step 2?

Thanks in advance,
-PT
From: papul on
On 6/2/2010 10:41 AM, Peter Tenenbaum wrote:
> I just finished building a new computer around the Intel DH55TC
> motherboard. I would like to configure the computer to use DHCP via its
> built-in ethernet tap, but the ethernet was not detected or configured
> on installation. There is no eth0 entry in /etc/network/interfaces, no
> eth0 entry displayed by ifconfig, no dhcpd.conf file is present, and
> dhcpd is not listed in inetd.conf.
>
> I suspect that the problem is that the motherboard is so new that it's
> not supported in the 2.6.26 version of the kernel: when I looked at the
> Intel webpage relevant to the
> board, http://www.intel.com/support/motherboards/desktop/dh55tc/sb/CS-031186.htm,
> it suggests that a LAN driver may be needed for Linux, and I infer from
> their table of information that this is more likely to be the case for
> kernel versions prior to about 2.6.31.
>
> So what I think I need to do is the following:
>
> 1. Download and install the LAN driver
> 2. Manually configure the system so that it recognizes the Ethernet tap
> 3. Add eth0 to /etc/network/interfaces
> 4. add a dhcpd.conf file
> 5. add dhcpd to inetd.conf.
>
> Does that sound about right, or is the reality simpler / less simple
> than that?
>
> Assuming I've got it right: how do I accomplish step 2?
>
> Thanks in advance,
> -PT

What is your current kernel version? An update might solve the issue.



--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/hu546e$5k6$2(a)dough.gmane.org
From: Peter Tenenbaum on
Wolodja -- the output from the lspci command is

00:19.0 Ethernet controller [0200]: Intel Corporation Device [8086:10f0]
(rev 06)

Papul -- the kernel is 2.6.26-2-amd64.

Sounds like I should just go ahead and update my kernel, and that should
solve some other, unrelated and less critical issues. I'll try that tonight
(right now it's 7:15 AM local time and I'm off to work).

Thanks for the suggestions,
-PT

On Tue, Jun 1, 2010 at 10:11 PM, Peter Tenenbaum <quarkpt(a)gmail.com> wrote:

> I just finished building a new computer around the Intel DH55TC
> motherboard. I would like to configure the computer to use DHCP via its
> built-in ethernet tap, but the ethernet was not detected or configured on
> installation. There is no eth0 entry in /etc/network/interfaces, no eth0
> entry displayed by ifconfig, no dhcpd.conf file is present, and dhcpd is not
> listed in inetd.conf.
>
> I suspect that the problem is that the motherboard is so new that it's not
> supported in the 2.6.26 version of the kernel: when I looked at the Intel
> webpage relevant to the board,
> http://www.intel.com/support/motherboards/desktop/dh55tc/sb/CS-031186.htm,
> it suggests that a LAN driver may be needed for Linux, and I infer from
> their table of information that this is more likely to be the case for
> kernel versions prior to about 2.6.31.
>
> So what I think I need to do is the following:
>
> 1. Download and install the LAN driver
> 2. Manually configure the system so that it recognizes the Ethernet tap
> 3. Add eth0 to /etc/network/interfaces
> 4. add a dhcpd.conf file
> 5. add dhcpd to inetd.conf.
>
> Does that sound about right, or is the reality simpler / less simple than
> that?
>
> Assuming I've got it right: how do I accomplish step 2?
>
> Thanks in advance,
> -PT
>
From: Wolodja Wentland on
On Wed, Jun 02, 2010 at 07:14 -0700, Peter Tenenbaum wrote:
> Wolodja -- the output from the lspci command is

> 00:19.0 Ethernet controller [0200]: Intel Corporation Device [8086:10f0] (rev
> 06)

Yes, [1] confirms that you need at least 2.6.31 for your NIC - I already
outlined the easiest way to install 2.6.32 in the previous mail.

Have a nice day

Wolodja

[1] http://kmuto.jp/debian/hcl/index.rhtmlx?check=1&lspci=8086:10f0
--
.''`. Wolodja Wentland <wentland(a)cl.uni-heidelberg.de>
: :' :
`. `'` 4096R/CAF14EFC
`- 081C B7CD FF04 2BA9 94EA 36B2 8B7F 7D30 CAF1 4EFC
From: Peter Tenenbaum on
Wolodja -- in looking at the instructions on the backports.org website, I
surmise that the instructions will download the new packages from the
backports.org website and then install the updated kernel and everything
that the updated kernel needs (ie, all its dependencies).

Unfortunately, since the problem I'm trying to solve is that the network
connection on my Debian workstation isn't supported, I'm assuming that this
won't work. I think that leaves me with two options:

1. Walk through the dependency information provided at backports.org to
identify all the packages which are needed by the updated kernel; download
on my working computer (WinXP) and copy to optical or USB drive; use that to
do the install.

2. Since my Debian installation is brand new, I could also simply replace
the Lenny install with a Squeeze install -- essentially, start over Squeeze.

Does option (1) sound utterly unappealing? I'm inclined to give it a shot,
knowing that I can always fall back on option (2) if I totally botch (1).

-PT

On Wed, Jun 2, 2010 at 7:14 AM, Peter Tenenbaum <quarkpt(a)gmail.com> wrote:

> Wolodja -- the output from the lspci command is
>
> 00:19.0 Ethernet controller [0200]: Intel Corporation Device [8086:10f0]
> (rev 06)
>
> Papul -- the kernel is 2.6.26-2-amd64.
>
> Sounds like I should just go ahead and update my kernel, and that should
> solve some other, unrelated and less critical issues. I'll try that tonight
> (right now it's 7:15 AM local time and I'm off to work).
>
> Thanks for the suggestions,
> -PT
>
>
> On Tue, Jun 1, 2010 at 10:11 PM, Peter Tenenbaum <quarkpt(a)gmail.com>wrote:
>
>> I just finished building a new computer around the Intel DH55TC
>> motherboard. I would like to configure the computer to use DHCP via its
>> built-in ethernet tap, but the ethernet was not detected or configured on
>> installation. There is no eth0 entry in /etc/network/interfaces, no eth0
>> entry displayed by ifconfig, no dhcpd.conf file is present, and dhcpd is not
>> listed in inetd.conf.
>>
>> I suspect that the problem is that the motherboard is so new that it's not
>> supported in the 2.6.26 version of the kernel: when I looked at the Intel
>> webpage relevant to the board,
>> http://www.intel.com/support/motherboards/desktop/dh55tc/sb/CS-031186.htm,
>> it suggests that a LAN driver may be needed for Linux, and I infer from
>> their table of information that this is more likely to be the case for
>> kernel versions prior to about 2.6.31.
>>
>> So what I think I need to do is the following:
>>
>> 1. Download and install the LAN driver
>> 2. Manually configure the system so that it recognizes the Ethernet
>> tap
>> 3. Add eth0 to /etc/network/interfaces
>> 4. add a dhcpd.conf file
>> 5. add dhcpd to inetd.conf.
>>
>> Does that sound about right, or is the reality simpler / less simple than
>> that?
>>
>> Assuming I've got it right: how do I accomplish step 2?
>>
>> Thanks in advance,
>> -PT
>>
>
>