From: Larry Finger <Larry.Finger@lwfinger.net>
To: Vignette consultant <vignette75@gmail.com>
Cc: wireless <linux-wireless@vger.kernel.org>
Subject: Re: RTL8187B wireless driver issue
Date: Mon, 14 Sep 2009 11:50:14 -0500 [thread overview]
Message-ID: <4AAE7446.3080407@lwfinger.net> (raw)
In-Reply-To: <3b0e19890909140905g4c6bfef3t38cd94a205d26f8@mail.gmail.com>
Vignette consultant wrote:
> Hi
>
> Attached files contain several logs of various commands. The log-1
> file is before running command and log-2 file is after running
> specific command.
>
> Here are commands that I give as soon as I log in. It's server edition.
>
> $ sudo ifconfig wlan0 up
> $ sudo iwconfig wlan0 ESSID linksys
> $ sudo dhclient wlan0 - results in no IP addr leased
Your wireless has not associated and has no communication, which is
why it cannot get an IP using DHCP.
A quick check with Google indicates that Ubuntu uses
/etc/network/interfaces to control the devices. Once that is correct,
you should be able to 'sudo /etc/init.d/networking restart' to start
the network. If the server is properly configured, the network should
start on boot.
BTW, the dmesg buffer is circular. All that usb monitoring output has
completely filled the buffer, and it contains no useful information.
next prev parent reply other threads:[~2009-09-14 16:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3b0e19890909122130l6c447e40r977f050e1a099794@mail.gmail.com>
2009-09-14 12:58 ` RTL8187B wireless driver issue Larry Finger
2009-09-14 14:19 ` Vignette consultant
2009-09-14 14:31 ` Larry Finger
2009-09-14 16:05 ` Vignette consultant
2009-09-14 16:50 ` Larry Finger [this message]
2009-09-14 17:56 ` Vignette consultant
2009-09-14 20:51 ` Hin-Tak Leung
[not found] ` <3b0e19890909141434t758a9b3dk2799623dfb19c6a6@mail.gmail.com>
2009-09-15 1:24 ` Hin-Tak Leung
2009-09-15 2:51 ` Vignette consultant
2009-09-15 4:04 ` Hin-Tak Leung
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=4AAE7446.3080407@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=vignette75@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).