arm March 2018

arm@lists.fedoraproject.org

27 participants
30 discussions

aarch64 copr?
by Avi Kivity 13 Jun '18

13 Jun '18

Hello, What are the prospects for getting aarch64 copr? Copr is very useful for bringing bleeding edge Fedora packages to CentOS/RHEL users.

3 3

Raspberry Pi 3+
by Richard Ryniker 16 Apr '18

16 Apr '18

F27 will not boot on the new Model 3+. Green LED blinks 4 times (medium), then 4 times (fast), then repeats. The colored splash screen is displayed. Might this be just a device tree problem? Raspbian journal contains a line: raspberrypi kernel: OF: fdt:Machine model: Raspberry Pi 3 Model B Plus Rev 1.3 Do we just need a bcm2710-rpi-3-b-plus.dtb file in Fedora's /boot filesystem? Has anyone succeeded to boot Fedora on the 3+ Pi?

6 17

what do i have to do to enable spi on fedora 27 on a raspberry pi
by adpdyj+4aw13di0ccx1w＠sharklasers.com 10 Apr '18

10 Apr '18

to quote the fedoraproject wiki on the raspberry pi: Are Device Tree Overlays supported? There's basic support for overlays in u-boot and the linux kernel but an overlay manager isn't yet upstream. There's (sic) Is GPIO supported? GPIO isn't supported well as they need to be mapped with Device Tree overlays. This will be improved in the F-27 cycle, and in Fedora 28. Is SPI supported? Yes, basic SPI is supported. Is I2C supported? Yes, basic I2C is supported. by default, i know that i2c is functional since i added an rtc and added a simple udev rule to make it work, however, spi isn't that simple i have an enc28j60 wired to the gpio in hopes of having a secondary ethernet interface, i know it's wired correctly since i downloaded raspbian and added the appropriate overlay magic to config.txt and it automatically registers as eth1 on fedora, a simple modprobe spidev or modprobe spi-bcm2835{,aux} doesn't seem to populate /dev/ with any spidev* i even grafted all of the fedora kernel patches (https://src.fedoraproject.org/rpms/kernel.git) onto the raspberry pi kernel (https://github.com/raspberrypi/linux.git, rpi-4.15.y), built it (make olddefconfig), installed it, did all that funny mkimage crap, booted off it (raspberries instead of penguins (everything else still worked)), and still no functional spi i think this implies that between raspbian and fedora there's a specific CONFIG_ option in the kernel i need to add, but i don't know what one (ones?) it would be any help would be appreciated ---- Sent using Sharklasers.com Block or report abuse: https://www.sharklasers.com//abuse/?a=QFN5JQEJUKAGxgix9HENcwTVQsCV0cMeyLZF

2 2

[Feedback on aarch64 image]
by pfrenard 09 Apr '18

09 Apr '18

Hello I wanted to try aarch64 image, but I had a small issue. When I used arm-installer, it triggered an error and did not complete, I discovered that vg name is fedora, but this is also the same name for my laptop... Perhaps adding aarch64 on the name could reduce the risk of conflicts "fedora_aarch64", it could also be a release number such as F28 "fedora_F28" or both "fedora_F28_aarch64" :) By the way, probably a stupid question, what are the differences between armhfp and aarch64 builds ? Fox

3 2

[aarch64 - fedora28 - Fedora-Server-28-20180327.n.0.aarch64.raw.xz ]
by pfrenard 03 Apr '18

03 Apr '18

Hello guys I tried the last one : Fedora-Server-28-20180327.n.0.aarch64.raw.xz here are feedbacks it makes sense because aarch64 is based on LVM :) I also had an error on the boot FS that was mounted on /tmp/boot but with IO error with kernel errors such as Mar 31 22:02:58 xps13 kernel: ------------[ cut here ]------------ Mar 31 22:02:58 xps13 kernel: proc_dir_entry 'jbd2/mmcblk0p2-8' already registered Mar 31 22:02:58 xps13 kernel: WARNING: CPU: 1 PID: 31631 at fs/proc/generic.c:330 proc_register+0xb7/0x120 Mar 31 22:02:58 xps13 kernel: Modules linked in: xfs mmc_block thunderbolt nvmem_core nfsv3 rpcsec_gss_krb5 nfsv4 dns_resolver nfs fscache rfcomm fuse ccm xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT Mar 31 22:02:58 xps13 kernel: dell_wmi dell_smbios_wmi wmi_bmof dell_wmi_descriptor intel_wmi_thunderbolt snd_hda_codec_hdmi snd_soc_skl irqbypass crct10dif_pclmul dell_smbios_smm dell_laptop dcdbas crc32_pclmul snd_soc_skl_ipc dell_smbios snd_hda_ext_core ghas Mar 31 22:02:58 xps13 kernel: intel_soc_dts_iosf intel_lpss intel_pch_thermal wmi pinctrl_sunrisepoint tpm_tis intel_vbtn soc_button_array tpm_tis_core pinctrl_intel int3403_thermal tpm intel_hid int340x_thermal_zone int3400_thermal acpi_thermal_rel acpi_pad sp Mar 31 22:02:58 xps13 kernel: CPU: 1 PID: 31631 Comm: pool Tainted: G W OE 4.15.10-300.fc27.x86_64 #1 Mar 31 22:02:58 xps13 kernel: Hardware name: Dell Inc. XPS 13 9360/0T3FTF, BIOS 2.4.2 11/21/2017 Mar 31 22:02:58 xps13 kernel: RIP: 0010:proc_register+0xb7/0x120 Mar 31 22:02:58 xps13 kernel: RSP: 0018:ffffa414c372bc20 EFLAGS: 00010282 Mar 31 22:02:58 xps13 kernel: RAX: 0000000000000000 RBX: ffff90dabdcb2648 RCX: 0000000000000006 Mar 31 22:02:58 xps13 kernel: RDX: 0000000000000007 RSI: 0000000000000082 RDI: ffff90dcfe4968f0 Mar 31 22:02:58 xps13 kernel: RBP: ffff90dcf4138d80 R08: 00000000000005fc R09: 0000000000000004 Mar 31 22:02:58 xps13 kernel: R10: 0000000000000880 R11: 0000000000000001 R12: ffff90dcf4138db8 Mar 31 22:02:58 xps13 kernel: R13: ffff90dc7efd944d R14: ffff90dc7efd93c0 R15: 0000000000000000 Mar 31 22:02:58 xps13 kernel: FS: 00007f7eada7d700(0000) GS:ffff90dcfe480000(0000) knlGS:0000000000000000 Mar 31 22:02:58 xps13 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 31 22:02:58 xps13 kernel: CR2: 00007f7ea400e5e8 CR3: 000000022212e005 CR4: 00000000003606e0 Mar 31 22:02:58 xps13 kernel: Call Trace: Mar 31 22:02:58 xps13 kernel: proc_mkdir_data+0x61/0x90 Mar 31 22:02:58 xps13 kernel: jbd2_stats_proc_init+0x1c/0x50 Mar 31 22:02:58 xps13 kernel: jbd2_journal_init_inode+0x9b/0xc0 Mar 31 22:02:58 xps13 kernel: ext4_fill_super+0x2cff/0x3840 Mar 31 22:02:58 xps13 kernel: ? yield_to+0x111/0x170 Mar 31 22:02:58 xps13 kernel: ? ext4_calculate_overhead+0x490/0x490 Mar 31 22:02:58 xps13 kernel: ? snprintf+0x45/0x70 Mar 31 22:02:58 xps13 kernel: ? ext4_calculate_overhead+0x490/0x490 Mar 31 22:02:58 xps13 kernel: ? mount_bdev+0x173/0x1b0 Mar 31 22:02:58 xps13 kernel: ? ext4_calculate_overhead+0x490/0x490 Mar 31 22:02:58 xps13 kernel: mount_bdev+0x173/0x1b0 Mar 31 22:02:58 xps13 kernel: mount_fs+0x35/0x150 Mar 31 22:02:58 xps13 kernel: vfs_kern_mount.part.22+0x54/0x110 Mar 31 22:02:58 xps13 kernel: do_mount+0x5ba/0xc40 Mar 31 22:02:58 xps13 kernel: ? _copy_from_user+0x37/0x60 Mar 31 22:02:58 xps13 kernel: ? memdup_user+0x4b/0x70 Mar 31 22:02:58 xps13 kernel: SyS_mount+0x80/0xd0 Mar 31 22:02:58 xps13 kernel: do_syscall_64+0x74/0x180 Mar 31 22:02:58 xps13 kernel: entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Mar 31 22:02:58 xps13 kernel: RIP: 0033:0x7f7ec2c9fada Mar 31 22:02:58 xps13 kernel: RSP: 002b:00007f7eada7c2a8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5 Mar 31 22:02:58 xps13 kernel: RAX: ffffffffffffffda RBX: 00007f7ea400aac0 RCX: 00007f7ec2c9fada Mar 31 22:02:58 xps13 kernel: RDX: 00007f7ea4002670 RSI: 00007f7ea4003710 RDI: 00007f7ea40043e0 Mar 31 22:02:58 xps13 kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 00007f7ea400256f Mar 31 22:02:58 xps13 kernel: R10: 00000000c0ed0006 R11: 0000000000000246 R12: 00007f7ea40043e0 Mar 31 22:02:58 xps13 kernel: R13: 00007f7ea4002670 R14: 0000000000000000 R15: 00007f7ec480d184 Mar 31 22:02:58 xps13 kernel: Code: 10 eb df 48 8d 53 b8 4c 89 ee e8 35 fe ff ff 85 c0 78 ea 75 c6 48 8d b5 8d 00 00 00 4c 89 ea 48 c7 c7 f8 47 0b b7 e8 f9 a7 da ff <0f> 0b c6 05 38 84 73 01 00 41 8b 36 48 c7 c7 40 96 2a b7 81 c6 Mar 31 22:02:58 xps13 kernel: ---[ end trace d236e7feb885ddc1 ]--- Mar 31 22:02:58 xps13 kernel: ------------[ cut here ]------------ Mar 31 22:02:58 xps13 kernel: sysfs: cannot create duplicate filename '/fs/ext4/mmcblk0p2' Mar 31 22:02:58 xps13 kernel: WARNING: CPU: 3 PID: 31631 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x51/0x60 Mar 31 22:02:58 xps13 kernel: Modules linked in: xfs mmc_block thunderbolt nvmem_core nfsv3 rpcsec_gss_krb5 nfsv4 dns_resolver nfs fscache rfcomm fuse ccm xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT Mar 31 22:02:58 xps13 kernel: dell_wmi dell_smbios_wmi wmi_bmof dell_wmi_descriptor intel_wmi_thunderbolt snd_hda_codec_hdmi snd_soc_skl irqbypass crct10dif_pclmul dell_smbios_smm dell_laptop dcdbas crc32_pclmul snd_soc_skl_ipc dell_smbios snd_hda_ext_core ghas Mar 31 22:02:58 xps13 kernel: intel_soc_dts_iosf intel_lpss intel_pch_thermal wmi pinctrl_sunrisepoint tpm_tis intel_vbtn soc_button_array tpm_tis_core pinctrl_intel int3403_thermal tpm intel_hid int340x_thermal_zone int3400_thermal acpi_thermal_rel acpi_pad sp Mar 31 22:02:58 xps13 kernel: CPU: 3 PID: 31631 Comm: pool Tainted: G W OE 4.15.10-300.fc27.x86_64 #1 Mar 31 22:02:58 xps13 kernel: Hardware name: Dell Inc. XPS 13 9360/0T3FTF, BIOS 2.4.2 11/21/2017 Mar 31 22:02:58 xps13 kernel: RIP: 0010:sysfs_warn_dup+0x51/0x60 Mar 31 22:02:58 xps13 kernel: RSP: 0018:ffffa414c372bb78 EFLAGS: 00010286 Mar 31 22:02:58 xps13 kernel: RAX: 0000000000000000 RBX: ffff90dccce80000 RCX: 0000000000000006 Mar 31 22:02:58 xps13 kernel: RDX: 0000000000000007 RSI: 0000000000000092 RDI: ffff90dcfe5968f0 Mar 31 22:02:58 xps13 kernel: RBP: ffff90dbf0087b20 R08: 000000000000062b R09: 0000000000000004 Mar 31 22:02:58 xps13 kernel: R10: 0000000000000001 R11: 0000000000000001 R12: ffff90dcf0046f68 Mar 31 22:02:58 xps13 kernel: R13: ffff90dcc0e27990 R14: ffff90dc81368190 R15: ffff90dc81368000 Mar 31 22:02:58 xps13 kernel: FS: 00007f7eada7d700(0000) GS:ffff90dcfe580000(0000) knlGS:0000000000000000 Mar 31 22:02:58 xps13 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 31 22:02:58 xps13 kernel: CR2: 0000562b0dd2f348 CR3: 000000022212e003 CR4: 00000000003606e0 Mar 31 22:02:58 xps13 kernel: Call Trace: Mar 31 22:02:58 xps13 kernel: sysfs_create_dir_ns+0x70/0x80 Mar 31 22:02:58 xps13 kernel: kobject_add_internal+0xa8/0x2e0 Mar 31 22:02:58 xps13 kernel: kobject_init_and_add+0x6f/0xb0 Mar 31 22:02:58 xps13 kernel: ? _cond_resched+0x15/0x40 Mar 31 22:02:58 xps13 kernel: ? __kmalloc_node+0x209/0x2b0 Mar 31 22:02:58 xps13 kernel: ext4_register_sysfs+0x6b/0xf0 Mar 31 22:02:58 xps13 kernel: ext4_fill_super+0x23a9/0x3840 Mar 31 22:02:58 xps13 kernel: ? yield_to+0x111/0x170 Mar 31 22:02:58 xps13 kernel: ? ext4_calculate_overhead+0x490/0x490 Mar 31 22:02:58 xps13 kernel: ? snprintf+0x45/0x70 Mar 31 22:02:58 xps13 kernel: ? ext4_calculate_overhead+0x490/0x490 Mar 31 22:02:58 xps13 kernel: ? mount_bdev+0x173/0x1b0 Mar 31 22:02:58 xps13 kernel: ? ext4_calculate_overhead+0x490/0x490 Mar 31 22:02:58 xps13 kernel: mount_bdev+0x173/0x1b0 Mar 31 22:02:58 xps13 kernel: mount_fs+0x35/0x150 Mar 31 22:02:58 xps13 kernel: vfs_kern_mount.part.22+0x54/0x110 Mar 31 22:02:58 xps13 kernel: do_mount+0x5ba/0xc40 Mar 31 22:02:58 xps13 kernel: ? _copy_from_user+0x37/0x60 Mar 31 22:02:58 xps13 kernel: ? memdup_user+0x4b/0x70 Mar 31 22:02:58 xps13 kernel: SyS_mount+0x80/0xd0 Mar 31 22:02:58 xps13 kernel: do_syscall_64+0x74/0x180 Mar 31 22:02:58 xps13 kernel: entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Mar 31 22:02:58 xps13 kernel: RIP: 0033:0x7f7ec2c9fada Mar 31 22:02:58 xps13 kernel: RSP: 002b:00007f7eada7c2a8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5 Mar 31 22:02:58 xps13 kernel: RAX: ffffffffffffffda RBX: 00007f7ea400aac0 RCX: 00007f7ec2c9fada Mar 31 22:02:58 xps13 kernel: RDX: 00007f7ea4002670 RSI: 00007f7ea4003710 RDI: 00007f7ea40043e0 Mar 31 22:02:58 xps13 kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 00007f7ea400256f Mar 31 22:02:58 xps13 kernel: R10: 00000000c0ed0006 R11: 0000000000000246 R12: 00007f7ea40043e0 Mar 31 22:02:58 xps13 kernel: R13: 00007f7ea4002670 R14: 0000000000000000 R15: 00007f7ec480d184 Mar 31 22:02:58 xps13 kernel: Code: 85 c0 48 89 c3 74 12 b9 00 10 00 00 48 89 c2 31 f6 4c 89 e7 e8 c1 c9 ff ff 48 89 ea 48 89 de 48 c7 c7 f8 54 0b b7 e8 5f ca d9 ff <0f> 0b 48 89 df 5b 5d 41 5c e9 d1 3f f4 ff 90 0f 1f 44 00 00 41 Mar 31 22:02:58 xps13 kernel: ---[ end trace d236e7feb885ddc2 ]--- I umounted it, eject sd card and reinserted it. It was correctly mounted then. I also add a label to this fs. Then I changed the vg name from fedora to fedora_aarch64 so it can co exists on my system where I have allready a fedora vg. I also changed the /etc/fstab to match the new name of the vg. Finally tried to follow arm-image-installer script but at the end script is modifying /boot/extlinux/extlinux.conf that is not present. I have now 2 issues 1/ the system is trying to activate old swap /dev/fedora-swap and has a timeout 2/ I reached "Target Basic System" but I have a lot of "dracut-initqueue[530] timeout" ending with message "Could not boot" + "Virtual Console Started" + "Starting dracut Emergency Shell" and nothing more Thanks for your help Fox

4 9

Fwd: [Pki-users] SAN for Launch page.
by Rafael Leiva-Ochoa 30 Mar '18

30 Mar '18

sending to alias also... ---------- Forwarded message ---------- From: Rafael Leiva-Ochoa <spawn(a)rloteck.net> Date: Thu, Mar 29, 2018 at 3:35 PM Subject: Re: [Pki-users] SAN for Launch page. To: Marc Sauton <msauton(a)redhat.com> It did not work. I am still getting SAN errors when using the Launch page. I viewed the Cert that was issued to the launch page, and it is still missing the SAN. Here is my ca.cfg: [CA] pki_admin_email=caadmin(a)test.com pki_admin_name=caadmin pki_admin_nickname=caadmin pki_admin_password=xxxxxxxx pki_admin_uid=caadmin pki_san_inject=True pki_san_for_server_cert=dogtag-ca-root.test.com pki_client_database_password=xxxxxxxx pki_client_database_purge=False pki_client_pkcs12_password=xxxxxxxxxx pki_ds_base_dn=dc=test,dc=com pki_ds_database=pki-tomcat pki_ds_password=xxxxxxx pki_ca_signing_subject_dn=cn=TEST Root CA,ou=TEST Certification Authority,c=US Thanks, Rafael On Thu, Mar 29, 2018 at 2:50 PM, Rafael Leiva-Ochoa <spawn(a)rloteck.net> wrote: > Thanks, I will give that a try. > > On Thu, Mar 29, 2018 at 12:57 PM, Marc Sauton <msauton(a)redhat.com> wrote: > >> Try to add to the pkispawn config file, for example: >> pki_san_inject=True >> pki_san_for_server_cert=ca01.example.com,ca02.example.com,ca.example.com >> >> Note for the "non-internal" certificates, there is a way to modify >> enrollment profiles to add a SAN, but a recent updated feature is described >> in the page at >> http://www.dogtagpki.org/wiki/PKI_10.4_Copy_CN_To_SAN >> >> Thanks, >> M. >> >> On Thu, Mar 29, 2018 at 11:42 AM, Rafael Leiva-Ochoa <spawn(a)rloteck.net> >> wrote: >> >>> Hi Everyone, >>> >>> I am trying to build a new CA, and I am using the ca.cfg file to >>> create the CA, but when I create the CA, the SAN is missing from the >>> website cert (:8443). I am trying to look for the right value to put on the >>> ca.cfg file for the SAN, so the the launch page does not give me SAN >>> errors. Here is what I found, but nothing relating to the SAN: >>> >>> [CA] >>> pki_admin_email=caadmin(a)example.com >>> pki_admin_name=caadmin >>> pki_admin_nickname=caadmin >>> pki_admin_password=Secret.123 >>> pki_admin_uid=caadmin >>> >>> pki_client_database_password=Secret.123 >>> pki_client_database_purge=False >>> pki_client_pkcs12_password=Secret.123 >>> >>> pki_ds_base_dn=dc=ca,dc=pki,dc=example,dc=com >>> pki_ds_database=ca >>> pki_ds_password=Secret.123 >>> >>> pki_security_domain_name=EXAMPLE >>> >>> Any ideas? >>> >>> Rafael >>> >>> _______________________________________________ >>> Pki-users mailing list >>> Pki-users(a)redhat.com >>> https://www.redhat.com/mailman/listinfo/pki-users >>> >> >> >

2 2

Re: [Pki-users] SAN for Launch page.
by Rafael Leiva-Ochoa 30 Mar '18

30 Mar '18

Yes, Making this a default will make it much easier. On Fri, Mar 30, 2018 at 8:14 AM Marc Sauton <msauton(a)redhat.com> wrote: > Yes,sorry, I forgot to mention the profile used for the internal SSL > server certificate at configuration needed to be copied > from /usr/share/pki/ca/conf/serverCert.profile.exampleWithSAN > Should we make this a default setting? > Thanks, > M. > > On Thu, Mar 29, 2018 at 10:05 PM, Rafael Leiva-Ochoa <spawn(a)rloteck.net> > wrote: > >> Found the solution here...Thanks again! >> >> https://www.redhat.com/archives/pki-devel/2015-April/msg00077.html >> >> On Thu, Mar 29, 2018 at 8:06 PM, Rafael Leiva-Ochoa <spawn(a)rloteck.net> >> wrote: >> >>> sending to alias also... >>> >>> ---------- Forwarded message ---------- >>> From: Rafael Leiva-Ochoa <spawn(a)rloteck.net> >>> Date: Thu, Mar 29, 2018 at 3:35 PM >>> Subject: Re: [Pki-users] SAN for Launch page. >>> To: Marc Sauton <msauton(a)redhat.com> >>> >>> >>> It did not work. I am still getting SAN errors when using the Launch >>> page. I viewed the Cert that was issued to the launch page, and it is still >>> missing the SAN. Here is my ca.cfg: >>> >>> [CA] >>> >>> pki_admin_email=caadmin(a)test.com >>> >>> pki_admin_name=caadmin >>> >>> pki_admin_nickname=caadmin >>> >>> pki_admin_password=xxxxxxxx >>> >>> pki_admin_uid=caadmin >>> >>> >>> pki_san_inject=True >>> >>> pki_san_for_server_cert=dogtag-ca-root.test.com >>> >>> >>> pki_client_database_password=xxxxxxxx >>> >>> pki_client_database_purge=False >>> >>> pki_client_pkcs12_password=xxxxxxxxxx >>> >>> >>> pki_ds_base_dn=dc=test,dc=com >>> >>> pki_ds_database=pki-tomcat >>> >>> pki_ds_password=xxxxxxx >>> >>> >>> pki_ca_signing_subject_dn=cn=TEST Root CA,ou=TEST Certification >>> Authority,c=US >>> >>> >>> Thanks, >>> >>> Rafael >>> >>> On Thu, Mar 29, 2018 at 2:50 PM, Rafael Leiva-Ochoa <spawn(a)rloteck.net> >>> wrote: >>> >>>> Thanks, I will give that a try. >>>> >>>> On Thu, Mar 29, 2018 at 12:57 PM, Marc Sauton <msauton(a)redhat.com> >>>> wrote: >>>> >>>>> Try to add to the pkispawn config file, for example: >>>>> pki_san_inject=True >>>>> pki_san_for_server_cert=ca01.example.com,ca02.example.com, >>>>> ca.example.com >>>>> >>>>> Note for the "non-internal" certificates, there is a way to modify >>>>> enrollment profiles to add a SAN, but a recent updated feature is described >>>>> in the page at >>>>> http://www.dogtagpki.org/wiki/PKI_10.4_Copy_CN_To_SAN >>>>> >>>>> Thanks, >>>>> M. >>>>> >>>>> On Thu, Mar 29, 2018 at 11:42 AM, Rafael Leiva-Ochoa < >>>>> spawn(a)rloteck.net> wrote: >>>>> >>>>>> Hi Everyone, >>>>>> >>>>>> I am trying to build a new CA, and I am using the ca.cfg file to >>>>>> create the CA, but when I create the CA, the SAN is missing from the >>>>>> website cert (:8443). I am trying to look for the right value to put on the >>>>>> ca.cfg file for the SAN, so the the launch page does not give me SAN >>>>>> errors. Here is what I found, but nothing relating to the SAN: >>>>>> >>>>>> [CA] >>>>>> pki_admin_email=caadmin(a)example.com >>>>>> pki_admin_name=caadmin >>>>>> pki_admin_nickname=caadmin >>>>>> pki_admin_password=Secret.123 >>>>>> pki_admin_uid=caadmin >>>>>> >>>>>> pki_client_database_password=Secret.123 >>>>>> pki_client_database_purge=False >>>>>> pki_client_pkcs12_password=Secret.123 >>>>>> >>>>>> pki_ds_base_dn=dc=ca,dc=pki,dc=example,dc=com >>>>>> pki_ds_database=ca >>>>>> pki_ds_password=Secret.123 >>>>>> >>>>>> pki_security_domain_name=EXAMPLE >>>>>> >>>>>> Any ideas? >>>>>> >>>>>> Rafael >>>>>> >>>>>> _______________________________________________ >>>>>> Pki-users mailing list >>>>>> Pki-users(a)redhat.com >>>>>> https://www.redhat.com/mailman/listinfo/pki-users >>>>>> >>>>> >>>>> >>>> >>> >>> >> >

1 0

Trying to upgrade to Fedora 26, but had power issues
by Rafael Leiva-Ochoa 29 Mar '18

29 Mar '18

I am getting errors on my Rasberry PI 3 after upgrading from Fedora 25 to 26. When I issue the DNF command, I get the following error: Traceback (most recent call last): File "/usr/bin/dnf", line 57, in <module> from dnf.cli import main I followed the following instruction: https://fedoramagazine.org/upgrading-fedora-25-fedora-26/ But, my Pi had some power issues, and the upgrade got interrupted. Is there any way to recover from this without losing my data? Thanks, Rafael

2 2

F28 GNOME graphical login screen not displayed on Raspberry Pi 3.
by Richard Ryniker 27 Mar '18

27 Mar '18

After booting an image such as Fedora-Workstation-armhfp-28-20180324.n.0-sda.raw.xz on a Raspberry Pi model 3, the First Boot process completes, but no graphical login screen appears. The system becomes unresponsive after a graphical pointer arrow is displayed (on top of whatever text was left on the screen from the boot process.) This failure remains even when the installed image is updated to include the latest software from updates-testing as of March 25. This is specific to the GNOME image. Graphical login works for other images, specifically KDE and LXDE. Question 1: Can anyone report success with F28 Raspberry Pi 3 GNOME graphical login? (Perhaps different display hardware makes a difference.) Question 2: Does this problem aflict other armhfp systems, or is this unique to Raspberry Pi hardware? This problem is new in F28. In my experience, up-to-date F27 GNOME systems using Raspberry Pi 3 hardware have no trouble with graphical login.

3 3

[help proposal]
by RENARD Pierre-Francois 27 Mar '18

27 Mar '18

Hello ARM guys, I am new to this mailing list but in a few word I propose you my help to work on the Fedora ARM. Let me introduce myself. I am Unix sysadmin since more than 20 years now, I am currently working as a Principal Storage Engineer for Société Générale in France. I have been playing with Raspberry Pi and Fedora since a few years and especially with PI3B for a few months, I have also 2 Pi3B+ I am currently trying to build a cluster of raspberry pi to host my home infrastructure (such as DNS/dhcpd/reverse proxy/torrent/sickrage .... using iSCSI shared storage from a Synology DS ) Let's say that I am new but I can learn fast. My personal interests in Raspberry PI are - basic installation - cluster from clusterlab.org - storage (no shared or shared LVM based on iSCSI) I am waiting for first 28 beta to test it and make a much feedback as possible. In time I hope I'll be able to do more. Fox (english translation for RENARD)

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm March 2018