Hi Zan - On Friday 22 December 2006 17:29, Zan Lynx wrote: > On Fri, 2006-12-22 at 15:17 -0700, Zan Lynx wrote: > [snip]
Thanks for the very detailed response! Indeed, part of the problem is in fact related to the bcm43xx wireless drivers. I don't really know why this *suddenly* happened, but the bcm drivers were in fact controlling my wireless and not ndiswrapper. Anyway, by rmmod'ing the bcm43xx drivers and re-modprob'ing ndiswrappper it all worked again (although eth2). I'll probably just leave well enough alone for now. If ndiswrapper wants to use eth2, I'll let it. I guess by that logic I can live with my main wired interface being eth1, too :-) I still don't understand why the Firewire IP interface suddenly appeared (never did before) - could very well be that I upgraded 'udev' while upgrading some of my bluez-* ebuilds... in fact, I just checked and it does indeed seem that udev was upgraded... that probably explains everything. Hmmm... serves me right for installing with 'ACCEPT_KEYWORDS="~amd64"' :-P -=R -- Rudolph Pienaar, M.Eng, D.Eng / email: [EMAIL PROTECTED] MGH/MIT/HMS Athinoula A. Martinos Center for Biomedical Imaging 149 (2301) 13th Street, Charlestown, MA 02129 USA _______________________________________________ LinuxR3000 mailing list [email protected] http://lists.pcxperience.com/cgi-bin/mailman/listinfo/linuxr3000 Wiki at http://prinsig.se/weekee/
