| View previous topic :: View next topic |
| Author |
Message |
Kurbel n00b

Joined: 23 Feb 2004 Posts: 6 Location: Germany
|
Posted: Wed Mar 10, 2004 1:38 pm Post subject: Intel PRO/Wireless 2100 (IPW2100) mini DRIVER!!! |
|
|
Look what a nice opensource Project Intel provides us with! I think, that about next week I'm going to give that thing a try. YEAH!
http://ipw2100.sourceforge.net/
best regards,
Kurbel! _________________ Q:How does a computer scientist prove, that all odd numbers are prime ones?
A: He proves that 1 is a prime number and 1 is a prime number and 1 is a prime number and ... |
|
| Back to top |
|
 |
latexer Retired Dev

Joined: 05 Mar 2003 Posts: 239 Location: NYC
|
Posted: Wed Mar 10, 2004 2:46 pm Post subject: In portage |
|
|
I added this to portage last night, please feel free to test from there. If on a 2.6 kernel, you'll still need to disable sandbox until the changes from bug #32737 on bugs.gentoo.org can be merged.
finally intel has stepped up and provided us with a driver! _________________ overlays - Use at your own risk. File bug reports on this stuff and i'll kick you in the junk. Ask me before asking upstream if these fail. I mean it. No, really.
#gentoo-dotnet on freenode |
|
| Back to top |
|
 |
flying_walus n00b

Joined: 07 Sep 2002 Posts: 58
|
Posted: Wed Mar 10, 2004 5:58 pm Post subject: how to emerge |
|
|
to emerge I needed to set the following:
FEATURES="-sandbox -userpriv -usersandbox" |
|
| Back to top |
|
 |
captmiddy n00b

Joined: 12 Mar 2003 Posts: 17
|
Posted: Wed Mar 10, 2004 8:21 pm Post subject: Figures |
|
|
I installed this just about an hour ago before I saw this message, which means I manually patched the kernel . Oh well.
I have this working on my Thinkpad T40 now, only problem so far is figuring out how to set the SSID on ths automatically since there are two access points in my area and I don't want to use my neighbor's network. |
|
| Back to top |
|
 |
amallah n00b

Joined: 20 Oct 2003 Posts: 20
|
Posted: Thu Mar 11, 2004 4:27 am Post subject: |
|
|
I emerged the ebuild (had to also do ACCEPT_KEYWORDS="~x86") and i can install the module just fine:
| Code: |
centrino root # lsmod
Module Size Used by
ipw2100 53136 0
fglrx 201068 9
rtc 9656 0
ppp_mppe_mppc 20520 0
ppp_generic 20752 1 ppp_mppe_mppc
slhc 6528 1 ppp_generic
|
When I do iwlist scan, I get the proper AP:
| Code: | Cell 04 - Address: 00:C0:02:C8:80:86
ESSID:"volkswagen"
Mode:Master
Frequency:2.462GHz
Bit Rate:1Mb/s
Bit Rate:2Mb/s
Bit Rate:5.5Mb/s
Bit Rate:11Mb/s
Quality:0 Signal level:206 Noise level:0
Encryption key:on |
However, after I bring up the interface, it doesn't seem to associate properly:
| Code: |
centrino root # iwconfig
eth0 no wireless extensions.
lo no wireless extensions.
eth1 IEEE 802.11b ESSID:"volkswagen" Nickname:"ipw2100"
Mode:Managed Frequency:2.412GHz Access Point: 00:00:00:00:00:00
Bit Rate=0kb/s Tx-Power=0 dBm
Retry:on RTS thr=2304 B Fragment thr:2332 B
Encryption key:####-####-## Security mode:restricted
|
As you can see, the frequency is off. When I do:
| Code: |
iwconfig eth1 freq 2.462G
|
It won't change. Does the ipw2100 driver not yet support frequency adjustment?
FWIW my installation using win32 drivers and ndiswrapper works flawlessy. |
|
| Back to top |
|
 |
amallah n00b

Joined: 20 Oct 2003 Posts: 20
|
Posted: Thu Mar 11, 2004 4:33 am Post subject: |
|
|
I'm a fool. I just checked the sourceforge site (should have done it before). The ipw2100 module does not support WEP yet.  |
|
| Back to top |
|
 |
recoco.zhang n00b

Joined: 20 Jan 2004 Posts: 50
|
Posted: Thu Mar 11, 2004 8:58 am Post subject: |
|
|
| amallah wrote: | I'm a fool. I just checked the sourceforge site (should have done it before). The ipw2100 module does not support WEP yet.  |
that is why i had to switch to driverloader...hope ipw2100 will support WEP soon... |
|
| Back to top |
|
 |
diddly n00b


Joined: 11 Mar 2004 Posts: 19 Location: Halifax, Nova Scotia, Canada
|
Posted: Thu Mar 11, 2004 1:43 pm Post subject: |
|
|
I had to use 0.0.30 (March 10 nightly build) of ipw2100 to get it to work with my toshiba m30 (centrino). I was experiencing a lockup with regard to processor mode C3 (documented at http://ipw2100.sourceforge.net)
(edit) It turns out that it did crash again due to that, I guess my notebook was just staying in C2 tricking me into thinking that it was fixed after I emerged 0.0.30  _________________ Dave Flogeras
Last edited by diddly on Fri Mar 12, 2004 1:29 am; edited 1 time in total |
|
| Back to top |
|
 |
latexer Retired Dev

Joined: 05 Mar 2003 Posts: 239 Location: NYC
|
Posted: Thu Mar 11, 2004 2:43 pm Post subject: |
|
|
Yeah, WEP and ad-hoc mode are still unsupported. I just commited 0.30, that fixes quite a few oopses for various things. This driver is still in heavy development, but i'd like to keep it in portage as ~x86 so that people can easily test if they want to. _________________ overlays - Use at your own risk. File bug reports on this stuff and i'll kick you in the junk. Ask me before asking upstream if these fail. I mean it. No, really.
#gentoo-dotnet on freenode |
|
| Back to top |
|
 |
kamikaz3 Apprentice

Joined: 06 Feb 2003 Posts: 187
|
Posted: Thu Mar 11, 2004 5:03 pm Post subject: |
|
|
I can get the module to load, and after that I do a ifconfig eth1 up
But then when I do a iwconfig I get "no wireless extensions" for eth1 _________________ - Gentoo Linux gives me power, speed and flexibility - |
|
| Back to top |
|
 |
Seemer n00b


Joined: 13 Jan 2004 Posts: 50 Location: Sweden
|
Posted: Thu Mar 11, 2004 5:09 pm Post subject: |
|
|
| I just emerged ipw2100 sucessfully.... but whats the next step?? |
|
| Back to top |
|
 |
djresonance n00b

Joined: 01 Jul 2002 Posts: 13 Location: Sacramento, CA, USA
|
Posted: Thu Mar 11, 2004 5:42 pm Post subject: lockups... |
|
|
| I was able to successfully emerge the package, but my laptop locks up whenever I try to bring up the interface. iwconfig shows that eth0 is a wireless device. How are you supposed to actually establish the link between the access point and the wireless card? I tried using 'dhcpd eth0', and that was when my pc locked up. |
|
| Back to top |
|
 |
amallah n00b

Joined: 20 Oct 2003 Posts: 20
|
Posted: Thu Mar 11, 2004 6:12 pm Post subject: |
|
|
| Quote: | | I just emerged ipw2100 sucessfully.... but whats the next step?? |
modprobe ipw2100
Then, you should be able to see a new device via iwconfig/ifconfig (you need wireless-tools, if you don't have iwconfig). Configure the wireless parameters via iwconfig, then ifconfig <interface> up and it should be all set. |
|
| Back to top |
|
 |
GyroJoe n00b


Joined: 05 Mar 2004 Posts: 52 Location: Ann Arbor, MI
|
Posted: Thu Mar 11, 2004 6:16 pm Post subject: |
|
|
Thanks for the ebuild, it's much easier to user portage than to patch the kernel myself
Seems to work fine for me but I only have one access point in my area. Tomorrow I'll be able to test it in a place with at least two APs. I'll post my results to this thread.
In order to get it to work, after emerging the driver, I did this:
| Code: | | /etc/init.d/net.eth1 start |
Of course, you need to make sure you have something like this in /etc/conf.d/net
| Code: | iface_eth1="dhcp"
iface_eth1="-t 10" |
If you don't have an /etc/init.d/net.eth1, copy /etc/init.d/net.eth0 to it.
If you are using the same AP on a regular basis, you could add something to /etc/conf.d/local.start to set it on boot. _________________ Backup - The duplicate copy of crucial data that no one bothered to make; used only in the abstract.
http://www.gnu.org/fun/jokes/software.terms.html for more software terms. |
|
| Back to top |
|
 |
djresonance n00b

Joined: 01 Jul 2002 Posts: 13 Location: Sacramento, CA, USA
|
Posted: Thu Mar 11, 2004 6:24 pm Post subject: |
|
|
| amallah wrote: | | Quote: | | I just emerged ipw2100 sucessfully.... but whats the next step?? |
modprobe ipw2100
Then, you should be able to see a new device via iwconfig/ifconfig (you need wireless-tools, if you don't have iwconfig). Configure the wireless parameters via iwconfig, then ifconfig <interface> up and it should be all set. |
I got my wireless working finally. I had to disable acpi by passing "acpi=off" to my kernel (is there an easier way to do this?) because of the c3 lockups, and I also had to
Once I did that, I saw a message in /var/log/messages that said
| Code: |
av5100: Radio being turned ON
|
After that I was able to use dhcpcd to grab an ip address from my router and start using the connection. |
|
| Back to top |
|
 |
diddly n00b


Joined: 11 Mar 2004 Posts: 19 Location: Halifax, Nova Scotia, Canada
|
Posted: Thu Mar 11, 2004 6:42 pm Post subject: Re: lockups... |
|
|
| djresonance wrote: | | I was able to successfully emerge the package, but my laptop locks up whenever I try to bring up the interface. iwconfig shows that eth0 is a wireless device. How are you supposed to actually establish the link between the access point and the wireless card? I tried using 'dhcpd eth0', and that was when my pc locked up. |
Try the 0.0.30 driver (now in ~x86). I got this and it doesnt lock up for me. _________________ Dave Flogeras |
|
| Back to top |
|
 |
Seemer n00b


Joined: 13 Jan 2004 Posts: 50 Location: Sweden
|
Posted: Thu Mar 11, 2004 8:01 pm Post subject: |
|
|
| It's working. It took a couple of minutes to get the module to load, but when it did, it worker at once |
|
| Back to top |
|
 |
marshall_j Tux's lil' helper


Joined: 22 Jan 2003 Posts: 98 Location: NZ
|
Posted: Thu Mar 11, 2004 11:39 pm Post subject: |
|
|
Has anyone managed to get this going on a R40?
The instructions are followed easily enough and I get no errors until I try to bring up eth1.
Then I get
| Code: |
[root@rza][/home/marshall]$ ifconfig eth1 up
eth1: unknown interface: No such device
|
Notice under lspci the network card doesn't appear to be recognised.... I'm thinking maybe I need to flash my BIOS to a newer version but that will be a hassle as I don't have a floppy disk drive.
DMESG
| Code: |
ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, 0.0.30
ipw2100: Copyright(c) 2003-2004 Intel Corporation
av5100: Radio being turned ON
|
LSPCI
| Code: |
02:02.0 Ethernet controller: Unknown device 168c:0012 (rev 01)
|
LSMOD
| Code: |
Module Size Used by
ds 15620 2
radeonfb 23688 0
e100 31488 0
av5100 2820 0
ipw2100 54544 0
yenta_socket 15872 0
pcmcia_core 60940 2 ds,yenta_socket
eepro100 29964 0
mii 4992 2 e100,eepro100
ide_cd 38788 0
sr_mod 15140 0
cdrom 38048 2 ide_cd,sr_mod
|
Any hints or suggestions would be great! |
|
| Back to top |
|
 |
GyroJoe n00b


Joined: 05 Mar 2004 Posts: 52 Location: Ann Arbor, MI
|
Posted: Fri Mar 12, 2004 5:27 pm Post subject: |
|
|
This is what I get from dmesg when the driver loads:
| Code: | ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, 0.0.30
ipw2100: Copyright(c) 2003-2004 Intel Corporation
Detected ipw2100 PCI device at 0000:02:03.0, dev: eth1, mem: 0xFAFEF000-0xE5CA1FFF -> e5ca1000, irq: 11 |
Are you sure that's the lspci entry for your wireless card? If it is, it doesn't appear to be an Intel card. From /usr/include/linux
| Code: | | pci_ids.h:#define PCI_VENDOR_ID_INTEL 0x8086 |
_________________ Backup - The duplicate copy of crucial data that no one bothered to make; used only in the abstract.
http://www.gnu.org/fun/jokes/software.terms.html for more software terms. |
|
| Back to top |
|
 |
Valdar n00b

Joined: 02 Dec 2003 Posts: 5
|
Posted: Fri Mar 12, 2004 8:49 pm Post subject: |
|
|
| try "update-pciids" and retry lspci .... |
|
| Back to top |
|
 |
latexer Retired Dev

Joined: 05 Mar 2003 Posts: 239 Location: NYC
|
Posted: Fri Mar 12, 2004 9:12 pm Post subject: |
|
|
Yes, 0.31 is out, no it does not come even close to compiling on 2.4 kernels. I 'm gonna hold off and see if any quick fixes are sent to the devel list, if they aren't i'll add this in with a check to make sure people only try it on a 2.6 kernel.
-pete _________________ overlays - Use at your own risk. File bug reports on this stuff and i'll kick you in the junk. Ask me before asking upstream if these fail. I mean it. No, really.
#gentoo-dotnet on freenode |
|
| Back to top |
|
 |
marshall_j Tux's lil' helper


Joined: 22 Jan 2003 Posts: 98 Location: NZ
|
Posted: Fri Mar 12, 2004 9:22 pm Post subject: |
|
|
Hey thanks for those tips on checking and updating the pciid.
Turns out IBM gave me a different wifi card to what I asked for *coughfreeupgradecough*
Thanks. |
|
| Back to top |
|
 |
RainmaN n00b

Joined: 13 Mar 2004 Posts: 4
|
Posted: Sat Mar 13, 2004 2:57 am Post subject: |
|
|
I'm getting the error
| Code: |
make[1]: warning: Clock skew detected. Your build may be incomplete.
Building modules, stage 2.
MODPOST
ACCESS DENIED open_wr: /usr/src/linux-2.6.3-gentoo-r1/.__modpost.cmd
/bin/sh: line 1: ./.__modpost.cmd: Permission denied
make[1]: *** [__modpost] Error 1
make: *** [modules] Error 2
make: Leaving directory `/usr/src/linux-2.6.3-gentoo-r1'
!!! ERROR: net-wireless/ipw2100-0.32 failed.
!!! Function src_compile, Line 47, Exitcode 2
!!! Module compilation failed
--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/tmp/sandbox-net-wireless_-_ipw2100-0.32-3524.log"
open_wr: /usr/src/linux-2.6.3-gentoo-r1/.__modpost.cmd
-----------------------------------------------------------------------------------------------
|
I've used both kernel 2.6.3 and the gentoo-dev-sources 2.6.3, and I get the same error both times.
Anyone have any ideas what's up? |
|
| Back to top |
|
 |
latexer Retired Dev

Joined: 05 Mar 2003 Posts: 239 Location: NYC
|
Posted: Sat Mar 13, 2004 3:52 am Post subject: |
|
|
| RainmaN wrote: | I'm getting the error
| Code: |
make[1]: warning: Clock skew detected. Your build may be incomplete.
Building modules, stage 2.
MODPOST
ACCESS DENIED open_wr: /usr/src/linux-2.6.3-gentoo-r1/.__modpost.cmd
/bin/sh: line 1: ./.__modpost.cmd: Permission denied
make[1]: *** [__modpost] Error 1
make: *** [modules] Error 2
make: Leaving directory `/usr/src/linux-2.6.3-gentoo-r1'
!!! ERROR: net-wireless/ipw2100-0.32 failed.
!!! Function src_compile, Line 47, Exitcode 2
!!! Module compilation failed
--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/tmp/sandbox-net-wireless_-_ipw2100-0.32-3524.log"
open_wr: /usr/src/linux-2.6.3-gentoo-r1/.__modpost.cmd
-----------------------------------------------------------------------------------------------
|
I've used both kernel 2.6.3 and the gentoo-dev-sources 2.6.3, and I get the same error both times.
Anyone have any ideas what's up? |
This is a consistent sandbox error due to the 2.6 kernel's build system. You can see more info on the work i've been doing to fix this on bug #32737 on bugs.gentoo.org. I'll be merging the major fixes from that bug next week.
For now, you can do
| Code: | | FEATURES="-sandbox -usersandbox" ACCEPT_KEYWORDS='~x86' emerge ipw2100 |
to get things working _________________ overlays - Use at your own risk. File bug reports on this stuff and i'll kick you in the junk. Ask me before asking upstream if these fail. I mean it. No, really.
#gentoo-dotnet on freenode |
|
| Back to top |
|
 |
RainmaN n00b

Joined: 13 Mar 2004 Posts: 4
|
Posted: Sat Mar 13, 2004 6:33 am Post subject: |
|
|
| latexer wrote: | | This is a consistent sandbox error due to the 2.6 kernel's build system. You can see more info on the work i've been doing to fix this on bug #32737 on bugs.gentoo.org. I'll be merging the major fixes from that bug next week. |
Thanks for clearing that up.  |
|
| Back to top |
|
 |
|