LSPCI shows network card, but the card refuses to come up

[Bijoy Lobo]

Hello all

I have 2 cards on my system. I had no errors while Expert Install of Debian
netinstall. even lspci shows me 2 ethernet controllers, However I cannot
bring the 2nd interface up.

ifconfig eth1 tells me no such interface
ifconfig -a show me only eth0 and lo

[The_Ace]

Post by Bijoy Lobo
Hello all
I have 2 cards on my system. I had no errors while Expert Install of
Debian netinstall. even lspci shows me 2 ethernet controllers, However I
cannot bring the 2nd interface up.
ifconfig eth1 tells me no such interface
ifconfig -a show me only eth0 and lo
--
Thanks and Regards
Bijoy Lobo
Paladion Networks

Does lspci -v (or -vv) show what driver and kernel modules are in use
for that card ?


--
The mysteries of the Universe are revealed when you break stuff.

[Camaleón]

Post by Bijoy Lobo
I have 2 cards on my system. I had no errors while Expert Install of
Debian netinstall. even lspci shows me 2 ethernet controllers, However I
cannot bring the 2nd interface up.

Show us the output of these two commands:

lspci -v | grep -i ether
dmesg | grep -i eth

Post by Bijoy Lobo
ifconfig eth1 tells me no such interface ifconfig -a show me only eth0
and lo

Also, show us the content of your "/etc/network/interfaces" file.

Greetings,

[Bob Proulx]

Post by Camaleón

Post by Bijoy Lobo
I have 2 cards on my system. I had no errors while Expert Install of
Debian netinstall. even lspci shows me 2 ethernet controllers, However I
cannot bring the 2nd interface up.

lspci -v | grep -i ether

Ahem... 'lspci | grep -i eth' is good but 'lspci -v' is paragraph
formatted and so finding that with grep is more trouble. You need a
"paragraph grep" of which there are many different programs and
techniques. Perl is always available these days so perhaps using perl
is easiest.

lspci -v | perl -00 -ne 'm/eth/i && print'

The extra -v information isn't usually useful though. YMMV.

Post by Camaleón
dmesg | grep -i eth

Post by Bijoy Lobo
ifconfig eth1 tells me no such interface ifconfig -a show me only eth0
and lo

Also, show us the content of your "/etc/network/interfaces" file.

Please also show us the output of

ip addr show

and also

cat /etc/udev/rules.d/70-persistent-net.rules

Bob

[Bijoy Lobo]

Hello guys,


Thanks alot. I sloved the problem. It was the older kernel which didnt have
support for my Atheros Card. I did a modprobe and it fixed the problem

Post by Bob Proulx

Post by Camaleón

Post by Bijoy Lobo
I have 2 cards on my system. I had no errors while Expert Install of
Debian netinstall. even lspci shows me 2 ethernet controllers, However

I

Post by Camaleón

Post by Bijoy Lobo
cannot bring the 2nd interface up.

lspci -v | grep -i ether

Ahem... 'lspci | grep -i eth' is good but 'lspci -v' is paragraph
formatted and so finding that with grep is more trouble. You need a
"paragraph grep" of which there are many different programs and
techniques. Perl is always available these days so perhaps using perl
is easiest.
lspci -v | perl -00 -ne 'm/eth/i && print'
The extra -v information isn't usually useful though. YMMV.

Post by Camaleón
dmesg | grep -i eth

Post by Bijoy Lobo
ifconfig eth1 tells me no such interface ifconfig -a show me only eth

0

Post by Bob Proulx

Post by Camaleón

Post by Bijoy Lobo
and lo

Also, show us the content of your "/etc/network/interfaces" file.

Please also show us the output of
ip addr show
and also
cat /etc/udev/rules.d/70-persistent-net.rules
Bob

[Alberto Fuentes]

Post by Bob Proulx
Ahem... 'lspci | grep -i eth' is good but 'lspci -v' is paragraph
formatted and so finding that with grep is more trouble. You need a
"paragraph grep" of which there are many different programs and
techniques. Perl is always available these days so perhaps using perl
is easiest.

for the shake of completesness

lspci -v | grep -A5 -i eth

or the even easier
lspci -v | grep -5 -i eth

greets!
aL

[Bob Proulx]

Post by Alberto Fuentes
for the shake of completesness

I commend your thoroughness. But...

Post by Alberto Fuentes
lspci -v | grep -A5 -i eth

But why did you stop at five lines? Aren't most network devices going
to print more lines than that? And it misses the "kernel driver in
use" line which is useful information.

Example:

***@fury:~# lspci -v | perl -00 -ne 'm/eth/i && print'
3f:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5755 Gigabit Ethernet PCI Express (rev 02)
Subsystem: Hewlett-Packard Company Device 280c
Flags: bus master, fast devsel, latency 0, IRQ 28
Memory at e0400000 (64-bit, non-prefetchable) [size=64K]
Expansion ROM at <ignored> [disabled]
Capabilities: [48] Power Management version 3
Capabilities: [50] Vital Product Data
Capabilities: [58] Vendor Specific Information: Len=78 <?>
Capabilities: [e8] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [d0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Virtual Channel
Capabilities: [160] Device Serial Number 00-1b-78-ff-fe-b0-a3-14
Capabilities: [16c] Power Budgeting <?>
Kernel driver in use: tg3

***@fury:~# lspci -v | grep -A5 -i eth
3f:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5755 Gigabit Ethernet PCI Express (rev 02)
Subsystem: Hewlett-Packard Company Device 280c
Flags: bus master, fast devsel, latency 0, IRQ 28
Memory at e0400000 (64-bit, non-prefetchable) [size=64K]
Expansion ROM at <ignored> [disabled]
Capabilities: [48] Power Management version 3

Post by Alberto Fuentes
or the even easier
lspci -v | grep -5 -i eth

Can't leave off the '-A' --after-context part since otherwise -NUM is
the same as --context not --after-context.

***@fury:~# lspci -v | grep -5 -i eth
Capabilities: [78] Express Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [128] Power Budgeting <?>
Kernel driver in use: nouveau

3f:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5755 Gigabit Ethernet PCI Express (rev 02)
Subsystem: Hewlett-Packard Company Device 280c
Flags: bus master, fast devsel, latency 0, IRQ 28
Memory at e0400000 (64-bit, non-prefetchable) [size=64K]
Expansion ROM at <ignored> [disabled]
Capabilities: [48] Power Management version 3

Bob

[Alberto Fuentes]

Post by Bob Proulx
But why did you stop at five lines? Aren't most network devices going
to print more lines than that? And it misses the "kernel driver in
use" line which is useful information.

I see, in my case, 5 was enough to show everything :)

Post by Bob Proulx
Can't leave off the '-A' --after-context part since otherwise -NUM is
the same as --context not --after-context.

I said even easier, because the info you are looking for shows up the
same as with the qualifier, and you don’t have to remember witch is
witch (and less typing!)

that said, i have a bind grep='grep --color' witch i think is a must as
well ;)

greets!
aL

[Camaleón]

Post by Bob Proulx

Post by Camaleón

Post by Bijoy Lobo
I have 2 cards on my system. I had no errors while Expert Install of
Debian netinstall. even lspci shows me 2 ethernet controllers,
However I cannot bring the 2nd interface up.

lspci -v | grep -i ether

Ahem... 'lspci | grep -i eth' is good but 'lspci -v' is paragraph
formatted and so finding that with grep is more trouble. You need a
"paragraph grep" of which there are many different programs and
techniques. Perl is always available these days so perhaps using perl
is easiest.
lspci -v | perl -00 -ne 'm/eth/i && print'
The extra -v information isn't usually useful though. YMMV.

(...)

Let's try out both:

***@stt008:~$ lspci -v | grep -i ether
00:19.0 Ethernet controller: Intel Corporation 82566DM-2 Gigabit Network Connection (rev 02)
11:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet

Subsystem: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet



***@stt008:~$ lspci -v | perl -00 -ne 'm/eth/i && print'
00:19.0 Ethernet controller: Intel Corporation 82566DM-2 Gigabit Network Connection (rev 02)
Subsystem: Super Micro Computer Inc Device 10bd
Flags: bus master, fast devsel, latency 0, IRQ 1276
Memory at dc600000 (32-bit, non-prefetchable) [size=128K]
Memory at dc625000 (32-bit, non-prefetchable) [size=4K]
I/O ports at 1820 [size=32]
Capabilities: <access denied>
Kernel driver in use: e1000e
Kernel modules: e1000e

11:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 20
I/O ports at 2000 [size=256]
Memory at dc300000 (32-bit, non-prefetchable) [size=256]
[virtual] Expansion ROM at dc400000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: r8169
Kernel modules: r8169

Nah, yours is too verbose for this matter ;-). Indeed, the extra information
(-v) can be omited as we just wanted to know what card it was.

Greetings,

[Andrei POPESCU]

Post by Camaleón
Nah, yours is too verbose for this matter ;-). Indeed, the extra information
(-v) can be omited as we just wanted to know what card it was.

In which case -nn is very useful.

Kind regards,
Andrei

[Camaleón]

Post by Andrei POPESCU

Post by Camaleón
Nah, yours is too verbose for this matter ;-). Indeed, the extra
information (-v) can be omited as we just wanted to know what card it
was.

In which case -nn is very useful.

To know the card's name/model, "-v" or "-nn" flags are both fine.

Greetings,