Cristian Mitchell,

También suele pasar cosas raras con el sistema de hibernación, ej: Me pasa
aveces que cuando vuelvo de una hibernación la pantalla se divide en 3...

Saludos



2014-02-05 Ricardo Zúñiga <ceaerr...@gmail.com>:

> Lo malo es que bootlogd esta desactivado por defecto y dmesg no es
> especifico.
>
>
> Bueno, Gracias por la ayuda y los comentarios. Estoy conectado a la red
> cableada nuevamente.
>
> Saludos
>
>
> 2014-02-05 Maykel Franco <maykeldeb...@gmail.com>:
>
>
>>
>>
>> 2014-02-05 Ricardo Zúñiga <ceaerr...@gmail.com>:
>>
>> Vamos que no se quemó ni nada por el estilo
>>>
>>> # ifconfig -a
>>> eth0      Link encap:Ethernet  HWaddr b8:70:f4:27:2b:a9
>>>           inet6 addr: fe80::ba70:f4ff:fe27:2ba9/64 Scope:Link
>>>           UP BROADCAST MULTICAST  MTU:1500  Metric:1
>>>           RX packets:1488 errors:0 dropped:0 overruns:0 frame:0
>>>           TX packets:43 errors:0 dropped:0 overruns:0 carrier:0
>>>           collisions:0 txqueuelen:1000
>>>           RX bytes:119938 (117.1 KiB)  TX bytes:9199 (8.9 KiB)
>>>           Interrupt:40 Base address:0x6000
>>>
>>> lo        Link encap:Local Loopback
>>>           inet addr:127.0.0.1  Mask:255.0.0.0
>>>           inet6 addr: ::1/128 Scope:Host
>>>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>>>            RX packets:34 errors:0 dropped:0 overruns:0 frame:0
>>>           TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
>>>           collisions:0 txqueuelen:0
>>>           RX bytes:2348 (2.2 KiB)  TX bytes:2348 (2.2 KiB)
>>>
>>>
>>> wlan0     Link encap:Ethernet  HWaddr ac:81:12:80:13:82
>>>           inet addr:200.0.0.80  Bcast:200.0.0.255  Mask:255.255.255.0
>>>           inet6 addr: fe80::ae81:12ff:fe80:1382/64 Scope:Link
>>>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>>            RX packets:151 errors:0 dropped:0 overruns:0 frame:2017
>>>           TX packets:100 errors:21 dropped:0 overruns:0 carrier:0
>>>           collisions:0 txqueuelen:1000
>>>           RX bytes:14144 (13.8 KiB)  TX bytes:22554 (22.0 KiB)
>>>           Interrupt:17
>>> Camaleón no uso windows, solo debian. Desactive y active la red desde la
>>> BIOS y nada.
>>>
>>> Pero.....
>>>
>>> Elimine "/etc/udev/rules.d/70-persistent-net.rules" y "APAGUE" el
>>> notebook, al volver a encenderlo volvio a aparecer, ahora me dice que no
>>> esta gestionado, pero ya aparecio (Volvio de sus cortas vacaciones).
>>>
>>> Anoche estube trabajando hasta tarde y me qede dormido con el encendido
>>> en la mañana al levantarme solo cerre la tapa y al llegar a la oficina ya
>>> estaba encendido. Quizas sea un tema de "Hibernación" que desactiva las
>>> eth0 o entran en conflicto.
>>>
>>>
>>> 2014-02-05 Debian GMail <javier.debian.bb...@gmail.com>:
>>>
>>> El 05/02/14 10:47, Ricardo Zúñiga escribió:
>>>>
>>>>  Saludos lista, les comento lo que me paso:
>>>>>
>>>>> Vaya sorpresa me eh dado esta mañana, Desaparecio la interfaz de red
>>>>> cableada eth0.
>>>>>
>>>>> # dmesg | grep -i eth
>>>>> [   18.761560] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
>>>>>
>>>>> Quitandole la sentencia -i no arroja resultado, pero con lspci no la
>>>>> veo:
>>>>> # lspci
>>>>> 00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller
>>>>> (rev 02)
>>>>> 00:02.0 VGA compatible controller: Intel Corporation Core Processor
>>>>> Integrated Graphics Controller (rev 02)
>>>>> 00:16.0 Communication controller: Intel Corporation 5 Series/3400
>>>>> Series
>>>>> Chipset HECI Controller (rev 06)
>>>>> 00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset
>>>>> USB2 Enhanced Host Controller (rev 05)
>>>>> 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset
>>>>> High Definition Audio (rev 05)
>>>>> 00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
>>>>> Express Root Port 1 (rev 05)
>>>>> 00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
>>>>> Express Root Port 2 (rev 05)
>>>>> 00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
>>>>> Express Root Port 5 (rev 05)
>>>>> 00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset
>>>>> USB2 Enhanced Host Controller (rev 05)
>>>>> 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5)
>>>>> 00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC
>>>>> Interface Controller (rev 05)
>>>>> 00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset
>>>>> 4 port SATA AHCI Controller (rev 05)
>>>>> 00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus
>>>>> Controller (rev 05)
>>>>> 00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400
>>>>> Series Chipset Thermal Subsystem (rev 05)
>>>>> 05:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n
>>>>> Wireless LAN Controller (rev 01)
>>>>> ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath
>>>>> Architecture Generic Non-core Registers (rev 02)
>>>>> ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath
>>>>> Architecture System Address Decoder (rev 02)
>>>>> ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev
>>>>> 02)
>>>>> ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0
>>>>> (rev 02)
>>>>> ff:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
>>>>> ff:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
>>>>>
>>>>> Agregue la interfaz en /etc/network/interfaces, pero al querer
>>>>> levantarla
>>>>>
>>>>> # /etc/init.d/networking restart
>>>>> [....] Running /etc/init.d/networking restart is deprecated because it
>>>>> may not re-enable some inte[warns ... (warning).
>>>>> [....] Reconfiguring network interfaces...Internet Systems Consortium
>>>>> DHCP Client 4.2.2
>>>>> Copyright 2004-2011 Internet Systems Consortium.
>>>>> All rights reserved.
>>>>> For info, please visit https://www.isc.org/software/dhcp/
>>>>>
>>>>> Cannot find device "eth0"
>>>>> Bind socket to interface: No such device
>>>>> Failed to bring up eth0.
>>>>> done.
>>>>>
>>>>> No sé por donde mas seguir no se me ocurre nada.
>>>>>
>>>>> Atento a cualquier comentario
>>>>>
>>>>> Saludos
>>>>>
>>>>> --
>>>>> Atte.
>>>>> Ricardo G. Zúñiga Bauer
>>>>> Analista programador
>>>>> Sitio web: http://ceaerrepe.com.ar
>>>>> User Linux: #455331
>>>>>
>>>>
>>>>
>>>> Si la placa es "on-board", se te quemó.
>>>> Si es PCI, está floja.
>>>> Sacala, limipiá con contamatic, y volvé a colocarla
>>>>
>>>> JAP
>>>>
>>>>
>>>>
>>>> --
>>>> To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
>>>> with a subject of "unsubscribe". Trouble? Contact
>>>> listmas...@lists.debian.org
>>>> Archive: http://lists.debian.org/52f25ac2.4020...@gmail.com
>>>>
>>>>
>>>
>>>
>>> --
>>> Atte.
>>> Ricardo G. Zúñiga Bauer
>>> Analista programador
>>> Sitio web: http://ceaerrepe.com.ar
>>> User Linux: #455331
>>>
>>
>>
>> Si te miras los logs lo sabrás....
>>
>
>
>
> --
> Atte.
> Ricardo G. Zúñiga Bauer
> Analista programador
> Sitio web: http://ceaerrepe.com.ar
> User Linux: #455331
>



-- 
Atte.
Ricardo G. Zúñiga Bauer
Analista programador
Sitio web: http://ceaerrepe.com.ar
User Linux: #455331

Responder a