Page 1 of 2 12 LastLast
Results 1 to 10 of 17

Thread: Asus USB-AC53 Nano driver redux - not working

  1. #1
    Join Date
    Aug 2020
    Beans
    11

    Unhappy Asus USB-AC53 Nano driver redux - not working

    I'm (un)lucky owner of WiFi dongle based on RTL8822BU. My system is
    Code:
    5.4.0-42-generic
    lsusb output is
    Code:
    Bus 001 Device 002: ID 0b05:184c ASUSTek Computer, Inc. 802.11ac NIC
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 002 Device 002: ID 046d:c505 Logitech, Inc. Cordless Mouse+Keyboard Receiver
    Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    There is CDROM included in package, even with "linux" folder, but running ready-to-use shell script produces error:

    Code:
    /home/szydas/Desktop/RTL88x2BU_WiFi_linux_v5.2.4.3_24934.20171101_COEX20171012-5044/driver/rtl88x2BU_WiFi_linux_v5.2.4.3_24934.20171101_COEX20171012-5044/include/osdep_service_linux.h:282:8: error: ‘_timer’ {aka ‘struct timer_list’} has no member named ‘data’
      282 |  ptimer->data = (unsigned long)cntx;
          |        ^~
    /home/szydas/Desktop/RTL88x2BU_WiFi_linux_v5.2.4.3_24934.20171101_COEX20171012-5044/driver/rtl88x2BU_WiFi_linux_v5.2.4.3_24934.20171101_COEX20171012-5044/include/osdep_service_linux.h:283:2: error: implicit declaration of function ‘init_timer’; did you mean ‘_init_timer’? [-Werror=implicit-function-declaration]
      283 |  init_timer(ptimer);
          |  ^~~~~~~~~~
          |  _init_timer
    So i followed steps from that thread https://ubuntuforums.org/showthread....395729&page=2& - unfortunately it produces lot of warnings and ends with an error:
    Code:
    home/szydas/rtl8822bu/os_dep/osdep_service.c: In function ‘isFileReadable’:
    /home/szydas/rtl8822bu/os_dep/osdep_service.c:2022:10: error: implicit declaration of function ‘get_ds’; did you mean ‘get_da’? [-Werror=implicit-function-declaration]
     2022 |   set_fs(get_ds());
          |          ^~~~~~
          |          get_da
    /home/szydas/rtl8822bu/os_dep/osdep_service.c:2022:10: error: incompatible type for argument 1 of ‘set_fs’
     2022 |   set_fs(get_ds());
          |          ^~~~~~~~
          |          |
          |          int
    In file included from ./include/linux/uaccess.h:11,
                     from ./include/linux/crypto.h:21,
                     from ./include/crypto/hash.h:11,
                     from ./include/linux/uio.h:10,
                     from ./include/linux/socket.h:8,
                     from ./include/linux/compat.h:15,
                     from ./include/linux/ethtool.h:17,
                     from ./include/linux/netdevice.h:37,
                     from /home/szydas/rtl8822bu/include/osdep_service_linux.h:35,
                     from /home/szydas/rtl8822bu/include/osdep_service.h:41,
                     from /home/szydas/rtl8822bu/include/drv_types.h:32,
                     from /home/szydas/rtl8822bu/os_dep/osdep_service.c:24:
    ./arch/x86/include/asm/uaccess.h:29:40: note: expected ‘mm_segment_t’ {aka ‘struct <anonymous>’} but argument is of type ‘int’
       29 | static inline void set_fs(mm_segment_t fs)
          |                           ~~~~~~~~~~~~~^~
    /home/szydas/rtl8822bu/os_dep/osdep_service.c: In function ‘retriveFromFile’:
    /home/szydas/rtl8822bu/os_dep/osdep_service.c:2052:11: error: incompatible type for argument 1 of ‘set_fs’
     2052 |    set_fs(get_ds());
          |           ^~~~~~~~
          |           |
          |           int
    In file included from ./include/linux/uaccess.h:11,
                     from ./include/linux/crypto.h:21,
                     from ./include/crypto/hash.h:11,
                     from ./include/linux/uio.h:10,
                     from ./include/linux/socket.h:8,
                     from ./include/linux/compat.h:15,
                     from ./include/linux/ethtool.h:17,
                     from ./include/linux/netdevice.h:37,
                     from /home/szydas/rtl8822bu/include/osdep_service_linux.h:35,
                     from /home/szydas/rtl8822bu/include/osdep_service.h:41,
                     from /home/szydas/rtl8822bu/include/drv_types.h:32,
                     from /home/szydas/rtl8822bu/os_dep/osdep_service.c:24:
    ./arch/x86/include/asm/uaccess.h:29:40: note: expected ‘mm_segment_t’ {aka ‘struct <anonymous>’} but argument is of type ‘int’
       29 | static inline void set_fs(mm_segment_t fs)
          |                           ~~~~~~~~~~~~~^~
    /home/szydas/rtl8822bu/os_dep/osdep_service.c: In function ‘storeToFile’:
    /home/szydas/rtl8822bu/os_dep/osdep_service.c:2087:11: error: incompatible type for argument 1 of ‘set_fs’
     2087 |    set_fs(get_ds());
          |           ^~~~~~~~
          |           |
          |           int
    In file included from ./include/linux/uaccess.h:11,
                     from ./include/linux/crypto.h:21,
                     from ./include/crypto/hash.h:11,
                     from ./include/linux/uio.h:10,
                     from ./include/linux/socket.h:8,
                     from ./include/linux/compat.h:15,
                     from ./include/linux/ethtool.h:17,
                     from ./include/linux/netdevice.h:37,
                     from /home/szydas/rtl8822bu/include/osdep_service_linux.h:35,
                     from /home/szydas/rtl8822bu/include/osdep_service.h:41,
                     from /home/szydas/rtl8822bu/include/drv_types.h:32,
                     from /home/szydas/rtl8822bu/os_dep/osdep_service.c:24:
    ./arch/x86/include/asm/uaccess.h:29:40: note: expected ‘mm_segment_t’ {aka ‘struct <anonymous>’} but argument is of type ‘int’
       29 | static inline void set_fs(mm_segment_t fs)
          |                           ~~~~~~~~~~~~~^~
    cc1: some warnings being treated as errors
    make[2]: *** [scripts/Makefile.build:275: /home/szydas/rtl8822bu/os_dep/osdep_service.o] Error 1
    make[1]: *** [Makefile:1731: /home/szydas/rtl8822bu] Error 2
    make[1]: Leaving directory '/usr/src/linux-headers-5.4.0-42-generic'
    make: *** [Makefile:1318: modules] Error 2
    I'm not a programmer and probably too old to learn it. Any help appreciated.

  2. #2
    Join Date
    Aug 2020
    Beans
    11

    Re: Asus USB-AC53 Nano driver redux - not working

    UPDATE:
    Following suggestion from friend I replaced get_ds() funktion with KERNEL_DS. And it almost solved problem.... almost
    Code:
    home/szydas/rtl8822bu/os_dep/linux/os_intfs.c:1170:22: error: initialization of ‘u16 (*)(struct net_device *, struct sk_buff *, struct net_device *)’ {aka ‘short unsigned int (*)(struct net_device *, struct sk_buff *, struct net_device *)’} from incompatible pointer type ‘u16 (*)(struct net_device *, struct sk_buff *, void *, u16 (*)(struct net_device *, struct sk_buff *, struct net_device *))’ {aka ‘short unsigned int (*)(struct net_device *, struct sk_buff *, void *, short unsigned int (*)(struct net_device *, struct sk_buff *, struct net_device *))’} [-Werror=incompatible-pointer-types]
     1170 |  .ndo_select_queue = rtw_select_queue,
          |                      ^~~~~~~~~~~~~~~~
    /home/szydas/rtl8822bu/os_dep/linux/os_intfs.c:1170:22: note: (near initialization for ‘rtw_netdev_ops.ndo_select_queue’)
    cc1: some warnings being treated as errors
    make[2]: *** [scripts/Makefile.build:275: /home/szydas/rtl8822bu/os_dep/linux/os_intfs.o] Error 1
    make[1]: *** [Makefile:1731: /home/szydas/rtl8822bu] Error 2
    make[1]: Leaving directory '/usr/src/linux-headers-5.4.0-42-generic'
    make: *** [Makefile:1318: modules] Error 2
    Last edited by szydas; August 3rd, 2020 at 05:55 PM. Reason: missing characters

  3. #3
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    25,363
    Distro
    Ubuntu 20.04 Focal Fossa

    Re: Asus USB-AC53 Nano driver redux - not working

    With a temporary working internet connection by ethernet, tethering or whatever means possible, do:

    Code:
    sudo apt update
    sudo apt install git dkms
    git clone https://github.com/jeremyb31/rtl8822bu.git
    sudo dkms add ./rtl8822bu
    sudo dkms install 8822bu/1.1
    Reboot.
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, Ph.D., Sc.D.

  4. #4
    Join Date
    Aug 2020
    Beans
    11

    Re: Asus USB-AC53 Nano driver redux - not working

    I did. It tells, that's everything was succesful. I rebooted. Now:
    1. lsusb does nothing, i mean after pressing Enter cursor blinks.... and blinks... until next reboot.
    2. lsmod gives
    Code:
    szydas@ubunciak:~$ lsmod |grep 8822
    8822bu               1781760  1
    cfg80211              704512  1 8822bu
    3. In Network Setings dongle is not visible. Tried every USB slot available. Several reboots - no change.

  5. #5
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    25,363
    Distro
    Ubuntu 20.04 Focal Fossa

    Re: Asus USB-AC53 Nano driver redux - not working

    lsusb does nothing, i mean after pressing Enter cursor blinks.... and blinks... until next reboot.
    It is not supposed to do anything at all except list (ls) the devices that are attached to your USB (usb) ports. Hence, lsusb. Installing a driver or the correct driver or the wrong driver doesn't change whether the device is or is not inserted.

    Let's check the log for clues:

    Code:
    dmesg | grep -i -e 8822 -e rtl
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, Ph.D., Sc.D.

  6. #6
    Join Date
    Aug 2020
    Beans
    11

    Re: Asus USB-AC53 Nano driver redux - not working

    I think that is most revelant part
    Code:
    [   20.563725] 8822bu: loading out-of-tree module taints kernel.
    [   20.569129] 8822bu: module verification failed: signature and/or required key missing - tainting kernel
    [   20.574186] RTW: rtl8822bu v5.1.0-5_17968.20160601_BTCOEX20160411-1400_beta
    [   20.574186] RTW: rtl8822bu BT-Coex version = BTCOEX20160411-1400
    [   20.574324] RTW: CHIP TYPE: RTL8822B
    [   20.576649] RTW: Chip Version Info: CHIP_8822B_Normal_Chip_UMC_D_CUT_2T2R_RomVer(3)

  7. #7
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    25,363
    Distro
    Ubuntu 20.04 Focal Fossa

    Re: Asus USB-AC53 Nano driver redux - not working

    Looks perfect, actually.

    Please remove the device and run:

    Code:
    tail -f /var/log/syslog
    Insert the device and tell us what the terminal reports in full related to the device and driver.

    Get ot of 'tail' with Ctrl+c.
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, Ph.D., Sc.D.

  8. #8
    Join Date
    Aug 2020
    Beans
    11

    Re: Asus USB-AC53 Nano driver redux - not working

    Well.... nothing happen. No single log entry about inserting something into USB. I found only one entry about removing it.
    Code:
    Aug  5 09:29:01 ubunciak kernel: [  858.665662] usb 1-2: USB disconnect, device number 3
    But, strangely, inserting pendrive also doesn't trigger any action,.. and it worked even few days ago. Maybe my mobo is dying?
    Last edited by szydas; August 5th, 2020 at 08:42 AM. Reason: additional info

  9. #9
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    25,363
    Distro
    Ubuntu 20.04 Focal Fossa

    Re: Asus USB-AC53 Nano driver redux - not working

    Quote Originally Posted by szydas View Post
    Well.... nothing happen. No single log entry about inserting something into USB. I found only one entry about removing it.
    Code:
    Aug  5 09:29:01 ubunciak kernel: [  858.665662] usb 1-2: USB disconnect, device number 3
    But, strangely, inserting pendrive also doesn't trigger any action,.. and it worked even few days ago. Maybe my mobo is dying?
    Perhaps.

    Have you tried all the available USB ports? Maybe it is just one port that is dying.
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, Ph.D., Sc.D.

  10. #10
    Join Date
    Aug 2020
    Beans
    11

    Re: Asus USB-AC53 Nano driver redux - not working

    Quote Originally Posted by chili555 View Post
    Perhaps.

    Have you tried all the available USB ports? Maybe it is just one port that is dying.
    Yes. I did. But my keyboard an mouse on USB work without problem... even if I change port

Page 1 of 2 12 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •