[Bug 299141] New: nVidia MCP61 Ethernet (rev a2) not supported anymore
https://bugzilla.novell.com/show_bug.cgi?id=299141 Summary: nVidia MCP61 Ethernet (rev a2) not supported anymore Product: openSUSE 10.3 Version: Beta 1 Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Blocker Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: fmfischer@gmx.net QAContact: qa@suse.de Found By: Beta-Customer The ASUS M2N-MX motherboard ethernet controller MCP61 (rev a2) is neither recognized nor manually useable (modprobe forcedeth). So my beta box has got no network. This is using 32bit 10.3 beta1 with "noapic". Without "noapic" box will not boot. Therefore I will suspend my beta test activities until MCP61 ethernet support is reestablished; it's just too cumbersome without network. I will therefore also not provide any additional info to this bug requiring the reboot into 10.3 beta1. The box and its ethernet controller runs perfectly under 32bit 10.2, kernel 2.6.18.8-0.5-default, booting with "noapic". Box will not boot 10.2 without "noapic". All 32bit kernel 2.6 distros required "noapic" on this motherboard. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=299141#c1 Greg Kroah-Hartman <gregkh@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |fmfischer@gmx.net --- Comment #1 from Greg Kroah-Hartman <gregkh@novell.com> 2007-08-10 01:46:27 MST --- Can you attach the output of 'hwinfo'? But if you are not going to boot into the 10.3 beta kernels, we will not be able to help you out at all. Try following the advice given on the opensuse-factory mailing list as to how to get the needed information off of this machine. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=299141#c2 Frank-Michael Fischer <fmfischer@gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|fmfischer@gmx.net | --- Comment #2 from Frank-Michael Fischer <fmfischer@gmx.net> 2007-08-10 01:57:14 MST --- Created an attachment (id=156699) --> (https://bugzilla.novell.com/attachment.cgi?id=156699) hwinfo, dmesg and boot.msg for my Asus M2N-MX motherboard Here you are. I did reboot into 10.3 beta 1 for that. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=299141#c3 Greg Kroah-Hartman <gregkh@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gregkh@novell.com AssignedTo|kernel- |kkeil@novell.com |maintainers@forge.provo.nove| |ll.com | --- Comment #3 from Greg Kroah-Hartman <gregkh@novell.com> 2007-08-10 02:46:38 MST --- Karsten, some odd network driver regression? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=299141#c4 --- Comment #4 from Michael Crees <mail@rhakios.ukfsn.org> 2007-08-11 12:30:40 MST --- Isn't this the same as Bug 297606? I found I could get MCP61 to work by creating my own /etc/sysconfig/network/ifcfg-eth0. Not ideal, but it does get you a network connection to enable testing of other features that require one. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=299141#c5 --- Comment #5 from N/A N/A <kernel01@hailfinger.org> 2007-08-11 17:00:24 MST --- forcedeth finds the device in 10.3beta1. Please run "ip a l" as root on both 10.2 and 10.3beta1 and post the result here (no need to attach, it's small). My suspicion is that eth0 has no ip address in 10.3beta1. The boot log shows that forcedeth finds the device and binds to it. However, it may be that just no ip address is assigned. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=299141#c6 --- Comment #6 from Frank-Michael Fischer <fmfischer@gmx.net> 2007-08-11 22:37:06 MST --- ip a l on 10.2: 1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo 2: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 10:33:22:44:77:66 brd ff:ff:ff:ff:ff:ff inet 192.168.178.99/24 brd 192.168.178.255 scope global eth0 3: wifi0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 199 link/ieee802.11 00:03:2f:39:a4:b4 brd ff:ff:ff:ff:ff:ff 4: ath0: <BROADCAST,MULTICAST,NOTRAILERS,UP,10000> mtu 1500 qdisc noqueue link/ether 00:03:2f:39:a4:b4 brd ff:ff:ff:ff:ff:ff inet 192.168.0.14/24 brd 192.168.0.255 scope global ath0 ip a l on 10.3b1: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo 2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000 link/ether 66:77:44:22:33:10 brd ff:ff:ff:ff:ff:ff ip a l on 10.3b1 after fiddling manually with /etc/sysconfig/network/ifcfg-eth0 and yast2 lan: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 66:77:44:22:33:10 brd ff:ff:ff:ff:ff:ff inet 192.168.178.99/24 brd 192.168.178.255 scope global eth0 yast2 lan provides strange error message now, viz coming attachment. But I do not think this is worth another bugzilla entry, since it comes up after manual fiddling with ifcfg-eth0 only. network functions now, actually using it for entering this comment. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=299141#c7 --- Comment #7 from Frank-Michael Fischer <fmfischer@gmx.net> 2007-08-11 22:40:05 MST --- Created an attachment (id=156934) --> (https://bugzilla.novell.com/attachment.cgi?id=156934) strange "yast2 lan" message for my MCP61 network card the interface and this message come up after manually creating /etc/sysconfig/network/ifcfg-eth0 only. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=299141#c8 N/A N/A <kernel01@hailfinger.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE --- Comment #8 from N/A N/A <kernel01@hailfinger.org> 2007-08-12 16:57:58 MST --- Thanks for checking. Let's continue this discussion in bug #297606. *** This bug has been marked as a duplicate of bug 297606 *** https://bugzilla.novell.com/show_bug.cgi?id=297606 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com