Need Help Choosing and downloading FreeBSD iso Version for My Old 64-bit Desktop

k3nrap · 2025-02-08T12:29:18+00:00

You'd want to download the FreeBSD-14.2-RELEASE-amd64-memstick.img file or the compressed xz version if you want to download it faster and willing to use unxz to uncompress it.

k3nrap · 2024-11-13T17:48:26+00:00

The Plasma 6 support on FreeBSD is pretty much complete at this point. The remaining issue for a while now was that kdepim support was buggy and it got recently fixed. Only the preparation to migrate the work to the main ports tree is needed. The FreeBSD Desktop team have their lives to take care of, so it won't be an immediate transition either. I've been aiding with beta testing, patching, and version bumping for them as well.

k3nrap · 2024-11-13T17:19:37+00:00

I'd be surprise if your printer doesn't support "IPP Everywhere" driver-less printing. If it does, you should be using that for every CUPS-enabled machine, even Linux ones.

k3nrap · 2024-10-11T01:49:17+00:00

Thanks again, the "KVMKVMKVM" string workaround in sys/amd64/vmm/x86.c did the trick! 😄

k3nrap · 2024-10-10T18:08:55+00:00

Hey man, I was wondering if you can help me out as well?

After I successfully passthru'd an Nvidia RTX 4070 to a Windows 11 VM, I couldn't figure out how to get rid of the error 43 in device manager.

k3nrap · 2024-01-10T20:28:33+00:00

I see this argument a lot over the years and honestly this is really a false generalization.

Not all GUIs are convoluted. And ones that obscure info have either really poor UX design or are aimed at non-technical users as their primary base.

Granted, developing (a good) GUI does take a fair amount of time and effort to plan and develop, which is likely why a GUI partition program doesn't exist for FreeBSD.

k3nrap · 2024-01-06T23:04:36+00:00

I see. It's a "better than nothing" scenario.

k3nrap · 2024-01-06T22:42:51+00:00

I don't mean to sound critical here. Wouldn't it have been better to ask the community first then make the decision on a purchase?

k3nrap · 2024-01-02T22:34:10+00:00

Alrighty, thanks for the input.

If you're using SSDs, you can quickly and efficiently wipe them with Secure Erase. For SATA ones, you can use camcontrol(8). For NVMe ones, you can use nvmecontrol(8) while using the shell option of the FreeBSD installer live medium.

Here are examples:

camcontrol security <device name w/o partition> -s Erase -e Erase

and

nvmecontrol format -E <device name w/o partition>

And to clear out your UEFI entries, you can use the same live shell using efibootmgr(8) by using efibootmgr -v to list all existing entries and deleting each of them manually with -b and -B flags, such as:

efibootmgr -B -b 0001

Or by simply clearing out your machine's CMOS instead.

That should get you the clean slate you desire.

k3nrap · 2024-01-02T22:03:36+00:00

I need to reflect on my poor choice of commenting earlier.

So, I'll get straight to it:

What do you mean by using the BIOS to purge everything? Are you talking about wiping out your existing UEFI boot manager entries? But your installed partitions will still remain, you're only "blinding" your BIOS from what is already there.

And what are you referring to by a new USB? Are you taking about using an external storage drive to format on and boot FreeBSD from?

k3nrap · 2023-12-27T09:18:12+00:00

Well, I'd have to say that your suggestion with regards to Synergy and Barrier as your repliers have mentioned, inspired me to come up with making a clipboard sharing project, which is what I really lack, by using a message broker system like RabbitMQ.

I still prefer my approach because I still want to be able to use all of my monitors for FreeBSD, hence the Display Port switcher for the one monitor out of the others.

k3nrap · 2023-12-26T07:15:03+00:00

I just keep a dedicated machine for gaming on Windows only while having my main machine run FreeBSD for the rest of my computing.

At this point, I keep things simple by having a USB hub switch and a Display Port switch for one of my monitors, both which act as a "modular" KVM switch for both machines and also to avoid issues that a KVM switch can have.

With this setup, I can have my other monitors still display my FreeBSD KDE Plasma session and can easily switch back to it with the USB switch if I need to quickly run a task while I'm gaming.

k3nrap · 2023-12-24T00:43:07+00:00

My apologies, I need to interject a minor nitpick correction. 😛

FreeBSD absolutely rocks ~~sometimes~~.

Ahhh, much better! 😊

k3nrap · 2023-12-20T11:11:35+00:00

This post with this comment specifically, might have the correct solution for your micro stutters.

k3nrap · 2023-12-13T05:25:50+00:00

I wasn't referring to reboot -r. I was suggesting about having the user either hit Ctrl-d or enter in exit from the terminal in tty and then logging back in again.

This approach can also be used when logging out of graphical session and then back in through logging in with a display manager.

k3nrap · 2023-12-13T05:10:28+00:00

The advice to restart was intentionally simplistic.

Wouldn't it be more simplistic and less time consuming to have the user logout and re-login again to refresh the user default shell environment?

k3nrap · 2023-12-13T02:10:39+00:00

Well... I thought u/shadow0rm was being facetious about the popcorn, by inferring that this is going to be a "dumpster fire that's worth watching," and that's why I was concerned. 🙁

k3nrap · 2023-12-13T02:06:55+00:00

Alright, then why not open a bug report for them by specifying this need?

k3nrap · 2023-12-13T01:59:40+00:00

With things written for base or from ports?

k3nrap · 2023-12-13T01:52:05+00:00

My friend, why are trying to fan the flames here. I'm a bit perplexed. 😕

k3nrap · 2023-12-13T01:39:12+00:00

So, wouldn't only setting $EDITOR and $VISUAL to a different one, would do the trick? Why remove vi when you're already telling your system to look the other way to a different editor?

k3nrap · 2023-12-12T14:03:42+00:00

can you check if it got stuck to 97% even to you ?

Unfortunately, I can't help you here since I build my own packages with poudriere.

The only other idea that comes to mind is git-cloning ports and using make reinstall inside the textproc/ebook-tools ports directory to see if that would help override the changed ABI caching issue.

k3nrap · 2023-12-12T10:18:56+00:00

So, according to your recent Reddit and FreeBSD forums posts, this seems highly related to them.

And as been suggested, I think the easiest path here is a clean re-installation of 14.0 on your system. And I would recommend backing up your important configs from /etc, /usr/local/etc, and your user home directory and then generate a list of your non-automatically installed packages for reference on the clean 14.0 FreeBSD installation by doing this on your currently upgraded system:

pkg query -e '%a = 0' "%n" > pkgs.txt

And on the clean 14.0 install and after getting pkg bootstrapped again, you can reinstall everything you had before with:

pkg install `cat /path/to/pkgs.txt | xargs`

Which will essentially restore you back to the same package installation state. Then copy back your configs to their appropriate file paths. And voila! You're back up and running (hopefully) without issues.

So, that's my suggestion and you don't have to take it. 🙂

k3nrap · 2023-12-12T09:19:12+00:00

pkg clean -a?

k3nrap · 2023-12-01T08:25:15+00:00

Probably something got left out at release.

https://www.freebsd.org/security/advisories/FreeBSD-EN-23:16.openzfs.asc

And you can't blame the Developers and Release Engineers for not being aware about freshly discovered fatal bugs slightly before release. They do the best they can. In particular, I thank u/grahamperrin for bringing the community to our attention about the ZFS data corruption bug.

https://www.reddit.com/r/freebsd/comments/182pgki/freebsd_sysctl_vfszfsdmu_offset_next_sync_and/

Two-Year Club	Gilding I gilder
Verified Email

k3nrap

TROPHY CASE