Resucitando un Samsung V25: Conexión inalámbrica detecta pero no conecta

Imagen de watjilpa
0 puntos

Buenas noches:
Estoy intentando sacarle partido a un viejo Samsung V25 de principios de siglo. He instalado Lubuntu (con ele) 13.04 y todo funciona perfectamente -dentro de lo que cabe, se entiende- menos la conexión inalámbrica. El caso es que el portátil detecta las redes circundantes. Pero cuando le indico que conecte a la mía parece que lo intenta un rato, pero al cabo, vuelve al estado de no conectado pero con redes inalámbricas disponibles.

Más abajo os dejo la salida lspci y la de iwconfig.

En la lspci intuyo que la línea que importa es la correspondiente a Network Controller. Lo que me escama es que en ella no figure una referencia a "wireless" y se me ocurre que pudiera ser que el portátil tuviera "Network controller" pero no "wireless controller" aunque no sé si eso es posible.

En la iwconfig me inquieta la parte que dice "Access Point: None" y también la última parte, en la que indica "no wireless extensions"

Ahora mismo estoy conectado con el cable y, como digo, todo funciona bien. ¿Alguna sugerencia?. Gracias por anticipado. Saludos

SALIDA LSPCI
watviejuno@watviejuno-SENS-V25:~$ lspci
00:00.0 Host bridge: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface (rev 03)
00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 03)
00:1d.0 USB controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 02)
00:1d.2 USB controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 02)
00:1d.7 USB controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 82)
00:1f.0 ISA bridge: Intel Corporation 82801DB/DBL (ICH4/ICH4-L) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801DB (ICH4) IDE Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 02)
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 02)
02:03.0 CardBus bridge: Ricoh Co Ltd RL5c475 (rev 80)
02:07.0 Network controller: Samsung Electro-Mechanics Co., Ltd. MagicLAN SWL-2210P 802.11b [Intersil ISL3874] (rev 01)
02:08.0 Ethernet controller: Intel Corporation 82801DB PRO/100 VE (LOM) Ethernet Controller (rev 82)
02:0d.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22A IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx]

SALIDA IWCONFIG

watviejuno@watviejuno-SENS-V25:~$ iwconfig
wlan0 IEEE 802.11b ESSID:"g\xC6isQ\xFFJ\xEC)\xCD\xBA\xAB\xF2\xFB\xE3F|\xC2T\xF8\x1B\xE8\xE7\x8DvZ.c3\x9F\xC9\x9A"
Mode:Managed Frequency:2.412 GHz Access Point: None
Bit Rate:2 Mb/s Sensitivity=1/3
Retry short limit:8 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=0/70 Signal level=-73 dBm Noise level=-73 dBm
Rx invalid nwid:0 Rx invalid crypt:40 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:268 Missed beacon:0

wifi0 IEEE 802.11b ESSID:"g\xC6isQ\xFFJ\xEC)\xCD\xBA\xAB\xF2\xFB\xE3F|\xC2T\xF8\x1B\xE8\xE7\x8DvZ.c3\x9F\xC9\x9A"
Mode:Managed Frequency:2.412 GHz Access Point: None
Bit Rate:2 Mb/s Sensitivity=1/3
Retry short limit:8 RTS thr:off Fragment thr:off
Power Management:off

lo no wireless extensions.

eth0 no wireless extensions.

Imagen de .doc
+1
+1
-1

si dices que tu Network Manager detecta las redes, tu problema no parece deberse a la tarjeta inalámbrica, sino a la configuración de tu conexión con tu router. Revísalo

+1
+1
-1
Imagen de elnetotaca
+1
0
-1

Como dice .doc, no es la tarjeta.
habre la terminal y teclea;
ping google.com

dejalo que corra por 6 segundos, y luego ctrl+c
pega aqui el resultado.

+1
0
-1

unzip; strip; touch; finger; mount; fsck; more; yes; unmount; sleep
Es lo que hago a diario....... En Linux mal pensados!

Imagen de watjilpa
+1
0
-1

1.- En cuanto a la sugerencia de .doc, los parámetros de conexión son idénticos a los que tiene otro portátil más moderno con el que sí me conecto a internet, salvo la dirección MAC, pero entiendo que esto último es normal

2.- Elnetotaca me pide el resultado del ping google.com. Decir que, lógicamente, lo he hecho conectado a través del cable, y esto es lo que indica:

watviejuno@watviejuno-SENS-V25:~$ ping google.com
PING google.com (173.194.41.224) 56(84) bytes of data.
64 bytes from mad01s15-in-f0.1e100.net (173.194.41.224): icmp_seq=1 ttl=55 time=20.6 ms
64 bytes from mad01s15-in-f0.1e100.net (173.194.41.224): icmp_seq=2 ttl=55 time=22.0 ms
64 bytes from mad01s15-in-f0.1e100.net (173.194.41.224): icmp_seq=3 ttl=55 time=21.4 ms
64 bytes from mad01s15-in-f0.1e100.net (173.194.41.224): icmp_seq=4 ttl=55 time=20.7 ms
64 bytes from mad01s15-in-f0.1e100.net (173.194.41.224): icmp_seq=5 ttl=55 time=21.0 ms
64 bytes from mad01s15-in-f0.1e100.net (173.194.41.224): icmp_seq=6 ttl=55 time=21.6 ms
64 bytes from mad01s15-in-f0.1e100.net (173.194.41.224): icmp_seq=7 ttl=55 time=21.4 ms
64 bytes from mad01s15-in-f0.1e100.net (173.194.41.224): icmp_seq=8 ttl=55 time=21.2 ms
64 bytes from mad01s15-in-f0.1e100.net (173.194.41.224): icmp_seq=9 ttl=55 time=20.4 ms
64 bytes from mad01s15-in-f0.1e100.net (173.194.41.224): icmp_seq=10 ttl=55 time=22.6 ms
64 bytes from mad01s15-in-f0.1e100.net (173.194.41.224): icmp_seq=11 ttl=55 time=20.4 ms
64 bytes from mad01s15-in-f0.1e100.net (173.194.41.224): icmp_seq=12 ttl=55 time=21.2 ms
64 bytes from mad01s15-in-f0.1e100.net (173.194.41.224): icmp_seq=13 ttl=55 time=20.6 ms
64 bytes from mad01s15-in-f0.1e100.net (173.194.41.224): icmp_seq=14 ttl=55 time=21.3 ms
64 bytes from mad01s15-in-f0.1e100.net (173.194.41.224): icmp_seq=15 ttl=55 time=21.1 ms
64 bytes from mad01s15-in-f0.1e100.net (173.194.41.224): icmp_seq=16 ttl=55 time=21.3 ms
64 bytes from mad01s15-in-f0.1e100.net (173.194.41.224): icmp_seq=17 ttl=55 time=21.0 ms
64 bytes from mad01s15-in-f0.1e100.net (173.194.41.224): icmp_seq=18 ttl=55 time=21.3 ms
64 bytes from mad01s15-in-f0.1e100.net (173.194.41.224): icmp_seq=19 ttl=55 time=22.0 ms
64 bytes from mad01s15-in-f0.1e100.net (173.194.41.224): icmp_seq=20 ttl=55 time=21.5 ms
64 bytes from mad01s15-in-f0.1e100.net (173.194.41.224): icmp_seq=21 ttl=55 time=20.9 ms

Una pregunta: ¿Tendría sentido comprar un usb de conexión inalámbrica?

Gracias y saludos,
Wat

+1
0
-1
Imagen de elnetotaca
+1
0
-1

lo que busco ver es algo como esto;

--- google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 16.651/17.005/17.153/0.205 ms

ese es el resultado que me da a mi

+1
0
-1

unzip; strip; touch; finger; mount; fsck; more; yes; unmount; sleep
Es lo que hago a diario....... En Linux mal pensados!

Imagen de watjilpa
+1
-1
-1

watviejuno@watviejuno-SENS-V25:~$ ping google.com
PING google.com (173.194.34.230) 56(84) bytes of data.
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=1 ttl=55 time=21.9 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=2 ttl=55 time=20.5 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=3 ttl=55 time=21.0 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=4 ttl=55 time=21.0 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=5 ttl=55 time=21.8 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=6 ttl=55 time=21.3 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=7 ttl=55 time=21.2 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=8 ttl=55 time=20.8 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=9 ttl=55 time=21.2 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=10 ttl=55 time=20.5 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=11 ttl=55 time=20.5 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=12 ttl=55 time=20.9 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=13 ttl=55 time=21.6 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=14 ttl=55 time=21.7 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=15 ttl=55 time=21.8 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=16 ttl=55 time=21.1 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=17 ttl=55 time=22.7 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=18 ttl=55 time=21.9 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=19 ttl=55 time=21.1 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=20 ttl=55 time=20.8 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=21 ttl=55 time=21.1 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=22 ttl=55 time=22.3 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=23 ttl=55 time=21.7 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=24 ttl=55 time=21.1 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=25 ttl=55 time=21.5 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=26 ttl=55 time=20.8 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=27 ttl=55 time=21.8 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=28 ttl=55 time=21.1 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=29 ttl=55 time=21.0 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=30 ttl=55 time=20.6 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=31 ttl=55 time=20.6 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=32 ttl=55 time=22.6 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=33 ttl=55 time=21.4 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=34 ttl=55 time=20.6 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=35 ttl=55 time=21.1 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=36 ttl=55 time=21.7 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=37 ttl=55 time=25.8 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=38 ttl=55 time=21.1 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=39 ttl=55 time=20.3 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=40 ttl=55 time=21.1 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=41 ttl=55 time=21.6 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=42 ttl=55 time=28.0 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=43 ttl=55 time=20.5 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=44 ttl=55 time=20.9 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=45 ttl=55 time=21.0 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=46 ttl=55 time=22.0 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=47 ttl=55 time=21.5 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=48 ttl=55 time=20.9 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=49 ttl=55 time=21.7 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=50 ttl=55 time=20.9 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=51 ttl=55 time=21.0 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=52 ttl=55 time=21.2 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=53 ttl=55 time=21.0 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=54 ttl=55 time=20.7 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=55 ttl=55 time=20.9 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=56 ttl=55 time=21.3 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=57 ttl=55 time=20.6 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=58 ttl=55 time=21.1 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=59 ttl=55 time=20.9 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=60 ttl=55 time=21.7 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=61 ttl=55 time=20.9 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=62 ttl=55 time=20.8 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=63 ttl=55 time=21.5 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=64 ttl=55 time=20.7 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=65 ttl=55 time=20.7 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=66 ttl=55 time=20.4 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=67 ttl=55 time=20.9 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=68 ttl=55 time=20.7 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=69 ttl=55 time=21.2 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=70 ttl=55 time=21.4 ms
64 bytes from mad01s09-in-f6.1e100.net (173.194.34.230): icmp_seq=71 ttl=55 time=20.5 ms

Espero que esto te dé alguna indicación de lo que pueda estar pasando. Muchas gracias y saludos

+1
-1
-1
Imagen de watjilpa
+1
0
-1

Me he comprado un pequeño adaptador usb (un TP Link modelo TL-WN8223N) que hace las veces de inalámbrico, y ha sido conectarlo y empezar a funcionar sin estar anclado al cable. Out of the Box, como dicen por ahí.

Saludos,
Wat

+1
0
-1