kernel test fail submit on second run!
by Cătălin George Feștilă
I have an error on second submit on kernel test :
Test suite complete PASS
Your log file is being submitted...
Traceback (most recent call last):
File "/home/mythcat/kernel-tests/./fedora_submit.py", line 43, in <module>
submitclient.login(
File "/usr/lib/python3.12/site-packages/fedora/client/openidbaseclient.py", line 303, in login
response = openid_login(
^^^^^^^^^^^^^
File "/usr/lib/python3.12/site-packages/fedora/client/openidproxyclient.py", line 138, in openid_login
raise AuthError(output['message'])
fedora.client.AuthError: Invalid request
The following information is not submitted with your log;
it is for informational purposes only.
Vulnerability status:
The first run work well the second not give me that error:
sudo ./runall.sh
sudo ./runall.sh --performance - has that error
configuration is :
# submit=none
# submit=anonymous
submit=authenticated
1 month, 3 weeks
Re: NVIDIA legacy driver installer failure
by Ian Laurie
On 3/31/24 5:05 AM, Robert McBroom wrote:
> akmods fails on all the 6.8.x kernels.
>
> rpm -qa|grep akmod
> akmods-0.5.8-8.fc40.noarch
> akmod-nvidia-470xx-470.223.02-2.fc40.x86_64
Yes but this is an RPM Fusion issue and needs reporting there. Be aware
there is currently no maintainer for this.
Please also note NVIDIA drops support for these legacy drivers September
this year.
My problem is severe... without these drivers for some reason my laptop
cooks itself until it crashes... as if the nouveau drivers use the card
but don't turn on the fans... I wish there were a way of disabling the
card in the BIOS because otherwise I have to ditch my hardware.
I use the term "card" metaphorically, it's not something I can remove.
--
Ian Laurie
FAS: nixuser | IRC: nixuser
TZ: Australia/Sydney
2 months
NVIDIA legacy driver installer failure
by Robert McBroom
akmods fails on all the 6.8.x kernels.
rpm -qa|grep akmod
akmods-0.5.8-8.fc40.noarch
akmod-nvidia-470xx-470.223.02-2.fc40.x86_64
2024/03/30 13:49:13 akmodsbuild: 3656 | const char *nv_firmware_path(
2024/03/30 13:49:13 akmodsbuild: | ^~~~~~~~~~~~~~~~
2024/03/30 13:49:13 akmodsbuild:
/tmp/akmodsbuild.WQUcpM4R/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.2-300.fc40.x86_64/nvidia/nv-acpi.c:644:22:
error: implicit declaration of function ‘acpi_bus_get_device’; did you
mean ‘acpi_is_pnp_device’? [-Wimplicit-function-declaration]
2024/03/30 13:49:13 akmodsbuild: 644 | retVal =
acpi_bus_get_device(nvif_parent_gpu_handle, &device);
2024/03/30 13:49:13 akmodsbuild: | ^~~~~~~~~~~~~~~~~~~
2024/03/30 13:49:13 akmodsbuild: | acpi_is_pnp_device
2024/03/30 13:49:13 akmodsbuild: make[3]: ***
[scripts/Makefile.build:243:
/tmp/akmodsbuild.WQUcpM4R/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.2-300.fc40.x86_64/nvidia/nv-i2c.o]
Error 1
2024/03/30 13:49:13 akmodsbuild: make[3]: ***
[scripts/Makefile.build:243:
/tmp/akmodsbuild.WQUcpM4R/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.2-300.fc40.x86_64/nvidia/nv-acpi.o]
Error 1
2024/03/30 13:49:13 akmodsbuild: make[3]: ***
[scripts/Makefile.build:243:
/tmp/akmodsbuild.WQUcpM4R/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.2-300.fc40.x86_64/nvidia/nv.o]
Error 1
2024/03/30 13:49:13 akmodsbuild:
/tmp/akmodsbuild.WQUcpM4R/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.2-300.fc40.x86_64/nvidia/nv-dma.c:
In function ‘nv_dma_gem_object_unreference_unlocked’:
2024/03/30 13:49:13 akmodsbuild:
/tmp/akmodsbuild.WQUcpM4R/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.2-300.fc40.x86_64/nvidia/nv-dma.c:978:5:
error: implicit declaration of function ‘drm_gem_object_put_unlocked’;
did you mean ‘drm_gem_object_lookup’? [-Wimplicit-function-declaration]
2024/03/30 13:49:13 akmodsbuild: 978 | drm_gem_object_put_unlocked(gem);
2024/03/30 13:49:13 akmodsbuild: | ^~~~~~~~~~~~~~~~~~~~~~~~~~~
2024/03/30 13:49:13 akmodsbuild: | drm_gem_object_lookup
2024/03/30 13:49:13 akmodsbuild: make[3]: ***
[scripts/Makefile.build:243:
/tmp/akmodsbuild.WQUcpM4R/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.2-300.fc40.x86_64/nvidia/nv-dma.o]
Error 1
2024/03/30 13:49:13 akmodsbuild: make[2]: ***
[/usr/src/kernels/6.8.2-300.fc40.x86_64/Makefile:1939:
/tmp/akmodsbuild.WQUcpM4R/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.2-300.fc40.x86_64]
Error 2
2024/03/30 13:49:13 akmodsbuild: make[1]: *** [Makefile:252: __sub-make]
Error 2
2024/03/30 13:49:13 akmodsbuild: make[1]: Leaving directory
'/usr/src/kernels/6.8.2-300.fc40.x86_64'
2024/03/30 13:49:13 akmodsbuild: make: *** [Makefile:80: modules] Error 2
2024/03/30 13:49:13 akmodsbuild: error: Bad exit status from
/var/tmp/rpm-tmp.qdrjr5 (%build)
2024/03/30 13:49:13 akmodsbuild:
2024/03/30 13:49:13 akmodsbuild: RPM build errors:
2024/03/30 13:49:13 akmodsbuild: Bad exit status from
/var/tmp/rpm-tmp.qdrjr5 (%build)
2024/03/30 13:49:13 akmodsbuild:
2024/03/30 13:49:13 akmods: Building rpms failed; see
/var/cache/akmods/nvidia-470xx/470.223.02-2-for-6.8.2-300.fc40.x86_64.failed.log
for details
The installer direct from NVIDIA also fails to complete
# Check that the tmp directory is executable
# Make path absolute if not already
if ! echo "$TMPROOT" | grep -q "^/"; then
TMPROOT=`pwd`/"$TMPROOT";
fi
if [ ! -d "$TMPROOT" ]; then
mkdir -p "$TMPROOT" || {
echo "Unable to create temp directory $TMPROOT"
exit 1
}
fi
TMPDIR="$TMPROOT"
TMPFILE=`mktemp "$TMPDIR/makeself.XXXXXXXX" 2> /dev/null`
if [ "a$TMPFILE" = "a" ]; then
echo "Unable to create temporary file in $TMPDIR"
exit 1
fi
chmod +x "$TMPFILE"
# Try to execute, see what happens
"$TMPFILE" > /dev/null 2>&1 || {
echo "ERROR: Temporary directory $TMPDIR is not executable - use the
" \
"--tmpdir option to specify a different one."
rm "$TMPFILE"
exit 1;
}
ERROR: Temporary directory /tmp is not executable - use the --tmpdir
option to specify a different one.
2 months
YubiKey and GPG observations for Fedora Silverblue 40 beta
by Fraser Tajima
1. YubiKey is still not released by Fedora after boot when the YubiKey is inserted at the time of boot up with the result that `gpg --card-status` fails (a problem from Fedora Silverblue 39). `systemctl restart pcscd' is still needed to get `gpg --card-status` to recognise the YubiKey. Windows does not do this.
2. `~/.gnupg/scdaemon.conf` setup by user in Fedora 39 seems to be gone in Fedora 40? Pinentry errors in Kleopatra are emitted in Fedora 40 even when `gpg --card-status` is fine, requiring re-creation of the `scdaemon.conf` file with the entry 'reader-port Yubico Yubi` and a reboot (after which Kleopatra is back to normal). see (https://support.yubico.com/hc/en-us/articles/360013714479-Troubleshooting...)
Fedora 40 beta is very impressive overall!
2 months, 1 week
toolbox not working after upgrade to 40
by Ian Laurie
I can create containers in toolbox but cannot enter them anymore.
I issued a "podman system reset", followed by "toolbox create" and
"toolbox enter" but I still get "Error: failed to start container
fedora-toolbox-40".
This is the first time trying to enter a container since upgrading from
39 to 40.
I have removed podman and toolbox and all their dependencies, and
reinstalled them in case files/directories were missing but I'm still
getting the same error.
It doesn't look to me like this is a "known" issue in that I can't seem
to find references to this, and there doesn't appear to be a BZ for it.
Not sure if it's random or a consequence of upgrading from 30 to 40.
zuke$ toolbox --verbose enter
DEBU Running as real user ID 1000
DEBU Resolved absolute path to the executable as /usr/bin/toolbox
DEBU Running on a cgroups v2 host
DEBU Looking up sub-GID and sub-UID ranges for user admin
DEBU TOOLBOX_PATH is /usr/bin/toolbox
DEBU Migrating to newer Podman
DEBU Toolbox config directory is /home/admin/.config/toolbox
DEBU Current Podman version is 5.0.0
DEBU Creating runtime directory /run/user/1000/toolbox
DEBU Old Podman version is 5.0.0
DEBU Migration not needed: Podman version 5.0.0 is unchanged
DEBU Setting up configuration
DEBU Setting up configuration: file
/home/admin/.config/containers/toolbox.conf not found
DEBU Resolving container and image names
DEBU Container: ''
DEBU Distribution (CLI): ''
DEBU Image (CLI): ''
DEBU Release (CLI): ''
DEBU Resolved container and image names
DEBU Container: 'fedora-toolbox-40'
DEBU Image: 'fedora-toolbox:40'
DEBU Release: '40'
DEBU Resolving container and image names
DEBU Container: ''
DEBU Distribution (CLI): ''
DEBU Image (CLI): ''
DEBU Release (CLI): ''
DEBU Resolved container and image names
DEBU Container: 'fedora-toolbox-40'
DEBU Image: 'fedora-toolbox:40'
DEBU Release: '40'
DEBU Checking if container fedora-toolbox-40 exists
DEBU Inspecting mounts of container fedora-toolbox-40
DEBU Starting container fedora-toolbox-40
Error: failed to start container fedora-toolbox-40
--
Ian Laurie
FAS: nixuser | IRC: nixuser
TZ: Australia/Sydney
2 months, 1 week
Silverblue 40 testing - just minor issues
by znmeb＠znmeb.net
I've got Silverblue 40 running on my Acer Nitro 5 and there are only minor issues so far. The rebase process was flawless. Issues:
1. For some reason, the WiFi adapter MAC address changed. I haven't dug into the settings so I don't know if there's a default setting to generate random MAC addresses.
2. The "dnf upgrade" on a Fedora 40 distrobox container is erroring:
```
sudo dnf upgrade -y
Last metadata expiration check: 0:10:09 ago on Tue 26 Mar 2024 11:23:24 PM UTC.
Dependencies resolved.
========================================================================================================================
Package Architecture Version Repository Size
========================================================================================================================
Upgrading:
filesystem x86_64 3.18-8.fc40 rawhide 1.1 M
setup noarch 2.14.5-2.fc40 rawhide 155 k
Transaction Summary
========================================================================================================================
Upgrade 2 Packages
Total download size: 1.2 M
Downloading Packages:
(1/2): setup-2.14.5-2.fc40.noarch.rpm 2.9 MB/s | 155 kB 00:00
(2/2): filesystem-3.18-8.fc40.x86_64.rpm 15 MB/s | 1.1 MB 00:00
------------------------------------------------------------------------------------------------------------------------
Total 2.1 MB/s | 1.2 MB 00:00
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Running scriptlet: filesystem-3.18-8.fc40.x86_64 1/1
Preparing : 1/1
Upgrading : setup-2.14.5-2.fc40.noarch 1/4
Error unpacking rpm package setup-2.14.5-2.fc40.noarch
Upgrading : filesystem-3.18-8.fc40.x86_64 2/4
error: unpacking of archive failed on file /etc/host.conf: cpio: chown failed - Device or resource busy
error: setup-2.14.5-2.fc40.noarch: install failed
Error unpacking rpm package filesystem-3.18-8.fc40.x86_64
Failed:
filesystem-3.18-6.fc39.x86_64 filesystem-3.18-8.fc40.x86_64 setup-2.14.5-1.fc40.noarch setup-2.14.5-2.fc40.noarch
Error: Transaction failed
```
2 months, 1 week
