Windows 10: Wifi issues on Windows 10

Make sure to get the 7260AC.HMWWB.R or 7260AC.HMWG.R, the .R is the revised version which fixes many problems that came out in September 2014.

Amazon.com: Intel Network 7260.HMWG.R Revised WiFi Wireless-AC 7260 H/T Dual Band 2x2 AC+Bluetooth HMC Free Mounting Screws Included: Computers Accessories

Amazon.com: Intel Dual Band Wireless-AC 7260 Network Adapter (7260.HMWWB.R): Computers Accessories

 

Almighty1 one you are quicker then I am. I was just going to post that link. Of course I still have the two old Realtek cards. I never use the Blue Tooth on them, because I was just looking for Dual Channel to help speed up wireless file transfers.

 

I just bought and installed mines (HMWWB.R) a little less than a month ago which was sold locally at Central Computers (CentralComputers.com - Computer Parts, PC Components, Laptop and more!
) for $24.99 and it's working fine at 867Mbps.

 

This is the model series that I bought at the time when I got them last year. 7260.HMWWB I have not had any problems with Windows 10 for the adapter on my wife's laptop or on mine running Linux Mint 17.2. The Blue Tooth does not work, which I expected with the laptops we have. So I broke down and got a Blue Tooth USB adapter in case we ever decide to use it for something.

 

You can't tell from the sticker or the card itself if it's the .R revision or not as the .R cards don't have it on the card themselves but in the cardboard box that contains a bunch of cards. All the information is still the same on the physical card including the 2013 date. The actual card does not say 7260.HMWWB or 7260.HWWG either as those are just order codes. The actual card will only say 7260HMW on it for the model. My bluetooth works fine, on Windows, you need the newer drivers (18.x) for the bluetooth to work or it requires a physical hack to get it working with older drivers... This guys review has all the info you need to get both the Wifi And Bluetooth working... People who had problems either got the older card or it's version 17.x drivers which were known to have problems.

http://www.amazon.com/review/R13URHA...41966&store=pc

You may need to do the hardware hack referenced from the above in post #50 of this thread by putting a piece of tape over pin 51 to get the bluetooth working:

Intel Centrino 6235 Bluetooth not detected by w... | Intel Communities

 

I did not flip it over. It is the series before the .R came out I know that it was last batch before the current series came out.

I was not looking for Bluetooth when I bought them. I was looking for towards future proof & compatibility with Linux.

 

The current series looks the same physically, there is nothing indicating it is the .R other than the price sticker from the store as they all come in the plastic holder. The actual model and .R is only on the box that the resellers receive with a quantity of cards. I've never figured out how to get Wireless working in Linux or *BSD as I was already on a GiGe ethernet connection anyways and I had a Atheros card(s), that was when Intel wasn't good for Wireless but the best for wired in the 1990s.

 

The latest Linux Kernels have the Intel adapters that are known to be used, coded in. This is the list of current supported Intel Wifi drivers supported by Linux. en:users:drivers:iwlwifi [Linux Wireless]

Code: 02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 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: 64 bytes Interrupt: pin A routed to IRQ 43 Region 0: Memory at f0200000 (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: 00000000fee0100c Data: 41b1 Capabilities: [40] Express (v2) Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 unlimited ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ 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- 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- DevCap2: Completion Timeout: Range B, TimeoutDis+, LTR+, OBFF Via WAKE# DevCtl2: Completion Timeout: 16ms to 55ms, TimeoutDis-, LTR-, OBFF Disabled LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [100 v1] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn- Capabilities: [140 v1] Device Serial Number 0c-8b-fd-ff-ff-d5-7a-a5 Capabilities: [14c v1] Latency Tolerance Reporting Max snoop latency: 0ns Max no snoop latency: 0ns Capabilities: [154 v1] Vendor Specific Information: ID=cafe Rev=1 Len=014 <?> Kernel driver in use: iwlwifi[/quote] Code: 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 73)[/quote]

 

Code: 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 73)[/quote] [/quote] The driver is not my concern. I'm on static IP as my machine actually serves as a server which is why I prefer the 1Gbps built-in Intel Ethernet. I just never figured out how to do DHCP on the WiFi side.

 

I pass through the DHCP from the Cisco Router through the Engenius A/P. The A/P has a static, so that it will never change IP's on me. I set the Static on the A/P. Then the Edge Router keeps it sticky in its table.

 

The one good thing is that with Linux, you get more diagnostic info as you can see.

 

I will try this n let you you know if it works

 

I never really looked into it as I prefer wired to wireless since I don't physically use the FreeBSD machine anyways except through ssh. I've always used static IPs on both Linux and FreeBSD on wired connections so wireless is something I never really had time to go figure out especially when it concerns DHCP as I haven't needed to use DHCP on anything with my CIDR/27 block.

 

All of the following are wired devices: 2 A/P's, 3 Streaming devices, a Desktop. Then of course at the shelf downstairs, there is the NAS, a Sam Knows box, Lantronix Airprint server, Engenius POE injector for the Engenius A/P.

I posted an updated picture of my network setup downstairs. The biggest issue I kept running into with the Gateway sitting on the metal shelf. Was that I was finding condensation underneath it. So I used a couple pieces of 1/4 round to help lift the Gateway up just enough to get some airflow under it.

Unless I go to a Domain setup. The Sticky IP's on the Cisco are holding up well, unless I have to do a table clear because of conflicts. The roaming devices like tablets, laptops, smartphones are the only devices that have Dynamic IP's on my network. Right now I just cannot see going 100% static, unless I start running into some major issues, or decide to play around with a Domain controller and Radius. If I decide to do that, I would use a Raspberry PI for that part.

I have gotten to where I really do not want to spend 8 hours a day dealing with the network, so I made it as simple as I could.

 

The last time I attempted to do a Wifi DHCP on FreeBSD was in the early 2000's, already have enough things to so didn't really mess with it as I run and own a ISP that I control remotely so it was already busy enough getting new boxes configured remotely to worry about the wifi as the notebook never moves since it sits under the table and with the Cisco 10GiGE Catalyst switch less than 3 feet away and the WiFi router routes back to same FreeBSD machine which is the outgoing gateway so the WiFi from the same machine won't serve any purpose as it's already providing WAN services and besides, it could be the card being a Atheros was not fully supported as these are not the Atheros that one buys but it was taken out of a Netgear FWAG114 Business WiFi router which had the SuperG 108Mbps except the SuperG didn't work in Windows XP either so the cards might be made to work only in the router as all I can get from it was 54Mbps. Tutorials didn't begin to be available another 10 years later... Basically, I'm talking about something from 15-16 years ago.