Package: network-manager
Version: 0.6.4-6
Followup-For: Bug #403112
OldWorld PowerMac beige G3 tower. Bog-standard configuration. No additional
devices above those on the motherboard.
In particular, the only ethernet interface is the "bmac" that comes standard on
lots of OldWorld PowerMac machines.
First I installed (20070228-2 "Netinst") using the default configuration
("Desktop" and "standard" tasks checked in
tasksel). The install went fine. No difficulties with network access.
Network info came from dhcp.
After the reboot, however, network access was not available. Poking around in
the log files brought up this snippit:
===================
Mar 1 02:48:11 debian NetworkManager: <information>^Istarting...
Mar 1 02:48:11 debian NetworkManager: <information>^Ieth0: Driver 'bmac' does
not support carrier detection. ^IYou
must switch to it manually.
Mar 1 02:48:11 debian NetworkManager: <information>^Inm_device_init(): waiting
for device's worker thread to start
Mar 1 02:48:11 debian NetworkManager: <information>^Inm_device_init():
device's worker thread started, continuing.
Mar 1 02:48:11 debian NetworkManager: <information>^INow managing wired
Ethernet (802.3) device 'eth0'.
Mar 1 02:48:11 debian NetworkManager: <information>^IDeactivating device eth0.
===================
So I did "aptitude remove network-manager-gnome" and rebooted. After the
reboot, the network (via the bmac) was
available again.
Many OldWorld PowerMac machines have bmac interfaces as their only way of
geting to the network. If network-manager
was smart enough to see that the machine has only one network interface, and
not deactivate it out-of-hand (regardless
of how braindead the interface may seem to be), then this problem would be much
less severe.
As it is, however, this is a very serious problem. I don't think it's a good
idea to release Etch without solving this
one way or another. It renders a whole class of machines unusable.
For machines with two or more network interfaces (a bmac and one or more
others) the workaround of not deactivating the
only interface would not work. But presumably, people with such machines would
be sophisticated enough to deal with
the problem some other way.
Rick
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: powerpc (ppc)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-powerpc
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages network-manager depends on:
ii adduser 3.102 Add and remove users and groups
ii dbus 1.0.2-1 simple interprocess messaging syst
pn dhcdbd <none> (no description available)
ii hal 0.5.8.1-6.1 Hardware Abstraction Layer
ii ifupdown 0.6.8 high level tools to configure netw
pn iproute <none> (no description available)
pn iputils-arping <none> (no description available)
ii libc6 2.3.6.ds1-11 GNU C Library: Shared libraries
ii libdbus-1-3 1.0.2-1 simple interprocess messaging syst
ii libdbus-glib-1-2 0.71-3 simple interprocess messaging syst
ii libgcrypt11 1.2.3-2 LGPL Crypto library - runtime libr
ii libglib2.0-0 2.12.4-2 The GLib library of C routines
ii libgpg-error0 1.4-1 library for common error values an
ii libhal1 0.5.8.1-6.1 Hardware Abstraction Layer - share
pn libiw28 <none> (no description available)
pn libnl1-pre6 <none> (no description available)
pn libnm-util0 <none> (no description available)
ii lsb-base 3.1-23 Linux Standard Base 3.1 init scrip
pn wpasupplicant <none> (no description available)
network-manager recommends no packages.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
