there is net/wifibox as a very good and reliable workaround. it will work in ac mode.
My Nvidia Gtx650 video card works very good in FreeBSD. With driver 470.There's some noise that NVidia GPUs don't play well with FreeBSD any more
AC mode is definitely NOT a problem on FreeBSD. Intel-branded AC cards work very well on FreeBSD. The drivers for wifi cards are very limited - meaning, very few brands are even supported on FreeBSD. But for the brands that are in fact supported by drivers available for FreeBSD (like Intel), AC works fine.there is net/wifibox as a very good and reliable workaround. it will work in ac mode.
I just loaded the site marketwatch, at first scroll up down was laggy, then it crashed outright. Only two tabs were open. Wasn't that way, say, this past march...Please explain as I type this on FreeBSD using Firefox.
What are you doing differently? According to the MAN page for iwlwifi:AC mode is definitely NOT a problem on FreeBSD. Intel-branded AC cards work very well on FreeBSD. The drivers for wifi cards are very limited - meaning, very few brands are even supported on FreeBSD. But for the brands that are in fact supported by drivers available for FreeBSD (like Intel), AC works fine.
Having said that, wifi is still a pain to set up - as I explained earlier in this thread.
While iwlwifi supports all 802.11 a/b/g/n/ac/ax the compatibility code
currently only supports 802.11 a/b/g modes. Support for 802.11 n/ac is
to come. 802.11ax and 6Ghz support are planned.
I have a Lenovo Ideapad 720S-13ARR... and swapped out the wireless card from original Realtek 8288 to Intel 8265 (bought on Amazon), which is an 802.11ac card... and it works, no extra drivers required.What are you doing differently? According to the MAN page for iwlwifi:
This tells me that 802.11ac is not working.
Yeah, I tried stuffing Firefox into a jail, then tried to tell the jail to only use 4 GB of RAM - that was a spectacular failure, limits(1) was not working as documented. So yeah, there's that, too.I just loaded the site marketwatch, at first scroll up down was laggy, then it crashed outright. Only two tabs were open. Wasn't that way, say, this past march...
I limited the RAM usage of my log in account, which Firefox runs under with rctl(8), as shown in Thread limiting-and-dedicating-memory-cpu-usage.89545. My computer with Firefox running hasn't froze up my whole computer anymore. Firefox has crashed, but it didn't bring the whole system down with it. Now my computer runs a lot better.Yeah, I tried stuffing Firefox into a jail, then tried to tell the jail to only use 4 GB of RAM - that was a spectacular failure, limits(8) was not working as documented. So yeah, there's that, too.
ps
and top
, Firefox runs under the login group.Limiting RAM for the entire login account just for Firefox seems a bit impractical for me... what if I want to run Konsole or Blender? will I have to kill the Firefox process completely? Sometimes I want to talk on Discord while doing something else - and Discord works best on Firefox, which competes with other apps for RAM...I limited the RAM usage of my log in account, which Firefox runs under with rctl(8). Thread limiting-and-dedicating-memory-cpu-usage.89545. My computer with Firefox hasn't froze up my whole computer anymore. Firefox has crashed, but it didn't bring the whole system down with it. Now my computer runs a lot better.
It may seem excessive to limit RAM for the main account to limit Firefox, but the main user account doesn't need to have the ability to tie up all of RAM anyway.
Limits in login.conf should be per-process. So even with a firefox consuming 4gigs, you should still be able to run discord and blender, each using another 4 gigs.Limiting RAM for the entire login account just for Firefox seems a bit impractical for me... what if I want to run Konsole or Blender? will I have to kill the Firefox process completely? Sometimes I want to talk on Discord while doing something else - and Discord works best on Firefox, which competes with other apps for RAM...![]()
Do you get AC connectivity though? I believe that is the same NIC in my laptop, and it works without extra configuration, just at 802.11g mode/54mbpsI have a Lenovo Ideapad 720S-13ARR... and swapped out the wireless card from original Realtek 8288 to Intel 8265 (bought on Amazon), which is an 802.11ac card... and it works, no extra drivers required.
How do you check that it's AC connectivity (as opposed to N/G/C/B? For me, the biggest bottleneck was the speed allowed by the AP...Do you get AC connectivity though? I believe that is the same NIC in my laptop, and it works without extra configuration, just at 802.11g mode/54mbps
If this or something else more specific works.Limits in login.conf should be per-process.
That doesn't work either. Can't find npm-node14 or node14 when running the first script in the install process. Have I got to obtain these packages manually?There are two sources :
or![]()
Releases · sec/dotnet-core-freebsd-source-build
Collection of script to build .NET Core under FreeBSD OS (with binary releases) - sec/dotnet-core-freebsd-source-buildgithub.com
cfr![]()
Releases · Thefrank/dotnet-freebsd-crossbuild
Bash script and patches for building dotNET for FreeBSD under Linux - Thefrank/dotnet-freebsd-crossbuildgithub.com
So when I wrote this I was on 13.2-Release (last patch level at the time). In the mean time I changed from Release to Stable. I just realized thatSuspend, Hibernation, Resume
hw.acpi.lid_switch_state=S3
stopped working and now I'm using S5 in the mean time. It is good enough for now.That's because of proprietary DRM (widevine) for which we don't get FreeBSD support/binaries.
There are ways to work around it by running a web browser through Linuxulator: https://forums.freebsd.org/threads/linuxulator-how-to-install-brave-linux-app-on-freebsd-13-0.78879/
vermaden also has us covered: https://vermaden.wordpress.com/2021...art-27-configuration-netflix-signal-telegram/
No matter which wifi hardware I use, they fail, giving a millennia of confusing errors/messages.Wireless interfaces
netwait_enable="YES"
netwait_timeout="120"
netwait_timeout
only seems to be sufficient.Sorry it has taken so long to reply, but I wanted to verify with my laptop, which I do not use very often. A simpleHow do you check that it's AC connectivity (as opposed to N/G/C/B? For me, the biggest bottleneck was the speed allowed by the AP...
ifconfig
will show, like this:Thanks, I'll check it out on my own hardware when I have a chance...Sorry it has taken so long to reply, but I wanted to verify with my laptop, which I do not use very often. A simpleifconfig
will show, like this:
View attachment 16757
This is connected to my home Wi-Fi, which is an 802.11ac router. As you can see, my FreeBSD laptop is only connecting at 802.11g, even though it is an Intel 8260 card
Second to that.Suspend, Hibernation, Resume