FreeBSD Screen Shots

I think I may just be scratching the surface here. Even ricing the mouse cursors changes everything on these DE's that I am foreign to wow. I3 and vtm are my next adventures
 

Attachments

  • xfceonbsd.png
    xfceonbsd.png
    1.1 MB · Views: 79
teo said:
The ram memory displays only a part of the hardware that may be consuming the other hardware of the machine. On low resource machines it is necessary to take into account when doing critical work such as compiling or viewing videos on YouTube unless the consumption immediately goes through the roof.
Click to expand...
Unused memory is wasted memory!!. The number shown include buffers, zfs ARC and so forth so that is actually a good thing for performance. And most of it will be freed up when needed for more important stuff.
 
teo said:
In the screenshots (graphical desktop environments or window managers) you can see high resource consumption for example 3257 MiB from where I started my answer.
Click to expand...
I understand the reason of your comment.
I did a check on what was causing that in my screenshot and it was the Code OSS that was causing that 3GB memory allocation.
The DE by itself is near 1GB RAM.
 
Xorg with amd and nvidia is broken for me .. so i thought - Wayland is the next step !
Nothing spectacular for now as many things needs to worked out and configured.
Running on AMD.
 

Attachments

  • 20250315_14h01m38s_grim.png
    20250315_14h01m38s_grim.png
    1.4 MB · Views: 83
astyle said:
Then how come your neofetch is quoting NVidia Quadro GPU?
Click to expand...
Because its neofetch lol. Later ill check up again when ill pass my nvidia to bhyve but if i recal it will show as well.
Its standard Neofetch config, no touching done and on FreeBSD it works differently than Linux.
One of those thing with it.
 
larshenrikoern said:
Unused memory is wasted memory!!
Click to expand...

Yes, a nice phrase I've been reading for years.
And what about the temperature of laptops? These days, they're slim or extra-flat in their chassis, and the temperature skyrockets.
When you turn off the laptop, you can't touch it because it's so hot, especially on the base/rest.
Not to mention if I connect any ports, it's a drag.
This is in my experience with an AMD Ryzen 7 5700u with 16GB of RAM from Dell. Everything is great with AMD; they're faster than Intel, but they get hot, and it's no joke. I don't know what's happening with these processors in desktop computers I don't have, but laptops get hot, and quite a bit.
My conclusion: less RAM equals lower operating temperatures and longer internal battery life.
Logically, a longer laptop life.

Let's continue with the screenshots..
 
GlitchyDot said:
Because its neofetch lol. Later ill check up again when ill pass my nvidia to bhyve but if i recal it will show as well.
Its standard Neofetch config, no touching done and on FreeBSD it works differently than Linux.
One of those thing with it.
Click to expand...
So, I can expect neofetch to just ask ChatGPT which GPU to display? and what if it thinks that it should display Voodoo next? or something else, other than the real GPU one has? Yeah, I guess I should not trust anybody's screenie if it includes neofetch, because neofetch cannot be relied on to quote the correct GPU. 😂
 
rmomota said:
I understand the reason of your comment.
I did a check on what was causing that in my screenshot and it was the Code OSS that was causing that 3GB memory allocation.
The DE by itself is near 1GB RAM.
Click to expand...
Thanks for understanding, in my tests of desktop environments called Xfce from the beginning it is from 600 to 650 MiB approximately, in Lxde from 350 to 450 MiB approximately.
 
astyle said:
So, I can expect neofetch to just ask ChatGPT which GPU to display? and what if it thinks that it should display Voodoo next? or something else, other than the real GPU one has? Yeah, I guess I should not trust anybody's screenie if it includes neofetch, because neofetch cannot be relied on to quote the correct GPU. 😂
Click to expand...
You are right. FreeBSD and Linux with neofetch works differently. Im going to fidle around now but i think show all gpus / show one gpu etc on gpu side does not work as intended.
 
astyle said:
So, I can expect neofetch to just ask ChatGPT which GPU to display? and what if it thinks that it should display Voodoo next? or something else, other than the real GPU one has? Yeah, I guess I should not trust anybody's screenie if it includes neofetch, because neofetch cannot be relied on to quote the correct GPU. 😂
Click to expand...
Left side is neofetch config - you see it shows gpu_type = "all" and check what my neofetch shows.
 

Attachments

  • 20250315_14h16m09s_grim.png
    20250315_14h16m09s_grim.png
    1.1 MB · Views: 70
I guess some hardware setups do confuse the hell out of neofetch... most people probably don't have 2 or 3 different GPUs installed on the same mobo, especially not expensive high-performance stuff like yours, GlitchyDot ... Even the rig where my RX 6900 XT lives.
 
astyle said:
I guess some hardware setups do confuse the hell out of neofetch... most people probably don't have 2 or 3 different GPUs installed on the same mobo, especially not expensive high-performance stuff like yours, GlitchyDot ... Even the rig where my RX 6900 XT lives.
Click to expand...
GPU info mostly for Linux ( even in config it stated ) but this is config file located in .config/neofetch directory but you can play around with actual neofetch file and do some changes ( did it before )
As i said - Neofetch in FreeBSD is bit different than Linux as by end of the day its written in Bash if i recall correctly and BSD is not the main OS for ricers :)
P.s. im still have one more gpu but cant be bothered to put it back in for now :D
 
GlitchyDot said:
Left side is neofetch config - you see it shows gpu_type = "all" and check what my neofetch shows.
Click to expand...
No matter how much you enlarge the image, you can't see the details, that happens with the window managers called i3 and others, terrible configurations that you can't even see the details.
 
teo said:
No matter how much you enlarge the image, you can't see the details, that happens with the window managers called i3 and others, terrible configurations that you can't even see the details.
Click to expand...
You know you can zoom in right :) its 4k res picture im sure you can see if you click on image and once it opens, click again so its zooms in and then use mouse to move picture around :)
 
GlitchyDot said:
You know you can zoom in right :) its 4k res picture im sure you can see if you click on image and once it opens, click again so its zooms in and then use mouse to move picture around :)
Click to expand...
Edit:

Sorry, I was able to zoom in and see the details.

16017 MiB on Hyprland
 
teo said:
No, I don't have a 4K TV, I'm only on a 1366x768 laptop, so you can imagine that no matter how much I maximize the image I can't see anything and worse details
Click to expand...
Dont zoom in web browser , zoom in actual picture or click right mouse on picture - open in new tab, once it opens - click on picture again and it will zoom in and click with mouse again (dont release mouse click ) and move around. I know you can do it :) dont make me spend few hours doing my 1366x768 thinkpad x220 to see if you can see it or no :D
 
teo said:
Edit:

Sorry, I was able to zoom in and see the details.

16017 MiB on Hyprland
Click to expand...
Incorrect. Its because was many packages running.plus zfs. so mostly of that memory was used by chromium.
I usually have around 20+ tabs open, something in the background, mpv, 2 or 3 terminal tabs or actual terminals so all this ads up.
Hyprland - 402Mib
Xwayland - 179Mib
Waybar - 69Mib
 
fmc000 said:
I'm not sure this question makes any sense. Xorg is an executable program that's always running, Wayland is not.
Click to expand...
Indeed it doesn't make much sense. I guess it depends on the Wayland compositor?

Xorg+i3 vs Sway is probably a more fair comparison.

I am going to assume Xorg+i3 is heavier because it does quite a bit more out of the box and isn't monolithic in the way that the separate i3 WM needs to communicate across the UNIX domain socket.
 
You must log in or register to reply here.
Back
Top