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 Tue 22 Jul 2014, 15:57
All times are UTC - 4
 Forum index » Advanced Topics » Hardware » Networking » Wireless
5.2 lucid and rtl8180
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 1 [7 Posts]  
Author Message
tim24

Joined: 11 Mar 2011
Posts: 3

PostPosted: Thu 17 Mar 2011, 16:04    Post subject:  5.2 lucid and rtl8180
Subject description: ndiswrapper is the ticket with net8180.INF & rtl8180.sys
 

after moving from 4.3.1 to 5.2, my lynksis wireless b card would not stay connected.

remembering ndiswrapper use on dsl linux, I got the card to work.

find the driver files for xp or lower windows system from the realtek archives and save them in root. These files are NET8180.INF and rtl8180.sys.

follow the instructions on the classic lan setup wizard and select ndiswrapper with the card inserted. blacklist the rtl8180 driver and follow prompts to select the NET8180.INF file

http://218.210.127.131/downloads/downloadsView.aspx?Langid=1&PNid=6&PFid=6&Level=5&Conn=4&DownTypeID=3&GetDown=false#2
Back to top
View user's profile Send private message 
growler


Joined: 24 Mar 2008
Posts: 209
Location: Kapiti - New Zealand

PostPosted: Sun 24 Apr 2011, 21:40    Post subject: rtl8187SE  

I have an MSI Wind - that was working ok with 4.3.1 but I thought I should update to a later kernel so downloaded lupu 5.25. However, I am now unable to use the wireless. The card was trouble and required fresh compilation of a driver for 4.3.1 but the machine/card is not that new now so I wasn't expecting issues with a more recent kernel.

The card is a RTL3187SE it is detected as a r8180 by the network wizard, but the description as RTL8187SE is correct and lsmod reports module r8187SE is loaded. It certainly finds networks ok but on applying for an IP address with DHCP it doesn't get a lease.

I have applied tempestuous's hotfix for 5.1 (after it didn't work intially and searching the forums) but still no joy.

I installed Pwireless2 and this actually reports no wireless interface detected??

Appreciate any pointers - would hate to have to go back to ndiswrapper.
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5216
Location: Australia

PostPosted: Mon 25 Apr 2011, 00:18    Post subject:  

growler, I suggest you first have a look at the output of "dmesg" looking for any errors relating to how the r8187se driver loaded.

If nothing bad there, it might just be the crappy version of dhcpcd included in Puppy 5.1/5.2.
See my post here about how to install jemimah's updated dhcpcd -
http://www.murga-linux.com/puppy/viewtopic.php?p=515521#515521
Back to top
View user's profile Send private message 
growler


Joined: 24 Mar 2008
Posts: 209
Location: Kapiti - New Zealand

PostPosted: Mon 25 Apr 2011, 01:22    Post subject:  

Hi Tempestuous,

Many thanks for looking at my problems once more!

Output of dmesg:
Quote:

r8187se: module is from the staging directory, the quality is unknown, you have been warned
r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
r8169 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
r8169 0000:01:00.0: setting latency timer to 64
r8169 0000:01:00.0: irq 27 for MSI/MSI-X
eth0: RTL8102e at 0xf8162000, 00:21:85:47:27:9d, XID 14a00000 IRQ 27
ieee80211_crypt: registered algorithm 'NULL'
ieee80211_crypt: registered algorithm 'TKIP'
ieee80211_crypt: registered algorithm 'CCMP'
ieee80211_crypt: registered algorithm 'WEP'

Linux kernel driver for RTL8180 / RTL8185 based WLAN cards
Copyright (c) 2004-2005, Andrea Merello
r8180: Initializing module
r8180: Wireless extensions version 22
r8180: Initializing proc filesystem
r8180: Configuring chip resources
r8180 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
r8180 0000:02:00.0: setting latency timer to 64
r8180: Channel plan is 2

Dot11d_Init()
r8180: MAC controller is a RTL8187SE b/g
r8180: usValue is 0x100

r8180: EEPROM version 104
r8180: WW:**PLEASE** REPORT SUCCESSFUL/UNSUCCESSFUL TO Realtek!
r8180: IRQ 17
r8180: Driver probe completed

HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
HDA Intel 0000:00:1b.0: irq 28 for MSI/MSI-X
HDA Intel 0000:00:1b.0: setting latency timer to 64
hda_codec: ALC1200: BIOS auto-probing.
r8169: eth0: link down
r8169: eth0: link down
r8180: Bringing up iface
r8180: Card successfully reset
r8180: WIRELESS_MODE_G

ip_tables: (C) 2000-2006 Netfilter Core Team
nf_conntrack version 0.5.0 (16006 buckets, 64024 max)
CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or
sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
r8169: eth0: link up
r8169: eth0: link up
r8180: Bringing up iface
r8180: Card successfully reset
r8180: WIRELESS_MODE_G

r8169: eth0: link up
[drm] Initialized drm 1.1.0 20060810
i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
i915 0000:00:02.0: setting latency timer to 64
[drm] set up 7M of stolen space
composite sync not supported
[drm] initialized overlay support
composite sync not supported
Console: switching to colour frame buffer device 128x37
fb0: inteldrmfb frame buffer device
registered panic notifier
[drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
composite sync not supported
composite sync not supported
atkbd.c: Unknown key pressed (translated set 2, code 0xf7 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e077 <keycode>' to make it known.
atkbd.c: Unknown key released (translated set 2, code 0xf7 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e077 <keycode>' to make it known.
atkbd.c: Unknown key pressed (translated set 2, code 0xf7 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e077 <keycode>' to make it known.
atkbd.c: Unknown key released (translated set 2, code 0xf7 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e077 <keycode>' to make it known.
r8169: eth0: link up
r8180: Bringing up iface
r8180: Card successfully reset
r8180: WIRELESS_MODE_G

r8180: Bringing up iface
r8180: Card successfully reset
r8180: WIRELESS_MODE_G

r8180: Setting SW wep key
r8180: Bringing up iface
r8180: Card successfully reset
r8180: WIRELESS_MODE_G

Linking with bunker: channel is 2
Linking with bunker: channel is 2
r8180: Setting SW wep key
r8180: Setting SW wep key
Associated successfully
Using G rates


The first line

r8187se: module is from the staging directory, the quality is unknown, you have been warned

sounds like it might be an issue? Also it is referring all the time to r8180 not r8187SE ??? R8169 is the hardwire - thanks goodness for good old ethernet! I have been using WEP since you helped me with this driver for 4.3.1 and I had a few issues with WPA-PSK

I got Jermiah's dhcpd and copied it back to /usr/sbin/dhcpd but same story....

Many thanks AGAIN!!
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5216
Location: Australia

PostPosted: Tue 26 Apr 2011, 05:13    Post subject:  

Well your dmesg results look fine.

growler wrote:
it is referring all the time to r8180 not r8187SE ???

That's no problem; Linux wifi drivers often report their name as different than the name of the actual driver. And in this particular case, "r8180" is the old Realtek RTL8180 driver upon which the rtl8187se driver is based.

At the outset I suggest you upgrade to the improved version of dhcpcd, which I have just posted here -
http://www.murga-linux.com/puppy/viewtopic.php?p=448997#448997
Reboot, and see if you get a better result.

If not, you then need to do some troubleshooting and experimentation.
It would be a good idea to turn off all encryption at your wifi router, and see if you can connect in this unencrypted state. If so, it means the rtl8187se driver is basically working.

Then try both WPA and WPA2 encryption. You may find that one works, while the other doesn't.

Also, try changing the HIDE/BROADCAST SSID setting at your router. Apparently the "BROADCAST SSID" setting is best for security, which is counter-intuitive.

And finally, experiment with the "AP Scan" value in the Network Wizard: Hidden SSID / Broadcast SSID / Driver.
Back to top
View user's profile Send private message 
growler


Joined: 24 Mar 2008
Posts: 209
Location: Kapiti - New Zealand

PostPosted: Sat 30 Apr 2011, 19:35    Post subject: Further troubleshooting  

Hi Tempestuous,

I tried your updated dhcp client but still no joy so I am into messing around with the router settings to see if I can get a combination of settings to work.

I will report back...

Thanks again
Back to top
View user's profile Send private message 
growler


Joined: 24 Mar 2008
Posts: 209
Location: Kapiti - New Zealand

PostPosted: Sat 07 May 2011, 01:04    Post subject: Ouch use Hex WEP password  

For your entertainment ....

The WEP password needs to be in hex when using the puppy network wizard - apologies for being such a dummy ... I knew this already and just needed to re-learn!!

Sorry to waste your time Tempestuous - I can confirm that RTL8187SE on MSI Wind works famously with 5.2

Thanks again for all your help
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 1 of 1 [7 Posts]  
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.0664s ][ Queries: 11 (0.0037s) ][ GZIP on ]