| View previous topic :: View next topic |
| Author |
Message |
RayDude
Advocate
Joined: 29 May 2004
Posts: 2062
Location: San Jose, CA
|
 Posted: Mon Aug 20, 2018 3:25 pm Post subject: iwlwifi and the POS Intel 2230 [solved] |
 |
|
Update: It is working. I was confused about how the KDE wifi password works. I had to set the password to be stored for all users with no encryption for it to connect automatically.
For those who come here. The router must be able to do 20 MHz bandwidth and you must ensure there is no TKIP option for the required wpa2 password.
I have an old tablet style PC with intel centrino wifi that is really being a PITA.
Here's lspci:
| Code: | 02:00.0 Network controller: Intel Corporation Centrino Wireless-N 2230 (rev c4)
Subsystem: Intel Corporation Centrino Wireless-N 2230 BGN
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 28
Region 0: Memory at f7c00000 (64-bit, non-prefetchable) [size=8K]
Capabilities: [c8] Power Management version 3
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: 00000000fee04004 Data: 4023
Capabilities: [e0] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 unlimited
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 0.000W
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+ FLReset-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <4us, L1 <32us
ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp-
LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi |
This thing connects to the internet just fine as long as I connect the ethernet cable first. But it won't authorize when it's clean booted...
I have found many many threads dating back almost a decade about intel chipset and specifically this not quite an N receiver but none of the options offered have helped me.
I have tried many options in my router config. No help.
I have gotten the REG entry to be set correctly.
my iwlwifi.conf file looks like this:
| Code: | options cfg80211 ieee80211_regdom=US
options iwlmvm power_scheme=1
options iwlwifi bt_coex_active=N swcrypto=1 11n_disable=8
|
I also tried 11n_disable=1
Making changes to /etc/default/crda did not make a difference for the REG entry.
Like I said, when it connects, it works fine. 48-59 mbit all the way, but it won't connect unless I connect the ethernet cable which kinda defeats the purpose of wifi, right?
I'm hoping one of you guys has this chip set and can tell me what to do. It does seem to work reliably on other distros so I know there's some voodoo that will cause it to work, I just haven't found it yet.
(ethernet is not an option because I don't want to climb around in the crawlspace...)
When it connects, this is what the output of iwconfig looks like:
| Code: | wlp2s0 IEEE 802.11 ESSID:"jaymaa_net"
Mode:Managed Frequency:2.452 GHz Access Point: [redacted]
Bit Rate=58.5 Mb/s Tx-Power=16 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=65/70 Signal level=-45 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:25 Missed beacon:0
|
dmesg is not very helpful when it can't connect, this is the only message that seems relevant:
| Code: | [ 6.332934] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
[ 6.463112] r8169 0000:01:00.0 enp1s0: No native access to PCI extended config space, falling back to CSI
[ 6.464562] r8169 0000:01:00.0 enp1s0: link down
[ 6.464651] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
[ 6.471869] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 6.484919] iwlwifi 0000:02:00.0: Radio type=0x2-0x0-0x0
[ 6.762635] iwlwifi 0000:02:00.0: Radio type=0x2-0x0-0x0
[ 6.819399] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 6.847898] iwlwifi 0000:02:00.0: Radio type=0x2-0x0-0x0
[ 7.126612] iwlwifi 0000:02:00.0: Radio type=0x2-0x0-0x0
[ 7.183786] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 7.238610] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 8.598911] iwlwifi 0000:02:00.0: Radio type=0x2-0x0-0x0
[ 8.866395] iwlwifi 0000:02:00.0: Radio type=0x2-0x0-0x0
[ 8.919804] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 8.924405] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 8.950872] iwlwifi 0000:02:00.0: Radio type=0x2-0x0-0x0
[ 9.217855] iwlwifi 0000:02:00.0: Radio type=0x2-0x0-0x0
[ 9.271396] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 17.055890] iwlwifi 0000:02:00.0: Radio type=0x2-0x0-0x0
[ 17.325885] iwlwifi 0000:02:00.0: Radio type=0x2-0x0-0x0
[ 17.379030] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
|
It does that over and over again while showing a spinning circle on NetworkManager's KDE interface.
Halp?
_________________
Some day there will only be free software.
Last edited by RayDude on Tue Aug 21, 2018 3:12 am; edited 1 time in total |
|
| Back to top |
|
 |
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54234
Location: 56N 3W
|
| Posted: Mon Aug 20, 2018 3:47 pm Post subject: |
|
|
RayDude,
Lets start with clean total dmesg outputs of when it works and when it doesn't.
I'm not sure what I'm looking for yet but I'll know it when I see it.
I'm not a big fan of GUIs for WiFi control, any of them, until wifi works manually.
Are you sure you have exactly one thing trying to control your WiFi.
Several things will fight over it and it won't work.
The bits of dmesg you didn't show us might help there.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
RayDude
Advocate
Joined: 29 May 2004
Posts: 2062
Location: San Jose, CA
|
| Posted: Tue Aug 21, 2018 3:04 am Post subject: |
|
|
Thanks Neddy.
Apparently I had gotten it to work at some point, but I didn't know it because the wifi password was stored under lock and key and I needed to put in the user password to get the wifi password for KDE to sign in.
Once I entered the user password, wifi connected...
Apparently one of the changes I made above worked...
Sorry to bother you.
I have another problem I'm going to hunt now... I'll probably post in the desktops group for help on that one...
_________________
Some day there will only be free software. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
