From: Pavel Roskin <proski@gnu.org>
To: Vadim Peretokin <vperetokin@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Belin FD7010 v7
Date: Fri, 23 Nov 2007 23:43:25 -0500 [thread overview]
Message-ID: <1195879405.7449.62.camel@dv> (raw)
In-Reply-To: <6995ca080711230736n54330d30s96831a664d46df1c@mail.gmail.com>
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 <adress> 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
next prev parent reply other threads:[~2007-11-24 4:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-22 20:39 Belin FD7010 v7 Vadim Peretokin
2007-11-23 1:39 ` Pavel Roskin
2007-11-23 2:04 ` Vadim Peretokin
2007-11-23 2:25 ` Pavel Roskin
2007-11-23 15:36 ` Vadim Peretokin
2007-11-24 4:43 ` Pavel Roskin [this message]
2007-11-24 18:54 ` Vadim Peretokin
2007-11-24 19:33 ` Pavel Roskin
2007-11-24 20:46 ` Vadim Peretokin
2007-11-25 1:42 ` Pavel Roskin
2007-11-25 17:30 ` Vadim Peretokin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1195879405.7449.62.camel@dv \
--to=proski@gnu.org \
--cc=linux-wireless@vger.kernel.org \
--cc=vperetokin@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).