intel 3945AGB can't join to wireless access point

[Kristaps1]

Hi all!

Thanks for new release - it is best as far i am tried various linux distros.

Unfortunately, my wireless card on Hp Pavillion dv9323 doesn't work well with new sabayon release.

It is Intel 3945AGB card iwl3945 driver, but dmesg shows that

Info of device and:
[i]Device driver 0000:02:00.0[A] lacks bus and class support for being resumed.[/i]

And after that:

[i]iwl3945: Channel 14 [2.4GHz] is Tx only -- skipping
(same with other channels)
iwl3945: Tunnable channels: 12 802.11bg, 23 800.11a channels.
Device driver phy0 lacks bus and class support for being resumed.
Device driver wmaster0 lacks bus and class support for being resumed.
wmaster0: Selected rate control agorithm 'iwl-3945-rs'
Device driver wmaster0 lacks bus and class support for being resumed.[/i]

and:

[i]iwl3945: REPLY_ADD_STA failed
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:13:46:20:47:30
wlan0: authenticate with AP 00:13:46:20:47:30
wlan0: authenticate with AP 00:13:46:20:47:30
wlan0: authenticate with AP 00:13:46:20:47:30 timed out
iwl3945: ipw going down[/i]

THE SADLY THING is that KNetworkmanager see wi-fi access point but can't join to it. From my collegues notebook it is possinle to join.

Help with any idea to slove this problem!

Thanks!

Upd: on left mouse click on knetworkmanager icon it shown: no active device.

How in such situation is possible that on one click - no device, on other it see access point?!

[Dark_MaGe]

are you sure your mac address is enabled to access the ap? looks to me that you're out of range or not enabled to associate, you should post also timings of those lines you posted

[JOStevison]

I'm having the exact same issue with that wireless card in my Toshiba Satellite. I'm dual booting Windows Vista and it can get on the network fine so mac address isn't my problem I don't think.

[juandejesus]

I had the same problem when I was using OpenSuse, and it works the same with Sabayon because both are working with Knetwork Manager, here we have an Access point protected with a password, when you try to connect your pc to the network and it ask you for the password, select the combobox "cifrado" from "Frase de Contraseña Web" and change it to the second option, I can't remember the name, is something like "Hexadecimal..." I'm giving this directions in spanish because my Sabayon is in spanish, I'll put a picture to make this easier to explain



and after you select "Hexadecimal..." type your ap's password and click on "Connect"

if you want to connect to that network automatically, you have to open your Kwallet and let it to store your password before doing all this

[JOStevison]

I'm using the WPA Protocol and there is no hexadecimal option for that. THanks for the help though

[juandejesus]

Oh that's an improved Wireless protocol different to WEP I think I'm not that advanced on Wireless Networks

[JOStevison]

iwconfig output:

lo no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11a ESSID:""
Mode:Managed Frequency:5.18 GHz Access Point: Not-Associated
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Encryption key:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

eth0 no wireless extensions.

[JOStevison]

dmesg:

[ 14.348149] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driv
er for Linux, 0.0.25k
[ 14.348153] iwl3945: Copyright(c) 2003-2007 Intel Corporation
[ 14.367772] ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ
16
[ 14.367781] intelfb: Cannot reserve FB region.
[ 14.367809] PCI driver intelfb lacks driver specific resume support.
[ 14.367942] sdhci: SDHCI controller found at 0000:03:0b.3 [104c:803c] (rev 0)
[ 14.367963] PCI: Enabling device 0000:03:0b.3 (0000 -> 0002)
[ 14.367968] ACPI: PCI Interrupt 0000:03:0b.3[D] -> GSI 23 (level, low) -> IRQ
23
[ 14.368640] Device driver mmc0 lacks bus and class support for being resumed.
[ 14.368653] mmc0: SDHCI at 0xffa06800 irq 23 DMA
[ 14.368832] ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 18 (level, low) -> IRQ
18
[ 14.368849] PCI: Setting latency timer of device 0000:02:00.0 to 64
[ 14.369411] iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection
[ 14.387936] Device driver 0000:02:00.0 lacks bus and class support for being
resumed.
[ 14.402022] e100: Intel(R) PRO/100 Network Driver, 3.5.17-k4-NAPI
[ 14.402026] e100: Copyright(c) 1999-2006 Intel Corporation
[ 14.599073] PCI: Enabling device 0000:03:0b.2 (0000 -> 0002)
[ 14.599094] ACPI: PCI Interrupt 0000:03:0b.2[D] -> GSI 23 (level, low) -> IRQ
23
[ 14.600582] Yenta: CardBus bridge found at 0000:03:0b.0 [1179:0001]
[ 14.600636] Yenta: Enabling burst memory read transactions
[ 14.600645] Yenta: Using CSCINT to route CSC interrupts to PCI
[ 14.600648] Yenta: Routing CardBus interrupts to PCI
[ 14.600689] Yenta TI: socket 0000:03:0b.0, mfunc 0x01aa1022, devctl 0x64
[ 14.812197] Yenta: ISA IRQ mask 0x0cf8, PCI irq 21
[ 14.812206] Socket status: 30000006
[ 14.812209] Yenta: Raising subordinate bus# of parent bus (#03) from #04 to #
07
[ 14.812221] pcmcia: parent PCI bridge I/O window: 0xb000 - 0xbfff
[ 14.812225] pcmcia: parent PCI bridge Memory window: 0xffa00000 - 0xffafffff
[ 14.812228] pcmcia: parent PCI bridge Memory window: 0x50000000 - 0x53ffffff
[ 14.813632] Device driver pcmcia_socket0 lacks bus and class support for bein
g resumed.
[ 14.817232] ACPI: PCI Interrupt 0000:03:08.0[A] -> GSI 20 (level, low) -> IRQ
20
[ 14.864990] iwl3945: Channel 12 [2.4GHz] is Tx only -- skipping.
[ 14.864994] iwl3945: Channel 13 [2.4GHz] is Tx only -- skipping.
[ 14.864996] iwl3945: Channel 14 [2.4GHz] is Tx only -- skipping.
[ 14.864998] iwl3945: Channel 183 [5.2GHz] is Tx only -- skipping.
[ 14.865001] iwl3945: Channel 184 [5.2GHz] is Tx only -- skipping.
[ 14.865003] iwl3945: Channel 185 [5.2GHz] is Tx only -- skipping.
[ 14.865005] iwl3945: Channel 187 [5.2GHz] is Tx only -- skipping.
[ 14.865007] iwl3945: Channel 188 [5.2GHz] is Tx only -- skipping.
[ 14.865010] iwl3945: Channel 189 [5.2GHz] is Tx only -- skipping.
[ 14.865012] iwl3945: Channel 192 [5.2GHz] is Tx only -- skipping.
[ 14.865014] iwl3945: Channel 196 [5.2GHz] is Tx only -- skipping.
[ 14.865016] iwl3945: Channel 7 [5.2GHz] is Tx only -- skipping.
[ 14.865019] iwl3945: Channel 8 [5.2GHz] is Tx only -- skipping.
[ 14.865021] iwl3945: Channel 11 [5.2GHz] is Tx only -- skipping.
[ 14.865023] iwl3945: Channel 12 [5.2GHz] is Tx only -- skipping.
[ 14.865025] iwl3945: Channel 16 [5.2GHz] is Tx only -- skipping.
[ 14.865032] iwl3945: Channel 34 [5.2GHz] is Tx only -- skipping.
[ 14.865035] iwl3945: Channel 38 [5.2GHz] is Tx only -- skipping.
[ 14.865037] iwl3945: Channel 42 [5.2GHz] is Tx only -- skipping.
[ 14.865039] iwl3945: Channel 46 [5.2GHz] is Tx only -- skipping.
[ 14.865042] iwl3945: Channel 100 [5.2GHz] is Tx only -- skipping.
[ 14.865044] iwl3945: Channel 104 [5.2GHz] is Tx only -- skipping.
[ 14.865046] iwl3945: Channel 108 [5.2GHz] is Tx only -- skipping.
[ 14.865048] iwl3945: Channel 112 [5.2GHz] is Tx only -- skipping.
[ 14.865051] iwl3945: Channel 116 [5.2GHz] is Tx only -- skipping.
[ 14.865053] iwl3945: Channel 120 [5.2GHz] is Tx only -- skipping.
[ 14.865055] iwl3945: Channel 124 [5.2GHz] is Tx only -- skipping.
[ 14.865057] iwl3945: Channel 128 [5.2GHz] is Tx only -- skipping.
[ 14.865060] iwl3945: Channel 132 [5.2GHz] is Tx only -- skipping.
[ 14.865062] iwl3945: Channel 136 [5.2GHz] is Tx only -- skipping.
[ 14.865064] iwl3945: Channel 140 [5.2GHz] is Tx only -- skipping.
[ 14.865066] iwl3945: Channel 145 [5.2GHz] is Tx only -- skipping.
[ 14.865069] iwl3945: Tunable channels: 11 802.11bg, 13 802.11a channels
[ 14.866588] Device driver phy0 lacks bus and class support for being resumed.
[ 14.870435] Device driver wmaster0 lacks bus and class support for being resu
med.
[ 14.870471] wmaster0: Selected rate control algorithm 'iwl-3945-rs'
[ 14.887434] Device driver wlan0 lacks bus and class support for being resumed
.
[ 14.887652] Device driver eth0 lacks bus and class support for being resumed.
[ 14.887667] e100: eth0: e100_probe: addr 0xffaff000, irq 20, MAC addr 00:15:B
7:11:F0:57
[ 18.638524] EXT3 FS on dm-0, internal journal
[ 18.969757] vboxdrv: Trying to deactivate NMI watchdog permanently...

[WarraWarra]

Mine did the same on Dell 3945 and Dell 1390/bcm4311mcg , dell wifi does not like the new fancy wifi drivers in 1.0BE and 3.4a , it works sometimes and or slow, never speeds up as suggested so the only fix I could find for now was to use ndiswrapper and the windows drivers for this.
This is driver bug not Sabayon bug. Dell 1390 bcm4311mcg works but very slow , intel/dell 3945 no connect at all.

Code: Select all

ndiswrapper -h
ndiswrapper -l
Browse to folder having windows .inf files for wifi device.
ndiswrapper -i bcmwl5.inf
ndiswrapper -m
ndiswrapper -ma
ndiswrapper -mi
modprobe ndiswrapper
ifconfig
rc-update add net.wlan0 default


and add " ndiswrapper " to /etc/modules.autload.d/kernel-2.6

You would have to unload the current mac80211 / iwl3945 by using
modprobe -r iwl3945
try them until they are all gone , if error try next as some is linked and stuborn so boss goes then workers goes as well. Not sure if needing to blacklist them as well and or stop from loading at boot I would presume it is a good idea to.
If the ipw3945 module was still there you might be able to load it but was removed as far as I have seen not iwl3945 = not working , ipw3945 works.

Hope this gets you going until they can fix it.

[Kristaps1]

Thanks all for help. Problem is solved. I do not know how, because my home wireless router immediately allows connection for my notebook, while work access point (which perfectly worked with 3.4 Loop 1) didn't give me any chance to connect to internet. Perhaps, problem is in access point configuration or in weak signal...