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
> 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-manage
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 k
> 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
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
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?
-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 if
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 th
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
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.
i
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
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
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 sw
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
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
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
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 s
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 in
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
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 we
-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
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.
___
22 matches
Mail list logo