June 2020 - Discuss - lists.centos.org

Upgrade to 8.2 from 7.8
by Jerry Geis 16 Jun '20

16 Jun '20

So now that 8 is out - is it still "frowned" upon to do that in place update ? Is that not a good / valid solution ? Thanks, Jerry

3 2

Simple scan in CentOS 7
by H 16 Jun '20

16 Jun '20

I just installed C7 on a new computer and despite Simple Scan being installed as part of C7, I have not been able to get it to recognize my Canon scanner connected to a USB port. I did have it running on another computer with C7 so there should not be any inherent issues. On a lark I installed gscan2pdf and sane-backends-drivers-scanners and sane-find-scanner found it: found USB scanner (vendor=0x04a9 [Canon], product=0x1908 [CanoScan]) at libusb:001:010 I perused my notes for the old computer but did not see I installed any additional software to get it going but I might be wrong. What have I missed? Thank you.

3 5

iwlwifi problem after Centos 8.2 update
by Georgios 16 Jun '20

16 Jun '20

Hi! I get high cpu usage on my laptop (yes im running Centos on my laptop) after my last update. At the beginning i though it was libvrtd but after stopping it gnome monitor keep showing high cpu usage although i couldnt find the app that was responsible for it with the top command. I searched my log files and I saw alot of iwlwifi message. I had to turn off wifi in order to stop high cpu usage. Any ideas how to solve it? Thanks in advance! dmesg command gives me the following output: 649.668600] RSP: 002b:00007fffaa691d60 EFLAGS: 00000293 ORIG_RAX: 000000000000002e [ 649.668602] RAX: ffffffffffffffda RBX: 000000000000000e RCX: 00007f21aecdeb07 [ 649.668603] RDX: 0000000000000000 RSI: 00007fffaa691db0 RDI: 000000000000000e [ 649.668604] RBP: 00007fffaa691db0 R08: 0000000000000000 R09: 0000000000000000 [ 649.668605] R10: 0000000000000012 R11: 0000000000000293 R12: 0000000000000000 [ 649.668605] R13: 0000000000000000 R14: 00007fffaa691f68 R15: 00007fffaa691f5c [ 649.756674] iwlwifi 0000:00:14.3: Found debug destination: EXTERNAL_DRAM [ 649.756676] iwlwifi 0000:00:14.3: Found debug configuration: 0 [ 649.757247] iwlwifi 0000:00:14.3: loaded firmware version 46.6bf1df06.0 op_mode iwlmvm [ 649.757275] iwlwifi 0000:00:14.3: Detected Intel(R) Dual Band Wireless AC 9462, REV=0x318 [ 649.765604] iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM [ 649.765843] iwlwifi 0000:00:14.3: Allocated 0x00400000 bytes for firmware monitor. [ 649.806204] iwlwifi 0000:00:14.3: base HW address: a0:a4:c5:dd:0c:52 [ 649.852141] ieee80211 phy644: Selected rate control algorithm 'iwl- mvm-rs' [ 649.853603] thermal thermal_zone8: failed to read out thermal zone (-61) [ 649.860442] iwlwifi 0000:00:14.3 wlo1: renamed from wlan0 [ 649.881196] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready [ 649.887951] iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM [ 649.977952] iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM [ 650.042990] iwlwifi 0000:00:14.3: FW already configured (0) - re- configuring [ 650.050559] iwlwifi 0000:00:14.3: Conflict between TLV & NVM regarding enabling LAR (TLV = enabled NVM =disabled) [ 650.250610] iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0. [ 650.250685] iwlwifi 0000:00:14.3: Start IWL Error Log Dump: [ 650.250686] iwlwifi 0000:00:14.3: Status: 0x00000040, count: 6 [ 650.250687] iwlwifi 0000:00:14.3: Loaded firmware version: 46.6bf1df06.0 [ 650.250688] iwlwifi 0000:00:14.3: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL [ 650.250689] iwlwifi 0000:00:14.3: 0x00A0A2B1 | trm_hw_status0 [ 650.250690] iwlwifi 0000:00:14.3: 0x00000000 | trm_hw_status1 [ 650.250690] iwlwifi 0000:00:14.3: 0x004882DA | branchlink2 [ 650.250691] iwlwifi 0000:00:14.3: 0x0047932A | interruptlink1 [ 650.250692] iwlwifi 0000:00:14.3: 0x0000B0D0 | interruptlink2 [ 650.250692] iwlwifi 0000:00:14.3: 0x0001A83E | data1 [ 650.250693] iwlwifi 0000:00:14.3: 0x00001000 | data2 [ 650.250694] iwlwifi 0000:00:14.3: 0xF0000008 | data3 [ 650.250695] iwlwifi 0000:00:14.3: 0x00000000 | beacon time [ 650.250695] iwlwifi 0000:00:14.3: 0x00038F74 | tsf low [ 650.250696] iwlwifi 0000:00:14.3: 0x00000000 | tsf hi [ 650.250697] iwlwifi 0000:00:14.3: 0x00000000 | time gp1 [ 650.250697] iwlwifi 0000:00:14.3: 0x00038F75 | time gp2 [ 650.250698] iwlwifi 0000:00:14.3: 0x00000001 | uCode revision type [ 650.250699] iwlwifi 0000:00:14.3: 0x0000002E | uCode version major [ 650.250700] iwlwifi 0000:00:14.3: 0x6BF1DF06 | uCode version minor [ 650.250700] iwlwifi 0000:00:14.3: 0x00000312 | hw version [ 650.250701] iwlwifi 0000:00:14.3: 0x18C89008 | board version [ 650.250702] iwlwifi 0000:00:14.3: 0x001E0177 | hcmd [ 650.250702] iwlwifi 0000:00:14.3: 0x20122080 | isr0 [ 650.250703] iwlwifi 0000:00:14.3: 0x00000000 | isr1 [ 650.250704] iwlwifi 0000:00:14.3: 0x08001802 | isr2 [ 650.250704] iwlwifi 0000:00:14.3: 0x404001C0 | isr3 [ 650.250705] iwlwifi 0000:00:14.3: 0x00000000 | isr4 [ 650.250706] iwlwifi 0000:00:14.3: 0x001E0177 | last cmd Id [ 650.250707] iwlwifi 0000:00:14.3: 0x0001A83E | wait_event [ 650.250707] iwlwifi 0000:00:14.3: 0x00000000 | l2p_control [ 650.250708] iwlwifi 0000:00:14.3: 0x00010820 | l2p_duration [ 650.250709] iwlwifi 0000:00:14.3: 0x00000000 | l2p_mhvalid [ 650.250709] iwlwifi 0000:00:14.3: 0x00000000 | l2p_addr_match [ 650.250710] iwlwifi 0000:00:14.3: 0x0000000D | lmpm_pmg_sel [ 650.250711] iwlwifi 0000:00:14.3: 0x08081425 | timestamp [ 650.250711] iwlwifi 0000:00:14.3: 0x0000183C | flow_handler [ 650.250744] iwlwifi 0000:00:14.3: Start IWL Error Log Dump: [ 650.250744] iwlwifi 0000:00:14.3: Status: 0x00000040, count: 7 [ 650.250746] iwlwifi 0000:00:14.3: 0x20000034 | NMI_INTERRUPT_WDG [ 650.250746] iwlwifi 0000:00:14.3: 0x00000000 | umac branchlink1 [ 650.250747] iwlwifi 0000:00:14.3: 0xC008885E | umac branchlink2 [ 650.250748] iwlwifi 0000:00:14.3: 0x80454D04 | umac interruptlink1 [ 650.250748] iwlwifi 0000:00:14.3: 0xC00842AC | umac interruptlink2 [ 650.250749] iwlwifi 0000:00:14.3: 0x00000400 | umac data1 [ 650.250750] iwlwifi 0000:00:14.3: 0xC00842AC | umac data2 [ 650.250751] iwlwifi 0000:00:14.3: 0xDEADBEEF | umac data3 [ 650.250751] iwlwifi 0000:00:14.3: 0x0000002E | umac major [ 650.250752] iwlwifi 0000:00:14.3: 0x6BF1DF06 | umac minor [ 650.250753] iwlwifi 0000:00:14.3: 0x00038F5B | frame pointer [ 650.250753] iwlwifi 0000:00:14.3: 0xC0886B5C | stack pointer [ 650.250754] iwlwifi 0000:00:14.3: 0x001F010C | last host cmd [ 650.250755] iwlwifi 0000:00:14.3: 0x00000000 | isr status reg [ 650.250772] iwlwifi 0000:00:14.3: Fseq Registers: [ 650.250780] iwlwifi 0000:00:14.3: 0x5CAAF71A | FSEQ_ERROR_CODE [ 650.250788] iwlwifi 0000:00:14.3: 0x00000000 | FSEQ_TOP_INIT_VERSION [ 650.250796] iwlwifi 0000:00:14.3: 0x48E767D9 | FSEQ_CNVIO_INIT_VERSION [ 650.250805] iwlwifi 0000:00:14.3: 0x0000A384 | FSEQ_OTP_VERSION [ 650.250813] iwlwifi 0000:00:14.3: 0xBDFB20C4 | FSEQ_TOP_CONTENT_VERSION [ 650.250821] iwlwifi 0000:00:14.3: 0xC098A1DF | FSEQ_ALIVE_TOKEN [ 650.250830] iwlwifi 0000:00:14.3: 0x247AF0C2 | FSEQ_CNVI_ID [ 650.250838] iwlwifi 0000:00:14.3: 0x3AE78660 | FSEQ_CNVR_ID [ 650.250846] iwlwifi 0000:00:14.3: 0x01000100 | CNVI_AUX_MISC_CHIP [ 650.250876] iwlwifi 0000:00:14.3: 0x00000201 | CNVR_AUX_MISC_CHIP [ 650.250887] iwlwifi 0000:00:14.3: 0x0000485B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM [ 650.250944] iwlwifi 0000:00:14.3: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR [ 650.250980] iwlwifi 0000:00:14.3: Collecting data: trigger 2 fired. [ 650.250983] ieee80211 phy644: Hardware restart was requested [ 650.251019] iwlwifi 0000:00:14.3: iwlwifi transaction failed, dumping registers [ 650.251021] iwlwifi 0000:00:14.3: iwlwifi device config registers: [ 650.251197] iwlwifi 0000:00:14.3: 00000000: 9df08086 00100406 02800030 00800010 a131c004 00000000 00000000 00000000 [ 650.251198] iwlwifi 0000:00:14.3: 00000020: 00000000 00000000 00000000 42a48086 00000000 000000c8 00000000 0000010b [ 650.251199] iwlwifi 0000:00:14.3: 00000040: 00928010 10000ec0 00100c10 00000000 00000000 00000000 00000000 00000000 [ 650.251201] iwlwifi 0000:00:14.3: 00000060: 00000000 00080812 00000405 00000000 00000000 00000000 00000000 00000000 [ 650.251202] iwlwifi 0000:00:14.3: 00000080: 800f0011 00002000 00003000 00000000 00000000 00000000 00000000 00000000 [ 650.251203] iwlwifi 0000:00:14.3: 000000a0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 650.251204] iwlwifi 0000:00:14.3: 000000c0: 00000000 00000000 c823d001 0d000008 00804005 00000000 00000000 00000000 [ 650.251205] iwlwifi 0000:00:14.3: 000000e0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 650.251206] iwlwifi 0000:00:14.3: 00000100: 14c00000 ff000000 000000ff 00462031 00000000 00002000 00000000 00000000 [ 650.251207] iwlwifi 0000:00:14.3: 00000120: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 650.251208] iwlwifi 0000:00:14.3: 00000140: 00000000 00000000 00000000 16410018 00000000 0001001e 00481e1f 00000000 [ 650.251209] iwlwifi 0000:00:14.3: iwlwifi device memory mapped registers: [ 650.251251] iwlwifi 0000:00:14.3: 00000000: 18c89008 00000040 00000000 00000000 00000000 00000000 00000000 00000000 [ 650.251252] iwlwifi 0000:00:14.3: 00000020: 00000000 0c040005 00000312 d55555d5 d55555d5 d55555d5 80008040 041f0040 [ 650.251260] iwlwifi 0000:00:14.3: FW error in SYNC CMD SCAN_CFG_CMD [ 650.251262] CPU: 0 PID: 1437 Comm: NetworkManager Kdump: loaded Not tainted 4.18.0-193.6.3.el8_2.x86_64 #1 [ 650.251263] Hardware name: Dell Inc. Vostro 5481/0PK27Y, BIOS 1.0.0 09/05/2018 [ 650.251263] Call Trace: [ 650.251268] dump_stack+0x5c/0x80 [ 650.251274] iwl_trans_pcie_send_hcmd+0x370/0x380 [iwlwifi] [ 650.251278] ? finish_wait+0x80/0x80 [ 650.251282] iwl_trans_send_cmd+0x5b/0xc0 [iwlwifi] [ 650.251288] iwl_mvm_send_cmd+0x1b/0x40 [iwlmvm] [ 650.251292] iwl_mvm_legacy_config_scan+0x274/0x440 [iwlmvm] [ 650.251297] iwl_mvm_config_scan+0xec/0x100 [iwlmvm] [ 650.251300] iwl_mvm_up+0x89a/0xa60 [iwlmvm] [ 650.251303] __iwl_mvm_mac_start+0x26/0x1d0 [iwlmvm] [ 650.251306] iwl_mvm_mac_start+0x23/0x40 [iwlmvm] [ 650.251318] drv_start+0x43/0x100 [mac80211] [ 650.251327] ieee80211_do_open+0x251/0x900 [mac80211] [ 650.251330] __dev_open+0xcd/0x160 [ 650.251331] __dev_change_flags+0x1ad/0x220 [ 650.251332] dev_change_flags+0x21/0x60 [ 650.251333] do_setlink+0x314/0xe90 [ 650.251334] ? update_curr+0x70/0x1c0 [ 650.251335] ? cpumask_next_and+0x1a/0x20 [ 650.251337] ? __nla_validate_parse+0x51/0x840 [ 650.251338] ? cpumask_next+0x17/0x20 [ 650.251340] ? __snmp6_fill_stats64.isra.56+0x6b/0x110 [ 650.251340] ? __nla_validate_parse+0x51/0x840 [ 650.251341] __rtnl_newlink+0x53d/0x890 [ 650.251343] ? __nla_reserve+0x38/0x50 [ 650.251345] ? security_sock_rcv_skb+0x2a/0x40 [ 650.251346] ? sk_filter_trim_cap+0x49/0x230 [ 650.251348] ? netlink_attachskb+0x1b0/0x1e0 [ 650.251349] ? skb_queue_tail+0x1b/0x50 [ 650.251351] ? __netlink_sendskb+0x51/0x70 [ 650.251354] ? _cond_resched+0x15/0x30 [ 650.251356] ? kmem_cache_alloc_trace+0x140/0x1c0 [ 650.251357] rtnl_newlink+0x43/0x60 [ 650.251358] rtnetlink_rcv_msg+0x200/0x2f0 [ 650.251359] ? rtnl_calcit.isra.35+0x110/0x110 [ 650.251360] netlink_rcv_skb+0x4c/0x120 [ 650.251362] netlink_unicast+0x19e/0x260 [ 650.251363] netlink_sendmsg+0x204/0x3d0 [ 650.251365] sock_sendmsg+0x4c/0x50 [ 650.251366] ___sys_sendmsg+0x29f/0x300 [ 650.251367] ? copy_overflow+0x20/0x20 [ 650.251368] ? __rtnl_unlock+0x25/0x50 [ 650.251369] ? netdev_run_todo+0x5e/0x290 [ 650.251370] ? addrconf_sysctl_forward+0x113/0x250 [ 650.251372] __sys_sendmsg+0x57/0xa0 [ 650.251374] do_syscall_64+0x5b/0x1a0 [ 650.251375] entry_SYSCALL_64_after_hwframe+0x65/0xca [ 650.251376] RIP: 0033:0x7f21aecdeb07 [ 650.251378] Code: c3 66 90 41 54 41 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 e8 eb ec ff ff 44 89 e2 48 89 ee 89 df 41 89 c0 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 48 89 44 24 08 e8 24 ed ff ff 48 [ 650.251378] RSP: 002b:00007fffaa692040 EFLAGS: 00000293 ORIG_RAX: 000000000000002e [ 650.251379] RAX: ffffffffffffffda RBX: 000000000000000e RCX: 00007f21aecdeb07 [ 650.251380] RDX: 0000000000000000 RSI: 00007fffaa692090 RDI: 000000000000000e [ 650.251380] RBP: 00007fffaa692090 R08: 0000000000000000 R09: 0000000000000000 [ 650.251381] R10: 0000000000000002 R11: 0000000000000293 R12: 0000000000000000 [ 650.251381] R13: 0000000000000000 R14: 00007fffaa692248 R15: 00007fffaa69223c [ 650.251384] iwlwifi 0000:00:14.3: Firmware not running - cannot dump error [ 650.271000] iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM [ 650.362380] iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM [ 650.427431] iwlwifi 0000:00:14.3: FW already configured (0) - re- configuring [ 650.436705] iwlwifi 0000:00:14.3: Conflict between TLV & NVM regarding enabling LAR (TLV = enabled NVM =disabled) [ 650.636708] iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0. [ 650.636788] iwlwifi 0000:00:14.3: Start IWL Error Log Dump: [ 650.636792] iwlwifi 0000:00:14.3: Status: 0x00000050, count: 6 [ 650.636796] iwlwifi 0000:00:14.3: Loaded firmware version: 46.6bf1df06.0 [ 650.636801] iwlwifi 0000:00:14.3: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL [ 650.636804] iwlwifi 0000:00:14.3: 0x00A0A2F1 | trm_hw_status0 [ 650.636807] iwlwifi 0000:00:14.3: 0x00000000 | trm_hw_status1 [ 650.636810] iwlwifi 0000:00:14.3: 0x004882DA | branchlink2 [ 650.636813] iwlwifi 0000:00:14.3: 0x0047932A | interruptlink1 [ 650.636816] iwlwifi 0000:00:14.3: 0x0000B0D0 | interruptlink2 [ 650.636819] iwlwifi 0000:00:14.3: 0x0001A83E | data1 [ 650.636822] iwlwifi 0000:00:14.3: 0x00001000 | data2 [ 650.636825] iwlwifi 0000:00:14.3: 0xF0000008 | data3 [ 650.636828] iwlwifi 0000:00:14.3: 0x00000000 | beacon time [ 650.636831] iwlwifi 0000:00:14.3: 0x000395B6 | tsf low [ 650.636834] iwlwifi 0000:00:14.3: 0x00000000 | tsf hi [ 650.636837] iwlwifi 0000:00:14.3: 0x00000000 | time gp1 [ 650.636840] iwlwifi 0000:00:14.3: 0x000395B6 | time gp2 [ 650.636860] iwlwifi 0000:00:14.3: 0x00000001 | uCode revision type [ 650.636863] iwlwifi 0000:00:14.3: 0x0000002E | uCode version major [ 650.636866] iwlwifi 0000:00:14.3: 0x6BF1DF06 | uCode version minor [ 650.636869] iwlwifi 0000:00:14.3: 0x00000312 | hw version [ 650.636872] iwlwifi 0000:00:14.3: 0x18C89008 | board version [ 650.636875] iwlwifi 0000:00:14.3: 0x001D0177 | hcmd [ 650.636878] iwlwifi 0000:00:14.3: 0x20122080 | isr0 [ 650.636881] iwlwifi 0000:00:14.3: 0x00000000 | isr1 [ 650.636884] iwlwifi 0000:00:14.3: 0x08001802 | isr2 [ 650.636887] iwlwifi 0000:00:14.3: 0x404001C0 | isr3 [ 650.636889] iwlwifi 0000:00:14.3: 0x00000000 | isr4 [ 650.636892] iwlwifi 0000:00:14.3: 0x001D0177 | last cmd Id [ 650.636895] iwlwifi 0000:00:14.3: 0x0001A83E | wait_event [ 650.636898] iwlwifi 0000:00:14.3: 0x00000000 | l2p_control [ 650.636901] iwlwifi 0000:00:14.3: 0x00000820 | l2p_duration [ 650.636904] iwlwifi 0000:00:14.3: 0x00000000 | l2p_mhvalid [ 650.636907] iwlwifi 0000:00:14.3: 0x00000000 | l2p_addr_match [ 650.636910] iwlwifi 0000:00:14.3: 0x0000000D | lmpm_pmg_sel [ 650.636913] iwlwifi 0000:00:14.3: 0x08081425 | timestamp [ 650.636916] iwlwifi 0000:00:14.3: 0x0000183C | flow_handler [ 650.636953] iwlwifi 0000:00:14.3: Start IWL Error Log Dump: [ 650.636956] iwlwifi 0000:00:14.3: Status: 0x00000050, count: 7 [ 650.636959] iwlwifi 0000:00:14.3: 0x20000034 | NMI_INTERRUPT_WDG [ 650.636962] iwlwifi 0000:00:14.3: 0x00000000 | umac branchlink1 [ 650.636965] iwlwifi 0000:00:14.3: 0xC008885E | umac branchlink2 [ 650.636968] iwlwifi 0000:00:14.3: 0x80454D04 | umac interruptlink1 [ 650.636971] iwlwifi 0000:00:14.3: 0xC00842AC | umac interruptlink2 [ 650.636974] iwlwifi 0000:00:14.3: 0x00000400 | umac data1 [ 650.636977] iwlwifi 0000:00:14.3: 0xC00842AC | umac data2 [ 650.636980] iwlwifi 0000:00:14.3: 0xDEADBEEF | umac data3 [ 650.636983] iwlwifi 0000:00:14.3: 0x0000002E | umac major [ 650.636986] iwlwifi 0000:00:14.3: 0x6BF1DF06 | umac minor [ 650.636989] iwlwifi 0000:00:14.3: 0x0003959E | frame pointer [ 650.636992] iwlwifi 0000:00:14.3: 0xC0886B5C | stack pointer [ 650.636995] iwlwifi 0000:00:14.3: 0x001E010C | last host cmd [ 650.636998] iwlwifi 0000:00:14.3: 0x00000000 | isr status reg [ 650.637017] iwlwifi 0000:00:14.3: Fseq Registers: [ 650.637025] iwlwifi 0000:00:14.3: 0x5CAAF71A | FSEQ_ERROR_CODE [ 650.637034] iwlwifi 0000:00:14.3: 0x00000000 | FSEQ_TOP_INIT_VERSION [ 650.637042] iwlwifi 0000:00:14.3: 0x48E767D9 | FSEQ_CNVIO_INIT_VERSION [ 650.637051] iwlwifi 0000:00:14.3: 0x0000A384 | FSEQ_OTP_VERSION [ 650.637060] iwlwifi 0000:00:14.3: 0xBDFB20C4 | FSEQ_TOP_CONTENT_VERSION [ 650.637068] iwlwifi 0000:00:14.3: 0xC098A1DF | FSEQ_ALIVE_TOKEN [ 650.637077] iwlwifi 0000:00:14.3: 0x247AF0C2 | FSEQ_CNVI_ID [ 650.637085] iwlwifi 0000:00:14.3: 0x3AE78660 | FSEQ_CNVR_ID [ 650.637094] iwlwifi 0000:00:14.3: 0x01000100 | CNVI_AUX_MISC_CHIP [ 650.637105] iwlwifi 0000:00:14.3: 0x00000201 | CNVR_AUX_MISC_CHIP [ 650.637115] iwlwifi 0000:00:14.3: 0x0000485B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM [ 650.637157] iwlwifi 0000:00:14.3: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR [ 650.637166] iwlwifi 0000:00:14.3: Firmware error during reconfiguration - reprobe! [ 650.637199] iwlwifi 0000:00:14.3: LED command failed: -5 [ 650.637219] iwlwifi 0000:00:14.3: FW error in SYNC CMD SCAN_CFG_CMD [ 650.637240] CPU: 3 PID: 1437 Comm: NetworkManager Kdump: loaded Not tainted 4.18.0-193.6.3.el8_2.x86_64 #1 [ 650.637241] iwlwifi 0000:00:14.3: LED command failed: -5 [ 650.637244] Hardware name: Dell Inc. Vostro 5481/0PK27Y, BIOS 1.0.0 09/05/2018 [ 650.637245] Call Trace: [ 650.637256] dump_stack+0x5c/0x80 [ 650.637275] iwl_trans_pcie_send_hcmd+0x370/0x380 [iwlwifi] [ 650.637284] ? finish_wait+0x80/0x80 [ 650.637300] iwl_trans_send_cmd+0x5b/0xc0 [iwlwifi] [ 650.637318] iwl_mvm_send_cmd+0x1b/0x40 [iwlmvm] [ 650.637337] iwl_mvm_legacy_config_scan+0x274/0x440 [iwlmvm] [ 650.637353] iwl_mvm_config_scan+0xec/0x100 [iwlmvm] [ 650.637366] iwl_mvm_up+0x89a/0xa60 [iwlmvm] [ 650.637379] __iwl_mvm_mac_start+0x26/0x1d0 [iwlmvm] [ 650.637391] iwl_mvm_mac_start+0x23/0x40 [iwlmvm] [ 650.637423] drv_start+0x43/0x100 [mac80211] [ 650.637460] ieee80211_do_open+0x251/0x900 [mac80211] [ 650.637466] __dev_open+0xcd/0x160 [ 650.637471] __dev_change_flags+0x1ad/0x220 [ 650.637475] dev_change_flags+0x21/0x60 [ 650.637480] do_setlink+0x314/0xe90 [ 650.637484] ? update_curr+0x70/0x1c0 [ 650.637489] ? cpumask_next_and+0x1a/0x20 [ 650.637493] ? __nla_validate_parse+0x51/0x840 [ 650.637497] ? cpumask_next+0x17/0x20 [ 650.637502] ? __snmp6_fill_stats64.isra.56+0x6b/0x110 [ 650.637505] ? __nla_validate_parse+0x51/0x840 [ 650.637510] __rtnl_newlink+0x53d/0x890 [ 650.637515] ? __nla_reserve+0x38/0x50 [ 650.637521] ? security_sock_rcv_skb+0x2a/0x40 [ 650.637527] ? sk_filter_trim_cap+0x49/0x230 [ 650.637533] ? netlink_attachskb+0x1b0/0x1e0 [ 650.637537] ? skb_queue_tail+0x1b/0x50 [ 650.637541] ? __netlink_sendskb+0x51/0x70 [ 650.637553] ? filename_lookup.part.63+0xd3/0x170 [ 650.637559] ? _cond_resched+0x15/0x30 [ 650.637563] ? kmem_cache_alloc_trace+0x140/0x1c0 [ 650.637568] rtnl_newlink+0x43/0x60 [ 650.637572] rtnetlink_rcv_msg+0x200/0x2f0 [ 650.637576] ? rtnl_calcit.isra.35+0x110/0x110 [ 650.637581] netlink_rcv_skb+0x4c/0x120 [ 650.637587] netlink_unicast+0x19e/0x260 [ 650.637593] netlink_sendmsg+0x204/0x3d0 [ 650.637598] sock_sendmsg+0x4c/0x50 [ 650.637602] ___sys_sendmsg+0x29f/0x300 [ 650.637608] ? try_to_wake_up+0x54/0x570 [ 650.637613] ? __check_object_size+0xa8/0x16b [ 650.637617] ? wake_up_q+0x70/0x70 [ 650.637623] ? __wake_up_common+0x7a/0x190 [ 650.637629] __sys_sendmsg+0x57/0xa0 [ 650.637635] do_syscall_64+0x5b/0x1a0 [ 650.637640] entry_SYSCALL_64_after_hwframe+0x65/0xca [ 650.637644] RIP: 0033:0x7f21aecdeb07 [ 650.637649] Code: c3 66 90 41 54 41 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 e8 eb ec ff ff 44 89 e2 48 89 ee 89 df 41 89 c0 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 48 89 44 24 08 e8 24 ed ff ff 48 [ 650.637651] RSP: 002b:00007fffaa691d60 EFLAGS: 00000293 ORIG_RAX: 000000000000002e [ 650.637655] RAX: ffffffffffffffda RBX: 000000000000000e RCX: 00007f21aecdeb07 [ 650.637657] RDX: 0000000000000000 RSI: 00007fffaa691db0 RDI: 000000000000000e [ 650.637658] RBP: 00007fffaa691db0 R08: 0000000000000000 R09: 0000000000000000 [ 650.637660] R10: 0000000000000012 R11: 0000000000000293 R12: 0000000000000000 [ 650.637662] R13: 0000000000000000 R14: 00007fffaa691f68 R15: 00007fffaa691f5c [ 650.722207] iwlwifi 0000:00:14.3: Found debug destination: EXTERNAL_DRAM [ 650.722209] iwlwifi 0000:00:14.3: Found debug configuration: 0 [ 650.722634] iwlwifi 0000:00:14.3: loaded firmware version 46.6bf1df06.0 op_mode iwlmvm [ 650.722653] iwlwifi 0000:00:14.3: Detected Intel(R) Dual Band Wireless AC 9462, REV=0x318 [ 650.729579] iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM [ 650.729914] iwlwifi 0000:00:14.3: Allocated 0x00400000 bytes for firmware monitor. [ 650.770224] iwlwifi 0000:00:14.3: base HW address: a0:a4:c5:dd:0c:52 [ 650.814071] ieee80211 phy645: Selected rate control algorithm 'iwl- mvm-rs' [ 650.822074] thermal thermal_zone8: failed to read out thermal zone (-61) [ 650.835672] iwlwifi 0000:00:14.3 wlo1: renamed from wlan0 [ 650.850976] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready

1 0

CentOS-announce Digest, Vol 184, Issue 6
by centos-announce-request＠centos.org 16 Jun '20

16 Jun '20

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. Release for CentOS Linux 8 (2004) (Brian Stinson) ---------------------------------------------------------------------- Message: 1 Date: Mon, 15 Jun 2020 11:29:32 -0500 From: Brian Stinson <bstinson(a)centosproject.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] Release for CentOS Linux 8 (2004) Message-ID: <1491307c-4a76-1bc2-7375-9c85cdff3214(a)centosproject.org> Content-Type: text/plain; charset=utf-8 Release for CentOS Linux 8 (2004) We are pleased to announce the general availability of CentOS Linux 8. Effectively immediately, this is the current release for CentOS Linux 8 and is tagged as 2004, derived from Red Hat Enterprise Linux 8.2 Source Code. As always, read through the Release Notes at : http://wiki.centos.org/Manuals/ReleaseNotes/CentOS8.2004? - these notes contain important information about the release and details about some of the content inside the release from the CentOS QA team. These notes are updated constantly to include issues and incorporate feedback from the users. ---------- Updates, Sources, and DebugInfos Updates released since the upstream release are all posted, across all architectures. We strongly recommend every user apply all updates, including the content released today, on your existing CentOS Linux 8 machine by just running 'dnf update'. As with all CentOS Linux 8 components, this release was built from sources hosted at git.centos.org. Sources will be available from vault.centos.org in their own dedicated directories to match the corresponding binary RPMs. Since there is far less traffic to the CentOS source RPMs compared with the binary RPMs, we are not putting this content on the main mirror network. If users wish to mirror this content they can do so using the reposync command available in the yum/dnf-utils package. All CentOS source RPMs are signed with the same key used to sign their binary counterparts. Developers and end users looking at inspecting and contributing patches to the CentOS Linux distro will find the code hosted at git.centos.org far simpler to work against. Details on how to best consume those are documented along with a quick start at : http://wiki.centos.org/Sources Debuginfo packages have been signed and pushed. Yum configs shipped in the new release file will have all the context required for debuginfo to be available on every CentOS Linux install. This release supersedes all previously released content for CentOS Linux 8, and therefore we highly encourage all users to upgrade their machines. Information on different upgrade strategies and how to handle stale content is included in the Release Notes. Note that older content, obsoleted by newer versions of the same applications are trim'd off from repos like extras/ and centosplus/ ---------- Download We produced the following installer images for CentOS Linux 8 # CentOS-8.2.2004-x86_64-minimal.iso: 1718616064 bytes SHA256 (CentOS-8.2.2004-x86_64-minimal.iso) = 47ab14778c823acae2ee6d365d76a9aed3f95bb8d0add23a06536b58bb5293c0 # CentOS-8.2.2004-x86_64-boot.iso: 654311424 bytes SHA256 (CentOS-8.2.2004-x86_64-boot.iso) = c67876a5602faa17f68b40ccf2628799b87454aa67700f0f57eec15c6ccdd98c # CentOS-8.2.2004-x86_64-dvd1.iso: 8231321600 bytes SHA256 (CentOS-8.2.2004-x86_64-dvd1.iso) = c87a2d81d67bbaeaf646aea5bedd70990078ec252fc52f5a7d65ff609871e255 # CentOS-8.2.2004-aarch64-minimal.iso: 1410226176 bytes SHA256 (CentOS-8.2.2004-aarch64-minimal.iso) = 621d08902bfd7ca8437cd536b86631c87ddc3e36a530abc77011d230401eb158 # CentOS-8.2.2004-aarch64-boot.iso: 579823616 bytes SHA256 (CentOS-8.2.2004-aarch64-boot.iso) = 76a9a5f84ac9581fee079d7154bf68f72661c9d941e9ab3143bccc760c23eecc # CentOS-8.2.2004-aarch64-dvd1.iso: 5988872192 bytes SHA256 (CentOS-8.2.2004-aarch64-dvd1.iso) = 9d2f066edfc3820fc9e4c6d52f01489a3ed57515cf608773e2b8a04f1903c838 # CentOS-8.2.2004-ppc64le-minimal.iso: 1493422080 bytes SHA256 (CentOS-8.2.2004-ppc64le-minimal.iso) = 1d6802ce5581bd6ae22d13e491dfad65b7a32166f1484e8d6c532cd4cd7e18db # CentOS-8.2.2004-ppc64le-boot.iso: 628408320 bytes SHA256 (CentOS-8.2.2004-ppc64le-boot.iso) = a039bc592e416b97914b6c99cc8cb070d6b35742dbcb7b6eccff55291659c664 # CentOS-8.2.2004-ppc64le-dvd1.iso: 7080738816 bytes SHA256 (CentOS-8.2.2004-ppc64le-dvd1.iso) = 1a94eff60fd016ea8efb1d592eda85f0b5edde2ff2ad4c77db546ab90392421e Information for the torrent files and sums are available at http://mirror.centos.org/centos/8/isos/ -------- Additional Images Vagrant and Generic Cloud images are available at: http://cloud.centos.org/centos/8/ Amazon Machine Images for Amazon Web Services are published by ID into a number of regions. A table of AMI IDs can be found here: https://wiki.centos.org/Cloud/AWS ---------- Getting Help The CentOS ecosystem is sustained by community driven help and guidance. The best place to start for new users is at http://wiki.centos.org/GettingHelp We are also on social media, you can find the project: on Twitter at? :http://twitter.com/CentOSProject on Facebook at :https://www.facebook.com/groups/centosproject/ on LinkedIn at :https://www.linkedin.com/groups/22405 And you will find the core team and a majority of the contributors on irc, on freenode.net in #centos ; talking about the finer points of distribution engineering and platform enablement. ---------- Contributors This release was made possible due to the hard work of many people, foremost on that list are the Red Hat Engineers for producing a great distribution and the CentOS QA team, without them CentOS Linux would look very different. Many of the team went further and beyond expectations to bring this release to you, and I would like to thank everyone for their help. We are also looking for people to get involved with the QA process in CentOS, if you would like to join this please introduce yourself on the centos-devel list (http://lists.centos.org/mailman/listinfo/centos-devel? ). Finally, please join me in thanking the donors who all make this possible for us. Enjoy the fresh new release! Thanks, Brian Stinson ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 184, Issue 6 ***********************************************

1 0

smb protocol version
by Christopher Wensink 16 Jun '20

16 Jun '20

I have a handful of Linux Servers, running Centos 6.10, and 6.8 with the main host running openvz w/ Centos 6.10 as the main OS. Two of the guests are running samba, sharing directories out to windows clients. I'm in the process of migrating servers over to vmware, using Centos 7.8. How can I determine what smb protocol version is being used in the shares for each server? I don't see the protocol specified anywhere in smb.conf? Chris

4 4

Re: [CentOS] C8 install problems SOLVED
by ejm 15 Jun '20

15 Jun '20

I burned a total of 7.55Gb from an ISO image to a dual-layer HP DVD+R disc. I got a bootable USB stick containing 8.1 and it's 7.65 Gb so apparently my ISO image file is messed up. I was able to install C8 just fine from the USB stick, so marking this as solved. Thanks, --Ed

1 0

/etc/networks file
by Jay Hart 15 Jun '20

15 Jun '20

I am having some network connectivity issues that manifest itself through ping, wget, dnf, etc. The symptoms are intermittent ability to ping, was wget, or connect to repositories. Where this inquiry is going is: If your internal network is using 192.168.1 or 10..50.10, what should be in /etc/networks. My current file contains: default 0.0.0.0 loopback 127.0.0.0 link-local 169.254.0.0 And I'm pretty sure this is the default OS installed contents. I don't think this is related to my connectivity issue, just curious about what this file does. My old server (which is working just fine) has the same content in its /etc/networks file so not configuring this does not seem to matter one way or the other. If one were using 192.168.1.x network , assume 'default' should be 192.168.1.0. 'Link-local' should match??? Thanks, Jay

4 4

halt versus shutdown
by Leon Fauster 15 Jun '20

15 Jun '20

Working with different OSs can be quite challenging (mentally :-)). I wonder why the command "halt" has not same result between EL6 and EL8. To shutdown the vm or workstation in EL8 i must use "shutdown now". Who mandates this behavior in terms of configuration file? -- Leon

6 10

Modifying username
by Jay Hart 15 Jun '20

15 Jun '20

I modified a users name on my system. From ABCLast, to ALast (used as an example). I modified the username, then the group name of the user (to align with the new name), and then I moved the users home directory from /home/ABCLast, to /home/ALast. Then using vipw, edited the home directory to use /home/ALast. When I got finished editing the passwd file, I got the following message: You have modified /etc/passwd. You may need to modify /etc/shadow for consistency. I don't know what to do here. Need some guidance please. lastly, did I miss anything here? Any other steps I need to do to get this user squared away due to the name change? Thanks, Jay

6 7

pppoe
by Joe 12 Jun '20

12 Jun '20

Hello, CentOS 8 dropped the rp-pppoe package. My attempts with NetworkManager-ppp already failed because it seems that it is not possible to use a VLAN as a device. Please, how does it work under C8 to set up a pppoe connection (German Telekom, VDSL (VLAN 7 required), ZTE modem). Thanks. Joe

2 1

Minicom and Ncurses
by Nicolas Kovacs 12 Jun '20

12 Jun '20

Hi, I have to do some maintenance on a CentOS 7 proxy installed on a routerboard without a video card. The only way to access this machine directly is via Minicom and serial port. I'm using NetworkManager TUI (nmtui) to configure network interfaces, but Ncurses rendering in Minicom works in the sense that chickens fly and horses swim. What you get is a forest of question marks with a few barely recognizable options lost in between. Is there some magical trick to render Ncurses interfaces correctly in Minicom ? Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12

4 4

CentOS-announce Digest, Vol 184, Issue 5
by centos-announce-request＠centos.org 12 Jun '20

12 Jun '20

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2020:2530 Important CentOS 7 tomcat Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 11 Jun 2020 21:13:08 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:2530 Important CentOS 7 tomcat Security Update Message-ID: <20200611211308.GA14121(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:2530 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:2530 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 1a682ecdfdca8179b910e4ad1364c7ea7af6484572fa4c0bf786d78a32b2352f tomcat-7.0.76-12.el7_8.noarch.rpm 3fbf1ba29d42285e346eea1daf56195b30a3e94182dc36be98483cd12cbd21cc tomcat-admin-webapps-7.0.76-12.el7_8.noarch.rpm 0e0d2a192959f0e924276b1a404f1696e4c8f489e745d0f759efae4b2e712533 tomcat-docs-webapp-7.0.76-12.el7_8.noarch.rpm 150fbb8d578feb9baac913edd690284b9723f51a4ef734cb834bd87b19eb6110 tomcat-el-2.2-api-7.0.76-12.el7_8.noarch.rpm 919467bef774bb63bf51ec63c3758c1b0a98fed3d3ba41eaf9da630bc7e7932a tomcat-javadoc-7.0.76-12.el7_8.noarch.rpm 4119baf0bb201bf72b2e037b2df5af8a2f03d88341a41e6af7310429daded8f4 tomcat-jsp-2.2-api-7.0.76-12.el7_8.noarch.rpm 1c864d58ea8b2a77959443e02fd45cd9424414ac02881ae7db8fb1f7abee126c tomcat-jsvc-7.0.76-12.el7_8.noarch.rpm 6d203bb8a91bda83c4ec3973e3bc72f428675e7c3a0f33363e535c92f56c5395 tomcat-lib-7.0.76-12.el7_8.noarch.rpm b02d127bdaef8b0e305453b6bdf3479008875b1f574b172429d5ead159591733 tomcat-servlet-3.0-api-7.0.76-12.el7_8.noarch.rpm d307e0fd8ecc96b206c97fe1e7003080cfc6a4d5f90d73a4aecbafd14f48c023 tomcat-webapps-7.0.76-12.el7_8.noarch.rpm Source: d18613ee3eff59b1223761f5843b528d137200f7ee6e7d66e4dde770fb164115 tomcat-7.0.76-12.el7_8.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 184, Issue 5 ***********************************************

1 0

CentOS-announce Digest, Vol 184, Issue 4
by centos-announce-request＠centos.org 11 Jun '20

11 Jun '20

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2020:2433 Moderate CentOS 6 microcode_ctl Security Update (Johnny Hughes) 2. CESA-2020:2430 Moderate CentOS 6 kernel Security Update (Johnny Hughes) 3. CESA-2020:2432 Moderate CentOS 7 microcode_ctl Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 10 Jun 2020 17:17:14 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:2433 Moderate CentOS 6 microcode_ctl Security Update Message-ID: <20200610171714.GA3446(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:2433 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2020:2433 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: bc2910c9f73fe13f75c2921410c368230698ad20c41c6bc8f2b077e875bc5ecb microcode_ctl-1.17-33.26.el6_10.i686.rpm x86_64: d61387797006fdb5af23de80a5751ff3769dbdbb53d89839809dc98359b58125 microcode_ctl-1.17-33.26.el6_10.x86_64.rpm Source: 29a7a32919a8d60ce03d01075170f32614032b89bd9bf8b3e46b76525018c082 microcode_ctl-1.17-33.26.el6_10.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Wed, 10 Jun 2020 17:19:46 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:2430 Moderate CentOS 6 kernel Security Update Message-ID: <20200610171946.GA3787(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:2430 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2020:2430 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 11bf519a323e41b66b238dc14e924b0b5d3b6d637dc4d8f5e866a566545ea7f0 kernel-2.6.32-754.30.2.el6.i686.rpm 2502bbcf915834aae1634c2ece36bafb9a3348fef2b9232e147477d81874c853 kernel-abi-whitelists-2.6.32-754.30.2.el6.noarch.rpm 15f96d91bfc8fe4a00f5ec978233cbc05167bfe7734ec2c1b6ed071e68566406 kernel-debug-2.6.32-754.30.2.el6.i686.rpm e7e5ffa9c22ed9d43fcf4e98e08dafdd1be3a308824a60103843540a0b1456d5 kernel-debug-devel-2.6.32-754.30.2.el6.i686.rpm 4fff97920b1df19e4b2ae0af5e2a3f0cfca8853858e7c892bfbfe112507cb6b6 kernel-devel-2.6.32-754.30.2.el6.i686.rpm 921d611a19b98c2f04f9981edf3324b27b869f8a1d327adb60061ff71a912aaf kernel-doc-2.6.32-754.30.2.el6.noarch.rpm bf7722b27bd32467a52cf669295c683070fba5151ee297a33f7718dd7dd16107 kernel-firmware-2.6.32-754.30.2.el6.noarch.rpm a29ac2d4a39828bc7c5a18c9f728b0695b35d33ffb11c3dbcd8dc2b0f4621f21 kernel-headers-2.6.32-754.30.2.el6.i686.rpm 86a91237241b6d70a7ef40118609a192095ebc6867b6dde631eb935f6301d794 perf-2.6.32-754.30.2.el6.i686.rpm 54ab43ad2015f540fa658ea87ef5c7b7e24d411150aa1d58398be71af04d8c6e python-perf-2.6.32-754.30.2.el6.i686.rpm x86_64: 921bf8f31a14a20b2ae2c729af200cac547e18d5459bdf68c2fd13e76c08f83e kernel-2.6.32-754.30.2.el6.x86_64.rpm 2502bbcf915834aae1634c2ece36bafb9a3348fef2b9232e147477d81874c853 kernel-abi-whitelists-2.6.32-754.30.2.el6.noarch.rpm 2c3fe628af77d70d17d4df1f409e693dad07100ae1394473258422a785403cc4 kernel-debug-2.6.32-754.30.2.el6.x86_64.rpm e7e5ffa9c22ed9d43fcf4e98e08dafdd1be3a308824a60103843540a0b1456d5 kernel-debug-devel-2.6.32-754.30.2.el6.i686.rpm 403bc658ff35b9fafb243d94d6cf6fa028b2530b2c31164e776f4b1a95995679 kernel-debug-devel-2.6.32-754.30.2.el6.x86_64.rpm 22d0199606b0ffa91d4981ffeafe3bf14eddb4176ebd1afe76e01e2dac46806f kernel-devel-2.6.32-754.30.2.el6.x86_64.rpm 921d611a19b98c2f04f9981edf3324b27b869f8a1d327adb60061ff71a912aaf kernel-doc-2.6.32-754.30.2.el6.noarch.rpm bf7722b27bd32467a52cf669295c683070fba5151ee297a33f7718dd7dd16107 kernel-firmware-2.6.32-754.30.2.el6.noarch.rpm 59b69f6865b2598236fd7f1062321e8cfba8562f8f6f03533a88a0d1234d6543 kernel-headers-2.6.32-754.30.2.el6.x86_64.rpm fe5f89cc7d77d68ded0aea3d056408e5405b90b1ecaea31e174ad600e17ff7e0 perf-2.6.32-754.30.2.el6.x86_64.rpm 5439d7ca2bbf1686b75f1209436985aaee824e9c188359f5e5dae1c1b10183dd python-perf-2.6.32-754.30.2.el6.x86_64.rpm Source: b23d189769ca45756cbf8dac9fdfd11b507414a2c64f5e8973fd8540aa2ba211 kernel-2.6.32-754.30.2.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Wed, 10 Jun 2020 17:22:53 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:2432 Moderate CentOS 7 microcode_ctl Security Update Message-ID: <20200610172253.GA4100(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:2432 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2020:2432 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: e60f84fe58d8f960f14241fc1c21ad0053213bad8ba294fc3c5f727d37076e4c microcode_ctl-2.1-61.6.el7_8.x86_64.rpm Source: 42a0ea626d8554d7d25af8a383010f11fd791f7689f8943c7b97646db5550acc microcode_ctl-2.1-61.6.el7_8.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 184, Issue 4 ***********************************************

1 0

virt-manager guest and sound
by Jerry Geis 10 Jun '20

10 Jun '20

I am running C7 host and pulse audio. I have a Win 10 guest with ICH9 audio. It works - but I hear artifacts. Anything to do to help audio be flawless under guest VM ? Currently I was just on youtube and playing a song. nothing special. Plenty of resources on the host. The guest has 8G ram and 8 CPU. Thanks Jerry

3 2

In CentOS 8 new install, old /home, .desktop opens in gedit
by Lamar Owen 10 Jun '20

10 Jun '20

Ok, hoping someone has seen this or at least knows where to look. I have been waiting around a bit to upgrade my system to CentOS 8, and actually wanted to wait on 8.2, but had an opportunity this week to actually do the work, so took the opportunity. Here was my process: 1.) Installed CentOS 8.1.1911 on a spare mSATA SSD in my spare M6700 laptop. Installed the RPMfusion nVidia drivers, the PowerTools repo, set up the extensions for Places, Applications, etc, and got it prepped to accept my /home disk. 2.) After complete backups, physically moved my /home disk from the CentOS 7 M6700 to the CentOS 8 M6700. /home is on a LUKS LVM lv; got all the mount options and encryption options setup to start on boot. All of that now works, even though it took a bit of wrangling (if the filesystem mount is set to start up at boot without the nofail option BUT the encryption option is left at the User Default setting, it will not work!). Did a complete SELinux relabel (touch /.autorelabel and reboot). Moved the default GNOME config dirs over to the old /home; don't want a lot of cruft left over from the C7 install (which has been upgraded over the years from C6, Fedora 14, and earlier, and it was time to get rid of some cruft, I'm sure). After booting back up with the old /home in place, verified the GNOME extensions settings I had set up after the new install. All looks good, and working like it's supposed to so far. 3.) Moved over the Win10 and Win7 virtual machines, all of that works fine. 4.) Started installing my everyday programs, beginning with Harrison Mixbus. The program put its menu entry in place; all good. However, when I go to double click on the .desktop shortcut, it opens in gedit. Hmm, this ain't quite right. This worked fine on C7 in GNOME Standard mode. So, at this point, the Mixbus_6.0.702.desktop file is on my desktop, it's in ~/Desktop with executable permissions and is owned by the correct user, but right-clicking on it does not bring up the choice to 'Allow Launching.' The GNOME Extension 'Desktop Icons' is installed and is active. I've tried a whole lot of suggestions, but wanted to see if anyone here had seen this before and has solved the problem to allow launching of the .desktop file as it is supposed to do. Just knowing that 'it works for you' actually is helpful, especially if we can figure out what is different from my install to yours (SELinux context, permissions, etc). Just knowing where to look would be helpful; and I'm going to diff my old GNOME config from my /home backup to the fresh as-installed config.... gnome-shell-extension-desktop-icons-3.32.1-10.el8.noarch is installed.

1 0

CentOS-announce Digest, Vol 184, Issue 3
by centos-announce-request＠centos.org 10 Jun '20

10 Jun '20

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2020:2414 Important CentOS 7 unbound Security Update (Johnny Hughes) 2. CESA-2020:2414 Important CentOS 7 unbound Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Tue, 9 Jun 2020 15:58:30 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:2414 Important CentOS 7 unbound Security Update Message-ID: <20200609155830.GA14423(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:2414 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:2414 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) Source: 23ffc6fc5c3340e4e55cb79b8da3f80361bd4adcac8215c0cf561dd83738560a unbound-1.6.6-4.el7_8.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Tue, 9 Jun 2020 17:13:01 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:2414 Important CentOS 7 unbound Security Update Message-ID: <20200609171301.GA16717(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:2414 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:2414 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: d7c7de939c7a3dbec81adf688ae2557ca2fc3f18498eb9c09b8896d3b73dd071 unbound-1.6.6-4.el7_8.x86_64.rpm d253cd8566f10e05e7bbaba91b8985b224760bd9bc95d7be1236a61a2a300846 unbound-devel-1.6.6-4.el7_8.i686.rpm e08699d98dc4bdc6e3b0420111f4c7a54fd21233dfe55c8b0a966c770023e54f unbound-devel-1.6.6-4.el7_8.x86_64.rpm 75c67d364ea5de70c161e35d62955896b31edafb1314e1338b5ff4d265ec23e4 unbound-libs-1.6.6-4.el7_8.i686.rpm 84862fc5e25c9431d1c50a088469c311a471ecf1f475906b2758ccb65ffe2f20 unbound-libs-1.6.6-4.el7_8.x86_64.rpm da25fe4519d413260c142ca775e23133ce865ed79ceeb4e60448c1fea9b1ecd0 unbound-python-1.6.6-4.el7_8.x86_64.rpm Source: 23ffc6fc5c3340e4e55cb79b8da3f80361bd4adcac8215c0cf561dd83738560a unbound-1.6.6-4.el7_8.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 184, Issue 3 ***********************************************

1 0

C8 install problems
by ejm 10 Jun '20

10 Jun '20

Hi all, I am trying to install C8 from a DVD I made onto a 1Tb disc partitioned into 2 ext4 partitions. The first partition contains C7 which I installed via a DVD. Trying to install C8 yields an error indicating the file /dev/root is missing. I've checked the SHA256 sum for the ISO for CentOS 8.1 1911 and it checks out fine. I've burned a couple of different DVDs and get the same error about /dev/root missing from both. I burned both DVDs using the PC app PowerISO. Is that potentially a problem ? Looking at the log file of the C8 install I see before the message about /dev/root, that the file /etc/iscsi/initiatorname.iscsi is missing --and /sbin/modprobe -bv sg failed w/ exit code 1 I am doing the install with the target 1Tb disc attached, via a USB cable from a SATA docking station, to a ASUS PC running Windows 7. I boot up via the DVD just fine on the PC, but I've not been able to get past the errors from iSCSI and /dev/root. I do see a message at the very beginning of the install that the hardware family 12h is "not supported upstream". I'm not sure if that message is important, or a red herring. Is it possible that the Orico SATA docking station (model 6619) has been dropped in C8 ? Any tips or suggestions would be greatly appreciated. Thanks, --Ed

2 1

yum/dnf diff
by Kenneth Porter 10 Jun '20

10 Jun '20

I'm used to using "git diff" and "svn diff" to view changes in my development system. Is there a similar thing that works with changes between a repository package and the installed RPM? Ie. something that shows the changes in /etc hinted at by "rpm -V". I'm already using etckeeper+git but that would combine changes from updates with my own modifications. The only thing I've found so far is a rather manual procedure: <https://serverfault.com/questions/378439/getting-diffs-for-file-changes-det…>

7 14

Disabling fips mode in Centos 7.6
by Akshar Kanak 10 Jun '20

10 Jun '20

Dear team if i need to disable FIPS on Centos 7.6 , then setting fips=0 in kernel parameter should be more then sufficient . Why should we remove the dracut-fips package and regenerate the initramfs? Thanks and regards Akshar

1 0

Switching between keyboards in CentOS 7 using the MATE desktop
by H 09 Jun '20

09 Jun '20

I switch between three keyboards, two western ones and Chinese Pinyin entry. I have fcitx installed to switch between Pinyin and standard entry and use the keyboard switching in MATE to switch between keyboards. While I originally believed there was a bug in fcitx since switching between entry fields in firefox, chromium and thunderbird using the non-default keyboard always switched me back to the default keyboard, this even when hitting ENTER in a Chromium entryfield, I now believe the problem might lie in MATE or CentOS. There is no problem remembering whether a particular program is configured by me to use Pinyin input or not so that seems to work fine. Can anyone else confirm this issue? Might it be a configuration issue on my end? By the way, I use CTRL-SHIFT+RIGHT-SHIFT to switch between keyboards.

1 0

firewalld / iptables / nftables
by Leon Fauster 09 Jun '20

09 Jun '20

Despite that the migration of our applications comes with a significant workload. It seems that also every aspect of common services had changed with EL8. In EL8 firewalld uses nftables as backend. I wonder why iptables does not list any rules while also configured to use nftables as backend. # iptables -V iptables v1.8.2 (nf_tables) # firewall-cmd --list-all |egrep -o '22|ssh' ssh # nft list ruleset | egrep -o '22|ssh' ssh # iptables -L -n | egrep -o '22|ssh' <EMPTY> Any hints? -- Leon

4 4

Trying to get bride network on CentOS 7 working with virt-manager
by Jerry Geis 09 Jun '20

09 Jun '20

I have these interfaces listed. eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.8 netmask 255.255.252.0 broadcast 192.168.3.255 inet6 fe80::e2d5:5eff:fe63:abe5 prefixlen 64 scopeid 0x20<link> ether e0:d5:5e:63:ab:e5 txqueuelen 1000 (Ethernet) RX packets 42411243 bytes 4701898681 (4.3 GiB) RX errors 0 dropped 156 overruns 0 frame 0 TX packets 78372982 bytes 34946337897 (32.5 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 16 memory 0x92f00000-92f20000 virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255 ether 52:54:00:fc:34:af txqueuelen 1000 (Ethernet) RX packets 132792 bytes 337411780 (321.7 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 138593 bytes 742263806 (707.8 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 virbr1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 192.168.100.1 netmask 255.255.255.0 broadcast 192.168.100.255 ether 52:54:00:9c:39:02 txqueuelen 1000 (Ethernet) RX packets 206217 bytes 132308800 (126.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 105448 bytes 197008661 (187.8 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 virbr0-nic: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether 52:54:00:fc:34:af 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 When I bring up virt-manager, got settings for my VM, and for "Network Source" I select "Specify Shared Device Name" and I have tried the virbr0 and clicked apply and boot the machine. I get networking but not bridged networking - not a 192.168.1.X address. Is there something I missed ? Thanks, Jerry

2 2

Postfix restrictions
by Nicolas Kovacs 09 Jun '20

09 Jun '20

Hi, I'm currently fine-tuning my mail server (Postfix and Dovecot on CentOS 7). SPF, DKIM and DMARC work fine, now I'd like to limit the spam tsunami. Besides the official Postfix documentation, I've read a few articles about Postfix spam restrictions, namely these : https://www.linuxbabe.com/mail-server/block-email-spam-postfix https://wiki.centos.org/HowTos/postfix_restrictions After some experimenting, here's what I currently have on my test server: --8<----- /etc/postfix/main.cf ----------------------------- ... smtpd_helo_required = yes smtpd_helo_restrictions = permit_mynetworks, permit_sasl_authenticated, check_helo_access hash:/etc/postfix/helo_access reject_invalid_helo_hostname, reject_non_fqdn_helo_hostname, reject_unknown_helo_hostname smtpd_sender_restrictions = permit_mynetworks, permit_sasl_authenticated, check_sender_access hash:/etc/postfix/sender_access, reject_unknown_sender_domain, reject_unknown_reverse_client_hostname, reject_unknown_client_hostname smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, check_client_access hash:/etc/postfix/rbl_override, reject_rhsbl_helo dbl.spamhaus.org, reject_rhsbl_reverse_client dbl.spamhaus.org, reject_rhsbl_sender dbl.spamhaus.org, reject_rbl_client zen.spamhaus.org --8<-------------------------------------------------------- Before committing this configuration to my main server, I thought I'd share this configuration on the list. Maybe the Postfix gurus among you have the odd comment to make. My aim is simply to eliminate as much spam as possible (that is, before adding SpamAssassin) while keeping false positives to a minimum. Any suggestions ? Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12

6 6

EPEL repository: Failure to download metadata
by Jay Hart 08 Jun '20

08 Jun '20

Trying to install certbot, for Lets Encrypt certificate installation. How do I fix the below repo issue? I have not been successful tracking down this issue using google. [root@dream postfix]# yum install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm CentOS-8 - AppStream 0.0 B/s | 0 B 00:10 Failed to download metadata for repo 'AppStream' Error: Failed to download metadata for repo 'AppStream' [root@dream postfix]# ^C [root@dream postfix]# ls /etc/yum.repos.d/ CentOS-AppStream.repo CentOS-CR.repo CentOS-Extras.repo CentOS-Media.repo CentOS-Vault.repo CentOS-Base.repo CentOS-Debuginfo.repo CentOS-fasttrack.repo CentOS-PowerTools.repo CentOS-centosplus.repo CentOS-Devel.repo CentOS-HA.repo CentOS-Sources.repo [root@dream postfix]# dnf repolist CentOS-8 - AppStream 0.0 B/s | 0 B 00:25 Failed to download metadata for repo 'AppStream' Error: Failed to download metadata for repo 'AppStream' Thanks, Jay

1 2

Logitech webcam for use with CentOS 7
by H 08 Jun '20

08 Jun '20

I am thinking of buying a Logitech C920S Pro HD or C922 webcam for the necessary video conferencing. Is anyone using that with Zoom or perhaps with Jitsi? Do I need drivers? Any issues? Thank you.

7 6

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss June 2020