tgwilt wrote: ⤴Sun Aug 05, 2018 1:39 pm
Hi dman,
I don't know what you mean by "canonical way to test the functionality of the wireless adapter". I just use the terminal command
to see the channel, dropped
packets, and other information. There are a couple of apps you may wish to install via software manager,
1. "Linssid"
2.I occassionaly use "Wicd network manager" to mange my wireless connections.
Thanks for the app ideas, which I'll explore.
What I meant was, among other things, how I can see if it's dropped packets, etc. But also, well, using my wife's Compaq laptop as an example, the wireless adapter for that is recognized and working under Mint xfce (which is all my wife uses, and she has no easy Ethernet-cable access from where she uses the laptop). But it works badly! It's barely adequate for her. I borrowed her laptop to give a public presentation to a roomful of people, and I couldn't get a decent connection in that room to the router in the next room. However, I have Win 10 on the machine also — and when I boot into that, the wireless adapter works very well! The laptop is a low-end model bought new in spring 2015.
After my wife had ongoing connection trouble with the WLAN in our house, I finally set up a repeater near where she works downstairs. (I used an old consumer-grade D-Link router that I had retired a few years ago but still had in the closet.) In Windows, though, I wouldn't need the repeater in our house to have a good wireless connection.
It turns out that many of the peripheral manufacturers are not forthcoming about what info they let out to open-source developers as to the exact architecture of their products. So Linux tinkerers and others have to reverse-engineer the hardware to write open-source drivers that work reasonably well. But Microsoft (or Apple) has an advantage, because the OEM peripheral manufacturers share the architecture details with big commercial OS houses under mutually beneficial contracts and non-disclosure agreements.
It means that Linux and other open-source or little-guy-OS coders are at a disadvantage to Microsoft (or Apple) in some cases. I'd tend to want to boot into Windows if I know the wireless adapter functions well there, when I also know it works like crap under Linux.
So that's what I had in mind. The computer I just installed the driver on in Mint also dual-boots to Windows, and I am in Windows a lot of the time because I need to run some complex Office VBA stuff that I can't replicate well under Linux. (OK, I could run it under a Windows guest OS in a VM under Linux, and I have done that before; but won't it be relying on the host OS's connectivity anyway? And also, well, must I publicly confess that I like Windows 10 pretty well anyway, along with liking Linux?
)
So I could test the wireless functionality for this adapter under both Win 10 and Linux Mint (with the driver I installed) and compare how well the Linux one actually works.
P.S. To Pjotr: thanks again for your help!
/dr