Author Topic: [SOLVED] Realtek wireless driver  (Read 9021 times)

Offline derekf

  • Full Member
  • ***
  • Posts: 249
[SOLVED] Realtek wireless driver
« on: February 01, 2012, 08:59:21 PM »
Hello Forum,

 I bought a Realtek USB 802.11N Wireless Adapter, but i do not know how to install the driver.

The disk came with it and i also downloaded the driver but it is a zip file, can someone help me please ?

My Operating System is:

 FullMonty          2011.09
 Kernel-version  2.6.38.8-pclos3.bfs
 KDE Version      4.6.5

Derek.
« Last Edit: February 06, 2012, 09:27:55 PM by derekf »

Offline rubentje1991

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 2108
  • Rubenus Parvus MCMXCI
Re: Realtek wireless driver
« Reply #1 on: February 02, 2012, 02:33:29 PM »
Your system is full up-to-date...?

What happens when you plugin the device, and boot the computer?
=> isn't the adapter visible in the network manager?

Offline derekf

  • Full Member
  • ***
  • Posts: 249
Re: Realtek wireless driver
« Reply #2 on: February 03, 2012, 04:01:04 PM »
I have not updated my system in about 2 months, so maybe i should do that first with the old pci card installed then retry the USB .

And the adapter is not visible in network manager.

Offline AS

  • Hero Member
  • *****
  • Posts: 4098
  • Have a nice ... night!
Re: Realtek wireless driver
« Reply #3 on: February 03, 2012, 04:15:11 PM »
Can you tell us exactly which brand/model is your network adapter ?

hint:  ;)
Quote
lspci -nn -k
lsusb

AS

Offline derekf

  • Full Member
  • ***
  • Posts: 249
Re: Realtek wireless driver
« Reply #4 on: February 03, 2012, 06:26:33 PM »
My system is now updated via the Package Manager. When i try to install dkms-r8192se i get a message saying:

 Could not mark all packages for installation or upgrade.

The following packages have unresolvable dependencies.
Make sure that all required reposotries are added and enabled in the preferences.

« Last Edit: February 03, 2012, 06:32:15 PM by derekf »

Offline derekf

  • Full Member
  • ***
  • Posts: 249
Re: Realtek wireless driver
« Reply #5 on: February 03, 2012, 06:37:33 PM »
AS,

[derek@localhost ~]$ lspci -nn -k
00:00.0 RAM memory [0500]: nVidia Corporation MCP61 LPC Bridge [10de:03e2] (rev a1)
        Subsystem: ASUSTeK Computer Inc. Device [1043:83a4]
00:01.0 ISA bridge [0601]: nVidia Corporation MCP61 LPC Bridge [10de:03e1] (rev a2)
        Subsystem: ASUSTeK Computer Inc. Device [1043:83a4]
00:01.1 SMBus [0c05]: nVidia Corporation MCP61 SMBus [10de:03eb] (rev a2)
        Subsystem: ASUSTeK Computer Inc. Device [1043:83a4]
        Kernel driver in use: nForce2_smbus
        Kernel modules: i2c-nforce2
00:01.2 RAM memory [0500]: nVidia Corporation MCP61 Memory Controller [10de:03f5] (rev a2)
        Subsystem: ASUSTeK Computer Inc. Device [1043:83a4]
00:02.0 USB Controller [0c03]: nVidia Corporation MCP61 USB Controller [10de:03f1] (rev a3)
        Subsystem: ASUSTeK Computer Inc. Device [1043:83a4]
        Kernel driver in use: ohci_hcd
        Kernel modules: ohci-hcd
00:02.1 USB Controller [0c03]: nVidia Corporation MCP61 USB Controller [10de:03f2] (rev a3)
        Subsystem: ASUSTeK Computer Inc. Device [1043:83a4]
        Kernel driver in use: ehci_hcd
        Kernel modules: ehci-hcd
00:04.0 PCI bridge [0604]: nVidia Corporation MCP61 PCI bridge [10de:03f3] (rev a1)
00:05.0 Audio device [0403]: nVidia Corporation MCP61 High Definition Audio [10de:03f0] (rev a2)
        Subsystem: ASUSTeK Computer Inc. Device [1043:8415]
        Kernel driver in use: HDA Intel
        Kernel modules: snd-hda-intel
00:06.0 IDE interface [0101]: nVidia Corporation MCP61 IDE [10de:03ec] (rev a2)
        Subsystem: ASUSTeK Computer Inc. Device [1043:83a4]
        Kernel driver in use: pata_amd
        Kernel modules: pata_amd, amd74xx
00:07.0 Bridge [0680]: nVidia Corporation MCP61 Ethernet [10de:03ef] (rev a2)
        Subsystem: ASUSTeK Computer Inc. Device [1043:83a4]
        Kernel driver in use: forcedeth
        Kernel modules: forcedeth
00:08.0 IDE interface [0101]: nVidia Corporation MCP61 SATA Controller [10de:03f6] (rev a2)
        Subsystem: ASUSTeK Computer Inc. Device [1043:83a4]
        Kernel driver in use: sata_nv
        Kernel modules: sata_nv
00:08.1 IDE interface [0101]: nVidia Corporation MCP61 SATA Controller [10de:03f6] (rev a2)
        Subsystem: ASUSTeK Computer Inc. Device [1043:83a4]
        Kernel driver in use: sata_nv
        Kernel modules: sata_nv
00:09.0 PCI bridge [0604]: nVidia Corporation MCP61 PCI Express bridge [10de:03e8] (rev a2)
        Kernel driver in use: pcieport
        Kernel modules: shpchp
00:0b.0 PCI bridge [0604]: nVidia Corporation MCP61 PCI Express bridge [10de:03e9] (rev a2)
        Kernel driver in use: pcieport
        Kernel modules: shpchp
00:0c.0 PCI bridge [0604]: nVidia Corporation MCP61 PCI Express bridge [10de:03e9] (rev a2)
        Kernel driver in use: pcieport
        Kernel modules: shpchp
00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor HyperTransport Configuration [1022:1200]
00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor Address Map [1022:1201]
00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor DRAM Controller [1022:1202]
00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor Miscellaneous Control [1022:1203]
        Kernel driver in use: k10temp
        Kernel modules: k10temp
00:18.4 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor Link Control [1022:1204]
02:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV730XT [Radeon HD 4670] [1002:9490]
        Subsystem: PC Partner Limited Device [174b:e100]
        Kernel driver in use: fglrx_pci
        Kernel modules: fglrx
02:00.1 Audio device [0403]: ATI Technologies Inc RV710/730 [1002:aa38]
        Subsystem: PC Partner Limited R700 Audio Device [Radeon HD 4000 Series] [174b:aa38]
        Kernel driver in use: HDA Intel
        Kernel modules: snd-hda-intel


[derek@localhost ~]$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN
Bus 001 Device 004: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
« Last Edit: February 03, 2012, 06:44:25 PM by derekf »

Offline AS

  • Hero Member
  • *****
  • Posts: 4098
  • Have a nice ... night!
Re: Realtek wireless driver
« Reply #6 on: February 03, 2012, 06:58:53 PM »
My system is now updated via the Package Manager. When i try to install dkms-r8192se i get a message saying:

 Could not mark all packages for installation or upgrade.

The following packages have unresolvable dependencies.
Make sure that all required reposotries are added and enabled in the preferences.



OK, start from here. Have you tried to change repo ?   How much time is past from your previous update ?
Which PCLinuxOS version did you installed ?

Offline derekf

  • Full Member
  • ***
  • Posts: 249
Re: Realtek wireless driver
« Reply #7 on: February 03, 2012, 08:47:09 PM »
AS,

 What do you mean by change repo ? My last update was about 2/3 months ago.

And i installed :

 FullMonty          2011.09
 Kernel-version  2.6.38.8-pclos3.bfs
 KDE Version      4.6.5

Is that what you mean.

Offline Texstar

  • Administrator
  • Super Villain
  • *****
  • Posts: 12657
Re: Realtek wireless driver
« Reply #8 on: February 04, 2012, 03:41:35 AM »
You can't install the dkms-8192se driver because the driver already exists in the 2.6.38.8 kernel. The dkms package is only for older kernels that don't have the driver included in the kernel package.

Thanks to everyone who donates. You keep the servers running.
Follow me on Twitter for the latest development info.

Offline derekf

  • Full Member
  • ***
  • Posts: 249
Re: Realtek wireless driver
« Reply #9 on: February 04, 2012, 04:05:46 PM »
ok Textar, Thanks for that info. So is there any way to get my wireless working ?

Offline AS

  • Hero Member
  • *****
  • Posts: 4098
  • Have a nice ... night!
Re: Realtek wireless driver
« Reply #10 on: February 04, 2012, 04:13:30 PM »
AS,

 What do you mean by change repo ? My last update was about 2/3 months ago.

And i installed :

 FullMonty          2011.09
 Kernel-version  2.6.38.8-pclos3.bfs
 KDE Version      4.6.5

Is that what you mean.

Open synaptic, top menu -> Settings -> Repository and check (eventually try to change) the mirror you are currently using, click on "reload", then click "Mark all updates", and "Apply".

Can you get the updates ? no updates ? Errors ?


Offline derekf

  • Full Member
  • ***
  • Posts: 249
Re: Realtek wireless driver
« Reply #11 on: February 04, 2012, 05:01:16 PM »
AS,

 There is no updates as i did a full update yesterday, which was about 465 files and about 991MB`s.

In the Network connection i dont see the Realtek USB Wireless. I installed Madwifi but dont know where it is, it is not under internet.
« Last Edit: February 04, 2012, 05:03:10 PM by derekf »

Offline AS

  • Hero Member
  • *****
  • Posts: 4098
  • Have a nice ... night!
Re: Realtek wireless driver
« Reply #12 on: February 04, 2012, 05:15:14 PM »
AS,

 There is no updates as i did a full update yesterday, which was about 465 files and about 991MB`s.

OK, but remember that PCLinuxOS is a rolling distro, you need to update often, (say every week or so ...)

Quote
In the Network connection i dont see the Realtek USB Wireless. I installed Madwifi but dont know where it is, it is not under internet.

Now, probably you need to build your own module, from the zip file you mentioned on your first post.
Do you have a link about this file ? Are the any instructions ?

Offline derekf

  • Full Member
  • ***
  • Posts: 249
Re: Realtek wireless driver
« Reply #13 on: February 04, 2012, 05:25:59 PM »
I have the file rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.2011401.tar.gz

Not sure what to do though.

1. readme.txt
   
   2. Release Notes Document
   
   3. driver source code

      3.1 Makefile - to build the modules     

      3.2 Script and configuration for DHCP:
       "wlan0dhcp"
       "ifcfg-wlan0"
     
      3.3 Example of supplicant configuration file:
         "wpa1.conf"

      3.4 Script to run wpa_supplicant
         "runwpa"

   4. wpa_supplicant-0.6.9.tar.gz - the tool help the wlan network to communicate under the
         protection of WPAPSK mechanism (WPA/WPA2)
   
   5. wpa_supplicant-0.6.9_wps_patch.tar.gz - for wps patch
   
==============================================================================================
         User Guide(1) - connecting wireless networking using "Network Manager" GUI utility
==============================================================================================
         (1) Network Manager is a utility attempts to make use of wireless networking easy.
         
         (2) Notes: if you want to use the following command-line method to connect wireless networking,
                           please disable the "Network Manager", because "Network Manager" will conflict with method of command line .



===============================================================================
            User Guide(2) - Set wireless lan MIBs in Command Line
===============================================================================
This driver uses Wireless Extension as an interface allowing you to set
Wireless LAN specific parameters.

Current driver supports "iwlist" to show the device status of nic
        iwlist wlan0 [parameters]
where
        parameter explaination         [parameters]    
        -----------------------        -------------  
        Show available chan and freq   freq / channel  
        Show and Scan BSS and IBSS    scan[ning]          
        Show supported bit-rate         rate / bit[rate]        

For example:
   iwlist wlan0 channel
   iwlist wlan0 scan
   iwlist wlan0 rate

Driver also supports "iwconfig", manipulate driver private ioctls, to set
MIBs.

   iwconfig wlan0 [parameters] [val]
where
   parameter explaination      [parameters]        [val] constraints
        -----------------------     -------------        ------------------
        Connect to AP by address    ap                 [mac_addr]
        Set the essid, join (I)BSS  essid                [essid]
        Set operation mode          mode                {Managed|Ad-hoc}
        Set keys and security mode  key/enc[ryption]    {N|open|restricted|off}

For example:
   iwconfig wlan0 ap XX:XX:XX:XX:XX:XX
   iwconfig wlan0 essid "ap_name"
   iwconfig wlan0 mode Ad-hoc
   iwconfig wlan0 essid "name" mode Ad-hoc
   iwconfig wlan0 key 0123456789 [2] open
   iwconfig wlan0 key off
   iwconfig wlan0 key restricted [3] 0123456789
        Note: Better to set these MIBS without GUI such as NetworkManager and be sure that our
              nic has been brought up before these settings. WEP key index 2-4 is not supportted by
              NetworkManager.

===============================================================================
            Getting IP address
===============================================================================
After start up the nic, the network needs to obtain an IP address before
transmit/receive data.
This can be done by setting the static IP via "ifconfig wlan0 IP_ADDRESS"
command, or using DHCP.

If using DHCP, setting steps is as below:
   (1)connect to an AP via "iwconfig" settings
      iwconfig wlan0 essid [name]   or
      iwconfig wlan0 ap XX:XX:XX:XX:XX:XX

   (2)run the script which run the dhclient
      ./wlan0dhcp
           or
      dhcpcd wlan0
                 (Some network admins require that you use the
                 hostname and domainname provided by the DHCP server.
                 In that case, use
      dhcpcd -HD wlan0)
      

===============================================================================
         WPAPSK/WPA2PSK - using wpa_supplicant
===============================================================================
   Wpa_supplicant helps to secure wireless connection with the protection of
WPAPSK/WPA2PSK mechanism.

   If the version of Wireless Extension in your system is equal or larger than 18,
WEXT driver interface is recommended. Otherwise, IPW driver interface is advised.  
   Note: Wireless Extension is defined us "#define WIRELESS_EXT" in Kernel
   Note: To check the version of wireless extension, please type "iwconfig -v"


    If IPW driver interface is used, it us suggested to follow the steps from 1 to 6.
If wpa_supplicant has been installed in your system, only steps 5 and 6 are required
to be executed for WEXT driver interface.

   To see detailed description for driver interface and wpa_supplicant, please type
"man wpa_supplicant".  
   
   (1)Download latetest source code for wpa supplicant or use wpa_supplicant-0.6.9
      attached in this package. (It is suggested to use default package contained
           in the distribution because there should less compilation issue.)

      Unpack source code of WPA supplicant:

     tar -zxvf wpa_supplicant-0.6.9.tar.gz (e.g.)
     cd wpa_supplicant-0.6.9
   
   (2)Create .config file:
     cp defconfig .config
   
   (3)Edit .config file, uncomment the following line if ipw driver interface
      will be applied:
     #CONFIG_DRIVER_IPW=y.
      
   (4)Build and install WPA supplicant:
     make
     cp wpa_cli wpa_supplicant /usr/local/bin   
   
   NOTE:
    1. If make error for lack of <include/md5.h>, install the openssl lib(two ways):
     (1) Install the openssl lib from corresponding installation disc:
         Fedora Core 2/3/4/5(openssl-0.9.71x-xx),
         Mandrake10.2/Mandriva10.2(openssl-0.9.7x-xmdk),
         Debian 3.1(libssl-dev), Suse 9.3/10.0/10.1(openssl_devl),
         Gentoo(dev-libs/openssl), etc.
     (2) Download the openssl open source package from www.openssl.org, build and
         install it.
    2. If make errors happen in RedHat(and also Fedora Core) for kssl.h,
please add lines below into Makefile
         CPPFLAGS+=-I/usr/kerboros/include
   
   (5)Edit wpa_supplicant.conf to set up SSID and its passphrase.
     For example, the following setting in "wpa1.conf" means SSID
          to join is "BufAG54_Ch6" and its passphrase is "87654321".

      Example 1: Configuration for WPA-PWK
     network={
         ssid="BufAG54_Ch6"
         #scan_ssid=1 //see note 3
         proto=WPA
         key_mgmt=WPA-PSK
         pairwise=CCMP TKIP
         group=CCMP TKIP WEP104 WEP40
         psk="87654321"
         priority=2
        }
   
       Example 2: Configuration for LEAP
       network={
         ssid="BufAG54_Ch6"
         key_mgmt=IEEE8021X
         group=WEP40 WEP104
         eap=LEAP
         identity="user1"
         password="1111"
        }
       Example 3: Linking to hidden ssid given AP's security policy exactly.(see note 3 below)
            ap_scan=2
       network={
      ssid="Hidden_ssid"
      proto=WPA
      key_mgmt=WPA-PSK
      pairwise=CCMP
      group=CCMP
      psk="12345678"
        }
      
       Example 4: Linking to ad-hoc (see note 4 below)
       ap_scan=2
       network={
      ssid="Ad-hoc"
                mode=1
      proto=WPA
      key_mgmt=WPA-NONE
      pairwise=NONE
      group=TKIP
      psk="12345678"
      }
   Note: 1. proto=WPA for WPA, proto=RSN for WPA2.
         2. If user needs to connect an AP with WPA or WPA2 mixed mode, it is suggested
       to set the cipher of pairwise and group to both CCMP and TKIP unless you
       know exactly which cipher type AP is configured.
         3. When connecting to hidden ssid, explicit security policy should be given with
       ap_scan=2 being setting.
         4. It is suggested setting ap_scan to 2 and mode to 1 when linking to or creating an ad-hoc. Group and pairwise
       cipher type should also be explicit, always with group setting to TKIP or CCMP and pairwise setting
       to NONE. Lower version wpa_supplicant may not allow setting group to CCMP with pairwise setting to NONE.
       So if any problem, you may try to set both group and pairwise to CCMP, leaving other setting unchanged, when
            connecting to an CCMP-encrypted ad-hoc.
         5. More config setting option, please refer to wpa_supplicant.conf in wpa_supplicant.tar.gz that we provide.

   (6)Execute WPA supplicant (Assume driver and related modules had been
           loaded):
           ./runwpa

           Note: The script runwpa will check Wireless Extension version automatically.
                 If the version of Wireless Extension is equal or larger than 18, the
                 option of "-D wext" is selected. If the version of Wireless extension
                 is less than 18, the option of "-D ipw" is selected.

===============================================================================
         WPS - PIN & PBC methods
===============================================================================

      (*) please see the "README-WPS" file in the package "wpa_supplicant-0.6.9.tar.gz"
            to perform the WPS function.
            
===============================================================================
         Power Saving Mode
===============================================================================

      (1) in order to enter PS Mode, you need to add the parameter of "power_mgnt=1" when executing "insmod 8712u.ko" :
             ~#insmod 8712u.ko power_mgnt=1
             or
             ~#insmod 8712u.ko power_mgnt=2
             
      (2) Notes:
            power_mgnt=0 ;//default, disable PS
          power_mgnt=1 ;//enable PS, MIN_PS Mode
          power_mgnt=2 ;//enable PS, MAX_PS Mode
          
  

Offline AS

  • Hero Member
  • *****
  • Posts: 4098
  • Have a nice ... night!
Re: Realtek wireless driver
« Reply #14 on: February 04, 2012, 05:38:01 PM »
I have the file rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.2011401.tar.gz

Not sure what to do though.

1. readme.txt
   
   2. Release Notes Document
   
   3. driver source code

      3.1 Makefile - to build the modules     


That's the part we are interested right now ...
Any link  ? Where do you have downloaded the file ?