openSuse13.1 - trouble installing TP-WN725N v2.2

Hi Forum!

(first try at using wireless, so please bear with me)

I have a new TP-WN725N wireless USB adapter. I am a bit lost on how to get it to work. Here’s what I believe to be relevant by now:

Running OpenSuse 13.1, kernel 3.12


linux-zzeta:/ # uname -rv
3.12.62-52-desktop #1 SMP PREEMPT Wed Aug 10 18:37:26 UTC 2016 (069dc39)

Searching the net, suggestions are to compile and install some driver, quite a few different ones suggested… I gave a quick try at the one suggested by the vendor - http://www.tp-link.com/en/download/TL-WN725N.html#Driver - with no immediate success. It is apparently though for Ubuntu.

One suggetion in here - /t/problem-with-tl-wn725n-v2-opensuse-12-3/93204/6 - says that: “This driver will be in the 3.12 kernel. For 3.12-rc1 and later (not yet released), the device recognition will be automatic”. So I hope I am mission something simpler than fixing a bunch of compilation errors.

The device is recognized as connected ta a USB port


linux-zzeta:/ # /usr/bin/lsusb
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 001 Device 004: ID 045e:00dd Microsoft Corp. Comfort Curve Keyboard 2000 V1.0
Bus 002 Device 003: ID 0951:1607 Kingston Technology DataTraveler 100
Bus 002 Device 006: ID 0bda:8179 Realtek Semiconductor Corp. 

It is the last of the list “Bus 002 Device 006: ID 0bda:8179”

dmesg logs (dis)connecting it but I notice no error nor warning messages there


linux-zzta:/ # dmesg | less
<-snip->
[27083.742966] usb 2-1.4: USB disconnect, device number 5
[27099.525171] usb 2-1.4: new high-speed USB device number 6 using ehci-pci
[27099.610990] usb 2-1.4: New USB device found, idVendor=0bda, idProduct=8179
[27099.610997] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[27099.611001] usb 2-1.4: Product: 802.11n NIC
[27099.611005] usb 2-1.4: Manufacturer: Realtek
[27099.611009] usb 2-1.4: SerialNumber: 00E04C0001

YaST’s Hardware Information list the device under USB > 802.11n NIC but lacks any information on “driver” or “kernel driver”.

As to similar drivers (?) I get


linux-zzeta:/ # find /lib -name \*8188\*
/lib/firmware/rtlwifi/rtl8188efw.bin
/lib/firmware/rtlwifi/rtl8188eufw.bin
/lib/modules/3.12.59-47-desktop/kernel/drivers/net/wireless/rtlwifi/rtl8188ee
/lib/modules/3.12.59-47-desktop/kernel/drivers/net/wireless/rtlwifi/rtl8188ee/rtl8188ee.ko
/lib/modules/3.12.62-52-desktop/kernel/drivers/net/wireless/rtlwifi/rtl8188ee
/lib/modules/3.12.62-52-desktop/kernel/drivers/net/wireless/rtlwifi/rtl8188ee/rtl8188ee.ko

Looks like I have the “rtl8188eufw.bin” some suggestion say I need, but not any “8188eu.ko” the same suggestions mention.

I am not sure what to try / search next…

Oh! Off course I have already rebooted the machine with the adaptor already connected.

Now what?..

If you took the time to read all the way down here, thank you, even if you do not get to reply!

Hi, welcome

Before starting any investigative activities: are you aware that openSUSE 13.1 is almost at it’s end of life?

Please post output of

ip addr

Thanks.

Yes. But its automatic updates still work - I think it made an update to the kernel only last month. As shown in my first message precisely to show that my system is not that much outdated. Other than that this is not the best moment to discuss the pros and cons of updating often, I presume, so I won’t


linux-zzeta:/ # ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:24:1d:7f:3a:52 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.65/24 brd 192.168.1.255 scope global enp5s0
       valid_lft forever preferred_lft forever
    inet6 2001:8a0:661a:a401:9573:b564:6025:163c/64 scope global temporary dynamic 
       valid_lft 85438sec preferred_lft 52988sec
    inet6 2001:8a0:661a:a401:224:1dff:fe7f:3a52/64 scope global dynamic 
       valid_lft 85438sec preferred_lft 85438sec
    inet6 fe80::224:1dff:fe7f:3a52/64 scope link 
       valid_lft forever preferred_lft forever

localhost, and my old ethernet, I presume

Install openSUSE 13.2.
https://cateee.net/lkddb/web-lkddb/R8188EU.html

Or try rtl8xxxu for openSUSE 13.1 from here:
download.opensuse.org/repositories/home:/Akoellh:/Kernelmodules/openSUSE_13.1_Update/

Am Thu, 22 Sep 2016 15:06:02 GMT
schrieb SusSerre <SusSerre@no-mx.forums.microfocus.com>:

> 100 Bus 002 Device 006: ID 0bda:8179 Realtek Semiconductor Corp.
>
> Code:
> --------------------
>
> linux-zzeta:/ # find /lib -name *8188*
> /lib/firmware/rtlwifi/rtl8188efw.bin
> /lib/firmware/rtlwifi/rtl8188eufw.bin
> /lib/modules/3.12.59-47-desktop/kernel/drivers/net/wireless/rtlwifi/rtl8188ee
> /lib/modules/3.12.59-47-desktop/kernel/drivers/net/wireless/rtlwifi/rtl8188ee/rtl8188ee.ko
> /lib/modules/3.12.62-52-desktop/kernel/drivers/net/wireless/rtlwifi/rtl8188ee
> /lib/modules/3.12.62-52-desktop/kernel/drivers/net/wireless/rtlwifi/rtl8188ee/rtl8188ee.ko
>

Just out of curiosity, what does

grep 8188 /boot/config-*

say?

The driver has been introduced in 3.12, but obviously it is not present in your
kernel.

OTOH, I agree with the remark from Knurpht, if you have the possibility
of upgrading to a newer version of openSUSE, your problem will most likely be
solved without the need of an external driver.

However, there might be another way but if you can just update the system, it
would not be worth the effort (in that case some effort by me), so consider the
advice of upgrading first.

AK


Never attribute to malice that which can be adequately explained by stupidity.
(R.J. Hanlon)

Am Thu, 22 Sep 2016 15:46:02 GMT
schrieb Sauerland <Sauerland@no-mx.forums.microfocus.com>:

> Or try rtl8xxxu for openSUSE 13.1 from here:
> ‘download.opensuse.org/repositories/home:/Akoellh:/Kernelmodules/openSUSE_13.1_Update/
> (http://tinyurl.com/ptlnp8h)
>
>

Nope, that driver does not support the ID 0bda:8179,

modinfo rtl8xxxu |grep 8179

gives nothing.

AK

P.S.

Am Thu, 22 Sep 2016 15:46:02 GMT
schrieb SusSerre <SusSerre@no-mx.forums.microfocus.com>:

> Yes. But its automatic updates still work -

They will stop working soon (mid november IIRC). so this is a rather non-sense
argumentation.


Never attribute to malice that which can be adequately explained by stupidity.
(R.J. Hanlon)

Thank you.

I do not understand what you mean, because I do not understand what the target page says. Is it something to install? is it some log stating that kernels 3.12 (as mine) should have it? I see no reference to 13.2 …

OK, that looks quite straight forward, I might just try it, but I’ll wait a little for respect of the other that also started to help to have time to have their say.

OK, I thought…
But have not installed.

OK, I thought…
But have not installed.

Thank you, too
(lots of people here, I should have joined sooner…)


linux-zzeta:/ # grep 8188 /boot/config-*
/boot/config-3.12.59-47-desktop:CONFIG_RTL8188EE=m
/boot/config-3.12.59-47-desktop:# CONFIG_R8188EU is not set
/boot/config-3.12.62-52-desktop:CONFIG_RTL8188EE=m
/boot/config-3.12.62-52-desktop:# CONFIG_R8188EU is not set

I do consider that advice. But I also know that most people advising to ugrade have no ideia if the upgrade will fix the problem at hand (in general, not this one). And I know that upgrading often risks having other, more critical, parts of my system to stop working. Though, with openSuse’s frequent semi-automatic updates working just fine, over some 7 years now, I am less suspicious of updates.

Actually I have it on my plans to when 13.1 update’s end working (which I see is only 2 month from now from another post). I just hoped to do it on my schedule, not because something that should be working is not.

That I was not aware of.

So that is why I had an alarm a few days ago on my agenda to check for the possibility of an update. Now I remember I read about that date months ago, and I set up the warning to myself. Unaware of the date, I have re-scheduled it to my next holidays, in… November!

As has been said, it should be working, so I still hope that there is some simple thing to do. Otherwise… I don’t know… I probably delay wifi to November, and till then I’ll assess what version should I update to.

Am Thu, 22 Sep 2016 16:16:01 GMT
schrieb SusSerre <SusSerre@no-mx.forums.microfocus.com>:

> /boot/config-3.12.62-52-desktop:# CONFIG_R8188EU is not set

Well, that explains it, driver available but not activated.

It might be a long shot, but maybe pointing to my little repo for kernel
modules was not such a bad idea as I have several (not yet) published packages
and by some coincidence there is also one for rtl8188eu devices.

However, before publishing that driver packages I need some extra info.

from your opening post I see this:

> linux-zzeta:/ # find /lib -name *8188*
> /lib/firmware/rtlwifi/rtl8188efw.bin
> /lib/firmware/rtlwifi/rtl8188eufw.bin

What does

md5sum /lib/firmware/rtlwifi/rtl8188eufw.bin

and

rpm -qf /lib/firmware/rtlwifi/rtl8188eufw.bin

say?

AK


Never attribute to malice that which can be adequately explained by stupidity.
(R.J. Hanlon)


linux-zzeta:/ # md5sum /lib/firmware/rtlwifi/rtl8188eufw.bin
aaef52a47852e599cbff63a3e7f96a94  /lib/firmware/rtlwifi/rtl8188eufw.bin
linux-zzeta:/ # rpm -qf /lib/firmware/rtlwifi/rtl8188eufw.bin
kernel-firmware-20140807git-2.24.2.noarch

Am Thu, 22 Sep 2016 16:56:02 GMT
schrieb SusSerre <SusSerre@no-mx.forums.microfocus.com>:

> Code:
> --------------------
>
> linux-zzeta:/ # md5sum /lib/firmware/rtlwifi/rtl8188eufw.bin
> aaef52a47852e599cbff63a3e7f96a94 /lib/firmware/rtlwifi/rtl8188eufw.bin
> linux-zzeta:/ # rpm -qf /lib/firmware/rtlwifi/rtl8188eufw.bin
> kernel-firmware-20140807git-2.24.2.noarch
>
> --------------------
>
>

Packages just finished building in OBS.

http://download.opensuse.org/repositories/home:/Akoellh:/Kernelmodules/openSUSE_13.1_Update/

  1. Install “rtl8188eu-kmp-desktop” RPM package matching your systems’
    architecture (x86_64 or i586).

  2. Before plugging in your USB Wifi-adapter open a terminal and run

dmesg --follow

  1. plug in your Wifi device.

See what happens and post the output created in the dmesg-Terminal when plugging
in the device.

AK


Never attribute to malice that which can be adequately explained by stupidity.
(R.J. Hanlon)

Addendum:

Ensure you are running kernel 3.12.62 as the packages are built for that
version.

AK

Hmmm… My software manager (y2base?) pre-selected 5 packages!

rtl8188eu-kmp-desktop 4.7.0_k3.12.62_52-1.1
rtl8188eu-kmp-default 4.7.0_k3.12.62_52-1.1
rtl8188eu-kmp-pae 4.7.0_k3.12.62_52-1.1
kernel-default 3.16.62-52.1
kernel-pae 3.16.62-52.1

I deselected them all and closed the software manager - with no action taken
restarted the software manager, no pre-selection now (that was weird…)

Installed rtl8188eu-kmp-desktop

I note that /lib has more “8188” files, presumably those are your files:


linux-zzeta:/ # find /lib -name \*8188\*
/lib/firmware/rtlwifi/rtl8188efw.bin
/lib/firmware/rtlwifi/rtl8188eufw.bin
/lib/modules/3.12.59-47-desktop/weak-updates/updates/drivers/staging/rtl8188eu
/lib/modules/3.12.59-47-desktop/weak-updates/updates/drivers/staging/rtl8188eu/r8188eu.ko
/lib/modules/3.12.59-47-desktop/kernel/drivers/net/wireless/rtlwifi/rtl8188ee
/lib/modules/3.12.59-47-desktop/kernel/drivers/net/wireless/rtlwifi/rtl8188ee/rtl8188ee.ko
/lib/modules/3.12.62-52-desktop/kernel/drivers/net/wireless/rtlwifi/rtl8188ee
/lib/modules/3.12.62-52-desktop/kernel/drivers/net/wireless/rtlwifi/rtl8188ee/rtl8188ee.ko
/lib/modules/3.12.62-52-desktop/updates/drivers/staging/rtl8188eu
/lib/modules/3.12.62-52-desktop/updates/drivers/staging/rtl8188eu/r8188eu.ko

As requested:


linux-zzeta:/ # dmesg --follow
<snip>
[41682.852984] usb 2-1.4: new high-speed USB device number 7 using ehci-pci
[41682.939556] usb 2-1.4: New USB device found, idVendor=0bda, idProduct=8179
[41682.939563] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[41682.939567] usb 2-1.4: Product: 802.11n NIC
[41682.939571] usb 2-1.4: Manufacturer: Realtek
[41682.939574] usb 2-1.4: SerialNumber: 00E04C0001
[41686.001689] usb 2-1.4: USB disconnect, device number 7

[41970.392501] usb 2-1.4: new high-speed USB device number 8 using ehci-pci
[41970.479141] usb 2-1.4: New USB device found, idVendor=0bda, idProduct=8179
[41970.479147] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[41970.479151] usb 2-1.4: Product: 802.11n NIC
[41970.479155] usb 2-1.4: Manufacturer: Realtek
[41970.479159] usb 2-1.4: SerialNumber: 00E04C0001
[41972.005031] cfg80211: Calling CRDA to update world regulatory domain
[41972.006117] Chip Version Info: CHIP_8188E_Normal_Chip_TSMC_D_CUT_1T1R_RomVer(0)
[41972.039576] usbcore: registered new interface driver r8188eu
[41972.052022] cfg80211: World regulatory domain updated:
[41972.052025] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[41972.052027] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[41972.052028] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[41972.052030] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[41972.052031] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[41972.052032] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)

The first set is me (un)plugging it before installing your driver.
The second set plugging it after installing your driver.
(much more promissing)

{if I do not reply within 30 minutes, it will take a few hours till the next one}


linux-zzeta:/ # uname --all
Linux linux-zzeta 3.12.62-52-desktop #1 SMP PREEMPT Wed Aug 10 18:37:26 UTC 2016 (069dc39) i686 i686 i386 GNU/Linux

There is one more entry at:


linux-zzeta:/ # ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:24:1d:7f:3a:52 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.65/24 brd 192.168.1.255 scope global enp5s0
       valid_lft forever preferred_lft forever
    inet6 2001:8a0:661a:a401:9573:b564:6025:163c/64 scope global temporary dynamic 
       valid_lft 72388sec preferred_lft 40559sec
    inet6 2001:8a0:661a:a401:224:1dff:fe7f:3a52/64 scope global dynamic 
       valid_lft 72388sec preferred_lft 72388sec
    inet6 fe80::224:1dff:fe7f:3a52/64 scope link 
       valid_lft forever preferred_lft forever
4: wlp0s29u1u4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 18:a6:f7:08:89:3d brd ff:ff:ff:ff:ff:ff

(the last one, 4:…)

Also:


linux-zzeta:/ # iwlist scan
lo        Interface doesn't support scanning.


enp5s0    Interface doesn't support scanning.


wlp0s29u1u4  No scan results

Either something not well yet, or there is no signal to be detected over here.

It is no surprise if there is none, I live in a rural area, not likely to have many active wireless networks over here, and I still have to buy the remaining stuff for me (a router)

YaST > Network, acknowledjes the adapter, but, as said, I have no info to configure it. Maybe tomorrow.

Also, after the computers gets back from sleep mode I had to unplug and re-plug in the adapter.

It took a few days for my (new) ISP to set up their side of the connection, so that I could confirm it is all fine.

It all works just fine by now.

Thank you