Screen fonts & mode in local terminal issue
-
Dear pfSense Gurus!
The IBM local console monitor are connected trough ATEN KVM CS64US (latest firmware updated).
How to fix issue with characters set (if I make a right conclusion), see the picture attached.I need to start btop, and mc file manager. But with both - I have the same issue…
Note:
- This is pfSense 2.8-BETA on FreeBSD 15-CURRENT;
- On FreeBSD 15.0-CURRENT there are no any issues with the same btop and mc.
This push me thinking that some Netgate’s BSD modifications are roots of this issue… No?
May be some corrections in loader.conf, etc/defaults/rc.conf, login.conf, /boot/device.hints, or additional fonts, etc… needed ?
-
Wow ... Midnight Commander !
( thought that one was doing only ftp ... )Btw : sftp with, for example, the free WinSCP, does the job for me.
I'm in France so I solved all the éà$¤ issues with :
pfSense runs in its native language.
The devices I uses us the same native language.
Not a (perfect solution), but no more "codepage" or OS language issues or whatever the like. -
@Gertjan said in Screen fonts & mode in local terminal issue:
Wow ... Midnight Commander !
( thought that one was doing only ftp ... )Btw : sftp with, for example, the free WinSCP, does the job for me.
For me ftp/sftp etc file transferring in any source/destination (include clouds) complete doing well Forklift.
In pfSense MC sometimes help to quickly operate with files inside systems. And great feature of MC - he has own shell.
I'm in France so I solved all the éà$¤ issues with :
pfSense runs in its native language.
The devices I uses us the same native language.
Not a (perfect solution), but no more "codepage" or OS language issues or whatever the like.Already have in /etc/loader.conf
:charset=UTF-8:\ :lang=en_US.UTF-8:\ :setenv=LC_COLLATE=C:\ :umask=022:
But unsuccessfully, - the result You able to see above….
-
It appears the same on the local console? Or over SSH?
-
@Sergei_Shablovsky said in Screen fonts & mode in local terminal issue:
Already have in /etc/loader.conf
:charset=UTF-8:
:lang=en_US.UTF-8:
:setenv=LC_COLLATE=C:
:umask=022:But unsuccessfully, - the result You able to see above….
Those are not
loader.conf
configuration directives, those look like/etc/login.conf
configuration. (And read the note at the top of that file, especially the part where you have to runcap_mkdb /etc/login.conf
after any edits)It does seem like you have some sort of issue/mismatch with UTF-8 handling somewhere, but it's hard to say exactly where. I have no issues with UTF-8 in my terminals over serial or SSH but I have no idea what that KVM setup might be doing.