Re: Weird wireless phantom device

[Rick Jones <rick activeservice co uk>]

--On Friday, October 02, 2009 18:25:59 -0700 Dan Williams <dcbw redhat com> wrote:

> On Fri, 2009-10-02 at 22:54 +0100, Rick Jones wrote:
> > I think your call on VBox was the right one. 
> > 
> > So now having installed 2.2 again, there's no problems with the WiFi
> > device. Bizarre bug, I'd never have made that connection.
> 
> It showed up because people got duplicate connections like this.
> VirtualBox seems to screw around with /sys in a broken attempt to
> virtualize it or something, which causes erroneous udev signals, which
> cause HAL to get the wrong information and duplicate the device.
> 
> What's in your /sys/class/net/ directory?

As follows:

eth0 -> ../../devices/pci0000:00/0000:00:1c.1/0000:04:00.0/net/eth0
lo -> ../../devices/virtual/net/lo
pan0 -> ../../devices/virtual/net/pan0
ra0 -> ../../devices/pci0000:00/0000:00:1c.3/0000:01:00.0/net/ra0
vboxnet0 -> ../../devices/virtual/net/vboxnet0

This is with VBox 2.2, I don't know what was there with 3.0. I've been running VBox 2 since I got this m/c nearly a year ago, and had no problems. It must have appeared with the update to 3 (or maybe a subsequent point-version update), I just didn't make the connection.

Cheers, Rick

> > --On Thursday, October 01, 2009 14:13:14 -0700 Dan Williams
> > <dcbw redhat com> wrote:
> > 
> > > On Thu, 2009-10-01 at 16:31 +0100, Rick Jones wrote:
> > > > I'm getting a repeated problem of my WiFi device showing up twice
> > in
> > > > NM. This isn't really an NM problem, but I'm hoping someone here
> > will
> > > > have an idea how to fix it.
> > > 
> > > NM 0.8?  Or NM 0.7?
> > > 
> > > For 0.7, run 'lshal' and look for device blocks with 'wlan0' in
> > them.
> > > If you see two, then it's a hal problem (though we've seen cases
> > where
> > > VirtualBox in it's misguided attempts to virtualize /sys completely
> > > screws over HAL).
> > > 
> > > For 0.8, what do you have in /sys/class/net/ ?
> > > 
> > > Dan
> > > 
> > > > The device appears twice in DBus, which is obviously the source of
> > the
> > > > problem, as NM is just listing what it finds. Both entries in DBus
> > are
> > > > identical, and point to the same device (which messes up NM as it
> > > > tries to open and connect on the same device twice).
> > > > 
> > > > The DBus node names are almost identical, the second entry just
> > has an
> > > > extra _0 at the end.
> > > > 
> > > > The output of lspci shows only one device:
> > > > 
> > > > 01:00.0 Network controller: RaLink RT2860
> > > >         Subsystem: RaLink Device 2790
> > > >         Flags: bus master, fast devsel, latency 0, IRQ 19
> > > >         Memory at f8000000 (32-bit, non-prefetchable) [size=64K]
> > > >         Capabilities: [40] Power Management version 3
> > > >         Capabilities: [50] Message Signalled Interrupts: Mask-
> > 64bit+
> > > > Queue=0/5 Enable-
> > > >         Capabilities: [70] Express Endpoint, MSI 00
> > > >         Capabilities: [100] Advanced Error Reporting <?>
> > > >         Kernel driver in use: rt2860
> > > >         Kernel modules: rt2860sta
> > > > 
> > > > Running "lsmod | grep 2860" shows only one user:
> > > > 
> > > > rt2860sta             513240  1 
> > > > 
> > > > Whether one or two devices show up is set from boot, and it seems
> > > > random when I re-boot what I'm going to get.
> > > > 
> > > > Anyone got any ideas?
> > > > 
> > > > TIA Rick 
> > > > _______________________________________________
> > > > NetworkManager-list mailing list
> > > > NetworkManager-list gnome org
> > > > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> > > 
> > > 
> > 
> > 
> 
>