On Sun, Jun 26, 2016 at 9:37 PM, Bernard Mentink <[email protected]> wrote: > Now the only other issue I have running KDE is that when I enable sound on > my platform by loading the snd_hda module, I get pulseaudio taking up 100% > of one of my cpu cores ... > Sound works ok though .... any idea what goes on there? do I have to adjust > some pulseaudio parameters?
Yes I've noticed that too, but sorry no idea what's going on or how to fix that; I haven't followed that up. Let us know if you find out. Cheers Peeter -- > > Cheers, > Bernie > > On Mon, Jun 27, 2016 at 2:06 AM, karu.pruun <[email protected]> wrote: >> >> On Sun, Jun 26, 2016 at 12:11 PM, Bernard Mentink <[email protected]> >> wrote: >> > Hi John, >> > >> > Appreciate the explanation. >> > However, the description of the FreeBSD setup for gnome and the DFly one >> > are >> > quite different. >> > >> > The FreeBSD one says to start dbus and hald via rc.conf. Dfly does not >> > say >> > to do that. >> > >> > If I follow FreeBSD instructions KDE won't work at all, because KDE >> > starts >> > dbus itself and bombs out if it is already running. So at least Dfly >> > works >> > with KDE by NOT starting dbus in rc.conf .. >> >> >> There are two standard dbus session instances normally: one is the >> systemwide bus that is started via /etc/rc.conf, the other is a >> session bus which is started by KDE, GNOME, XFCE, MATE when they >> launch. So you should include >> >> dbus_enable="YES" >> >> in rc.conf. If you do not do this, you'll see some complaining in the >> log; but may still be able to run the DE. This is how I run KDE and I >> can confirm that it runs fine on my machine DragonFly >> v4.5.0.1247.g122b6-DEVELOPMENT. MATE and XFCE run fine as well. I >> don't run hald for any of the DEs. Not sure why KDE does not run when >> you start the system dbus instance. >> >> GNOME (gnome3) does not work, or at least to my experience. There's >> some complaining by gnome-settings-daemon about not being able to >> communicate via dbus, and it may well be the reason but I haven't >> followed up. >> >> >> > PS: Man pages don't help a new user get up and running when they are >> > used to >> > the Linux way of doing things .... for example, the Lack of the lspci >> > instruction means I can't see what module I need to load for my audio >> > hardware ... >> >> >> pciconf -l >> pciconf -lv >> >> A lot of this applies to DragonFly as well: >> >> https://www.freebsd.org/doc/en/articles/linux-users/article.html >> >> >> Cheers >> >> Peeter >> >> -- >> >> >> >> >> >> On 6/26/2016 3:38 AM, Bernard Mentink wrote: >> >>> >> >>> Hi John, >> >>> >> >>> So why should I use the FreeBSD instructions? I thought this was >> >>> DragonFlyBSD forum? >> >>> >> >>> I used the instructions from >> >>> here: https://www.dragonflybsd.org/docs/handbook/X/#index2h2 >> >>> >> >>> Are you saying I should not use the DFly instructions to setup DFly? >> >>> >> >>> That is just weird .. >> >> >> >> >> >> Hi Bernard, >> >> Of course it would be ideal if DragonFly documentation was at the same >> >> level as FreeBSD but the fact is that this is not the case. FreeBSD >> >> has an >> >> entire team whose primary responsibility is documentation. >> >> >> >> Now you may be aware that DragonFly DPorts is basically FreeBSD ports >> >> made >> >> to work on DragonFly. As such, instructions to install third-party >> >> software >> >> on FreeBSD are good for DragonFly as well. So it's not weird to >> >> reference >> >> FreeBSD documentation when DPorts are involved as is the case here. >> >> >> >> As a last thought, our handbook is a living wiki. Some people have >> >> improved KDE instructions recently, but if you think it needs more then >> >> you >> >> have the ability to write these improvements so everyone can benefit. >> >> >> >> DragonFly MAN pages are top notch, but the handbook / wiki is not at >> >> the >> >> same quality level (and in some cases are poor quality). >> >> >> >> John >> >> >> >> >> >> --- >> >> This email has been checked for viruses by Avast antivirus software. >> >> https://www.avast.com/antivirus >> >> >> > >> > >> > >> > -- >> > >> > ------------------------------------------------------------------------------------------------------------------------------------- >> > Life is a sexually transmitted disease with a 100% mortality rate. >> > >> > ------------------------------------------------------------------------------------------------------------------------------------- > > > > > -- > ------------------------------------------------------------------------------------------------------------------------------------- > Life is a sexually transmitted disease with a 100% mortality rate. > -------------------------------------------------------------------------------------------------------------------------------------
