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
Hi again, I was not able to boot this way.
I tried then to do all the stuffs (update to latest 28 ) with a rpi2 and it worked. But when I try to boot this sd card on the rpi3b+ it is not working. I can see the EFI boot + grub menu. Then the screen goes black and nothing more.
How can I try to understand what's going on ?
Thanks Fox
See Peter Robinson's post on March 23, 2018, at 10:42 PM that details how to copy the Raspberry Pi device tree file for the model 3+.
I did it already. I checked the /boot/dtb/broadcom/ directory and I have 2 files
-rw-r--r--. 1 root root 12611 Mar 26 18:10 bcm2837-rpi-3-b.dtb -rw-r--r--. 1 root root 12933 Mar 26 18:10 bcm2837-rpi-3-b-plus.dtb
I am running kernel 4.16.0-0.rc7.git0.1.fc28.aarch64 and Peter was talking about rc6?
I used Fedora-Workstation-28-20180402.n.0.aarch64.raw.xz and can boot successfully on my Raspberry Pi model 3B-plus. I used:
fedora-arm-image-installer --target=rpi3 --media=/dev/sdi --norootpass --resizefs --selinux=off --image=fedora/F28/Fedora-Workstation-28-20180402.n.0.aarch64.raw.xz
to prepare a new SD card, but the root file system was not resized. I had to do that manually. A dtb file for the 3-plus is already in this image, there is no need to do anything about that.
There was some hesitation early in the boot process. (Maybe fsck? Maybe some First Boot procedure timing out, or perhaps some parameter-setting activity - there was something that looked like a text menu but it disappeared before I could read it.) It lasted around two minutes.
After boot, I logged on as root, created a user, enabled sshd, and can now connect to the machine using ssh.
Note that before I booted the system, I changed the default target from graphical to multi-user, in order to avoid gnome-shell troubles:
https://bugzilla.redhat.com/show_bug.cgi?id=1561184
I suspect the wired Ethernet port is not operational (I used a USB Ethernet dongle for my ssh connection.) I have not tried any wi-fi activity.
"dnf upgrade" wqs successful, and updated 60 packages.
There are problems, but a lot is working. Certainly enough to make it reasonable to explore and learn what needs work.
On Tue, Apr 3, 2018 at 5:02 AM, Richard Ryniker ryniker@alum.mit.edu wrote:
I used Fedora-Workstation-28-20180402.n.0.aarch64.raw.xz and can boot successfully on my Raspberry Pi model 3B-plus. I used:
fedora-arm-image-installer --target=rpi3 --media=/dev/sdi --norootpass --resizefs --selinux=off --image=fedora/F28/Fedora-Workstation-28-20180402.n.0.aarch64.raw.xz
Why disable SELinux, there should be no need to do that, is there a particular reason or "just because"?
to prepare a new SD card, but the root file system was not resized. I had to do that manually. A dtb file for the 3-plus is already in this image, there is no need to do anything about that.
Correct, rc7 is now stable and it includes that file, there's been further updates and improvements that will be going out stable soon.
There was some hesitation early in the boot process. (Maybe fsck? Maybe some First Boot procedure timing out, or perhaps some parameter-setting activity - there was something that looked like a text menu but it disappeared before I could read it.) It lasted around two minutes.
When in the boot process? Was it the grub2 menu, that should be the only text menu you get with a Workstation install.
After boot, I logged on as root, created a user, enabled sshd, and can now connect to the machine using ssh.
Note that before I booted the system, I changed the default target from graphical to multi-user, in order to avoid gnome-shell troubles:
So why not just use the minimal image?
https://bugzilla.redhat.com/show_bug.cgi?id=1561184
I suspect the wired Ethernet port is not operational (I used a USB Ethernet dongle for my ssh connection.) I have not tried any wi-fi activity.
I've had reports of this working fine, that said it should be much improved with the 4.16.0-300 or later kernel when that lands including stable MAC address.
There are problems, but a lot is working. Certainly enough to make it reasonable to explore and learn what needs work.
Well the support has just landed, I've also been traveling so not had the time to actually focus on it, we should have it to parity with the original RPi3 in time for GA freeze in a couple of weeks.
Ok guys,
I tried the last image this morning :) I am using the Server one
With fedora-arm-image-installer, there are a few things that are not working ( especially the LVM management, so root is not resized, passwd cannot be erased ...)
I am working on a small hack of the script to managed that :)
I tried then to boot on 2 different rpi3b+ here is what I discovered
1/ it is loading the EFI firmware ("starting EFI application at 010000000 ..." message is printed 2/ "8xx_eth Waiting for PHY auto negociation to complete..." 2.1/ no ethernet cable => printing something ending by "-5" like an infinite loop 2.2/ ethernet cable present => it is OK and grub menu is printed and then kernel linux is loaded, but screen goes black each time but after a lot of time I finally have the configuration menu :)
I configured it, but ethernet was not a success (it is the embedded port). After reboot same issue black screen for a very long time no ethernet
Fox
On Tue, Apr 3, 2018 at 10:17 AM, Pierre-Francois RENARD pfrenard@gmail.com wrote:
Ok guys,
I tried the last image this morning :) I am using the Server one
With fedora-arm-image-installer, there are a few things that are not working ( especially the LVM management, so root is not resized, passwd cannot be erased ...)
As per the documentation you cal also just dd it out and expand the LVM to your liking once it's booted.
https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi#Manual
I am working on a small hack of the script to managed that :)
Pull requests are welcome: https://pagure.io/arm-image-installer
I tried then to boot on 2 different rpi3b+ here is what I discovered
1/ it is loading the EFI firmware ("starting EFI application at 010000000 ..." message is printed
That;s expected, it is booting via EFI for aarch64
2/ "8xx_eth Waiting for PHY auto negociation to complete..." 2.1/ no ethernet cable => printing something ending by "-5" like an infinite loop 2.2/ ethernet cable present => it is OK and grub menu is printed and then kernel linux is loaded, but screen goes black each time but after a lot of time I finally have the configuration menu :)
I configured it, but ethernet was not a success (it is the embedded port). After reboot same issue black screen for a very long time no ethernet
I've had reports of the ethernet working just fine by a few people, I suggest installing this kernel [1] as there's improvements to ethernet, at least static MAC address, else you can wait until it lands in a stable image.
[1] https://koji.fedoraproject.org/koji/buildinfo?buildID=1064791
Why disable SELinux?
It does not provide any significant value for my Raspberry Pi computer intended for use as an embedded system or in a DACS role, where network security is important but a simple (root or user) local privilege scheme is fine. The goals of SELinux are important, but its rocky history suggests there will continue to be problems. I am reluctant to spend resources on SELinux for these Raspberry Pi systems, but will do so for open or multi-user systems.
Actually, the fedora-arm-image-installer "--selinux=off" option configures SELinux to permissive mode, therefore it will still report troubles but not interrupt programs because of them. This seems a good middle ground.
When in the boot process? Was it the grub2 menu
Possibly. I do not know. If you think it useful, I will repeat the experiment and make a video recording of the console. I do not see evidence of the pause in the log files:
http://ryniker.org/Fedora/dmesg03 http://ryniker.org/Fedora/log03
So why not just use the minimal image?
I probobly ought to, but in this case I wanted to try an aarch64 image similar to one that Tomáš Frolík reported caused him difficulty.
I've had reports of this [on board wired Ethernet port] working fine
From the log file, it appears to fail (repeatedly) during appempts to perform a DHCP operation for its default configuration. However, default configuration of the USB Ethernet dongle uses DHCP without any problem. This suggests a hardware setup or driver issue is the culprit.
On Mon, Apr 2, 2018 at 8:46 PM, Pierre-Francois RENARD pfrenard@gmail.com wrote:
Hi again, I was not able to boot this way.
I tried then to do all the stuffs (update to latest 28 ) with a rpi2 and it worked. But when I try to boot this sd card on the rpi3b+ it is not working. I can see the EFI boot + grub menu. Then the screen goes black and nothing more.
HDMI based screen? Serial console? More details please.
I have rebased a bunch of stuff around the support for the 3+, there's not an official Fedora kernel build just yet but you can get a scratch and test it [1]
[1] https://koji.fedoraproject.org/koji/taskinfo?taskID=26121358
-
Peter Robinson -
pfrenard -
Pierre-Francois RENARD
-
Richard Ryniker