[equinux] Agere systems ET-131x PCI-E
CONSUELO FLORES
conny310 en gmail.com
Jue Mar 5 12:04:59 EST 2009
Realice un: lspci -vv
La respuesta es:
1. 02:00.0 Ethernet controller: Agere Systems ET-131x PCI-E Ethernet
Controller (rev 02)
2. Subsystem: Agere Systems ET-131x PCI-E Ethernet Controller
3. Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
4. Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
5. Latency: 0, Cache Line Size: 64 bytes
6. Interrupt: pin A routed to IRQ 11
7. Region 0: Memory at fcc00000 (64-bit, non-prefetchable)
[size=2M]
8. Expansion ROM at fcee0000 [disabled] [size=128K]
9. Capabilities: [40] Power Management version 2
10. Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA
PME(D0+,D1+,D2-,D3hot+,D3cold+)
11. Status: D0 PME-Enable- DSel=0 DScale=0 PME-
12. Capabilities: [48] Express Endpoint IRQ 0
13. Device: Supported: MaxPayload 256 bytes, PhantFunc 0,
ExtTag-
14. Device: Latency L0s <4us, L1 <32us
15. Device: AtnBtn- AtnInd- PwrInd-
16. Device: Errors: Correctable- Non-Fatal- Fatal-
Unsupported-
17. Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
18. Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
19. Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1,
Port 0
20. Link: Latency L0s <1us, L1 <32us
21. Link: ASPM L0s Enabled RCB 64 bytes CommClk-
ExtSynch-
22. Link: Speed 2.5Gb/s, Width x1
23. Capabilities: [5c] Message Signalled Interrupts: Mask- 64bit+
Queue=0/0 Enable-
24. Address: 0000000000000000 Data: 0000
25. Capabilities: [100] Advanced Error Reporting
26. Capabilities: [130] Virtual Channel
27. Capabilities: [14c] Device Serial Number
49-02-03-fe-ff-3b-13-02
28.
29. 07:00.0 Ethernet controller: Broadcom Corporation Unknown device 165a
30. Subsystem: Hewlett-Packard Company Unknown device 7051
31. Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
32. Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast
>TAbort- <TAbort- <MAbort- >SERR- <PERR-
33. Latency: 0, Cache Line Size: 64 bytes
34. Interrupt: pin A routed to IRQ 10
35. Region 0: Memory at fcff0000 (64-bit, non-prefetchable)
[size=64K]
36. Capabilities: [48] Power Management version 3
37. Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot+,D3cold+)
38. Status: D0 PME-Enable- DSel=0 DScale=1 PME-
39. Capabilities: [50] Vital Product Data
40. Capabilities: [58] Vendor Specific Information
41. Capabilities: [e8] Message Signalled Interrupts: Mask- 64bit+
Queue=0/0 Enable-
42. Address: 1d80129000becc4c Data: 2080
43. Capabilities: [d0] Express Endpoint IRQ 0
44. Device: Supported: MaxPayload 128 bytes, PhantFunc 0,
ExtTag+
45. Device: Latency L0s <4us, L1 unlimited
46. Device: AtnBtn- AtnInd- PwrInd-
47. Device: Errors: Correctable- Non-Fatal- Fatal-
Unsupported-
48. Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
49. Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
50. Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s,
Port 0
51. Link: Latency L0s <4us, L1 <64us
52. Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch-
53. Link: Speed 2.5Gb/s, Width x1
54. Capabilities: [100] Advanced Error Reporting
55. Capabilities: [13c] Virtual Channel
56. Capabilities: [160] Device Serial Number
33-c9-fc-fe-ff-0b-1e-00
57. Capabilities: [16c] Power Budgeting
58. 0a:04.0 Ethernet controller: VIA Technologies, Inc. VT6105
[Rhine-III] (rev 8b)
59. Subsystem: D-Link System Inc Unknown device 1405
60. Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
ParErr- Stepping- SERR- FastB2B-
61. Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR-
62. Latency: 64 (750ns min, 2000ns max), Cache Line Size: 64
bytes
63. Interrupt: pin A routed to IRQ 169
64. Region 0: I/O ports at e800 [size=256]
65. Region 1: Memory at fdfffc00 (32-bit, non-prefetchable)
[size=256]
66. Capabilities: [44] Power Management version 2
67. Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
68. Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Que te parece en que crees que este fallando?
2009/3/5 Ovnicraft <ovnicraft en gmail.com>
>
>
> 2009/3/4 CONSUELO FLORES <conny310 en gmail.com>
>
>> Adicional a la de placa madre tengo otra que es d-link con socket PCI, la
>> de la placa madre es una broadcom y no me reconoce los drivers ..
>> *ejecutando un lspci:*
>>
>> 02:00.0 Ethernet controller: Agere Systems ET-131x PCI-E Ethernet
>> Controller (rev 02)
>> 07:00.0 Ethernet controller: Broadcom Corporation Unknown device 165a
>> 0a:04.0 Ethernet controller: VIA Technologies, Inc. VT6105 [Rhine-III]
>> (rev 8b)
>
>
> rhine, agere estan reconocidas, talves con la broadcom tengas que ponerle
> algun firmware en /lib/firmware (en slackware)
>
>>
>> Aparentemente reconoce los driver..
>> Ahora con las instrucciones que me diste:
>>
>> fbiee:~# *mii-tool*
>> eth0: negotiated 100baseTx-FD flow-control, link ok
>>
>
>>
>> fbiee:~# *ifconfig eth0*
>> eth0 Link encap:Ethernet HWaddr 00:1E:58:9C:55:3D
>> inet addr:172.31.10.11 Bcast:172.31.10.255 Mask:255.255.255.0
>> inet6 addr: 2800:68:11:12:21e:58ff:fe9c:553d/64 Scope:Global
>> inet6 addr: fe80::21e:58ff:fe9c:553d/64 Scope:Link
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>> RX packets:369620 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:98241 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:1000
>> RX bytes:36232218 (34.5 MiB) TX bytes:121522258 (115.8 MiB)
>> Interrupt:169 Base address:0xe800
>>
>> fbiee:~# *ifconfig eth1*
>> eth1: error fetching interface information: Device not found
>>
>> fbiee:~# *ifconfig eth2*
>> eth2: error fetching interface information: Device not found
>>
>> Al momento de ingresar al :/etc/network/interface.
>> No se cual es la interface.
>> Y cuando reinicio los servicios de red.
>>
>> fbiee:/etc/network# */etc/init.d/networking restart*
>> Reconfiguring network interfaces...SIOCSIFADDR: No such device
>> eth2: ERROR while getting interface flags: No such device
>> SIOCSIFNETMASK: No such device
>> eth2: ERROR while getting interface flags: No such device
>> Failed to bring up eth2.
>> done.
>>
>> Att.
>>
>> Consuelo Flores
>>
>>
> Te recomiendo darle un lspci -vv para que veas a detalle que modulo esta
> trabajando con tus 2 tarjetas que estan reconocidas.
> Si quieres mostrar la salida te recomiendo usar
> http://equinux.pastebin.com/.
>
>>
>>
>>
>>
>>
>>
>>
>> 2009/3/4 Ovnicraft <ovnicraft en gmail.com>
>>
>>
>>>
>>> 2009/3/4 CONSUELO FLORES <conny310 en gmail.com>
>>>
>>>> Estimados:
>>>>
>>>> tengo instalado en mi servidor debian etch, adquiri una tarjeta de red
>>>> PCI y express 1x, el problema sq reconoce los drivers pero no sube la
>>>> tarjeta como puedo hacer para que le reconozca. mi tarjeta de red es una
>>>> Agere systems ET-131x PCI-E
>>>
>>>
>>> Si el modulo del kernel reconocio la tarjeta pues esta lista para usar,
>>> pq crees que no esta reconocida?
>>>
>>> si es una tarjeta pci-e, seria la eth1 (la de la placa madre es eth0).
>>>
>>> ifconfig eth1, te puede ayudar
>>> mii-tool, si tienes un cable de red conectado a la tarjeta que quieres
>>> usar.
>>>
>>> te daran info suficiente.
>>>
>>>>
>>>>
>>>> Att.
>>>>
>>>> Consuelo Flores
>>>>
>>>> _______________________________________________
>>>> Lista de correo de equinux
>>>> Para enviar un correo a la lista envie a:
>>>> equinux en nuevared.org
>>>> Para suscribirse o desuscribirse entre a:
>>>> http://nuevared.org/mailman/listinfo/equinux_nuevared.org
>>>>
>>>>
>>>
>>>
>>> --
>>> [b]question = (to) ? be : !be; .[/b]
>>>
>>> _______________________________________________
>>> Lista de correo de equinux
>>> Para enviar un correo a la lista envie a:
>>> equinux en nuevared.org
>>> Para suscribirse o desuscribirse entre a:
>>> http://nuevared.org/mailman/listinfo/equinux_nuevared.org
>>>
>>>
>>
>> _______________________________________________
>> Lista de correo de equinux
>> Para enviar un correo a la lista envie a:
>> equinux en nuevared.org
>> Para suscribirse o desuscribirse entre a:
>> http://nuevared.org/mailman/listinfo/equinux_nuevared.org
>>
>>
>
>
> --
> [b]question = (to) ? be : !be; .[/b]
>
> _______________________________________________
> Lista de correo de equinux
> Para enviar un correo a la lista envie a:
> equinux en nuevared.org
> Para suscribirse o desuscribirse entre a:
> http://nuevared.org/mailman/listinfo/equinux_nuevared.org
>
>
------------ próxima parte ------------
Se ha borrado un adjunto en formato HTML...
URL: <http://nuevared.org/pipermail/equinux_nuevared.org/attachments/20090305/511564d5/attachment.html>
Más información sobre la lista de distribución equinux