Bug#402547: debian-installer: OldWorld beige G3 Macintosh bmac network interface disabled on reboot
On Dec 11, 2006, at 2:08 PM, Frans Pop wrote:
On Monday 11 December 2006 09:26, Rick Thomas wrote:
After installing etch from a daily netinst CD (2006/12/10 20:42
UTC) on
my beige G3 (OldWorld) PowerMac machine, the builtin ethernet
interface
is disabled.
[...]
There is a strange and possibly relevant thing in syslog
Dec 11 02:34:47 debian NetworkManager: <information>^Ieth1: Driver
'bmac' does not support carrier detection. ^IYou must switch to it
manually.
So during the installation everything worked OK?
Except for the mentioned problem with the bmac network interface,
everything was pretty much as expected[*]. I boot this machine with
the BootX bootloader. Up to now, etch has not worked with BootX.
This is the first time it has been possible to do that since debian
changed to >2.6.15 kernels. If we can get this bug fixed, I'll write
up the full procedure step-by-step for the wiki. If this can't get
fixed (or worked around) in time for etch release, it raises the
question of whether or not to say that OldWorld PowerMacs are fully
supported in this release. I'll leave that decision up to the
release manager -- I'm just raising the question.
[*] I had to use video=ofonly to get decent video. With sarge, I
used to be able to use video=atyfb... but with this kernel, that gave
a strange "almost readable" shimmery screen. I also had to
explicitly state "root=/dev/hde9" in the kernel parameters. This
again was new from sarge. In sarge, I don't need to make that explicit.
I'll do a full installation report if you think it would be useful.
I'm also planning to do an installation from the businesscard CD.
I'll do a full report on that if there's anything interesting.
In that case I have no idea what to do with this report, especially if
something like networkmanager is involved.
As the initial dhcp setup seems to go fine (which means that eth1 was
working at that point), I suspect that your problem is
networkmanager's
fault, or maybe a configuration issue.
Joey: does this impact your decision to install networkmanager by
default?
The initial DHCP during the installation went fine -- I was able to
retrieve lots of packages over the net during the "tasksel" part of
the installation. It's just after rebooting into the installed
system that the problem manifests. I'm not completely sure, but I
*think* from looking at the log files, that the interface comes up
and succeeds in doing DHCP early in the boot process, then is killed
later on, possibly by Networkmanager?
Would it be helpful to see what happens if I physically remove the
extra ethernet card? Or if I install using the extra card instead of
the bmac?
Rick
Reply to: