On 10/26/2014 08:51 PM, poma wrote:
On 27.10.2014 03:25, jd1008 wrote:
On 10/26/2014 08:15 PM, poma wrote:
On 27.10.2014 02:24, jd1008 wrote:
On 10/26/2014 05:38 PM, poma wrote:
- station(client) mode
$ modinfo r8712u
filename:       
/lib/modules/3.17.1-202.fc20.x86_64/kernel/drivers/staging/rtl8712/r8712u.ko.xz
firmware:       rtlwifi/rtl8712u.bin
author:         Larry Finger
description:    rtl871x wireless lan driver
license:        GPL

- master(AP) mode
$ modinfo rtl8192su
filename:       /lib/modules/3.17.1-202.fc20.x86_64/updates/rtl8192su.ko
firmware:       rtlwifi/rtl8192sufw.bin
description:    Realtek 8188S/8191S/8192S 802.11n USB wireless
license:        GPL
author:         Christian Lamparter     <chunk...@googlemail.com>
author:         Joshua Roys             <joshua.r...@gtri.gatech.edu>
author:         Larry Finger            <larry.fin...@lwfinger.net>
author:         Realtek WlanFAE         <wlan...@realtek.com>
author:         lizhaoming              <chaoming...@realsil.com.cn>


http://wireless.kernel.org/en/users/Drivers/rtl819x
https://wiki.debian.org/rtl819x


poma
must I manually install kernel 17?  It is not yet in the updates repo:

# yum update
Loaded plugins: langpacks, refresh-packagekit
adobe-linux-x86_64 |  951 B  00:00:00
google-earth |  951 B  00:00:00
rpmfusion-free-updates | 3.3 kB  00:00:00
rpmfusion-nonfree-updates | 3.3 kB  00:00:00
updates/20/x86_64/metalink |  19 kB  00:00:00
No packages marked for update

Forget the kernel version, it doesn't matter, I'm just showing what I currently 
drive.
The question is do you need a:
1. Station mode
or
2. Access Point  mode
or
3. Both

See http://wireless.kernel.org/en/users/Documentation/modes

BTW paste here 'lsusb' output


poma

# lsusb
Bus 002 Device 007: ID 07d1:3304 D-Link System FR-300USB 802.11bgn
Wireless Adapter<<<<<<this is the dongle in question.
Bus 002 Device 007: ID 07d1:3304 D-Link System FR-300USB 802.11bgn Wireless 
Adapter

https://git.kernel.org/cgit/linux/kernel/git/iwlwifi/iwlwifi-next.git/tree/drivers/staging/rtl8712/usb_intf.c#n70
        /* D-Link */
        {USB_DEVICE(0x2001, 0x3306)},
        {USB_DEVICE(0x07D1, 0x3306)}, /* 11n mode disable */

https://git.kernel.org/cgit/linux/kernel/git/iwlwifi/iwlwifi-next.git/tree/drivers/staging/rtl8712/usb_intf.c#n126
        /* D-Link */
        {USB_DEVICE(0x07D1, 0x3302)},
        {USB_DEVICE(0x07D1, 0x3300)},
        {USB_DEVICE(0x07D1, 0x3303)},


https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-bus-usb
...
What:           /sys/bus/usb/drivers/.../new_id
Date:           October 2011
Contact:        linux-...@vger.kernel.org
Description:
                Writing a device ID to this file will attempt to
                dynamically add a new device ID to a USB device driver.
                This may allow the driver to support more hardware than
                was included in the driver's static device ID support
                table at compile time. The format for the device ID is:
                idVendor idProduct bInterfaceClass RefIdVendor RefIdProduct
                The vendor ID and device ID fields are required, the
                rest is optional. The Ref* tuple can be used to tell the
                driver to use the same driver_data for the new device as
                it is used for the reference device.
                Upon successfully adding an ID, the driver will probe
                for the device and attempt to bind to it.  For example:
                 ...

# modprobe -v r8712u
insmod 
/lib/modules/3.17.1-202.fc20.x86_64/kernel/drivers/staging/rtl8712/r8712u.ko.xz

# ls /sys/bus/usb/drivers/r8712u/new_id
/sys/bus/usb/drivers/r8712u/new_id

# echo "07d1 3304" > /sys/bus/usb/drivers/r8712u/new_id

# cat /sys/bus/usb/drivers/r8712u/new_id
07d1 3304

# dmesg | grep r8712u


Well:
$ dmesg | grep r8712u
[ 380.529042] r8712u: module is from the staging directory, the quality is unknown, you have been warned.
[  380.530516] usbcore: registered new interface driver r8712u

But still it does not detect my fry's FR-300 USB dongle.

I am not going to go through the git kernel sources because I do not know what I will end up with as far other parts of the kernel. They state clearly that the driver that has been patched to work
with this dongle must be built on the git kernel source.

Guess I have to wait until fedora 30? :) :)

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Reply via email to