ipw2100 (Intel Pro/Wireless 2100) Install

Mondus · 07-26-2005, 05:29 AM

I have been using this guide to try and get my wireless working on the laptop with Debian:

2.3. Wireless adapter

You will need to install the packages hostap-source, wireless-tools, hostap-utils and hostapd. Furthermore you will need the source for ipw2100, that may be obtained here.

To install, first extract the hostap-source, and then issue the command

make HOSTAP=/usr/src/modules/hostap-source KSRC=/path/to/kernel-source install

in the ipw2100 directory. Next compile the hostap modules with the command

debian/rules binary-modules KSRC=/path/to/kernel-source

from the hostap-source directory. Now you may for example scan your vicinity with iwlist scan.

------------------------------------------------------------------------------------------------------------

But at the following point I don't know what to do:
make HOSTAP=/usr/src/modules/hostap-source KSRC=/path/to/kernel-source install

The problem is that my kernel is 2.6.8-2-386... But I installed this kernel using the apt system.. so it's a precompiled kernel.. But the guide wants me to give them a path to my kernel-source.. Something I don't have... What do I do?

P.s. Sorry for not giving a link.. But I just found out I have to have 5 posts before being able to post a URL.

Noth · 07-26-2005, 11:00 PM

Install module-assistant and ipw2100-source. Running module-assistant should then grab anything else you need and compile the ipw2100 module.

Mondus · 08-24-2005, 03:52 PM

I've tried using module assistent with the help of this guide:

http://blogs.cocoondev.org/michaelm/...es/002084.html

But when I build it with the command:

sudo module-assistant a-i ipw2100

It doesn't work.. Here's what the log said: (sorry if some of this is in Danish)

Quote:

dh_testdir
dh_testroot
rm -f build-arch-stamp build-indep-stamp configure-stamp
rm -rf modules
/usr/bin/make clean
make[1]: Entering directory `/usr/src/modules/ipw2100'
make[1]: Leaving directory `/usr/src/modules/ipw2100'
/usr/bin/make -C driver clean
make[1]: Entering directory `/usr/src/modules/ipw2100/driver'
rm -f *.mod.c *.mod *.o *.ko .*.cmd .*.flags .lst *.lst
rm -rf /usr/src/modules/ipw2100/driver/tmp
for file in *.{c,h}; do \
sed -i -e "s:\ *$::g" -e "s:\t*$::g" $file; \
done
make[1]: Leaving directory `/usr/src/modules/ipw2100/driver'
dh_clean
/usr/bin/make -f debian/rules kdist_clean kdist_config binary-modules
make[1]: Entering directory `/usr/src/modules/ipw2100'
dh_testdir
dh_testroot
rm -f build-arch-stamp build-indep-stamp configure-stamp
rm -rf modules
/usr/bin/make clean
make[2]: Entering directory `/usr/src/modules/ipw2100'
make[2]: *** Ingen regel til at skabe mål 'clean'. Stop.
make[2]: Leaving directory `/usr/src/modules/ipw2100'
make[1]: [clean] Fejl 2 (ignoreret)
/usr/bin/make -C driver clean
make[2]: Entering directory `/usr/src/modules/ipw2100/driver'
rm -f *.mod.c *.mod *.o *.ko .*.cmd .*.flags .lst *.lst
rm -rf /usr/src/modules/ipw2100/driver/tmp
for file in *.{c,h}; do \
sed -i -e "s:\ *$::g" -e "s:\t*$::g" $file; \
done
make[2]: Leaving directory `/usr/src/modules/ipw2100/driver'
dh_clean
/usr/bin/gcc-4.0
for templ in ; do \
cp $templ `echo $templ | sed -e 's/_KVERS_/2.6.12.5/g'` ; \
done
for templ in `ls debian/*.modules.in` ; do \
test -e ${templ%.modules.in}.backup || cp ${templ%.modules.in} ${templ%.modules.in}.backup 2>/dev/null || true; \
sed -e 's/##KVERS##/2.6.12.5/g ;s/#KVERS#/2.6.12.5/g ; s/_KVERS_/2.6.12.5/g ; s/##KDREV##/saralin.1.0/g ; s/#KDREV#/saralin.1.0/g ; s/_KDREV_/saralin.1.0/g' < $templ > ${templ%.modules.in}; \
done
export DH_OPTIONS='-pipw2100-modules-2.6.12.5'
sed s/_UPSTREAM_VERSION_/1.1.0/ < debian/config > debian/config.new
mv debian/config.new debian/config
dh_testdir
dh_testroot
dh_clean -k
# Build the module
/usr/bin/make -C driver KSRC=/usr/src/linux KVER=2.6.12.5
make[2]: Entering directory `/usr/src/modules/ipw2100/driver'
/usr/bin/make -C /usr/src/linux SUBDIRS=/usr/src/modules/ipw2100/driver MODVERDIR=/usr/src/modules/ipw2100/driver modules
make[3]: Entering directory `/usr/src/linux-2.6.12.5'
CC [M] /usr/src/modules/ipw2100/driver/ipw2100.o
include/linux/etherdevice.h: In function 'ipw2100_set_address':
include/linux/etherdevice.h:84: internal compiler error: Lagersegmentfejl
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
For Debian GNU/Linux specific bug reporting instructions,
see <URL:file:///usr/share/doc/gcc-4.0/README.Bugs>.
make[4]: *** [/usr/src/modules/ipw2100/driver/ipw2100.o] Fejl 1
make[3]: *** [_module_/usr/src/modules/ipw2100/driver] Fejl 2
make[3]: Leaving directory `/usr/src/linux-2.6.12.5'
make[2]: *** [modules] Fejl 2
make[2]: Leaving directory `/usr/src/modules/ipw2100/driver'
make[1]: *** [binary-modules] Fejl 2
make[1]: Leaving directory `/usr/src/modules/ipw2100'
make: *** [kdist_build] Fejl 2

Noth · 08-24-2005, 05:40 PM

Are you running testing or unstable? The build is attempting to use gcc-4.0 which is probably wrong unless you compiled your own kernel with that compiler. Run 'cat /proc/version' to see what compiler your kernel was built with.

And if I'm interpreting "include/linux/etherdevice.h:84: internal compiler error: Lagersegmentfejl" correctly that's a segmentation fault meaning the compiler crashed which is usually a sign of a bug in the compiler or hardware.

Mondus · 08-24-2005, 11:36 PM

You translated correctly... I used gcc 4.0.1 and I'm running on a Debian Testing distro... And I know there's nothing wrong with the hardware..

Noth · 08-24-2005, 11:56 PM

A quick hack would be to replace the gcc symlink, delete /usr/bin/gcc and create a new one pointing to /usr/bin/gcc-3.3. I highly doubt a module compiled with gcc-4.0 would load in a kernel created with gcc-3.3 anyway, even if it hadn't crashed.

Mondus · 08-25-2005, 05:06 AM

Excuse me.. but I just told you that the kernel was compiled with gcc 4.0.1.. so how's changing the symlink going to work?

Noth · 08-25-2005, 09:40 AM

Oh nevermind then, I missed that part.

Mondus · 08-25-2005, 10:22 AM

No problem.... Do you have any other ideas?.... It's really odd... Every single installation which would normally require kernel-headers on Debian, isn't working properly... Nvidia driver, Lexmark driver, and this (I believe it uses that, but hey... not sure)... But I got this kernel off kernel.org, so I shouldn't be needing kernel-headers right?.. But I'm beginning to doubt it a little.. it is really weird that nothing of that sort is working!

Noth · 08-25-2005, 12:31 PM

I've never compiled a kernel with 4.0, so I have no idea what sort of problems to expect. I know the mainline kernel has had a lot of fixes with regards to 4.0, but it's impossible to know how external modules will work.