And where can I find documentation on sddm, and how to set up black-theme?
Also, the built-in help for KDE in my localized version is from 2018. There are links to online documentation, but how do you tell what applies to FreeBSD from things that only apply to Linux?
And where can I find documentation on sddm, and how to set up black-theme?
Also, the built-in help for KDE in my localized version is from 2018. There are links to online documentation, but how do you tell what applies to FreeBSD from things that only apply to Linux?
Sometimes, the documentation includes a FreeBSD-specific section. If it doesn't - I play with the .conf file a bit, and make an educated guess about where to tell it to look for themes. But I do agree with Menelkir , if KDE offers a config module (I do bother to compile those from ports) for the stuff, try that first.
Here are preliminary instructions I typed up for installing KDE on FreeBSD. Since I am a noob, I will need these instructions looked over with a fine-toothed comb by the community. The more people who can comment on these instructions, the better! Even if you’re the third person in a row to say the instructions look correct, I will find your comment helpful. These instructions apply to computers with integrated Intel graphics.
Instructions for Installing KDE on FreeBSD (Rough Draft)
Enter the superuser/root account by entering % su and the password for the root account. Note that the command prompt on the shell (%, $, #, etc.) is dependent on what user is currently logged in. Therefore, the % should not actually be typed out. Once in the root account, the command prompt will be #.
Run # pkg install -y kde5 sddm xorg drm-kmod firefox
Enter the easy editor to edit the file /etc/fstab by entering the following command: # ee /etc/fstab
Once in the easy editor, on new lines, enter the following two lines: fdesc /dev/fd fdescfs rw 0 0
proc /proc procfs rw 0 0
(See post #33)
Make sure to hit Enter so the file starts on a new line after saving.
Save and exit the easy editor by pushing Esc and following the prompts to save and exit.
Run # mount /dev/fd
Run # mount /proc
Enter the easy editor to edit the file /etc/rc.conf by entering the following command: # ee /etc/rc.conf
Once in the easy editor, on a new line, enter the following line: kld_list="/boot/modules/i915kms.ko"
Make sure to hit Enter so the file starts on a new line after saving.
Save and exit the easy editor by pushing Esc and following the prompts to save and exit. The KMS driver should now be set up.
Go ahead and load the drm driver. Run # kldload /boot/modules/i915kms.ko
Run # sysrc dbus_enable="YES" && service dbus start
Run # sysrc sddm_enable="YES" && service sddm start
Reboot by running # shutdown -r now
If you chose not to reboot, enter # exit to leave the superuser account
When logging in, avoid the Plasma (Wayland) … default that's presented by sddm – for Plasma, Wayland is not yet reliable.
Questions:
What does the -y do in step 2? Should I delete it?
According to astylein post #23, there is “no need to run # kldload /boot/modules/i915kms.ko if you have the kldlist line in /etc/rc.conf as per the wiki.” Is this true? Should step #13 be removed?
Do steps #14 and #15 do the same things as adding the lines sddm_enabled="YES" dbus_enabled="YES"
to the file /etc/rc.conf? If so, is one method better than the other?
What exactly is the final step talking about regarding "Wayland" (taken from KDE’s Wiki)?
What’s the sddm setup GVitaliy was talking about (in post #34, for example)? Is it something I should do as well?
Assuming KDE successfully installed, how do I start it? Do I enter the command % startx?
I will be erasing Ubuntu on my laptop relatively soon and installing FreeBSD again. Shortly thereafter, I will install KDE. This might not be for a week or longer, as I want to reread The FreeBSD Handbook and the beginning chapters of Absolute FreeBSD, 3rd Edition. Thank you to everyone who has responded so far! I will post an update when I have KDE installed.
According to astylein post #23, there is “no need to run # kldload /boot/modules/i915kms.ko if you have the kldlist line in /etc/rc.conf as per the wiki.” Is this true? Should step #13 be removed?
Do steps #14 and #15 do the same things as adding the lines sddm_enabled="YES" dbus_enabled="YES"
to the file /etc/rc.conf?
As long as you know that # sysrc sddm_enable="YES" && service sddm start is in fact the same thing as ( adding the line sddm_enable="YES" to /etc/rc.conf and rebooting), you can just pick one, and do it just once, no need to repeat that step in its many variants.
I run Plasma Wayland as per developer blog at euroquis.nl, but that's without SDDM - the two don't play well with each other at time of this post. I did my homework on how to make that work, and I have the patience with shortcomings of such bleeding-edge stuff.
As long as you know that # sysrc sddm_enable="YES" && service sddm start is in fact the same thing as ( adding the line sddm_enable="YES" to /etc/rc.conf and rebooting), you can just pick one, and do it just once, no need to repeat that step in its many variants.
I run Plasma Wayland as per developer blog at euroquis.nl, but that's without SDDM - the two don't play well with each other at time of this post. I did my homework on how to make that work, and I have the patience with shortcomings of such bleeding-edge stuff.
Nah, just reboot, get to SDDM, enter your login credentials, and select Plasma (not Plasma Wayland) session from the drop-down list.
Yes to removing step #13 and yes to steps #14 and #15 doing the same thing as entering the lines sddm_enabled="YES" dbus_enabled="YES"
to the file /etc/rc.conf?
You're saying those two lines mermentioned in /etc/fstab aren't necessary? What about mersaying "like enabling/disabling d-bus, you may lose some functionality by not having them"? Or Vullsaying he'd "require it" because he's using LibreOffice? I am planning on using LibreOffice as well.
DBUS needs to run in order for KDE to run. Disabling DBUS - not impossible, but not recommended - I'd suggest first getting KDE to run, period, and get comfortable doing that, before you mess with DBUS.
What mer mentions is overkill for a simple use case like yours. Won't hurt anything to add those 2 lines, but pointless for your use case. Get KDE running first, and then worry about OpenOffice / LibreOffice.
astyle, since you say it won't "hurt anything to add those 2 lines" -- and I am planning on using LibreOffice -- I think I may keep those lines in there. I think LibreOffice is used by many people who want to install KDE.
grahamperrin, I understand the sentiment, but isn't LibreOffice something many people plan to install right away? As astyle says above, it can't hurt to add those 2 lines. Perhaps adding a note as to why I'm including those instructions (such as, "To use LibreOffice...") would be helpful.
To everyone: How do the rest of my instructions look? Look at my other questions if you can. If there is a minor or major error anywhere, please let me know!
According to astylein post #23, there is “no need to run # kldload /boot/modules/i915kms.ko if you have the kldlist line in /etc/rc.conf as per the wiki.” Is this true? Should step #13 be removed?
Do steps #14 and #15 do the same things as adding the lines sddm_enabled="YES" dbus_enabled="YES"
to the file /etc/rc.conf? If so, is one method better than the other?
What exactly is the final step talking about regarding "Wayland" (taken from KDE’s Wiki)?
What’s the sddm setup GVitaliy was talking about (in post #34, for example)? Is it something I should do as well?
Assuming KDE successfully installed, how do I start it? Do I enter the command % startx?
I will be erasing Ubuntu on my laptop relatively soon and installing FreeBSD again. Shortly thereafter, I will install KDE. This might not be for a week or longer, as I want to reread The FreeBSD Handbook and the beginning chapters of Absolute FreeBSD, 3rd Edition. Thank you to everyone who has responded so far! I will post an update when I have KDE installed.
1. as per pkg-install(8) manpage: "-y, --yes Assume yes when asked for confinrmation before package installation." so, pkg does not ask for confirmation and presumes you agree with anything.
2. no idea
3. does not need to start nor end with a new line
4. and 5. alredy solved by astyle
6. can you please provide a link?
7. he probably meant just installing and enabling sddm in rc.conf
8. if successfully installed, you should be able to run it via startx xor (you chose to use sddm) it will be launched by sddm.
1. as per pkg-install(8) manpage: "-y, --yes Assume yes when asked for confinrmation before package installation." so, pkg does not ask for confirmation and presumes you agree with anything.
2. no idea
3. does not need to start nor end with a new line
4. and 5. alredy solved by astyle
6. can you please provide a link?
7. he probably meant just installing and enabling sddm in rc.conf
8. if successfully installed, you should be able to run it via startx xor (you chose to use sddm) it will be launched by sddm.
1. That's what I thought. Thanks. I couldn't find the information on the manpage.
2. It would be nice if someone could look into this before I add both lines.
3. Thanks, but I'm guessing it couldn't hurt?
4. I was looking for confirmation on question #4. Do you think step #13 should be removed?
5. Thanks. It's my understanding the two methods are equal.
6. https://community.kde.org/FreeBSD/Setup#Quick_start (step #4 under "KDE and the rest")
7. Is this sddm setup unnecessary for me?
8. Since I am using sddm, how exactly does that work? Do I still have to login to FreeBSD, or does sddm show up instead of the FreeBSD screen? What credentials do I provide to sddm? My regular username and password?
The instructions alone have the potential to confuse people because there are contractions. Better to re-title the instructions, to not suggest that they're for KDE; and to have a separate section for things that are not KDE.
3. Thanks, but I'm guessing it couldn't hurt?
4. I was looking for confirmation on question #4. Do you think step #13 should be removed?
6. https://community.kde.org/FreeBSD/Setup#Quick_start (step #4 under "KDE and the rest")
7. Is this sddm setup unnecessary for me?
8. Since I am using sddm, how exactly does that work? Do I still have to login to FreeBSD, or does sddm show up instead of the FreeBSD screen? What credentials do I provide to sddm? My regular username and password?
3. no, it won't hurt, it does not matter
4. well, you are adding the kld_list line to rc.conf, right? That means that the kernel module will be loaded at boot. The kernel module is not loaded right after you added the line to rc.conf, because the rc script (which reads the contents of /etc/rc.conf) runs at boot time. So you load the kernel module manually with kldload, so you can continue without rebooting. Or you reboot and then you don't need to do that manually, but why would you reboot for such a trivial thing? This is not Windows XP.
6. He means to check in the sddm "greeting menu" if you have wayland selected or not. Wayland does not work yet, so you check in sddm if you have X11 selected, you dont want Wayland. You would immediately notice that even after entering good login and pass, sddm would not log you in with Wayland selected.
7. I don't know, do you want to use sddm or not?
8. If you are using sddm and you added sddm_enable to rc.conf, then it should start automatically after system reboot(*) and it should greet you with login: and password: prompts. You enter your credentials as usual. KDE should start. This is not different than any linux distribution you've ever used. You are using exactly the same programs (kde, sddm) as you would on linux, so the behavior is the same.
again, you don't need to reboot after doing sddm_enable=YES in rc.conf. You can run it manually by invoking service sddm start. On next reboot though, it will be run by rc automatically.
3. no, it won't hurt, it does not matter
4. well, you are adding the kld_list line to rc.conf, right? That means that the kernel module will be loaded at boot. The kernel module is not loaded right after you added the line to rc.conf, because the rc script (which reads the contents of /etc/rc.conf) runs at boot time. So you load the kernel module manually with kldload, so you can continue without rebooting. Or you reboot and then you don't need to do that manually, but why would you reboot for such a trivial thing? This is not Windows XP.
6. He means to check in the sddm "greeting menu" if you have wayland selected or not. Wayland does not work yet, so you check in sddm if you have X11 selected, you dont want Wayland. You would immediately notice that even after entering good login and pass, sddm would not log you in with Wayland selected.
7. I don't know, do you want to use sddm or not?
8. If you are using sddm and you added sddm_enable to rc.conf, then it should start automatically after system reboot(*) and it should greet you with login: and password: prompts. You enter your credentials as usual. KDE should start. This is not different than any linux distribution you've ever used. You are using exactly the same programs (kde, sddm) as you would on linux, so the behavior is the same.
again, you don't need to reboot after doing sddm_enable=YES in rc.conf. You can run it manually by invoking service sddm start. On next reboot though, it will be run by rc automatically.
7. I want to use sddm, but is all the setup stuff GVitaliy was talking about earlier in this thread (see page 2, for example) really necessary? It seemed kind of advanced to me, and I wasn't really sure what they were doing.
7. I want to use sddm, but is all the setup stuff GVitaliy was talking about earlier in this thread (see page 2, for example) really necessary? It seemed kind of advanced to me, and I wasn't really sure what they were doing.
If you actually read what GVitaliy wrote - he's got some of the same questions as you. He found some different info than you, and was trying to make sense of it. I'd like to reiterate that the Handbook is the place to get started. Any outside info that you find - it has to line up with that Handbook online.
I guess a good way to visualize that is having both instruction sets side-by-side. Then you'll see where different lines of code go, and how to mix them properly. Kind of like a jacket zipper. Left side is Handbook, right side is outside info that I was talking about.
Not sure if answered already but it is key in FreeBSD to get xorg running first without a login manager or desktop environment. Then get the desktop environment working, then introduce a login manager, if desired. Trying to do it all at once introduces too many variables to troubleshoot.
Not sure if answered already but it is key in FreeBSD to get xorg running first without a login manager or desktop environment. Then get the desktop environment working, then introduce a login manager, if desired. Trying to do it all at once introduces too many variables to troubleshoot.
Come on, the Handbook tells you to first install everything needed (xorg, KDE, and SDDM), then enable it by editing a few .conf files, and then reboot. That takes you directly to the login screen. No need to specifically get Xorg running first. I did that a few times, only to discover that it only confuses things down the road.
Come on, the Handbook tells you to first install everything needed (xorg, KDE, and SDDM), then enable it by editing a few .conf files, and then reboot.
I would especially recommend doing so with the added complexity of the KMS drivers needing to be added from ports rather than part of the base OS. Small incremental changes are much easier to debug than a frozen screen and having no idea what caused it. Particularly because SSH/serial debugging is a little scary for some newcomers.
The biggest risk has always been that if you have severe issues with your GPU hardware, the display manager could freeze your machine. You reboot and the same thing happens in a loop (you would need to then boot into single user mode). It is safer to ensure that X11 is fully working first to avoid that mess.
I would especially recommend doing so with the added complexity of the KMS drivers needing to be added from ports rather than part of the base OS. Small incremental changes are much easier to debug than a frozen screen and having no idea what caused it. Particularly because SSH/serial debugging is a little scary for some newcomers.
The biggest risk has always been that if you have severe issues with your GPU hardware, the display manager could freeze your machine. You reboot and the same thing happens in a loop (you would need to then boot into single user mode). It is safer to ensure that X11 is fully working first to avoid that mess.
One unfortunate issue that has been pointed out (too lazy to dig out links) is that FreeBSD's KDE packages do not specify Xorg as a dependency. However, # pkg install x11/sddm will properly pull Xorg in as a dependency. The Handbook will tell you that most of the time, Xorg does not require any config - but you do have to have the proper driver for the GPU as per the wiki linked to earlier in this thread.
If you actually read what GVitaliy wrote - he's got some of the same questions as you. He found some different info than you, and was trying to make sense of it. I'd like to reiterate that the Handbook is the place to get started. Any outside info that you find - it has to line up with that Handbook online.
I guess a good way to visualize that is having both instruction sets side-by-side. Then you'll see where different lines of code go, and how to mix them properly. Kind of like a jacket zipper. Left side is Handbook, right side is outside info that I was talking about.
I'm now thinking it might be easier to just do without sddm. Is the only real advantage sddm gives the ability to have a graphical login? If so, I'm not sure I need this. I am OK with starting KDE from the command line. If I go with this method, do I just add the following line to ~/.xinitrc: exec ck-launch-session startplasma-x11
To edit that file, would I just run # ee ~/.xinitrc, enter the line on a new line, and leave the editor on another new line? What, specifically, would I want to remove from my instructions (see above link) to get rid of the sddm stuff?
It seems there is now a debate as to whether Xorg should be installed first. If this is the case, how should I amend my instructions (see above link)?
I suppose arguably Xorg is not a dependency of KDE (or any software really). For example you may be using Xvnc or entirely X11/SSH forwarding from a server with no physical GPU. No need to clutter it up with a useless install of Xorg.
I'm now thinking it might be easier to just do without sddm. Is the only real advantage sddm gives the ability to have a graphical login? If so, I'm not sure I need this. I am OK with starting KDE from the command line. If I go with this method, do I just add the following line to ~/.xinitrc: exec ck-launch-session startplasma-x11
To edit that file, would I just run # ee ~/.xinitrc, enter the line on a new line, and leave the editor on another new line? What, specifically, would I want to remove from my instructions (see above link) to get rid of the sddm stuff?
It seems there is now a debate as to whether Xorg should be installed first. If this is the case, how should I amend my instructions (see above link)?
KDE cannot run without Xorg. So even if Xorg is not explicitly specified as a dependency, Xorg still needs to be installed first. What seems to be debatable is whether to first make sure it's actually running, or to edit a few .conf files as instructed by the Handbook.
I just install editors/nano as the very first package, that saves me from having to learn ee or re-learn vi.
Looks like VNC is the drop-in replacement for Xorg in your case. I'd rather not make things very complicated for people who are just trying to get KDE going on localhost, period. Let's teach them to follow the Handbook, and experience some success that way first, before moving on to playing with things like that.
Edit: Even without Xorg installed on localhost, KDE cannot run without X11 forwarding on SSH, either.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.