61–70 of 148 posts
This is for 5ghz AP (access point) mode. As a station/client it works fine. A workaround here https://tildearrow.org/?p=post&month=7&year=2022&item=lar
> since it does not disable LAR at all, it inherits the issue of requiring a 5GHz access point to be active and near the card in order to detect a 5GHz-able country.
This is for 5ghz AP (access point) mode. As a station/client it works fine. A workaround here https://tildearrow.org/?p=post&month=7&year=2022&item=lar
"Intel wireless cards are among the best for Linux, with support for new devices landing even before they are released. however, they have one big drawback: LAR (Location-Aware Regulatory).
basically the card detects in which country it is (and therefore the regulatory domain) based on nearby access points' ones, and doesn't let you change it manually. the sad thing is that it often sets the card to the wrong country, which is a problem.
prior to Linux 5.5 there was an option to disable this annoying feature in the iwlwifi module (lar_disable=1), but it was removed as later firmware versions caused card crashes and Intel claimed the option shouldn't be accessible anyway "
Earlier quoted context omitted.
Is there a patch for the kernel 6 line to add back the lar_disable functionality?
This was the patch that removed it: https://github.com/torvalds/linux/commit/f06021a18fcf8d8a1e7... But this commit message is burying the lede a bit. There are two problems here: 1) you can revert the change, but a large part of the regulatory logic lives in the firmware blob running on the chip and you can not change this. 2) the FCC doesn't look kindly upon functionality that ignores regulatory limits being availa…
Considering the average user would never bother to set their correct regdomain when they buy a crap Chinese wifi router, you are pretty much guaranteed to always be using the wrong (mostly CN) regdomain, because that's what your neighbours are using...
This is for 5ghz AP (access point) mode. As a station/client it works fine. A workaround here https://tildearrow.org/?p=post&month=7&year=2022&item=lar
What insane lengths are people prepared to go to to work around this issue, and still... > since it does not disable LAR at all, it inherits the issue of requiring a 5GHz access point to be active and near the card in order to detect a 5GHz-able country.
The link seems to be experiencing a mysterious outage, reporting "404" when I visit the page. Other bugs seem to be fine. Not sure what's going on. Here's a mirror: https://web.archive.org/web/20230317164517/https://bugzilla....
The admins probably got grumpy because a bajilion HN bots querying for link previews DDOS'ed the whole bugzilla.
Earlier quoted context omitted.
What insane lengths are people prepared to go to to work around this issue, and still... > since it does not disable LAR at all, it inherits the issue of requiring a 5GHz access point to be active and near the card in order to detect a 5GHz-able country.
[flagged]
- outside of the Apple ecosystem of course, because it's literally the only choice. For anything else, any recent Linux distro provides better tools and better UX, so why bother with Apple's ecosystem, lack of package manager that doesn't suck, compatibility issues left and right (can you run a VM on M Macs now? Kind of, sometimes, depends on how much you pay to whom; containers are still a pain), an undebuggable and uncustomisable OS, etc. etc.
Earlier quoted context omitted.
What insane lengths are people prepared to go to to work around this issue, and still... > since it does not disable LAR at all, it inherits the issue of requiring a 5GHz access point to be active and near the card in order to detect a 5GHz-able country.
[flagged]
Earlier quoted context omitted.
Is there a patch for the kernel 6 line to add back the lar_disable functionality?
This was the patch that removed it: https://github.com/torvalds/linux/commit/f06021a18fcf8d8a1e7... But this commit message is burying the lede a bit. There are two problems here: 1) you can revert the change, but a large part of the regulatory logic lives in the firmware blob running on the chip and you can not change this. 2) the FCC doesn't look kindly upon functionality that ignores regulatory limits being availa…
It also doesn't seem to be that much of an issue for other vendors to allow the user to configure their regulatory locale, it definitely raises the question how necessary this current approach is.
In the end, Intel's current LAR implementation hurts users that want to use their hardware within their locale's regulatory limits. It does not prevent intentionally misleading the LAR implementation or acquiring other equipment to be disruptive. To me it seems to achieve very little positive, and I've not even touched the freedom aspect of Linux being violated.
This is for 5ghz AP (access point) mode. As a station/client it works fine. A workaround here https://tildearrow.org/?p=post&month=7&year=2022&item=lar
What insane lengths are people prepared to go to to work around this issue, and still... > since it does not disable LAR at all, it inherits the issue of requiring a 5GHz access point to be active and near the card in order to detect a 5GHz-able country.
Earlier quoted context omitted.
What insane lengths are people prepared to go to to work around this issue, and still... > since it does not disable LAR at all, it inherits the issue of requiring a 5GHz access point to be active and near the card in order to detect a 5GHz-able country.
[flagged]