← Back to team overview

kernel-packages team mailing list archive

[Bug 1365844] Re: 0bda:8178 buggy driver rtl8192cu


Same Issue; tested on fresh installed Ubuntu 14.10 and no surprise,
connection drop after a while...

NOTE: i did the same exact way as explained by the above to load the
module for chip 8192. When i do `lsmod  | grep 8192` i can see it has
been loaded. But the problem continuous.

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  0bda:8178 buggy driver rtl8192cu

Status in “linux” package in Ubuntu:

Bug description:
  Ubuntu 14.04/14.10 driver rtl8192cu for a Realtek USB wireless card is
  buggy. I can connect to wifi, but soon the connection is dropped.

  WORKAROUND: 1. First check whether the buggy driver rtl8192cu is active in your operating system. Execute at a terminal window:
  lsmod | grep rtl

  2. Disconnect your wireless connection (unplug the USB adapter that
  contains the Realtek chipset), and temporarily connect to the internet
  by means of an ethernet cable (or by means of another wireless chipset
  that does function well).

  3. Now install some applications for building the right driver via a terminal:
  sudo apt-get install linux-headers-generic build-essential dkms git

  4. Now download the source code of the driver via a terminal:
  git clone https://github.com/pvaret/rtl8192cu-fixes.git

  5. Set it up as a DKMS module via a terminal:
  sudo dkms add ./rtl8192cu-fixes

  6. Build and install the new driver via a terminal:
  sudo dkms install 8192cu/1.9

  7. Refresh the module list via a terminal:
  sudo depmod -a

  8. Blacklist the faulty driver via a terminal:
  sudo cp ./rtl8192cu-fixes/blacklist-native-rtl8192.conf /etc/modprobe.d/

  9. Reboot your computer. The problem should now be solved: disconnect the temporary ethernet cable and insert the Realtek device again. With the following terminal command you can check whether the right driver is active now (copy and paste it into the terminal):
  lsmod | grep 8192

  Note: a possibly surprising side effect might be, that the light on
  your wireless card is blinking constantly now. That's normal: the
  light is blinking whenever data are being sent or received.

  Source: https://github.com/pvaret/rtl8192cu-fixes

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-headers-3.13.0-24 3.13.0-24.47
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
   /dev/snd/controlC0:  bob        1852 F.... pulseaudio
   /dev/snd/controlC1:  bob        1852 F.... pulseaudio
  CurrentDesktop: LXDE
  Date: Fri Sep  5 14:02:05 2014
  HibernationDevice: RESUME=UUID=6d790ec4-ec3d-43a7-ab1a-c4b574e60673
  InstallationDate: Installed on 2014-05-20 (107 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: ASUS All Series
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=37f58aeb-6419-4ca6-a667-002bb0791572 ro quiet splash vt.handoff=7
   linux-restricted-modules-3.13.0-35-generic N/A
   linux-backports-modules-3.13.0-35-generic  N/A
   linux-firmware                             1.127.5

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0803
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81I-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd01/07/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81I-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to: