![]() I installed the zram-config package, which is apparently marked as staging. I uninstalled avahi-daemon and avahi-autoipd today. Apport prompted me to send a problem report, but I don't know if it ever reached Launchpad due to the problem being network-related. I had seen during the first week of installation ( to ) that avahi-daemon crashed and caused one or two disconnections during that week, after which dhclient ran and reconnected to the LAN. I attempted a workaround based on something I found at : add "ethtool -s eth0 autoneg off" to /etc/network/ if-pre- up.d/ethtool. Even after deleting its configuration files and rebooting, the bug persists. I installed the "connman" package around and uninstalled it right away, restoring network-manager (because connman was flaky), and only today () uninstalled its configuration files. There is also a custom DNS suffix for the local network, which is not '.local'. NetworkManager is set up via GNOME to seek DHCP addresses but have custom DNS nameservers at 127.0.0.1 (bind9, for the local network) and 192.168.0.1, the D-Link router, which forwards DNS requests to the ISP's nameservers. There are no IPv6 addresses on the network. ![]() The D-Link router is set up as a DHCP server and hands out fixed addresses by MAC. IPv4 addresses are not in conflict on the network. * A SpeedTouch modem for ADSL service, whose status light for "Internet" does absolutely nothing when this bug occurs, staying on throughout the disconnection and subsequent reconnection * An Ethernet cable between the router and the modem, also bought during the month of 2011-12 and known good * A D-Link router, whose status light for the affected computer does absolutely nothing when this bug occurs, staying on throughout the subsequent reconnection * An Ethernet cable bought during the month of 2011-12, with connectors that rest securely in the Ethernet plug, known good due to it working flawlessly on the previous computer the power supply unit) flashes when the network is accessed, and the status light closest to the bottom is constantly on The status light closest to the top of the computer (i.e. * A plug on the computer, with 2 status lights, one on either side of the plug. * The NIC, which is on a chip on the motherboard, and supports 100BaseT and 1000BaseT From it, the path to the Internet is as follows: The computer that is affected was bought during the month of 2012-02. 'dhclient' gets killed and restarted, and no crash is reported on dhclient. The dmesg log gets filled with "link is now down" and "link is now up" at random times, the period between which is random and can be anything from 5 minutes to 2 hours. ![]() On or around, the network interface started to go down and up at random times, which I initially thought of as the Internet access on my downstream router going out, but I started to see NetworkManager (GNOME) notifications as well: Until or so, the network interface worked fine in Precise ( unlike in Lucid where it would constantly go up and down every 5 to 20 minutes, starting from boot ). RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06) The computer I am currently using is an Acer Aspire AM3450-ES10P, whose network card is identified in 'lspci' output as follows:Ġ5:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. I am using Linux 3.2.0-24- generic- pae on Ubuntu Precise Pangolin, 32-bit, installed on.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |