no network since last update

[Ernst Zlo]

Karmic alpha5
Since the last update, no networking possible.
Auto eth0 is missing in the network manager.

Sep 15 16:11:30 ernst-v5-desktop kernel: [ 8.267628] eth0: registered as PCnet/FAST III 79C973

but then no

Sep 15 15:59:35 ernst-v5-desktop kernel: [ 67.961511] eth0: link up, 100Mbps, full-duplex

following.

I think this is urgent ...

[Ernst Zlo (ernst-zlo)]

sorry for the 2nd posting, here's the complete protocol ...

[Santiago Otero (siryurian)]

I had the same problem. I think the problem is /etc/init.d/network-manager:
$ tail /etc/init.d/network-manager
 ;;
    *)
     echo
 echo "The script you are attempting to invoke has been converted to an Upstart" 1>&2
 echo "job, but $COMMAND is not supported for Upstart jobs." 1>&2
 exit 1
    esac
fi

s

After removing the ending 's', now the network works again.

[jcwinnie (jcwinnie)]

Otero's fix failed to work for me. I noted during the most recent update that init scripts was held back, so maybe I lack a proper update, which I will lack until can restore network connection.

Interestingly, the update seemed to leave the wireless info and only wiped out eth0

[J. (jose-manuel-rodriguez-moreno)]

I'm having the same problem after update,
but I don't have a trailing "s" to remove...

$ tail /etc/init.d/network-manager
reload)
    PID=$(status "$JOB" 2>/dev/null | awk '/[0-9]$/ { print $NF }')
    [ -z "$PID" ] || kill -HUP $PID
    ;;
*)
    echo
    echo "The script you are attempting to invoke has been converted to an Upstart" 1>&2
    echo "job, but $COMMAND is not supported for Upstart jobs." 1>&2
    exit 1
esac

[jcwinnie (jcwinnie)]

Did some more reading about Bug#430224, then, as root, tried:

  service network-manager start

which worked, although it chastised me by stating that I could have typed

  start network-manager

oh, well

[icb410 (ian-berke)]

This is the same as Bug #430405. Network manager does not start automatically anymore. I'm not familiar with the upstart system, but "sudo start network-manager" gets everything up and running. However, it doesn't work on the next boot. From the /etc/init/network-manager.conf file, it should start automatically if the hal and dbus services are started:

# network-manager - network connection manager
#
# The Network Manager daemon manages the system's network connections,
# automatically switching between the best available.

description "network connection manager"

start on (filesystem
          and started dbus
          and started hal)
stop on (stopping dbus
         or stopping hal)

expect fork
respawn

exec NetworkManager

dbus and hal are started through /etc/init.d/ scripts. Does the Upstart system recognize this? If not, I suppose we'll have to make do until someone converts them to start through Upstart.

[Brian Rogers (brian-rogers)]

It seems to be fixed now if you update, then restart.

[Ernst Zlo (ernst-zlo)]

jcwinnie's
sudo start network-manager
worked on Karmic alpha5 too

As this is 'my' bug#430071 and therefore the bug#430224 and bug#430405 are later I'm going an cry a little <snif>because they are the same as mine and not the other way round <snifsnifsnif> ;-)

As after a reboot with the newest updates the bug is gone, I go and try to change the status to fix released (and risk to be thrown out here to work with windows again <!!!!>)

[Ernst Zlo (ernst-zlo)]

Additional Information:

After a complete new install of Karmic alpha-5 on a new formated disk and no changes in any scripts:

404 updates -> partial Upgrade
  5 deleted
 49 new
434 updated
483 files downloaded
++++++++++++++++++++++++++++++
fsck
++++++++++++++++++++++++++++++
Everything's fine and smooth

So this bug is really gone.

[eris23 (jdkatz23)]

After deleting and recreating the wireless profile in nm-applet, my wireless now holds the connection.