F31RC1.9 install fails on Ryzen 7 3800X if file system encryption is enabled
by Eric Smith
I have a new Ryzen 7 3800X system, and since Fedora 30 won't install on
that, I tried Fedora 31 RC1.9 Workstation Live. That boots up fine, but
when I try to install to my "disk" (M.2 NVMe), if file system encryption is
enabled, it hangs at "Creating luks on /dev/nvme0n1p6". I let it sit there
for 20 minutes with no progress made.
If I install with file system encryption disabled, it installs fine.
Maybe this is more fallout from the RDRAND problem?
4 years, 7 months
Re: Please read over my upgrade notes
by ToddAndMargo
On 10/30/19 8:36 AM, Doug H. wrote:
> On Tue, 2019-10-29 at 22:37 -0700, ToddAndMargo via users wrote:
>> Hi All,
>>
>> This is my upgrade notes for upgrading from FC29 to FC30.
>> Has anything changed I need to update my notes?
>> Well, except for "--releasever=31".
>>
>>
>> FC 29 -->> FC 30:
>>
>> # rpm --rebuilddb
>> # rpm -Va --nofiles --nodigest
>> if anything is too new, do a
>> # dnf downgrade offender(s)
>>
>> # dnf --enablerepo=* update --refresh
>> # dnf install python3-dnf-plugin-system-upgrade
>> # dnf system-upgrade download --refresh --releasever=30 --
>> allowerasing
>> --best
>> # dnf clean packages <-- optional
>> # dnf system-upgrade reboot
>
>
> Or maybe just a note to always check:
>
> https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/
>
> Note that it only suggests the rpm rebuild *after* the upgrade. But I
> guess it does not hurt to run it before hand to avoid issues.
I check that first. It is not always inclusive of things that
can go wrong, such as the rpm -Va thing.
This is what I have so far:
FC 30 -->> FC 31:
https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/
# rpm --rebuilddb
# rpm -Va --nofiles --nodigest
if anything is too new, do a
# dnf downgrade offender(s)
# dnf --enablerepo=* update --refresh
# dnf install python3-dnf-plugin-system-upgrade
# dnf system-upgrade download --refresh --releasever=31 --allowerasing
--best
# rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-31-primary
# dnf clean packages <-- optional
# dnf system-upgrade reboot
4 years, 7 months
Please read over my upgrade notes
by ToddAndMargo
Hi All,
This is my upgrade notes for upgrading from FC29 to FC30.
Has anything changed I need to update my notes?
Well, except for "--releasever=31".
FC 29 -->> FC 30:
# rpm --rebuilddb
# rpm -Va --nofiles --nodigest
if anything is too new, do a
# dnf downgrade offender(s)
# dnf --enablerepo=* update --refresh
# dnf install python3-dnf-plugin-system-upgrade
# dnf system-upgrade download --refresh --releasever=30 --allowerasing
--best
# dnf clean packages <-- optional
# dnf system-upgrade reboot
Many thanks,
-T
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Computers are like air conditioners.
They malfunction when you open windows
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
4 years, 7 months
WiFi now disabled by radio killswitch
by Paolo Galtieri
Folks,
several months ago I was getting the following error:
WiFi now disabled by radio killswitch
forcing a reboot to get my wifi back. Then the problem went away, but
now it's back. Every time I close the lid of my laptop and then reopen
it several minutes later the wifi is dead and requires a reboot to fix.
The problem has happened while running. This is really annoying.
Is this a hardware issue or software?
Any idea what I can do to get around this issue?
I'm running f29.
4 years, 7 months
How to protect 2 kernels from upgrades?
by Tony Nelson
When DNF upgrades the kernel packages, it removes kernels so that
there are not more than installonly_limit installed. It won't
remove the running kernel.
How do I protect more than the running kernel from DNF during
a kernel upgrade? I have two that I would like to keep. Neither
excludepkgs nor protected_packages have any effect on DNF's
autoremove, though they do prevent normal operations.
4 years, 7 months
Re: Removing old kernels attempts to remove more than kernels...
by George R Goffe
Stan,
Thank you for your response... it's DEFINITELY appreciated.
A little misunderstanding here though. I could have been more explicit in the description of my problem. I have seen this situation before (and written bug reports on it). This situation looks like a packaging(?) problem. I once tried this kind of thing and dnf came back with > 800 (maybe 1400) packages to remove... including rpm and dnf et. al.... NOT GOOD. It's good that dnf asks if it's ok to proceed. Whew. Bullet dodged.
So... I'm not trying to back out to fc31... all my kernels are f32. You DO bring out an interesting possibility though. If the newer f32 kernels depend on different "things" than the older f32 kernel I want to keep... there would be a big problem. Sigh. I haven't seen anything like that though. Yay!
The "real" situation is that I have frozen this system's kernel at an older version because of problems with the newer kernels going crazy... reporting apparent stalling on cpus (excessive disablement maybe). I thought I had a broken cpu but went back to the oldest kernel and the messages went away. I haven't written a bug on this mainly because I haven't had much luck with reporting kernel bugs. This current effort was the beginning of an effort to get the most current kernel and see if the problem persists... and then report the bug... if that's what it is. Just talking with you has given me an idea though. I could change the # of kernels to retain, install the latest kernel, test for messages, write a bug if the problem still appears... AND I'd still have my latest kernel. I'll give that a try.
So... THANKS for your help It was GOOD "talking" with you,
George...
On Thursday, October 24, 2019, 12:24:20 PM PDT, stan <xrnu(a)q.com> wrote:
On Thu, 24 Oct 2019 18:12:22 +0000 (UTC)
George R Goffe via users <users(a)lists.fedoraproject.org> wrote:
> Hi,
>
> I am attempting to remove old kernels from my system but "dnf erase
> <kernel-package>" wants to remove much more than just that kernel
> package. I wrote a bug at bugzilla.redhat.com but have gotten
> nowhere. This is the bug URL: 1761024 – removing old kernels wants to
> remove more than kernel packages
This is really a question for the test list, since you are using
rawhide. That alone makes diagnosing the problem difficult, since
there can be incompatibilities because of new version and process
introduction in rawhide. The rule for running rawhide is, 'if it
breaks, you get to keep the pieces', though it is rare that developers
don't fix things to avoid that drastic an outcome. And they do need
people like you running it and reporting problems so they can be fixed
before rawhide becomes a release candidate. That said, early in the
rawhide cycle, like now, when F31 hasn't even been released, things can
be a little chaotic.
>
> 1761024 – removing old kernels wants to remove more than kernel
> packages
>
>
>
> I want to keep the oldest kernel and remove the "newer" kernels.
At a guess, I think this is the source of your problem. You are trying
to remove f32 kernels, and return to an f31 kernel. There is probably
some link between packages compiled under the new regime (newer gcc?,
newer glibc?) than in f31, so it has to remove all those packages in
order to be compatible.
You could try letting the removals complete, keeping track of the
packages removed, and then installing them after f32 is purged, from
the f31 repositories. Alternatively, you could force a return to f31 by
manually installing the fedora-release\* and fedora-repo packages for
f31 and running a
dnf distrosync
to remove / replace anything newer than f31.
4 years, 7 months
Removing old kernels attempts to remove more than kernels...
by George R Goffe
Hi,
I am attempting to remove old kernels from my system but "dnf erase <kernel-package>" wants to remove much more than just that kernel package. I wrote a bug at bugzilla.redhat.com but have gotten nowhere. This is the bug URL: 1761024 – removing old kernels wants to remove more than kernel packages
1761024 – removing old kernels wants to remove more than kernel packages
I want to keep the oldest kernel and remove the "newer" kernels. I don't want to just use "rpm --nodeps -e". That has gotten me into trouble in the past. I think that confuses dnf and then things just go downhill from there. rpm -Va --nofiles --nodigest starts producing error messages about dependencies missing.
Here's a partial list of packages that dnf wants to remove:
Removing dependent packages:
ImageMagick-c++-devel x86_64 1:6.9.10.67-1.fc32 @rawhide 401 k
ImageMagick-devel x86_64 1:6.9.10.67-1.fc32 @rawhide 499 k
OpenEXR-devel x86_64 2.3.0-4.fc31 @rawhide 563 k
alien noarch 8.95-11.fc31 @rawhide 218 k
annobin x86_64 8.81-1.fc32 @rawhide 189 k
arts-devel x86_64 8:1.5.10-44.fc31 @rawhide 1.5 M
clang x86_64 9.0.0-1.fc32 @rawhide 1.6 M
debhelper noarch 12.6.1-1.fc32 @rawhide 1.3 M
dh-autoreconf noarch 19-6.fc31 @rawhide 19 k
Any/all help/hints/tips/suggestions will be appreciated.
Thanks,
George...
4 years, 7 months
Random module?
by John M. Harris Jr
I installed `fish` with `dnf install fish`, but somehow I ended up getting a
module? Anyone know what's going on there?
--
John M. Harris, Jr.
Splentity
4 years, 7 months
Laser printers that work out of the box
by Sam Varshavchik
My printer's is on its last legs. I'm having some trouble finding a printer
that's currently widely available on sale (US) and which appears as
"works perfectly" on http://www.openprinting.org/printers/
I did find some Lexmark model, but when I check up on the replacement toner
cartridges, they're priced in the $200 range (!). Apparently Lexmark uses a
lockout chip on their toner cartridges, so you can use only OEM replacement
toners.
Has anyone gotten a laser printer recently, which worked out of the box
without any fiddling, or downloading any blobs?
4 years, 7 months
ansbile-freeipa client install
by Andrew Meyer
Hello I have setup ansible to use install freeipa client on my CentOS 7/8 machines. I am able to get the packages installed however when it goes through the configuration I am getting the following:
TASK [ipaclient : Install - Ensure that IPA client packages are installed] ******************************************************************************************************************************************************************
ok: [10.150.10.15]
TASK [ipaclient : Install - Set ipaclient_servers] ******************************************************************************************************************************************************************************************
skipping: [10.150.10.15]
TASK [ipaclient : Install - Set ipaclient_servers from cluster inventory] *******************************************************************************************************************************************************************
skipping: [10.150.10.15]
TASK [ipaclient : Install - Check that either principal or keytab is set] *******************************************************************************************************************************************************************
skipping: [10.150.10.15]
TASK [ipaclient : Install - Set default principal if no keytab is given] ********************************************************************************************************************************************************************
ok: [10.150.10.15]
TASK [ipaclient : Install - IPA client test] ************************************************************************************************************************************************************************************************
ok: [10.150.10.15]
TASK [ipaclient : Install - Cleanup leftover ccache] ****************************************************************************************************************************************************************************************
ok: [10.150.10.15]
TASK [ipaclient : Install - Configure NTP] **************************************************************************************************************************************************************************************************
changed: [10.150.10.15]
TASK [ipaclient : Install - Disable One-Time Password for on_master] ************************************************************************************************************************************************************************
skipping: [10.150.10.15]
TASK [ipaclient : Install - Test if IPA client has working krb5.keytab] *********************************************************************************************************************************************************************
ok: [10.150.10.15]
TASK [ipaclient : Install - Disable One-Time Password for client with working krb5.keytab] **************************************************************************************************************************************************
skipping: [10.150.10.15]
TASK [ipaclient : Install - Keytab or password is required for otp] *************************************************************************************************************************************************************************
skipping: [10.150.10.15]
TASK [ipaclient : Install - Get One-Time Password for client enrollment] ********************************************************************************************************************************************************************
skipping: [10.150.10.15]
TASK [ipaclient : Install - Report error for OTP generation] ********************************************************************************************************************************************************************************
skipping: [10.150.10.15]
TASK [ipaclient : Install - Store the previously obtained OTP] ******************************************************************************************************************************************************************************
skipping: [10.150.10.15]
TASK [ipaclient : Install - Check if principal and keytab are set] **************************************************************************************************************************************************************************
skipping: [10.150.10.15]
TASK [ipaclient : Install - Check if one of password or keytabs are set] ********************************************************************************************************************************************************************
fatal: [10.150.10.15]: FAILED! => {"changed": false, "msg": "At least one of password or keytabs must be specified"}
TASK [ipaclient : Install - Restore original admin password if overwritten by OTP] **********************************************************************************************************************************************************
skipping: [10.150.10.15]
TASK [ipaclient : Cleanup leftover ccache] **************************************************************************************************************************************************************************************************
ok: [10.150.10.15]
PLAY RECAP **********************************************************************************************************************************************************************************************************************************
10.150.10.15 : ok=10 changed=1 unreachable=0 failed=1 skipped=11 rescued=0 ignored=0
I am not sure that I am using the correct variables in ansible-vault for the keytabs:
ipaadmin_password1: password1234
ipadm_password1: password1234
ipaserver_realm1: TEST.EXAMPLE
ipaserver_domain1: test.example
ipaclient_principal1: admin
ipaclient_password1: password1234
Should the variable be 'ipaadmin_principal1:' ? Also should this be the password?
And I want to skip installing the ntp client would this be the correct way to do it?
ansible-playbook --ask-vault-pass --extra-vars 'ansible/passwd.yml' ansible-freeipa/playbooks/install-client.yml --limit=10.150.10.15 --user=user123 -e "ipaclient_no_ntp=no"
4 years, 7 months
