FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian User

 
 
LinkBack Thread Tools
 
Old 09-10-2010, 07:12 AM
Camaleón
 
Default detect ethernet card?

On Thu, 09 Sep 2010 21:24:57 +0200, Atu wrote:

> On Thursday 09 September 2010 09:19:30 pm Camaleón wrote:

>> (...)
>>
>> Try "/sbin/ifconfig" to check if the card is there.
>
> I tried and it isn't. I see "lo" but not "eth0".

Then review the "dmesg | grep eth" log, as David told you.

If something is wrong with your card/kernel module, dmesg will tell.

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: pan.2010.09.10.07.12.06@gmail.com">http://lists.debian.org/pan.2010.09.10.07.12.06@gmail.com
 
Old 09-10-2010, 08:10 AM
Geoff Simmons
 
Default detect ethernet card?

Hi Atu,

On Fri, Sep 10, 2010 at 02:42:12AM +0200, Atu wrote:
> 00.19.0 Ethernet controller: Intel Corporation 82567LM-3 Gigabit Network Connection (rev 02)

Support for the 82567LM-3 (PCI ID 8086:10de) was added to the e1000e
driver in linux-2.6 2.6.26-25, which is part of the recent[1] Debian
Lenny point release (5.0.6).

In your situation, you could either:

* Acquire an update CD/DVD[2] and upgrade your system to 5.0.6.

* Temporarily use an alternate network device (e.g. supported wireless
LAN adapter) in order to communicate with a Debian archive mirror,
then upgrade your system to 5.0.6.

* Manually acquire the relevant linux-image-2.6.26-2-* package for
your system from packages.debian.org[3], transfer and install via
dpkg.

An interface for this network device should become available once your
system is restarted with the updated kernel.

Geoff

[1] http://www.debian.org/News/2010/20100904
[2] http://www.debian.org/CD/faq/#update-cd
[3] http://packages.debian.org/linux-image-2.6.26-2


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100910081021.GA26525@tammy.lan.gsimmons.org">htt p://lists.debian.org/20100910081021.GA26525@tammy.lan.gsimmons.org
 
Old 09-10-2010, 08:33 PM
Atu
 
Default detect ethernet card?

On Friday 10 September 2010 10:10:22 am Geoff Simmons wrote:
> Support for the 82567LM-3 (PCI ID 8086:10de) was added to the e1000e
> driver in linux-2.6 2.6.26-25, which is part of the recent[1] Debian
> Lenny point release (5.0.6).
>
> upgrade your system to 5.0.6.
>
> An interface for this network device should become available once your
> system is restarted with the updated kernel.

That worked. Problem solved. Thank you very much!

I still don't have e1000e or e1000 in /etc/modules, but since the problem is solved, that should not matter any more.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201009102233.11680.atucelulis@googlemail.com">http ://lists.debian.org/201009102233.11680.atucelulis@googlemail.com
 
Old 09-10-2010, 09:54 PM
Stephen Powell
 
Default detect ethernet card?

On Fri, 10 Sep 2010 16:33:11 -0400 (EDT), atucelulis@googlemail.com wrote:
> On Friday 10 September 2010 10:10:22 am Geoff Simmons wrote:
>> Support for the 82567LM-3 (PCI ID 8086:10de) was added to the e1000e
>> driver in linux-2.6 2.6.26-25, which is part of the recent[1] Debian
>> Lenny point release (5.0.6).
>>
>> upgrade your system to 5.0.6.
>>
>> An interface for this network device should become available once your
>> system is restarted with the updated kernel.
>
> That worked. Problem solved. Thank you very much!
>
> I still don't have e1000e or e1000 in /etc/modules, but since the
> problem is solved, that should not matter any more.

As a general rule, kernel modules which function as a device driver
for a piece of hardware do not need to be listed (and should not be
listed) in /etc/modules.
They will be loaded automatically by udev if the kernel module has
an alias which matches the id of the piece of hardware. For example,

user@icc07:~$ /sbin/lspcmcia -v
Socket 0 Bridge: [yenta_cardbus] (bus ID: 0000:00:03.0)
Configuration: state: on ready: unknown
Voltage: 5.0V Vcc: 5.0V Vpp: 0.0V
Socket 0 Device 0: [xirc2ps_cs] (bus ID: 0.0)
Configuration: state: on
Product Name: Compaq Netelligent 10/100 PC Card CPQ-10/100 1.00
Identification: manf_id: 0x0183 card_id: 0x010a
function: 6 (network)
prod_id(1): "Compaq" (0x54f7c49c)
prod_id(2): "Netelligent 10/100 PC Card" (0xefe96769)
prod_id(3): "CPQ-10/100" (0x7a590ccf)
prod_id(4): "1.00" (0x83dbf271)
Socket 1 Bridge: [yenta_cardbus] (bus ID: 0000:00:03.1)
Configuration: state: on ready: unknown
user@icc07:~$ /sbin/modinfo xirc2ps_cs
filename: /lib/modules/2.6.26-2-686/kernel/drivers/net/pcmcia/xirc2ps_cs.ko
license: Dual MPL/GPL
description: Xircom PCMCIA ethernet driver
alias: pcmcia:m*c*f*fn*pfn*pa44A09D9CpbB44DEECFpc*pd*
alias: pcmcia:m*c*f*fn*pfn*pa816CC815pb174397DBpc*pd*
alias: pcmcia:m*c*f*fn*pfn*pa54F7C49CpbEFE96769pc*pd*
alias: pcmcia:m*c*f*fn*pfn*pa54F7C49Cpb9FD2F0A2pc*pd*
alias: pcmcia:m*c*f*fn*pfn*pa2E3EE845pb*pcF7188E46pd*
alias: pcmcia:m*c*f*fn*pfn*pa2E3EE845pb*pc3E08D609pd*
alias: pcmcia:m*c*f*fn*pfn*pa2E3EE845pb*pc2464A6E3pd*
alias: pcmcia:m*c*f*fn*pfn*pa2E3EE845pb*pc947D9073pd*
alias: pcmcia:m*c*f*fn*pfn*pa2E3EE845pb*pc0EC0AC37pd*
alias: pcmcia:m*c*f*fn*pfn*pa1B3B94FEpb*pcF381C1A2pd*
alias: pcmcia:m01BFc010Af*fn*pfn*pa*pb*pc*pd*
alias: pcmcia:m*c*f*fn*pfn00pa2E3EE845pbECA401BFpc*pd*
alias: pcmcia:m*c*f*fn*pfn00pa2E3EE845pb*pcF1403719pd*
alias: pcmcia:m*c*f*fn*pfn00pa2E3EE845pb*pc76DF1D29pd*
alias: pcmcia:m*c*f*fn*pfn00pa2E3EE845pb*pcA650C32Apd*
alias: pcmcia:m*c*f*fn*pfn00pa2E3EE845pb*pc80609023pd*
alias: pcmcia:m*c*f*fn*pfn00pa2E3EE845pb*pc0EA978EApd*
alias: pcmcia:m0138c110Af*fn*pfn00pa*pb*pc*pd*
alias: pcmcia:m0089c110Af*fn*pfn00pa*pb*pc*pd*
depends: pcmcia,pcmcia_core
vermagic: 2.6.26-2-686 SMP mod_unload modversions 686
parm: if_port:int
parm: full_duplex:int
parm: do_sound:int
parm: lockup_hack:int
user@icc07:~$

In this case, the xirc2ps_cs kernel module is loaded automatically
because its third alias matches the piece of hardware. (Notice the
correspondence between the hexadecimal identifiers for prod_id(1)
and prod_id(2) with the hexadecimal identifiers in the alias.) The
exact mechanism for matching is bus-dependent (isa, pcmcia, pci,
etc.) But the point is that udev finds a match between a piece of
hardware and a kernel module via the aliases of the kernel module.
If a kernel module is known to work with a piece of hardware, but
it does not have a suitable internal alias defined, an alias statement
may be added to a .conf file in /etc/modprobe.d to define the alias.
This is the preferred method for loading a kernel module which is
a device driver.

--
.'`. Stephen Powell
: :' :
`. `'`
`-


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 324848364.18841.1284155697333.JavaMail.root@md01.w ow.synacor.com">http://lists.debian.org/324848364.18841.1284155697333.JavaMail.root@md01.w ow.synacor.com
 
Old 09-11-2010, 07:28 PM
Atu
 
Default detect ethernet card?

On Friday 10 September 2010 11:54:57 pm Stephen Powell wrote:
> On Fri, 10 Sep 2010 16:33:11 -0400 (EDT), atucelulis@googlemail.com wrote:
> > On Friday 10 September 2010 10:10:22 am Geoff Simmons wrote:
> >> Support for the 82567LM-3 (PCI ID 8086:10de) was added to the e1000e
> >> driver in linux-2.6 2.6.26-25, which is part of the recent[1] Debian
> >> Lenny point release (5.0.6).
> >>
> >> upgrade your system to 5.0.6.
> >>
> >> An interface for this network device should become available once your
> >> system is restarted with the updated kernel.
> >
> > That worked. Problem solved. Thank you very much!
> >
> > I still don't have e1000e or e1000 in /etc/modules, but since the
> > problem is solved, that should not matter any more.
>
> As a general rule, kernel modules which function as a device driver
> for a piece of hardware do not need to be listed (and should not be
> listed) in /etc/modules.
> They will be loaded automatically by udev if the kernel module has
> an alias which matches the id of the piece of hardware.

Thanks for the info Steven. I like this approach of not needing to know which driver module to use and instead let the kernel pick it.

I wonder why the original error message ("SIOCSIFADDR" and so on) had to be so cryptic though. Couldn't it just have said "No support for this ethernet chip (yet)"? That would have made it easier to see that upgrading could help.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201009112128.44803.atucelulis@googlemail.com">http ://lists.debian.org/201009112128.44803.atucelulis@googlemail.com
 
Old 09-13-2010, 03:30 PM
Stephen Powell
 
Default detect ethernet card?

On Sat, 11 Sep 2010 15:28:44 -0400 (EDT), Atu wrote:
> On Friday 10 September 2010 11:54:57 pm Stephen Powell wrote:
>> As a general rule, kernel modules which function as a device driver
>> for a piece of hardware do not need to be listed (and should not be
>> listed) in /etc/modules.
>> They will be loaded automatically by udev if the kernel module has
>> an alias which matches the id of the piece of hardware.
>
> Thanks for the info Steven.

That's Stephen, not Steven. (Same pronunciation though.)

> I like this approach of not needing to
> know which driver module to use and instead let the kernel pick it.
>
> I wonder why the original error message ("SIOCSIFADDR" and so on)
> had to be so cryptic though.

That's no fun! Where's the mystery? ;-)

Seriously, though,

#ifup eth0
[...]
SIOCSIFADDR: No such device

Seems pretty plain to me. No such device. If you know you have
an ethernet adapter, and you're getting a message such as
"no such device", it should be fairly obvious that the device was
not recognized.

> Couldn't it just have said
> "No support for this ethernet chip (yet)"?

It loads drivers for cards that it recognizes. It doesn't usually
issue any messages at all for devices it does not recognize.
But if it did issue any messages, it would be in bootup messages,
("dmesg|less") not messages issued during "ifup eth0".

> That would have made it easier to see that upgrading could help.

An old release cannot usually tell you that a newer release will
support your card. That's because the old release doesn't know
if or when support will be added.

--
.'`. Stephen Powell
: :' :
`. `'`
`-


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 1859790224.72999.1284391808288.JavaMail.root@md01. wow.synacor.com">http://lists.debian.org/1859790224.72999.1284391808288.JavaMail.root@md01. wow.synacor.com
 

Thread Tools




All times are GMT. The time now is 05:43 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org