Page 5 of 6
Posted: Thu 14 Sep 2006, 22:30
by rafa1215
tempestuous,
I have a motorola wireless router WR850GP and a motorola wireless pci card
WN825GP
Motorola has Linux drivers on their site
Should I use their's or yours?
http://www.motorola.com/softmodem/driver.htm
I used the wifi-1.0.4-beta-2.pup and it lit up my card and recognized it
Now i have to configure that conf file to get it to commuinicate with my router which sends out DHCP
Posted: Thu 14 Sep 2006, 23:19
by tempestuous
violetdream,
No, sorry, I won't be updating these drivers. As I mentioned in an earlier post on July 29 in this thread, they remain useful as a reference for people who compile their own drives in the future. By unzipping these dotpups, you can often find extra firmware files and utilities not included in the main driver source code.
rafa1215
Your wireless router, of course, requires no driver at all.
The Motorola WN825GP PCI card has a Broadcom chipset, so the bcm43xx-softmac driver is the one of choice.
wifi-1.0.4-beta-2.pup is a package of Windows drivers for use with ndiswrapper, so is unrelated to my Linux driver packages.
There are many other threads on this forum regarding ndiswrapper.
The download link you provided is for (old) Motorola SM56 soft modem drivers, nothing to do with wifi at all.
Posted: Fri 15 Sep 2006, 00:07
by rafa1215
Thanks for clearing that up
tempestuous wrote:violetdream,
No, sorry, I won't be updating these drivers. As I mentioned in an earlier post on July 29 in this thread, they remain useful as a reference for people who compile their own drives in the future. By unzipping these dotpups, you can often find extra firmware files and utilities not included in the main driver source code.
rafa1215
Your wireless router, of course, requires no driver at all.
The Motorola WN825GP PCI card has a Broadcom chipset, so the bcm43xx-softmac driver is the one of choice.
wifi-1.0.4-beta-2.pup is a package of Windows drivers for use with ndiswrapper, so is unrelated to my Linux driver packages.
There are many other threads on this forum regarding ndiswrapper.
The download link you provided is for (old) Motorola SM56 soft modem drivers, nothing to do with wifi at all.
Posted: Fri 15 Sep 2006, 04:27
by violetdream
tempestuous wrote:violetdream,
No, sorry, I won't be updating these drivers. As I mentioned in an earlier post on July 29 in this thread, they remain useful as a reference for people who compile their own drives in the future. By unzipping these dotpups, you can often find extra firmware files and utilities not included in the main driver source code.
I'm not sure where your original post stating this is, but I'm disapointed at your choice. Of course, it is up to you whether you choose to maintain these drivers or not and I appreciate all you've done so far, but many Puppy users are beginners and are quite intimidated by compiling their own things. I'm not quite what you would call a beginner but even I couldn't figure out how to get things to compile - I'm just not a long term linux user. I know a solution would be to use ndiswrapper, but often the range is pathetic compared to the native drivers. I'm just disapointed because I would like to update puppy, but I'm held back because of wireless drivers unavailable for the most current versions (2.10 now). Would anyone else be willing to step up and take tempestuous's place? It would be a great service to all the Puppy users who are still beginners and cannot compile on their own (or don't have a good enough computer to consider compiling on).
Posted: Tue 19 Sep 2006, 02:22
by tempestuous
Two recent synergies may make it easier for wifi drivers to be updated in the future:
- the new T2 development system
- several wifi drivers are being merged into the mainstream Linux kernel from version 2.6.18
See
http://www.murga.org/~puppy/viewtopic.php?p=69635
violetdream, if MADWiFi is what you want, it was included in the package list for Puppy 2.10alpha
http://www.puppyos.net/news/comments.ph ... 827-093218
Barry has explained that this means the MADWiFi driver will be in the next Puppy release AFTER 2.10.
Posted: Sun 24 Sep 2006, 12:02
by tempestuous
If/when additional wifi drivers become available in future Puppy releases, I will package the necessary firmware and hotplug "extras".
For the current release (2.10) 5 such packages are needed now, so I thought I would start the ball rolling by packaging these: Atmel, HostAP, IPW2100, IPW2200, Prism54.
These dotpups are at Mark's site
http://dotpups.de/dotpups/Wifi/wifi-driver-firmware/
Posted: Mon 23 Oct 2006, 16:48
by edoc
tempestuous wrote:Barry has explained that this means the MADWiFi driver will be in the next Puppy release AFTER 2.10.
I do not see MADWiFi in 2.11
Did it get delayed or is it somewhere I am not looking, please?
Posted: Mon 23 Oct 2006, 19:42
by edoc
edoc wrote:tempestuous wrote:Barry has explained that this means the MADWiFi driver will be in the next Puppy release AFTER 2.10.
I do not see MADWiFi in 2.11
Did it get delayed or is it somewhere I am not looking, please?
OK, found MADWiFi. Downloaded and installed.
Per the instructions I opened Console (rxvt), entered the first code and
received the following result.
Code: Select all
sh-3.00# modprobe ath_pci
WARNING: Error inserting ath_hal (/lib/modules/2.6.16.7/net/wireless/madwifi/ath_hal.ko): Invalid module format
WARNING: Error inserting wlan (/lib/modules/2.6.16.7/net/wireless/madwifi/wlan.ko): Invalid module format
WARNING: Error inserting ath_rate_sample (/lib/modules/2.6.16.7/net/wireless/madwifi/ath_rate_sample.ko): Invalid module format
FATAL: Error inserting ath_pci (/lib/modules/2.6.16.7/net/wireless/madwifi/ath_pci.ko): Invalid module format
sh-3.00#
It breaks eth0. I had to issue "ifconfig eth0 up" and then walk through
Setup-Ethernet/network Wizard to restore a wired connection until I
am able to get wireless working again.
This did not happen in prior versions of MADWiFi.
Posted: Fri 27 Oct 2006, 04:08
by tempestuous
edoc wrote:I do not see MADWiFi in 2.11
This was Barry's intention, at the same time as Puppy moves to the new 2.6.18.x kernel, but 2.11 became an "intermediate" release.
Wifi drivers (and some others) for Puppy 2.12 have been announced on the developer forum
http://www.puppyos.net/news/comments.ph ... 019-222209
Posted: Sun 29 Oct 2006, 22:16
by edoc
tempestuous wrote:edoc wrote:I do not see MADWiFi in 2.11
This was Barry's intention, at the same time as Puppy moves to the new 2.6.18.x kernel, but 2.11 became an "intermediate" release.
Wifi drivers (and some others) for Puppy 2.12 have been announced on the developer forum
http://www.puppyos.net/news/comments.ph ... 019-222209
Thanks! I see the post. Is the failure to compile the 'linux-wlan-ng' package a temporary
problem or does it mean that it will not be included in 2.12?
Wireless modules compiled
Thursday, October 19, 2006, 10:22 PM
I've compiled more modules for the 2.6.18.1 kernel. This time it is wireless modules.
I was unable to compile the 'linux-wlan-ng' package.
Compiled the Texas Instruments 'acx100' driver okay.
Compiled the Admtek 'adm8211' driver.
Compiled the Atmel 'at76_usb' driver, for the at76c503a chip.
Compiled the Madwifi drivers, for the Atheros chips.
Compiled the Ralink 'rt2400', 'rt2500', 'rt2570' and 'rt61' drivers.
Compiled the Zydas 'zd1211' driver.
Posted: Mon 30 Oct 2006, 01:05
by tempestuous
Further down that developer forum post you will see that I suggested to Barry that only the PCMCIA version of the linux-wlan-ng driver might be failing to compile, and it's possible to disable this particular driver in order to compile the other versions.
As to the outcome? Wait until 2.12 is released, and run "modinfo prism2_usb" to see if the USB version is available.
If your Prism2-based device is NOT USB, then you don't need linux-wlan-ng. Use the HostAP driver instead.
Posted: Mon 30 Oct 2006, 03:03
by edoc
tempestuous wrote:Further down that developer forum post you will see that I suggested to Barry that only the PCMCIA version of the linux-wlan-ng driver might be failing to compile, and it's possible to disable this particular driver in order to compile the other versions.
As to the outcome? Wait until 2.12 is released, and run "modinfo prism2_usb" to see if the USB version is available.
If your Prism2-based device is NOT USB, then you don't need linux-wlan-ng. Use the HostAP driver instead.
I have an internally mounted NL-5354MP Plus Aries2(F) - 1.00
The chip is labeled Atheros AR5213A-00 A19911C 1804
Posted: Mon 30 Oct 2006, 05:51
by tempestuous
Well your device is neither USB, nor Prism2-based. linux-wlan-ng has no relevance to your situation.
Posted: Mon 30 Oct 2006, 12:42
by edoc
tempestuous wrote:Well your device is neither USB, nor Prism2-based. linux-wlan-ng has no relevance to your situation.
It is all very confusing to me! I went through a bunch of wireless nics before installing
this one internally and getting it to work.
Now that it has stopped working in 2.11 I am back on wired until I figure out what to do
to get it working again.
If not possible under 2.11 does it appear that 2.12 will restore the lost functionality, please?
Posted: Sun 18 Nov 2007, 21:13
by setecio
Bookmarked for info.