Wireless network problem after upgrade to 8.04

[Derek Broughton]

Paul Johnson wrote:

> On Thu, Jun 5, 2008 at 8:08 AM, Derek Broughton <news at pointerstop.ca>
> wrote:
>> Ken McLennan wrote:
>>
>>> G'day there Paul,
>> ...
>>>> So in the terminal again, make sure the network-manager is running
>>>>
>>>> # /etc/init.d/network-manager restart
>>>>
>>>     I don't have a 'network-manager' there, only a 'networking' entry.
>>> Is that the same?
>>
>> Ahem.  Paul, network-manager doesn't start out of init.d, it starts from
>> dbus:  "sudo /etc/dbus-1/event.d/25NetworkManager restart"
>>
> 
> Au contraire, mon brother! :)
> 
> At least for me, there is there is a script in /etc/init.d

OK, then, "the network-manager package no longer installs anything
in /etc/init.d". :-)  If you have "dlocate" installed, it would be
informative to run "dlocate /etc/init.d/network-manager" to see just where
yours came from.  Anyway, Ken probably doesn't have it, as it moved into
dbus a release or two back.

> I agree there is also a script in /etc/dbus-1.  I'm from Fedora-land,
> and I'm having a bit of trouble understanding the way Ubuntu manages
> services, but I am here to testify that I do
> 
> /etc/init.d/network-manager restart
> 
> when I have trouble, and it works!
> 
Well, back when I had a flaky network and was always messing with
network-manager, I used to do that too.  So it was a little annoying when
it disappeared.

>>>     If it's any use, this is the result of stopping & starting the
>>> init.d/networking command:
>> ...
>>> wmaster0: unknown hardware address type 801
>>> wmaster0: unknown hardware address type 801
>>> Listening on LPF/wlan0/00:19:d2:75:cf:ff
>>> Sending on   LPF/wlan0/00:19:d2:75:cf:ff
>>> Sending on   Socket/fallback
>>> Error for wireless request "Set Mode" (8B06) :
>>>     SET failed on device wlan0 ; Invalid argument.
>>
>> That looks rather serious.
>>
> It is not serious.  I have that iwl3945 device too and that always
> appears in the logs.  I was assured by the Fedora guys that it was no
> big deal.

OK, that's sort of good and bad - we know _that's_ not the problem, but we
still don't know what is :-)  Do you get that "wmaster0" error, too?
-- 
derek