From: Sherif Omran <sherifomran2000@gmail.com>
To: Ayoub Zaki <ayoub.zaki@embexus.com>,
Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: rfkill cannot open control device
Date: Wed, 20 Dec 2017 10:03:16 +0100 [thread overview]
Message-ID: <CAPb0b+NJKoXidhcwuOkCYnqUz4zi7kT2VBJF=Qn0UcYGtK5gCw@mail.gmail.com> (raw)
In-Reply-To: <CAPb0b+OoCGwv_F3qp-hs87QurWk0RrYWADriZ_Vfh_NXiJyxZw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1491 bytes --]
i have it now installed as a kernel module
but still i get can not open rfkill control device at boot time
On Wed, Dec 20, 2017 at 5:28 AM, Sherif Omran <sherifomran2000@gmail.com>
wrote:
> Bluez5 is already added to local.conf. It gets installed, if i instal
> rpi-basic-image
> with no changes to local.conf, if i use core-image-minimal
> Bluez5 gets installed but not rfkill ..
>
> On Tue, Dec 19, 2017 at 7:16 PM, Ayoub Zaki <ayoub.zaki@embexus.com>
> wrote:
>
>>
>>
>> On 19.12.2017 19:03, Sherif Omran wrote:
>>
>>> how can i add rfkill recipe?
>>>
>>> On Tue, Dec 19, 2017 at 4:23 PM, Sherif Omran <sherifomran2000@gmail.com
>>> <mailto:sherifomran2000@gmail.com>> wrote:
>>>
>>> i used core-image-minimal for a raspberry pi 0w. But i get rfkill
>>> can not open control device. when i give rfkill , i get the
>>> syntanx output, this means it exists.
>>> the wifi driver is installed.
>>>
>>> What is the rfkill device? is it /dev/rfkill ?
>>>
>>>
>> rfkill is part of Bluez5, you can add it to your image recipe.
>>
>>
>>>
>>>
>>>
>>>
>> --
>> Ayoub Zaki
>> Embedded Systems Consultant
>>
>> Vaihinger Straße 2/1
>> D-71634 Ludwigsburg
>>
>> Email : ayoub.zaki@embexus.com
>> Homepage : https://embexus.com
>> VAT No. : DE313902634
>>
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>
>
[-- Attachment #2: Type: text/html, Size: 3064 bytes --]
next prev parent reply other threads:[~2017-12-20 9:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 15:23 rfkill cannot open control device Sherif Omran
2017-12-19 15:31 ` Marc Ferland
2017-12-19 15:40 ` Sherif Omran
2017-12-19 18:03 ` Sherif Omran
2017-12-19 18:16 ` Ayoub Zaki
[not found] ` <CAPb0b+OoCGwv_F3qp-hs87QurWk0RrYWADriZ_Vfh_NXiJyxZw@mail.gmail.com>
2017-12-20 9:03 ` Sherif Omran [this message]
2017-12-20 9:25 ` Zoran Stojsavljevic
2017-12-20 10:18 ` Zoran Stojsavljevic
2017-12-20 10:21 ` Burton, Ross
2017-12-20 10:30 ` Zoran Stojsavljevic
2017-12-20 10:39 ` Burton, Ross
2017-12-20 12:09 ` Sherif Omran
2017-12-20 12:13 ` Burton, Ross
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='CAPb0b+NJKoXidhcwuOkCYnqUz4zi7kT2VBJF=Qn0UcYGtK5gCw@mail.gmail.com' \
--to=sherifomran2000@gmail.com \
--cc=ayoub.zaki@embexus.com \
--cc=yocto@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.