Wrong screen resolution (1024x768) after upgrade
by Frédéric
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
1 year, 6 months
- 9
- 28
How do I rebuild Grub/Boot/initramfs from a Live USB?
by Jake D
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/commo...]
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/#r...]
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.
1 year, 6 months
- 15
- 54
Fedora 36: suspend failed with "PM: Some devices failed to suspend,
or early wake event detected"
by Dario Lesca
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)
1 year, 6 months
- 5
- 9
KDE Task Manager Colouring Settings
by Stephen Morris
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
1 year, 6 months
- 2
- 4
Can I see an iMac drive with a Live USB?
by ToddAndMargo
Hi All,
I have an upcoming appointment with a customer
who wants a number of his old computers
(mostly iMacs) removed from service.
With other computers, if I can remove the
drives, I just remove them and give them
to the customer to hit with a hammer.
But iMacs I will need a glass puller, etc..
So what I usually do when I can not get the
drive out is to boot into a Linux (Fedora)
Live USB and run
# dd if=/dev/zero of=/dev/sd[x]
Where sd[x] is the drive to be blanked.
This will write 0x00H across every section
of the drive.
Then give it to the computer local charity used
computer store (or the dumpster)
"dev" only has to see the drive. I do not
need or want to be able to mount or read
the drive, just see it. dd is a block
device and does not care what format is.
Do any of you guys know if I will be able
to see the drive on a iMac?
Many thanks,
-T
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Computers are like air conditioners.
They malfunction when you open windows
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 year, 7 months
- 9
- 18
Can't unsubscribe from a list
by fs 3000
I keep getting mails from arm@ no matter what i do. I have tried sending mail to arm-leave@, it says i'm not a member. I went to the page and unsubscribed from there, nothing works. Any idea?
1 year, 7 months
- 4
- 4
Fwd: [Undeliverable: Re: Mailing lists and Discourse]
by Wolfgang Pfeiffer
TL;DR:
Emails I'm sending to this list take many hours until they reach this
list. Main problem 'tho is that shortly after sending them I'm getting
an error message from postmaster(a)outlook.com telling me about
unspecified errors regarding the mail transport. The message for this
is attached with this email.
Details:
I actually wanted to send this email to an admin responsible for this
list, but there's no one to find. And I encourage everyone not
familiar with a mess like below to simply ignore this message:
I hope 'tho that someone from the Fedora list admins has a look at it.
The problem seems to be on the side of the Fedora mail distribution
servers, that seem to be connected in one way or another with
outlook.com.
The error message below, that was sent to me after sending an email to
this list (via relay=mail.gmx.net. [212.227.17.190] - the message
itself can be seen at the very end of the forwarded message below) is
a mess, so it's not clear at all who is resposible for the fact that
my emails to this list are
1: first delivered with no problems that I'd know of to the Fedora
list's servers (see the default Fedora list footers attached to my
email that I sent, at the very end of this message, which seem to
indicate just that) and after that successfull delivery to the
fedora servers are
2: managed by some outlook.com servers (please see messages below),
that complain that
"(protection.outlook.com: domain of transitioning
lists.fedoraproject.org discourages use of 205.220.165.146 as
permitted sender)"
3: Additionally some y.antoniowatson(a)gmail.com is involved (see below).
Plus I checked my MTA (sendmail) logs: I have not sent this mail at
the very end to some y.antoniowatson(a)gmail.com, whoever this is ...
The email below, at the very end of this forwarded mail, obviously,
after successfully being sent to the fedora list servers, was handled
by outlook.com and lists.fedoraproject.org - and in the end delivered
to this list. After many hours.
So two questions to Fedora list admins (or anyone else who understands
the message attached)
1: Is my email address roto(a)gmx.net seen as a spammer address by the
Fedora list software?
2: Does anyone understand what happened according to the message
attached below from postmaster(a)outlook.com
Thanks in anticipation
Wolfgang
----- Forwarded message from postmaster(a)outlook.com -----
Date: Wed, 26 Oct 2022 17:46:59 +0000
From: postmaster(a)outlook.com
Subject: Undeliverable: Re: Mailing lists and Discourse
To: roto(a)gmx.net
Delivery has failed to these recipients or groups:
y.antoniowatson(a)gmail.com<mailto:y.antoniowatson@gmail.com>
Your message wasn't delivered because the recipient's email provider rejected it.
Diagnostic information for administrators:
Generating server: PR3P189MB1017.EURP189.PROD.OUTLOOK.COM
y.antoniowatson(a)gmail.com
Remote Server returned '550-5.7.26 The MAIL FROM domain [gmx.net] has an SPF record with a hard fail 550-5.7.26 policy (-all) but it fails to pass SPF checks with the ip: 550-5.7.26 [104.47.13.56]. To best protect our users from spam and phishing, 550-5.7.26 the message has been blocked. Please visit 550-5.7.26 https://support.google.com/mail/answer/81126#authentication for more 550 5.7.26 information. r20-20020a05640251d400b0045d4b7ad162si6801981edd.546 - gsmtp'
Original message headers:
Received: from AM7P189MB0759.EURP189.PROD.OUTLOOK.COM (2603:10a6:20b:112::22)
by PR3P189MB1017.EURP189.PROD.OUTLOOK.COM (2603:10a6:102:49::19) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5746.28; Wed, 26 Oct
2022 17:46:59 +0000
Resent-From: <yurelw(a)outlook.com>
Received: from AM7P189MB0759.EURP189.PROD.OUTLOOK.COM ([::1]) by
AM7P189MB0759.EURP189.PROD.OUTLOOK.COM ([fe80::55cb:31af:f4b8:4802%7]) with
Microsoft SMTP Server id 15.20.5746.026; Wed, 26 Oct 2022 17:46:59 +0000
Authentication-Results: spf=softfail (sender IP is 205.220.165.146)
smtp.mailfrom=lists.fedoraproject.org; dkim=none (message not signed)
header.d=none;dmarc=fail action=none header.from=gmx.net;
Received-SPF: SoftFail (protection.outlook.com: domain of transitioning
lists.fedoraproject.org discourages use of 205.220.165.146 as permitted
sender)
X-IncomingTopHeaderMarker: OriginalChecksum:5F996FCD486CB9A5DDC47F972D9B274246B5922993F5A04FD24DDE6016C7FBA6;UpperCasedChecksum:98B9C064274D738DF1836C2DE295FF7A3BECD580157A142003FD238176733849;SizeAsReceived:8269;Count:50
Authentication-Results-Original: ppops.net; spf=pass
smtp.mailfrom=users-bounces(a)lists.fedoraproject.org
DKIM-Filter: OpenDKIM Filter v2.11.0 bastion01.iad2.fedoraproject.org 34842309A1BC
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
mailman01.iad2.fedoraproject.org
X-Spam-Level:
X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE
autolearn=disabled version=3.4.0
X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a
Date: Wed, 26 Oct 2022 19:46:03 +0200
From: Wolfgang Pfeiffer <roto(a)gmx.net>
To: Community support for Fedora users <users(a)lists.fedoraproject.org>
Subject: Re: Mailing lists and Discourse
Message-ID: <Y1lyW5vQH38/PuKq@localhost>
References: <cf58117ae2537939313425e20d1e782174551b8f.camel(a)gmail.com>
<cone.1666658660.788601.74631.1004(a)monster.email-scan.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <cone.1666658660.788601.74631.1004(a)monster.email-scan.com>
User-Agent: Mutt/2.1.5 (2021-12-30)
X-Provags-ID: V03:K1:9i1HzSehIxgsFHqIVzO2mpUH4B9K7b0QnEYEiU7URgdhSDf2X9h
g1fqP+oGWslID5hT+fny4KXifcqELWaTUlk0I3jS51vW08esUCcrgopgXXOkKutRlsYcjuI
FOMPb86JNAKy+XVatM0CeA5oEfhcRlgDZMeTu4yLutB64szWFTxq5YuiEvOzvLrcUF8/1g8
5p1ChPJCbltDiOeKiUgfg==
UI-OutboundReport: notjunk:1;M01:P0:KdSpR1RrdTo=;xRC5Z9PZSnzq7+mEMXcKufwJnlx
a1v1z20iBrAwuXW5ibmsyJmX5sgwEVSIh01uffICDM4nLnHxk1ne41+0A/LTTkehFzuXMlZlk
6BC8r3S1Q4mnq0qGhis7zieLyTbtYLXVDA0crajBEP8Q8PO81/A8mp9Uk0lOdATYcoqvKWIbb
iX0spn53kY9bGrsqGZOEQ4Wq6S6S2gS5Amx426nCBY7BiGrgxQnkhPHN4RQJJgnAFBVKGVBxH
u78V2sqkrMxiTDr+wkXw6x9fbgtUjPD4aW8lq6BZYQyIYIt0gSRsQ6/calTyJc3s76jEXKVSd
Yq3y0cAabmNxVwi8pbq181yLQ3RiOST1f8Ve8/YEf6SQ1XzrHZTvVUq5XjX5nDG0dBQw09pGU
xnf7Opy3mNcP9pkpvAhpNgyQKVkQTQUOoP3b/b7bw62dpn5DiE01C0CcKVWAD2CdZNUV8wug3
dNmNyVu906Nslp/NfqoxMLoeZRpPajY4iNjTswZKux85/liL35qGujpY1rELHNCgpTEzTpH+o
r9XbeXWkIX5tV+hF3USQtIV5y8dmvYnHd0yuL8grwd4ldd5tHKDXzcq98eMAelKklLvxPMkc4
K7MYu3fAzh4DignsfKaOs3ugS0KF+JGF20XLMHtf55UNWwB3Ci+qHO9+lfTMNlISKA9caN+5j
p1wsdbpeGN4zycI6SfMqZPgI5PvPmO/GimxJ01eea6wzDraVX4Ge0P7HrrSr4ahXqwzBTsPEj
baWBn1+hcc2OA3hZsrG6Z4s1FL7YrWRM5Rs4/OolW8micEA1dJhombZKymB15JF9GroQwLrbc
lXjTw7Pgmp6xw4bBdHZ9FAUnPbgmhpf4Xo2iamKK+SSv/WRCPuUv5kMKJHsAKvdFn8Ek5HK1Q
TyoI5Ix9OCdbTChXuvZ/WA23wHS8WNdMQIdcQA9V6HRclSTQcT+qPWeSS6ERKXSrAJmRoqqof
22oRFi31AuboEmXhtHepDlCzyIs=
Message-ID-Hash: GKCG5AXR4DQWAVNOHFBJLNIHEV6GSTTC
X-Message-ID-Hash: GKCG5AXR4DQWAVNOHFBJLNIHEV6GSTTC
X-MailFrom: roto(a)gmx.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-config-1; header-match-config-2; header-match-config-3; header-match-users.lists.fedoraproject.org-0; header-match-users.lists.fedoraproject.org-1; header-match-users.lists.fedoraproject.org-2; header-match-users.lists.fedoraproject.org-3; header-match-users.lists.fedoraproject.org-4; header-match-users.lists.fedoraproject.org-5; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header
X-Mailman-Version: 3.1.1
Precedence: list
Reply-To: Community support for Fedora users <users(a)lists.fedoraproject.org>
List-Id: Community support for Fedora users <users.lists.fedoraproject.org>
Archived-At: <https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.o...>
List-Archive: <https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/>
List-Help: <mailto:users-request@lists.fedoraproject.org?subject=help>
List-Post: <mailto:users@lists.fedoraproject.org>
List-Subscribe: <mailto:users-join@lists.fedoraproject.org>
List-Unsubscribe: <mailto:users-leave@lists.fedoraproject.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: base64
X-Proofpoint-GUID: NeBoWrY21wJ00SsHX8ZudHSgL2fSLCu1
X-Proofpoint-ORIG-GUID: NeBoWrY21wJ00SsHX8ZudHSgL2fSLCu1
X-CLX-Response: 1TFkXGx4ZEQpMehccGhEKWUQXa1N9f1N6bVJhf3sRClhYF2UBaHhyHGN5WEt bEQp4ThdiYUtZZBNCUB5/HREKeEsXZQFoeHIcY3lYS1sRCnhMF2F6YxMaYxkaaWxMEQp5TBdkZV lHb3NyHkgccBEKQ0gXBxgTExEKQ1kXBx4cHREKQ0kXGgQaGhoRCllNF2dmchEKWUkXGnEaEBp3B
hlxGBodEBsTHncGGBoGGxgaEQpZXhdobmYRCklGF19FTF1HS1leT1h1QkVZXk9OEQpJRxdrRl4R CkNOF2RPaEV9WHMYG11gGhp5WWJyEnBfTmJ5TWYYTHlmaV8bEQpYXBcfBBoEGB0ZBRsaBBsaGgQ bGR4EGR4QGx4aHxoRCl5ZF0tAUklYEQpNXBccGxgRCkxaF2xtUk1dEQpNThdoEQpMRhdva2tvXm
tuEQpCTxdnTRN9YE1aQUVtXBEKQ1oXGBsYBBgYHQQbHQQYGxEKQl4XGxEKWUUXExEKRUkXGxEKR WYXHhEKQkYXa1N9f1N6bVJhf3sRCkJHF2dOSRxHTltHekZjEQpCRRdlZW5DGB9pflocWxEKQk4X YV19XGhOTXBLTnoRCkJMF2tiflNtAVN5WX1vEQpCbBdobxNbG3BdG1IbXBEKQkAXY1N6ZBkaRXN
gbl4RCkJYF2NwY0RhaE5lZWRvEQpaWBceEQp5QxdmGhJ9HFgTbG9ccxEKWUsXEh0YGBEKcGcXa1 xSe2xwHl1DWGsQGBgRCnBoF2NFQElzZlpnQUVhEBoRCnBoF2hrZx9Jf2lNa0NaEBoRCnBoF2lEa WhJZ3JfQENiEBoRCnBoF2dBTx5Fa0BjUkVrEBoRCnBoF2hHUkRcSEN7Ek5PEBoRCnBoF2QSQgFz
bkJTRVlrEBoRCnBoF2FQfxpASVoZQGQTEB4aEQpwaBdvGWN+eEQeQ3JOYRAeGhEKcH0XYnISZBl +fl5hYFIQGhEKcGcXem5pckZib1AeQHMQGBgRCnB9F28cBU9HQm1bcG5BEBsaGxEKcH0XYFxMRl sYHFlLZXgQGxobEQpwZxdrck9heXxBYhxdEhAYGBEKcH0XbE1BGBhQfh0abkwQHRoRCnB/F2dOB
Whcb0hua3N7EBMYEQpwXxdiQV1dbHtTH3xDZRAaEQpwfxdkHkdoZ0VQXltTQBASHREKcF8XYkkT fkxEWVBoXgEQGxobEQpwXxdpYkYZQGJhTh1IchAbGhsRCnBfF2lHWB5/b3ABRnNTEBgYEQpwbBd hbmBTEnxPZkJgWxAaEQpwQxdoTx5HbEN9SX8aSBAaEQptfhcaEQpYTRdLESA=
X-CLX-Shades: MLX
X-Proofpoint-Virus-Version: vendor=baseguard
engine=ICAP:2.0.205,Aquarius:18.0.895,Hydra:6.0.545,FMLib:17.11.122.1
definitions=2022-10-26_07,2022-10-26_01,2022-06-22_01
X-Proofpoint-Spam-Details: rule=in_ext_notspam policy=in_ext score=0 bulkscore=0 unknownsenderscore=20
spamscore=0 lowpriorityscore=0 mlxlogscore=999 suspectscore=0
impostorscore=0 priorityscore=60 mlxscore=0 adultscore=0 phishscore=0
malwarescore=0 clxscore=143 classifier=spam adjust=0 reason=mlx
scancount=1 engine=8.12.0-2209130000 definitions=main-2210260100
domainage_hfrom=8722
X-IncomingHeaderCount: 50
Return-Path: roto(a)gmx.net
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic:
BN8NAM04FT038:EE_|GV1P189MB2148:EE_|AM7P189MB0759:EE_|PR3P189MB1017:EE_
X-MS-UserLastLogonTime: 10/26/2022 5:31:45 PM
X-MS-Office365-Filtering-Correlation-Id: 36ef44af-0bcf-47d6-2f48-08dab77a13c2
X-MS-Exchange-EOPDirect: true
X-Sender-IP: 205.220.165.146
X-SID-PRA: ROTO(a)GMX.NET
X-SID-Result: NONE
X-MS-Exchange-AtpMessageProperties: SA|SL
X-Microsoft-Antispam: BCL:0;
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 26 Oct 2022 17:46:56.9389
(UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 36ef44af-0bcf-47d6-2f48-08dab77a13c2
X-MS-Exchange-CrossTenant-Id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-CrossTenant-AuthSource: BN8NAM04FT038.eop-NAM04.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-FromEntityHeader: Internet
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-Transport-CrossTenantHeadersStamped: GV1P189MB2148
X-MS-Exchange-Transport-EndToEndLatency: 00:00:01.8242613
X-MS-Exchange-Processed-By-BccFoldering: 15.20.5746.026
X-MS-Exchange-Inbox-Rules-Loop: yurelw(a)outlook.com
X-OriginatorOrg: sct-15-20-4734-24-msonline-outlook-c54b5.templateTenant
Reporting-MTA: dns;PR3P189MB1017.EURP189.PROD.OUTLOOK.COM
Received-From-MTA: dns;AM7P189MB0759.EURP189.PROD.OUTLOOK.COM
Arrival-Date: Wed, 26 Oct 2022 17:46:59 +0000
Final-Recipient: rfc822;y.antoniowatson(a)gmail.com
Action: failed
Status: 5.7.26
Diagnostic-Code: smtp;550-5.7.26 The MAIL FROM domain [gmx.net] has an SPF record with a hard fail
550-5.7.26 policy (-all) but it fails to pass SPF checks with the ip:
550-5.7.26 [104.47.13.56]. To best protect our users from spam and phishing,
550-5.7.26 the message has been blocked. Please visit
550-5.7.26 https://support.google.com/mail/answer/81126#authentication for more
550 5.7.26 information. r20-20020a05640251d400b0045d4b7ad162si6801981edd.546 - gsmtp
Date: Wed, 26 Oct 2022 19:46:03 +0200
From: Wolfgang Pfeiffer <roto(a)gmx.net>
Subject: Re: Mailing lists and Discourse
Reply-To: Community support for Fedora users <users(a)lists.fedoraproject.org>
To: Community support for Fedora users <users(a)lists.fedoraproject.org>
User-Agent: Mutt/2.1.5 (2021-12-30)
On Mon, Oct 24, 2022 at 08:44:20PM -0400, Sam Varshavchik wrote:
>
> I've been observing, from the sidelines, the devolution of mailing
> lists, Usenet, and IRC into web-based discussion forums of various
> flavors; getting the bar lowered to the level of Twooter, Spacebook,
> and TokTik, and more of the same. It takes more mental effort and
> discipline to participate meaningfully in the former, but much less in
> the latter. It's a much lower barrier of entry; hence this latest
> episode with Gnome.
>
Nailed it: Twooter, Spacebook, TokTik.
Devolution - whatever you call it - in the West seems to be a fact in
many fields. Whereas intellectually and when it comes to patents
Asians are getting a lot better over the last years. 2021 more than
50% of patent filings [*] came from Asia (China 25.1%, Japan 18.1%,
Republic of Korea 7.5%), USA 21.5% and Germany 6.2% - this is a total
reverse from the numbers of 1994: US were No.1, Germany #2, Japan #4,
Korea #18, China #21.
But yes: Let's all be happy with a few butttons to press.
"Press Green" > "Say yes" > "Now Go away"
Wolfgang
[*] https://www.wipo.int/edocs/pctndocs/en/2022/pct_news_2022_02.pdf
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
----- End forwarded message -----
1 year, 7 months
- 10
- 26
Nouveau Blacklisting not in /etc/default/grub
by Stephen Morris
Hi,
Having secureboot in the bios set to "Windows Mode" I have manually
signed the nvidia drivers after uninstalling akmod-nvidia and
kmod-nvidia and all the associated packages.
I then:
generated a signing key using kmodgenca
ran mokutil to import the generated key
rebooted
And at the MOK Manager interface I enrolled the key and
rebooted again
Then once in KDE I reinstalled akmod-nvidia and kmod-nvidia
I then ran lsmod | grep -i nvidia
Does the following display from lsmod indicate that the
nvidia module has not installed properly? I don't have the drm module
and the blacklisting of nouveau and the nvidia modeset parameter have
not been added to the kernel parameters in /etc/default/grub, or is it
that I did not force a rebuild of the kernel module and I did not force
an update of the boot image?
lsmod | grep -i nvidia
nvidia_drm 73728 32
nvidia_modeset 1187840 65 nvidia_drm
nvidia_uvm 1318912 0
nvidia 55242752 2950 nvidia_uvm,nvidia_modeset
regards,
Steve
1 year, 7 months
- 7
- 16
grub2 Question
by Robert McBroom
Running Fedora 35 and trying to fix installed boot files on a third drive.
~]# grub2-install /dev/sdc
grub2-install: error: this utility cannot be used for EFI platforms
because it does not support UEFI Secure Boot.
Secure Boot is turned off in the bios. The boot is from UEFI.
1 year, 7 months
- 5
- 7
New kernel install had issues. (6.0.5-200.fc36.x86_64)
by Doug H.
I do dnf upgrade any morning where something shows up as new. Today was
the big kernel jump to 6.x kernel. Was not worried I guess since I just
ran the update like normal and rebooted to it.
Ended up at:
error: ../../grub-core/kern/dl.c:429:symbol `grub_debug_is_enabled' not
found.
Entering rescue mode...
gruub rescue> _
Booted to the F36 install media and did the rescue option. It found my
system and setup my chroot. I simply ran:
chroot /mnt/sysroot
grub2-install /dev/sda
(no errors)
exit
And rebooted to that. All seems great.
Note that this is a very "old" system, having been dnf upgraded from
F19 all the way to today. I notice that the grub menu looks a bit
different, so it could be an issue of having an old grub on the disk
that needed an update.
Also note that I am pretty sure I have not rebooted since doing a disk
clone from my laptop (not this system) where I mounted old and new
laptop on this system and did a variety of dd, rsync, grub2-install,
reset UUIDs, etc. If I accidentally touch my sda instead of the sdd and
sde that I was working on then I might have created a bomb that went
off at reboot. I don't *think* that happened but not 100% sure.
Everything seems to be working, so I don't need any help, but wanted to
report this just in case.
--
Doug H.
1 year, 7 months
- 11
- 13