Gutsy Beta Kubuntu could not connect

[jerrylamos]

Gutsy Beta Kubuntu desktop icon says "no active device" and Konqueror says "could not connect". Following post attachments are dmesg and syslog; I can provide whatever info might be useful.

This is surprising since Gutsy Tribe 5 Kubuntu says "wired ethernet connection active eth0" and Konqueror connects to the internet fine. For contrast, dmesg and syslog are in following post attachments.

Likewise, Gutsy Beta Ubuntu comes up with "no active device" however issuing "sudo dhclient" establishes connection and Firefox connects to the internet.

Gutsy Beta Kubuntu issuing "sudo dhclient" does connect as in a following post attachment, however Konqueror is still unable to connect to the internet. No way to get to the internet, Beta is useless to me.

FYI this is a quad boot 1.2 gHz Celeron with Windoze, Edgy, Feisty, Gutsy Tribe 5, internet connection is Realtek RTL-8029(AS).

Installed Gutsy Beta had same problems as CD Live so I re-installed Tribe 5 which runs fine, except if I install the updates which cause the internet connection problem again. I don't have any reasonable way to tell which of the pending 560 (!) updates cause the problem.

Jerry

[jerrylamos (jerrylamos)]

dmesg from Gutsy Beta Kubuntu which won't connect to internet.

[jerrylamos (jerrylamos)]

syslog from Gutsy Beta Kubuntu which won't connect to internet

[jerrylamos (jerrylamos)]

dhclient report from Gutsy Beta Kubuntu showing wired connection but desktop network manager icon still shows no connection and Konqueror does not connect to the internet.

Do note Configure Network Connection does not show anything before dhclient. After dhclient it does show eth0, it's IP address, and enabled. I can ping the remote internet DNS just fine however Konqueror still cannot connect and desktop network manager still shows no active connection.

And as in previous posts, Gutsy Tribe 5 Kubuntu comes up running and connecting just fine.

Jerry

[jerrylamos (jerrylamos)]

dmesg from Gutsy Tribe 5 Konqueror which connects to the internet as booted up, compare to the dmesg from Beta which does not.

[jerrylamos (jerrylamos)]

syslog from Gutsy Tribe 5 Kubuntu which connects fine as booted up, for contrast to syslog from Gutsy Beta Kubuntu which Konqueror cannot connect.

[Frank Bob (frankbob)]

I have the same problem: Knetworkmanager says: No active device.

I have an integrated network card Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
and a atheros wifi card: Ethernet controller: Atheros Communications, Inc. AR5212/AR5213 Multiprotocol MAC/baseband processor (rev 01)

To get my wireless connection working, I disabled encryption and configured the connection using the Network Settings menu in KDE system settings. In gutsy Ubuntu (GNOME), networkmanager works fine on the computer.

I haven't tried earlier kubuntu alphas.

[Frank Bob (frankbob)]

I see now that the No active Device message is normal when there is no connection established.

Knetworkmanager still behaves very strangely.

I somehow managed to get the wireless network to appear when I right-click the knetworkmanager icon. I'm not sure how it happened. Maybe because I configured the wireless network manually using the kde config tool, then remove the ath0 lines in /etc/network/interfaces then kill and restart NetworkManager.

When I right-clicked the icon, I could see my wireless network. I was then able to setup the connection with WPA and it worked. I then restarted the computer to see if it would come up again.

When I restarted and logged in KDE again, the connection was not established. When I right-clicked the icon, I saw the 'Wired Devices' part but not the 'Wireless Devices' part. I then tried killing and restarting NetworkManager. The KDE Wallet popup came and asked me for the password. The wireless connection I had setup was then established (using WPA). However, when I right-click the icon, I STILL don't see the wireless device part and wouldn't be able to change wireless network.

If this problem is widespread, many kubuntu users will not be able to connect to wireless networks.

[Frank Bob (frankbob)]

Gahhhhh!!

I had Disabled wireless in knetworkmanager. Now it seems to work perfectly.

Problem between keyboard and chair.

[Luka Renko (lure)]

jerrylamos, policy for gutsy have changed and you need to have interfaces controlled by n-m completely commented out ot /etc/network/interfaces. From my system:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
#iface eth0 inet dhcp

Can you check/attach your interfaces file?

[jerrylamos (jerrylamos)]

Luka, my interfaces files are from the CD Live as downloaded from
http://cdimage.ubuntu.com/kubuntu/daily-live/current/gutsy-desktop-i386.iso
Since these are from the kubuntu site on CD Live, they are as provided by Kubuntu since I don't have the expertise to change CD Live. I didn't make any changes.

Kubuntu Gutsy Beta /etc/network/interfaces where the network does NOT work:

auto lo
iface lo inet loopback

(end of file)

Kubuntu Gutsy Tribe5 /etc/network/interfaces where the network does work fine:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp

(end of file)

The /etc/network/interfaces certainly look different. If I were able to change CD Live Beta I'd try at least using Tribe5's /etc/network/interfaces. Any info on any other changes that could have disabled the network on Beta?

Thanks, Jerry

[jerrylamos (jerrylamos)]

Release candidate Kubuntu cannot get the internet even with manual entry of IP address and gateway. See dmesg attached.

Tribe 5 Kubuntu accesses the internet just fine as booted up. Release candidate Ubuntu comes up with no connection. Manually selecting the Ubuntu network manager icon on the desktop and selecting wired network activates the connection and enables internet.

attempts at activating Kubuntu release candidate connection network manager icon fail because all the tabs are grey and inactive even when administrator mode is selected. The same hardware is running fine on Tribe 5.

Jerry

[jerrylamos (jerrylamos)]

Attached is /etc/network/interfaces after manually entering the correct IP and gateway. Still doesn't get the internet. Ping works fine, hardware is good, Tribe 5 Kubuntu is good, both Beta Kubuntu and Release Candidate Kubuntu fail to access internet.

Jerry

[mmaurer (mbfmaurer)]

After having upgraded from Kubuntu Feisty Fawn to the Gutsy beta Release and a few upgrades down the road, I had a very similar issue, and commenting out (i.e. adding a # to the start of the line) the lines starting with iface in my /etc/network/interfaces, seems to have solved it for me.
I think this is more or less the upgrading issue mentioned on http://www.ubuntu.com/getubuntu/releasenotes/710 under Network Manager.

Michael

[Jonathan Jesse (jjesse)]

Just curious as to where we stand with this bug? Is it somehting we can close out or does more work need to be done? Where does this stand with the hardy release?

Jonathan

[jerrylamos (jerrylamos)]

Let me download Kubuntu Hardy and give it a try. The downloads have been pretty busy.....
Jerry

[jerrylamos (jerrylamos)]

Hardy Release iso dated 0425 can get Konqueror running on internet manually, on every boot, so the problem as written can be resolved, however that is done.

Network Manager disables the internet adapter on boot up, after it is already running(!) because some (debian?) programmer decided that the Realtek wouldn't work (without checking to see if it was already active) and disables the adapter. The NM desktop icon has a red mark on it indicating disconnected. The Hardy Release shows "wired connection" when the cursor is placed over the icon, this can be selected and after a delay the connection is established just fine. Then Konqueror connects to internet O.K. In this bug as reported, Kubuntu NM had the "wired connection" selection "greyed out" so that manual intervention could not be done.

The underlying problem is a Network Manager failure see Bug #82927 on Ubuntu/Xubuntu/Kubuntu which requires manual intervention on every boot. So far as I can tell no NM developer is interested in solving the problem which of course does not exist on Dapper and Edgy which don't have Network Manager as default. Removing NM doesn't help because even when removed, NM is active during boot.

Anyway, I can get Konqueror running now.

Jerry

[Jonathan Jesse (jjesse)]

Jerry,

Sorry I wish I knew how to help you out with the other problems you are having with networkmanager. I will be marking the bug closed per your comments

Jonathan

[Jonathan Jesse (jjesse)]

actually i don't want to mark the bug, want to leave it up to Luka Renko who is assigned this bug.

Jonathan

[Jonathan Jesse (jjesse)]

Marking this as fix released based on the comments in the bug