[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: wireless is disabled



On Fri, Feb 24, 2012 at 7:22 PM, Keith McKenzie <km3952@gmail.com> wrote:
> A good book for learning base linux commands is Linux in a Nutshell / O'Reilly.

Thanks, http://shop.oreilly.com/product/9780596154493.do
is this book?

> A good 'book' for Linux in general is 'RUTE', & can be found here :-
> http://freecode.com/projects/rute
>
> On 24/02/2012, lina <lina.lastname@gmail.com> wrote:
>> On Fri, Feb 24, 2012 at 6:26 AM, Florian Kulzer
>> <debian-lists@florian-kulzer.eu> wrote:
>>> On Fri, Feb 24, 2012 at 00:36:02 +0800, lina wrote:
>>>> Supplementary Information:
>>>>
>>>> # nm-tool
>>>>
>>>> NetworkManager Tool
>>>>
>>>> State: disconnected
>>>>
>>>> - Device: eth0
>>>> -----------------------------------------------------------------
>>>>   Type:              Wired
>>>>   Driver:            tg3
>>>>   State:             unmanaged
>>>
>>>  [snip: eth0 looks normal to me for an unmanaged device]
>>>
>>>> - Device: wlan0
>>>> ----------------------------------------------------------------
>>>>   Type:              802.11 WiFi
>>>>   Driver:            b43
>>>>   State:             unavailable
>>>>   Default:           no
>>>>   HW Address:        E0:F8:47:0A:B0:D8
>>>>
>>>>   Capabilities:
>>>>
>>>>   Wireless Properties
>>>>     WEP Encryption:  yes
>>>>     WPA Encryption:  yes
>>>>     WPA2 Encryption: yes
>>>>
>>>>   Wireless Access Points
>>>
>>> It should be possible to change the line "State: unavailable" to "State:
>>> disconnected" by running:
>>>
>>>  nmcli nm wifi on
>>
>> Thanks, this works.
>>
>> How can I know enough commands to use.
>> are there some hand-book (terse ones) for it? so I may recite some
>> (hope not sounds so silly, might a bit though).
>>
>> In the past (maybe till future), one channel is learning form
>> people/list, another channel is in the process of google-searching the
>> problem.
>> Sometimes read man pages, so much information and I just got lost so soon.
>>
>>>
>>> If this does not work then it might be necessary to install the package
>>> "rfkill" and use
>>>
>>>  rfkill list
>>
>> Just installed.
>>
>> Thanks with best regards,
>>>
>>> to check if an RF killswitch has inadvertently been activated. Post any
>>> output or error messages that you may get from these commands.
>>>
>>> --
>>> Regards,            |
>>>          Florian   | http://www.florian-kulzer.eu
>>>
>>>
>>> --
>>> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
>>> with a subject of "unsubscribe". Trouble? Contact
>>> listmaster@lists.debian.org
>>> Archive: [🔎] 20120223222648.GB14071@isar.localhost">http://lists.debian.org/[🔎] 20120223222648.GB14071@isar.localhost
>>>
>>
>>
>> --
>> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
>> with a subject of "unsubscribe". Trouble? Contact
>> listmaster@lists.debian.org
>> Archive:
>> [🔎] CAG9cJmnoU1H6TUt-H+c+gQXf675zX9npZqm+LdA_CLSLWcqc5A@mail.gmail.com">http://lists.debian.org/[🔎] CAG9cJmnoU1H6TUt-H+c+gQXf675zX9npZqm+LdA_CLSLWcqc5A@mail.gmail.com
>>
>>
>
>
> --
> Sent from FOSS (Free Open Source Software)
> Debian GNU/Linux


Reply to: