All of lore.kernel.org
 help / color / mirror / Atom feed
From: Riko Ho <antonius.riko@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: RTL8192EU rev B (SMIC) ==> rtl8192eu_nic.bin ?
Date: Wed, 21 Jun 2017 09:52:38 +0800	[thread overview]
Message-ID: <cc299730-167a-9ba2-fae2-ef0d130649fb@gmail.com> (raw)
In-Reply-To: <CAMKF1spo=pDw1XDhwwbPoQTMjkY-fXmvSgvLrNh5Tum5tn_-wA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3887 bytes --]

How can I obtain that "udev" ? and where can I find the log ? "dmesg" | 
"grep" ?

Two days ago, I saw activity on UART when the dongle was inserted, but 
it's gone now, I can't see the activity..
Any clues ?
Thanks
On 20/06/17 12:51, Khem Raj wrote:
> On Mon, Jun 19, 2017 at 8:46 PM, Riko Ho <antonius.riko@gmail.com> wrote:
>> I got all the files needed, but now I get no response from the dongle when I
>> plug it,
> you might want to check logs and see if there are udev events generated
> on insertion.
>
>> Here's the files on the board :
>> root@beaglebone:/lib/firmware/rtlwifi# ls
>> rtl8188efw.bin           rtl8192eu_ap_wowlan.bin  rtl8723bs_bt.bin
>> rtl8188eufw.bin          rtl8192eu_nic.bin        rtl8723bs_nic.bin
>> rtl8192cfw.bin           rtl8192eu_wowlan.bin     rtl8723bs_wowlan.bin
>> rtl8192cfwU.bin          rtl8192sefw.bin          rtl8723bu_ap_wowlan.bin
>> rtl8192cfwU_B.bin        rtl8712u.bin             rtl8723bu_nic.bin
>> rtl8192cufw.bin          rtl8723aufw_A.bin        rtl8723bu_wowlan.bin
>> rtl8192cufw_A.bin        rtl8723aufw_B.bin        rtl8723fw.bin
>> rtl8192cufw_B.bin        rtl8723aufw_B_NoBT.bin   rtl8723fw_B.bin
>> rtl8192cufw_TMSC.bin     rtl8723befw.bin          rtl8821aefw.bin
>> rtl8192defw.bin          rtl8723befw_36.bin       rtl8821aefw_29.bin
>> rtl8192eefw.bin          rtl8723bs_ap_wowlan.bin  rtl8821aefw_wowlan.bin
>>
>>
>> On 20/06/17 03:57, Khem Raj wrote:
>>
>> On Sun, Jun 18, 2017 at 8:00 PM, Riko Ho <antonius.riko@gmail.com> wrote:
>>
>> Hello Everyone,
>>
>> How can I obtain : rtl8192eu_nic.bin?
>>
>> I got this message :
>>
>> RTL8192EU rev B (SMIC) 2T2R, TX queues 3, WiFi=1, BT=0, GPS=0, HI PA=0
>> usb 1-1: RTL8192EU MAC: 00:0b:81:a2:a5:60
>> usb 1-1: rtl8xxxu: Loading firmware rtlwifi/rtl8192eu_nic.bin
>> usb 1-1: Direct firmware load for rtlwifi/rtl8192eu_nic.bin failed with
>> error -2
>> usb 1-1: request_firmware(rtlwifi/rtl8192eu_nic.bin) failed
>>
>> you probably need to add the nonfree firmware bits something like this
>>
>> https://github.com/resin-os/meta-resin/blob/master/meta-resin-common/recipes-kernel/linux-firmware/linux-firmware_git.bbappend
>>
>> and
>>
>> https://github.com/resin-os/meta-resin/blob/master/meta-resin-common/recipes-kernel/rtl8192cu/rtl8192cu_4.0.2_9000.bb
>>
>> might help
>>
>> Thanks,
>>
>> On 18/06/17 15:49, Martin Jansa wrote:
>>
>> You didn't say which versions you're using.
>>
>> If you're using latest oe-core with gcc7 then you will need v3 version of
>> this change:
>> http://lists.openembedded.org/pipermail/openembedded-devel/2017-June/113247.html
>> I'll send it later today.
>>
>> And how can I clean after building it ? It took about 70Gb of my drive
>>
>> Like any other recipe:
>> bitbake -c clean foo
>>
>> On Sun, Jun 18, 2017 at 1:41 AM, Riko Ho <antonius.riko@gmail.com> wrote:
>>
>> Hello Everyone,
>>
>> I tried to compile chromium but never succeeded, took me already 12 hours
>> and stopped on 99%,
>> I used bitbake for doing it,
>>
>> Is chromium not compatible with arm CPU ? it was working with X86_64
>> before.
>> And how can I clean after building it ? It took about 70Gb of my drive
>>
>> Thanks
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>>
>> --
>>
>> /*******/
>> Sent by Ubuntu LTS 16.04,
>> 谢谢,
>> Regards,
>> Riko Ho
>> /*******/
>>
>>
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>>
>> --
>>
>> /*******/
>> Sent by Ubuntu LTS 16.04,
>> 谢谢,
>> Regards,
>> Riko Ho
>> /*******/

-- 
*

/*******/
Sent by Ubuntu LTS 16.04,
谢谢,
Regards,
Riko Ho
/*******/

*

[-- Attachment #2: Type: text/html, Size: 5428 bytes --]

  reply	other threads:[~2017-06-21  1:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-14  4:10 bitbake core-image-web-kiosk question ? Riko Ho
2017-06-14  5:38 ` Khem Raj
2017-06-15  5:53   ` FriendlyArm Mini6410 ? Riko Ho
2017-06-15  6:05     ` Belisko Marek
2017-06-15  7:16       ` Riko Ho
2017-06-16  1:32       ` Image type on bitbake ? Riko Ho
2017-06-17 23:41       ` Compiling meta-browser ==>chromium ? cleaning ? Riko Ho
2017-06-18  7:49         ` Martin Jansa
2017-06-18  7:52           ` Riko Ho
2017-06-18 11:48           ` dd image to sdcard ? Riko Ho
2017-06-18 19:17             ` Burton, Ross
2017-06-18 19:37               ` Maciej Borzęcki
2017-06-18 22:03                 ` Riko Ho
2017-06-19  3:00           ` RTL8192EU rev B (SMIC) ==> rtl8192eu_nic.bin ? Riko Ho
2017-06-19 19:57             ` Khem Raj
2017-06-20  3:35               ` Riko Ho
2017-06-20  3:46               ` Riko Ho
2017-06-20  4:51                 ` Khem Raj
2017-06-21  1:52                   ` Riko Ho [this message]
2017-06-21  2:28                     ` Khem Raj
2017-06-21  2:32                       ` Riko Ho

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=cc299730-167a-9ba2-fae2-ef0d130649fb@gmail.com \
    --to=antonius.riko@gmail.com \
    --cc=raj.khem@gmail.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.