Re: [64studio-devel] 3b3 wifi issue: AR5212/AR5213 detected as wire
Jonathan E. Brickman wrote: > >> Could you try to compile and test it on your machine? >> >> Try sth. like this: >> -8< >> sudo apt-get install build-essential fakeroot >> sudo apt-get build-dep network-manager >> cd /tmp >> wget http://rg42.org/_media/wiki/nm-0.7.1-debian.tgz >> tar xvzf nm-0.7.1-debian.tgz >> cd network-manager-0.7.1/ >> dpkg-buildpackage -rfakeroot >> cd .. >> sudo dpkg -i network-manager*deb >> -8< >> > I get: > > dpkg-checkbuilddeps: Unmet build dependencies: libdbus-glib-1-dev (>= > 0.75) ppp-dev libpolkit-dbus-dev uuid-dev libudev-dev > > I then tried: > > # sudo apt-get install libdbus-glib-1-dev ppp-dev libpolkit-dbus-dev > uuid-dev libudev-dev > Reading package lists... Done > Building dependency tree Reading state information... Done > libdbus-glib-1-dev is already the newest version. > E: Couldn't find package libudev-dev > > Not sure what to do next? > > J.E.B. You can check `apt-cache search udev` if you can find the -dev package. and put that name in debian/control of the nm's source instead of libudev-dev. You can also try to run `dpkg-buildpackage -d` which ignores missing dependancies; but the build may fail. Anyway, I'm just installing 64studio 3b3 on qemu; and I'll see if I can do a backport . It may take some time however.. Cheers, robin ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel
Re: [64studio-devel] 3b3 wifi issue: AR5212/AR5213 detected as wire
> Could you try to compile and test it on your machine? > > Try sth. like this: > -8< > sudo apt-get install build-essential fakeroot > sudo apt-get build-dep network-manager > cd /tmp > wget http://rg42.org/_media/wiki/nm-0.7.1-debian.tgz > tar xvzf nm-0.7.1-debian.tgz > cd network-manager-0.7.1/ > dpkg-buildpackage -rfakeroot > cd .. > sudo dpkg -i network-manager*deb > -8< > I get: dpkg-checkbuilddeps: Unmet build dependencies: libdbus-glib-1-dev (>= 0.75) ppp-dev libpolkit-dbus-dev uuid-dev libudev-dev I then tried: # sudo apt-get install libdbus-glib-1-dev ppp-dev libpolkit-dbus-dev uuid-dev libudev-dev Reading package lists... Done Building dependency tree Reading state information... Done libdbus-glib-1-dev is already the newest version. E: Couldn't find package libudev-dev Not sure what to do next? J.E.B. ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel
Re: [64studio-devel] 3b3 wifi issue: AR5212/AR5213 detected as wire
Hi Jonathan,
Since iwconfig, and iwlist work, this really looks like a bug with
network-manager.
64studio is based on Ubuntu Hardy, which is why you get version 0.6.6.
I've filed a ticket to backport nm-0.7.1 to 64studio
( http://trac.64studio.com/64studio/ticket/515 ) but it would be great
to know if that will solve the problem before we start backporting.
Could you try to compile and test it on your machine?
Try sth. like this:
-8<
sudo apt-get install build-essential fakeroot
sudo apt-get build-dep network-manager
cd /tmp
wget http://rg42.org/_media/wiki/nm-0.7.1-debian.tgz
tar xvzf nm-0.7.1-debian.tgz
cd network-manager-0.7.1/
dpkg-buildpackage -rfakeroot
cd ..
sudo dpkg -i network-manager*deb
-8<
The nm-0.7.1 on my server is taken from debian/squeeze. There may be
some version-conflicts in the build-dependacies.. if you run into
problems, be creative or get back to us..
robin
Jonathan E. Brickman wrote:
>
>> 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 VersionDescription
> +++-==-==-
>
> 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 VersionDescription
> +++-==-==-
>
> 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
Re: [64studio-devel] 3b3 wifi issue: AR5212/AR5213 detected as wire
> 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 VersionDescription
+++-==-==-
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 VersionDescription
+++-==-==-
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
64studio-devel@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-devel
Re: [64studio-devel] 3b3 wifi issue: AR5212/AR5213 detected as wire
Hi Jonathan, Jonathan E. Brickman wrote: > Well, Gustin, I'm not sure what distro you're advising me on, but it's not > 64studio 3b3 :-) There is no /etc/init.d/NetworkManager at all. I have not tried 64studio 3b3 yet, but on recent debian it's called /etc/init.d/network-manager Anyways `sudo killall NetworkManager` will have the same result. > I did try > disabling the new module as you suggested, but now the wifi hardware isn't > seen > in Network Manager at all. > > Perhaps I'm using the wrong kernel? 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. Maybe it's even simpler: try hitting the WiFi-en/disable button (Fn+F5?!) or flick the Wifi kill-switch ;) > The linux-rt package was automatically > removed by Synaptic during my first general update, and I am running > linux-2.6.29-1-multimedia-686. Should I put the linux-rt package back in, > going > backwards as needed? On 64studio "linux-rt" is only a 'dummy package' that installs the "latest stable kernel", which is linux-2.6.29-1-multimedia-686. If you have a mixed installation with Ubunutu repositories: Ubunutu also provides a package named "linux-rt", which is actually linux-rt_2.6.28.3.1_i386.deb It seems likely that you have a mixed system, which would also explain the NetworkManager vs. network-manager naming difference. 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 and pkg-query -l network-manager say? Are they the same version? (0.7.1) Does `nm-tool` detect wlan0 as "Type: 802.11 WiFi" ? Can you detect WiFi-networks by running `sudo iwlist wlan0 scan` ? Anyways. the at5k should be detected as ath0 not wlan0. 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. 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.. - or maybe the device is simply defect.. 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. > Or how about that new 2.6.31 rt kernel I keep hearing about? > > J.E.B. >> It looks like the newer ath5 driver is being used. ath5k /should/ work for the AR5212/AR5213 chipset. >> Try this: >> Temporarily change your AP to not require security (for testing only, >> you do not want this long term). Why not? Since most AP ship with password enabled by default, there's too few Free-WiFi access points in this world!! The security involved in that technology is not secure anyway. Just leave it open, share with your neighbors and use SSL when appropriate. >> sudo /etc/init.d/NetworkManger stop >> sudo ifdown wlan0 >> sudo ip link set wlan0 up >> sudo iwconfig wlan0 essid >> >> Now we need to check to see if the wifi device has actually connected to >> the AP. >> sudo iwconfig >> >> You should see something like this: >> >> wlan0 IEEE 802.11abgn ESSID:"myessid" >> Mode:Managed Frequency:5.18 GHz Access Point: 00:0B:6B:86:EB:AF >> Bit Rate=54 Mb/s Tx-Power=14 dBm >> Retry min limit:7 RTS thr:off Fragment thr=2352 B >> Power Management:off >> Link Quality=100/100 Signal level:-50 dBm Noise level=-92 dBm >> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 >> Tx excessive retries:0 Invalid misc:0 Missed beacon:0 >> >> Of course your Frequency and link quality will differ (in this example, >> my machine is connected to an 802.11a AP in the 5Ghz spectrum, and is on >> the desk next to the AP). >> >> If the Mac address after the "Access Point" matches your AP's wireless >> interface, we need to configure IPv4. >> >> Automatic method: >> Check to see if a dhcp client is running: >> ps axf | grep dhclient >> >> If you do not see one, then start one: >> sudo dhclient wlan0 >> >> Manual method: >> sudo ip addr add 192.168.0.20/24 dev wlan0 >> sudo ip route add default via 192.168.0.1 >> >> You will also need to configure a DNS server in /etc/resolv.conf >> >> Failing the above, we can disable the new ath5k driver to see if there >> is some weirdness with the newer driver: >> >> sudo echo "ath5k" >> /etc/modprobe.d/blacklist That won't work. "echo" is executed as root (due to sudo) bit the ">>" are still intepreted by the shell running as normal user. You want echo "ath5k" | sudo tee -a /etc/modprobe.d/blacklist >> Reboot and report. instead of blacklisting & re-booting, you can simply call sudo ifconfig wlan0 down sudo rmmod ath5k But I don't know w
Re: [64studio-devel] 3b3 wifi issue: AR5212/AR5213 detected as wire
Well, Gustin, I'm not sure what distro you're advising me on, but it's not 64studio 3b3 :-) There is no /etc/init.d/NetworkManager at all. I did try disabling the new module as you suggested, but now the wifi hardware isn't seen in Network Manager at all. Perhaps I'm using the wrong kernel? The linux-rt package was automatically removed by Synaptic during my first general update, and I am running linux-2.6.29-1-multimedia-686. Should I put the linux-rt package back in, going backwards as needed? Or how about that new 2.6.31 rt kernel I keep hearing about? J.E.B. It looks like the newer ath5 driver is being used. Try this: Temporarily change your AP to not require security (for testing only, you do not want this long term). sudo /etc/init.d/NetworkManger stop sudo ifdown wlan0 sudo ip link set wlan0 up sudo iwconfig wlan0 essid Now we need to check to see if the wifi device has actually connected to the AP. sudo iwconfig You should see something like this: wlan0 IEEE 802.11abgn ESSID:"myessid" Mode:Managed Frequency:5.18 GHz Access Point: 00:0B:6B:86:EB:AF Bit Rate=54 Mb/s Tx-Power=14 dBm Retry min limit:7 RTS thr:off Fragment thr=2352 B Power Management:off Link Quality=100/100 Signal level:-50 dBm Noise level=-92 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 Of course your Frequency and link quality will differ (in this example, my machine is connected to an 802.11a AP in the 5Ghz spectrum, and is on the desk next to the AP). If the Mac address after the "Access Point" matches your AP's wireless interface, we need to configure IPv4. Automatic method: Check to see if a dhcp client is running: ps axf | grep dhclient If you do not see one, then start one: sudo dhclient wlan0 Manual method: sudo ip addr add 192.168.0.20/24 dev wlan0 sudo ip route add default via 192.168.0.1 You will also need to configure a DNS server in /etc/resolv.conf Failing the above, we can disable the new ath5k driver to see if there is some weirdness with the newer driver: sudo echo "ath5k" >> /etc/modprobe.d/blacklist Reboot and report. To reverse these changes simply remove ath5k from the end of the /etc/modprobe.d/blacklist file. I have far more experience with the older ath_pci driver as I build my own APs (for fun and for profit) and the ath5k driver has issues acting as an AP. Hope this helps, -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFKwZipwRXgH3rKGfMRAhD9AJwPQRMlPoK5+dm42VnBArOqrnftLwCdGIPv 8YZYOgn0pg0wkI2ZUYSiTe4= =xjmL -END PGP SIGNATURE- ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel
Re: [64studio-devel] 3b3 wifi issue: AR5212/AR5213 detected as wire
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jonathan E. Brickman wrote: > Attached. > It looks like the newer ath5 driver is being used. Try this: Temporarily change your AP to not require security (for testing only, you do not want this long term). sudo /etc/init.d/NetworkManger stop sudo ifdown wlan0 sudo ip link set wlan0 up sudo iwconfig wlan0 essid Now we need to check to see if the wifi device has actually connected to the AP. sudo iwconfig You should see something like this: wlan0 IEEE 802.11abgn ESSID:"myessid" Mode:Managed Frequency:5.18 GHz Access Point: 00:0B:6B:86:EB:AF Bit Rate=54 Mb/s Tx-Power=14 dBm Retry min limit:7 RTS thr:off Fragment thr=2352 B Power Management:off Link Quality=100/100 Signal level:-50 dBm Noise level=-92 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 Of course your Frequency and link quality will differ (in this example, my machine is connected to an 802.11a AP in the 5Ghz spectrum, and is on the desk next to the AP). If the Mac address after the "Access Point" matches your AP's wireless interface, we need to configure IPv4. Automatic method: Check to see if a dhcp client is running: ps axf | grep dhclient If you do not see one, then start one: sudo dhclient wlan0 Manual method: sudo ip addr add 192.168.0.20/24 dev wlan0 sudo ip route add default via 192.168.0.1 You will also need to configure a DNS server in /etc/resolv.conf Failing the above, we can disable the new ath5k driver to see if there is some weirdness with the newer driver: sudo echo "ath5k" >> /etc/modprobe.d/blacklist Reboot and report. To reverse these changes simply remove ath5k from the end of the /etc/modprobe.d/blacklist file. I have far more experience with the older ath_pci driver as I build my own APs (for fun and for profit) and the ath5k driver has issues acting as an AP. Hope this helps, -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFKwZipwRXgH3rKGfMRAhD9AJwPQRMlPoK5+dm42VnBArOqrnftLwCdGIPv 8YZYOgn0pg0wkI2ZUYSiTe4= =xjmL -END PGP SIGNATURE- ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel
Re: [64studio-devel] 3b3 wifi issue: AR5212/AR5213 detected as wire
The standard source and binary repos do not have wifi-tools of the needed version. I tried lots of things using apt-get; here is the Synaptic synopsis: madwifi-modules-2.6.29-1-multimedia-686: Depends: madwifi-tools (>=1:0.9.4~rc2+dfsg-1) but 1:0.9.3+dfsg-3 is to be installed What is the next step? J.E.B. Hi, You can always install madwifi-tools from source. You will need the kernel headers and various -dev packages to compile though. Cheers. Patrick Shirkey 64 Studio Support Team On 09/29/2009 09:26 AM, Jonathan E. Brickman wrote: That is very interesting. I searched a lot, didn't come up with any firmware. But I did come up with an anomaly in Synaptic. I have madwifi-tools 1:0.9.3+dfsg-3 installed. My kernel is 2.6.29-1-multimedia-686. madwifi-modules-2.6.29-1-mul requires madwifi-tools 1:0.9.3+dfsg-4. But madwifi-tools 1:0.9.3+dfsg-4 doesn't exist in Synaptic. Anyone know what best I should do next? J.E.B. Not sure if this is a red herring... I think this is the same behaviour I got when I installed 3.0b3 (and 2.1 for that matter) before I installed the driver firmware for my chipset (iwl3945 in my case). After installing on the wire and restarting it was recognised correctly. On Tue, 2009-09-29 at 05:02 +1000, Patrick Shirkey wrote: Hi, Your ifconfig says it is a wlan0 device so it's quite strange that gnome says it is a wired 802.1x wired network. What messages do you get if you attempt to connect? Cheers. Patrick Shirkey 64 Studio Support Team On 09/28/2009 10:43 PM, Jonathan E. Brickman wrote: Below is a PNG; hope it makes it: 64studio 3b3 thinks that the wireless NIC is a wired NIC. J.E.B. -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jonathan E. Brickman wrote: Greetings. I have just installed 3.0b3 into my old Toshiba laptop. All is very well so far, except that the Atheros AR5212/AR5213 wifi is detected as a wired, not wireless, interface, and so the wireless network detection system isn't being engaged. What can I do to help? Can you be more specific? I have no idea what "detected as a wired" means. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkrAVg4ACgkQwRXgH3rKGfMUywCdEzPRPs6emUcBIZdII1DWJeqT afgAnR2ehR+kKF6NbglYMHEZUAM2HwXh =kZCs -END PGP SIGNATURE- ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel
Re: [64studio-devel] 3b3 wifi issue: AR5212/AR5213 detected as wire
Attached. J.E.B. Hi, Can you send us the output of lspci -vv Cheers. Patrick Shirkey 64 Studio Support Team On 09/29/2009 09:17 AM, Jonathan E. Brickman wrote: I can't get any list of wireless networks at all. When I tell it to connect as if it were a wired, the lower-left dot goes green, the swirl keeps on going for several minutes, and then it reports connected, even though I have not typed in a key. After it reports connected, the ifconfig looks like this: eth0 Link encap:Ethernet HWaddr 00:08:0d:9f:18:f4 inet addr:192.168.0.198 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::208:dff:fe9f:18f4/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:34336 errors:0 dropped:0 overruns:0 frame:0 TX packets:20792 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:47215866 (45.0 MB) TX bytes:1691300 (1.6 MB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:578 errors:0 dropped:0 overruns:0 frame:0 TX packets:578 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:29489 (28.7 KB) TX bytes:29489 (28.7 KB) wlan0 Link encap:Ethernet HWaddr 00:90:96:82:ea:85 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wmaster0 Link encap:UNSPEC HWaddr 00-90-96-82-EA-85-00-00-00-00-00-00-00-00-00-00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) J.E.B. Hi, Your ifconfig says it is a wlan0 device so it's quite strange that gnome says it is a wired 802.1x wired network. What messages do you get if you attempt to connect? Cheers. Patrick Shirkey 64 Studio Support Team On 09/28/2009 10:43 PM, Jonathan E. Brickman wrote: Below is a PNG; hope it makes it: 64studio 3b3 thinks that the wireless NIC is a wired NIC. J.E.B. -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jonathan E. Brickman wrote: Greetings. I have just installed 3.0b3 into my old Toshiba laptop. All is very well so far, except that the Atheros AR5212/AR5213 wifi is detected as a wired, not wireless, interface, and so the wireless network detection system isn't being engaged. What can I do to help? Can you be more specific? I have no idea what "detected as a wired" means. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkrAVg4ACgkQwRXgH3rKGfMUywCdEzPRPs6emUcBIZdII1DWJeqT afgAnR2ehR+kKF6NbglYMHEZUAM2HwXh =kZCs -END PGP SIGNATURE- ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel 00:00.0 Host bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02) Subsystem: Toshiba America Info Systems Unknown device 0001 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- (32-bit, prefetchable) Capabilities: 00:00.1 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02) Subsystem: Toshiba America Info Systems Unknown device 0001 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- 00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) Subsystem: Toshiba America Info Systems Unknown device 0002 Control: I/O- Mem- BusMaster-
Re: [64studio-devel] 3b3 wifi issue: AR5212/AR5213 detected as wire
Attached. "lsmod.grep.80211.txt" is the output of "ls | grep 80211". "iwconfig.txt" is the output of "iwconfig &> iwconfig.txt", because I noticed some lines coming through stderr. J.E.B. -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jonathan E. Brickman wrote: Certainly. ifconfig > ifconfig.txt is attached. I am much more interested in the output of the following two commands: lsmod |grep 80211 iwconfig -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkrBEIAACgkQwRXgH3rKGfOy+gCgjfwFPTM1X8WkWlEnK552mT/g TooAn0vin67zmjKSpY2JDCjeQBB+cE4y =289P -END PGP SIGNATURE- lono wireless extensions. eth0 no wireless extensions. wmaster0 no wireless extensions. wlan0 IEEE 802.11bg ESSID:"" Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated Tx-Power=27 dBm Retry min limit:7 RTS thr:off Fragment thr=2352 B Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 mac80211 136936 1 ath5k cfg80211 32756 2 ath5k,mac80211 ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel
Re: [64studio-devel] 3b3 wifi issue: AR5212/AR5213 detected as wire
Hi, You can always install madwifi-tools from source. You will need the kernel headers and various -dev packages to compile though. Cheers. Patrick Shirkey 64 Studio Support Team On 09/29/2009 09:26 AM, Jonathan E. Brickman wrote: That is very interesting. I searched a lot, didn't come up with any firmware. But I did come up with an anomaly in Synaptic. I have madwifi-tools 1:0.9.3+dfsg-3 installed. My kernel is 2.6.29-1-multimedia-686. madwifi-modules-2.6.29-1-mul requires madwifi-tools 1:0.9.3+dfsg-4. But madwifi-tools 1:0.9.3+dfsg-4 doesn't exist in Synaptic. Anyone know what best I should do next? J.E.B. Not sure if this is a red herring... I think this is the same behaviour I got when I installed 3.0b3 (and 2.1 for that matter) before I installed the driver firmware for my chipset (iwl3945 in my case). After installing on the wire and restarting it was recognised correctly. On Tue, 2009-09-29 at 05:02 +1000, Patrick Shirkey wrote: Hi, Your ifconfig says it is a wlan0 device so it's quite strange that gnome says it is a wired 802.1x wired network. What messages do you get if you attempt to connect? Cheers. Patrick Shirkey 64 Studio Support Team On 09/28/2009 10:43 PM, Jonathan E. Brickman wrote: Below is a PNG; hope it makes it: 64studio 3b3 thinks that the wireless NIC is a wired NIC. J.E.B. -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jonathan E. Brickman wrote: Greetings. I have just installed 3.0b3 into my old Toshiba laptop. All is very well so far, except that the Atheros AR5212/AR5213 wifi is detected as a wired, not wireless, interface, and so the wireless network detection system isn't being engaged. What can I do to help? Can you be more specific? I have no idea what "detected as a wired" means. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla -http://enigmail.mozdev.org/ iEYEARECAAYFAkrAVg4ACgkQwRXgH3rKGfMUywCdEzPRPs6emUcBIZdII1DWJeqT afgAnR2ehR+kKF6NbglYMHEZUAM2HwXh =kZCs -END PGP SIGNATURE- ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel
Re: [64studio-devel] 3b3 wifi issue: AR5212/AR5213 detected as wire
That is very interesting. I searched a lot, didn't come up with any firmware. But I did come up with an anomaly in Synaptic. I have madwifi-tools 1:0.9.3+dfsg-3 installed. My kernel is 2.6.29-1-multimedia-686. madwifi-modules-2.6.29-1-mul requires madwifi-tools 1:0.9.3+dfsg-4. But madwifi-tools 1:0.9.3+dfsg-4 doesn't exist in Synaptic. Anyone know what best I should do next? J.E.B. Not sure if this is a red herring... I think this is the same behaviour I got when I installed 3.0b3 (and 2.1 for that matter) before I installed the driver firmware for my chipset (iwl3945 in my case). After installing on the wire and restarting it was recognised correctly. On Tue, 2009-09-29 at 05:02 +1000, Patrick Shirkey wrote: Hi, Your ifconfig says it is a wlan0 device so it's quite strange that gnome says it is a wired 802.1x wired network. What messages do you get if you attempt to connect? Cheers. Patrick Shirkey 64 Studio Support Team On 09/28/2009 10:43 PM, Jonathan E. Brickman wrote: Below is a PNG; hope it makes it: 64studio 3b3 thinks that the wireless NIC is a wired NIC. J.E.B. -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jonathan E. Brickman wrote: Greetings. I have just installed 3.0b3 into my old Toshiba laptop. All is very well so far, except that the Atheros AR5212/AR5213 wifi is detected as a wired, not wireless, interface, and so the wireless network detection system isn't being engaged. What can I do to help? Can you be more specific? I have no idea what "detected as a wired" means. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkrAVg4ACgkQwRXgH3rKGfMUywCdEzPRPs6emUcBIZdII1DWJeqT afgAnR2ehR+kKF6NbglYMHEZUAM2HwXh =kZCs -END PGP SIGNATURE- ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel
Re: [64studio-devel] 3b3 wifi issue: AR5212/AR5213 detected as wire
Hi, Can you send us the output of lspci -vv Cheers. Patrick Shirkey 64 Studio Support Team On 09/29/2009 09:17 AM, Jonathan E. Brickman wrote: I can't get any list of wireless networks at all. When I tell it to connect as if it were a wired, the lower-left dot goes green, the swirl keeps on going for several minutes, and then it reports connected, even though I have not typed in a key. After it reports connected, the ifconfig looks like this: eth0 Link encap:Ethernet HWaddr 00:08:0d:9f:18:f4 inet addr:192.168.0.198 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::208:dff:fe9f:18f4/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:34336 errors:0 dropped:0 overruns:0 frame:0 TX packets:20792 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:47215866 (45.0 MB) TX bytes:1691300 (1.6 MB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:578 errors:0 dropped:0 overruns:0 frame:0 TX packets:578 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:29489 (28.7 KB) TX bytes:29489 (28.7 KB) wlan0 Link encap:Ethernet HWaddr 00:90:96:82:ea:85 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wmaster0 Link encap:UNSPEC HWaddr 00-90-96-82-EA-85-00-00-00-00-00-00-00-00-00-00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) J.E.B. Hi, Your ifconfig says it is a wlan0 device so it's quite strange that gnome says it is a wired 802.1x wired network. What messages do you get if you attempt to connect? Cheers. Patrick Shirkey 64 Studio Support Team On 09/28/2009 10:43 PM, Jonathan E. Brickman wrote: Below is a PNG; hope it makes it: 64studio 3b3 thinks that the wireless NIC is a wired NIC. J.E.B. -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jonathan E. Brickman wrote: Greetings. I have just installed 3.0b3 into my old Toshiba laptop. All is very well so far, except that the Atheros AR5212/AR5213 wifi is detected as a wired, not wireless, interface, and so the wireless network detection system isn't being engaged. What can I do to help? Can you be more specific? I have no idea what "detected as a wired" means. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkrAVg4ACgkQwRXgH3rKGfMUywCdEzPRPs6emUcBIZdII1DWJeqT afgAnR2ehR+kKF6NbglYMHEZUAM2HwXh =kZCs -END PGP SIGNATURE- ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel
Re: [64studio-devel] 3b3 wifi issue: AR5212/AR5213 detected as wire
I can't get any list of wireless networks at all. When I tell it to connect as if it were a wired, the lower-left dot goes green, the swirl keeps on going for several minutes, and then it reports connected, even though I have not typed in a key. After it reports connected, the ifconfig looks like this: eth0 Link encap:Ethernet HWaddr 00:08:0d:9f:18:f4 inet addr:192.168.0.198 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::208:dff:fe9f:18f4/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:34336 errors:0 dropped:0 overruns:0 frame:0 TX packets:20792 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:47215866 (45.0 MB) TX bytes:1691300 (1.6 MB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:578 errors:0 dropped:0 overruns:0 frame:0 TX packets:578 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:29489 (28.7 KB) TX bytes:29489 (28.7 KB) wlan0 Link encap:Ethernet HWaddr 00:90:96:82:ea:85 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wmaster0 Link encap:UNSPEC HWaddr 00-90-96-82-EA-85-00-00-00-00-00-00-00-00-00-00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) J.E.B. Hi, Your ifconfig says it is a wlan0 device so it's quite strange that gnome says it is a wired 802.1x wired network. What messages do you get if you attempt to connect? Cheers. Patrick Shirkey 64 Studio Support Team On 09/28/2009 10:43 PM, Jonathan E. Brickman wrote: Below is a PNG; hope it makes it: 64studio 3b3 thinks that the wireless NIC is a wired NIC. J.E.B. -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jonathan E. Brickman wrote: Greetings. I have just installed 3.0b3 into my old Toshiba laptop. All is very well so far, except that the Atheros AR5212/AR5213 wifi is detected as a wired, not wireless, interface, and so the wireless network detection system isn't being engaged. What can I do to help? Can you be more specific? I have no idea what "detected as a wired" means. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkrAVg4ACgkQwRXgH3rKGfMUywCdEzPRPs6emUcBIZdII1DWJeqT afgAnR2ehR+kKF6NbglYMHEZUAM2HwXh =kZCs -END PGP SIGNATURE- ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel
Re: [64studio-devel] 3b3 wifi issue: AR5212/AR5213 detected as wire
Not sure if this is a red herring... I think this is the same behaviour I got when I installed 3.0b3 (and 2.1 for that matter) before I installed the driver firmware for my chipset (iwl3945 in my case). After installing on the wire and restarting it was recognised correctly. On Tue, 2009-09-29 at 05:02 +1000, Patrick Shirkey wrote: > Hi, > > Your ifconfig says it is a wlan0 device so it's quite strange that > gnome says it is a wired 802.1x wired network. > > What messages do you get if you attempt to connect? > > > Cheers. > > Patrick Shirkey > 64 Studio Support Team > > On 09/28/2009 10:43 PM, Jonathan E. Brickman wrote: > > Below is a PNG; hope it makes it: > > > > > > > 64studio 3b3 thinks that the wireless NIC is a wired NIC. > > > > > > J.E.B. > > > > > > > -BEGIN PGP SIGNED MESSAGE- > > > > Hash: SHA1 > > > > > > > > Jonathan E. Brickman wrote: > > > > > > > > > Greetings. I have just installed 3.0b3 into my old Toshiba laptop. > > > > > All > > > > > is very well so far, except that the Atheros AR5212/AR5213 wifi is > > > > > detected as a wired, not wireless, interface, and so the wireless > > > > > network detection system isn't being engaged. What can I do to help? > > > > > > > > > > > > > > Can you be more specific? I have no idea what "detected as a wired" > > > > means. > > > > -BEGIN PGP SIGNATURE- > > > > Version: GnuPG v1.4.9 (GNU/Linux) > > > > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > > > > > > > iEYEARECAAYFAkrAVg4ACgkQwRXgH3rKGfMUywCdEzPRPs6emUcBIZdII1DWJeqT > > > > afgAnR2ehR+kKF6NbglYMHEZUAM2HwXh > > > > =kZCs > > > > -END PGP SIGNATURE- > > > > ___ > > > > 64studio-devel mailing list > > > > 64studio-devel@lists.64studio.com > > > > http://lists.64studio.com/mailman/listinfo/64studio-devel > > > > > > > > > > > > > > > > > ___ > > 64studio-devel mailing list > > 64studio-devel@lists.64studio.com > > http://lists.64studio.com/mailman/listinfo/64studio-devel > > > ___ > 64studio-devel mailing list > 64studio-devel@lists.64studio.com > http://lists.64studio.com/mailman/listinfo/64studio-devel ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel
Re: [64studio-devel] 3b3 wifi issue: AR5212/AR5213 detected as wire
Hi, Your ifconfig says it is a wlan0 device so it's quite strange that gnome says it is a wired 802.1x wired network. What messages do you get if you attempt to connect? Cheers. Patrick Shirkey 64 Studio Support Team On 09/28/2009 10:43 PM, Jonathan E. Brickman wrote: Below is a PNG; hope it makes it: 64studio 3b3 thinks that the wireless NIC is a wired NIC. J.E.B. -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jonathan E. Brickman wrote: Greetings. I have just installed 3.0b3 into my old Toshiba laptop. All is very well so far, except that the Atheros AR5212/AR5213 wifi is detected as a wired, not wireless, interface, and so the wireless network detection system isn't being engaged. What can I do to help? Can you be more specific? I have no idea what "detected as a wired" means. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkrAVg4ACgkQwRXgH3rKGfMUywCdEzPRPs6emUcBIZdII1DWJeqT afgAnR2ehR+kKF6NbglYMHEZUAM2HwXh =kZCs -END PGP SIGNATURE- ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel
Re: [64studio-devel] 3b3 wifi issue: AR5212/AR5213 detected as wire
Below is a PNG; hope it makes it: 64studio 3b3 thinks that the wireless NIC is a wired NIC. J.E.B. -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jonathan E. Brickman wrote: Greetings. I have just installed 3.0b3 into my old Toshiba laptop. All is very well so far, except that the Atheros AR5212/AR5213 wifi is detected as a wired, not wireless, interface, and so the wireless network detection system isn't being engaged. What can I do to help? Can you be more specific? I have no idea what "detected as a wired" means. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkrAVg4ACgkQwRXgH3rKGfMUywCdEzPRPs6emUcBIZdII1DWJeqT afgAnR2ehR+kKF6NbglYMHEZUAM2HwXh =kZCs -END PGP SIGNATURE- ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel
Re: [64studio-devel] 3b3 wifi issue: AR5212/AR5213 detected as wire
Certainly. ifconfig > ifconfig.txt is attached. J.E.B. Hi, Can you send us the output of the following command run in the terminal please? /sbin/ifconfig Cheers. Patrick Shirkey 64 Studio Support Team On 09/28/2009 10:51 AM, Jonathan E. Brickman wrote: Greetings. I have just installed 3.0b3 into my old Toshiba laptop. All is very well so far, except that the Atheros AR5212/AR5213 wifi is detected as a wired, not wireless, interface, and so the wireless network detection system isn't being engaged. What can I do to help? J.E.B. ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel eth0 Link encap:Ethernet HWaddr 00:08:0d:9f:18:f4 inet addr:192.168.0.198 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::208:dff:fe9f:18f4/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:968 errors:0 dropped:0 overruns:0 frame:0 TX packets:848 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1174894 (1.1 MB) TX bytes:77943 (76.1 KB) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:204 errors:0 dropped:0 overruns:0 frame:0 TX packets:204 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:10789 (10.5 KB) TX bytes:10789 (10.5 KB) wlan0 Link encap:Ethernet HWaddr 00:90:96:82:ea:85 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wmaster0 Link encap:UNSPEC HWaddr 00-90-96-82-EA-85-00-00-00-00-00-00-00-00-00-00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel
Re: [64studio-devel] 3b3 wifi issue: AR5212/AR5213 detected as wire
64studio 3b3 thinks that the wireless NIC is a wired NIC. J.E.B. -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jonathan E. Brickman wrote: Greetings. I have just installed 3.0b3 into my old Toshiba laptop. All is very well so far, except that the Atheros AR5212/AR5213 wifi is detected as a wired, not wireless, interface, and so the wireless network detection system isn't being engaged. What can I do to help? Can you be more specific? I have no idea what "detected as a wired" means. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkrAVg4ACgkQwRXgH3rKGfMUywCdEzPRPs6emUcBIZdII1DWJeqT afgAnR2ehR+kKF6NbglYMHEZUAM2HwXh =kZCs -END PGP SIGNATURE- ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel
Re: [64studio-devel] 3b3 wifi issue: AR5212/AR5213 detected as wire
Hi, Can you send us the output of the following command run in the terminal please? /sbin/ifconfig Cheers. Patrick Shirkey 64 Studio Support Team On 09/28/2009 10:51 AM, Jonathan E. Brickman wrote: > Greetings. I have just installed 3.0b3 into my old Toshiba laptop. All > is very well so far, except that the Atheros AR5212/AR5213 wifi is > detected as a wired, not wireless, interface, and so the wireless > network detection system isn't being engaged. What can I do to help? > > J.E.B. > > ___ > 64studio-devel mailing list > 64studio-devel@lists.64studio.com > http://lists.64studio.com/mailman/listinfo/64studio-devel > ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel
Re: [64studio-devel] 3b3 wifi issue: AR5212/AR5213 detected as wire
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jonathan E. Brickman wrote: > Greetings. I have just installed 3.0b3 into my old Toshiba laptop. All > is very well so far, except that the Atheros AR5212/AR5213 wifi is > detected as a wired, not wireless, interface, and so the wireless > network detection system isn't being engaged. What can I do to help? > Can you be more specific? I have no idea what "detected as a wired" means. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkrAVg4ACgkQwRXgH3rKGfMUywCdEzPRPs6emUcBIZdII1DWJeqT afgAnR2ehR+kKF6NbglYMHEZUAM2HwXh =kZCs -END PGP SIGNATURE- ___ 64studio-devel mailing list 64studio-devel@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-devel
