> I don't think this is a kernel issue.
> If you succeed configuring it "by hand" as outlined by Gustin below with
> `iwconfig` it is a network-manager problem, not a kernel/driver issue.
>   
I am rather strongly allergic to setting my wireless network to 
unauthenticated :-)  My wife's XP PC is nearby :-)
> Maybe it's even simpler: try hitting the WiFi-en/disable button
> (Fn+F5?!) or flick the Wifi kill-switch ;)
>   
Good try *grin*  It's marked 'on', its light is lit.
> It seems likely that you have a mixed system, which would also explain
> the NetworkManager vs. network-manager naming difference.
>   
Nope.  Vanilla 64studio 3b3, have changed no repos, have just run 
vanilla updates via Synaptic.
> Maybe that's the whole issue: Are you mixing different versions of the
> network-manager-applet and the network-manager service:
>
> what does
>   dpkg-query -l network-manager-gnome
>   
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: 
uppercase=bad)
||/ Name           Version        Description
+++-==============-==============-============================================
ii  network-manage 0.6.6-0ubuntu3 network management framework (GNOME 
frontend

> and
>   pkg-query -l network-manager
> say? Are they the same version? (0.7.1)
>   
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: 
uppercase=bad)
||/ Name           Version        Description
+++-==============-==============-============================================
ii  network-manage 0.6.6-0ubuntu5 network management framework daemon

Now you've got me a bit weirded out :-)  I wonder why 3b3 is packaged 
with NM 0.6.6? 
> Does `nm-tool` detect wlan0 as "Type: 802.11 WiFi" ?
>   
- Device: wlan0 
----------------------------------------------------------------
  NM Path:           /org/freedesktop/NetworkManager/Devices/wlan0
  Type:              Wired
  Driver:            ath5k
  Active:            no
  HW Address:        00:90:96:82:EA:85

  Capabilities:
    Supported:       yes

  Wired Settings
    Hardware Link:   yes

> Can you detect WiFi-networks by running `sudo iwlist wlan0 scan` ?
>   
Yes -- all of the nearby WAPs, including my own, are detected via the 
above command.
> Anyways. the at5k should be detected as ath0 not wlan0.
>   
Perhaps this is indicative of an NM version glitch.  But I don't 
understand why 3b3 standard repos have sent me an old NM.
> Is this a new install of 64studio, or did you upgrade from a previous
> System? It could be due to some relic udev rule: Do you have a file
>   /etc/udev/rules.d/70-persistent-net.rules
> (`ls /etc/udev/rules.d/*net*` , the name may be slightly different),
> there might be a clue in there.
>   
This is a vanilla install onto bare hardware, of 3b3.  The above file 
does exist, and contains:

# This file was automatically generated by the /lib/udev/write_net_rules
# program run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single line.

# PCI device 0x8086:0x103d (e100)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="00:08:0d:9f:18:f4", ATTR{type}=="1", KERNEL=="eth*", 
NAME="eth0"

# PCI device 0x168c:0x0013 (ath5k)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="00:90:96:82:ea:85", ATTR{type}=="1", KERNEL=="wlan*", 
NAME="wlan0"

> There's plenty of reasons why things could not work as expected; maybe
> you once used /etc/iftab with `ifrename` or set up mii-tools.. 
Nope.
> - or
> maybe the device is simply defect..
>   
The hardware, including wireless, was working well with Puppy Linux 
4.21, until I wiped it for 64studio.
> Anyways the issue of Network-manager detecting a WiFi interfaces as
> "wired" is unprecedented to my knowledge.
>
> If the iwconfig steps below work, you can be pragmatic and use
> wpa_supplicant and wpagui to /work around/ network-manager.
>   
I could.  But my primary purpose right now is to help debug 64studio.  I 
would like to use it as my primary platform, but on principle, I don't 
carry kludges around with me unless I have no choice.

J.E.B.

_______________________________________________
64studio-devel mailing list
[email protected]
http://lists.64studio.com/mailman/listinfo/64studio-devel

Reply via email to