Re: usb wifi dongle for f27

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

 



My dmesg shows:

[78982.428363] usb 3-4: new high-speed USB device number 3 using xhci_hcd
[78982.555490] usb 3-4: New USB device found, idVendor=0bda, idProduct=8178
[78982.555497] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[78982.555501] usb 3-4: Product: USB WLAN
[78982.555503] usb 3-4: Manufacturer: 802.11n
[78982.555506] usb 3-4: SerialNumber: 00e04c000001
[78982.558671] rtl8192cu: Chip version 0x11
[78982.592147] rtl8192cu: Board Type 0
[78982.592242] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1
[78982.592388] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin
[78982.592689] ieee80211 phy1: Selected rate control algorithm 'rtl_rc'
[78982.610025] rtl8192cu 3-4:1.0 wlp17s0f3u4: renamed from wlan0
[78982.628687] IPv6: ADDRCONF(NETDEV_UP): wlp17s0f3u4: link is not ready
[78982.630253] rtl8192cu: MAC auto ON okay!
[78982.643190] rtl8192cu: Tx queue select: 0x05
[78983.190522] IPv6: ADDRCONF(NETDEV_UP): wlp17s0f3u4: link is not ready
[78983.198607] rtl8192cu: MAC auto ON okay!
[78983.211619] rtl8192cu: Tx queue select: 0x05
[78983.764725] IPv6: ADDRCONF(NETDEV_UP): wlp17s0f3u4: link is not ready
[78983.788448] IPv6: ADDRCONF(NETDEV_UP): wlp17s0f3u4: link is not ready
[78984.771085] rtl8192cu: MAC auto ON okay!
[78984.783995] rtl8192cu: Tx queue select: 0x05
[78985.337847] IPv6: ADDRCONF(NETDEV_UP): wlp17s0f3u4: link is not ready
[78986.325008] wlp17s0f3u4: authenticate with c0:4a:00:be:86:ef
[78986.346513] wlp17s0f3u4: send auth to c0:4a:00:be:86:ef (try 1/3)
[78986.449931] wlp17s0f3u4: send auth to c0:4a:00:be:86:ef (try 2/3)
[78986.525616] wlp17s0f3u4: authenticated
[78986.525920] wlp17s0f3u4: associate with c0:4a:00:be:86:ef (try 1/3)
[78986.568890] wlp17s0f3u4: RX AssocResp from c0:4a:00:be:86:ef (capab=0x431 status=0 aid=2)
[78986.671127] wlp17s0f3u4: associated
[78986.680755] IPv6: ADDRCONF(NETDEV_CHANGE): wlp17s0f3u4: link becomes ready


On Fri, Jan 19, 2018 at 2:41 AM, JD <jd1008@xxxxxxxxx> wrote:




On 01/15/2018 09:45 AM, Joost wrote:
My tp-link TL-WN823N works on F27 out-of-the-box. It's 2.4GHz only and costs about 13 €.

On Sun, Jan 14, 2018 at 8:20 PM, JD <jd1008@xxxxxxxxx <mailto:jd1008@xxxxxxxxx>> wrote:



    On 01/14/2018 10:42 AM, Tom Horsley wrote:

        On Sun, 14 Jan 2018 10:11:57 -0700
        JD wrote:

            Could you or someone list some chipsets (even legacy ones)
            that are very likely fully supported by f27 distribution iso
            right out of the box.\

        Well, I've got this one in my F27 desktop at work providing
        wifi for my phone and tablet acting as an access point:

        Bus 002 Device 003: ID 0411:01a2 BUFFALO INC. (formerly
        MelCo., Inc.) WLI-UC-GNM Wireless LAN Adapter [Ralink RT8070]

        It is a cute little thing, just a tad bigger than the USB
        slot it is plugged into.

        You can probably guess some more by looking in the
        kernel modules directories at:

        /usr/lib/modules/*/kernel/drivers/net/wireless

    I looked at older installations I have, and I am shocked to see they
    contain the b43 and b43legacy  wireless drivers.
    How come they did not make it into f27????

    See below:

    $ find /lib/modules/ -name b43\*
    /lib/modules/3.19.8-100.fc20.x86_64/kernel/drivers/net/wireless/b43
    /lib/modules/3.19.8-100.fc20.x86_64/kernel/drivers/net/wireless/b43/b43.ko
    /lib/modules/3.19.8-100.fc20.x86_64/kernel/drivers/net/wireless/b43legacy
    /lib/modules/3.19.8-100.fc20.x86_64/kernel/drivers/net/wireless/b43legacy/b43legacy.ko
    /lib/modules/3.11.10-301.fc20.x86_64/kernel/drivers/net/wireless/b43
    /lib/modules/3.11.10-301.fc20.x86_64/kernel/drivers/net/wireless/b43/b43.ko
    /lib/modules/3.11.10-301.fc20.x86_64/kernel/drivers/net/wireless/b43legacy
    /lib/modules/3.11.10-301.fc20.x86_64/kernel/drivers/net/wireless/b43legacy/b43legacy.ko


Well, plugging it in, and running dmesg, I see

[371723.353041] usb 4-1: new high-speed USB device number 27 using ehci-pci
[371723.865025] usb 4-1: device not accepting address 27, error -71
[371724.160043] usb 8-1: new full-speed USB device number 12 using uhci_hcd
[371724.291232] usb 8-1: No LPM exit latency info found, disabling LPM.
[371724.319228] usb 8-1: New USB device found, idVendor=2357, idProduct=0109
[371724.319234] usb 8-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[371724.319236] usb 8-1: Product: 802.11n NIC
[371724.319238] usb 8-1: Manufacturer: Realtek
[371724.319240] usb 8-1: SerialNumber: 00e04c000001

I ran
$ sudo modprobe realtek 8139cp 8139too atp r8169
(so I could cover all the realtek related drivers),

$ lsmod | egrep 'realtek|8139cp|8139too|atp|r8169'
realtek                12700  0

then I ran ifconfig:

$ ifconfig
bond0: flags=5123<UP,BROADCAST,MASTER,MULTICAST>  mtu 1500
        ether 4e:70:82:2e:39:81  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

em1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 00:24:e8:93:0f:3c  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 22  memory 0xf6fe0000-f7000000

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 19881  bytes 1802009 (1.7 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 19881  bytes 1802009 (1.7 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255
        ether 52:54:00:47:9a:79  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)

The realtek interface is NOT visible to the user.



_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@lists.fedoraproject.org

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux