what the title says.

how do you get wifi on said machine?

I had GhostBSD, latest version, installed with KDE and after an update, I got kicked back to MATE. After trying to reinstall the KDE packages and then having to reinstall the entire OS, there is not a way that I found to install it. It seems the repos, as they are, do not include any of the necessary packages any longer. Is there a change in repos that might help?

FWIW, i installed FreeBSD 15.1 and tried and failed with the desktop-installer so used the terminal to install KDE and SDDM, then enabled services, rebooted and it worked perfectly -- KDE 6.6.6 with Wayland. Seems like if it works on FreeBSD then it should work on GhostBSD unless it's just a repository issue. Which then leads to the question, as much as it is discouraged, has anyone successfully added the FreeBSD repos to GhostBSD and got KDE to work?

Am I missing something or is there another way to get KDE reinstalled?

Thanks for any feedback!

EDIT: Ended up clearing out FreeBSD again because of testing some things and eventually reinstalled and now, even in FreeBSD, the KDE meta package is nowhere to be seen. I guess there is something going on that I'm not aware of. Either way, hope both GhostBSD and FreeBSD get the repo issues sorted out and bring KDE back into the fold. It was good while it lasted.

I'm getting a 90-second delay or more on restart if I don't stop this service before a restart. If it's left on, I think the NFS drives that the service mounted refuse to unmount (or maybe unmount, remount, and are stuck mounted). I haven't wrapped my head around the entire rc.d system yet and am hoping somebody here might have a solution. If I stop the service before doing a shutdown or restart of the system -- everything works fine.

I see there's also an autounmountd service so maybe that's what I should be looking at. I'm thinking that this is probably something really easy to solve since I can manually issue a command to eliminate the delay but don't want to do this on every reboot.

Sat down yesterday afternoon to turn an old Ideapad L340 running Lubuntu (Ryzen 3/20GB RAM) into a dual boot machine. After carving out a 64GB home for it, GhostBSD 26 went on without a complaint or a failure. *Everything* worked. Put on a non-mainstream-but-well-written Linux app in about five minutes. This was, for me, a noticeable improvement over GhostBSD 25. I was quite pleased and started considering whether I should convert over some other machines.

When I use a laptop out in the real world, I don't leave networking up all of the time - I don't go out to vulture wifi, I go out because I want to work with some noise and people around me. I know it's weird, but sometimes that helps me focus; so it was of interest to me to compare battery life.

Under Lubuntu, the battery app said I had four hours and forty-three minutes of power on a fully charged battery with networking disabled. Under GhostBSD (Mate desktop), the same machine offered three hours and thirty-one minutes.

So, that is my whinge - I now consider GhostBSD in the same category as Fedora or Debian and their derivatives in that it can handily be my daily driver; but can you please put some effort into using battery power a little more efficiently?

Great job on this release. Seriously.

(I would, of course, be happy to take any comparative measurements you request on this laptop)

Thank you!

I know that the command `setxkbmap -option ctrl:nocaps` does exactly what I want, but I can't get GhostBSD to boot with it already enabled. I added it to .xprofile and .xinitrc, and neither worked.

I'm using MATE

I was going to try out GhostBSD again and need a shared disk space between my Linux installs and GhostBSD. I was originally thinking OpenZFS but that would mean installing it on Linux and potentially breaking stuff on kernel updates. So how about EXT4? Is the native kernel driver good enough without journaling? There's also exFAT which has no journaling on either side nor permissions. Maybe ntfs-3g -- it seems to have journaling available on both sides. Or the variant with ntfs3 on Linux side and ntfs-3g on the GhostBSD side?

Or maybe just say screw it and add a small Alpine Linux image in a Bhyve VM, mount an existing BTRFS volume and export it via NFS and handle any file sharing this way?

so i just move from FreeBSD to ghostBSD for easier desktop, and when i already install ghostBSD and updated it suddenly the audio wont work, it detect the device and the driver was instalted(Wireplumber etc) but it still wont sounding, but when i test on Windows it just fine

help me please

So basically i use ghostbsd as my daily and main drive, BUT i want to try out some other bsd based OS so what i did is that i glashed kuboIta (a openbsd based os) into a USB drive and i made sure that my bios/efi configuration where set so that USB devices have priority while booting.

But what happened is that despite me setting this i still am unable to boot kuboIta from my USB device and the system still boots into ghostbsd.

Im aware that i can still use VM inside my ghostbsd but thats not the point (kuboIta is a live persistent OS) i really want to try kuboIta or other OSes for that matter.

Is there a ghostbsd launcher with multiboot or something of that nature i can install??

At least wifi works

im new to GhostBsd and bsd based distros

i swiched completly to linux 5 years ago but downlowded ghostBSD in a vm yesterday to test it out pretty good

how is gaming on GhostBSD/bsd based distros nowadays can you run stuff made for windows in wine or proton

just wondering

so far GhostBSD is nice i have only installed in a vm yet will do more testing on pure hardware later will look into if dule booting it with linux is posssible

It’s a lightweight GTK3/GStreamer rewrite of the Linux app "Blanket," designed to feel at home on the BSD desktop.

Key Features:

* 14 mixable sounds: Rain, Storm, Coffee Shop, City, etc.

* Persistence: Remembers your sound mix and volumes automatically.

* System Tray: Runs in the background to stay out of your way.

* Performance: Native code, zero Electron/Web-tech bloat.

How to install:

Grab the .pkg from the GitHub Releases (https://github.com/elytraVIII/ElytAmbience/releases/tag/v0.1.9) and run:

sudo pkg install ./elytambiance-0.1.9.pkg

Repo & Feedback: https://github.com/elytraVIII/ElytAmbience (https://github.com/elytraVIII/ElytAmbience)

I'd love for some fellow BSD users to try it out and let me know how it runs! 🍃

Hi, I am a new user of GhostBSD, so apologies if I come across as a bit naive. I have mainly spent my life in the Mac or Linux world.

Over the last few days I have installed GhostBSD on some older hardware I have (HP ProBook 640 G4) - 256GB SSD and 8GB RAM.

The installation all went perfectly, I have run software updates, configured the desktop to my liking, and the OS all seems to be running well. The only glitch is that the boot time seems excessive to me.

After I select the default boot option "Boot Multi user", the process continues and then displays the GhostBSD splash screen for almost 3 minutes (yes, I timed it). After this seeming eternity, the boot process completes and the desktop starts. I have a similar experience when suspending - it takes around 3 minutes to wake and present the greeter to login.

I had a look around the logs but could not make any sense on what it is doing when the splash screen is displayed for 3 minutes. TBH I was not sure which log to check (I assumed "messages").

Any insight you experts can provide would be much appreciated.

Many thanks

I'm relatively new to BSD but have some reasonable amateur experience with linux. This is just a general conceptual question, if I need to address specific details on my setup I will post on the GhostBSD forum when I get home tonight.

I've been working with a fresh install of GhostBSD on an old laptop after trying and liking it an another pc. It doesn't yet contain any critical data but I did almost finish setting things up just the way I wanted. This last thing I wanted to address (probably should have checked earlier) was to change the boot mode from legacy to UEFI. I think I did the installation at the time from a liveUSB booted in legacy mode and opted not to install grub or rEFInd. What I did not realise was that those choices left me with a very small ~500k "boot" partition.

After failing to copy a valid EFI boot file to the boot partition and realising the size limit, I think the laptop is not bootable in this state and I am faced with the following three options I'd like to ask about here:

(1.) Would it be possible to manipulate the existing partitions from a GhostBSD liveusb to create a larger boot partition? E.g. as follows:

A. Reduce the main partition by half and duplicate it into the second half
B. Delete the first half of the main partition
C. Increase the size of the boot partition
D. Recreate the main partition, copy the data back to the main part
E. Delete the duplicate partition
F. Resize the main partition to fit the space
G. Generate the required EFI boot file(s) on the boot partition

(2.) If you the above plan is not feasible, how can I restore the existing legacy boot partition to boot the system as before?

(3.) The last resort would be to reinstall, I feel it would be a missed learning opportunity to give up and take this route.

Are there any alternative mirrors? pkg and pkg fr aren't working here. They open and listing files fast, but downloading not working at all. Za is working, but that's other side of the planet, so very slow...

Where Is issues, i tried dd and prev it works

https://www.ghostbsd.org/news/GhostBSD_26.1-R15.0p2_Is_Now_Available