LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   ipw2200 and slackware 10.2 (https://www.linuxquestions.org/questions/slackware-14/ipw2200-and-slackware-10-2-a-365072/)

chess 09-19-2005 09:27 PM

ipw2200 and slackware 10.2
 
has anyone been able to successfully compile and install both ieee80211 and ipw2200 on slackware 10.2, either on the stock 2.6.13 kernel or on any custom 2.6.12 or 2.6.13 kernel? I had it working fine with slackware 10.1 and kernel 2.6.12.1 but now I can't get ipw2200 to install for the life of me. It looks like ieee80211 compiles ok, and it looks like ipw2200 makes ok, but when I run "make install" on the ipw2200 I get a slew of "error: dereferencing pointer to incomplete type" and "... undeclared (first use in this function)" and syntax errors and all sorts of stuff.

Anyone got it working on 10.2? Thanks.

kite 09-20-2005 11:13 AM

I would like to evidence that ipw2200-1.0.6 compiled and installed fine under slack 10.2 with kernel 2.6.12.6.

The only issue is that, i have to use "modprobe ipw2200 hwcrypto=0" instead to overcome "ipw2200: Firmware error detected. Restarting" problem, otherwise the wireless connection seems to be up but there is no successful ping etc for the first a couple of minutes.

I did not have this problem with ipw2200-1.0.4 under slack 10.1 before. But ipw2200-1.0.4 refused to compile under slack 10.2 :(.

derrekito 09-20-2005 12:20 PM

I was doing that kind of stuff yesterday but have not finished, however the drivers do work as intended on the 2.6.10 kernel for sure.

chess 09-20-2005 01:10 PM

It does look like there are some problems with ieee80211, ipw2200, and 2.6.13+ kernels:

http://www.ussg.iu.edu/hypermail/lin...06.3/1537.html

and here is a post further down in that same kernel mailing list thread that has the exact same kind of errors I got:

http://www.ussg.iu.edu/hypermail/lin...06.3/1577.html

there is also a patch on the ieee80211 site (scroll down to "issues")
http://ieee80211.sourceforge.net/

I think I borked some things so I'm going to reinstall 10.2, roll back to a 2.6.12.x kernel and try again. I'll post results. If anyone else has input here, please post. Thanks. :)

derrekito 09-20-2005 01:24 PM

Yea I Broke slackware 10.2 well actually it wasnt me.... it was slackware 10.2 and that 2.6.13 kernel... well its just the kernel.... it isnt very good, I guess its the difference between 2.4 and 2.6 oh well. going to roll bacl to 2.4.31 and build the 2.6.10 kernel i suppose and use both :(

carboncopy 09-20-2005 07:59 PM

works for me
 
It works for me. However I compiled 2.6.13.1 first.

I have no access point to connect. But I did have an iBook to setup ad-hoc connection with. Transfer rate over sftp at 2.6Mbyte/s so, should be able to achieve around 5Mbyte/s without those encryption overhead.

chess 09-20-2005 09:49 PM

Re: works for me
 
Quote:

Originally posted by carboncopy
It works for me. However I compiled 2.6.13.1 first.
I may have figured out my mistake. I rolled back to 2.6.12.1, which is the kernel I had ipw2200 working with in 10.1, and ran into the same error messages. Then, I realized I only did "make" with the ieee80211 and forgot the "make install" part! doh! When I did that, everything worked fine with 2.6.12.1 -- I haven't tried going back to 2.6.13 yet, but I'm sure it would now work.

Proving once again that the problem did not lie with PV or Linus and crew, but with the user sitting in front of my laptop. :)

derrekito 09-20-2005 09:50 PM

Re: Re: works for me
 
Quote:

Originally posted by Jackson1995
I may have figured out my mistake. I rolled back to 2.6.12.1, which is the kernel I had ipw2200 working with in 10.1, and ran into the same error messages. Then, I realized I only did "make" with the ieee80211 and forgot the "make install" part! doh! When I did that, everything worked fine with 2.6.12.1 -- I haven't tried going back to 2.6.13 yet, but I'm sure it would now work.

Proving once again that the problem did not lie with PV or Linus and crew, but with the user sitting in front of my laptop. :)

OUCH! that must hurt :P well at least you may have gotten it!

jstamcar 10-08-2005 09:46 AM

can anyone tell me please where to put the firmware and the drivers for the ipw2200bg....
i dont know where to install those two things

thx in advice
best regards,
Jan

carboncopy 10-29-2005 04:33 AM

firmware (*.fw) goes to /lib/firmware

the drivers:

make
make install

Note that in 2.6.14 kernel, the ipw2100 and ipw2200 has been included into the kernel. I have compiled it, got the modules loaded automatically, but no network device. Have not read the docs yet.

carboncopy 11-01-2005 11:49 AM

Referring to my post above ^

The ipw2200 driver in 2.6.14 is version 1.0.0. The current version (at the time of writing) is 1.0.8.

So, it is still better to go to http://ipw2200.sf.net for your driver.

chess 11-01-2005 11:55 AM

Interesting. Have you got it to work? Is the ieee80211 also included in 2.6.14?

jnsg 11-01-2005 03:09 PM

I thought the ipw2200 site recommends to use the latest stable release, which is 1.0.0. In fact, this is what I have succesfully compiled and used on Slackware 10.2, 2.6.13.4 kernel...

luceroz 11-10-2005 01:32 PM

what did you gues do in kernel config about iee80211? (i am using 2.6.14 from kernel.org) did you compile as modules/builtin or not at all?

niether as modules or built in will compile for me -- i get an error like "no target to make ieee80211.s which is needed by [i think] ieee80211.o" or something like that (from memory).

EDIT:: ieee80211 is in 2.6.14 -- under networking --> (last one). but as mentioned above -- i cannot compile ieee80211 in the kkernel -- it shits on me.


i know I am to end up using the modules from ieee80211.sourceforge.org (whatever the url is) so do i need to leave the ieee80211 parts in the kernel out completely?



and as for firmware loading -- compiling hotplug firmware support into the kernel and throwing the *.fw files into /lib/firmwre is all i need correct?




I too have been forgeting 'make install' in the process as well -- i dont know why, im ususally not this retarded.


All times are GMT -5. The time now is 04:09 PM.