Announcing the creation of a new nightly release validation test event
for Fedora 41 Rawhide 20240726.n.0. Please help run some tests for this
nightly compose if you have time. For more information on nightly
release validation testing, see:
https://fedoraproject.org/wiki/QA:Release_validation_test_plan
Notable package version changes:
anaconda - 20240723.n.0: anaconda-41.25-2.fc41.src, 20240726.n.0: anaconda-41.26-1.fc41.src
Test coverage information for the current release can be seen at:
https://openqa.fedoraproject.org/testcase_stats/41
You can see all results, find testing instructions and image download
locations, and enter results on the Summary page:
https://fedoraproject.org/wiki/Test_Results:Fedora_41_Rawhide_20240726.n.0_Summary
The individual test result pages are:
https://fedoraproject.org/wiki/Test_Results:Fedora_41_Rawhide_20240726.n.0_Installation
https://fedoraproject.org/wiki/Test_Results:Fedora_41_Rawhide_20240726.n.0_Base
https://fedoraproject.org/wiki/Test_Results:Fedora_41_Rawhide_20240726.n.0_Server
https://fedoraproject.org/wiki/Test_Results:Fedora_41_Rawhide_20240726.n.0_Cloud
https://fedoraproject.org/wiki/Test_Results:Fedora_41_Rawhide_20240726.n.0_Desktop
https://fedoraproject.org/wiki/Test_Results:Fedora_41_Rawhide_20240726.n.0_Security_Lab
Thank you for testing!
--
Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer
--
_______________________________________________
test-announce mailing list -- test-announce@lists.fedoraproject.org
To unsubscribe send an email to test-announce-leave@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/test-announce@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Friday, July 26, 2024
Thursday, July 25, 2024
[Test-Announce]Fedora-IoT 41 RC 20240725.1 nightly compose nominated for testing
Announcing the creation of a new nightly release validation test event
for Fedora-IoT 41 RC 20240725.1. Please help run some tests for this
nightly compose if you have time. For more information on nightly
release validation testing, see:
https://fedoraproject.org/wiki/QA:Release_validation_test_plan
Test coverage information for the current release can be seen at:
https://openqa.fedoraproject.org/testcase_stats/41iot
You can see all results, find testing instructions and image download
locations, and enter results on the Summary page:
https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_41_RC_20240725.1_Summary
The individual test result pages are:
https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_41_RC_20240725.1_General
Thank you for testing!
--
Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer
--
_______________________________________________
test-announce mailing list -- test-announce@lists.fedoraproject.org
To unsubscribe send an email to test-announce-leave@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/test-announce@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
for Fedora-IoT 41 RC 20240725.1. Please help run some tests for this
nightly compose if you have time. For more information on nightly
release validation testing, see:
https://fedoraproject.org/wiki/QA:Release_validation_test_plan
Test coverage information for the current release can be seen at:
https://openqa.fedoraproject.org/testcase_stats/41iot
You can see all results, find testing instructions and image download
locations, and enter results on the Summary page:
https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_41_RC_20240725.1_Summary
The individual test result pages are:
https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_41_RC_20240725.1_General
Thank you for testing!
--
Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer
--
_______________________________________________
test-announce mailing list -- test-announce@lists.fedoraproject.org
To unsubscribe send an email to test-announce-leave@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/test-announce@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[fedora-arm] Re: Questions to Fedora on Rock 5B
Hello,
even with the newest updates, neither Audio or graphics are working well:
andreas@rockpi5:~$ inxi -G
Graphics:
Message: No PCI device data found.
Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 24.1.1
compositor: kwin_wayland driver: X: loaded: modesetting gpu: N/A
resolution: 1920x1080
API: EGL v: 1.5 drivers: kms_swrast,swrast
platforms: gbm,wayland,x11,surfaceless,device
API: OpenGL v: 4.5 vendor: mesa v: 24.1.4 renderer: llvmpipe (LLVM 18.1.8
128 bits)
API: Vulkan v: 1.3.283 drivers: N/A surfaces: xcb,xlib,wayland
andreas@rockpi5:~$ inxi -A
Audio:
Message: No device data found.
API: ALSA v: k6.11.0-0.rc0.20240724git786c8248dbd3.12.fc41.aarch64
status: kernel-api
Server-1: PipeWire v: 1.2.1 status: active
andreas@rockpi5:~$ alsaucm -c rk3588-es8316 list _devices
ALSA lib parser.c:2541:(get_by_card_name) no soundcards found...
ALSA lib main.c:1554:(snd_use_case_mgr_open) error: failed to import rk3588-es8316 use case configuration -2
alsaucm: error failed to open sound card rk3588-es8316: No such file or directory
andreas@rockpi5:~$
Am 28.06.24 um 22:32 schrieb Andreas Reschke:
Update:
see below
Am 21.06.24 um 10:46 schrieb Andreas Reschke:
Hello Peter,
thanks for the update. Audio didn't work for me:
root@rockpi5:~# alsaucm -c rk3588-es8316 reset reload set _verb HiFi list _devices set _enadev Headphones set _enadev Headset
ALSA lib parser.c:2541:(get_by_card_name) no soundcards found...
ALSA lib main.c:1554:(snd_use_case_mgr_open) error: failed to import rk3588-es8316 use case configuration -2
alsaucm: error failed to open sound card rk3588-es8316: No such file or directory
root@rockpi5:~# aplay /usr/share/sounds/alsa/Front_Left.wav
Playing WAVE '/usr/share/sounds/alsa/Front_Left.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono
aplay: set_params:1456: Unable to install hw params:
ACCESS: RW_INTERLEAVED
FORMAT: S16_LE
SUBFORMAT: STD
SAMPLE_BITS: 16
FRAME_BITS: 16
CHANNELS: 1
RATE: 48000
PERIOD_TIME: 125000
PERIOD_SIZE: 6000
PERIOD_BYTES: 12000
PERIODS: 4
BUFFER_TIME: 500000
BUFFER_SIZE: 24000
BUFFER_BYTES: 48000
TICK_TIME: [0 0]
root@rockpi5:~#root@rockpi5:~# inxi -A
Audio:
Message: No device data found.
API: ALSA v: k6.10.0-0.rc4.20240618git14d7c92f8df9.39.fc41.aarch64
status: kernel-api
Server-1: PipeWire v: 1.1.83 status: active
root@rockpi5:~#
I'm running KDE (Fedora Linux 41 (Rawhide Prerelease) on my ROCK 5 Model B.
Am 20.06.24 um 17:32 schrieb Peter Robinson:
On Tue, 11 Jun 2024 at 19:43, Andreas Reschke <arm_ml@rirasoft.de> wrote:Hello 1. Audio on this side https://gitlab.collabora.com/hardware-enablement/rockchip-3588/notes-for-rockchip-3588/-/blob/main/mainline-status.md is shows Headphone Jack Playback is enable with 6.4-rc1 What does this mean? I didn't found any soundcard on my device root@rockpi5:~# inxi -A Audio: Message: No device data found. API: ALSA v: k6.10.0-0.rc2.20240607git8a92980606e3.28.fc41.aarch64 status: kernel-api Server-1: PipeWire v: 1.1.82 status: activeRunning the following gives me sound via a headset: alsaucm -c rk3588-es8316 reset reload set _verb HiFi list _devices set _enadev Headphones set _enadev Headset aplay /usr/share/sounds/alsa/Front_Left.wav Can you provide more details of your configuration? Desktop etc. I suspect there's a ucm profile missing to do this automatically. I'll add it to my (very long) todo list to look at some point.There are ucm profiles:
root@rockpi5:~# rpm -ql alsa-ucm-1.2.12-1.fc41.noarch | grep 3588
/usr/share/alsa/ucm2/Rockchip/rk3588-es8316
/usr/share/alsa/ucm2/Rockchip/rk3588-es8316/HiFi.conf
/usr/share/alsa/ucm2/Rockchip/rk3588-es8316/rk3588-es8316.conf
/usr/share/alsa/ucm2/conf.d/rk3588-es8316
/usr/share/alsa/ucm2/conf.d/rk3588-es8316/rk3588-es8316.conf
root@rockpi5:~#root@rockpi5:~# alsaucm -c rk3588-es8316 list _devices
ALSA lib parser.c:2541:(get_by_card_name) no soundcards found...
ALSA lib main.c:1554:(snd_use_case_mgr_open) error: failed to import rk3588-es8316 use case configuration -2
alsaucm: error failed to open sound card rk3588-es8316: No such file or directory
root@rockpi5:~#
It seems for me ALSA didn't load these files, or they didn't work.
root@rockpi5:~# 2. GPU I know the GPU isn't complete at the moment, how to load the kernel driver panthor at boot time ?This is working for me with the Fedora 6.10-rc4 build.Didn't work for me, do I have to update initramfs-6.10.0-0.rc4.20240618git14d7c92f8df9.39.fc41.aarch64.img
Thanks
andreas
-- _______________________________________________ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@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/arm@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[fedora-arm] RK3568 + Panfrost needs clk-scmi.ko on F40 Live iso
Hi,
I'm installing F40 on an Odroid M1 (RK3568) NVMe. After writing
Fedora-Workstation-Live-osb-40-1.14.aarch64.iso [0] to an eMMC card and
booting it I see lots of:
[ 69.233581] panfrost fde60000.gpu: get clock failed -517
[ 69.233617] panfrost fde60000.gpu: clk init failed -517
On RK3568 the Panfrost driver needs the clk-scmi kernel module to be
loaded to be functional. Where to report this?
FWIW: when F40 Live is booted, it says "PRE-RELEASE/TESTING" in the top
right corner and there are no options to select packages nor add a repo
with updates (IIRC this was possible with F40 Live x86_64?)
At the end the installer reports an error that it could not remove
something old EFI related, that the system would not be bootable and
that it's due to a bug. After finishing the installation, U-boot could
not find/boot Fedora on the NVMe. So it's a known issue but is there a fix?
Best,
Patrick
[0]
https://mirrors.hostiserver.com/fedora/fedora/linux/releases/40/Workstation/aarch64/iso/Fedora-Workstation-Live-osb-40-1.14.aarch64.iso
--
_______________________________________________
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-leave@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/arm@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
I'm installing F40 on an Odroid M1 (RK3568) NVMe. After writing
Fedora-Workstation-Live-osb-40-1.14.aarch64.iso [0] to an eMMC card and
booting it I see lots of:
[ 69.233581] panfrost fde60000.gpu: get clock failed -517
[ 69.233617] panfrost fde60000.gpu: clk init failed -517
On RK3568 the Panfrost driver needs the clk-scmi kernel module to be
loaded to be functional. Where to report this?
FWIW: when F40 Live is booted, it says "PRE-RELEASE/TESTING" in the top
right corner and there are no options to select packages nor add a repo
with updates (IIRC this was possible with F40 Live x86_64?)
At the end the installer reports an error that it could not remove
something old EFI related, that the system would not be bootable and
that it's due to a bug. After finishing the installation, U-boot could
not find/boot Fedora on the NVMe. So it's a known issue but is there a fix?
Best,
Patrick
[0]
https://mirrors.hostiserver.com/fedora/fedora/linux/releases/40/Workstation/aarch64/iso/Fedora-Workstation-Live-osb-40-1.14.aarch64.iso
--
_______________________________________________
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-leave@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/arm@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Wednesday, July 24, 2024
[389-users] Re: How do we set lastLoginHistorySize?
FYI, I've worked this out;
dn: cn=config,cn=Account Policy Plugin,cn=plugins,cn=config
changetype: modify
add: lastLoginHistorySize
lastLoginHistorySize: 0
modifying entry "cn=config,cn=Account Policy Plugin,cn=plugins,cn=config"
changetype: modify
add: lastLoginHistorySize
lastLoginHistorySize: 0
modifying entry "cn=config,cn=Account Policy Plugin,cn=plugins,cn=config"
Unsure what I was doing wrong last night. Let's just call it sleep deprivation!
Regards,
Grant
On 25/7/24 07:02, Grant Byers wrote:
Hi Pierre,
On 24/7/24 23:54, Pierre Rogier wrote:
Hi Grant,
I think that you can disable the password history feature by using:
dsconf instance_name pwpolicy set --pwdhistory off
Password history and last login history are separate things though, right? We do need to maintain password history for our password policy (rotation, can't use last x passwords, etc.)
From what I was reading, the lastLoginHistory attribute was something that was added recently (well, about 12 months ago) to satisfy a RFE. See https://github.com/389ds/389-ds-base/issues/5752
Thanks,
Grant
Similarly, to change the history size, you can try:
dsconf instance_name pwpolicy set --pwdhistorycount 0
Regards,
Pierre
On Wed, Jul 24, 2024 at 2:23 PM Grant Byers <Grant.Byers@aarnet.edu.au> wrote:
Hi,
We've recently migrated our multi-supplier, multi-consumer 389 infra
from 2.0.x to 2.2.9. The migration was relatively painless, but our logs
are currently flooded with messages like the following;
[24/Jul/2024:11:10:10.499567264 +0000] - ERR - acct_update_login_history
- Modify error 20 on entry 'uid=xxxxx,ou=people,dc=example,dc=net'
[24/Jul/2024:11:10:10.696468976 +0000] - ERR - attrlist_replace -
attr_replace (lastLoginHistory, 20240724111004Z) failed.
There's a bug report for this that matches ours[1], and the issue
appears to have been addressed. It doesn't appear to have been addressed
in 2.2.9 however, which is the latest version available in the copr
repo[2] that effectively replaced epel8-modular.
We have the AccountPolicy plugin enabled only to record lastLoginTime (a
requirement from our security team), so we can't just disable it. We
also use password policy, so we chain binds from consumers to suppliers.
I've seen mention that the lastLoginHistory attribute can be disabled by
setting lastLoginHistorySize to 0. I can't find any documentation on
this anywhere though. I've tried setting it in the AccountPolicyPlugin
config & also directly in cn=config, unsuccessfully.
What are our options?
Thanks,
Grant
[1] https://github.com/389ds/389-ds-base/issues/5834
[2] https://copr.fedorainfracloud.org/coprs/g/389ds/389-directory-server/
--
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@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/389-users@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
--
--
389 Directory Server Development Team
[389-users] Re: How do we set lastLoginHistorySize?
Hi Pierre,
On 24/7/24 23:54, Pierre Rogier wrote:
Hi Grant,
I think that you can disable the password history feature by using:
dsconf instance_name pwpolicy set --pwdhistory off
Password history and last login history are separate things though, right? We do need to maintain password history for our password policy (rotation, can't use last x passwords, etc.)
From what I was reading, the lastLoginHistory attribute was something that was added recently (well, about 12 months ago) to satisfy a RFE. See https://github.com/389ds/389-ds-base/issues/5752
Thanks,
Grant
Similarly, to change the history size, you can try:
dsconf instance_name pwpolicy set --pwdhistorycount 0
Regards,
Pierre
On Wed, Jul 24, 2024 at 2:23 PM Grant Byers <Grant.Byers@aarnet.edu.au> wrote:
Hi,
We've recently migrated our multi-supplier, multi-consumer 389 infra
from 2.0.x to 2.2.9. The migration was relatively painless, but our logs
are currently flooded with messages like the following;
[24/Jul/2024:11:10:10.499567264 +0000] - ERR - acct_update_login_history
- Modify error 20 on entry 'uid=xxxxx,ou=people,dc=example,dc=net'
[24/Jul/2024:11:10:10.696468976 +0000] - ERR - attrlist_replace -
attr_replace (lastLoginHistory, 20240724111004Z) failed.
There's a bug report for this that matches ours[1], and the issue
appears to have been addressed. It doesn't appear to have been addressed
in 2.2.9 however, which is the latest version available in the copr
repo[2] that effectively replaced epel8-modular.
We have the AccountPolicy plugin enabled only to record lastLoginTime (a
requirement from our security team), so we can't just disable it. We
also use password policy, so we chain binds from consumers to suppliers.
I've seen mention that the lastLoginHistory attribute can be disabled by
setting lastLoginHistorySize to 0. I can't find any documentation on
this anywhere though. I've tried setting it in the AccountPolicyPlugin
config & also directly in cn=config, unsuccessfully.
What are our options?
Thanks,
Grant
[1] https://github.com/389ds/389-ds-base/issues/5834
[2] https://copr.fedorainfracloud.org/coprs/g/389ds/389-directory-server/
--
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@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/389-users@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
--
--
389 Directory Server Development Team
[389-users] Re: How do we set lastLoginHistorySize?
Hi Grant,
I think that you can disable the password history feature by using:
dsconf instance_name pwpolicy set --pwdhistory off
Similarly, to change the history size, you can try:
dsconf instance_name pwpolicy set --pwdhistorycount 0
Regards,
Pierre
I think that you can disable the password history feature by using:
dsconf instance_name pwpolicy set --pwdhistory off
Similarly, to change the history size, you can try:
dsconf instance_name pwpolicy set --pwdhistorycount 0
Regards,
Pierre
On Wed, Jul 24, 2024 at 2:23 PM Grant Byers <Grant.Byers@aarnet.edu.au> wrote:
Hi,
We've recently migrated our multi-supplier, multi-consumer 389 infra
from 2.0.x to 2.2.9. The migration was relatively painless, but our logs
are currently flooded with messages like the following;
[24/Jul/2024:11:10:10.499567264 +0000] - ERR - acct_update_login_history
- Modify error 20 on entry 'uid=xxxxx,ou=people,dc=example,dc=net'
[24/Jul/2024:11:10:10.696468976 +0000] - ERR - attrlist_replace -
attr_replace (lastLoginHistory, 20240724111004Z) failed.
There's a bug report for this that matches ours[1], and the issue
appears to have been addressed. It doesn't appear to have been addressed
in 2.2.9 however, which is the latest version available in the copr
repo[2] that effectively replaced epel8-modular.
We have the AccountPolicy plugin enabled only to record lastLoginTime (a
requirement from our security team), so we can't just disable it. We
also use password policy, so we chain binds from consumers to suppliers.
I've seen mention that the lastLoginHistory attribute can be disabled by
setting lastLoginHistorySize to 0. I can't find any documentation on
this anywhere though. I've tried setting it in the AccountPolicyPlugin
config & also directly in cn=config, unsuccessfully.
What are our options?
Thanks,
Grant
[1] https://github.com/389ds/389-ds-base/issues/5834
[2] https://copr.fedorainfracloud.org/coprs/g/389ds/389-directory-server/
--
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@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/389-users@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
--
389 Directory Server Development Team
389 Directory Server Development Team
Subscribe to:
Posts (Atom)