Fresh Installation Of FreeBSD 11.2--Mate Not Working Properly

Xfce seems to be one of the less troublesome desktop environments on FreeBSD; I just don't like it much for aesthetic reasons and have at this point pretty well settled on using either Plasma 5/KDE or LXDE. I've read in several places that we shouldn't log into X using the root account so I never do it.

Regarding the issue of shutting down or rebooting from the desktop, I still have one and only one old test installation of KDE which allows me to do it. I can't remember exactly how I made it work on that install, but I think it had something to do with either autofs, /usr/local/etc/PolicyKit/PolicyKit.conf, or maybe both. However I sometimes get errors shutting down that way, so I've made it a habit to always log out first, and then shut down using either the login/display manager or a text console. Also I've noticed that whenever I start the DE using startx instead of a login manager, I have the shutdown and reboot buttons on the desktop, but when I start the exact same DE using the login manager (usually sddm), then I don't see those buttons on the desktop. Not really sure exactly why.

I just did a clean install of 11.2 and KDE5 using SDDM and have the logout, reboot and shut down buttons. I am using dsbmc and dsbmd for mounting 'exotic' stuff. I created devfs.rules based on the information from 'cooltrainers' website. It was a full install of KDE5 so I think it pulled the right dependencies. The only trouble I have now is Kodi not playing nice with KDE5/Dolphin. Xfce also runs great (although only logout button available, need to adjust /usr/local/etc/PolicyKit/PolicyKit.conf). Plasma feels as snappy as Xfce, although memory consumption is higher.
 
Xfce seems to be one of the less troublesome desktop environments on FreeBSD; I just don't like it much for aesthetic reasons and have at this point pretty well settled on using either Plasma 5/KDE or LXDE. I've read in several places that we shouldn't log into X using the root account so I never do it.

Regarding the issue of shutting down or rebooting from the desktop, I still have one and only one old test installation of KDE which allows me to do it. I can't remember exactly how I made it work on that install, but I think it had something to do with either autofs, /usr/local/etc/PolicyKit/PolicyKit.conf, or maybe both. However I sometimes get errors shutting down that way, so I've made it a habit to always log out first, and then shut down using either the login/display manager or a text console. Also I've noticed that whenever I start the DE using startx instead of a login manager, I have the shutdown and reboot buttons on the desktop, but when I start the exact same DE using the login manager (usually sddm), then I don't see those buttons on the desktop. Not really sure exactly why.
Thanks for your comments. I'll likely do some more tinkering with it to see what happens.

Mind you, this is the first laptop that I've been able to install Mate on. I tried it with some others that I have and either the installer or the system itself didn't like that. Maybe it has to do with the fact that the laptop I bought a few days ago came with more RAM.

I'm not crazy about Xfce, either, but it's the closest to Mate, for my purposes, of the other desktops I've tried. I never got the hang of KDE. I found it too convoluted for my liking and even more so now with the current version.

One thing I've noticed is that it appears that what I get from an installation seems to vary from one machine to another. It's just little things like, for example, the alert window that opens when one is unmounting a USB drive after having stored something on it. On one laptop, it was of a different size and colour than it was on a different computer. Go figure.
 
Thanks for your comments. I'll likely do some more tinkering with it to see what happens.

Mind you, this is the first laptop that I've been able to install Mate on. I tried it with some others that I have and either the installer or the system itself didn't like that. Maybe it has to do with the fact that the laptop I bought a few days ago came with more RAM.

I'm not crazy about Xfce, either, but it's the closest to Mate, for my purposes, of the other desktops I've tried. I never got the hang of KDE. I found it too convoluted for my liking and even more so now with the current version.

One thing I've noticed is that it appears that what I get from an installation seems to vary from one machine to another. It's just little things like, for example, the alert window that opens when one is unmounting a USB drive after having stored something on it. On one laptop, it was of a different size and colour than it was on a different computer. Go figure.
I tweaked my laptop earlier this evening to allow it to run Mate after logging in through Slim.

The System menu allowed me to shut down the machine, but moving windows was a touch slower than when I was running Mate after typing startx with exec mate-session in .xinitrc.

Now this is on a laptop with only 3 GB RAM and a 60 GB hard drive. I'll have to see what happens when I try the same thing on the original system after upgrading it to FreeBSD 12.0. That system is on one of my tower machines, which has more RAM and a larger HD than the laptop.
 
I also have 3 GB ram but my machine is 32-bit. I'm guessing your laptop might be 64-bit. My Acer Aspire laptop with amd64 and 6 GB RAM ran Mate okay, and I didn't notice the window dragging lag, but I probably wouldn't notice it unless it was pretty severe... a little bit of lag is pretty common in my experience and doesn't really bother me much. Least amount of lag I get is probably with LXDE. Could easily be wrong but I tend t oassociate the window lag problem with this one particular FreeBSD 32-bit Mate port, and not with the amd64 port.
Thanks for keeping us in the loop regarding your progress.
 
I also have 3 GB ram but my machine is 32-bit. I'm guessing your laptop might be 64-bit. My Acer Aspire laptop with amd64 and 6 GB RAM ran Mate okay, and I didn't notice the window dragging lag, but I probably wouldn't notice it unless it was pretty severe... a little bit of lag is pretty common in my experience and doesn't really bother me much. Least amount of lag I get is probably with LXDE. Could easily be wrong but I tend t oassociate the window lag problem with this one particular FreeBSD 32-bit Mate port, and not with the amd64 port.
Thanks for keeping us in the loop regarding your progress.
I'm running FreeBSD 12 with Mate on the wobbly system on my tower machine right now.

There is quite a lag in dragging windows in this installation, though I'm not sure if it's because I'm running a 64-bit OS on a 32-bit machine. As well, there seems to be something running in the background that makes the desktop behave erratically.

Maybe what I should do is delete the entire installation and start over again from scratch.
 
<snip>

Maybe what I should do is delete the entire installation and start over again from scratch.
Never knowing when to leave well enough alone, I did just that.

I started by installing FreeBSD 11.2 AMD64 on my 32-bit machine. I figured it's worked before, so it should this time. I then upgraded to 12.0.

I then installed Mate and it behaves exactly the way it did when this whole situation started several weeks ago. I might try tweaking Mate a bit further, but I don't think I want to spend much more time on it right now. :mad:

As much as I don't particularly like it, Xfce might be my best option. :(
 
I'd probably be using xfce if I wasn't so stubborn; I've seen several posts here where people seem to be using it without many problems. I'm still on plasma5-plasma with baloo file search options and a few other features turned off, and shall probably stick with it, even though, now, I can't seem to get the power management options to work quite the way I want. When (and if) the port maintainers update the mate ports and or packages again, I'll probably give mate another try just to see how it goes, but shall probably be sticking with plasma5 for my working FreeBSD installs for the foreseeable future, if for no better reason than because it seems a little less "linux-centric" than either Mate or LXDE/LXQT-- neither of which seem to be getting much attention or putting much focus on FreeBSD. Even KDE/Plasma seems to be slowly slipping into the GNU/Linux camp, but I've always associated KDE with FreeBSD ever since the old XFree86 days-- when, if I recall correctly, it was sort of like the main supported desktop environment for FreeBSD. Plus I've just always liked the colors, look, and feel of it, especially when using the Oxygen/Elarun theme and widget styles.
 
I'd probably be using xfce if I wasn't so stubborn; I've seen several posts here where people seem to be using it without many problems. I'm still on plasma5-plasma with baloo file search options and a few other features turned off, and shall probably stick with it, even though, now, I can't seem to get the power management options to work quite the way I want. When (and if) the port maintainers update the mate ports and or packages again, I'll probably give mate another try just to see how it goes, but shall probably be sticking with plasma5 for my working FreeBSD installs for the foreseeable future, if for no better reason than because it seems a little less "linux-centric" than either Mate or LXDE/LXQT-- neither of which seem to be getting much attention or putting much focus on FreeBSD. Even KDE/Plasma seems to be slowly slipping into the GNU/Linux camp, but I've always associated KDE with FreeBSD ever since the old XFree86 days-- when, if I recall correctly, it was sort of like the main supported desktop environment for FreeBSD. Plus I've just always liked the colors, look, and feel of it, especially when using the Oxygen/Elarun theme and widget styles.
I used Scientific Linux for a number of years. It was, as I recall, based on Red Hat and had a Gnome desktop. Another reason was that FreeBSD wasn't terribly stable on the machines I installed it on, frequently freezing and requiring rebooting.

I eventually switched to FreeBSD when I found that the previous problems I had with it rarely occurred. In addition, the SL repository was rather limited and adding new packages proved to be rather convoluted.

I guess I became enamoured with Gnome because it was a lot like Solaris on the old Sun workstations I used while I was still a grad student some 20 years ago.
 
In the late 90s my employers chose Red Hat (version 6.2 I think) over FreeBSD, after I introduced them to both systems-- they knew nothing whatsoever about FOSS at that time-- but later we all regretted it when they split Red Hat into Fedora and Enterprise Edition, which got all the routing and ipchains/iptables features we wanted (for some kind of fee, I forget how much). We continued using 6.2 for routers and gateways only long after the support for it started running dry. These were all headless machines with no desktop environments, and RH also had a buggy but usable IMSBASIC implementation which we used to support legacy BASIC software for a few live customers. Personally I experimented with X-windows features at home, using the FreeBSD documentation, which was much better and more comprehensive than anything I could find easily for Red Hat. I personally went dry on all GNU/Linux after that, until a few years ago when I started using Linux Mint to replace Windows on a few of my friends' boxes which were unable to keep up with the ever-growing hardware requirements for Windows, but whose hardware was not supported by FreeBSD. I've hated Windows for decades and haven't used it personally since Sun successfully sued M$ for-- what was it-- around $14 million back around the turn of the century, when M$ more or less killed Java applets on the desktop through blatantly illegal contract violations and anti-competitive business practices. They were laughing all the way to the bank I'm sure when they paid off the $14 million which was chump change for them. Playing around with Linux Mint sent me running back to FreeBSD again right away-- I had been using MacOS X for several years, and played around with Debian in 2011 for a server implementation-- anything but Windows for me ha, bad enough that I still had to support Windows for several years, for customers running PowerTerm, putty, and the one and only M$ app we had written in Borland C++ for Windows.
 
In the late 90s my employers chose Red Hat (version 6.2 I think) over FreeBSD, after I introduced them to both systems-- they knew nothing whatsoever about FOSS at that time-- but later we all regretted it when they split Red Hat into Fedora and Enterprise Edition, which got all the routing and ipchains/iptables features we wanted (for some kind of fee, I forget how much). We continued using 6.2 for routers and gateways only long after the support for it started running dry. These were all headless machines with no desktop environments, and RH also had a buggy but usable IMSBASIC implementation which we used to support legacy BASIC software for a few live customers. Personally I experimented with X-windows features at home, using the FreeBSD documentation, which was much better and more comprehensive than anything I could find easily for Red Hat. I personally went dry on all GNU/Linux after that, until a few years ago when I started using Linux Mint to replace Windows on a few of my friends' boxes which were unable to keep up with the ever-growing hardware requirements for Windows, but whose hardware was not supported by FreeBSD. I've hated Windows for decades and haven't used it personally since Sun successfully sued M$ for-- what was it-- around $14 million back around the turn of the century, when M$ more or less killed Java applets on the desktop through blatantly illegal contract violations and anti-competitive business practices. They were laughing all the way to the bank I'm sure when they paid off the $14 million which was chump change for them. Playing around with Linux Mint sent me running back to FreeBSD again right away-- I had been using MacOS X for several years, and played around with Debian in 2011 for a server implementation-- anything but Windows for me ha, bad enough that I still had to support Windows for several years, for customers running PowerTerm, putty, and the one and only M$ app we had written in Borland C++ for Windows.
I became interested in FreeBSD through OS X when I bought what was back then Apple's top-of-the-line G4 machine. I had been an avid Apple user for several years by then, but when I started having problems with the hardware and Apple gave me the runaround, I started looking at Linux and FreeBSD.

I also moved to either refurbished or homebrew computers. With that hardware, there was a chance I could get spare parts as there weren't any readily available for my Apple. I spent quite a lot of money on that last setup and I hated the idea of having to put it up on blocks simply because the manufacturer didn't want to repair it or sell me replacement components, and I certainly wasn't going to buy brand new machinery. ("We only support it for xxx number of years. That time has passed. G'bye.") By going to second-hand or custom-built units, I could either fix them myself or, since they were often a lot cheaper than buying new stuff off the shelf, I could scrap them or strip them for spare parts.

I certainly wasn't going over to Windows. I've hated that OS from the very beginning and even more so when the institution I used to teach at dumped a perfectly good Unix system some 20 years ago and adopted M$.
 
I try to run all computers to the drop dead point whenever possible and practical to do so. It's alarming how much metal and plastic junk I've already scrapped over the years and I'm just one person. The computers we consider to be junk today are still technological marvels when compared with what we've had decades past or even just a few years ago. Running FreeBSD with a new disk drive, this 12 year old computer I'm typing on right now is even more powerful than it was when it was brand new and probably cost over $K. It's only practical to drive it 'til it drops.
 
Never content to let slumbering canines doze in peace, I did some more tinkering.

I reconfigured the machine that's been so troublesome. The hard drive with the wobbly Mate was replaced by a larger one and I installed FreeBSD 12/Mate on that, starting with the AMD64 version. Mate still didn't work like I expected it to.

I deleted the installation and replaced it with the i386 version with the same result, leading me to believe that the FreeBSD/Mate combination might not be compatible with the processor.

By comparison, I have a quad-core machine and, before I tried my latest tricks with the original computer, I took that second drive, and connected it. I then installed FreeBSD/Mate on it, and Mate runs. The only thing I noticed that's not quite the same as what's on my other machines is that, when dragging windows, it's slower with the mouse pointer leading by a split second.

Now that I've answered some questions I've had, I think I'll leave things be because I can't think of what else I can do. On that larger drive, I'm running Xfce and there doesn't seem to be any problems with the installation.
 
I came to a similar point and am now using plasma5-plasma on my i386 Dell. No longer testing other DEs on FreeBSD, at least not for the time being, but still using Mate on Debian, where it works well. I'll probably give Mate on FreeBSD another try whenever the next Mate port is made -- mainly just out of curiosity though, since I'm really pretty content at this point to keep running a customized version of plasma5-plasma 5.14.4 with no HAL daemon and BSDISKS enabled.
 
As I believe I mentioned before, I have two tower machines, one of which has the wobbly installation on one of its hard drives. The remainder of the drives on those computers have the original Mate installation and I upgraded those to FreeBSD 12.0 over the past few days.

Now that the upgrading is finished, the original Mate setup runs off the respective drives.

When I trashed the one installation, I was trying to update to an RC of 12. I think I might have neglected to upgrade all the packages and ports, which the upgrading process for 12.0-RELEASE suggests should be done.
 
Hello to all...

I need your kind help. I am trying to get to the desktop (MATE) without any success. The installation in on bare metal. The steps I follow are:

  1. Clean FreeBSD installation
  2. Login as root
(a) # pkg update
(b) # pkg upgrade
(c) # pkg install xorg mate slim slim-themes
(d) # sysrc dbus_enable=YES
# sysrc hald_enable=YES
# sysrc slim_enable=YES
(e) # vi .xinitrc and I put "exec mate-session" inside
(f) # cp .xinitrc /home/USERNAME/.xinitrc

3) I reboot

and I get the screen of step 2) !!! (again).

Any ideas/suggestions/help would be more than welcome.


Thank you all in advance.
 
and I get the screen of step 2) !!! (again).

Any ideas/suggestions/help would be more than welcome.
Check /var/log/Xorg.0.log for any warnings (WW) or errors (EE) that might occur during starting the X server. What graphics hardware do you use and are the drivers correctly installed?
 
Check /var/log/Xorg.0.log for any warnings (WW) or errors (EE) that might occur during starting the X server. What graphics hardware do you use and are the drivers correctly installed?

I have an integrated Intel card. Should I install anything relevant?
 
I think you are going to need graphics/drm-kmod.
Hello again..

I made the following:
(a1) # echo kern.vty=vt >> /etc/loader.conf
(a2) # pkg install drm-kmod
(a3) # I added the line

kld_list="/boot/modules/i915kms.ko"

in /etc/rc.conf

The result is pretty much the same... see attached picture (/var/log/Xorg...)


PS. DO I NEED something like xf86-video-intel AS WELL?
 

Attachments

  • pic1.png
    pic1.png
    550.4 KB · Views: 239
I solved the problem... xf86-video-intel was needed as well.

Yet there is something strange. Although I change the .xinitrc content to
"exec ck-launch-session mate-session"
I do not have the shutdown/reboot/etc options.
 
(a1) # echo kern.vty=vt >> /etc/loader.conf
That needs to go into /boot/loader.conf.

kld_list="/boot/modules/i915kms.ko"
Try without leading path and without the .ko, i.e.
Code:
kld_list="i915kms"
Then reboot the machine. After reboot check dmesg for any messages from the driver if it loaded up correctly.
The result is pretty much the same... see attached picture (/var/log/Xorg...)
PS. DO I NEED something like xf86-video-intel AS WELL?
I don't think you need that one. It seems to be for older chipsets and only offers 2D acceleration, according to the pkg-descr file.
 
That needs to go into /boot/loader.conf.


Try without leading path and without the .ko, i.e.
Code:
kld_list="i915kms"
Then reboot the machine. After reboot check dmesg for any messages from the driver if it loaded up correctly.

I don't think you need that one. It seems to be for older chipsets and only offers 2D acceleration, according to the pkg-descr file.
Thank you very much. May I ask you something else? How to load some drivers upon booting from a USB stick with the image of a new current edition?
 
How to load some drivers upon booting from a USB stick with the image of a new current edition?
That question is pretty vague. I believe 13-current if that's what you mean is not supported here. Probably the same way as in 12.0 I guess, via kld_list in /etc/rc.conf. That's the preferred way for loading up kernel modules, unless the module is needed early in the boot stage i.e. for mounting filesystems, then it still needs to be loaded from /boot/loader.conf.
 
That question is pretty vague. I believe 13-current if that's what you mean is not supported here. Probably the same way as in 12.0 I guess, via kld_list in /etc/rc.conf. That's the preferred way for loading up kernel modules, unless the module is needed early in the boot stage i.e. for mounting filesystems, then it still needs to be loaded from /boot/loader.conf.
I would like to perform an installation in a nvme ssd and upon booting of the USB stick I get the message "nvme interrupt" so I guess I need to load the nvme driver early. Yet I do not know how to do it.
 
I would like to perform an installation in a nvme ssd and upon booting of the USB stick I get the message "nvme interrupt" so I guess I need to load the nvme driver early. Yet I do not know how to do it.
The required drivers should already be included in the GENERIC kernel:
Code:
$ grep "nvme" /sys/amd64/conf/GENERIC
device          nvme                    # base NVMe driver
device          nvd                     # expose NVMe namespaces as disks, depends on nvme
So i guess the problem lies somewhere else.
 
Back
Top