iB::Topic::intel prowireless 2200bg

	Damn Small Linux :: Damn Small Linux Board The DSL Forums

» Welcome Guest
[ Log In :: Register ]

Damn Small Linux Board » Damn Small Linux » Networking » intel prowireless 2200bg

		Mini-ITX Boards Sale, Fanless BareBones Mini-ITX, Bootable 1G DSL USBs, 533MHz Fanless PC <-- SALE $200 each!
		Get The Official Damn Small Linux Book. DSL Market , Great VPS hosting provided by Tektonic

Pages: (5) </ 1 2 [3] 4 5 >/

[ Track this topic :: Email this topic :: Print this topic ]

Topic: intel prowireless 2200bg, How to setup

< Next Oldest | Next Newest >

tempestuous Offline

Group: Members
Posts: 259
Joined: Aug. 2004

Posted: July 15 2005,13:54

spring,
Yes, build tools are available for DSL, but I have no experience with them. And I would only attempt to use them on a hard drive installation.
I prefer a hard drive installation of Knoppix 3.4 as a development environment.

I just downloaded the patch to have a look at it ... and you're right - the patch is for the ipw2200 driver package, not the kernel. So there's no need to modify and replace DSL's kernel. But you still need the kernel build tree in place to compile the ipw2200 package.
I just checked DSL's kernel configuration and it satisfies most of the configuration options required by this driver package -
CONFIG_CRYPTO=y
CONFIG_CRYPTO_ARC4=m
CONFIG_CRC32=m

... although the configuration options for optional WPA support are not available -
CONFIG_CRYPTO_AES_586
CONFIG_CRYPTO_MICHAEL_MIC

I don't have the Intel ProWireless myself, but instead of making suggestions, I decided to try the driver build myself.
I will keep you updated.

And by the way, it seems that ndiswrapper just won't work with DSL's 2.4.26 kernel. gjhicks has tried it extensively, see here -
http://damnsmalllinux.org/cgi-bin....;t=6747

tempestuous Offline

Group: Members
Posts: 259
Joined: Aug. 2004

Posted: July 16 2005,01:27

Sorry, the compilation failed for me with error messages. But the process has possibly cast some light on gjhicks' attempt in Feather -
Geoff, I think your patch command is wrong.

Quote

patch < ipw2200-1.0.1-3.patch

This did not return any meaningful response when I ran it.
What seemed to work for me was being in the same directory as the driver source (/usr/src/ipw2200-1.0.1) then running this -
patch -p1 < /usr/src/ipw2200-1.0.1-3.patch

If I'm right, it means you have compiled the driver package ... without the patch.
Perhaps you could try it again.

Of course, if you're successful, this driver package can only be used in Feather, not DSL, because they have different versions of the kernel.

spring

Group: Members
Posts: 15
Joined: Dec. 2004

Posted: July 16 2005,09:08

i compiled in slackware 2.4.26 and slax pro 2.4.28,the patch and driver all work well,so i think the process of gjhacks is right way, and i could patch the driver in my environment, i always compiled the driver in /ipw2200-1.0.1, and patched them.

thank you,tempestuous ,and thank your try, maybe another try can success,*_^

tempestuous Offline

Group: Members
Posts: 259
Joined: Aug. 2004

Posted: July 16 2005,13:39

spring,
So you have already compiled the ipw2200 driver in Slackware with 2.4.26 ... fantastic.
My understanding is that linux drivers are kernel-specific, so you should be able to just copy this driver across to DSL, and not have to bother compiling it again in DSL.

I think the files you need will be -
/lib/modules/2.4.26/xxxxx/ipw2200.o
/usr/lib/hotplug/firmware/ipw....

Then run "update-modules" as root so the operating system can find the new driver.

If it works, I'm sure gjhicks will want these files, too.
You might consider making a dsl package ... instructions here -
http://www.damnsmalllinux.org/talk/node/185
Upload to extensions|AT|damnsmalllinux|DOT|org

spring

Group: Members
Posts: 15
Joined: Dec. 2004

Posted: July 17 2005,10:53

thank you tempestuous,that's a good way to make .dsl, but the ipw2200.dsl failed in modprobe.

i've made a ipw2200.dsl like this way:
1,cp ipw2200.o and other five files (ieee80211.o ieee80211_crypt.o ieee80211_crypt_ccmp.o ieee80211_crypt_tkip.o ieee80211_crypt_wep.o)to /ramdisk/lib/modules/2.4.26/kernel/drivers/net/wireless.
2.cp fireware files to /ramdisk/usr/lib/hotplug/fireware/
3.create a fireware.agent like this:

Quote

#!/bin/sh
#
# Firmware-specific hotplug policy agent.
#
# Kernel firmware hotplug params include:
#
# ACTION=%s [add or remove]
# DEVPATH=%s [in 2.5 kernels, /sys/$DEVPATH]
# FIRMWARE=%s
#
# HISTORY:
#
# 24-Jul-2003 Initial version of "new" hotplug agent.
#
# $Id: firmware.agent,v 1.1 2003/10/07 19:34:19 kroah Exp $
#

cd /etc/hotplug
. hotplug.functions
# DEBUG=yes export DEBUG

# directory of the firmware files
FIRMWARE_DIR=/usr/lib/hotplug/firmware

# mountpoint of sysfs
SYSFS=$(sed -n 's/^.* $[^ ]*$ sysfs .*$/\1/p' /proc/mounts)

# use /proc for 2.4 kernels
if [ "$SYSFS" = "" ]; then
SYSFS=/proc
fi

#
# What to do with this firmware hotplug event?
#
case "$ACTION" in

add)
if [ ! -e $SYSFS/$DEVPATH/loading ]; then
sleep 1
fi

if [ -f $FIRMWARE_DIR/$FIRMWARE ]; then
echo 1 > $SYSFS/$DEVPATH/loading
cp $FIRMWARE_DIR/$FIRMWARE $SYSFS/$DEVPATH/data
echo 0 > $SYSFS/$DEVPATH/loading
else
echo -1 > $SYSFS/$DEVPATH/loading
fi

;;

remove)
;;

*)
mesg "Firmware '$ACTION' event not supported"
exit 1
;;

esac

i cp my slackware's file to /etc/hotplug/, then made ipw2200.dsl, and reboot my box,
then run update-modules as root:

Quote

dsl@box:~$ sudo update-modules
depmod: *** Unresolved symbols in /lib/modules/2.4.26/kernel/drivers/net/wireless/ieee80211_crypt_tkip.o
depmod: *** Unresolved symbols in /KNOPPIX/lib/modules/2.4.26/kernel/drivers/usb/auerswald.o
depmod: *** Unresolved symbols in /KNOPPIX/lib/modules/2.4.26/kernel/drivers/usb/speedtch.o
depmod: *** Unresolved symbols in /KNOPPIX/lib/modules/2.4.26/kernel/net/bridge/bridge.o
depmod: *** Unresolved symbols in /KNOPPIX/lib/modules/2.4.26/kernel/net/sctp/sctp.o
dsl@box:~$ sudo modprobe ipw2200
/lib/modules/2.4.26/kernel/drivers/net/wireless/ipw2200.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.26/kernel/drivers/net/wireless/ipw2200.o: insmod /lib/modules/2.4.26/kernel/drivers/net/wireless/ipw2200.o failed
/lib/modules/2.4.26/kernel/drivers/net/wireless/ipw2200.o: insmod ipw2200 failed
dsl@box:~$ dmesg

ieee80211_crypt: registered algorithm 'NULL'
ipw2200: Intel® PRO/Wireless 2200/2915 Network Driver, 1.0.1-3
ipw2200: Copyright© 2003-2004 Intel Corporation
ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
ipw2200: ipw-2.2-boot.fw load failed: Reason -2
ipw2200: Unable to load firmware: 0xFFFFFFFE
ipw2200: failed to register network device
ieee80211_crypt: unregistered algorithm 'NULL' (deinit)
dsl@box:~$

there was something wrong, i reboot my box again and modprobe ipw2200 got the same message.:(

23 replies since Dec. 23 2004,22:53

< Next Oldest | Next Newest >

[ Track this topic :: Email this topic :: Print this topic ]

Pages: (5) </ 1 2 [3] 4 5 >/

Damn Small Linux Board » Damn Small Linux » Networking » intel prowireless 2200bg