Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Fri 01 Aug 2014, 20:55
All times are UTC - 4
 Forum index » Advanced Topics » Hardware » Networking » Wireless
failure of r8187 with pup 412 and 421 using WPA
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 2 [21 Posts]   Goto page: 1, 2 Next
Author Message
davesurrey

Joined: 05 Aug 2008
Posts: 1201
Location: UK

PostPosted: Thu 03 Dec 2009, 19:19    Post subject:  failure of r8187 with pup 412 and 421 using WPA  

Having problems getting wpa to work with a friend's laptop.
It has Windows Vista and I've installed puppy 431 both of which can find a wpa AP and connect to the net.

But with Puppy 412 and 421 it doesn't work.

Did
Code:
cat /proc/bus/usb/devices
which returned
Quote:
Vendor=0bda
ProdID=8189 rev2.00
Product= RTL8187B_WLA_NAdapter


(note it really is spelled NAdapter in the last line)

With Puppy 431 it uses the rtl8187b driver.

Searching through the forum I found that with the 2.6.25.16 kernel it needs tempetuous's r8187-B-FEB09-k2.6.25.16.pet which I have installed, done modprobe r8187, but even after a reboot it still shows as Module rtl8187 in Network Manager.

Scan finds local networks but after putting in the Shared Key it fails to acquire a WPA connection.

Has anyone got this to work in 421 or 412?
Anyone can help please?
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5218
Location: Australia

PostPosted: Fri 04 Dec 2009, 02:42    Post subject:  

davesurrey wrote:
modprobe r8187, but even after a reboot it still shows as Module rtl8187 in Network Manager.


It appears that Puppy's PREFLIST mechanism is not working, and this has only come to light recently.
rerwin is looking for a fix. See progress here
http://www.murga-linux.com/puppy/viewtopic.php?p=368431#368431
Back to top
View user's profile Send private message 
davesurrey

Joined: 05 Aug 2008
Posts: 1201
Location: UK

PostPosted: Fri 04 Dec 2009, 07:54    Post subject:  

tempestuous:

Thanks for the reply but rerwin seems to be looking at puppy 431 with the 2.6.30.X kernel.

As I said wifi in my 431 is working fine. It's puppy 421 and 412 where I have the problem.

I checked in puppy 412 and found:

/etc/modprobe.conf has a long line to install r8187.
there was no
Code:
remove rtl8187
so I added one

/etc/rc.d/modules.config has
Code:
rtl8187:r8187
in the PREFLIST.

/tmp/pup_event_modprobe.conf doesn't show any blacklist of rtl8187

In the Network manager if I go to load a module I see r8187 in the module list and when I load it, it confirms loaded.

Checking in Bootmanager the r8187 also seems to be loaded.

So, are you saying that pup 412 and 420 also have this problem with PREFLIST?

Thanks
Dave
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5218
Location: Australia

PostPosted: Sat 05 Dec 2009, 01:19    Post subject:  

davesurrey wrote:
So, are you saying that pup 412 and 420 also have this problem with PREFLIST?

In theory, yes. The PREFLIST mechanism is related to Puppy's version of udev (pup_event) which is common to all official Puppy versions from kernel 2.6.25.16 onwards.

davesurrey wrote:
As I said wifi in my 431 is working fine.

That's because the standard kernel module works fine with that kernel. There are no competing modules for the same device in this situation.
Back to top
View user's profile Send private message 
davesurrey

Joined: 05 Aug 2008
Posts: 1201
Location: UK

PostPosted: Sat 05 Dec 2009, 06:57    Post subject:  

Thanks tempestuous for the explanation.

I find it surprising that this hasn't been picked up until recently if it goes back that far but let's hope rerwin will fix this.

Thanks again for all your efforts for drivers etc.

Dave
Back to top
View user's profile Send private message 
davesurrey

Joined: 05 Aug 2008
Posts: 1201
Location: UK

PostPosted: Wed 09 Dec 2009, 07:08    Post subject:  

@tempestuous

Richard, rerwin, and I have had a series of PM and exchanged files and he is now of the conclusion that the problems I am having with r8187 and 412 (2.6.25.16 kernel) are not to do with any preflist issue.

The modules.alias file shows no duplicates of the hardware ID and also show that r8187 is installed. Checking Bootmanager all seems as would be expected with r8187 available and not blacklisted.

So may I ask you to have another look at this. Please let me know what I can do to help you to help me.

Thanks
Dave
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5218
Location: Australia

PostPosted: Wed 09 Dec 2009, 16:44    Post subject:  

OK, I looked into this further.
I see now that the standard rtl8187 driver in Puppy 4.1/4.2 is not compatible with your device ID of 0bda:8189. So the r8187 driver is loading (as it should) ...
but this driver appears to report itself to the Network Manager as "rtl8187". That's what caused the confusion.

And this problem is probably also messing up WPA configuration in the Network Wizard.
First we need to check exactly how the Network Wizard sees the r8187 driver. Please run this command -
Code:
readlink /sys/class/net/wlan0/device/driver

Obviously replace "wlan0" if that's not your wifi interface.
Is the result of this command "rtl8187"? If so, the solution should be a simple change to the Network Wizard.
Back to top
View user's profile Send private message 
davesurrey

Joined: 05 Aug 2008
Posts: 1201
Location: UK

PostPosted: Wed 09 Dec 2009, 23:20    Post subject:  

Thanks for getting back to me.

It does use wlan0.

Your readlink cmd returned:
Code:
../../../../../../bus/usb/drivers/rtl8187


HTH
Dave
Back to top
View user's profile Send private message 
8-bit


Joined: 03 Apr 2007
Posts: 3357
Location: Oregon

PostPosted: Wed 09 Dec 2009, 23:56    Post subject:  

This is not a fix for blacklisting a module, but when I want one to be bypassed that is loaded I just rename the module to old_name of module.
That way, the module is not found, bypassed, and the correct module is loaded.
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5218
Location: Australia

PostPosted: Thu 10 Dec 2009, 03:12    Post subject:  

8-bit, the problem in this case is not conflicting modules as I originally suspected, it's a simple case of wpa_supplicant configuration.

davesurrey, I just posted a fix here -
http://www.murga-linux.com/puppy/viewtopic.php?p=252339#252339

If WPA connections still fail, all is not lost. You can still try pre-loading some of the encryption-related modules, and run the wpa_supplicant command manually. Let me know if you need further help.
Back to top
View user's profile Send private message 
davesurrey

Joined: 05 Aug 2008
Posts: 1201
Location: UK

PostPosted: Thu 10 Dec 2009, 14:44    Post subject:  

tempestuous,
I installed your NetWiz-fix.pet on a fresh install of puppy 412 (new save file) just in case anything in the save file would cause any problems.

Sorry to say that I experienced the same problem,

ie Scan finds my AP.
But when I put in my shared key (for WPA) and it goes to "Acquiring wpa connection" it crashes. ie the mouse freezes and I can't get any response eg ctlr+alt+backspace so have to force a power down.

Before this I checked in Bootmanager.

It tells me I have a pref rtl8187:r8187.
No sign of rtl8187 being installed but shows that r8187 is available.

However Network Manager still shows rtl8187 in the gui.

So yes I'd appreciate some more help please.

Cheers
Dave
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5218
Location: Australia

PostPosted: Fri 11 Dec 2009, 04:04    Post subject:  

davesurrey wrote:
It tells me I have a pref rtl8187:r8187.
No sign of rtl8187 being installed but shows that r8187 is available.

Don't worry about module preferences. The newly installed r8187 is the only driver (under kernel 2.6.25.16) which is compatible with your device, so there's no chance of a conflict.

Now it's time for some troubleshooting.
First we must check that your version of Puppy has a suitable version of wpa_supplicant.
The r8187 driver requires the old "ipw" driver interface, which was definitely enabled in older versions of Puppy with wpa_supplicant v0.5.10 (I should know, I contributed that wpa_supplicant package).
Check by running this command
Code:
wpa_supplicant

hopefully you will see this -
Code:
 ...
drivers:
  wext = Linux wireless extensions (generic)
  hostap = Host AP driver (Intersil Prism2/2.5/3)
  atmel = ATMEL AT76C5XXx (USB, PCMCIA)
  ipw = Intel ipw2100/2200 driver (old; use wext with Linux 2.6.13 or newer)
  wired = wpa_supplicant wired Ethernet driver

If you see "ipw" listed as such, move on to the next step.
But at some point in Puppy's development wpa_supplicant was upgraded to v0.6.0 and the "ipw" interface was not enabled. If so, download and install the older version -
http://distro.ibiblio.org/pub/linux/distributions/puppylinux/pet_packages-4/wpa_supplicant-0.5.10.pet

Now it's time to manually configure your WPA configuration file.
Open /etc/network-wizard/wireless/wpa_profiles/wpa_supplicant.conf
in Geany (or if your router uses WPA2, open wpa_supplicant2.conf)
Modify this file to include your SSID and Personal Security Key (PSK). Save.

Now run the command to connect -
Code:
wpa_supplicant -i wlan0 -D ipw -c /etc/network-wizard/wireless/wpa_profiles/wpa_supplicant.conf -dd

If you see a successful connection reported, go ahead and open a second xterminal, and do this -
Code:
rm -f /var/lib/dhcpcd/*.info
rm -f /var/run/*.pid
dhcpcd -t 30 -h puppypc -d wlan0


If no successful connection, there's still a chance that an earlier version of wpa_supplicant is necessary - as reported by forum member mikeb. So terminate the wpa_supplicant process with Ctrl>c, then download and install
http://distro.ibiblio.org/pub/linux/distributions/puppylinux/pet_packages-4/wpa_supplicant-0.5.8-rt73patch-1.pet
A reboot is probably a good idea before trying the wpa_supplicant command again.
Back to top
View user's profile Send private message 
davesurrey

Joined: 05 Aug 2008
Posts: 1201
Location: UK

PostPosted: Fri 11 Dec 2009, 09:04    Post subject:  

wpa_supplicant told me I had v0.5.8 and I confirmed under the driver section there was an ipw entry.

Added my ssid and psk into /etc/network-wizard/wireless/wpa_profiles/wpa_supplicant.conf and saved it.

Ran the long supplicant cmd but it continued trying and failing to make a connection. So I terminated it with Ctlr+c.

Just in case other experiments had corrupted wpa_supplicant I downloaded the wpa_supplicant-0.5.10.pet and installed it.

No difference.

So did a new install, new save file.
Installed r8187 driver, your NetWiz_fix.pet, added my AP parameters to /wpa_supplicant.conf file and did long wpa_supplicant cmd again. Same problem. Also tried without your NetWiz-fix.pet just in case. Seemed to produce same results.

Large amount of information passing the terminal but did spot
"no keys have been configured-skip key clearing"
Please see attached. (wpa supp terminal report)

Then I added the 0..5.8-rt73patch.pet rebooted and ran long cmd again.
Didn't see the "no keys...." message but still very similar result.
Please see attached. (with rt73 patched)

Sorry but I have always had a brain-clog in doing cut and paste in Linux, especially from the terminal.

I saw somewhere recently that it was suggested not to use a psk in ordinary ascii but in hex instead. eg I am using eg "psk=fred_bloggs" rather than something like "4383aed0272bd8d67dbaf9ba". Hope that makes sense. But I wouldn't know how to find what my ascii psk translates into hex.

HTH
Dave
with rt73 patch pet.txt.tar.gz
Description 
gz

 Download 
Filename  with rt73 patch pet.txt.tar.gz 
Filesize  534 Bytes 
Downloaded  307 Time(s) 
wpa_supplicant terminal report.txt.tar.gz
Description 
gz

 Download 
Filename  wpa_supplicant terminal report.txt.tar.gz 
Filesize  582 Bytes 
Downloaded  301 Time(s) 
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5218
Location: Australia

PostPosted: Fri 11 Dec 2009, 09:49    Post subject:  

We're running out of possibilities, but it would be worth checking whether encryption-related modules are loaded.
Once booted, run "lsmod" and check that ieee80211_crypt_tkip-rtl is loaded. (I'm working on the assumption you're using WPA encryption, not WPA2).
If anyone is confused about the name of this module, relax, it's unique to the older Realtek proprietary drivers.
If it's not loaded, do so -
Code:
modprobe ieee80211_crypt_tkip-rtl

Now try the wpa_supplicant command again.
Back to top
View user's profile Send private message 
davesurrey

Joined: 05 Aug 2008
Posts: 1201
Location: UK

PostPosted: Fri 11 Dec 2009, 10:20    Post subject:  

Yes using wpa not wpa2.

Okay I found ieee80211_crypt_tkip_rtl. Note not ieee80211_crypt_tkip-rtl.

Not trying to be pedantic but just want to make sure about anything and everything at this stage.

Did a
Code:
modprobe ieee80211_crypt_tkip-rtl
anyway and also
Code:
modprobe ieee80211_crypt_tkip_rtl
then wpa long cmd and got a very different looking report on the terminal including what looked like some hex encryption..the psk?

However it then froze the system. Sad

To eliminate what I can I've even re-booted the router to no avail.

One last point I just looked and can't find any /var/run/wpa_supplicant file which wpa_supplicant.conf talks about.

Dave
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 1 of 2 [21 Posts]   Goto page: 1, 2 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Hardware » Networking » Wireless
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0984s ][ Queries: 13 (0.0062s) ][ GZIP on ]