Mensaje del debate
Posible bug en las tarjetas Realtek RTL8168 (Gigabit ethernet) y Ralink RT2561S (Linksys wireless)
Received: by 10.114.106.1 with SMTP id e1mr2590774wac.1194894467538;
Mon, 12 Nov 2007 11:07:47 -0800 (PST)
Return-Path: <overdrive.open...@gmail.com>
Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175])
by mx.google.com with ESMTP id k36si22108861waf.2007.11.12.11.07.40;
Mon, 12 Nov 2007 11:07:47 -0800 (PST)
Received-SPF: pass (google.com: domain of overdrive.open...@gmail.com designates 66.249.92.175 as permitted sender) client-ip=66.249.92.175;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of overdrive.open...@gmail.com designates 66.249.92.175 as permitted sender) smtp.mail=overdrive.open...@gmail.com; dkim=pass (test mode) header...@gmail.com
Received: by ug-out-1314.google.com with SMTP id u2so730115uge
for <OpenBSD-Mexico@googlegroups.com>; Mon, 12 Nov 2007 11:07:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=beta;
h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding;
bh=img/iQT9cQWoAMhA8CiLJu+PPnLSVhf+0Q9cLjsKwyQ=;
b=H8yhB06SVfhU2+V39iOV8wxzoMTYqULPlY6icUKD8NnSxFYZ1rW57Izr07qVmpP2gbI1ovy1OOsAjJmfxnZbWrwsDvcqeFE02c6rKfjGTUejG9/EqABXyCJQY89KmgklaN2h9VNNDCCYYihs684AbzBCdeJIg2GjxdXh54FwnCI=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=beta;
h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding;
b=D7Qd8sBCHfYIGKkHc3Y3cNq3lDKMeSHfEIkm3OLQ5qXspuwb0FKFKQPOTH16ta+pPT8v5RnALn51Sof3FDl6TTdhn1HTFnuM6j+p8KMUA729dzFVUMoW95z53aBi7mGJRicrxngaSfZsAQDsoVEAa2xCUCxoMTzmsPXlsZpK/Zg=
Received: by 10.78.137.7 with SMTP id k7mr5812079hud.1194894447855;
Mon, 12 Nov 2007 11:07:27 -0800 (PST)
Return-Path: <overdrive.open...@gmail.com>
Received: from ?192.168.1.101? ( [82.14.74.208])
by mx.google.com with ESMTPS id i8sm6774826nfh.2007.11.12.11.07.26
(version=TLSv1/SSLv3 cipher=RC4-MD5);
Mon, 12 Nov 2007 11:07:27 -0800 (PST)
Message-ID: <4738A38E.8010...@gmail.com>
Date: Mon, 12 Nov 2007 19:03:42 +0000
From: Borja Tarraso <overdrive.open...@gmail.com>
User-Agent: Mail/News 1.5.0.9 (X11/20070902)
MIME-Version: 1.0
To: OpenBSD-Mexico@googlegroups.com
Subject: Re: Posible bug en las tarjetas Realtek RTL8168 (Gigabit ethernet)
y Ralink RT2561S (Linksys wireless)
References: <f4b1a4790709070743y34a46b58lae8ab8822d342...@mail.gmail.com> <5414e0910709070758y541b1f57s9f5ec365d7b3c...@mail.gmail.com> <003801c7f162$c9cfdb40$5d6f91c0$@com> <5ca35d40709070944i7056942dk590edd11430d4...@mail.gmail.com> <4737AC41.90...@gmail.com> <5ca35d40711120323l40469a30i6930753edf1e9...@mail.gmail.com> <40b34c120711120722j5992044byfffd8907a4680...@mail.gmail.com>
In-Reply-To: <40b34c120711120722j5992044byfffd8907a4680...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Hola Francisco,
pues creo que estas equivocado te muestro ciertos outputs:
Soportada por el kernel:
# grep 8169
GENERIC
re* at pci? # Realtek 8169/8169S/8110S
rgephy* at mii? # Realtek 8169S/8110S PHY
#
Detectada en el dmesg:
bash-3.2$ dmesg | grep re0
re0 at pci4 dev 0 function 0 "Realtek 8168" rev 0x01: RTL8168 2
(0x3800), apic 4 int 17 (irq 5), address 00:1a:4d:4c:18:b1
rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 2
bash-3.2$
Configurada y vista por el sistema operativo:
bash-3.2$ ifconfig -a
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33224
groups: lo
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
re0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
lladdr 00:1a:4d:4c:18:b1
media: Ethernet autoselect (10baseT half-duplex)
status: no carrier
ral0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
lladdr 00:1a:70:ac:9d:85
groups: wlan egress
media: IEEE802.11 autoselect (OFDM36 mode 11g)
status: active
ieee80211: nwid blackhats.es chan 11 bssid 00:1a:70:97:aa:c0
119dB 100dBm
inet6 fe80::21a:70ff:feac:9d85%ral0 prefixlen 64 scopeid 0x2
inet 192.168.1.101 netmask 0xffffff00 broadcast 192.168.1.255
pflog0: flags=0<> mtu 33224
enc0: flags=0<> mtu 1536
bash-3.2$
Saludos.
Borja Tarraso.
Francisco Valladolid wrote:
> On Nov 12, 2007 5:23 AM, HDC <fire...@gmail.com> wrote:
>
>> Desconozco si esto es realmente así, me refiero a si es un bug.
>> Creo que lo que tendrías que hacer es buscar en misc@, y luego enviar el
>> dmesg a misc@ y a dm...@openbsd.org.
>> Ahí te podrán decir si realmente es un bug o no.
>>
>> Saludos,
>> Hernán
>>
>> On Nov 11, 2007 10:28 PM, Borja Tarraso <overdrive.open...@gmail.com> wrote:
>>
>>> Hola,
>>>
>>> Debo decir que en mi caso trabajo con un Quad core a 64 bits y me
>>> funciona casi todo perfectamente. En concreto mi Realtek RTL8168 PCI-E
>>> Gigabit NIC, la cual me da como status de la tarjeta "no sense" al hacer
>>> un ifconfig -a. Y al intentar un dhclient me da un "re0: no
>>> link......... giving up". El cable esta perfectamente y la tarjeta
>>> tambien (ya que funciona con otros dos sistemas operativos distintos),
>>> por lo que estoy casi seguro que es un bug, alguien sabe algo al
>>> respecto? si ha sido anunciado o no ya? y en el caso, la posible
>>> solucion/patch?
>>>
>>> Tambien he podido ver un problema parecido en mi wireless linksys, en
>>> este caso cada poco tiempo (1 minuto) deja de funcionar, y tengo que
>>> bajar y subir la interfaz de nuevo y vuelve a funcionar bien. He probado
>>> con dos access points distintos, uno con WEP y otro sin WEP y con MAC
>>> ACLs. En este caso es una Linksys PCI express tambien con chipset Ralink
>>> RT2561S.
>>>
>>> Gracias, Overdrive.
>>>
>>>
>
> Corrijanme si estoy mal, pero al parecer el RTL8168 no es soportado
> por el driver re(4)
>
> Saludos.
>
>
>> --
>> # /dev/hdc
>> -> OpenBSDeros.org
>> hdc [at] openbsderos [dot] org
>> >
>>
>>
>
>
>
>
|
