Your message dated Sat, 06 Jun 2009 02:07:16 +0100 with message-id <1244250436.21215.49.camel@deadeye> and subject line Re: ne2k-pci driver does not support link detection has caused the Debian Bug report #496887, regarding ne2k-pci driver does not support link detection to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 496887: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496887 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: network-manager: disables working interfaces it can't administer
- From: Michael Below <mbelow@antithese.de>
- Date: Thu, 28 Aug 2008 11:44:08 +0200
- Message-id: <20080828094408.4910.16344.reportbug@localhost>
Package: network-manager Version: 0.6.6-2 Severity: important Hi, I have an old PCI ethernet card run by the ne2k-pci kernel driver. Before installing NetworkManager, this card was autoconfigured by the Debian installer via an entry in /etc/network/interfaces to use DHCP, and everything worked alright. After installing NetworkManager, the card is initially configured using during normal boot, and then NetworkManager starts up, takes over, finds that the card has no carrier detect and then disables it. This is obviously wrong, and there seems to be no easy way to work around it. The recommended way of action for similar cases in the Ubuntu forums is uninstalling NetworkManager, and that's what I did. So the package seems essentially harmful for people with network interfaces NetworkManager can't deal with. Thank you for your work! Michael Below Some snippets from my syslog: Aug 28 10:29:54 tucholsky avahi-daemon[3450]: avahi-daemon 0.6.22 starting up. Aug 28 10:29:54 tucholsky avahi-daemon[3450]: Successfully called chroot(). Aug 28 10:29:54 tucholsky avahi-daemon[3450]: Successfully dropped remaining capabilities. Aug 28 10:29:54 tucholsky avahi-daemon[3450]: No service file found in /etc/avahi/services. Aug 28 10:29:54 tucholsky avahi-daemon[3450]: Joining mDNS multicast group /on interface eth0.IPv6 with address fe80::280:48ff:feca:a535. Aug 28 10:29:54 tucholsky avahi-daemon[3450]: New relevant interface /eth0.IPv6 for mDNS. Aug 28 10:29:54 tucholsky avahi-daemon[3450]: Joining mDNS multicast group /on interface eth0.IPv4 with address 192.168.178.25. Aug 28 10:29:54 tucholsky avahi-daemon[3450]: New relevant interface /eth0.IPv4 for mDNS. Aug 28 10:29:54 tucholsky avahi-daemon[3450]: Network interface enumeration /completed. Aug 28 10:29:54 tucholsky avahi-daemon[3450]: Registering new address record /for fe80::280:48ff:feca:a535 on eth0.*. Aug 28 10:29:54 tucholsky avahi-daemon[3450]: Registering new address record /for 192.168.178.25 on eth0.IPv4. Aug 28 10:29:54 tucholsky avahi-daemon[3450]: Registering HINFO record with /values 'I686'/'LINUX'. Aug 28 10:29:54 tucholsky avahi-dnsconfd[3462]: Successfully connected to /Avahi daemon. Aug 28 10:29:54 tucholsky dhcdbd: Started up. Aug 28 10:29:55 tucholsky avahi-daemon[3450]: Server startup complete. Host name is tucholsky.local. Local service cookie is 25709544. Aug 28 10:30:01 tucholsky NetworkManager: <info> starting... Aug 28 10:30:01 tucholsky NetworkManager: <info> New VPN service 'vpnc' (org.freedesktop.NetworkManager.vpnc). Aug 28 10:30:01 tucholsky NetworkManager: <info> New VPN service 'openvpn' (org.freedesktop.NetworkManager.openvpn). Aug 28 10:30:02 tucholsky NetworkManager: <info> eth0: Driver 'ne2k-pci' does not support carrier detection. ^IYou must switch to it manually. Aug 28 10:30:02 tucholsky NetworkManager: <info> nm_device_init(): waiting for device's worker thread to start Aug 28 10:30:02 tucholsky ntpd[3438]: synchronized to 88.198.18.245, stratum 3 Aug 28 10:30:02 tucholsky ntpd[3438]: time reset +0.210506 s Aug 28 10:30:02 tucholsky ntpd[3438]: kernel time sync status change 0001 Aug 28 10:30:02 tucholsky NetworkManager: <info> nm_device_init(): device's worker thread started, continuing. Aug 28 10:30:02 tucholsky NetworkManager: <info> Now managing wired Ethernet (802.3) device 'eth0'. Aug 28 10:30:02 tucholsky NetworkManager: <info> Deactivating device eth0. Aug 28 10:30:02 tucholsky avahi-daemon[3450]: Withdrawing address record for 192.168.178.25 on eth0. Aug 28 10:30:02 tucholsky avahi-daemon[3450]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.178.25. Aug 28 10:30:02 tucholsky avahi-daemon[3450]: Interface eth0.IPv4 no longer relevant for mDNS. Aug 28 10:30:02 tucholsky avahi-daemon[3450]: Withdrawing address record for fe80::280:48ff:feca:a535 on eth0. Aug 28 10:30:02 tucholsky avahi-daemon[3450]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::280:48ff:feca:a535. Aug 28 10:30:02 tucholsky avahi-daemon[3450]: Interface eth0.IPv6 no longer relevant for mDNS. Aug 28 10:30:05 tucholsky ntpd[3438]: sendto(88.198.18.245) (fd=21): Invalid argument Aug 28 10:32:44 tucholsky dhclient: Internet Systems Consortium DHCP Client V3.1.1 Aug 28 10:32:44 tucholsky dhclient: Copyright 2004-2008 Internet Systems Consortium. Aug 28 10:32:44 tucholsky dhclient: All rights reserved. Aug 28 10:32:44 tucholsky dhclient: For info, please visit http://www.isc.org/sw/dhcp/ Aug 28 10:32:44 tucholsky dhclient: Aug 28 10:32:45 tucholsky dhclient: Listening on LPF/eth0/00:80:48:ca:a5:35 Aug 28 10:32:45 tucholsky dhclient: Sending on LPF/eth0/00:80:48:ca:a5:35 Aug 28 10:32:45 tucholsky dhclient: Sending on Socket/fallback Aug 28 10:32:46 tucholsky dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Aug 28 10:32:46 tucholsky dhclient: DHCPACK from 192.168.178.1 Aug 28 10:32:46 tucholsky avahi-daemon[3450]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.178.25. Aug 28 10:32:46 tucholsky avahi-daemon[3450]: New relevant interface eth0.IPv4 for mDNS. Aug 28 10:32:46 tucholsky avahi-daemon[3450]: Registering new address record for 192.168.178.25 on eth0.IPv4. Aug 28 10:32:46 tucholsky dhclient: bound to 192.168.178.25 -- renewal in 399454 seconds. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26 (PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.UTF-8) Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
- To: 496887-done@bugs.debian.org
- Subject: Re: ne2k-pci driver does not support link detection
- From: Ben Hutchings <ben@decadent.org.uk>
- Date: Sat, 06 Jun 2009 02:07:16 +0100
- Message-id: <1244250436.21215.49.camel@deadeye>
This is not a bug. The NE2000 controller (DP8390) does not appear to report the link state, so the driver cannot do so. Ben. -- Ben Hutchings Logic doesn't apply to the real world. - Marvin MinskyAttachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---