RE: My wireless card activity could notberecognizedbyNetworkManager

[Dan Williams <dcbw redhat com>]

On Tue, 2007-02-20 at 10:10 -0800, Jihua Cheng wrote:
> Dan,
> 
> Could you tell me
> 1) How to find the HAL's version?
> 2) How to know if HAL detects my driver?

If you're on an rpm-based distribution:

rpm -qv hal

If hal detects your driver, it will show something like the following
for your wireless network device when you run 'lshal':

udi = '/org/freedesktop/Hal/devices/net_00_16_xx_xx_xx_xx'
  info.udi = '/org/freedesktop/Hal/devices/net_00_16_xx_xx_xx_xx'  (string)
  linux.subsystem = 'net'  (string)
  linux.hotplug_type = 2  (0x2)  (int)
  net.80211.mac_address = xxxxxxxxxx  (0x16xxxxxxxx)  (uint64)
  info.product = 'WLAN Interface'  (string)
  net.arp_proto_hw_id = 1  (0x1)  (int)
  net.linux.ifindex = 3  (0x3)  (int)
  net.address = '00:16:xx:xx:xx:xx'  (string)
  net.interface = 'eth0'  (string)
  net.physical_device = '/org/freedesktop/Hal/devices/pci_8086_4220'  (string)
  info.capabilities = {'net', 'net.80211'} (string list)
  info.category = 'net.80211'  (string)
  info.parent = '/org/freedesktop/Hal/devices/pci_8086_4220'  (string)
  linux.sysfs_path = '/sys/class/net/eth0'  (string)


Dan

> Thanks a lot!
> 
> Jihua
> 
> -----Original Message-----
> From: Dan Williams [mailto:dcbw redhat com] 
> Sent: Saturday, February 17, 2007 5:58 AM
> To: Jihua Cheng
> Cc: networkmanager-list gnome org
> Subject: RE: My wireless card activity could
> notberecognizedbyNetworkManager
> 
> On Fri, 2007-02-16 at 12:28 -0800, Jihua Cheng wrote:
> > Dan,
> > 
> > I added the SET_NETDEV_DEV. Network Manager still does not detect my
> > wireless card.
> > 
> > I noticed that when I right click mouse on NetworkManager icon, only
> > Gray "Wired Network" showed up. I disconnect Ethernet connection.
> Should
> > Network manager show "Wireless Network"? Could some parameter setting
> is
> > not properly setup for NetworkManager?
> 
> This is really an issue between the driver and HAL.  If you get it to
> show up in HAL, then it will show up in NetworkManager (and then we can
> see if your driver does WEXT right :).  In any case, what version of HAL
> do you have?  Then we can track down exactly how HAL is looking for
> wireless.
> 
> Dan
> 
> > Thanks!
> > 
> > Jihua
> > 
> > -----Original Message-----
> > From: Dan Williams [mailto:dcbw redhat com] 
> > Sent: Friday, February 16, 2007 11:45 AM
> > To: Jihua Cheng
> > Cc: networkmanager-list gnome org
> > Subject: RE: My wireless card activity could
> > notberecognizedbyNetworkManager
> > 
> > On Fri, 2007-02-16 at 11:25 -0800, Jihua Cheng wrote:
> > > Dan,
> > > Thanks a lot.
> > > 
> > > Please find the answer bellow.
> > > 
> > > - Do you call SET_NETDEV_DEV in your driver?
> > > My driver does not call SET_NETDEV_DEV.
> > 
> > Do this then, that is definitely required for 2.6 drivers.  It won't
> > break hard if you don't have it, but you need it.  It makes a link
> > between your hardware device and the class device in sysfs and allows
> > HAL to determine the parent/child relationship.
> > 
> > Dan
> > 
> > > 
> > > - Does it show up in /proc/net/wireless?
> > > Yes. "cat /proc/net/wireless" shows
> > > Inter-| sta-|   Quality        |   Discarded packets               |
> > > Missed | WE
> > >  face | tus | link level noise |  nwid  crypt   frag  retry   misc |
> > > beacon | 20
> > >   eth1: 0001    0     0   160        0      0 6128224     27     86
> > > 0
> > > 
> > > - What is the contents of /sys/class/net/ethX ? (where ethX should
> be
> > > replaced with the interface name of the wireless device that is
> > created
> > > when you load your driver)
> > > "ls /sys/class/net/eth1" shows
> > > address
> > > addr_len
> > > broadcast
> > > carrier
> > > dormant
> > > features
> > > flags
> > > ifindex
> > > iflink
> > > link_mode
> > > mtu
> > > operstate
> > > statistics
> > > subsystem
> > > tx_queue_len
> > > type
> > > uevent
> > > weight
> > > wireles
> > > 
> > > 
> > > - What is the contents of /sys/class/net/ethX/wireless? (same as
> > above,
> > > replace ethX as appropriate)
> > > "ls /sys/class/net/eth1/wireless " shows
> > > beacon
> > > crypt
> > > fragment
> > > level
> > > link
> > > misc
> > > noise
> > > nwid
> > > retries
> > > status
> > > 
> > > - Do you implement the get_wireless_stats function in your
> > > iw_handler_def structure?  That's what actually allows the system to
> > > create the /sys/class/net/ethX/wireless directory for you.
> > > get_wireless_stats is implemented.
> > > 
> > > Regards,
> > > 
> > > Charles
> > > 
> > > 
> > > -----Original Message-----
> > > From: Dan Williams [mailto:dcbw redhat com] 
> > > Sent: Friday, February 16, 2007 10:47 AM
> > > To: Jihua Cheng
> > > Cc: networkmanager-list gnome org
> > > Subject: RE: My wireless card activity could not
> > > berecognizedbyNetworkManager
> > > 
> > > On Fri, 2007-02-16 at 10:26 -0800, Jihua Cheng wrote:
> > > /> Dan,
> > > > Thanks a lot!
> > > > 
> > > > The card model is SD wireless card, attached into PCI card. PCI
> card
> > > > provides the bridge.
> > > > 
> > > > I wrote this driver. I can insmod my driver and it works well with
> > > > wireless tools(iwconfig, iwlist, etc) and network command ( for
> > > example,
> > > > ping). I could find my driver loaded properly, by using lsmod.
> > > > 
> > > > You mentioned "HAL doesn't appear to know about any wireless
> > > > interfaces". How can I make HAL know my wireless interface? Some
> > > system
> > > > function call?
> > > 
> > > Make sure it does the right thing with sysfs.
> > > 
> > > - Do you call SET_NETDEV_DEV in your driver?
> > > 
> > > - Does it show up in /proc/net/wireless?
> > > 
> > > - What is the contents of /sys/class/net/ethX ? (where ethX should
> be
> > > replaced with the interface name of the wireless device that is
> > created
> > > when you load your driver)
> > > 
> > > - What is the contents of /sys/class/net/ethX/wireless? (same as
> > above,
> > > replace ethX as appropriate)
> > > 
> > > - Do you implement the get_wireless_stats function in your
> > > iw_handler_def structure?  That's what actually allows the system to
> > > create the /sys/class/net/ethX/wireless directory for you.
> > > 
> > > Dan
> > > 
> > > 
> > 
>