[Bug 315947] Re: forcedeth NIC fails to operate
This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: Triaged = Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/315947 Title: forcedeth NIC fails to operate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/315947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315947] Re: forcedeth NIC fails to operate
I found this when trying to figure out why my dual-boot win7 and ubuntu 10.10 machine kept failing to acquire DHCP from my router. http://forums.fedoraforum.org/showthread.php?t=240880 Scroll down to post #3 to get the fix he used. Here is a brief on it. Basically the person had the same issues I had. Dual booting win7 and Linux (most likely any distro), and almost randomly switching between the two OS's would cause a DHCP failure in usually the linux install but less frequently the Win7 install. The firmware is all there, the drivers, et al. The NIC (s) would be recognized and functioning, but it would fail to register itself with a DNS lookup with a DHCP server. He found 2 issues . From the post: I've managed to sort the problem after a bit of playing with both Linux and the CentOS server. For anyone looking for a solution to the same problem, it was down to two separate faults: 1) The Linux installations (both Ubuntu 9.10 and Fedora 12) needed to have the DHCP client ID field set to the NICs MAC address - this is within the eth0 IPv4 panel of Network Manager. This allows the DHCP clients to appear to be as the same machine to the server, as Windows sends this DHCP uuid to the server by default. 2) There was also a mis-configuration of the DNS zone files, with the trailing dot being left off on the reverse lookup zone, so it might have been unrelated but it could have contributed to the overall not-working- ness of the server. After refreshing the DHCP lease caches on both the server and the clients, all three OSes on the PC are now assigned the same IP. This problem can really only occur on machines multi-booting, but it could be useful nonetheless Thanks I have been using this with no issues for two days now. Hope this helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/315947 Title: forcedeth NIC fails to operate -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315947] Re: forcedeth NIC fails to operate
@m0sia: I tried setting the MAC address manually, but no result. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/315947 Title: forcedeth NIC fails to operate -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315947] Re: forcedeth NIC fails to operate
Hi all, Try to set the mac address on the interface with the following command: sudo ifconfig eth0 hw ether your NIC MAC -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/315947 Title: forcedeth NIC fails to operate -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315947] Re: forcedeth NIC fails to operate
Still not working with Linux 2.6.35-24-generic #42-Ubuntu SMP Thu Dec 2 01:41:57 UTC 2010 i686 GNU/Linux Machine Zotac MAG HD. lspci | grep -i ether 00:0a.0 Ethernet controller: nVidia Corporation MCP79 Ethernet (rev b1) dmesg | grep eth0 [1.387597] forcedeth :00:0a.0: ifname eth0, PHY OUI 0x732 @ 3, addr 00:01:2e:2b:21:b9 dhclient eth0 Internet Systems Consortium DHCP Client V3.1.3 Copyright 2004-2009 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/eth0/00:01:2e:2b:21:b9 Sending on LPF/eth0/00:01:2e:2b:21:b9 Sending on Socket/fallback DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 19 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 No DHCPOFFERS received. No working leases in persistent database - sleeping. rmmod/modprobe is no use. Link goes up, but no activity present. Same thing in FreeBSD btw. Wireless works fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/315947 Title: forcedeth NIC fails to operate -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315947] Re: forcedeth NIC fails to operate
My forecedeth based NICs actually work now as of Maverick. I was running a maverick live cd on the system I've been having this problem with and noticed it worked out of the box. I upgraded to maverick that night and it's been bliss since. If it helps any, here's some command output: ADR-super:~$ uname -a Linux ADR-super 2.6.35-24-generic #42-Ubuntu SMP Thu Dec 2 02:41:37 UTC 2010 x86_64 GNU/Linux ADR-super:~$ lspci | grep -i ether 00:11.0 Bridge: nVidia Corporation MCP55 Ethernet (rev a2) 00:12.0 Bridge: nVidia Corporation MCP55 Ethernet (rev a2) ADR-super:~$ dmesg | grep -E 'eth[0-9]' [1.311826] forcedeth :00:11.0: ifname eth0, PHY OUI 0x5043 @ 19, addr 00:1a:92:83:1c:31 [1.840590] forcedeth :00:12.0: ifname eth1, PHY OUI 0x5043 @ 19, addr 00:1a:92:83:2b:cc [ 12.551658] udev[487]: renamed network interface eth1 to eth2 [ 12.580380] udev[486]: renamed network interface eth0 to eth1 [ 40.467322] eth2: no link during initialization. [ 40.468368] ADDRCONF(NETDEV_UP): eth2: link is not ready [ 50.730009] eth1: no IPv6 routers present -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/315947 Title: forcedeth NIC fails to operate -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315947] Re: forcedeth NIC fails to operate
** Description changed: I just installed and dist-upgrade'ed Jaunty alpha-2 and discovered my on-board ethernet was not working. With my previous OS (gutsy) it was using the forcedeth kernel module, and it is doing so now too. I have tried my normal dhcp settings (via /etc/network/interfaces and NetworkManager) and setting it static (via /etc/network/interfaces). When set with dhcp, it never receives a dhcp offer and when set static it is not able to send or receive any packets through that connection. I took a spare usb 802.11g nic and plugged it in. Within 20 seconds it was initialized and connected to my home wifi without problem. I am not a kernel/hardware/networking expert, but below are a few things I could thing of that could be helpful. and...@adr-super:~$ lsb_release -rd Description: Ubuntu jaunty (development branch) Release: 9.04 and...@adr-super:~$ uname -a Linux ADR-super 2.6.28-4-generic #9-Ubuntu SMP Tue Jan 6 19:33:48 UTC 2009 x86_64 GNU/Linux and...@adr-super:~$ sudo lshw | grep -A7 network: - *-network:0 -description: Wireless interface -physical id: 1 -logical name: wlan0 -serial: 00:14:d1:c0:06:55 -capabilities: ethernet physical wireless -configuration: broadcast=yes ip=172.16.1.179 multicast=yes wireless=IEEE 802.11bg - *-network:1 DISABLED -description: Ethernet interface -physical id: 2 -logical name: pan0 -serial: 56:6c:c0:dc:fb:f4 -capabilities: ethernet physical -configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A link=yes multicast=yes + *-network:0 + description: Wireless interface + physical id: 1 + logical name: wlan0 + serial: 00:14:d1:c0:06:55 + capabilities: ethernet physical wireless + configuration: broadcast=yes ip=172.16.1.179 multicast=yes wireless=IEEE 802.11bg + *-network:1 DISABLED + description: Ethernet interface + physical id: 2 + logical name: pan0 + serial: 56:6c:c0:dc:fb:f4 + capabilities: ethernet physical + configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A link=yes multicast=yes and...@adr-super:~$ sudo lshw | grep -A14 bridge: - *-bridge:0 DISABLED - description: Ethernet interface - product: MCP55 Ethernet - vendor: nVidia Corporation - physical id: 11 - bus info: p...@:00:11.0 - logical name: eth0 - version: a2 - serial: 00:1a:92:83:1c:31 - size: 10 - capacity: 10 - width: 32 bits - clock: 66MHz - capabilities: bridge pm msix msi ht bus_master cap_list ethernet physical mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation - configuration: autonegotiation=on broadcast=yes driver=forcedeth driverversion=0.61 duplex=full ip=172.16.1.200 latency=0 link=yes maxlatency=20 mingnt=1 module=forcedeth multicast=yes port=MII speed=1GB/s - *-bridge:1 DISABLED - description: Ethernet interface - product: MCP55 Ethernet - vendor: nVidia Corporation - physical id: 12 - bus info: p...@:00:12.0 - logical name: eth1 - version: a2 - serial: 00:1a:92:83:2b:cc - capacity: 10 - width: 32 bits - clock: 66MHz - capabilities: bridge pm msix msi ht bus_master cap_list ethernet physical mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation - configuration: autonegotiation=on broadcast=yes driver=forcedeth driverversion=0.61 latency=0 link=no maxlatency=20 mingnt=1 module=forcedeth multicast=yes port=MII + *-bridge:0 DISABLED + description: Ethernet interface + product: MCP55 Ethernet + vendor: nVidia Corporation + physical id: 11 + bus info: p...@:00:11.0 + logical name: eth0 + version: a2 + serial: 00:1a:92:83:1c:31 + size: 10 + capacity: 10 + width: 32 bits + clock: 66MHz + capabilities: bridge pm msix msi ht bus_master cap_list ethernet physical mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation + configuration: autonegotiation=on broadcast=yes driver=forcedeth driverversion=0.61 duplex=full ip=172.16.1.200 latency=0 link=yes maxlatency=20 mingnt=1 module=forcedeth multicast=yes port=MII speed=1GB/s + *-bridge:1 DISABLED + description: Ethernet interface + product: MCP55 Ethernet + vendor: nVidia Corporation + physical id: 12 + bus info:
[Bug 315947] Re: forcedeth NIC fails to operate
Still not working with: 2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:27:30 UTC 2010 i686 GNU/Linux dmesg | grep -i eth0 [1.436766] forcedeth :00:0a.0: ifname eth0, PHY OUI 0x0 @ 1, addr 00:01:2e:2c:22:4b [7.287548] eth0: no link during initialization. [7.288043] ADDRCONF(NETDEV_UP): eth0: link is not ready -- forcedeth NIC fails to operate https://bugs.launchpad.net/bugs/315947 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315947] Re: forcedeth NIC fails to operate
I'm having the problem with ubuntu 10.4 and 9.10, however mint 9.10 works. -- forcedeth NIC fails to operate https://bugs.launchpad.net/bugs/315947 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315947] Re: forcedeth NIC fails to operate
Still not working with 2.6.32-21-generic-pae -- forcedeth NIC fails to operate https://bugs.launchpad.net/bugs/315947 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315947] Re: forcedeth NIC fails to operate
I am still not able to connect to my wired connection. Using DHCP, it never receives a dhcp offer and when set to static it is not able to send or receive any packets. I was wondering if the link comes up during boot, and tried: sudo rmmod -f forcedeth sudo modprobe forcedeth phy_power_down=0 and created a /etc/modprobe.d/forcedeth.conf but still no luck. Ethernet works in Win --- Can somebody help Thanks lspci | grep -i ethernet 00:0a.0 Ethernet controller: nVidia Corporation MCP79 Ethernet (rev b1) uname -a Linux etclive-desktop 2.6.31-20-generic #58-Ubuntu SMP Fri Mar 12 04:38:19 UTC 2010 x86_64 GNU/Linux nm-tool result: Device: eth0 - Type: Wired Driver:forcedeth State: unavailable Default: no HW Address:00:01:2E:2C:22:4B Capabilities: Carrier Detect: yes Wired Properties Carrier: off sudo lshw -C network *-network description: Ethernet interface product: MCP79 Ethernet vendor: nVidia Corporation physical id: a bus info: p...@:00:0a.0 logical name: eth0 version: b1 serial: 00:01:2e:2c:22:4b capacity: 100MB/s width: 32 bits clock: 66MHz capabilities: pm bus_master cap_list ethernet physical mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=forcedeth driverversion=0.64 latency=0 link=no maxlatency=20 mingnt=1 multicast=yes port=MII resources: irq:22 memory:fe02b000-fe02bfff ioport:fc00(size=8) memory:fe02a000-fe02a0ff memory:fe029000-fe02900f *-network description: Wireless interface physical id: 1 logical name: wlan1 serial: 00:14:d1:6a:e9:18 capabilities: ethernet physical wireless configuration: broadcast=yes ip=130.15.41.33 multicast=yes wireless=IEEE lsmod | grep forced forcedeth 61292 0 I added a forcedeth.conf, but still disconnected... more /etc/modprobe.d/forcedeth.conf alias eth0 forcedeth options forcedeth phy_power_down=0 sudo dhclient3 eth0 [sudo] password for etclive: Internet Systems Consortium DHCP Client V3.1.2 Copyright 2004-2008 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Listening on LPF/eth0/00:01:2e:2c:22:4b Sending on LPF/eth0/00:01:2e:2c:22:4b Sending on Socket/fallback DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17 No DHCPOFFERS received. No working leases in persistent database - sleeping. ifconfig -a eth0 Link encap:Ethernet HWaddr 00:01:2e:2c:22:4b UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:22 Base address:0x4000 eth0:avahi Link encap:Ethernet HWaddr 00:01:2e:2c:22:4b inet addr:169.254.3.225 Bcast:169.254.255.255 Mask:255.255.0.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 Interrupt:22 Base address:0x4000 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:128 errors:0 dropped:0 overruns:0 frame:0 TX packets:128 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:8960 (8.9 KB) TX bytes:8960 (8.9 KB) wlan1 Link encap:Ethernet HWaddr 00:14:d1:6a:e9:18 inet addr:130.15.41.33 Bcast:130.15.41.255 Mask:255.255.255.0 inet6 addr: fe80::214:d1ff:fe6a:e918/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:87996 errors:0 dropped:0 overruns:0 frame:0 TX packets:27437 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:55655894 (55.6 MB) TX bytes:3447736 (3.4 MB) wmaster0 Link encap:UNSPEC HWaddr 00-14-D1-6A-E9-18-00-00-00-00-00-00-00-00-00-00 UP RUNNING MTU:0 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) dmesg | grep -i eth0 [2.040725] forcedeth :00:0a.0: ifname eth0, PHY OUI 0x0 @ 1, addr 00:01:2e:2c:22:4b [ 12.204669] eth0: no link during initialization. [ 12.205165] ADDRCONF(NETDEV_UP): eth0: link is
[Bug 315947] Re: forcedeth NIC fails to operate
Any updateds on this? Tried latest mainline-2.6.32 kernel, which didn't solve the problem, so my NIC is broken ATM. -- forcedeth NIC fails to operate https://bugs.launchpad.net/bugs/315947 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315947] Re: forcedeth NIC fails to operate
Its working for me now in ubuntu server kernel: 2.6.31-17-server -- forcedeth NIC fails to operate https://bugs.launchpad.net/bugs/315947 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315947] Re: forcedeth NIC fails to operate
** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Changed in: linux (Ubuntu) Status: Incomplete = Triaged -- forcedeth NIC fails to operate https://bugs.launchpad.net/bugs/315947 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315947] Re: forcedeth NIC fails to operate
Thank you for your interest, Leann. I downloaded and installed the 2.6.31-rc2 mainline kernel build and booted it this afternoon. My forcedeth-dependent network interfaces still did not work. My symptoms and issues relating to it were unchanged from the original post. I ran `ubuntu-bugs linux` and saved the attached file. Hopefully this can help someone fix this. I'm pretty good these days with hacking through code and recompiling whatever. Please let me know if there are any other steps I can take to help troubleshoot this problem and test any potential patches someone may have. ** Attachment added: saved output of ubuntu-bugs linux http://launchpadlibrarian.net/28900982/linux%20bug%20report.txt -- forcedeth NIC fails to operate https://bugs.launchpad.net/bugs/315947 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315947] Re: forcedeth NIC fails to operate
Hi Guys, The upcoming kernel for Karmic is going to target the 2.6.31 kernel. Currently the karmic kernel has most recently rebased with the upstream 3.6.31-rc2 kernel and is available for testing in the latest Karmic Alpha images (linux-image-2.6.31-2-generic). Would be great if someone could test this latest 2.6.31-2 karmic kernel and confirm if this issue is resolved. An alternative would also be to test the latest mainline 2.6.31-rc2 mainline kernel build - https://wiki.ubuntu.com/KernelTeam/MainlineBuilds . Please let us know your results. Thanks. ** Changed in: linux (Ubuntu) Status: New = Incomplete -- forcedeth NIC fails to operate https://bugs.launchpad.net/bugs/315947 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315947] Re: forcedeth NIC fails to operate
I've got what i assume is this problem on a Sun Fire X4140: Linux director 2.6.28-11-server #42-Ubuntu SMP Fri Apr 17 02:45:36 UTC 2009 x86_64 GNU/Linux I had two of the four interfaces configured and working for a short period, then one of them locked up, even after a reboot I cant seem to move data across it again (it's configured and the firewall reports its sending packets across it but nothing arrives). If I leave ping running I get: PING 192.168.5.2 (192.168.5.2) 56(84) bytes of data. From 192.168.5.1 icmp_seq=2 Destination Host Unreachable From 192.168.5.1 icmp_seq=3 Destination Host Unreachable From 192.168.5.1 icmp_seq=4 Destination Host Unreachable From 192.168.5.1 icmp_seq=5 Destination Host Unreachable From 192.168.5.1 icmp_seq=6 Destination Host Unreachable From 192.168.5.1 icmp_seq=7 Destination Host Unreachable From 192.168.5.1 icmp_seq=9 Destination Host Unreachable From 192.168.5.1 icmp_seq=10 Destination Host Unreachable From 192.168.5.1 icmp_seq=11 Destination Host Unreachable From 192.168.5.1 icmp_seq=13 Destination Host Unreachable From 192.168.5.1 icmp_seq=14 Destination Host Unreachable From 192.168.5.1 icmp_seq=15 Destination Host Unreachable ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available ... The four other interfaces (intel based pci cards) are working fine. If this has been fixed upstream do we have any indication of when fixes available for 9.04? -- forcedeth NIC fails to operate https://bugs.launchpad.net/bugs/315947 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315947] Re: forcedeth NIC fails to operate
Is this going to be fixed in 9.04? according to http://bugs.debian.org /cgi-bin/bugreport.cgi?bug=521691 it is fixed in 2.6.29-2 -- forcedeth NIC fails to operate https://bugs.launchpad.net/bugs/315947 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315947] Re: forcedeth NIC fails to operate
I just dist-upgrade'ed and tried again and my forcedeth interfaces still do not work. My packages are up-to-date as of 2:00AM EDT today. Let me know if there is anything I can do to help fix this. -- forcedeth NIC fails to operate https://bugs.launchpad.net/bugs/315947 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315947] Re: forcedeth NIC fails to operate
Maybe its related to this bug? http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=521691 i ran into this yesterday when trying to install 2.6.29. apparently it broke in 2.6.28.8 which ships with ubuntu 9.04 ** Bug watch added: Debian Bug tracker #521691 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=521691 -- forcedeth NIC fails to operate https://bugs.launchpad.net/bugs/315947 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315947] Re: forcedeth NIC fails to operate
** Changed in: linux (Ubuntu) Sourcepackagename: None = linux -- forcedeth NIC fails to operate https://bugs.launchpad.net/bugs/315947 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
