Howto reactivate laptop's NIC (it worked fine and still works under Parabola)
- Anmelden oder Registrieren um Kommentare zu schreiben
Hi, I've spent a couple of days fighting with this, so, I hope someone could lend me a hand...
Abstract:
Tried to use the laptop's wireless card installing its firmware from a Debian's package; it doesn't work at all; purged that package and removed the modules, but after reboot the NIC stoped working (but it works if I boot a LiveUSB of Parabola, just that not as 'eth0' but as 'enp6s0').
This is the actual situation:
root@user:/home/user# lspci
03:00.0 Network controller: Intel Corporation Centrino Wireless-N 1030 [Rainbow Peak] (rev 34)
04:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04)
06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
root@user:/home/user# lshw
user
descripción: Portátil
producto: Dell System XPS L502X (System SKUNumber)
fabricante: Dell Inc.
versión: 0.1
serie: FRSTQQ1
anchura: 64 bits
capacidades: smbios-2.6 dmi-2.6 vsyscall32
configuración: administrator_password=unknown boot=normal chassis=portable family=HuronRiver System frontpanel_password=unknown keyboard_password=unknown power-on_password=unknown sku=System SKUNumber uuid=44454C4C-5200-1053-8054-C6C04F515131
*-network NO RECLAMADO
descripción: Network controller
producto: Centrino Wireless-N 1030 [Rainbow Peak]
fabricante: Intel Corporation
id físico: 0
información del bus: pci@0000:03:00.0
versión: 34
anchura: 64 bits
reloj: 33MHz
capacidades: pm msi pciexpress cap_list
configuración: latency=0
recursos: memoria:f1b00000-f1b01fff
*-network DESACTIVADO
descripción: Ethernet interface
producto: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
fabricante: Realtek Semiconductor Co., Ltd.
id físico: 0
información del bus: pci@0000:06:00.0
nombre lógico: eth0
versión: 06
serie: 14:fe:b5:b8:11:13
tamaño: 1Gbit/s
capacidad: 1Gbit/s
anchura: 64 bits
reloj: 33MHz
capacidades: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
configuración: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full ip=10.0.0.3 latency=0 link=no multicast=yes port=MII speed=1Gbit/s
recursos: irq:50 ioport:2000(size=256) memoria:f1804000-f1804fff memoria:f1800000-f1803fff
root@user:/home/user# ifconfig -a
eth0 Link encap:Ethernet direcciónHW 14:fe:b5:b8:11:13
Direc. inet:10.0.0.3 Difus.:10.0.0.255 Másc:255.255.255.0
DIFUSIÓN MULTICAST MTU:1500 Métrica:1
Paquetes RX:0 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:0 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:1000
Bytes RX:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Bucle local
Direc. inet:127.0.0.1 Másc:255.0.0.0
Dirección inet6: ::1/128 Alcance:Anfitrión
ACTIVO BUCLE FUNCIONANDO MTU:65536 Métrica:1
Paquetes RX:4882 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:4882 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:0
Bytes RX:398520 (398.5 KB) TX bytes:398520 (398.5 KB)
virbr0 Link encap:Ethernet direcciónHW e6:81:37:a7:6f:32
Direc. inet:192.168.122.1 Difus.:192.168.122.255 Másc:255.255.255.0
ACTIVO DIFUSIÓN MULTICAST MTU:1500 Métrica:1
Paquetes RX:0 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:0 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:0
Bytes RX:0 (0.0 B) TX bytes:0 (0.0 B)
root@user:/home/user# iwconfig
eth0 no wireless extensions.
lo no wireless extensions.
virbr0 no wireless extensions.
root@user:/home/user# nmap -sP 10.0.0.*
Starting Nmap 6.40 ( http://nmap.org ) at 2016-12-03 08:55 ART
setup_target: failed to determine route to 10.0.0.0
setup_target: failed to determine route to 10.0.0.1
[...]
setup_target: failed to determine route to 10.0.0.254
setup_target: failed to determine route to 10.0.0.255
mass_dns: warning: Unable to determine any DNS servers. Reverse DNS is disabled. Try using --system-dns or specify valid servers with --dns-servers
Nmap scan report for 10.0.0.3
Host is up.
Nmap done: 1 IP address (1 host up) scanned in 0.01 seconds
root@user:/home/user# nm-online
Conectando............... 1s
root@user:/home/user# nm-online -x
root@user:/home/user# nm-tool
NetworkManager Tool
State: disconnected
- Device: eth0 -----------------------------------------------------------------
Type: Wired
Driver: r8169
State: unavailable
Default: no
HW Address: 14:FE:B5:B8:11:13
Capabilities:
Carrier Detect: yes
Wired Properties
Carrier: off
The NIC used to work just fine. But now I can't make it connect.
Strangely, if I boot with Parabola's LiveCD, I get:
root@parabolaiso ~ # lspci
03:00.0 Network controller: Intel Corporation Centrino Wireless-N 1030 [Rainbow Peak] (rev 34)
04:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04)
06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
root@parabolaiso ~ # lshw
parabolaiso
description: Portable Computer
product: Dell System XPS L502X (System SKUNumber)
vendor: Dell Inc.
version: 0.1
serial: FRSTQQ1
width: 4294967295 bits
capabilities: smbios-2.6 dmi-2.6 smp vsyscall32
configuration: administrator_password=unknown boot=normal chassis=portable family=HuronRiver System frontpanel_password=unknown keyboard_password=unknown power-on_password=unknown sku=System SKUNumber uuid=44454C4C-5200-1053-8054-C6C04F515131
*-network UNCLAIMED
description: Network controller
product: Centrino Wireless-N 1030 [Rainbow Peak]
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:03:00.0
version: 34
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress cap_list
configuration: latency=0
resources: memory:f1b00000-f1b01fff
*-network
description: Ethernet interface
product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:06:00.0
logical name: enp6s0
version: 06
serial: 14:fe:b5:b8:11:13
size: 100Mbit/s
capacity: 1Gbit/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full ip=10.0.0.3 latency=0 link=yes multicast=yes port=MII speed=100Mbit/s
resources: irq:25 ioport:2000(size=256) memory:f1804000-f1804fff memory:f1800000-f1803fff
root@parabolaiso ~ # ifconfig -a
enp6s0: flags=4163 mtu 1500
inet 10.0.0.3 netmask 255.255.255.0 broadcast 10.0.0.255
inet6 fe80::ae8a:4c4c:9fc5:97d1 prefixlen 64 scopeid 0x20
ether 14:fe:b5:b8:11:13 txqueuelen 1000 (Ethernet)
RX packets 221424 bytes 240347192 (229.2 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 174187 bytes 23830144 (22.7 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73 mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1 (Local Loopback)
RX packets 64 bytes 3896 (3.8 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 64 bytes 3896 (3.8 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
root@parabolaiso ~ # iwconfig
lo no wireless extensions.
enp6s0 no wireless extensions.
root@parabolaiso ~ # lsmod | grep iwl
iwlwifi 180224 0
cfg80211 495616 1 iwlwifi
root@parabolaiso ~ # lsmod | grep r81
r8169 77824 0
mii 16384 1 r8169
And the NIC works just fine (I'm using it right now) with the same modules, so: How can I make the NIC work again under Trisquel?
Thanks a lot.
The wireless card won't work at all. Intel WiFi stuff needs proprietary junk. Linux-libre has that stuff deleted. A bug in Linux-libre prevents the firmware from ever being loaded, even if it's there. As to the built-in ethernet if it works in Parabola but not Trisquel perhaps the kernel in Trisquel is too old? Parabola makes a policy of living on the bleeding edge. So try a newer kernel in Trisquel and see if that solves it? Information and instructions at https://jxself.org/linux-libre/
Thanks a lot, jxself, I will check that now.
Effectively, under Trisquel:
# uname -a
Linux trisquel 3.13.0-101-lowlatency #148+7.0trisquel2 SMP PREEMPT Thu Nov 10 11:45:49 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
And with Parabola (LiveCD):
# uname -a
Linux parabolaiso 4.8.6-gnu-1 #1 SMP PREEMPT Tue Nov 1 10:19:01 UYT 2016 x86_64 GNU/Linux
So, it maybe could be worked out by a change in the kernel. I'll test it.
But this would be just a workaround: I know (as a couple-of-years-fact) that the ethernet card worked perfectly, and it is being seen by the system. So, I really would like to solve the actual problem.
Any clue on that? Any system/hardware info that I could post to help on clear this issue?
Thanks *a lot*.
No, it's not a workaround but the fundamental passage of time at question here. We can't possibly build drivers today for the gadgets of tomorrow.
I've been checking https://jxself.org/linux-libre/, and the instructions there are very clear. But I don't have Internet connection on Trisquel right now, so: Which would be the best way to install, for instance, linux-libre-lts kernel, on a Trisquel without connection?
Thanks a lot.
Download https://linux-libre.fsfla.org/pub/linux-libre/freesh/pool/main/l/linux-libre-4.1/linux-libre-4.1_4.1.36_amd64.deb and bring it to the offline system (e.g., through a pendrive). There, install it with 'sudo dpkg -i linux-libre-4.1_4.1.36_amd64.deb' (assuming the working directory has the file, otherwise specify its path).
Actually, that one is a meta pacakge not the actual kernel.
The exact one to download depends on the CPU architecture. Normally the package manager will figure that out automatically but since they're doing it manually:
For 32-bit without support for PAE:
https://linux-libre.fsfla.org/pub/linux-libre/freesh/pool/main/l/linux-upstream/linux-image-4.1.36-gnu.nonpae_4.1.36-gnu-1.0_i386.deb
Once the kernel is installed and the computer is restarted it's important to then go and set up the repository as indicated in the directions on the website and install one of the meta packages listed. This is important. ***If you don't do this you won't get updates. Ever.***
Thanks a lot, jxself.
The kernel installation went without issues (I'll put the terminal output next), but after reboot it didn't solved the problem. It has to be something else.
Here you have all the process and actual situation. Could you please have a look and give any advice/idea?
[Before kernel's installation]
$ uname -a
Linux user 3.13.0-101-lowlatency #148+7.0trisquel2 SMP PREEMPT Thu Nov 10 11:45:49 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
root@user:/home/user# ifconfig -a
eth0 Link encap:Ethernet direcciónHW 14:fe:b5:b8:11:13
ACTIVO DIFUSIÓN MULTICAST MTU:1500 Métrica:1
Paquetes RX:0 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:0 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:1000
Bytes RX:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Bucle local
Direc. inet:127.0.0.1 Másc:255.0.0.0
Dirección inet6: ::1/128 Alcance:Anfitrión
ACTIVO BUCLE FUNCIONANDO MTU:65536 Métrica:1
Paquetes RX:304 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:304 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:0
Bytes RX:24224 (24.2 KB) TX bytes:24224 (24.2 KB)
virbr0 Link encap:Ethernet direcciónHW c2:38:52:c7:44:a9
Direc. inet:192.168.122.1 Difus.:192.168.122.255 Másc:255.255.255.0
ACTIVO DIFUSIÓN MULTICAST MTU:1500 Métrica:1
Paquetes RX:0 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:0 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:0
Bytes RX:0 (0.0 B) TX bytes:0 (0.0 B)
root@user:/home/user# ping 10.0.0.2
connect: Network is unreachable
root@user:/home/user# ifconfig eth0 up && ifconfig eth0 10.0.0.3 netmask 255.255.255.0 && route add default gateway 10.0.0.2
root@user:/home/user# ifconfig -a
eth0 Link encap:Ethernet direcciónHW 14:fe:b5:b8:11:13
Direc. inet:10.0.0.3 Difus.:10.0.0.255 Másc:255.255.255.0
ACTIVO DIFUSIÓN MULTICAST MTU:1500 Métrica:1
Paquetes RX:0 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:0 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:1000
Bytes RX:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Bucle local
Direc. inet:127.0.0.1 Másc:255.0.0.0
Dirección inet6: ::1/128 Alcance:Anfitrión
ACTIVO BUCLE FUNCIONANDO MTU:65536 Métrica:1
Paquetes RX:304 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:304 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:0
Bytes RX:24224 (24.2 KB) TX bytes:24224 (24.2 KB)
virbr0 Link encap:Ethernet direcciónHW c2:38:52:c7:44:a9
Direc. inet:192.168.122.1 Difus.:192.168.122.255 Másc:255.255.255.0
ACTIVO DIFUSIÓN MULTICAST MTU:1500 Métrica:1
Paquetes RX:0 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:0 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:0
Bytes RX:0 (0.0 B) TX bytes:0 (0.0 B)
root@user:/home/user# ping 10.0.0.2
PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.
From 10.0.0.3 icmp_seq=1 Destination Host Unreachable
From 10.0.0.3 icmp_seq=2 Destination Host Unreachable
From 10.0.0.3 icmp_seq=3 Destination Host Unreachable
From 10.0.0.3 icmp_seq=4 Destination Host Unreachable
From 10.0.0.3 icmp_seq=5 Destination Host Unreachable
From 10.0.0.3 icmp_seq=6 Destination Host Unreachable
From 10.0.0.3 icmp_seq=7 Destination Host Unreachable
From 10.0.0.3 icmp_seq=8 Destination Host Unreachable
From 10.0.0.3 icmp_seq=9 Destination Host Unreachable
From 10.0.0.3 icmp_seq=10 Destination Host Unreachable
From 10.0.0.3 icmp_seq=11 Destination Host Unreachable
From 10.0.0.3 icmp_seq=12 Destination Host Unreachable
^C
--- 10.0.0.2 ping statistics ---
12 packets transmitted, 0 received, +12 errors, 100% packet loss, time 11001ms
pipe 4
root@user:/home/user# ping 10.0.0.3
PING 10.0.0.3 (10.0.0.3) 56(84) bytes of data.
64 bytes from 10.0.0.3: icmp_seq=1 ttl=64 time=0.108 ms
64 bytes from 10.0.0.3: icmp_seq=2 ttl=64 time=0.097 ms
64 bytes from 10.0.0.3: icmp_seq=3 ttl=64 time=0.100 ms
64 bytes from 10.0.0.3: icmp_seq=4 ttl=64 time=0.099 ms
64 bytes from 10.0.0.3: icmp_seq=5 ttl=64 time=0.096 ms
^C
--- 10.0.0.3 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 0.096/0.100/0.108/0.004 ms
root@user:/home/user# ifdown eth0
ifdown: interface eth0 not configured
root@user:/home/user# ifup eth0
Ignoring unknown interface eth0=eth0.
root@user:/home/user# ifconfig -a
eth0 Link encap:Ethernet direcciónHW 14:fe:b5:b8:11:13
Direc. inet:10.0.0.3 Difus.:10.0.0.255 Másc:255.255.255.0
ACTIVO DIFUSIÓN MULTICAST MTU:1500 Métrica:1
Paquetes RX:0 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:0 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:1000
Bytes RX:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Bucle local
Direc. inet:127.0.0.1 Másc:255.0.0.0
Dirección inet6: ::1/128 Alcance:Anfitrión
ACTIVO BUCLE FUNCIONANDO MTU:65536 Métrica:1
Paquetes RX:334 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:334 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:0
Bytes RX:27192 (27.1 KB) TX bytes:27192 (27.1 KB)
virbr0 Link encap:Ethernet direcciónHW c2:38:52:c7:44:a9
Direc. inet:192.168.122.1 Difus.:192.168.122.255 Másc:255.255.255.0
ACTIVO DIFUSIÓN MULTICAST MTU:1500 Métrica:1
Paquetes RX:0 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:0 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:0
Bytes RX:0 (0.0 B) TX bytes:0 (0.0 B)
root@user:/home/user# nm-online
Conectando............... 1s
root@user:/home/user# nm-tool
NetworkManager Tool
State: disconnected
- Device: eth0 -----------------------------------------------------------------
Type: Wired
Driver: r8169
State: unavailable
Default: no
HW Address: 14:FE:B5:B8:11:13
Capabilities:
Carrier Detect: yes
Wired Properties
Carrier: off
$ sudo dpkg -i linux-image-4.1.36-gnu_4.1.36-gnu-1.0_amd64.deb
Seleccionando el paquete linux-image-4.1.36-gnu previamente no seleccionado.
(Leyendo la base de datos ... 205188 ficheros o directorios instalados actualmente.)
Preparando para desempaquetar linux-image-4.1.36-gnu_4.1.36-gnu-1.0_amd64.deb ...
Desempaquetando linux-image-4.1.36-gnu (4.1.36-gnu-1.0) ...
Configurando linux-image-4.1.36-gnu (4.1.36-gnu-1.0) ...
update-initramfs: Generating /boot/initrd.img-4.1.36-gnu
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
P: Checking for EXTLINUX directory... found.
P: Writing config for /boot/vmlinuz-4.1.36-gnu...
P: Writing config for /boot/vmlinuz-3.13.0-101-lowlatency...
P: Writing config for /boot/vmlinuz-3.13.0-100-lowlatency...
P: Updating /boot/extlinux/linux.cfg...
P: Installing debian theme... done.
Generando archivo de configuración grub...
Se encontró una imagen linux: /boot/vmlinuz-4.1.36-gnu
Se encontró una imagen initrd: /boot/initrd.img-4.1.36-gnu
Se encontró una imagen linux: /boot/vmlinuz-3.13.0-101-lowlatency
Se encontró una imagen initrd: /boot/initrd.img-3.13.0-101-lowlatency
Se encontró una imagen linux: /boot/vmlinuz-3.13.0-100-lowlatency
Se encontró una imagen initrd: /boot/initrd.img-3.13.0-100-lowlatency
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
hecho
$ sudo apt-get -f install
Leyendo lista de paquetes... Hecho
Creando árbol de dependencias
Leyendo la información de estado... Hecho
Los paquetes indicados a continuación se instalaron de forma automática y ya no son necesarios.
linux-headers-3.13.0-100 linux-headers-3.13.0-100-lowlatency
linux-image-3.13.0-100-lowlatency
Use 'apt-get autoremove' to remove them.
0 actualizados, 0 se instalarán, 0 para eliminar y 0 no actualizados.
[With the new kernel]
root@user:/home/user# uname -a
Linux user 4.1.36-gnu #1 SMP Wed Nov 30 19:12:57 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
root@user:/home/user# ifconfig -a
eth0 Link encap:Ethernet direcciónHW 14:fe:b5:b8:11:13
ACTIVO DIFUSIÓN MULTICAST MTU:1500 Métrica:1
Paquetes RX:0 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:0 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:1000
Bytes RX:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Bucle local
Direc. inet:127.0.0.1 Másc:255.0.0.0
Dirección inet6: ::1/128 Alcance:Anfitrión
ACTIVO BUCLE FUNCIONANDO MTU:65536 Métrica:1
Paquetes RX:304 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:304 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:0
Bytes RX:24224 (24.2 KB) TX bytes:24224 (24.2 KB)
virbr0 Link encap:Ethernet direcciónHW 46:30:2f:b9:f1:07
Direc. inet:192.168.122.1 Difus.:192.168.122.255 Másc:255.255.255.0
ACTIVO DIFUSIÓN MULTICAST MTU:1500 Métrica:1
Paquetes RX:0 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:0 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:0
Bytes RX:0 (0.0 B) TX bytes:0 (0.0 B)
root@user:/home/user# ifup eth0
Ignoring unknown interface eth0=eth0.
root@user:/home/user# ifdown eth0
ifdown: interface eth0 not configured
root@user:/home/user# ping 10.0.0.2
connect: Network is unreachable
root@user:/home/user# ifconfig eth0 up && ifconfig eth0 10.0.0.3 netmask 255.255.255.0 && route add default gateway 10.0.0.2
root@user:/home/user# ifconfig -a
eth0 Link encap:Ethernet direcciónHW 14:fe:b5:b8:11:13
Direc. inet:10.0.0.3 Difus.:10.0.0.255 Másc:255.255.255.0
ACTIVO DIFUSIÓN MULTICAST MTU:1500 Métrica:1
Paquetes RX:0 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:0 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:1000
Bytes RX:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Bucle local
Direc. inet:127.0.0.1 Másc:255.0.0.0
Dirección inet6: ::1/128 Alcance:Anfitrión
ACTIVO BUCLE FUNCIONANDO MTU:65536 Métrica:1
Paquetes RX:304 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:304 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:0
Bytes RX:24224 (24.2 KB) TX bytes:24224 (24.2 KB)
virbr0 Link encap:Ethernet direcciónHW 46:30:2f:b9:f1:07
Direc. inet:192.168.122.1 Difus.:192.168.122.255 Másc:255.255.255.0
ACTIVO DIFUSIÓN MULTICAST MTU:1500 Métrica:1
Paquetes RX:0 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:0 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:0
Bytes RX:0 (0.0 B) TX bytes:0 (0.0 B)
root@user:/home/user# ping 10.0.0.2
PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.
From 10.0.0.3 icmp_seq=1 Destination Host Unreachable
From 10.0.0.3 icmp_seq=2 Destination Host Unreachable
From 10.0.0.3 icmp_seq=3 Destination Host Unreachable
^C
--- 10.0.0.2 ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2999ms
pipe 3
root@user:/home/user# ping 10.0.0.3
PING 10.0.0.3 (10.0.0.3) 56(84) bytes of data.
64 bytes from 10.0.0.3: icmp_seq=1 ttl=64 time=0.094 ms
64 bytes from 10.0.0.3: icmp_seq=2 ttl=64 time=0.092 ms
64 bytes from 10.0.0.3: icmp_seq=3 ttl=64 time=0.086 ms
^C
--- 10.0.0.3 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.086/0.090/0.094/0.011 ms
root@user:/home/user# nm-tool
NetworkManager Tool
State: disconnected
- Device: eth0 -----------------------------------------------------------------
Type: Wired
Driver: r8169
State: unavailable
Default: no
HW Address: 14:FE:B5:B8:11:13
Capabilities:
Carrier Detect: yes
Wired Properties
Carrier: off
root@user:/home/user# nmap -sP 10.0.0.*
Starting Nmap 6.40 ( http://nmap.org ) at 2016-12-05 12:44 ART
mass_dns: warning: Unable to determine any DNS servers. Reverse DNS is disabled. Try using --system-dns or specify valid servers with --dns-servers
Nmap scan report for 10.0.0.3
Host is up.
Nmap done: 256 IP addresses (1 host up) scanned in 10.50 seconds
root@tanuki:/home/tanuki# nmap -sP 10.0.0.* --system-dns
Starting Nmap 6.40 ( http://nmap.org ) at 2016-12-05 12:45 ART
Nmap scan report for 10.0.0.3
Host is up.
Nmap done: 256 IP addresses (1 host up) scanned in 10.46 seconds
"It has to be something else."
Not necessarily. Parabola is using version 4.8, but you installed an older kernel (4.1.) You're not even testing the same versions so the results of your experiment are invalid in my opinion. Try Linux-libre 4.8 please.
Well, in a big way, you were absolutelly right. Effectively, with the change of kernel 4.1 → 4.8, or to be more precise,
# uname -a
Linux user 4.8.12-gnu #1 SMP Fri Dec 2 16:56:47 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
, the network card started to work again. (I'm unable to put in words the level of happiness that moment give to me, and there's an equal level of thankfulness from me to you. :) ) Thanks for the patience and persistance.
Now, new issues have arisen:
1) The network manager is a lot slower than before, like if it were doing a lot of stuff any time it tries (and finally achieve) to connect. But that's not important, I'm just mentioning it as a symptom for the sake of description.
2) When I connect to my other machine via sshfs, the connection goes without issues. But the speed of transmission is absolutely ludicrous. A 1GB file takes like an hour to get copied from one disk (in this machine) to another (in the other pc). This is specially relevant because I need to make a backup of the info in this laptop, and I don't have a removable disk to move hundreds of GBs. So, I really need the LAN to work normally. What can I do to help you people have an idea for diagnostic this issue?
3) The resources monitor in the bottom panel shows correctly the CPU work, but fails completelly in show the RAM in use. Any clue on that?
4) Is there a way to be sure to receive the updates for this version of the libre-kernel?
I'll paste down the current situation. Thanks *a lot* (really)! Let me know about any info I can give to better understand this issues, specially number 2, that's the really essential.
root@user:~# rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
root@user:~# ifconfig -a
eth0 Link encap:Ethernet direcciónHW 14:fe:b5:b8:11:13
Direc. inet:10.0.0.3 Difus.:10.0.0.255 Másc:255.255.255.0
Dirección inet6: fe80::16fe:b5ff:feb8:1113/64 Alcance:Enlace
ACTIVO DIFUSIÓN FUNCIONANDO MULTICAST MTU:1500 Métrica:1
Paquetes RX:2464135 errores:0 perdidos:744 overruns:0 frame:0
Paquetes TX:1462613 errores:44 perdidos:735 overruns:0 carrier:0
colisiones:0 long.colaTX:1000
Bytes RX:2608261921 (2.6 GB) TX bytes:1059907026 (1.0 GB)
lo Link encap:Bucle local
Direc. inet:127.0.0.1 Másc:255.0.0.0
Dirección inet6: ::1/128 Alcance:Anfitrión
ACTIVO BUCLE FUNCIONANDO MTU:65536 Métrica:1
Paquetes RX:30188 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:30188 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:1
Bytes RX:2856779 (2.8 MB) TX bytes:2856779 (2.8 MB)
virbr0 Link encap:Ethernet direcciónHW 6a:47:60:50:4b:3e
Direc. inet:192.168.122.1 Difus.:192.168.122.255 Másc:255.255.255.0
ACTIVO DIFUSIÓN MULTICAST MTU:1500 Métrica:1
Paquetes RX:0 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:0 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:1000
Bytes RX:0 (0.0 B) TX bytes:0 (0.0 B)
root@user:~# nm-tool
NetworkManager Tool
State: connected (global)
- Device: eth0 [Conexión cableada 1] -----------------------------------------
Type: Wired
Driver: r8169
State: connected
Default: yes
HW Address: 14:FE:B5:B8:11:13
Capabilities:
Carrier Detect: yes
Speed: 100 Mb/s
Wired Properties
Carrier: on
IPv4 Settings:
Address: 10.0.0.3
Prefix: 24 (255.255.255.0)
Gateway: 10.0.0.2
DNS: 10.0.0.2
"Is there a way to be sure to receive the updates for this version of the libre-kernel?"
I assume that you had to download the package manually and install it. To be sure you get updates (now that your ethernet somewhat works, even if slowly) you should now go back to https://jxself.org/linux-libre/ and set up the repository properly, following all the directions there... including installing one of those packages listed in the chart at the end. Because it's those meta packages at the end that important. But your computer also needs to have the repo properly set up, and one of those meta packages installed from it. So do everything shown there from start to finish, as if you're just starting out.
As an example: Your message shows you were using 4.8.12. well, 4.8.13 is now out. Once you've done all of those things, getting to 4.8.13 should be as simple as:
sudo apt update
sudo apt full-upgrade
(And then rebooting once everything is done.)
All done. The instructions are perfectly clear. Thanks a lot. I'm running now with the linux-libre-4.8 version and full-upgrade went without issues.
The main problem persist: My LAN speed for copying files is, by sftp in terminal, 1.1MB/s:
sftp> put /local/machine/movie.avi /remote/machine/dir
Uploading /local/machine/movie.avi to /remote/machine/dir/movie.avi
/local/machine/movie.avi 47% 672MB 1.1MB/s 11:22 ETA
It takes 20 minutes to copy 1GB.
This behaviour is consistent in pcmanfm mounting the remote machine via sshfs or using the pcmanfm mounting way (writing ssh://remote@machine in the address bar).
Any clue?
I'm worried because I have no idea what was the real problem. The 3.x libre-kernel that cames with Trisquel Mini Belenos by default worked flawlessly for a couple of years. And the fact that the network card stopped working even booting with other distros live-sessions makes me think of a problem that is not just in the OS.
PS: RAM indicator in Resources Monitor applet (LXDE bottom panel) keeps showing nothing ('0.0MB (0.00%)')
Thanks a lot.
I add this info in case it has some useness to find the root of the problem:
$ uname -a && dpkg -l ssh sshfs pcmanfm ftp
Linux user 4.8.15-gnu #1 SMP Thu Dec 15 18:46:29 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
||/ Nombre Versión Arquitectura Descripción
+++-==============-============-============-=================================
ii ftp 0.17-28 amd64 classical file transfer client
ii pcmanfm 1.2.0-1 amd64 extremely fast and lightweight fi
ii ssh 1:6.6p1-2ubu all secure shell client and server (m
ii sshfs 2.5-1ubuntu1 amd64 filesystem client based on SSH Fi
Anything else I could do?
Thanks a lot!
BTW, I've just tested that this problem is not Trisquel exclusive: If I boot with Parabola (live) the slow-LAN-speed issue repeats identically.
Thanks a lot for any help!
This is an old machine, that I even bought used, because it's no longer sold as new (and in any case, I wouldn't have that kind of money anyway).
But the thing is that for the last almost two years, the built-in ethernet has been working flawlessly, so, there must be a way to recover that normal behaviour, fixing whatever that has been changed (that I can't clear up by myself, clearly...).
Sorry for my English, it's not my native language.
Thanks a lot.
I am a member!
Maybe you can use a WiFi USB adapter compatible with fully free GNU distros such as Trisquel.
For the wireless connection, yes, that's (apparently) the only solution, specially because the libre-kernel refuse to load privative drivers/firmware/stuff.
But the main problem in my case was that the network card (by cable) stopped working.
Now it has started to work again, after change the kernel to 4.8, but appart from some other issues, I still have no idea why it stopped to work in the first place.
Thanks a lot.
Hi,
I strongly suspect some rfkill related issue.
rfkill is a Linux framework that let programs activate/deactivate the radio(wifi, bluetooth, etc) antenna.
This is useful when, for instance, you are on an airplane and required not to "turn off wifi/bluetooth".
I already had similar issues on the Lenovo Thinkpads X60 with the default Intel WiFi card.
I don't remember under which distribution though (Parabola or Trisquel).
The issue was that, if the Intel wifi driver was loaded, the module would load, but the card would not initialize due to the missing firmware.
Then adding an extra wireless card didn't work either since network-manager would somehow think that the wifi is disabled trough rfkill, and disable *all* wifi cards.
In my case blacklisting the intel wifi driver worked, but on your laptop it seem to be required instead.
What makes me think it's rfkill are the following elements:
* " *-network DESACTIVADO"
* "purged that package and removed the modules, but after reboot the NIC stoped working"
* Trisquel uses network-manager while it isn't installed by default on parabola
* I had a similar issue.
Note that there is an rfkill command.
If you don't have it, you still have several interesting files in /sys/class/rfkill/*/ :
- type: wlan is for wifi
- soft: It will be set to 1 if you disable network through network-manager, and set to 0 otherwise (not blocked)
- hard: That correspond a hardware button or key combination on laptops, if you flip the switch to power off wifi, it will be 1, else it's 0 (not blocked)
You might have several directories in /sys/class/rfkill/, to find the correct one, look at the "type" filename that I mentioned before.
Also it might be interesting to open a bug on that, especially because, if I understood your issue correctly:
- Blacklisting the intel wifi module on thinkpad would make thinkpad work
- Blacklisting the intel wifi module on your laptop would break wifi
Denis.
The idea is also to document it enough, in order to decide what to do for trisquel8 with that issue. I should document the issue on the thinkpad if I can find the time.
In Trisquel the wireless card (Intel Centrino Wireles-N 1030) doesn't work and apparently it will not work, because of the proprietary drivers/firmware needed and the behaviour of the linux-libre kernel about that, AFAIguess.
But the built-in ethernet card was working perfectly. The problem started when I (full of ignorance) tried to install the proprietary drivers with a Debian package. The WiFi didn't worked. But after reboot, the ethernet card also refuse to connect to the router.
For some reason, in Parabola, where the NIC is called enp6s0 instead of eth0, it works.
So, the problem persist even booting different distros (via LiveUSB). Therefore, I assume it's not a problem just in the OS, but something else (don't know what), because when booting, for instance, a Debian LiveUSB, the NIC doesn't work either (again, under the name eth0), but with Arch derivatives (as enp6s0) the NIC works fine.
Any other hardware/software info that I could post that could give a clue about the source of the problem?
Thanks a lot.
The naming scheme doesn't matter. Newer versions of systemd/udev use a newer naming scheme but that's only a side thing.
https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
Trisquel will eventually get this but it's not in version 7.
Absolutely right. The name is irrelevant. Thanks!
The fact that the problem persist in other distros is consistent with my hypothesis.
Could you paste the output of the following commands:
- rfkill list
- dmesg
Note that the dmesg command will print the whole kernel log, and may print some serial numbers(like your laptop serial number, the HDD uuid, MAC addresses and so on).
Denis.
Also could you try that command:
"sudo ifconfig up"
Replace "" by the interface name for your ethernet card, example: "sudo ifconfig eth0 up".
Denis.
Hi, Denis, check this out, maybe you find some clue on int?
Thanks a lot!
root@user:/home/user# uname -a
Linux user 4.1.36-gnu #1 SMP Wed Nov 30 19:12:57 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
root@user:/home/user# ifconfig -a
eth0 Link encap:Ethernet direcciónHW 14:fe:b5:b8:11:13
ACTIVO DIFUSIÓN MULTICAST MTU:1500 Métrica:1
Paquetes RX:0 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:0 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:1000
Bytes RX:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Bucle local
Direc. inet:127.0.0.1 Másc:255.0.0.0
Dirección inet6: ::1/128 Alcance:Anfitrión
ACTIVO BUCLE FUNCIONANDO MTU:65536 Métrica:1
Paquetes RX:304 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:304 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:0
Bytes RX:24224 (24.2 KB) TX bytes:24224 (24.2 KB)
virbr0 Link encap:Ethernet direcciónHW 46:30:2f:b9:f1:07
Direc. inet:192.168.122.1 Difus.:192.168.122.255 Másc:255.255.255.0
ACTIVO DIFUSIÓN MULTICAST MTU:1500 Métrica:1
Paquetes RX:0 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:0 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:0
Bytes RX:0 (0.0 B) TX bytes:0 (0.0 B)
root@user:/home/user# ifup eth0
Ignoring unknown interface eth0=eth0.
root@user:/home/user# ifdown eth0
ifdown: interface eth0 not configured
root@user:/home/user# ping 10.0.0.2
connect: Network is unreachable
root@user:/home/user# ifconfig eth0 up && ifconfig eth0 10.0.0.3 netmask 255.255.255.0 && route add default gateway 10.0.0.2
root@user:/home/user# ifconfig -a
eth0 Link encap:Ethernet direcciónHW 14:fe:b5:b8:11:13
Direc. inet:10.0.0.3 Difus.:10.0.0.255 Másc:255.255.255.0
ACTIVO DIFUSIÓN MULTICAST MTU:1500 Métrica:1
Paquetes RX:0 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:0 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:1000
Bytes RX:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Bucle local
Direc. inet:127.0.0.1 Másc:255.0.0.0
Dirección inet6: ::1/128 Alcance:Anfitrión
ACTIVO BUCLE FUNCIONANDO MTU:65536 Métrica:1
Paquetes RX:304 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:304 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:0
Bytes RX:24224 (24.2 KB) TX bytes:24224 (24.2 KB)
virbr0 Link encap:Ethernet direcciónHW 46:30:2f:b9:f1:07
Direc. inet:192.168.122.1 Difus.:192.168.122.255 Másc:255.255.255.0
ACTIVO DIFUSIÓN MULTICAST MTU:1500 Métrica:1
Paquetes RX:0 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:0 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:0
Bytes RX:0 (0.0 B) TX bytes:0 (0.0 B)
root@user:/home/user# ping 10.0.0.2
PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.
From 10.0.0.3 icmp_seq=1 Destination Host Unreachable
From 10.0.0.3 icmp_seq=2 Destination Host Unreachable
From 10.0.0.3 icmp_seq=3 Destination Host Unreachable
^C
--- 10.0.0.2 ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2999ms
pipe 3
root@user:/home/user# ping 10.0.0.3
PING 10.0.0.3 (10.0.0.3) 56(84) bytes of data.
64 bytes from 10.0.0.3: icmp_seq=1 ttl=64 time=0.094 ms
64 bytes from 10.0.0.3: icmp_seq=2 ttl=64 time=0.092 ms
64 bytes from 10.0.0.3: icmp_seq=3 ttl=64 time=0.086 ms
^C
--- 10.0.0.3 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.086/0.090/0.094/0.011 ms
root@user:/home/user# nm-tool
NetworkManager Tool
State: disconnected
- Device: eth0 -----------------------------------------------------------------
Type: Wired
Driver: r8169
State: unavailable
Default: no
HW Address: 14:FE:B5:B8:11:13
Capabilities:
Carrier Detect: yes
Wired Properties
Carrier: off
root@user:/home/user# nmap -sP 10.0.0.*
Starting Nmap 6.40 ( http://nmap.org ) at 2016-12-05 12:44 ART
mass_dns: warning: Unable to determine any DNS servers. Reverse DNS is disabled. Try using --system-dns or specify valid servers with --dns-servers
Nmap scan report for 10.0.0.3
Host is up.
Nmap done: 256 IP addresses (1 host up) scanned in 10.50 seconds
root@tanuki:/home/tanuki# nmap -sP 10.0.0.* --system-dns
Starting Nmap 6.40 ( http://nmap.org ) at 2016-12-05 12:45 ART
Nmap scan report for 10.0.0.3
Host is up.
Nmap done: 256 IP addresses (1 host up) scanned in 10.46 seconds
> root@user:/home/user# ifconfig eth0 up && ifconfig eth0 10.0.0.3 netmask 255.255.255.0 && [...]
[...]
> root@user:/home/user# ifconfig -a
> eth0 Link encap:Ethernet direcciónHW 14:fe:b5:b8:11:13
> Direc. inet:10.0.0.3 Difus.:10.0.0.255 Másc:255.255.255.0
> ACTIVO DIFUSIÓN MULTICAST MTU:1500 Métrica:1
> Paquetes RX:0 errores:0 perdidos:0 overruns:0 frame:0
> Paquetes TX:0 errores:0 perdidos:0 overruns:0 carrier:0
> colisiones:0 long.colaTX:1000
> Bytes RX:0 (0.0 B) TX bytes:0 (0.0 B)
Here "FUNCIONANDO" is absent from ifconfig, this means that you have no carrier.
The content below also confirms it:
> - Device: eth0 [...]
[...]
> Carrier Detect: yes
[...]
> Carrier: off
No carrier means that your laptop doesn't see the network cable as connected to another machine on the other side.
To get an ethernet carrier signal you need:
- Your laptop's ethernet interface being up (ifconfig eth0 up)
- The computer's ethernet interface on the other side being up (ifconfig eth0 up)
OR:
A switch on the other side that is powered on.
Try that:
(1) Boot the machine under parabola and get the network with:
> ifconfig eth0 up && ifconfig eth0 10.0.0.3 netmask 255.255.255.0 && ping -c4 10.0.0.2
This will validate that the hardware setup works.
(2) Try again under Trisquel with the exact same command:
> ifconfig eth0 up && ifconfig eth0 10.0.0.3 netmask 255.255.255.0 && ping -c4 10.0.0.2
(3) If that fails, try to use the network manager GUI instead to do the same thing.
Network manager tend to claim the interface and to not let you use ifconfig on the command
line interface.
There are ways to make sure it doesn't handle your network card, but it might not be that
easy to configure.
Also note that I use parabola, and due to some technical issue, my Trisquel vms are gone.
I have to reinstall them but it's not my priority right now.
Denis.
Hi, Denis, thanks a lot for your help.
If you can, please check what has happened, which is explained in these comments: https://trisquel.info/es/forum/howto-reactivate-laptops-nic-it-worked-fine-and-still-works-under-parabola#comment-107213
Thanks again, any help would be really appreciated!
In order to close this issue I want to let everybody know that the source of the problem was finally identified.
It was not Trisquel, nor the kernel, module/driver, neither NIC or cable: The malfunction was in the port of the router that was in use.
The router has 4 ports for Ethernet cable and the laptop was using port 2. This port has proven to have a random behavior (sometimes connect, sometimes not, and the speed is low, etc.).
Using any other of the ports solve all the issues, for any kernel and distro.
So, could anybody give me an idea about which would be the better way to go back to the normal Trisquel kernel?
Thanks a lot for everything to everybody!
- Install (if it is not there anymore) the image of one of the kernels Trisquel provides: "linux-image-lowlatency" (that is the one that was installed by default) or "linux-image-generic" or...;
- Remove the packages provided by linux-libre.fsfla.org (you can easily list them with the "Origin" button in the bottom-left corner of the "Synaptic Package Manager" in the "System Settings";
- Optionally, remove the line "deb https://linux-libre.fsfla.org/pub/linux-libre/freesh/ freesh main" from /etc/apt/sources.list with a text editor (here GEdit):
$ gksu gedit /etc/apt/sources.list
I am actually not certain APT will let you remove the kernel you are currently running. If not, reboot on Trisquel's kernel after installing it: at GRUB's menu, choose the "Advanced options" and then Trisquel 7's kernel (version 3.13). If you have not removed GRUB password, first learn it:
$ sudo cat /etc/grub.d/01_PASSWORD
It is the number at the very end of the output. The user is "grub".
- Anmelden oder Registrieren um Kommentare zu schreiben