Your message dated Sun, 30 Sep 2012 12:39:58 -0700 with message-id <[email protected]> and subject line Re: tulip has no link detection, under VirtualPC and Hyper-V has caused the Debian Bug report #490816, regarding linux-image-2.6-686: tulip has no detection under VirtualPC and Hyper-V 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 [email protected] immediately.) -- 490816: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490816 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: network-manager Version: 0.6.6-1 Severity: normal Please describe the problem: When I boot Debian under Microsoft VirtualPC 2007 or WindowsServer Hyper-V, the network is "disconnected". The network interface is has PCI id =1011:0009 "Digital Equipment Corporation DECchip 21140 [FasterNet]" The Linux kernel module to handle it is "tulip". Steps to reproduce: 1. Boot Debian (stable or Testing) under VirtualPC 2007 or Hyper-V 2a. Open a session in a console, type "ifconfig" : The interface isn't configured 3a. Type "ifup eth0" : the interface get configured. or 2b. Open a session under gnome : the NM applet says the link is down. (click on the icon, the "Wired Networking" isn't ticked in !). 3b. Click on the NM applet, tick-in "Wired Networking" : the interface get configured. Actual results: We notice that the interface is down. Expected results: The interface should be up and configured. Does this happen every time? Yes. Under Debian stable (kernel 2.6.18 + NM 0.6.4) and Debian Testing (kernel 2.6.25 + NM 0.6.6) I've opened a bug upstream : http://bugzilla.gnome.org/show_bug.cgi?id=542916 Franklin -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.25-2-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages network-manager depends on: ii adduser 3.108 add and remove users and groups ii dbus 1.2.1-2 simple interprocess messaging syst ii dhcdbd 3.0-4 D-Bus interface to the ISC DHCP cl ii hal 0.5.11-2 Hardware Abstraction Layer ii ifupdown 0.6.8+nmu1 high level tools to configure netw ii iproute 20080417-1 networking and traffic control too ii iputils-arping 3:20071127-1 Tool to send ICMP echo requests to ii libc6 2.7-10 GNU C Library: Shared libraries ii libdbus-1-3 1.2.1-2 simple interprocess messaging syst ii libdbus-glib-1-2 0.76-1 simple interprocess messaging syst ii libgcrypt11 1.4.1-1 LGPL Crypto library - runtime libr ii libglib2.0-0 2.16.3-2 The GLib library of C routines ii libgpg-error0 1.4-2 library for common error values an ii libhal1 0.5.11-2 Hardware Abstraction Layer - share ii libiw29 29-1 Wireless tools - library ii libnl1 1.1-2 library for dealing with netlink s ii libnm-util0 0.6.6-1 network management framework (shar ii lsb-base 3.2-12 Linux Standard Base 3.2 init scrip ii wpasupplicant 0.6.3-2 Client support for WPA and WPA2 (I Versions of packages network-manager recommends: ii network-manager-gnome 0.6.6-2 network management framework (GNOM -- no debconf information
--- End Message ---
--- Begin Message ---In May, Jonathan Nieder wrote: > In 2008, Franklin PIAT wrote: >> When I boot Debian under Microsoft VirtualPC 2007 or WindowsServer Hyper-V, >> the network is "disconnected". [...] > Did you make any progress with the help of Grant? Do you > still have access to this [setup], and if so, can you still reproduce > the bug? Closing due to lack of response. If you have more information, please don't hesitate to write, though, and we can pick up where we left off.
--- End Message ---
