Peter Humphrey wrote: > Hello list, > > After the switch to elogind yesterday, chronyd now won't run. It complains > "Could not get user/group of ntp." I remerged chrony with USE=-ntp, but it > didn't help. I know that several people here use chrony, so what is your > experience? > > Secondly, this morning when I started firefox to listen to BBC Radio 3, as > usual, I had no sound. Then I remembered that alsa-utils was unmerged during > the switch to elogind yesterday, so I remerged it and ran alsamixer to unmute > the master. Still no sound. > > This box has two sound devices: > > # lspci | grep Audio > 00:1b.0 Audio device: Intel Corporation C610/X99 series chipset HD Audio > Controller (rev 05) > 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI > Audio [Radeon RX 470/480 / 570/580/590] > > The first of those is the one I use; the AMD device is part of the VGA card > and > not used. I'd have to get myself some kind of HDMI cable to split the sound > out if I wanted to use it. > > Should I assume that firefox is trying to use the AMD device? In that case, > how > do I redirect it? There's no sound configuration panel under multimedia in > KDE > system settings; only cddb. >
I use chrony here and haven't ran into that problem, yet. Give me some time tho. ;-) As to the sound problem, I'd try logging out of the GUI, restarting elogind or rebooting, and then trying again. One thing I've noticed about elogind, if it or something it depends on triggers the need for a restart, it causes some weird problems. Once restarted, everything works as it should. Which brings me to this. Anyone know if moving elogind from the boot runlevel to default would cause problems? I'm thinking about doing that since I forget to restart elogind manually after a KDE upgrade, or other upgrades that require restarting a lot of services. Hope that helps. It seems elogind has a few quirks still, or maybe it is a feature we just don't want. ROFL Dale :-) :-)
