> On 7 Dec 2021, at 09:30, Javier Perez wrote:
>
>
>
>> On Sat, Dec 4, 2021 at 10:13 AM Tom Horsley wrote:
>> On Sat, 4 Dec 2021 15:16:05 +0800
>> Ed Greshko wrote:
>>
>> > So, you have a common keyboard, and monitor? I've not used a KVM switch
>> > in a long time but they sometimes woul
On Tue, 7 Dec 2021 04:29:40 -0500
Javier Perez wrote:
> How do I do that? Do you have a link I could go to and learn how to do it?
> I have a KVM and whenever I switch from Fedora to the other PCs, I start
> getting a bunch of lines on the journal complaining that the system could
> not get the ED
On Sat, Dec 4, 2021 at 10:13 AM Tom Horsley wrote:
> On Sat, 4 Dec 2021 15:16:05 +0800
> Ed Greshko wrote:
>
> > So, you have a common keyboard, and monitor? I've not used a KVM switch
> in a long time but they sometimes would cause
> > problems.
>
> A lot of KVM switches don't pass through EDID
On Mon, 6 Dec 2021 12:19:17 -0800
Paolo Galtieri wrote:
> I have disabled chronyd. The main problem is the graphical.target vs
> multi-user.target. ntpd only starts in multi-user.target.
graphical target includes everything from multi user target (but not vice
veras).
I have disabled chronyd. The main problem is the graphical.target vs
multi-user.target. ntpd only starts in multi-user.target.
Paolo
On 12/5/21 13:59, Ed Greshko wrote:
On 06/12/2021 01:48, Paolo Galtieri wrote:
systemctl status ntpd
○ ntpd.service - Network Time Service
Loaded: loaded
On 12/6/21 9:13 AM, Paolo Galtieri wrote:
It turned out chronyd was also enabled, but marked as dead.
Have you tried
1)
get the time servers out of the way
systemctl disable chronyd
systemctl disable ntpd
2)
timedatectl # see what's happening
timedatec
It turned out chronyd was also enabled, but marked as dead.
○ chronyd.service - NTP client/server
Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled;
vendor preset: enabled)
Active: inactive (dead) since Sun 2021-12-05 09:47:14 PST; 23h ago
Docs: man:chronyd(8)
Here's the output:
systemctl cat ntpd.service
# /usr/lib/systemd/system/ntpd.service
[Unit]
Description=Network Time Service
Documentation=man:ntpd(8)
Wants=network.target
ConditionCapability=CAP_SYS_TIME
After=network.target nss-lookup.target
Conflicts=systemd-timesyncd.service
[Service]
Type=f
Here's the output:
[pgaltieri@truckin ~]$ systemctl get-default
graphical.target
[pgaltieri@truckin ~]$ find /etc/systemd/system -name chronyd.service -ls
4195823 0 lrwxrwxrwx 1 root root 39 Apr 25 2019
/etc/systemd/system/multi-user.target.wants/chronyd.service ->
/usr/l
On 06/12/2021 01:48, Paolo Galtieri wrote:
systemctl status ntpd
○ ntpd.service - Network Time Service
Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled; vendor
preset: disabled)
Active: inactive (dead)
Docs: man:ntpd(8)
As Tom has already indicated, this is what y
On Sun, 05 Dec 2021 20:18:13 +0100
francis.montag...@inria.fr wrote:
> Sorry: I was comparing with chronyd
Actually that's a good thing to look at. Have you disabled chrony?
If not, they will fight over the NTP port.
___
users mailing list -- users@list
On Sun, 05 Dec 2021 19:55:15 +0100 francis.montag...@inria.fr wrote:
> I suspect that ntpd is not enabled in the proper "target".
> What gives:
> systemctl get-default
> find /etc/systemd/system -name chronyd.service -ls
Sorry: I was comparing with chronyd
I meant thus:
systemctl get-d
Hi
On Sun, 05 Dec 2021 09:48:50 -0800 Paolo Galtieri wrote:
> Here's the info:
> systemctl status ntpd
> ○ ntpd.service - Network Time Service
> Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled;
> vendor preset: disabled)
> Active: inactive (dead)
> Docs: man:n
Here's the info:
systemctl status ntpd
○ ntpd.service - Network Time Service
Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled;
vendor preset: disabled)
Active: inactive (dead)
Docs: man:ntpd(8)
At this point here's the current network config:
ifconfig
eno1: flags
On 05/12/2021 00:27, Paolo Galtieri wrote:
This isn't true. I stopped ntpd, stopped the wifi connection and restarted
ntpd and ntpd started fine with no wifi connection. It should only need a
network connection to synchronize the time.
That is why I asked you to provide the output of
syste
On Sat, 4 Dec 2021 08:20:12 -0800
Paolo Galtieri wrote:
> The "Input not supported" error occurs on the active connection. But
> what has changed recently to introduce this problem since booting on
> older kernels does not exhibit it?
I've noticed that the newer nouveau drivers somehow misinter
This isn't true. I stopped ntpd, stopped the wifi connection and
restarted ntpd and ntpd started fine with no wifi connection. It should
only need a network connection to synchronize the time.
Paolo
On 12/3/21 10:15, Joe Zeff wrote:
On 12/3/21 11:05 AM, Paolo Galtieri wrote:
Next issue. Thi
The "Input not supported" error occurs on the active connection. But
what has changed recently to introduce this problem since booting on
older kernels does not exhibit it?
Paolo
On 12/4/21 05:54, Tom Horsley wrote:
On Sat, 4 Dec 2021 15:16:05 +0800
Ed Greshko wrote:
So, you have a common k
On Sat, 4 Dec 2021 15:16:05 +0800
Ed Greshko wrote:
> So, you have a common keyboard, and monitor? I've not used a KVM switch in a
> long time but they sometimes would cause
> problems.
A lot of KVM switches don't pass through EDID info correcly (especially
for connections not currently active)
On 04/12/2021 02:05, Paolo Galtieri wrote:
Folks,
I have 2 systems running F34. These 2 systems connect to a common monitor
via a keyboard-video-mouse switch.
First issue. One of these systems, when I boot any of the 3 most recent kernels, when it
gets to multi user mode displays "Input not
On 12/3/21 11:05 AM, Paolo Galtieri wrote:
Next issue. This same system is configured to start ntpd at boot, but it
doesn't start. I need to start it manually after the system is booted.
Of course it doesn't. That service requires a network connection and
can't start until you've unplugged y
Folks,
I have 2 systems running F34. These 2 systems connect to a common
monitor via a keyboard-video-mouse switch.
First issue. One of these systems, when I boot any of the 3 most recent
kernels, when it gets to multi user mode displays "Input not supported"
but works fine when I boot ker
22 matches
Mail list logo
