TP-LINK Wireless N USB Adapt- Howtoconnect[Solved by pemasu]

Message
Author
tytower

TP-LINK Wireless N USB Adapt- Howtoconnect[Solved by pemasu]

#1 Post by tytower »

I have splashed about a bit and it just ain't coming.

It does not run out of the box so I tried around on the ADSL D-Link Modem but did not find a mac address to enter yet .

So the device is not recognised so I went looking for a driver ,trying a few on the puppy network module load page to no avail , then as I had the CD for the device I tried NDISWrapper approach and found the right files on the CD but Puppy said it was an invalid inf file .

Splashed around in there for a bit looking at various options but atm I am just scratching the head??pemasu
Last edited by tytower on Fri 11 Jan 2013, 20:54, edited 1 time in total.

tytower

#2 Post by tytower »

I've now tried every module with usb in it on Barrys driver load program to no avail

I've also downloaded the right drivers from TP-LINK's site and tried to load the ".inf" file but just get an error message and it does not work

Can anyone help at all ?

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#3 Post by rcrsn51 »

1. You need to supply an exact model number.

2. With the device UNPLUGGED, type "lsusb". Then plug it in and repeat. Report the vendor:product ID codes.

3. Please supply a link to the website where you got the driver.

tytower

#4 Post by tytower »

Doubled up
Last edited by tytower on Sat 01 Dec 2012, 21:25, edited 1 time in total.

tytower

#5 Post by tytower »

The Model is TL-WN723N


# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 413c:1003 Dell Computer Corp. (Keyboard)
Bus 002 Device 003: ID 0461:4d22 Primax Electronics, Ltd
Bus 002 Device 004: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC (Arduino)
Bus 002 Device 005: ID 413c:2010 Dell Computer Corp. (Mouse)
# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 0bda:8176 Realtek Semiconductor Corp.
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 413c:1003 Dell Computer Corp.
Bus 002 Device 003: ID 0461:4d22 Primax Electronics, Ltd
Bus 002 Device 004: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 002 Device 005: ID 413c:2010 Dell Computer Corp.
# lsusb

An observation here to those concerned with lsusb- If it indented after each root hub it could be clearer

I got the driver from
http://www.tp-link.com/en/support/downl ... n=V2#tbl_a

And I have the Windows installation disk and Mac address

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#6 Post by rcrsn51 »

You haven't said what Puppy version you are using.

But the latest Slacko 5.3.7.7 with Kernel 3.2.33 has the rtl8192cu module that supports your [obda:8176] device.

It also uses the firmware file rtl8192cufw.bin. Check in dmesg for any problems.

tytower

#7 Post by tytower »

Well I brought down the iso and gave it a whirl.
Driver is there and seems to be working . Light comes on in adaptor but no connection to router as yet.
It says there is no available wireless network and as this is a second hand router that may be the case . I'll have to pull it apart and see if the antenna is OK and connected

Working on it --Thanks rcrsn51

tytower

#8 Post by tytower »

No the router works fine . I tested it with windows and it connected straight away.

So I have a device being recognised by the driver but it will not connect to the ADSL2 modem?

It says " No wireless network found"
Last edited by tytower on Wed 05 Dec 2012, 06:27, edited 1 time in total.

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#9 Post by rcrsn51 »

There is a driver here for Puppy 431 that matches your device.

I believe that there is also one here for Lupu.

tytower

#10 Post by tytower »

Yes thanks for that

I d/l and tried all and any driver pets I could .
I saw a driver in the module load page and tried to load it but got a message that it would not load - see attached screenshot

Where do these files go when a pet downloads it.
Attachments
Driverloadmessage.png
(165.08 KiB) Downloaded 3008 times

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#11 Post by rcrsn51 »

Remember that these packages ONLY work in the Puppy for which they were built.

tytower

#12 Post by tytower »

Using the 5.4.2 distro the device is recognised but cannot find a network .
Now I know my settings are right because I can connect through windows without problem
Using the correct driver then for 5.4.2 is not working?

tytower

#13 Post by tytower »

Well in an effort to move on I bought another one today

I bought a Digitech USB2.0 Wireless dongle whatever that is ?
Didn't have a model number except maybe 802.11N on the packaging
Documentation calls it a " Wireless-N USB 2.0 Adaptor (802.11n)

Supposed to be good for Linux above kernel 2.4
With the latest "Puppy 5.4.2" I found I had to load the driver "rtl8193cu" and I messed about with the linux stuff on the CD so that may have been appended after I messed about attempting to run the install script which hangs . Tried it 3 times

Got a bit further with this one .Plugging and unplugging got it to at least get a network signal but it still would not operate through the router . So it continues

tytower

#14 Post by tytower »

Merry Christmas to all !

With the Christmas influx of iPods ,IPhones ,IPads and wiFi devices I have had an opportunity to check this out some more.

All of the above connect successfully even with WEP security enabled .
My computer connects OK by line connection eth0 and wlan0 but wlan0 will not get access to the dns server and so can't get a web site through wlan.

I just need an expert to tell me what to change in the router ?

tytower

#15 Post by tytower »

Anyone got any ideas here? What Router setting should I change?

Aside from that:-
As far as "frisbee" is concerned I don't find it very helpful
It does stuff behind the scenes and when it gets it wrong it is difficult to find out whats wrong . Not enough feedbback for me .

My machine getsan IP from the router on bootup then immediately goes down so I then have to connects again which then connect properly . Finding out what it's doing is not very easy !

I don't recommend "Frisbee"

Here is what the log says
Dec 23 08:32:14 puppypc6935 daemon.info dhcpcd[4074]: eth0: leased 10.1.1.3 for 3600 seconds
Dec 23 08:32:16 puppypc6935 daemon.info dhcpcd[4770]: version 5.2.9 starting
Dec 23 08:32:16 puppypc6935 daemon.debug dhcpcd[4770]: forking to background
Dec 23 08:32:16 puppypc6935 daemon.info dhcpcd[4770]: forked to background, child pid 4777
Dec 23 08:32:16 puppypc6935 daemon.debug dhcpcd[4777]: eth0: using hwaddr 00:1d:09:22:75:69
Dec 23 08:32:16 puppypc6935 daemon.debug dhcpcd[4777]: eth0: executing `/usr/libexec/dhcpcd-run-hooks', reason PREINIT
Dec 23 08:32:16 puppypc6935 daemon.debug dhcpcd[4777]: eth0: executing `/usr/libexec/dhcpcd-run-hooks', reason CARRIER
Dec 23 08:32:20 puppypc6935 daemon.info dhcpcd[4074]: forked to background, child pid 5232
Dec 23 08:32:20 puppypc6935 daemon.info dhcpcd[5232]: eth0: carrier lost
Dec 23 08:32:20 puppypc6935 daemon.info dhcpcd[5236]: sending commands to master dhcpcd process
Dec 23 08:32:22 puppypc6935 daemon.info dhcpcd[4777]: eth0: carrier lost
Dec 23 08:32:22 puppypc6935 daemon.debug dhcpcd[4777]: eth0: executing `/usr/libexec/dhcpcd-run-hooks', reason NOCARRIER
Dec 23 08:32:23 puppypc6935 daemon.info dhcpcd[4777]: control command: dhcpcd --release eth0
Dec 23 08:32:23 puppypc6935 daemon.info dhcpcd[4777]: eth0: removing interface
Dec 23 08:32:23 puppypc6935 daemon.debug dhcpcd[4777]: eth0: executing `/usr/libexec/dhcpcd-run-hooks', reason STOP

tytower

#16 Post by tytower »

Bump
any new takers?

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

#17 Post by gyro »

Hi,

I'm currently connected to the Internet via a TP-LINK TL-WN727N usb wi-fi dongle.
I am running Dpup Expimo 5.X.3.4.12 as a frugal install.
So these things can work.

My device is not the same as yours, but a couple of suggestions might help:

1) Don't use the CD, find a version of Puppy that recognises it when you plug it in. (In a terminal window, type "dmesg", after plugging it in.)

2) Then use "Puppy Network Wizard" to configure the device.
If the device doesn't show up in "Puppy Network Wizard" then it hasn't been properly recognised.

gyro

tytower

#18 Post by tytower »

HELP !


I'm still trying to get this sorted

I'm using Puppy 5.4.3 updated so I have the right driver loaded and the device is recognised and configured but though it says it is connected to the router it will not send or get any packets from or to it. I can do it with a cable fine but not wireless ?

Here is an error log I found

I just need someone who knows whats going on with these things to point out what is wrong !

Code: Select all

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:50 errors:0 dropped:0 overruns:0 frame:0
          TX packets:50 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:4378 (4.2 KiB)  TX bytes:4378 (4.2 KiB)

wlan0     Link encap:Ethernet  HWaddr 00:9E:95:9C:4D:1F  
          inet addr:10.1.1.2  Bcast:10.255.255.255  Mask:255.0.0.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)


Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         10.1.1.1        0.0.0.0         UG    0      0        0 wlan0
10.0.0.0        0.0.0.0         255.0.0.0       U     0      0        0 wlan0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo

DNS:
nameserver 8.8.8.8
nameserver 8.8.4.4

wlan0     Access Point/Cell: 00:00:00:00:00:00
wlan0     Mode:Managed
wlan0     2 key sizes : 40, 104bits
          4 keys available :
		[1]: off
		[2]: off
		[3]: off
		[4]: off
          Current Transmit Key: [1]
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State      
tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN     
EXIT="OK"
/usr/sbin/ipinfo: line 115: 12926 Terminated              yaf-splash -close never -bg orange -text "$(gettext 'Please wait, probing...')"
134744072
134743044
134744072
134743044
134744072
134743044
Configuring interface wlan0 to network DLINK with iwconfig...
/usr/sbin/net-setup.sh: line 993: 18657 Terminated              gtkdialog3 --program NETWIZ_Connecting_DIALOG
134744072
134743044
Configuring interface wlan0 to network DLINK with iwconfig...
/usr/sbin/net-setup.sh: line 993: 20364 Terminated              gtkdialog3 --program NETWIZ_Connecting_DIALOG
rtl8187
134744072
134743044
Configuring interface wlan0 to network DLINK with iwconfig...
wlan0     No such device

Waiting time 2 seconds
wlan0     No such device

Waiting time 4 seconds
/usr/sbin/net-setup.sh: line 993: 30824 Terminated              gtkdialog3 --program NETWIZ_Connecting_DIALOG
cdromreadraw: Input/output error
mount: block device /dev/sr0 is write-protected, mounting read-only
mount: block device /dev/sr0 is write-protected, mounting read-only

User avatar
pemasu
Posts: 5474
Joined: Wed 08 Jul 2009, 12:26
Location: Finland

#19 Post by pemasu »

In console, run pmodemdiag and post the created tarball here.
It will be created to the /root.

tytower

#20 Post by tytower »

No other error messages that I saw
Last edited by tytower on Tue 15 Jan 2013, 20:54, edited 1 time in total.

Post Reply