users November 2022

users@lists.fedoraproject.org

87 participants
80 discussions

i915 Unstable
by Ken Smith 13 Nov '22

13 Nov '22

Hi everyone, I have a Dell Latitude 5480 laptop with a Fedora 36 install. It crashes regularly, uptime can sometimes be less that 5 mins but sometimes it lasts several hours. There is no trace at all in journalctl of its demise. It behaves like a machine with a memory issue. I've moved the memory from one slot to another and cleaned the connector. I've been using Redhat style systems for over 20 years and have known uptimes of several years. This laptop also boots Win10 and that install is stable. The machine passes Dells internal diagnostics. I'm travelling this week and don't have access to memtest86, but the Win10 memory test passes. Once I'm back home I can network boot it and run memtest86 and FC36 live - which will eliminate the ssd & its controller from the picture. . This machine has a KabbyLake processor (Intel Core i5-7200U 2.50GHz), 8G memory, an Intel i915 (HD Graphics 620) GPU and SSD storage. I've read on various forums that this combination of CPU/GPU can be problematic and some mentions that an upcoming Kernel release may contain a remedy for this. In addition to the FC36 standard kernel, I have tried a 6.0 kernel build and even the development 6.1 kernel from Rawhide's daily builds ( Beta for FC38 ) and its related firmware RPM. Also tried loading the 5.11 kernel from FC34. All with the same results. In fact the FC38 beta kernel only survives a few minutes even without the GUI. Is this hardware faulty, despite Win10 being stable? Does the Linux install stress the hardware in a way Win10 doesent. Should I hold on for a later kernel release with a fix. Is anyone else experiencing this issue? I'd value any insights. Many thanks Ken -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

5 10

Moving to a new GPU
by Patrick O'Callaghan 12 Nov '22

12 Nov '22

I've replaced my ageing Nvidia card with a more recent and much faster AMD GPU. However when I boot the system, the default display still shows as the built-in Intel chip, even though AMD modules are loaded: $ sudo lsmod|grep -i amd amdgpu 10153984 1 iommu_v2 24576 1 amdgpu gpu_sched 49152 1 amdgpu drm_ttm_helper 16384 1 amdgpu drm_buddy 20480 2 amdgpu,i915 drm_display_helper 180224 2 amdgpu,i915 ttm 94208 3 amdgpu,drm_ttm_helper,i915 (Nvidia modules are not loaded). Inxi shows: $ inxi -G Graphics: Device-1: Intel IvyBridge GT2 [HD Graphics 4000] driver: i915 v: kernel Device-2: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] driver: amdgpu v: kernel Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 22.1.3 driver: X: loaded: amdgpu,modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel HD Graphics 4000 (IVB GT2) v: 4.2 Mesa 22.1.7 Switcherooctl shows both GPUs: $ switcherooctl list Device: 0 Name: Intel® HD Graphics 4000 Default: yes Environment: DRI_PRIME=pci-0000_00_02_0 Device: 1 Name: Advanced Micro Devices, Inc. [AMD®/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (Radeon RX 580) Default: no Environment: DRI_PRIME=pci-0000_01_00_0 I should mention that both GPUs are connected through an HDMI switch to a single monitor. I've used this successfully in the past to get PCI passthrough on Windows VMs for gaming. I haven't touched anything else. I tried unplugging the i915 and rebooting (after removing the HDMI switch and connecting the monitor directly), but simply got a blank screen (in fact three dots at the top left). Is there some grub magic I need to do? I assumed this would be automatic but it seems not. poc

7 21

Font Error Before a Display of the Grub Boot Menu
by Stephen Morris 12 Nov '22

12 Nov '22

Hi, When I boot my machine I am getting a font error before the Grub Menu is being displayed but is disappearing before I can get a good look at it, which may be because of the Grub Boot Theme I am using, which has not installed its files into /boot/grub2/themes but has stored them in /usr/share/grub, irrespective of the error the grub menus display fine with the theme. The error message seems to be referencing efi/EFI/fedora/unicode.pf2 as a target but I can't be sure, but the theme being used doesn't use that file anyway. Is there anywhere I can look to find the message to understand what is being objected to? regards, Steve

2 2

Wrong screen resolution (1024x768) after upgrade
by Frédéric 11 Nov '22

11 Nov '22

Hi, I'm using F36 on a 10 year old laptop running an nividia GPU (GeForce GT 560M). I'm using the nvidia drivers from rpmfusion (390xx). Yesterday, I ran dnf upgrade and got the new 6.0.5 kernel. I lost the native screen resolution (1920x1080) and have a 1024x768 instead. I then removed the nvidia driver with dnf but it did not improve. Maybe what is provided below may help. In particular, it seems that nouveau is blacklisted but nvidia is not installed anymore... Thanks for your help, F $ lspci |grep "VGA" 01:00.0 VGA compatible controller: NVIDIA Corporation GF116M [GeForce GT 560M] (rev a1) $ cat /proc/cmdline BOOT_IMAGE=(hd0,msdos1)/vmlinuz-6.0.5-200.fc36.x86_64 root=UUID=4aab7630-84b2-4eae-9c5e-804ff8657b7f ro rhgb quiet $ cat /etc/sysconfig/grub GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_TERMINAL_OUTPUT="console" GRUB_CMDLINE_LINUX="rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1" GRUB_DISABLE_RECOVERY="true" GRUB_ENABLE_BLSCFG=true $ journalctl -b 0 oct. 31 09:28:49 vouise kernel: video: probe of PNP0A08:00 failed with error -22 oct. 31 09:28:49 vouise kernel: ACPI: video: [Firmware Bug]: ACPI(MXM3) defines _DOD but not _DOS oct. 31 09:28:49 vouise kernel: ACPI: video: Video Device [MXM3] (multi-head: yes rom: no post: no) oct. 31 09:28:49 vouise kernel: acpi device:1a: registered as cooling_device8 oct. 31 09:28:49 vouise kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:18/LNXVIDEO:00/input/input18

9 28

Can one rescue a dead SSD?
by andreas.fournier＠runbox.com 10 Nov '22

10 Nov '22

So, a SSD just dieded on me, the root and home partition was on it. The computer froze and after a cold boot the BIOS doesn't find the disk anymore. I opened up the casing but couldn't see anything suspicious to the naked eye. Anything I could do at home to try to rescue it? I have backups of most things but not the most recent stuff.

10 14

Looking to get connection between 2 local networks?
by Michael D. Setzer II 10 Nov '22

10 Nov '22

Probable a simple solution, but its been a while since I done this type of stuff. Have a cable modem that has 4 ports but using 2. First port gets public IP xxx.xxx.233.11 with private network 192.168.16.x Second port gets public IP xxx.xxx.234.251 with private network 192.168.24.x ip route default via 192.168.16.1 dev enp8s0 proto dhcp metric 100 default via 192.168.24.1 dev wlp7s0 proto dhcp metric 600 192.168.16.0/24 dev enp8s0 proto kernel scope link src 192.168.16.101 metric 100 192.168.24.0/24 dev wlp7s0 proto kernel scope link src 192.168.24.13 metric 600 Years ago, had setup a Redhat 9 machine that had 9 ethernet interfaces. 1 connected to college backbone, and 8 that connect to 8 separate classrooms with each having its own private network. Used IPtables and had it all able to communicate with any machine in any classroom, and all machines used a squid server running on same machine getting a 40% cache hit ratio. So know it can be done. In searching found pages that say shouldn't have two default routes, but that it what it shows on systems connect to both networks by default. Many things work, but others don't. Some things mentioned echo 1 >> /proc/sys/net/ipv4/ip_forward Which I recall needing before, but didn't seem to solve issue? Ping works between networks, but traceroute doesn't. Wondering if there is a simple solution. Thanks. +------------------------------------------------------------+ Michael D. Setzer II - Computer Science Instructor (Retired) mailto:mikes@guam.net mailto:msetzerii@gmail.com Guam - Where America's Day Begins G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/ +------------------------------------------------------------+

6 7

How do I rebuild Grub/Boot/initramfs from a Live USB?
by Jake D 08 Nov '22

08 Nov '22

Hello all. I need some help. Firstly: Please forgive the formatting - I'm new to this medium and not sure what the accepted conventions are, the HyperKitty interface is ...very basic. Also please forgive the length, I just don't know how to make it shorter without losing potentially relevant detail. If I've asked this in the wrong place, by all means punt my backside in the direction of the right place. I seem to have got myself in a bit of a mess and I’ve having trouble finding documentation that I can apply directly to my case . This is my first time on Linux so I’m not familiar with much of the terminology or background of these systems. **Background** I have an internal drive that used to successfully dual boot windows and a LUKS-encrypted F36 installation with BTRFS. I also had some spare unpartitioned space, which I used to fully install some other linux distros (including another F36 installation) to troubleshoot other minor problems (a tri-boot, so to speak) **What went wrong** The new distros installed fine, but I discovered afterwards I could no longer find/boot into my original LUKS F36 installation. In my igornance, I tried deleting clearing the new installation partitions, and now, if I select the Fedora option thru my BIOS boot menu, I just get to a 'grub> ’ prompt. I’ve tried a few commands there to boot manually but nothing worked and it wouldn’t even decrypt the root partition, worse still, somehow this process accidentally wiped the ORIGINAL LUKS F36 /boot partition too. I have no idea how. **What I have now** Partitioning follows: nvme0n1p1: EFI partition (both win and DF36) nvme0n1p2: MS Reserved nvme0n1p3: Win10 nvme0n1p5: Original Fedora /boot (accidentally wiped) nvme0n1p6: LUKS volume nvme0n1p7: Former ‘third OS’ boot partition (wiped) nvme0n1p8: Former ‘third OS’ root partition (also wiped) nvme0n1p4: Win Recovery **What I am trying to do** Unbork everything, somehow? I tried using these instructions in the official Fedora Docs, but they seem to be …wrong? Out of date? They didn’t work, I suspect due to LUKS/BTRFS. [ https://docs.fedoraproject.org/en-US/Fedora/23/html/Multiboot_Guide/common_…] The I found these...other Fedora Docs? Which seemed more up to date and looked like they had relevant bits, bit still seem directly applicable and didn't work. [https://docs.fedoraproject.org/en-US/quick-docs/bootloading-with-grub2/#res…] The only success I’ve had is with this guide: https://fedoramagazine.org/os-chroot-101-covering-btrfs-subvolumes/ . I’ve managed to chroot (a very dumb word) thru a LiveUSB session, with the following commands: >>cryptsetup luksOpen /dev/nvme0n1p6 fedora_crypt >>mount /dev/mapper/fedora_crypt /mnt/ -t btrfs -o subvol=root >>mount /dev/mapper/fedora_crypt /mnt/home -t btrfs -o subvol=home >>mount /dev/nvme0n1p5 /mnt/boot >>mkdir /mnt/boot/efi >>mount /dev/nvme0n1p1 /mnt/boot/efi >>mount --bind /dev /mnt/dev >>mount -t proc /proc /mnt/proc >>mount -t sysfs /sys /mnt/sys >>mount -t tmpfs tmpfs /mnt/run >>mkdir -p /mnt/run/systemd/resolve/ >>nano /mnt/run/systemd/resolve/stub-resolv.conf (enter 'nameserver 1.1.1.1', save) >>chroot /mnt I can ping google, and browse the original home folder with ls, so it looks like ‘im in’ the original installation via chroot (which is still a dumb word) What the problems are From there, I go back to the Fedora Docs and run >>dnf reinstall grub2-efi grub2-efi-modules shim That seems to work? Downloads and seems to install without any errors. The next step though; >>grub2-mkconfig -o /boot/grub2/grub.cfg fails with the following: >> /usr/sbin/grub2-probe: error: failed to get canonical path of ‘/dev/mapper/fedora_crypt’ I have no idea what that means. On the side, I also sees that despite the grub reinstall, theres no vmlinuz or initramfs kernel files in the reconstructed /boot partition, so I tried running >>dracut --regenerate-all which results in >>dracut: Can’t write to /boot/efi/[long-ass id code string]/[kernel version]: Directory /boot/efi/[long-ass id code string]/[kernel version] does not exist or is not accessible. This is true - that folder isn’t in /boot/efi. But I dont remember ever seeing it there, and just to check I did a fresh test install on another drive and theres nothing like that there either. So now I’m lost What I’m looking for I’m fairly sure the error messages I’m seeing are a result of oversights from my cobbled-together method and gneral lack of understanding. So if anyone knows what I missed and how/why, that’d help …but honestly I still really don’t know what’s going on and suspect I’m probably going to run into another problem just as quick Really, I’m after some sort of clear, up to date walk-through with entry-level language/detail, on how exactly to rebuild from scratch the EFI/boot partitions for F36 with a LUKS encrypted root, using BTRFS. I know the installation itself is fine and should be recoverable, I just dont know how all these different bits fit togther, and none of the guides out there seem to explain/unify the different bits into a cohesive procedure for the unfamiliar. Thanks very much.

15 54

Fedora 36: suspend failed with "PM: Some devices failed to suspend, or early wake event detected"
by Dario Lesca 08 Nov '22

08 Nov '22

When I try suspend with "systemctl suspend" my notebook Fedora 36 sometime do not suspend with "PM: Some devices failed to suspend, or early wake event detected" error. Someone can help me to resolve this issue? Many thanks Dario #---------------------------- set 14 00:41:26 dodo.home.solinos.it kernel: PM: suspend entry (s2idle) set 14 00:41:26 dodo.home.solinos.it kernel: Filesystems sync: 0.006 seconds set 14 00:41:28 dodo.home.solinos.it kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. set 14 00:41:28 dodo.home.solinos.it kernel: OOM killer disabled. set 14 00:41:28 dodo.home.solinos.it kernel: Freezing remaining freezable tasks ... (elapsed 0.002 seconds) done. set 14 00:41:28 dodo.home.solinos.it kernel: printk: Suspending console(s) (use no_console_suspend to debug) set 14 00:41:28 dodo.home.solinos.it kernel: xhci_hcd 0000:00:14.0: PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16 set 14 00:41:28 dodo.home.solinos.it kernel: xhci_hcd 0000:00:14.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x160 returns -16 set 14 00:41:28 dodo.home.solinos.it kernel: xhci_hcd 0000:00:14.0: PM: failed to suspend async: error -16 set 14 00:41:28 dodo.home.solinos.it kernel: PM: Some devices failed to suspend, or early wake event detected set 14 00:41:28 dodo.home.solinos.it kernel: nouveau 0000:01:00.0: Refused to change power state from D3hot to D0 set 14 00:41:28 dodo.home.solinos.it kernel: nouveau 0000:01:00.0: Refused to change power state from D3hot to D0 set 14 00:41:28 dodo.home.solinos.it kernel: nouveau 0000:01:00.0: Refused to change power state from D3hot to D0 set 14 00:41:28 dodo.home.solinos.it kernel: nouveau 0000:01:00.0: fb: VPR locked, but no scrubber binary! set 14 00:41:28 dodo.home.solinos.it kernel: usb 1-3: reset high-speed USB device number 4 using xhci_hcd set 14 00:41:28 dodo.home.solinos.it kernel: ata1: SATA link down (SStatus 4 SControl 300) set 14 00:41:28 dodo.home.solinos.it kernel: usb 1-3.1: reset low-speed USB device number 6 using xhci_hcd set 14 00:41:28 dodo.home.solinos.it kernel: usb 1-3.2: reset high-speed USB device number 8 using xhci_hcd set 14 00:41:28 dodo.home.solinos.it kernel: PM: resume devices took 1.418 seconds set 14 00:41:28 dodo.home.solinos.it kernel: OOM killer enabled. set 14 00:41:28 dodo.home.solinos.it kernel: Restarting tasks ... done. set 14 00:41:28 dodo.home.solinos.it gvfsd[219783]: PTP: reading event an error 0x05 occurred set 14 00:41:28 dodo.home.solinos.it kernel: thermal thermal_zone9: failed to read out thermal zone (-61) set 14 00:41:29 dodo.home.solinos.it bluetoothd[1739]: Controller resume with wake event 0x0 set 14 00:41:29 dodo.home.solinos.it kernel: PM: suspend exit set 14 00:41:29 dodo.home.solinos.it kernel: PM: suspend entry (s2idle) set 14 00:41:29 dodo.home.solinos.it kernel: Filesystems sync: 0.002 seconds set 14 00:41:31 dodo.home.solinos.it kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. set 14 00:41:31 dodo.home.solinos.it kernel: OOM killer disabled. set 14 00:41:31 dodo.home.solinos.it kernel: Freezing remaining freezable tasks ... (elapsed 0.003 seconds) done. set 14 00:41:31 dodo.home.solinos.it kernel: printk: Suspending console(s) (use no_console_suspend to debug) set 14 00:41:31 dodo.home.solinos.it kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915]) set 14 00:41:31 dodo.home.solinos.it kernel: xhci_hcd 0000:00:14.0: PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16 set 14 00:41:31 dodo.home.solinos.it kernel: xhci_hcd 0000:00:14.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x160 returns -16 set 14 00:41:31 dodo.home.solinos.it kernel: xhci_hcd 0000:00:14.0: PM: failed to suspend async: error -16 set 14 00:41:31 dodo.home.solinos.it kernel: PM: Some devices failed to suspend, or early wake event detected set 14 00:41:31 dodo.home.solinos.it kernel: nouveau 0000:01:00.0: Refused to change power state from D3hot to D0 set 14 00:41:31 dodo.home.solinos.it kernel: nouveau 0000:01:00.0: Refused to change power state from D3hot to D0 set 14 00:41:31 dodo.home.solinos.it kernel: nouveau 0000:01:00.0: Refused to change power state from D3hot to D0 set 14 00:41:31 dodo.home.solinos.it kernel: nouveau 0000:01:00.0: fb: VPR locked, but no scrubber binary! set 14 00:41:31 dodo.home.solinos.it kernel: usb 1-3: reset high-speed USB device number 4 using xhci_hcd set 14 00:41:31 dodo.home.solinos.it kernel: ata1: SATA link down (SStatus 4 SControl 300) set 14 00:41:31 dodo.home.solinos.it kernel: usb 1-3.1: reset low-speed USB device number 6 using xhci_hcd set 14 00:41:31 dodo.home.solinos.it kernel: usb 1-3.2: reset high-speed USB device number 8 using xhci_hcd set 14 00:41:31 dodo.home.solinos.it kernel: PM: resume devices took 1.418 seconds set 14 00:41:31 dodo.home.solinos.it kernel: OOM killer enabled. set 14 00:41:31 dodo.home.solinos.it kernel: Restarting tasks ... set 14 00:41:31 dodo.home.solinos.it kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915]) set 14 00:41:31 dodo.home.solinos.it kernel: done. set 14 00:41:31 dodo.home.solinos.it gvfsd[219783]: PTP: reading event an error 0x05 occurred set 14 00:41:31 dodo.home.solinos.it kernel: thermal thermal_zone9: failed to read out thermal zone (-61) set 14 00:41:31 dodo.home.solinos.it systemd-sleep[225719]: Failed to put system to sleep. System resumed again: Device or resource busy set 14 00:41:31 dodo.home.solinos.it kernel: PM: suspend exit set 14 00:41:31 dodo.home.solinos.it bluetoothd[1739]: Controller resume with wake event 0x0 set 14 00:41:31 dodo.home.solinos.it systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE set 14 00:41:31 dodo.home.solinos.it systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. set 14 00:41:31 dodo.home.solinos.it systemd[1]: Failed to start systemd-suspend.service - System Suspend. set 14 00:41:31 dodo.home.solinos.it audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' set 14 00:41:31 dodo.home.solinos.it systemd[1]: Dependency failed for suspend.target - Suspend. set 14 00:41:31 dodo.home.solinos.it systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'. set 14 00:41:31 dodo.home.solinos.it ModemManager[1836]: <info> [sleep-monitor] system is resuming set 14 00:41:31 dodo.home.solinos.it systemd-logind[1762]: Operation 'sleep' finished. -- Dario Lesca (inviato dal mio Linux Fedora 36 Workstation)

5 9

KDE Task Manager Colouring Settings
by Stephen Morris 07 Nov '22

07 Nov '22

Hi, Where do I find the settings to control the colour of the Task Manager bar for KDE under X11. I have gone into the Edit Mode settings and set the bar to Opaque, but that is not working to my satisfaction. At the moment all the icons on the bar are almost transparent and the background colour of the bar changes depending on what application I have displayed. For example, when I have a game I play being displayed in Firefox the bar colour is a sort of yellow centre gradient (yellow from the left and right edges to white in the middle) and it if have Thunderbird showing my mails the colour displayed is a slightly off-white. In system settings->appearance->colours I have turned off highlighting from the current colour theme. regards, Steve

2 4

gpt question
by ToddAndMargo 05 Nov '22

05 Nov '22

Hi All, I am going to clone (Clonezilla) a Windows gpt mechanical drive to a smaller SSD drive. I am going into gparted (FEdora Xfce Live 36) and resizing the large partition (sda3, C:) so it will fit on the new ssd drive. Question: there is a tiny sda4 hanging out there, which is presume is the gpt partition tables. Do I also need to move sda4 to the end of sda3 or is it okay to just leave it at the end of the disk? Many thanks, -T -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ When you say, "I wrote a program that crashed Windows," people just stare at you blankly and say, "Hey, I got those with the system, for free." -- Linus Torvalds ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

3 6