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: <none> 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 (<none>) 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