| View previous topic :: View next topic |
| Author |
Message |
diddly
n00b
Joined: 11 Mar 2004
Posts: 19
Location: Halifax, Nova Scotia, Canada
|
 Posted: Sat Mar 13, 2004 1:14 pm Post subject: |
 |
|
| djresonance wrote: |
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
|
I believe you only have to disable the processor section within acpi. Hopefully, soon they'll fix that and you wont have to disable anything 
_________________
Dave Flogeras |
|
| Back to top |
|
 |
diddly
n00b
Joined: 11 Mar 2004
Posts: 19
Location: Halifax, Nova Scotia, Canada
|
| Posted: Sat Mar 13, 2004 1:16 pm 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? |
Read the third post of this topic, its already been covered.
_________________
Dave Flogeras |
|
| Back to top |
|
|
Moled
l33t
Joined: 09 Jul 2003
Posts: 635
|
| Posted: Sat Mar 13, 2004 4:35 pm Post subject: |
|
|
does /proc/net/wireless contain anything for anybody?
it seems to recognise my card but iwconfig/list will not work |
|
| Back to top |
|
|
latexer
Retired Dev
Joined: 05 Mar 2003
Posts: 239
Location: NYC
|
| Posted: Sat Mar 13, 2004 5:56 pm Post subject: |
|
|
| Moled wrote: | does /proc/net/wireless contain anything for anybody?
it seems to recognise my card but iwconfig/list will not work |
This can happen if you don't have support for the wireless extensions in your kernel. Make sure you have Device Drivers -> Networking Support -> Wireless LAN (non-ham radio) -> Wireless LAN drivers & Wireless Extensions support enabled if on 2.6, or on 2.4 enabled Network Device Support -> Wireless LAN -> Wireless LAN.
_________________
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 |
|
|
Moled
l33t
Joined: 09 Jul 2003
Posts: 635
|
| Posted: Sat Mar 13, 2004 7:02 pm Post subject: |
|
|
I do have it enabled
being more specific, iwconfig picks up my card
none of the options in iwlist work, yet earlier in this thread amallah seems to get it to work?
and if somebody does "cat /proc/net/wireless" what does it contain? |
|
| Back to top |
|
|
froke
Apprentice
Joined: 16 Dec 2003
Posts: 174
Location: Westside USA
|
| Posted: Sat Mar 13, 2004 7:37 pm Post subject: |
|
|
I have emerged ipw2100 on my IBM Thinkpad R40.
The module loads without problems. Here is /var/log/messages:
| Code: | Mar 13 11:31:12 froketop ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, 0.32
Mar 13 11:31:12 froketop ipw2100: Copyright(c) 2003-2004 Intel Corporation
Mar 13 11:31:12 froketop PCI: Found IRQ 11 for device 0000:02:02.0
Mar 13 11:31:12 froketop PCI: Sharing IRQ 11 with 0000:00:1d.2
Mar 13 11:31:12 froketop PCI: Sharing IRQ 11 with 0000:00:1f.1
Mar 13 11:31:12 froketop Detected ipw2100 PCI device at 0000:02:02.0, dev: eth1, mem: 0xC0204000-0xC0204FFF -> f1989000, irq: 11 |
But about half the time, net.eth1 fails to start. Here is /var/log/messages:
| Code: | Mar 13 11:24:07 froketop eth1: No response from Symbol - hw not alive
Mar 13 11:24:07 froketop eth1: Error loading microcode: -5
Mar 13 11:24:07 froketop eth1: Failed to power on the adapter.
Mar 13 11:24:07 froketop eth1: Failed to start the firmware.
Mar 13 11:24:07 froketop dhcpcd[7195]: dhcpStart: ioctl SIOCSIFFLAGS: File exists
Mar 13 11:24:07 froketop rc-scripts: Failed to bring eth1 up |
And sometimes it works:
| Code: |
Mar 13 11:31:58 froketop ipw2100: Associated with 'aernet' at 11Mbps, channel 11 |
I am using it to post this.
Anyone else gettings some of these errors? I am pretty sure it is hardware related, but I'm not sure if it's interrupt related or power related, or both. As a side note, does anyone know how I can change what devices are using which interrupt so I can stop sharring interrupts?
And | Code: | # cat /proc/net/wireless
Inter-| sta-| Quality | Discarded packets | Missed | WE
face | tus | link level noise | nwid crypt frag retry misc | beacon | 16 |
_________________
Top notch image hosting. Great for screen shots! http://www.imagelink.org |
|
| Back to top |
|
|
megienos
n00b
Joined: 15 Mar 2004
Posts: 4
|
| Posted: Mon Mar 15, 2004 12:53 am Post subject: |
|
|
| latexer wrote: |
For now, you can do
| Code: | | FEATURES="-sandbox -usersandbox" ACCEPT_KEYWORDS='~x86' emerge ipw2100 |
to get things working |
Hi,
I've done that and emerged ipw2100 without apparent problems. But, I can load the module. When I key modprobe ipw2100, I get module ipw2100 not found.
Any clue?
MEgienos |
|
| Back to top |
|
|
froke
Apprentice
Joined: 16 Dec 2003
Posts: 174
Location: Westside USA
|
| Posted: Mon Mar 15, 2004 1:27 am Post subject: |
|
|
Try running
Or a reboot might fix this too.
_________________
Top notch image hosting. Great for screen shots! http://www.imagelink.org |
|
| Back to top |
|
|
froke
Apprentice
Joined: 16 Dec 2003
Posts: 174
Location: Westside USA
|
| Posted: Mon Mar 15, 2004 7:16 am Post subject: |
|
|
Here's an interesting bit of debugging information: (from the source documentation)
| Quote: | ISSUES
------------ ----- ----- ---- --- -- -
No packets! - RF kill switch
If the module loads, but no packets are transferred you may have a SW based
radio kill switch. All laptops have some capability to disable the radio
via a button or switch. On some laptops that switch is physically tied to the
IPW2100; simply toggling the switch should enable the radio.
On other laptops, the switch is a button that when pressed requires some
software driver to send some hardware command to some other piece of hardware
on the laptop, that then controls the radio. The driver currently has support
for the Averatec 5100P laptop's SW switch. Support will be added for other
laptop vendors as we become aware of them and figure out how to enable the
radio.
To know if the radio is being disabled via the RF switch, perform the following:
% cat /proc/ipw2100/eth1/state
Radio is disabled by RF switch
If it says that, then your RF switch is currently disabling the radio. The
driver doesn't currently support switching back to the on state if you have a
physical RF switch (the radio may turn on and packets will work, but the proc
entry won't be updated)
|
_________________
Top notch image hosting. Great for screen shots! http://www.imagelink.org |
|
| Back to top |
|
|
Seemer
n00b
Joined: 13 Jan 2004
Posts: 50
Location: Sweden
|
| Posted: Mon Mar 15, 2004 9:18 am Post subject: |
|
|
My computer locks him self up when i start it. I can't do anything, it locks up when it's trying to bring up eth0.
When I have a cable connected i get an IP from my router, both for eth0 (cable) and eth1 (wireless). When i try to use internet the system totaly dies.... i can't do nothing but reboot.
Any Ideas?? I use 0.32 ipw2100... |
|
| Back to top |
|
|
latexer
Retired Dev
Joined: 05 Mar 2003
Posts: 239
Location: NYC
|
| Posted: Mon Mar 15, 2004 3:16 pm Post subject: |
|
|
| Seemer wrote: | My computer locks him self up when i start it. I can't do anything, it locks up when it's trying to bring up eth0.
When I have a cable connected i get an IP from my router, both for eth0 (cable) and eth1 (wireless). When i try to use internet the system totaly dies.... i can't do nothing but reboot.
Any Ideas?? I use 0.32 ipw2100... |
Are you using ACPI? currently ipw2100 has issues when the processor enters the C3 state, causing hangs, etc. If using ACPI, try to disable the process stuff, or boot with acpi=off as one of your kernel parameters.
_________________
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 |
|
|
Seemer
n00b
Joined: 13 Jan 2004
Posts: 50
Location: Sweden
|
| Posted: Mon Mar 15, 2004 4:35 pm Post subject: |
|
|
Ok, now when I use acpi=off it seems to be working fine.
Thanks for the advice! |
|
| Back to top |
|
|
GyroJoe
n00b
Joined: 05 Mar 2004
Posts: 52
Location: Ann Arbor, MI
|
| Posted: Mon Mar 15, 2004 7:59 pm Post subject: |
|
|
| latexer wrote: | | Seemer wrote: | My computer locks him self up when i start it. I can't do anything, it locks up when it's trying to bring up eth0.
When I have a cable connected i get an IP from my router, both for eth0 (cable) and eth1 (wireless). When i try to use internet the system totaly dies.... i can't do nothing but reboot.
Any Ideas?? I use 0.32 ipw2100... |
Are you using ACPI? currently ipw2100 has issues when the processor enters the C3 state, causing hangs, etc. If using ACPI, try to disable the process stuff, or boot with acpi=off as one of your kernel parameters. |
There is a patch for this on the driver website (it disables C3), however, it didn't apply correctly for me on 2.6.3 or on 2.6.4. Here is my modified patch:
| Code: | --- processor.c.orig 2004-03-13 20:10:36.009076144 -0500
+++ processor.c 2004-03-13 20:14:41.045824896 -0500
@@ -2182,6 +2182,11 @@
"No bus mastering arbitration control\n"));
/*
+ * Hack: Disable bus master controller to disable C3 power transitions
+ */
+ pr->flags.bm_control = 0;
+
+ /*
* Evalute the processor object. Note that it is common on SMP to
* have the first (boot) processor with a valid PBLK address while
* all others have a NULL address.
|
Only the line numbers needed to be changed. This seems to work and hasn't failed on me yet. I'm using the driver right now to post this.
_________________
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 |
|
|
latexer
Retired Dev
Joined: 05 Mar 2003
Posts: 239
Location: NYC
|
| Posted: Wed Mar 17, 2004 9:24 pm Post subject: |
|
|
okay, all you happy ACPI people, i just commited 0.33-r1 which includes a new patch from james which fixes the acpi issue. Give it a whirl when it hits rsync mirrors. Happy wireless!
_________________
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 |
|
|
jarealist
Apprentice
Joined: 07 Oct 2002
Posts: 218
|
| Posted: Wed Mar 17, 2004 10:32 pm Post subject: |
|
|
I'm having trouble getting the driver (0.33-r1) to load. I get the following from dmesg:
av5100: Radio being turned ON
ipw2100: Unknown symbol release_firmware
ipw2100: Unknown symbol request_firmware
This from modprobe:
modprobe ipw2100
FATAL: Error inserting ipw2100 (/lib/modules/2.6.4-gentoo-r1/net/ipw2100.ko): Unknown symbol in module, or unknown parameter (see dmesg)
From lspci -v:
02:0b.0 Network controller: Intel Corp. PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04)
Subsystem: Intel Corp.: Unknown device 2596
Flags: bus master, medium devsel, latency 64, IRQ 9
Memory at d0201000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [dc] Power Management version 2
I did an update-pciids. Any suggestions? |
|
| Back to top |
|
|
jarealist
Apprentice
Joined: 07 Oct 2002
Posts: 218
|
| Posted: Thu Mar 18, 2004 12:16 am Post subject: |
|
|
| Solved my problem by downgrading to the 0.32 driver. Loads OK now. If anyone else sees this, maybe a bug report is in order. |
|
| Back to top |
|
|
diddly
n00b
Joined: 11 Mar 2004
Posts: 19
Location: Halifax, Nova Scotia, Canada
|
| Posted: Thu Mar 18, 2004 12:22 am Post subject: |
|
|
| jarealist wrote: | | Solved my problem by downgrading to the 0.32 driver. Loads OK now. If anyone else sees this, maybe a bug report is in order. |
This happens to me as well on 0.33-r1 or 0.33
Likewise, i downgraded to 0.32
_________________
Dave Flogeras |
|
| Back to top |
|
|
latexer
Retired Dev
Joined: 05 Mar 2003
Posts: 239
Location: NYC
|
| Posted: Thu Mar 18, 2004 2:36 am Post subject: |
|
|
| jarealist wrote: | I'm having trouble getting the driver (0.33-r1) to load. I get the following from dmesg:
av5100: Radio being turned ON
ipw2100: Unknown symbol release_firmware
ipw2100: Unknown symbol request_firmware
This from modprobe:
modprobe ipw2100
FATAL: Error inserting ipw2100 (/lib/modules/2.6.4-gentoo-r1/net/ipw2100.ko): Unknown symbol in module, or unknown parameter (see dmesg)
From lspci -v:
02:0b.0 Network controller: Intel Corp. PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04)
Subsystem: Intel Corp.: Unknown device 2596
Flags: bus master, medium devsel, latency 64, IRQ 9
Memory at d0201000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [dc] Power Management version 2
I did an update-pciids. Any suggestions? |
This is due to a change in the way ipw2100 handles uploading the firmware to the card. Make sure you have CONFIG_FW_LOADER set in your kernel. I'm just commited 0.33-r1, and add 0.34 that fixes where the firmwares go (they moved from /etc/firmware to /usr/lib/hotplug/firmware/) , has a dep on hotplug, and checks for this firmware loader support.
_________________
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 |
|
|
jarealist
Apprentice
Joined: 07 Oct 2002
Posts: 218
|
| Posted: Thu Mar 18, 2004 3:40 am Post subject: |
|
|
latexer wrote:
| Quote: | | Make sure you have CONFIG_FW_LOADER set in your kernel. |
That's what I was missing. Thanks for your help. |
|
| Back to top |
|
|
diddly
n00b
Joined: 11 Mar 2004
Posts: 19
Location: Halifax, Nova Scotia, Canada
|
| Posted: Fri Mar 19, 2004 2:11 am Post subject: |
|
|
how long does it take everyone elses eth1 to start? with ipw2100 and firmware class loaded, it still takes about 30 or more seconds before /etc/init.d/net.eth1 to come up.
_________________
Dave Flogeras |
|
| Back to top |
|
|
froke
Apprentice
Joined: 16 Dec 2003
Posts: 174
Location: Westside USA
|
| Posted: Sun Mar 21, 2004 5:09 am Post subject: |
|
|
Mine takes about 2 seconds to come up, when it loads correctly. Sometimes it doesn't (see above post). The time might be based on how long it takes to associate with the access point and get an IP. I find it takes longer to come up if I'm at a different access point than the last time I used it. It's probably scanning channels and other things before associating.
Wow, the dev team sure is releasing new versions faster than our portage can keep up with. I'm still using 0.32 from portage, has anyone tried installing the driver with the source from the website?
_________________
Top notch image hosting. Great for screen shots! http://www.imagelink.org |
|
| Back to top |
|
|
deadaim
Guru
Joined: 27 Oct 2003
Posts: 467
Location: Florida
|
| Posted: Mon Mar 22, 2004 12:38 am Post subject: |
|
|
Well, I got wireless working thanks to this thread, but I want my eth1(wireless) to be picked up when I boot. I did the following:
1. I added ipw2100 to /etc/modules.autoload.d/kernel-2.6
2. I did the following: rc-update add net.eth1 default
When I reboot, eth1 isn't picked up.
That's one problem. Here's another:
When I don't have eth0(wired) connected, it does a long timeout. In my /etc/conf.d/net I added the following:
iface_eth0="dhcp"
iface_eth0="t -10"
Now it just flys by eth0. I was thinking maybe it wasn't 10 seconds, so I put 100,000,000 and it was still flew by.
Thanks for all your help. |
|
| Back to top |
|
|
Moled
l33t
Joined: 09 Jul 2003
Posts: 635
|
| Posted: Mon Mar 22, 2004 5:00 am Post subject: |
|
|
| deadaim wrote: | Well, I got wireless working thanks to this thread, but I want my eth1(wireless) to be picked up when I boot. I did the following:
1. I added ipw2100 to /etc/modules.autoload.d/kernel-2.6
2. I did the following: rc-update add net.eth1 default
When I reboot, eth1 isn't picked up.
That's one problem. Here's another:
When I don't have eth0(wired) connected, it does a long timeout. In my /etc/conf.d/net I added the following:
iface_eth0="dhcp"
iface_eth0="t -10"
Now it just flys by eth0. I was thinking maybe it wasn't 10 seconds, so I put 100,000,000 and it was still flew by.
Thanks for all your help. |
shouldn't that be:
iface_eth0="-t 10"
and 2 seconds should be more than enough for wired? |
|
| Back to top |
|
|
deadaim
Guru
Joined: 27 Oct 2003
Posts: 467
Location: Florida
|
| Posted: Mon Mar 22, 2004 9:09 am Post subject: |
|
|
| Moled wrote: | | deadaim wrote: | Well, I got wireless working thanks to this thread, but I want my eth1(wireless) to be picked up when I boot. I did the following:
1. I added ipw2100 to /etc/modules.autoload.d/kernel-2.6
2. I did the following: rc-update add net.eth1 default
When I reboot, eth1 isn't picked up.
That's one problem. Here's another:
When I don't have eth0(wired) connected, it does a long timeout. In my /etc/conf.d/net I added the following:
iface_eth0="dhcp"
iface_eth0="t -10"
Now it just flys by eth0. I was thinking maybe it wasn't 10 seconds, so I put 100,000,000 and it was still flew by.
Thanks for all your help. |
shouldn't that be:
iface_eth0="-t 10"
and 2 seconds should be more than enough for wired? |
Yes, it should be. Typo++; |
|
| Back to top |
|
|
maj
Tux's lil' helper
Joined: 22 Nov 2002
Posts: 92
|
| Posted: Wed Mar 24, 2004 11:49 am Post subject: |
|
|
anyone have scanning support working? it says on the sf page that it does support scanning....
tried this since ndiswrapper suddenly decided that it couldnt load the module - dont understand what changed, but this seems to work very well once its up, i just need scanning support |
|
| Back to top |
|
|
|
Kernel & Hardware
