I have Fedora 20 setup with default kernel configuration, where bridge feature is enabled as a module (CONFIG_BRIDGE=m), and the bridge module loads as the system starts. I don't understand who initiates it, since I have not found anything about bridge.ko in /etc/sysconfig/modules/*. However it ends up in the memory and every time I have to 'rmmod' it. I would like to prohibit loading of the bridge.ko on the start up, yet I still want to manually load/unload bridge.ko whenever necessary. I know it is possible to use the blacklist feature in /etc/modprobe.d/blacklist.conf, but can anybody point out who is loading bridge.ko in default setup of Fedora 20?

I have a Dell laptop and I'm trying to run Fedora KDE Desktop 42 from an external SSD. I've freshly installed Fedora in the external SSD using another USB flash drive containing the live image. When I boot up Fedora from the external SSD, it tells me to enter passphrase for the disk. After I enter the correct passphrase/password, it takes me to a loading screen and stays there forever. If I press ESC on that screen, it displays a completely blank screen. When I press ESC again, it takes me back to the loading screen. For the installation options I made the following choices: * I selected Storage Configuration as Automatic. I also deleted everything in the drive by selecting Delete all/Reclaim space. Then I selected Encrypt my data option. * I enabled root account. I also created a user with admin privilege. I have tried to troubleshoot it and made the following adjustments as suggested by others in the Dell UEFI settings: * I have enabled all the thunderbolt related options (since I'm using thunderbolt 4 port to connect to the external SSD). Namely, *Enabled Thunderbolt Technology Support*, *Enable Thunderbolt Boot Support*, *Enable Thunderbolt (and PCle behind TBT) pre-boot modules*. * Selected Storage -> *AHCI* (default was *RAID On*, it didn't work when I tried with *RAID On* either) * Selected Pre-boot Behaviour -> *Thorough* (default was *Fastboot*) * Tried turning *Secure Boot* on and off, which made no difference (I understand that Fedora 42 is supposed to work with secure boot, but it was worth a try) #### Hardware specs - Dell Latitude 5530 - CPU: 12th Gen Intel(R) Core(TM) i5-1245U (1.60 GHz) - RAM: 16.0 GB (15.7 GB usable) - Internal Graphics Card: Intel(R) Iris(R) Xe Graphics - Internal 500 GB SSD (Contains Windows 11) - [This](https://www.amazon.co.uk/dp/B0B9C3ZVHR) Samsung 990 pro 1TB external SSD (to run Fedora) - [This](https://www.amazon.co.uk/dp/B0C8CTW8M6) ACASIS SSD enclosure, which uses thunderbolt 4 cable Any kind of help to resolve this would be appreciated. --- Edit: Just reinstalled Fedora without using the Encrypt Drive option, now I can see the following output/log when I press ESC on the loading screen. (Please note that it scrolls really fast at times so I couldn't take a proper sequential set of photos)

I am trying to access SD cards on Fedora 28, but do not have any success. System info is as follows: $ lsb_release -a LSB Version: :core-4.1-amd64:core-4.1-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-4.1-amd64:desktop-4.1-noarch:languages-4.1-amd64:languages-4.1-noarch:printing-4.1-amd64:printing-4.1-noarch Distributor ID: Fedora Description: Fedora release 28 (Twenty Eight) Release: 28 Codename: TwentyEight I was not able to access different SD cards using two different card readers. Despite of being accessible on both macOS and Windows, none of them is shown in the Nautilus file browser, the desktop or elsewhere obvious. The card readers are recognized by the system as per lsusb output: $ lsusb -v # some other USB devices Bus 001 Device 005: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x058f Alcor Micro Corp. idProduct 0x6362 Flash Card Reader/Writer bcdDevice 1.29 iManufacturer 1 iProduct 2 iSerial 3 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 250mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 # some other USB devices Bus 001 Device 006: ID 0dda:2027 Integrated Circuit Solution, Inc. USB 2.0 Card Reader Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x0dda Integrated Circuit Solution, Inc. idProduct 0x2027 USB 2.0 Card Reader bcdDevice 1.6e iManufacturer 1 iProduct 2 iSerial 3 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 4 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 5 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 # some other USB devices I then had a look at the udev events while plugging a card in and out: $ udevadm monitor monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[701.434565] change /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host4/target4:0:0/4:0:0:2/block/sde (block) UDEV [714.263816] change /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host4/target4:0:0/4:0:0:2/block/sde (block) KERNEL[748.477184] change /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host4/target4:0:0/4:0:0:2/block/sde (block) UDEV [761.338940] change /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host4/target4:0:0/4:0:0:2/block/sde (block) In addition, I had a look at the kernel messages: $ dmesg [ 603.846840] usb-storage 1-3:1.0: USB Mass Storage device detected [ 603.847749] scsi host4: usb-storage 1-3:1.0 [ 605.703531] scsi 4:0:0:0: Direct-Access Generic CF 1.6E PQ: 0 ANSI: 0 CCS [ 605.704982] scsi 4:0:0:1: Direct-Access Generic MS 1.6E PQ: 0 ANSI: 0 CCS [ 606.509034] scsi 4:0:0:2: Direct-Access Generic MMC/SD 1.6E PQ: 0 ANSI: 0 CCS [ 606.510387] scsi 4:0:0:3: Direct-Access Generic SM 1.6E PQ: 0 ANSI: 0 CCS [ 606.511519] sd 4:0:0:0: Attached scsi generic sg4 type 0 [ 606.511943] sd 4:0:0:1: Attached scsi generic sg5 type 0 [ 606.512177] sd 4:0:0:2: Attached scsi generic sg6 type 0 [ 606.512408] sd 4:0:0:3: Attached scsi generic sg7 type 0 [ 608.924586] sd 4:0:0:1: [sdd] Attached SCSI removable disk [ 629.830776] sd 4:0:0:2: [sde] Attached SCSI removable disk [ 633.048754] sd 4:0:0:3: [sdf] Attached SCSI removable disk [ 639.490479] sd 4:0:0:0: [sdc] Attached SCSI removable disk Both the output of dmesg and udevadm monitor are telling that the card should be shown as sde. However, fdisk -l does not list sde. Besides that, trying to mount the device manually, raises an error: $ mount -t auto /dev/sde /mnt/ mount: /mnt: no medium found on /dev/sde. I am not sure, whether the needed driver module is loaded properly, since there is no mmc0-like entry in the dmesg output (as I am used to know from Debian-based systems). lsmod does not list the mmc0 kernel module either: $ lsmod | grep mm rtl8192c_common 61440 1 rtl8192cu rtlwifi 98304 3 rtl8192c_common,rtl_usb,rtl8192cu The only mmc-like modules which seems to be available but are not loaded are mmc_block and mmc_core: $ modprobe mm # listing suggestions using tab auto-completion mma7660 mmc_block mmc_core mms114 How could I solve this problem or at least narrow it down?

I'm using Fedora 31 on my Notebook. Everything works well, except for Fedora dropping the wifi connection after a while, making it necessary to reconnect to the network. Every few minutes after reconnecting the behaviour repeats itself. I have no idea what the reasons are for that. It often happens when I download files (putting "load" on the network) but sometimes also without any obvious reason. The problem first appeared under Fedora 30 and stayed after the upgrade to Fedora 31. Output from journalctl -b -u NetworkManager: -- Logs begin at Sun 2019-07-14 01:05:47 CEST, end at Sat 2019-11-16 23:42:15 CET. -- Nov 16 23:35:19 localhost.localdomain systemd: Starting Network Manager... Nov 16 23:35:19 localhost.localdomain NetworkManager: [1573943719.8189] NetworkManager (version 1.20.6-1.fc31) is starting... (after a restart) Nov 16 23:35:19 localhost.localdomain NetworkManager: [1573943719.8191] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity-fedora.conf) Nov 16 23:35:19 localhost.localdomain systemd: Started Network Manager. Nov 16 23:35:19 localhost.localdomain NetworkManager: [1573943719.8260] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager" Nov 16 23:35:19 localhost.localdomain NetworkManager: [1573943719.8355] manager[0x5559cd8e80f0]: monitoring kernel firmware directory '/lib/firmware'. Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3382] hostname: hostname: using hostnamed Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3385] hostname: hostname changed from (none) to "localhost.localdomain" Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3390] dns-mgr[0x5559cd8cd240]: init: dns=default,systemd-resolved rc-manager=symlink Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3401] rfkill2: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1d.3/0000:05:00.0/ieee80211/phy0/rfkill2) (driver ath10k_pci) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3403] manager[0x5559cd8e80f0]: rfkill: Wi-Fi hardware radio set enabled Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3403] manager[0x5559cd8e80f0]: rfkill: WWAN hardware radio set enabled Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3479] Loaded device plugin: NMWifiFactory (/usr/lib64/NetworkManager/1.20.6-1.fc31/libnm-device-plugin-wifi.so) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3486] Loaded device plugin: NMAtmManager (/usr/lib64/NetworkManager/1.20.6-1.fc31/libnm-device-plugin-adsl.so) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3511] Loaded device plugin: NMTeamFactory (/usr/lib64/NetworkManager/1.20.6-1.fc31/libnm-device-plugin-team.so) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3553] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/1.20.6-1.fc31/libnm-device-plugin-bluetooth.so) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3559] Loaded device plugin: NMWwanFactory (/usr/lib64/NetworkManager/1.20.6-1.fc31/libnm-device-plugin-wwan.so) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3561] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3563] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3565] manager: Networking is enabled by state file Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3567] dhcp-init: Using DHCP client 'internal' Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3644] settings: Loaded settings plugin: ifcfg-rh ("/usr/lib64/NetworkManager/1.20.6-1.fc31/libnm-settings-plugin-ifcfg-rh.so") Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3644] settings: Loaded settings plugin: keyfile (internal) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3838] device (lo): carrier: link connected Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3845] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3886] manager: (enp4s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3951] settings: (enp4s0): created default wired connection 'Kabelgebundene Verbindung 1' Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3986] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.4067] device (wlp5s0): driver supports Access Point (AP) mode Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.4079] manager: (wlp5s0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.4127] device (wlp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.7252] device (wlp5s0): set-hw-addr: set MAC address to 96:1B:95:D7:6D:B2 (scanning) Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0023] modem-manager: ModemManager available Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0103] manager: (virbr0): new Bridge device (/org/freedesktop/NetworkManager/Devices/4) Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0157] supplicant: wpa_supplicant running Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0157] device (wlp5s0): supplicant interface state: init -> starting Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0323] manager: (virbr0-nic): new Tun device (/org/freedesktop/NetworkManager/Devices/5) Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0446] device (virbr0-nic): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0458] device (virbr0-nic): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0583] sup-iface[0x5559cd8fe130,wlp5s0]: supports 5 scan SSIDs Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0596] device (wlp5s0): supplicant interface state: starting -> ready Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0597] Wi-Fi P2P device controlled by interface wlp5s0 created Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0599] manager: (p2p-dev-wlp5s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/6) Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0602] device (p2p-dev-wlp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0610] device (p2p-dev-wlp5s0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0613] device (wlp5s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0631] sup-iface: failed to cancel p2p connect: P2P cancel failed Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.3859] device (virbr0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.3906] device (virbr0): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.3924] device (virbr0): Activation: starting connection 'virbr0' (dc059138-81a5-4d0a-bb5e-725c891ae6bf) Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.3935] device (virbr0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.3947] device (virbr0): state change: prepare -> config (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.3976] device (virbr0-nic): Activation: starting connection 'virbr0-nic' (d3fd587b-3b1e-418f-9fa9-dc52709be3e1) Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.3980] device (virbr0): state change: config -> ip-config (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.3991] device (virbr0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4045] device (virbr0-nic): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4060] device (virbr0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4066] device (virbr0-nic): state change: prepare -> config (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4073] device (virbr0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4083] manager: NetworkManager state is now CONNECTED_LOCAL Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4108] device (virbr0): Activation: successful, device activated. Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4127] device (virbr0-nic): state change: config -> ip-config (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4203] device (virbr0): bridge port virbr0-nic was attached Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4203] device (virbr0-nic): Activation: connection 'virbr0-nic' enslaved, continuing activation Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4214] device (virbr0-nic): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4270] device (virbr0-nic): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4274] device (virbr0-nic): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4291] device (virbr0-nic): Activation: successful, device activated. Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4363] device (virbr0-nic): state change: activated -> unmanaged (reason 'connection-assumed', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4374] device (virbr0): bridge port virbr0-nic was detached Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4374] device (virbr0-nic): released from master device virbr0 Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7709] policy: auto-activating connection 'Wifi-SSID' (b11eeab9-1cd2-40cf-b02e-719ac7a2cbcb) Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7722] device (wlp5s0): Activation: starting connection 'Wifi-SSID' (b11eeab9-1cd2-40cf-b02e-719ac7a2cbcb) Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7731] device (wlp5s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7741] manager: NetworkManager state is now CONNECTING Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7777] device (wlp5s0): set-hw-addr: reset MAC address to 58:00:E3:D0:B5:0F (preserve) Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7887] device (wlp5s0): supplicant interface state: ready -> disabled Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7889] device (p2p-dev-wlp5s0): supplicant management interface state: ready -> disabled Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7892] device (wlp5s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7897] device (wlp5s0): Activation: (wifi) access point 'Wifi-SSID' has security, but secrets are required. Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7898] device (wlp5s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7901] sup-iface[0x5559cd8fe130,wlp5s0]: wps: type pbc start... Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7939] device (wlp5s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7946] device (wlp5s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7950] device (wlp5s0): Activation: (wifi) connection 'Wifi-SSID' has security, and secrets exist. No new secrets needed. Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7952] Config: added 'ssid' value 'Wifi-SSID' Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7952] Config: added 'scan_ssid' value '1' Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7953] Config: added 'bssid' value '54:67:51:B8:29:2A' Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7954] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK' Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7955] Config: added 'psk' value '' Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7982] device (wlp5s0): supplicant interface state: disabled -> inactive Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7982] device (p2p-dev-wlp5s0): supplicant management interface state: disabled -> inactive Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.8098] device (wlp5s0): supplicant interface state: inactive -> scanning Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.8099] device (p2p-dev-wlp5s0): supplicant management interface state: inactive -> scanning Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.5410] device (wlp5s0): supplicant interface state: scanning -> authenticating Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.5412] device (p2p-dev-wlp5s0): supplicant management interface state: scanning -> authenticating Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.5617] device (wlp5s0): supplicant interface state: authenticating -> associating Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.5618] device (p2p-dev-wlp5s0): supplicant management interface state: authenticating -> associating Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.6162] device (wlp5s0): supplicant interface state: associating -> associated Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.6162] device (p2p-dev-wlp5s0): supplicant management interface state: associating -> associated Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.6367] device (wlp5s0): supplicant interface state: associated -> 4-way handshake Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.6367] device (p2p-dev-wlp5s0): supplicant management interface state: associated -> 4-way handshake Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.7563] device (wlp5s0): supplicant interface state: 4-way handshake -> completed Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.7564] device (wlp5s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Wifi-SSID" Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.7564] device (p2p-dev-wlp5s0): supplicant management interface state: 4-way handshake -> completed Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.7651] device (wlp5s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.7656] dhcp4 (wlp5s0): activation: beginning transaction (timeout in 45 seconds) Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.8962] dhcp4 (wlp5s0): state changed unknown -> bound Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.8970] device (wlp5s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.8993] device (wlp5s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.8995] device (wlp5s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.9002] manager: NetworkManager state is now CONNECTED_LOCAL Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.9017] manager: NetworkManager state is now CONNECTED_SITE Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.9018] policy: set 'Wifi-SSID' (wlp5s0) as default for IPv4 routing and DNS Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.9062] device (wlp5s0): Activation: successful, device activated. Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.9069] manager: startup complete Nov 16 23:35:31 localhost.localdomain NetworkManager: [1573943731.0336] manager: NetworkManager state is now CONNECTED_GLOBAL Nov 16 23:35:32 localhost.localdomain NetworkManager: [1573943732.0747] policy: set 'Wifi-SSID' (wlp5s0) as default for IPv6 routing and DNS Nov 16 23:35:34 localhost.localdomain NetworkManager: [1573943734.5034] agent-manager: req[0x5559cd9eb540, :1.201/org.gnome.Shell.NetworkAgent/1000]: agent registered Nov 16 23:40:47 localhost.localdomain NetworkManager: [1573944047.5176] manager: NetworkManager state is now CONNECTED_SITE The general journal shows the following before dropping the connection: Nov 16 23:40:40 localhost.localdomain systemd: Starting Tracker metadata database store and lookup manager... Nov 16 23:40:40 localhost.localdomain systemd: Started Tracker metadata database store and lookup manager. Nov 16 23:40:47 localhost.localdomain NetworkManager: [1573944047.5176] manager: NetworkManager state is now CONNECTED_SITE Nov 16 23:40:47 localhost.localdomain systemd: Starting Network Manager Script Dispatcher Service... Nov 16 23:40:47 localhost.localdomain systemd: Started Network Manager Script Dispatcher Service. Nov 16 23:40:47 localhost.localdomain audit: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Nov 16 23:40:57 localhost.localdomain systemd: NetworkManager-dispatcher.service: Succeeded. Nov 16 23:40:57 localhost.localdomain audit: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Nov 16 23:41:11 localhost.localdomain tracker-store: OK Nov 16 23:41:11 localhost.localdomain systemd: tracker-store.service: Succeeded. I also get the following error during the creation phase of the connection: Nov 16 23:43:08 localhost.localdomain systemd: Started Network Manager Script Dispatcher Service. Nov 16 23:43:08 localhost.localdomain kernel: wlp5s0: deauthenticating from 54:67:51:b8:29:2a by local choice (Reason: 3=DEAUTH_LEAVING) Nov 16 23:43:08 localhost.localdomain wpa_supplicant: wlp5s0: CTRL-EVENT-DISCONNECTED bssid=54:67:51:b8:29:2a reason=3 locally_generated=1 Nov 16 23:43:08 localhost.localdomain wpa_supplicant: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/0 Nov 16 23:43:08 localhost.localdomain NetworkManager: [1573944188.6104] sup-iface[0x5559cd8fe130,wlp5s0]: connection disconnected (reason -3) Nov 16 23:43:08 localhost.localdomain NetworkManager: [1573944188.6110] device (wlp5s0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed') Nov 16 23:43:08 localhost.localdomain wpa_supplicant: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Nov 16 23:43:08 localhost.localdomain NetworkManager: [1573944188.6136] dhcp4 (wlp5s0): canceled DHCP transaction Nov 16 23:43:08 localhost.localdomain NetworkManager: [1573944188.6136] dhcp4 (wlp5s0): state changed bound -> done Nov 16 23:43:08 localhost.localdomain wpa_supplicant: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=DE

I'm running Fedora 23. I have SELinux enabled and enforced. I know that you can change a file's labels with restorecon and chcon (and possibly other programs). This is no doubt an avenue by which a file's security can be bypassed. How can I make it so SELinux labels cannot be changed. [This](https://wiki.gentoo.org/wiki/SELinux/Tutorials/How_SELinux_controls_file_and_directory_accesses) Gentoo documentation page says that SELinux can be used to do that, but it doesn't say how. Fedora's targeted policy provides three particular booleans: + secure_mode — "Do not allow transition to sysadm_t, sudo and su effected" + secure_mode_insmod — "Do not allow any processes to load kernel modules" + secure_mode_policyload — "Do not allow any processes to modify kernel SELinux policy" Does Fedora policy come with some way to prevent user space processes from modifying SELinux labels?

I changed tomorrowto my old hdd to save some old files. After I installed again the new disk I cannot boot anymore in fedora and I see only the grub command display. Now I have only my phone so I took a picture and I don’t know what to enter in the ‘root=‘ command as you can see on the picture. Could you help me to restore the boot process on my pc?

Here is my disk space usage: Filesystem Size Used Avail Use% Mounted on devtmpfs 1.9G 0 1.9G 0% /dev tmpfs 1.9G 296K 1.9G 1% /dev/shm tmpfs 1.9G 1.6M 1.9G 1% /run tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup /dev/mapper/fedora-root 46G 6.0G 38G 14% / tmpfs 1.9G 76K 1.9G 1% /tmp /dev/mapper/fedora-var 9.1G 8.2G 444M 95% /var /dev/mapper/fedora-home 138G 16G 115G 12% /home tmpfs 387M 12K 387M 1% /run/user/42 tmpfs 387M 16K 387M 1% /run/user/1000 I got a 95% usage on /dev/mapper/fedora-var. I don't have much stuff to be cleaned and I am not sure whether cleaning the stuff would help in this issue. I would like to expand the disk space on /var, how could I do that? thanks

I am trying to boot Fedora Silverblue onto my laptop VIA a USB drive and I keep getting

[FAILED] Failed to start checkisomd5@dev-sdb.service - Media check on /dev/sdb.
dracut-initqueue: Job for checkisomd5@dev-sdb.service failed because the control process exited with error code.
dracut-initqueue: See "systemct1 status checkisomd5@dev-sdb.service" and "journalct1 -xeu checkisomd5@dev-sdb.service" for details
dracut: FATAL: CD check failed!
dracut: Refusing to continue

I tried running the ISO I downloaded directly on a VM through VBox and it worked fine, any clue why I keep getting this error?

I am using Fedora 28 workstation with Gnome. My current layout status with localectl status is System Locale: LANG=en_US.UTF-8 VC Keymap: us X11 Layout: us I am using localectl set-x11-keymap "us,gr" "" "," in order to add second (greek) layout. New localectl status result is System Locale: LANG=en_US.UTF-8 VC Keymap: us X11 Layout: us,gr X11 Variant: , but when I press super(key) + space, no greek characters are displayed. How can I add a second keyboard layout with command line? I have a fresh install of Fedora 28 Workstation. Selected language and keyboard layout are "US". I am trying to add a second language in the keyboard but not from Gnome (i.e. Settings->Region & Language-> Input Source), but from the command line. I am using localectl; when I use set-keymap, I can write greek characters on the login screen but not in a terminal. I am trying set-x11-keymap and I can't write greek characters -- only US. When I enter the simple command localectl set-x11-keymap us,gr in the login screen the language selector is present. But AFTER I log in, there is no language selector in the taskbar!?!?! I then made a clean install. Step 1: before I make anything, I execute setxkbmap -print and I get xkb_keymap { xkb_keycodes { include "evdev+aliases(qwerty)" }; xkb_types { include "complete" }; xkb_compat { include "complete" }; xkb_symbols { include "pc+us+inet(evdev)" }; xkb_geometry { include "pc(pc105)" }; }; Step 2: I execute the following command setxkbmap -layout "us,gr" -option "grp:win_space_toggle" Step 3: now I am trying to press win+space keys but I can't print greek characters. Step 4: the output of setxkbmap -print is now xkb_keymap { xkb_keycodes { include "evdev+aliases(qwerty)" }; xkb_types { include "complete" }; xkb_compat { include "complete" }; xkb_symbols { include "pc+us+gr:2+inet(evdev)+group(win_space_toggle)"}; xkb_geometry { include "pc(pc105)" }; }; I logged out and there is no language selector on login screen. Also: after I log in, I can write only English characters.

I am facing while dual-booting Windows and Fedora on my system. I have Fedora installed on an external SSD and Windows on the laptop's internal SSD. Every time I start my laptop, it directly boots into Windows. If I want to boot into Fedora manually, I have to press the esc button (I have a HP Pavillion laptop) while the laptop is loading to go to the boot menu, then start the UEFI-Fedora boot option, which then opens the Grub menu to choose Fedora. This is a very annoying issue, and I have tried almost all possible ways from YouTube, but they are not working and the Windows boot manager is opening by default. Please help me solve this problem.

I have an external monitor on my laptop, but it's placed wrong on the right instead of on the left from of my laptop display. When I go to displays configuration on my Fedora 42, I can rearrange it. However, when I click Apply all my windows get closed and my Plasma session resets. After I log back in, the monitors are still placed in the wrong way. I cannot change the settings. I'm using X11, the problem doesn't appear on Wayland. Using xrandr doesn't help – the same behavior repeats. This is the output of lspci | grep VGA: 00:02.0 VGA compatible controller: Intel Corporation TigerLake-H GT1 [UHD Graphics] (rev 01) 01:00.0 VGA compatible controller: NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] (rev a1) How to rearrange my displays so that it doesn't break my DE?

I'm trying to connect my Laptop (which is running fedora or manjaro) to connect all the time to my raspberry Pi with PiVPN. I have set up the IP tables and also port forwarding. I can access my Pi under 10.6.0.1 but not my normal subnet 192.168.0.0/24. On my mobile phone I can access my Local Lan from other networks, but not from my laptop. I've generated the wg0.conf wireguard file from PiVPN and put it under /etc/wireguard. And it is working. But I can't access the Lan. It should route all traffic through the Pi. I've tried adding more to the Allowed IPs but this did'nt helped either. I also added IP Tables in the conf file. Is it a problem with the OS or Wireguard? I also can ping 10.6.0.1 (PI) from another network while being connected over WireGuard, but when I try to ping 196.168.178.35 (LAN PI) it says couldn't reach host. Conf files: Pi Server: [Interface] PrivateKey = Address = 10.6.0.1/24 MTU = 1420 ListenPort = PostUp = iptables -A FORWARD -i wg0 -j ACCEPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE PostDown = iptables -D FORWARD -i wg0 -j ACCEPT; iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE [Peer] PublicKey = PresharedKey = AllowedIPs = 10.6.0.4/32 Client: [Interface] PrivateKey = Address = 10.6.0.4/24 PostUp = iptables -A FORWARD -i wg0 -j ACCEPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE PostDown = iptables -D FORWARD -i wg0 -j ACCEPT; iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE DNS = 10.6.0.1 [Peer] PublicKey = PresharedKey = Endpoint = : AllowedIPs = 0.0.0.0/0 PersistentKeepalive=30

Whenever I login to my computer I get a window which says *Enter password to unlock your login keyring* and *The password that you use to login to your computer doesn't match with the login keyring* To solve this problem I went to Accessories->Password and Keys-> right clicked on the login tab and found few options but that were of no use to me. Can anybody tell me why I get it and how to get rid from it? > I have fedora 25 installed on my computer.

I am trying to get my Blackmagic Quad HDMI Recorder working on Arch Linux. Since rebooting after the first installation, the device was never recognized by Blackmagic Software on Arch, while it continues to work on Windows. I suspect that this has to do with [the latest version of Desktop Video not released for Windows.](https://www.blackmagicdesign.com/support/family/capture-and-playback) A Fedora user created module patches for the [blackmagic](https://forum.blackmagicdesign.com/viewtopic.php?f=12&t=223633) and [blackmagic-io modules](https://forum.blackmagicdesign.com/viewtopic.php?f=12&t=215626) , but they failed on my PC.

> lspci | grep Blackmagic
05:00.0 Multimedia video controller: Blackmagic Design DeckLink Quad HDMI Recorder

> lsmod | grep blackmagic
blackmagic794624  0
blackmagic_io2424832  4

> dkms status -m blackmagic -k uname -r
blackmagic/14.4.1a4, 6.15.6-arch1-1, x86_64: installed
> dkms status -m blackmagic-io -k uname -r
blackmagic-io/14.4.1a4, 6.15.6-arch1-1, x86_64: installed

> sudo modprobe blackmagic-io

> sudo dkms build -m blackmagic -v 14.4.1a4
Module blackmagic/14.4.1a4 already built for kernel 6.15.6-arch1-1 (x86_64), skip. You may override by specifying --force.
> sudo dkms build -m blackmagic-io -v 14.4.1a4
Module blackmagic-io/14.4.1a4 already built for kernel 6.15.6-arch1-1 (x86_64), skip. You may override by specifying --force.

> cd /usr/src/blackmagic-io-14.4.1a4/
> sudo patch  sudo patch  cd ../blackmagic-14.4.1a4/
> sudo patch  sudo dkms install -m blackmagic-io -v 14.4.1 --all
Error! The action install does not support the --all parameter.

BlackMagic's FAQ in their Linux installer: > > * How do I update the firmware on a device? > > The device's firmware can be updated with the BlackmagicFirmwareUpdater. > See the man page for instructions and examples on how to use the utility. > > * The driver crashed my system > > Look for kernel output messages in dmesg and /var/log/messages. > > * The package installed, but the driver was not loaded > > Try the following command: > > # dkms status -m blackmagic-io -k uname -r > > If the status is 'installed', then the module is installed, but probably > not loaded. It can be loaded with the following command: > > # sudo modprobe blackmagic-io > > If the status is 'added', then the module failed to build. You can issue > the following command to manually run the build and use the output to > determine the problem. > > # sudo dkms build -m blackmagic-io -v 14.4.1 > > The full module version number is in the form 14.4.1aXX. This module number > can be found by running dkms status. > > A common cause is a version mismatch between the installed kernel image, > and the kernel source/headers. If they do not match, simply bring either > the source/headers or the image version up to date, and reboot your system. > Once the system is back up, the driver should be built for you at startup. > The command to install matching headers for your currently running kernel > on CentOS is: > > # sudo yum install "kernel-devel-uname-r == $(uname -r)" > > If the status is 'built', then the module has been built, but not > installed. You can issue the following command to manually install and use > the output to determine the problem. > > # sudo dkms install -m blackmagic-io -v 14.4.1 --all > > Legacy Desktop Video products on x86_64 platforms use an older driver. > Users should build and install this module with the dkms commands above, > replacing -m blackmagic-io option with -m blackmagic. > > > Known Issues > ------------ > > * Kernel module fails to install due to CET/IBT > > Intel 11th Generation and later CPUs and Linux kernels from version 5.18 > have included an Indirect Branch Tracking (IBT) feature. Linux > distributions are gradually enabling this kernel feature. For example > Fedora 40 has enabled it. The Desktop Video kernel module will fail to > load if both the CPU and distribution support IBT, this will result in > "(failed)" messages when installing Desktop Video and lines in dmesg such > as: > Missing ENDBR: nothing+0x0/0x10 [blackmagic_io] > and > kernel BUG at arch/x86/kernel/cet.c:102! > To work around this, disable IBT by adding ibt=off to the kernel command > line. > > * Performance of Nvidia embedded platforms > > Nvidia devices like Jetson may default to a mid-range power/performance > mode, eg. 30W / "mode 2". When using higher-end video modes that require > more processing, you may have to increase this setting. Refer to the > nvpmodel command or other related method in NVidia's documentation. > > * Incompatibility with small memory systems > > Sufficient memory must be available to the driver to support the number of > devices installed and their frame buffering requirements. A 64 bit system > with adequate memory is strongly recommended. In some configurations, > reserving more memory at boot for vmalloc may be necessary. More memory > can be allocated by adding 'vmalloc=' option to the kernel command > line. > > e.g. vmalloc=256M > > * Driver fails to build against certain version of linux-rt > > Some versions of the linux-rt patchset may be incompatible with the > driver. > > * ASPM with some PCI-e cards > > Some PCI-e cards (1x lane cards) do not function properly by default when > ASPM is enabled. When in this state, the device will be listed in lspci > and the BlackmagicFirmwareUpdater status will report version ff. To work > around this please add kernel boot parameter "pcie_aspm=off" to your boot > loader. > > * Settings are not saved on some versions of Fedora > > This issue is caused by the SELinux policies being incorrect on the > preferences file. To fix this issue, ensure the policycoreutils-python-utils > package is installed and run the following commands: > > # sudo rm /etc/blackmagic/BlackmagicPreferences.xml > # sudo semanage fcontext -a -t etc_runtime_t /etc/blackmagic > # sudo restorecon /etc/blackmagic

After updating to Fedora 30 and reboot, the Maschine fell in a login LOOP, but after some reboots it gets stuck at something Like this: [OK] Started Network Manager Script Dispatcher Service Within a black background. And i don't know what to do now. Could you help me with some ideas ? Thank you very much