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 Thu 17 Apr 2014, 02:23
All times are UTC - 4
 Forum index » Advanced Topics » Hardware
Wireless driver packages for Puppy2
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 4 of 7 [105 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6, 7 Next
Author Message
tempestuous

Joined: 10 Jun 2005
Posts: 5139
Location: Australia

PostPosted: Wed 28 Jun 2006, 09:41    Post subject:  

Oops. Yes, all revised dotpups were corrupt. Fixed now.
Back to top
View user's profile Send private message 
displacedtexan

Joined: 06 Jul 2006
Posts: 3

PostPosted: Thu 06 Jul 2006, 01:05    Post subject: Where's ipw394*.pup?  

New puppy user... I was looking for a Linux distro that was lightning fast to boot up and shut down and I think I have found it with Puppy!

Now my probably... trying to install my Laptop's wireless card from:
http://www.dotpups.de/dotpups/Wifi/wireless-drivers/

is it just me, or is the ipw394*.pup file missing from the above link? I see ipw3945_README.txt but not the .pup

thanks...

Jason
Back to top
View user's profile Send private message 
smog

Joined: 13 Jun 2006
Posts: 134

PostPosted: Thu 06 Jul 2006, 08:37    Post subject:  

Nevermore,

Don't give up, I couldn't get my internal wireless to work, despite trying very hard!! so I bought a netgear pcmcia card. BUT, thanks to tempestuous' help, within 2 days of buying the pcmcia card, I did get the internal wireless card working.

Are you usng WEP? If so, are you sure you have set it up properly?

I found that setting the WEP key as iwconfig "key restricted MYWEPKEY" i.e. not just "key MYWEPKEY" solved my problem.

Also I spent a long time setting up iwconfig on wlan0 but it turned out I should have been using eth1.

Hope you get it working.
Back to top
View user's profile Send private message 
MU


Joined: 24 Aug 2005
Posts: 13642
Location: Karlsruhe, Germany

PostPosted: Thu 06 Jul 2006, 09:59    Post subject:  

Quote:
is it just me, or is the ipw394*.pup file missing from the above link? I see ipw3945_README.txt but not the .pup


Updated the downloads with this driver.
Mark
Back to top
View user's profile Send private message Visit poster's website 
pakt


Joined: 04 Jun 2005
Posts: 1089
Location: Sweden

PostPosted: Sat 08 Jul 2006, 08:51    Post subject:  

I have repeated my tests of the bcm43xx-softmac.pup in Puppy 2.01. The results are different from what I reported to tempestuous in a PM, but, unfortunately, the dotpup still doesn't work. Using ndiswrapper does work well though.

This is a summary of printouts during testing.
The Dell Inspiron 510m laptop uses the Broadcom BCM94306 chip (802.11b/g). It has built-in 10/100 cable ethernet which was disconnected during testing.

# modprobe bcm43xx

dmesg shows:
Quote:
ieee80211_crypt: no version for "struct_module" found: kernel tainted.
ieee80211_crypt: registered algorithm 'NULL'
ieee80211: 802.11 data/management/control stack, git-1.1.7
ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
bcm43xx driver
ACPI: PCI Interrupt 0000:01:03.0[A] -> Link [LNKB] -> GSI 5 (level, low) -> IRQ 5
bcm43xx: Chip ID 0x4306, rev 0x3
bcm43xx: Number of cores: 5
bcm43xx: Core 0: ID 0x800, rev 0x4, vendor 0x4243, enabled
bcm43xx: Core 1: ID 0x812, rev 0x5, vendor 0x4243, disabled
bcm43xx: Core 2: ID 0x80d, rev 0x2, vendor 0x4243, enabled
bcm43xx: Core 3: ID 0x807, rev 0x2, vendor 0x4243, disabled
bcm43xx: Core 4: ID 0x804, rev 0x9, vendor 0x4243, enabled
bcm43xx: PHY connected
bcm43xx: Detected PHY: Version: 2, Type 2, Revision 2
bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2)
bcm43xx: Radio turned off
bcm43xx: Radio turned off

Quote:
sh-3.00# iwconfig eth1
eth1 IEEE 802.11b/g ESSID:off/any Nickname:"Broadcom 4306"
Mode:Managed Access Point: Invalid Bit Rate=1 Mb/s
RTS thr:off Fragment thr:off
Encryption key:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

# iwconfig eth1 essid MyAP
# iwconfig eth1
eth1 IEEE 802.11b/g ESSID:"MyAP" Nickname:"Broadcom 4306"
Mode:Managed Access Point: Invalid Bit Rate=1 Mb/s
RTS thr:off Fragment thr:off
Encryption key:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

# dhcpcd -t 30 -h puppypc -d eth1
dhcpcd: MAC address = 00:90:96:be:f5:41
# ifconfig eth1
eth1 Link encap:Ethernet HWaddr 00:90:96:BE:F5:41
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)
Interrupt:11 Base address:0x8000

I tried using a static IP address, but the interface still didn't work.

I repeated the test with fw I got using fwcutter on Dell's latest XP driver, but I got the same results Sad

Using ndiswrapper with two versions of XP drivers worked well.

dmesg output with older driver:
Quote:
ndiswrapper version 1.15 loaded (preempt=no,smp=no)
ndiswrapper: driver bcmwl5 (Broadcom,07/17/2003, 3.30.15.0) loaded
ACPI: PCI Interrupt 0000:01:03.0[A] -> Link [LNKB] -> GSI 5 (level, low) -> IRQ 5
ndiswrapper: using irq 5
wlan0: vendor: ''
wlan0: ndiswrapper ethernet device 00:90:96:be:f5:41 using driver bcmwl5, 14E4:4320.5.conf
wlan0: encryption modes supported: WEP; TKIP with WPA; AES/CCMP with WPA

Quote:
# iwconfig wlan0
wlan0 IEEE 802.11g ESSID:"MyAP"
Mode:Managed Frequency:2.412 GHz Access Point: 00:11:2F:9D:1F:4A
Bit Rate:54 Mb/s Tx-Power:14 dBm
RTS thr:2347 B Fragment thr:2346 B
Encryption key:off
Power Management:off
Link Quality:100/100 Signal level:-24 dBm Noise level:-256 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

# ifconfig wlan0
wlan0 Link encap:Ethernet HWaddr 00:90:96:BE:F5:41
inet addr:192.168.0.125 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:90239 errors:0 dropped:0 overruns:0 frame:0
TX packets:72610 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:128777710 (122.8 MiB) TX bytes:6776522 (6.4 MiB)
Interrupt:5 Memory:fcffc000-fcffe000


dmesg output with latest Dell XP driver:
Quote:
ndiswrapper version 1.15 loaded (preempt=no,smp=no)
ndiswrapper: driver bcmwl5 (Broadcom,11/02/2005, 4.10.40.0) loaded
ACPI: PCI Interrupt 0000:01:03.0[A] -> Link [LNKB] -> GSI 5 (level, low) -> IRQ 5
ndiswrapper: using irq 5
wlan0: vendor: ''
wlan0: ndiswrapper ethernet device 00:90:96:be:f5:41 using driver bcmwl5, 14E4:4320:1028:0003.5.conf
wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK

Quote:
# iwconfig wlan0
wlan0 IEEE 802.11g ESSID:"MyAP"
Mode:Managed Frequency:2.412 GHz Access Point: 00:11:2F:9D:1F:4A
Bit Rate:54 Mb/s Tx-Power:32 dBm
RTS thr:2347 B Fragment thr:2346 B
Encryption key:off
Power Management:off
Link Quality:100/100 Signal level:-33 dBm Noise level:-256 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

# ifconfig wlan0
wlan0 Link encap:Ethernet HWaddr 00:90:96:BE:F5:41
inet addr:192.168.0.125 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:48073 errors:0 dropped:0 overruns:0 frame:0
TX packets:34960 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:68738464 (65.5 MiB) TX bytes:3340065 (3.1 MiB)
Interrupt:5 Memory:fcffc000-fcffe000

Perhaps the information above can be useful in troubleshooting the dotpup.

Tempestuous, thanks anyway for your effort in trying to make this work Smile
Paul
Back to top
View user's profile Send private message 
MU


Joined: 24 Aug 2005
Posts: 13642
Location: Karlsruhe, Germany

PostPosted: Sat 08 Jul 2006, 09:53    Post subject:  

PM from tempestous::
Quote:
- PaulBx1 asked me to make WPA encrption information more clear.
- The ralink-legacy.pup now has another driver included.
... so, please overwrite these files with new versions I just uploaded -

_Puppy2_wireless_README.txt
ralink-legacy.pup
ralink-legacy_README.txt
wpa_supplicant-0.4.9.pup
wpa_supplicant_README.txt


Uploaded the updates.
Mark
Back to top
View user's profile Send private message Visit poster's website 
tempestuous

Joined: 10 Jun 2005
Posts: 5139
Location: Australia

PostPosted: Sat 08 Jul 2006, 10:00    Post subject:  

Thanks Mark.

Paul, the bcm43xx driver looks like it's close to success. Troubleshooting:
Load all modules that bcm43xx depends on first -

modprobe ieee80211_crypt
modprobe ieee80211
modprobe ieee80211softmac
modpobe firmware_class
modprobe bcm43xx

After "modprobe bcm43xx" you must bring up the interface before doing anything else -
ifconfig eth1 up
This is helpful for most wifi drivers, but CRUCIAL for this driver.

I see this - "Invalid Bit Rate=1 Mb/s" so be a bit more explicit with your iwconfig command -
iwconfig eth1 essid MyAP rate 11M mode managed
You could also specify the channel in this command.

And now do "ifconfig eth1 up" again just to be sure, before running dhcpcd.

If still no success, please report any relevant dmesg output, especially stuff relating to "SoftMAC".

And one little thing to check - your access point must broadcast its SSID. Hidden SSID's won't work with this driver.
Back to top
View user's profile Send private message 
pakt


Joined: 04 Jun 2005
Posts: 1089
Location: Sweden

PostPosted: Wed 12 Jul 2006, 02:28    Post subject:  

EDIT: I've trying to post this since last weekend but kept getting a "URL not found" error from the forum. I finally discovered it was this text: '<jketreno@linux.intel.com>' that was part of the quote below that caused the problem. Once I removed it, I had no problem posting Confused

Thanks, tempestuous, for your patience. I've now got the interface working using your dotpup Smile

After a bit of experimenting, the key commands seem to be 'ifconfig eth1 up' and specifying the right combination of 'iwconfig' parameters. To get the interface to work, I managed to minimize the commands to:
Quote:
modprobe bcm43xx
ifconfig eth1 up
iwconfig eth1 essid WTwo channel 8 rate 11M mode managed
ifconfig eth1 up
dhcpcd -t 30 -h puppypc -d eth1

The complete messages from dmesg were:
Quote:
ieee80211_crypt: no version for "struct_module" found: kernel tainted.
ieee80211_crypt: registered algorithm 'NULL'
ieee80211: 802.11 data/management/control stack, git-1.1.7
ieee80211: Copyright (C) 2004-2005 Intel Corporation
bcm43xx driver
ACPI: PCI Interrupt 0000:01:03.0[A] -> Link [LNKB] -> GSI 5 (level, low) -> IRQ 5
bcm43xx: Chip ID 0x4306, rev 0x3
bcm43xx: Number of cores: 5
bcm43xx: Core 0: ID 0x800, rev 0x4, vendor 0x4243, enabled
bcm43xx: Core 1: ID 0x812, rev 0x5, vendor 0x4243, disabled
bcm43xx: Core 2: ID 0x80d, rev 0x2, vendor 0x4243, enabled
bcm43xx: Core 3: ID 0x807, rev 0x2, vendor 0x4243, disabled
bcm43xx: Core 4: ID 0x804, rev 0x9, vendor 0x4243, enabled
bcm43xx: PHY connected
bcm43xx: Detected PHY: Version: 2, Type 2, Revision 2
bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2)
bcm43xx: Radio turned off
bcm43xx: Radio turned off
bcm43xx: PHY connected
bcm43xx: Radio turned on
bcm43xx: Chip initialized
bcm43xx: DMA initialized
bcm43xx: 80211 cores initialized
bcm43xx: Keys cleared
SoftMAC: Open Authentication completed with 00:50:18:0e:6f:10
#

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

Joined: 10 Jun 2005
Posts: 5139
Location: Australia

PostPosted: Thu 13 Jul 2006, 09:50    Post subject:  

Well done Paul. I'm pleased that the bcm43xx driver works, it was quite difficult to compile, since the source code was available only as a (large) kernel source patch. Apparently the latest kernels include this driver as a standard module, along with the latest softmac wifi stack.
I will update the README to reflect your results. The fact that you needed to force the bitrate and channel parameters appears to be characteristic of a driver in its early stages of development. The process of forcing the bitrate to 11M also appears to be helpful with Linux wifi drivers that are failing to connect to some modern 54Mbs and 108Mbs routers.
I now wonder if this solution would also make the rt2x00 (Ralink new code) driver achieve better success?
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5139
Location: Australia

PostPosted: Wed 19 Jul 2006, 20:22    Post subject:  

Update July 2006: Atmel-based USB wifi adaptors are now supported in Puppy2.
The BerliOS Atmel at76c503a wifi driver package will now compile under Puppy2's kernel, thanks to some recent development of this driver for the first time in 2 1/2 years. I have just added it to the collection of wifi dotpups.
Back to top
View user's profile Send private message 
BlackAdder


Joined: 22 May 2005
Posts: 382

PostPosted: Fri 21 Jul 2006, 20:09    Post subject: ATMEL drivers  

Thanks for the Atmel drivers, tempestuous. I have access to a Netcomm NP7042 (03eb:7605) and a Micronet SP907BB V2 (12fd:1001). Both work well with these Puppy 2 drivers.
The at76c503-connect script could benefit from a sleep after the modprobe - I found 5 seconds was needed. The device connects and downloads the firmware, then disconnects and reconnects - don't know why, but that is what dmesg shows, and all that fluffing around takes some time.

tempestuous, you should get another Goodonyer award. If they were medals, you would look like a Russian general.
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5139
Location: Australia

PostPosted: Sat 29 Jul 2006, 22:50    Post subject:  

With the release of Puppy 2.02, these drivers are no longer useful.
But the contents of these driver packages can be helpful in creating your own updated driver. The main modules must, of course, be recompiled from source, but the original dotpups often contain additional utilities (hotplug, for example) plus firmware files, configuration files, and the all-important README which can be the most useful resource of all.
To extract the contents of a dotpup first do this - "unzip MYWIFIDRIVER.pup"
The unzipped dotpup will contain "FILESYSTEM.tgz". Uncompress this as such - "tar -zxvf FILESYSTEM.tgz"
Now you will have the full contents of the dotpup. All kernel-specific modules are in /lib/modules/xxx. All OTHER files are useful.

The wpa_supplicant, aircrack, kismet, and HostAP daemon dotpups remain useful, since these utilities don't contain kernel-specific modules.
Back to top
View user's profile Send private message 
Rickrandom

Joined: 21 Jan 2006
Posts: 195
Location: Bedfordshire, UK

PostPosted: Sun 30 Jul 2006, 13:04    Post subject:  

Excuse my ignorance, but I thought these drivers were for kernel 2.6.16.7, and I thought from Barry's news page that Puppy2.02 was still at this kernel version.

In very simple terms, why do they no longer work?

I did as suggested, and read the readme, but it was way over my head.

I was pretty pleased with myself (I'm easily pleased) when I got my Atheros mini-PCI card working in 2.01 with the madwifi driver. I was equally pleased with NTFS read/write in 2.02. I guess with the rapid evolution of Puppy, it's very difficult to have the best of all worlds immediately....
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5139
Location: Australia

PostPosted: Mon 31 Jul 2006, 00:22    Post subject:  

At http://www.puppyos.net/news/
under the heading Puppy 2.02beta, with full NTFS write support, Thursday, July 27, 2006, 04:03 AM
BarryK wrote:
Another point: the kernel is 2.6.16.7 but earlier modules (v2.01) are not compatible. A nuisance if you have compiled one for wireless for example. I can help out, post the link here or the forum and I'll download and compile it.
Back to top
View user's profile Send private message 
violetdream

Joined: 15 Apr 2006
Posts: 109

PostPosted: Mon 31 Jul 2006, 03:54    Post subject:  

Have new driver packages been compiled for pup202? I'm dying without my madwifi Sad If anyone could package a new version that would be fantastic!
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 4 of 7 [105 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6, 7 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Hardware
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.0941s ][ Queries: 12 (0.0060s) ][ GZIP on ]