Looks like a way to save a process to a file and restart it from that later, maybe even on a different host.What's that? A suspend/resume like Linux has?
Looks like a way to save a process to a file and restart it from that later, maybe even on a different host.What's that? A suspend/resume like Linux has?
That should be fixed long time ago with the following commit (wonder what release you are running) and I used corsair k65 back in 2020:I don't know if my Corsair K70 keyboard will get properly detected with the new kernel.
I'm using it but in BIOS mode that gets a annoying blinking led all time and no function keys at all.
So I will be pleased with bug and security fix and that's it.
commit d4028678f27c762603661745f86896cb2870109c
Author: Hans Petter Selasky <hselasky@FreeBSD.org>
Date: Thu Feb 13 16:03:12 2020 +0000
Improve USB gaming keyboard support.
Add support for decoding pressed keys as a bitmap. The keys in the
bitmap are described in the interface specific HID descriptor. Some
keyboards even have multiple input interfaces, only using the bitmap
method when the event array is full. That typically means when more
than seven keys are pressed simultaneously.
The internals of the USB keyboard driver have been slightly reworked
to keep track of all keys in a single bitmap having 256 bits. This
bitmap is then divided into blocks of 64-bits as an optimisation.
Simplify automatic key repeat logic, because only the last key pressed
can be repeated.
PR: 224592
PR: 233884
Tested by: Alex V. Petrov <alexvpetrov@gmail.com>
MFC after: 1 week
Sponsored by: Mellanox Technologies
It does not seem to work with this keyboard.That should be fixed long time ago with the following commit (wonder what release you are running) and I used corsair k65 back in 2020:
Code:commit d4028678f27c762603661745f86896cb2870109c Author: Hans Petter Selasky <hselasky@FreeBSD.org> Date: Thu Feb 13 16:03:12 2020 +0000 Improve USB gaming keyboard support. Add support for decoding pressed keys as a bitmap. The keys in the bitmap are described in the interface specific HID descriptor. Some keyboards even have multiple input interfaces, only using the bitmap method when the event array is full. That typically means when more than seven keys are pressed simultaneously. The internals of the USB keyboard driver have been slightly reworked to keep track of all keys in a single bitmap having 256 bits. This bitmap is then divided into blocks of 64-bits as an optimisation. Simplify automatic key repeat logic, because only the last key pressed can be repeated. PR: 224592 PR: 233884 Tested by: Alex V. Petrov <alexvpetrov@gmail.com> MFC after: 1 week Sponsored by: Mellanox Technologies
I'm really confused with wifi card support being an issue/barrier for people. Anyone with a screwdriver can swap a laptop's wifi card with one supported by FreeBSD. Even laptops with soldered-on RAM almost always have removable standard wifi cards.
$30 or so for a supported card and you're golden. I've done this for countless Windows and Linux laptops.
Soldered RAM, soldered SSD, soldered WIFI, glued-in battery. Built-in obsolescence by design. Proprietary screws, and parts/upgrades that cost 5-10 times over commodity pricing.Most issues described here are resolved in a macbook.
Sorry for posting this one here but what driver should it use?That should be fixed long time ago with the following commit (wonder what release you are running) and I used corsair k65 back in 2020:
Code:commit d4028678f27c762603661745f86896cb2870109c Author: Hans Petter Selasky <hselasky@FreeBSD.org> Date: Thu Feb 13 16:03:12 2020 +0000 Improve USB gaming keyboard support. Add support for decoding pressed keys as a bitmap. The keys in the bitmap are described in the interface specific HID descriptor. Some keyboards even have multiple input interfaces, only using the bitmap method when the event array is full. That typically means when more than seven keys are pressed simultaneously. The internals of the USB keyboard driver have been slightly reworked to keep track of all keys in a single bitmap having 256 bits. This bitmap is then divided into blocks of 64-bits as an optimisation. Simplify automatic key repeat logic, because only the last key pressed can be repeated. PR: 224592 PR: 233884 Tested by: Alex V. Petrov <alexvpetrov@gmail.com> MFC after: 1 week Sponsored by: Mellanox Technologies
As I look through the changes/features I have to wonder if this really warranted a .0 release. Perhaps more appropriately 13.3? What do others think? Maybe adjust the question to be "what features/changes do you feel warranted bumping to 14.0?"What's your favourite new feature?
As I look through the changes/features I have to wonder if this really warranted a .0 release.
Perhaps more appropriately 13.3? …
I'm really confused with wifi card support being an issue/barrier for people. Anyone with a screwdriver can swap a laptop's wifi card with one supported by FreeBSD. Even laptops with soldered-on RAM almost always have removable standard wifi cards.
$30 or so for a supported card and you're golden. I've done this for countless Windows and Linux laptops.
$ uname -bimoprs
FreeBSD 14.0-RC4 arm64 aarch64 GENERIC bf03a8d54af18e2b9e21ee3d52c4e243e19e965e
$ speedtest-go
...
✓ Latency: 5.005271ms Jitter: 522.785µs Min: 4.288402ms Max: 5.759092ms
✓ Download: 926.09Mbps (used: 1103.99MB)
✓ Upload: 598.00Mbps (used: 712.88MB)
My Thinkpad X1 Carbon Gen9 does have a non-soldered & non-glued WiFi card (AX210 is what I ordered it with).I'm also reasonably sure some Thinkpad or other has a soldered Wifi chip (X1 Carbon?).
Historically speaking FreeBSD is known for its quality networking stack. So much that Facebook put money into the Linux ecosystem to compete: https://www.phoronix.com/news/MTc1NjYI was quite surprised to see pi4 do this well!
How about$ uname -bimoprs
FreeBSD 14.0-RC4 arm64 aarch64 GENERIC bf03a8d54af18e2b9e21ee3d52c4e243e19e965e
$ speedtest-go
...
✓ Latency: 5.005271ms Jitter: 522.785µs Min: 4.288402ms Max: 5.759092ms
✓ Download: 926.09Mbps (used: 1103.99MB)
✓ Upload: 598.00Mbps (used: 712.88MB)
I was quite surprised to see pi4 do this well!
uname -urk
? I have the k68 as well and I have that blinking light too and it's a little annoying but it's not terrible.I don't know if my Corsair K68 keyboard will get properly detected with the new kernel.
I'm using it but in BIOS mode that gets a annoying blinking led all time and no function keys at all.
So I will be pleased with bug and security fix and that's it.
it's not the blinking led what mostly bugs me, I could cover it with a tape if I wanted, the problem is the functions keys, multimedia shortcuts, sound volume/mute etc.I have the k68 as well and I have that blinking light too and it's a little annoying but it's not terrible.
I have learned to not expect THAT stuff to work very well under FreeBSD. Function keys can be reprogrammed under FreeBSD (F5 works to refresh a browser page), but every keyboard maker does multimedia slightly different.it's not the blinking led what mostly bugs me, I could cover it with a tape if I wanted, the problem is the functions keys, multimedia shortcuts, sound volume/mute etc.
That is not what I am finding. Maybe something changed.Incidentally, sh(1) is not a default for non-root users.
# echo $0
echo $0
sh
# adduser
adduser
Username: user
Full name: user
Uid (Leave empty for default):
Login group [user]:
Login group is user. Invite user into other groups? []: wheel video
Login class [default]:
Shell (sh csh tcsh nologin) [sh]:
author Scott Long <scottl@FreeBSD.org> 2002-12-03 05:41:09 +0000
committer Scott Long <scottl@FreeBSD.org> 2002-12-03 05:41:09 +0000
+#### END SUBROUTINE DEFENITION ####
+
+THISCMD=`/usr/bin/basename $0`
+DEFAULTSHELL=/bin/sh
+ADDUSERCONF="${ADDUSERCONF:-/etc/adduser.conf}"
+PWCMD="${PWCMD:-/usr/sbin/pw}"
+MAILCMD="${MAILCMD:-mail}"
+ETCSHELLS="${ETCSHELLS:-/etc/shells}"
EXAMPLES
defaultshell=/bin/csh
Some laptops even worse.I have just seen a laptop with glued in Wifi M.2 card.
I'm also reasonably sure some Thinkpad or other has a soldered Wifi chip (X1 Carbon?).