compaq evo no pcmcia?

Message

rcrsn51 · #21 Post by **rcrsn51** » Tue 21 Mar 2017, 16:31

The "interface name" is the WiFi device name you saw in step 1, like "wlan0".

If step 3 worked, then your hardware is OK.

What about step 4?

In step 5, make sure that you are spelling the filename resolv.conf correctly. This file should be automatically created. Browse to the /etc folder and look for it.

specialpuppy · #22 Post by **specialpuppy** » Tue 21 Mar 2017, 16:41

step 4 worksno errors no drops no collisions etc.

rcrsn51 · #23 Post by **rcrsn51** » Tue 21 Mar 2017, 16:43

specialpuppy wrote:step 4 works

Please state EXACTLY what IP address wlan0 has.

specialpuppy · #24 Post by **specialpuppy** » Tue 21 Mar 2017, 16:51

link encap: Ethernet HWaddr 00:1E:2A:09:DO:7A
inet addr:169.254.20.1 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 METRIC:1

rcrsn51 · #25 Post by **rcrsn51** » Tue 21 Mar 2017, 16:58

specialpuppy wrote:169.254.20.1

This is a bogus IP address, so you are NOT getting a valid connection.

You can check this yourself. Connect by Ethernet and run: ifconfig eth0. Then check the /etc/resolv.conf file to see what it should contain.

Unfortunately, I don't own any PCMCIA hardware, so I have no other suggestions on how to fix this.

specialpuppy · #26 Post by **specialpuppy** » Tue 21 Mar 2017, 17:03

roger that. thanks for your help.

specialpuppy · #27 Post by **specialpuppy** » Tue 21 Mar 2017, 23:44

ifconfig=# ifconfig
eth0 Link encap:Ethernet HWaddr 00:08:02:D4:C1:04
inet addr:192.168.1.165 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4966 errors:0 dropped:2 overruns:0 frame:0
TX packets:3253 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6219495 (5.9 MiB) TX bytes:370869 (362.1 KiB)
Interrupt:11

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

wlan0 Link encap:Ethernet HWaddr 00:1E:2A:09:D0:7A
inet addr:169.254.129.139 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:502 (502.0 B) TX bytes:3454 (3.3 KiB)

greengeek · #28 Post by **greengeek** » Wed 22 Mar 2017, 07:31

specialpuppy wrote:ifconfig=# ifconfig
eth0 Link encap:Ethernet HWaddr 00:08:02:D4:C1:04
inet addr:192.168.1.165 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4966 errors:0 dropped:2 overruns:0 frame:0
TX packets:3253 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6219495 (5.9 MiB) TX bytes:370869 (362.1 KiB)
Interrupt:11

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

wlan0 Link encap:Ethernet HWaddr 00:1E:2A:09:D0:7A
inet addr:169.254.129.139 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:502 (502.0 B) TX bytes:3454 (3.3 KiB)

Did you have a network cable connected when you did this? If so did you try the wifi connection with the cable removed?

specialpuppy · #29 Post by **specialpuppy** » Wed 22 Mar 2017, 15:45

yes it was connected and here it is NOT connected
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:08:02:D4:C1:04
inet addr:192.168.1.165 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:21851 errors:0 dropped:33 overruns:0 frame:0
TX packets:12344 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:10022418 (9.5 MiB) TX bytes:2398401 (2.2 MiB)
Interrupt:11

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

wlan0 Link encap:Ethernet HWaddr 00:1E:2A:09:D0:7A
inet addr:169.254.129.139 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3 errors:0 dropped:0 overruns:0 frame:0
TX packets:917 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:502 (502.0 B) TX bytes:371878 (363.1 KiB)

rcrsn51 · #30 Post by **rcrsn51** » Thu 23 Mar 2017, 13:02

@specialpuppy: Have you addressed the issue of WEP encryption and whether your WiFi router is configured to use it? If this is a G-mode card, it may only work with WEP.

Hopefully, one of the PCMCIA experts will comment on this.

I notice that your Ethernet port is getting the high address 192.168.1.165. Is that a static IP address set by your router? Is your router accepting wireless connections for other devices, like Windows machines?

specialpuppy · #31 Post by **specialpuppy** » Sat 25 Mar 2017, 00:30

yes all my other devices have a GOOD ip address???

rcrsn51 · #32 Post by **rcrsn51** » Sun 26 Mar 2017, 13:50

rcrsn51 wrote:@specialpuppy: Have you addressed the issue of WEP encryption and whether your WiFi router is configured to use it? If this is a G-mode card, it may only work with WEP.

Any update on this?

[Edit] I guess not.

specialpuppy · #33 Post by **specialpuppy** » Tue 28 Mar 2017, 20:21

thats why i pasted what i had. Im not sure how to do what you are implying?
sorry.
steve

rcrsn51 · #34 Post by **rcrsn51** » Tue 28 Mar 2017, 20:31

WiFi adapters and routers use different types of encryption to communicate. Your old PCMCIA card may only work with WEP. You can google WEP for more details.

You need to open your router's administration web page to see what kind of encryption it supports. It is probably at 192.168.1.0.

I don't think that you have identified the Puppy connection tool that you are using. Does it allow you to specifically request WEP encryption?

This would be easier if you scrapped the PCMCIA card and got a modern USB WiFi adapter that would be compatible with Slacko 630.

Mike Walsh · #35 Post by **Mike Walsh** » Tue 28 Mar 2017, 23:31

While I fully accept what Bill is saying about the PCMCIA card (it is, after all, considered ancient tech by today's standards), I just want to mention that my own NetGear WPN-511 is connecting through our router via WPA2 encryption.....and auto-connects every time without fail.

However, it might work out better going the USB adapter route. I can recommend two that'll definitely work:-

http://uk.tp-link.com/products/details/TL-WN725N.html

The TP-Link WN-725N is a 'nano'-sized dongle, which can be plugged in and forgotten about, it's that small. For all that it has a very good range, and Bill does a range of drivers for the 'r8188eu' chipset it has.....although the chipset has been supported in the Linux kernel since Tahrpup's 3.14.20 kernel that I know of.

Or, there's this 'mini' design:-

http://www.netgear.co.uk/home/products/ ... 3100M.aspx

.....from NetGear, again. This one uses the in-kernel 'rtl8192cu' driver; I use this one myself in Slacko 5.6.0, and it connects straightaway using Simple Network Setup.

Bill does a range of 'rtl8192cu' drivers for various kernels; Slacko 630's version is at the top of the list in this thread:-

http://www.murga-linux.com/puppy/viewtopic.php?t=100675

Hope some of that helps!

Mike.

rcrsn51 · #36 Post by **rcrsn51** » Wed 29 Mar 2017, 00:58

Since Mike has confirmed that this should NOT be a WEP issue, your next step should be to reboot everything, including the router.

specialpuppy · #37 Post by **specialpuppy** » Wed 29 Mar 2017, 03:15

ok thanks gentlemen, ill give it a try and let you know.

Mike Walsh · #38 Post by **Mike Walsh** » Wed 29 Mar 2017, 12:55

Yes, I agree with Bill on that one. Rebooting your router should be performed on a regular basis anyway; I reboot ours about once a month, and it's surprising how much more responsive everything seems after doing so.

Mike.

specialpuppy · #39 Post by **specialpuppy** » Thu 30 Mar 2017, 01:50

Well, thanks for all your helpbut... I just think I'll give up on getting this to work with a wifi card and get a usb wifi.

Cheers Steve

Mike Walsh · #40 Post by **Mike Walsh** » Thu 30 Mar 2017, 13:23

Hi again, Steve.

That's probably a wise choice..!

Remember, the adapters that I've listed I know will work. If you want to try something else (and 'el cheapos' from the Far East are not a very good idea), use this site:-

https://wikidevi.com/wiki/Main_Page

.....to try and figure out the chipset for any given device before you purchase. If you need any help, just give me a shout.

I always take the view that if I have to purchase something like this, I'd rather take my time, do my research, find something of good quality that I know will work, and, if necessary, save up and pay a bit more for it. I'd sooner make this kind of purchase once.....and be done with it.

Mike.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

compaq evo no pcmcia?