Connection Failed Activation of Network Connection Failed

English Install/Boot/Login
1

I am running openSUSE 12.1 Beta 1 GNOME and I cannot get an internet connection.

The wireless on my laptop says missing firmware which is fine. It says this on any distro and I can get it working. However, I can not get my wired connection to work. It keeps trying to connect and says "Connection Failed Activation of Network Connection Failed.

I have seen other people have this problem online somewhere and they said they had to swap something from manual to auto, but I am not sure what or where.

I know that this laptops ethernet card will work fine on here b/c I used openSUSE 11.4 before and I also was on the last milestone release before beta and it worked.

Any help will be much appreciated.

Thank you in advance.

2

As an update I just did a reinstall and the ethernet continues to fail to connect.

3

On another side note I just installed openSUSE 12.1 KDE Beta 1 and it does not work there as well.

Just like in GNOME the network options do not show up on initial boot until I do a reboot after the install.

Then it just tries to connect and fails over and over.

Any ideas?

4

On 10/07/2011 03:46 PM, Aydos13 wrote:
>
> On another side note I just installed openSUSE 12.1 KDE Beta 1 and it
> does not work there as well.

Some details concerning the faulty hardware is necessary, or do you just want to
complain. In particular, ‘/sbin/lspci -nn’ is needed.

5

No I did not just come here to complain that is a bold face assumption.

However, I am driving now and I will get the information when I get home today. I was not sure what information was needed from me.

6

This may be a variant of the problem that I have run into in testing both Fedora 16 and openSUSE 12.1. If so, one workaround is to edit the connection, setting it to launch automatically and to be available to all users. Then restart the system. If you do have the same problem, all should be well thereafter. The problem has been around for some time in network manager, and there was a bug report active at one stage - sorry, but I don’t have the number to hand.

7

Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5752 Gigabit Ethernet PCI Express [14e4:1600] (rev 02)

8

That is the problem I saw floating around the web.

Forgive my ignorance, but where do I need to go and what do I need to edit to get it running.

Thank you.

9

Go to <Network> under <System Settings>, and click on the <Configure> button to launch the editor. I suspect that you could edit almost anything, including the name you choose to give the connection, and that the real catalyst for a working connection is saving the revised configuration. However, the common wisdom seems to be that the connection should be set to launch automatically (even if it is already in that configuration - just click the relevant box off then on again) and that works for me too.

As a security blanket (because it forces the package actually to save the new configuration) I usually also make the connection available to all users. That is fine from my perspective, but you could try omitting that step if you have any concerns. Let us know how you get on.

10

On 10/07/2011 05:16 PM, Aydos13 wrote:
>
> Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5752
> Gigabit Ethernet PCI Express [14e4:1600] (rev 02)

Editing any files other than the driver source will not help you. Your device is
NOT in the kernel driver tables. I’m not quite sure why, as an older source I
found has that ID included. I will contact the maintainer to see why it might
have been changed.

As a temporary work around, do the following:


su -
/sbin/modprobe -v tg3
/bin/echo "14e4 1600" > /sys/bus/drivers/tg3/new_id

Please report back if this helps. If it does, you will need these commands every
time you reboot. You could also add the last two of those commands to
/etc/init.d/boot.local. That way the commands will be run whenever you reboot.

11

When I open Network under system settings I get a window that pops up with a computer making a :frowning: face and says The system network services are not compatible with this version.

Any ideas from here ?

12

When I run that command I get /sys/bus/drivers/tg3/new_id: No such file or directory.

Any luck contacting the maintainer ?

13

I apologize. I guess I had not originally rebooted after the install (I have re installed a couple of times in KDE and GNOME) so it was not detecting any network stuff and just ad proxy as an option. After a quick reboot I had a wired connection again that failed to connect.

I went to network under settings and looked at wired and nothing seemed to be wrong. I clicked save on the configure menu and it popped a window asking for the admin password and then it instantly closes and starts trying to connect again which fails.

14

Ok I am not sure what all I did, but i have it working. Thanks for all the help that got me here.

15

From YaST2; Global Options (tab) select; Traditional Method with ifup /click-OK then reboot the system.
The wired network should connect. I made sure the following (below) were also added, then I went back to Network Settings, and selected; User Controlled with NetworkManager. Use only KDE not the gnome.

NetworkManager - Network Link Manager and User Applications (0.9.0-7.1)
NetworkManager-kde4-libs - NetworkManager client for KDE 4 (0.9.1git20110911-1.1)
libnm-glib4 - Convenience library for clients of NetworkManager (0.9.0-7.1)
libnm-util2 - Convenience library for clients of NetworkManager (0.9.0-7.1)
plasmoid-networkmanagement - NetworkManager client for KDE 4 (0.9.1git20110911-1.1)
NetworkManager-openvpn - NetworkManager VPN support for OpenVPN (0.9.0-1.2)
NetworkManager-openvpn-kde4 - NetworkManager client for KDE 4 (0.9.1git20110911-1.1)
libnm-glib-vpn1 - Convenience library for NetworkManager VPN plugins (0.9.0-7.1)