Jump to content


  • Content Count

  • Joined

  • Last visited

About bug

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Setting a static IP ( in this case, because the subnet is results in nothing. eth0 reports as connected but receives no traffic. Out of curiosity, I also looked into what "ipv6_addaddr1: Permission denied" might mean, and it seems that it has to do with NetworkManager disabling ipv6 temporarily while it tries to set up the connection. However, enabling it doesn't let dhcpcd get any further, it just removes the "ipv6_addaddr1: Permission denied" error, and fails in the exact same way (timeout). Thank you all for running me through the basic diagnostics,
  2. no such file. nothing has been changed from the defaults since install.
  3. It should be giving both, but so far, I am receiving neither. eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 44:8a:5b:85:2b:be txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 37 Other devices on the same LAN are receiving both IPv4 and IPv6 addresses.
  4. formicarium bug # lsmod | grep alx alx 40960 0 mdio 16384 1 alx you are correct.
  5. NetworkManager, but it fails with dhcpcd and dhclient too. Here's dhcpcd output: DUID 00:01:00:01:21:7a:8f:c1:44:8a:5b:85:2b:be eth0: IAID 5b:85:2b:be eth0: adding address fe80::77fd:da5a:d9ab:e830 ipv6_addaddr1: Permission denied eth0: soliciting an IPv6 router eth0: soliciting a DHCP lease eth0: probing for an IPv4LL address eth0: carrier lost eth0: carrier acquired eth0: IAID 5b:85:2b:be eth0: soliciting a DHCP lease eth0: soliciting an IPv6 router eth0: probing for an IPv4LL address eth0: carrier lost eth0: carrier acquired eth0: IAID 5b:85:2b:be eth0: soliciting an IPv6 router eth0:
  6. Yes, as mentioned, I tested both debian-sources and gentoo-sources. I used genkernel, making sure CONFIG_ALX is enabled (alx is the only known driver that supports my card). LAN does not work in any case. The module loads, and detects my card, but does not complete DHCP with my router. The router works with other devices. All of this was working until last week.
  7. I have tested three different kernels from recent history, making sure the alx driver module is enabled, in an attempt to determine whether it was a kernel/driver issue, and I think I can rule that out. eth0 fails to connect on all three. sys-kernel/debian-sources-4.8.15 sys-kernel/gentoo-sources-4.13.9 sys-kernel/gentoo-sources-4.4.94 However, I did notice that the alx driver was disabled by default on 4.13.9, which probably means it is viewed as unstable. I suppose that should not be surprising. The Killer NIC series is not very well supported by anybody, not even the
  8. After doing a sucessful emerge -auvDN @world for the first time since the switch to ego (which involved a LOT of pain and masking/unmasking/oneshots due to version differences), my NIC is not working. Due to the very large number of packages updated, I have no idea which one could have caused the malfunction.I'm having to tether my desktop to my phone through USB. I have tried every possible relevant genkernel config, and I even tried patching the atl1c driver by hand to support my card (details below) 03:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet
  • Create New...