From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from nf-out-0910.google.com ([64.233.182.191]:13558 "EHLO nf-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753178AbXKXSya (ORCPT ); Sat, 24 Nov 2007 13:54:30 -0500 Received: by nf-out-0910.google.com with SMTP id g13so182755nfb for ; Sat, 24 Nov 2007 10:54:29 -0800 (PST) Message-ID: <6995ca080711241054s4aeca1f9r2496a36f93a9db43@mail.gmail.com> (sfid-20071124_185435_193455_C717CDB2) Date: Sat, 24 Nov 2007 13:54:27 -0500 From: "Vadim Peretokin" To: "Pavel Roskin" Subject: Re: Belin FD7010 v7 Cc: linux-wireless@vger.kernel.org In-Reply-To: <1195879405.7449.62.camel@dv> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 References: <6995ca080711221239t2947765ds765fd933fce5de31@mail.gmail.com> <1195781993.11966.27.camel@dv> <6995ca080711221804w7310134aw8a5902e45aa09942@mail.gmail.com> <1195784707.11966.38.camel@dv> <6995ca080711230736n54330d30s96831a664d46df1c@mail.gmail.com> <1195879405.7449.62.camel@dv> Sender: linux-wireless-owner@vger.kernel.org List-ID: Yes, so I believe the problem was that that the rtl8180 driver didn't see, and claim the card. I believe the command I used to get the driver to see the card was "sudo echo -n " - I don't remember it exactly, but if you need it, I can dig it up. On Nov 23, 2007 11:43 PM, Pavel Roskin wrote: > On Fri, 2007-11-23 at 10:36 -0500, Vadim Peretokin wrote: > > That didn't quite work. iwconfig and ifconfig couldn't see the card, > > but lswh -C network showed my card. > > You probably mean lshw. I've never heard of it, but it looks like a > useful program. > > > It said "* - network UNCLAIMED", > > but it didn't say any logical adresses. > > It means there is no driver using the card. It you load either rtl8180 > or ndiswrapper, it won't be unclaimed. > > > I tried a host of adresses > > with "sudo ifconfig up", but nothing would work. > > You need to have a network interface first. If the driver doesn't > create the interface, then it's not working with your card. Use dmesg > to see kernel message for possible explanations. > > Once you have the interface (let's say it's wlan0), use "ifconfig wlan0 > up" to bring it up, "iwlist wlan0 scan" to see access points around you, > iwconfig to configure the wireless parameters, possible wpa_supplicant > for WPA authentication. Once the driver report association, use > ifconfig or dhclient to configure it. I'm sure there is more detailed > documentation somewhere. > > > I had a friend help me do some hacks involving telling the driver the > > adress of my card, and then iwconfig saw it - but for some reason Wicd > > couldn't see it (I'll try again when I get back home and install > > Network Manager again.). I have a log of what we did to get it > > "working", if it's any help. > > wicd is another interesting program I've never heard before. Perhaps > you should ask in a list for wicd users, just make sure to provide with > sufficient details. > > Anyway, wicd should not be required to connect to an AP. > > > And yes, the card does work if you install the net8185.inf driver in > > ndiswrapper and then use the -a command to link the card to the > > driver. I was just hoping that the card would work out of the box :) > > Well, not everything is working out of box, but we are getting there. > > -- > Regards, > Pavel Roskin >