Re: several issues with f34
> 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 would cause >> > problems. >> >> A lot of KVM switches don't pass through EDID info correcly (especially >> for connections not currently active), there is a kernel option you >> can add to the kernel boot line to point at a binary blob of EDID >> info that will ovferride whatever incorrect nonsense it is getting from >> the KVM. Usually you just want to save the EDID from the real monitor >> when it is properly connected, then point the kernel at that so it >> will always know the right stuff. > > > Hi Sorry to barge in. > > 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 EDID info: > > "nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device VGA-0" For vga I recall that edid is sent over dedicated pins. It’s worth trying a different cable to see if the cable is the problem. Also try without the kvm in the way. Another thing to check is that the pins in the vga cable and socket have not been damaged. It used to be a problem that pins could get broken off or flattened into socket. Barry > > Thanks > > -- > -- > /\_/\ > |O O| pepeb...@gmail.com > Javier Perez > While the night runs > toward the day... > m m Pepebuho watches > from his high perch. > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: several issues with f34
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 EDID info: Search for EDID in the kernel command line parameters doc: https://www.kernel.org/doc/html/v4.14/admin-guide/kernel-parameters.html That tells you where to put the edid blob and how to point to it on the kernel command line. If you boot when the monitor is correctly connected, there should be a file like this: /sys/class/drm/card0-HDMI-A-1/edid That is the edid it read from the monitor which you can copy and point at on the command line. That card* directory is different depending on where the monitor is connected. There is also a read-edid tool that can dig up the same info. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: several issues with f34
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 info correcly (especially > for connections not currently active), there is a kernel option you > can add to the kernel boot line to point at a binary blob of EDID > info that will ovferride whatever incorrect nonsense it is getting from > the KVM. Usually you just want to save the EDID from the real monitor > when it is properly connected, then point the kernel at that so it > will always know the right stuff. > Hi Sorry to barge in. 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 EDID info: "nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device VGA-0" Thanks -- -- /\_/\ |O O| pepeb...@gmail.com Javier Perez While the night runs toward the day... m m Pepebuho watches from his high perch. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: several issues with f34
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). ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: several issues with f34
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 (/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 you'd get if you have both ntpd and chronyd enabled. So, make sure only one time sync service is enabled. -- Did 황준호 die? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: several issues with f34
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 timedatectl set-ntp true # turn on network time sync ? Only do surgery on the systemd files as the very last resort ;D Mike Wright ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: several issues with f34
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) man:chrony.conf(5) Process: 1047 ExecStart=/usr/sbin/chronyd $OPTIONS (code=exited, status=0/SUCCESS) Main PID: 1053 (code=exited, status=0/SUCCESS) CPU: 42ms Dec 05 09:37:31 truckin.homenet192-10.com chronyd[1053]: Frequency -3.984 +/- 0.061 ppm read from /var/lib/chrony/drift Dec 05 09:37:31 truckin.homenet192-10.com chronyd[1053]: Using right/UTC timezone to obtain leap second data Dec 05 09:37:31 truckin.homenet192-10.com systemd[1]: Started NTP client/server. Dec 05 09:41:40 truckin.homenet192-10.com chronyd[1053]: Selected source 213.154.236.182 (2.fedora.pool.ntp.org) Dec 05 09:41:40 truckin.homenet192-10.com chronyd[1053]: System clock TAI offset set to 37 seconds Dec 05 09:43:52 truckin.homenet192-10.com chronyd[1053]: Selected source 95.81.173.74 (2.fedora.pool.ntp.org) Dec 05 09:47:14 truckin.homenet192-10.com chronyd[1053]: chronyd exiting Dec 05 09:47:14 truckin.homenet192-10.com systemd[1]: Stopping NTP client/server... Dec 05 09:47:14 truckin.homenet192-10.com systemd[1]: chronyd.service: Deactivated successfully. Dec 05 09:47:14 truckin.homenet192-10.com systemd[1]: Stopped NTP client/server. I think the problem is the target. My default target is listed as graphical.target and ntpd (and chronyd) only run in multi-user.target. I did not explicitly choose graphical target so I assume it is what was configured when I installed the system some time ago. Are there going to be any issues changing the target from graphical to multi-user? Paolo On 12/5/21 11:27, Tom Horsley wrote: 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@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: several issues with f34
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=forking PrivateTmp=true ExecStart=/usr/sbin/ntpd -g -N -u ntp:ntp # Specifying -g on the command line allows ntpd to make large adjustments to # the clock on boot. However, if Restart=yes is set, a malicious (or broken) # server could send the incorrect time, trip the panic threshold, and when # ntpd restarts, serve it the incorrect time (which would be accepted). Restart=no [Install] WantedBy=multi-user.target [pgaltieri@truckin ~]$ systemctl status systemd-timesyncd.service ○ systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; disable> Active: inactive (dead) Docs: man:systemd-timesyncd.service(8) systemctl status systemd-timesyncd.service ○ systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; disable> Active: inactive (dead) Docs: man:systemd-timesyncd.service(8) Paolo On 12/5/21 11:18, francis.montag...@inria.fr wrote: systemctl status systemd-timesyncd.service ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: several issues with f34
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/lib/systemd/system/chronyd.service find /etc/systemd/system -name ntpd.service -ls 4196557 0 lrwxrwxrwx 1 root root 36 Sep 4 19:19 /etc/systemd/system/multi-user.target.wants/ntpd.service -> /usr/lib/systemd/system/ntpd.service Paolo On 12/5/21 10:55, francis.montag...@inria.fr wrote: find /etc/systemd/system -name chronyd.service -ls ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: several issues with f34
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 you'd get if you have both ntpd and chronyd enabled. So, make sure only one time sync service is enabled. -- Did 황준호 die? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: several issues with f34
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@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: several issues with f34
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-default find /etc/systemd/system -name ntpd.service -ls What gives also: systemctl cat ntpd.service and: systemctl status systemd-timesyncd.service -- francis ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: several issues with f34
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:ntpd(8) Effectively enabled. > I rebooted the system at 9:37 AM and there is no entry indicating ntpd > was started after this time. I suspect that ntpd is not enabled in the proper "target". What gives: systemctl get-default find /etc/systemd/system -name chronyd.service -ls This should produce, when in multi-user.target: systemctl get-default multi-user.target find /etc/systemd/system -name chronyd.service -ls 29844 4 lrwxrwxrwx 1 root root 39 Nov 11 18:31 /etc/systemd/system/multi-user.target.wants/chronyd.service -> /usr/lib/systemd/system/chronyd.service -- francis ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: several issues with f34
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=4163 mtu 1500 inet 192.168.10.66 netmask 255.255.255.0 broadcast 192.168.10.255 inet6 fe80::4741:dbcc:7824:9f5 prefixlen 64 scopeid 0x20 ether 4c:d9:8f:6d:87:21 txqueuelen 1000 (Ethernet) RX packets 1067 bytes 125274 (122.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 725 bytes 95167 (92.9 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 17 eno2: flags=4099 mtu 1500 ether 4c:d9:8f:6d:87:22 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 18 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 503 bytes 40302 (39.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 503 bytes 40302 (39.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 virbr0: flags=4099 mtu 1500 inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255 ether 52:54:00:ba:c1:00 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 The wifi interface does not exist, at this point I started ntpd sudo systemctl start ntpd ● ntpd.service - Network Time Service Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled; vendor preset: disabled) Active: active (running) since Sun 2021-12-05 09:09:37 PST; 2s ago Docs: man:ntpd(8) Process: 3288 ExecStart=/usr/sbin/ntpd -g -N -u ntp:ntp (code=exited, status=0/SUCCESS) Main PID: 3289 (ntpd) Tasks: 2 (limit: 37863) Memory: 11.8M CPU: 52ms CGroup: /system.slice/ntpd.service └─3289 /usr/sbin/ntpd -g -N -u ntp:ntp Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: IO: Listen normally on 3 eno1 192.168.10.66:123 Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: IO: Listen normally on 4 lo [::1]:123 Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: IO: Listen normally on 5 eno1 [fe80::4741:dbcc:7824:9> Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: IO: Listening on routing socket on fd #22 for interfa> Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: SYNC: Found 5 servers, suggest minsane at least 3 Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: INIT: MRU 10922 entries, 13 hash bits, 65536 bytes Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: INIT: Built with OpenSSL 1.1.1k FIPS 25 Mar 2021, 10> Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: INIT: Running with OpenSSL 1.1.1l FIPS 24 Aug 2021, > Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: NTSc: Using system default root certificates. Dec 05 09:09:38 truckin.homenet192-10.com ntpd[3289]: DNS: dns_probe: 0.pool.ntp.org, cast_flags:1, flags:2> I went and looked in /var/log/messages to see if there was anything there that might indicate the problem. What I found is that the only time I see: Dec 5 09:09:37 truckin systemd[1]: Starting Network Time Service... is when I do it manually. I rebooted the system at 9:37 AM and there is no entry indicating ntpd was started after this time. Paolo On 12/4/21 09:38, Ed Greshko wrote: 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 systemctl status ntpd before you restart manually. That way we may see the error causing it to fail to start initially. Paolo On 12/3/21 10:15, Joe Zeff wrote: 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 your wireless adapter and plugged it back in. Fix that and this issue should solve itself. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List
Re: several issues with f34
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 systemctl status ntpd before you restart manually. That way we may see the error causing it to fail to start initially. Paolo On 12/3/21 10:15, Joe Zeff wrote: 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 your wireless adapter and plugged it back in. Fix that and this issue should solve itself. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure -- Did 황준호 die? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: several issues with f34
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 misinterpret the EDID from the LG television I'm using as a monitor. For me I don't get an error, I just get really bad resolution. When I install the rpmfusion binary drivers they pick the correct resolution. Possibly this is a Wayland issue, not a nouveau issue. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: several issues with f34
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. 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 your wireless adapter and plugged it back in. Fix that and this issue should solve itself. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: several issues with f34
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 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), there is a kernel option you can add to the kernel boot line to point at a binary blob of EDID info that will override whatever incorrect nonsense it is getting from the KVM. Usually you just want to save the EDID from the real monitor when it is properly connected, then point the kernel at that so it will always know the right stuff. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: several issues with f34
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), there is a kernel option you can add to the kernel boot line to point at a binary blob of EDID info that will override whatever incorrect nonsense it is getting from the KVM. Usually you just want to save the EDID from the real monitor when it is properly connected, then point the kernel at that so it will always know the right stuff. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: several issues with f34
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 supported" but works fine when I boot kernel 5.14.18-200.fc34.x86_64. The other system boots fine. So what do I need to look at in order to get it to display the login screen? 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. Can you switch the configuration/cabling to see if the problem follows the cables? Next issue. This same system connects to the internet via a USB wireless adapter. This adapter never comes up at boot time. In order to get it to work I need to unplug it and plug it back in. By USB wireless adapter, do you mean a Wifi adapter? 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. Before you start it, what is the status? "systemctl status ntpd" I'm assuming it is ntpd since I've switched to usiing chronyd. -- Did 황준호 die? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: several issues with f34
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 your wireless adapter and plugged it back in. Fix that and this issue should solve itself. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
several issues with f34
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 kernel 5.14.18-200.fc34.x86_64. The other system boots fine. So what do I need to look at in order to get it to display the login screen? Next issue. This same system connects to the internet via a USB wireless adapter. This adapter never comes up at boot time. In order to get it to work I need to unplug it and plug it back in. 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. Next issue. Here is the output of df Filesystem 1K-blocks Used Available Use% Mounted on devtmpfs 16155236 0 16155236 0% /dev tmpfs 16175828 70840 16104988 1% /dev/shm tmpfs 6470332 1960 6468372 1% /run /dev/mapper/fedora_localhost--live-root 71724152 39066764 28970988 58% / tmpfs 16175832 5196 16170636 1% /tmp /dev/mapper/fedora_localhost--live-home 871075068 77722284 749034884 10% /home /dev/sdc1 999320 305456 625052 33% /boot tmpfs 3235164 136 3235028 1% /run/user/1000 /dev/sdb1 1953512032 68907808 1884604224 4% /run/media/pgaltieri/LOGS /dev/sda2 3906885628 1275040388 2631845240 33% /run/media/pgaltieri/TRUCKIN-EX tmpfs 3235164 88 3235076 1% /run/user/0 When I run sudo tune2fs -l /dev/mapper/fedora_localhost--live-root | grep Last\ c I get Last checked: Wed Jun 5 06:15:41 2019 when I do touch /forcefsck, reboot and run tune2fs again it still shows last checked as 2019. Here's the fstab /dev/mapper/fedora_localhost--live-root / ext4 defaults 1 1 UUID=e5521a04-3b65-4ceb-998d-6d4cc0a4d69e /boot ext4 defaults 1 2 /dev/mapper/fedora_localhost--live-home /home ext4 defaults 1 2 What do I need to do to get the system to check my filesystems at boot? Here is the full output of tune2fs: tune2fs 1.45.6 (20-Mar-2020) Filesystem volume name: Last mounted on: / Filesystem UUID: 1d5272bc-1524-4ddf-a5d8-cf40499a9432 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent 64bit flex_bg sparse_super large_file huge_file dir_nlink extra_isize metadata_csum Filesystem flags: signed_directory_hash Default mount options: user_xattr acl Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 4587520 Block count: 18350080 Reserved block count: 917504 Free blocks: 8150468 Free inodes: 3814351 First block: 0 Block size: 4096 Fragment size: 4096 Group descriptor size: 64 Reserved GDT blocks: 1024 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 512 Flex block group size: 16 Filesystem created: Wed Jun 5 06:15:41 2019 Last mount time: Fri Dec 3 09:15:31 2021 Last write time: Fri Dec 3 09:15:25 2021 Mount count: 180 Maximum mount count: -1 Last checked: Wed Jun 5 06:15:41 2019 Check interval: 0 () Lifetime writes: 1996 GB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 32 Desired extra isize: 32 Journal inode: 8 First orphan inode: 3410261 Default directory hash: half_md4 Directory Hash Seed: d178b832-2df2-4163-8d99-aa806b8838b7 Journal backup: inode blocks Checksum type: crc32c Checksum: 0x67b77b7d One thing I should mention is that the system that is having the problems started as a Fedora 32 system and has been upgraded to Fedora 34 using dnf upgrade. Any help is appreciated. Paolo ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it:
