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?
On Tue, Mar 20, 2018 at 1:47 AM, Richard Ryniker ryniker@alum.mit.edu wrote:
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.
That's expected.
Might this be just a device tree problem? Raspbian journal contains a line:
No, it's a firmware, u-boot and device tree problem.
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?
Yes, I have support there and it works fine, we'll almost be there for F-28 beta with likely just a small process to get it to boot initially. I'm undecided whether I want to do the related work to get this support into F-27.
Peter
I am a fan Fedora project and Raspberry, too, I have a whole new piece RPi 3+ in the drawer for only a few days. Nevertheless, there is no functional combination RPi 3+ and Fedora. I will be excited when it will be ready to use. Can you here indicate the functional image is released when it will happen? Tom
On Fri, Mar 23, 2018 at 11:28 AM, Tomáš Frolík tomas.frolik2@gmail.com wrote:
I am a fan Fedora project and Raspberry, too, I have a whole new piece RPi 3+ in the drawer for only a few days. Nevertheless, there is no functional combination RPi 3+ and Fedora. I will be excited when it will be ready to use. Can you here indicate the functional image is released when it will happen?
Everything is in Fedora 28+ now.... well almost. The 4.16rc6 kernel has a bootable DT, that's not yet in the F-28 nightly images though due to the beta freeze.
There's all the bits in the firmware/u-boot though. So on a F-28 nightly image if you set a card up as per usual for a Raspberry Pi 3 and then do one other command it'll boot.
Once you've set up the card all you have to do is copy the RPi3 DT to a 3plus DT and it'll do an initial boot. Once it's booted you can then just upgrade the kernel and it'll be fine moving forward.
On ARMv7 basically do the following: cp <BOOT mount point>/dtb-kernel-4.16.0-0.rc4.git0.1.fc28/bcm2837-rpi-3-b.dtb <BOOT mount point>/dtb-kernel-4.16.0-0.rc4.git0.1.fc28/bcm2837-rpi-3-b-plus.dtb
On aarch64: cp <BOOT mount point>/dtb-kernel-4.16.0-0.rc4.git0.1.fc28/broadcom/bcm2837-rpi-3-b.dtb <BOOT mount point>/dtb-kernel-4.16.0-0.rc4.git0.1.fc28/broadcom/bcm2837-rpi-3-b-plus.dtb
Unmount boot and continue as usual.
Once it's running if you update the kernel to rc6 you should be running just fine. One other thing to note is there's some different bits needed for the wifi. I'm going to put all of those, inc the one needed for the original Pi3, into an rpm but I've not had a chance to do that as yet. Give me a day or so and I'll likely get that done.
Peter
Hello Peter,
thank You very much for your quick and exhaustive answer and hint. I spent some time with the issue (to the joy of my wife) but I was not successful. My RPi 3+ is still not booting. Just for recapitulation: - I downloaded Fedora-Server-28-20180323.n.0.aarch64.raw.xz from http://mirror.vutbr.cz/fedora/development/28/Server/aarch64/images/ .There is newer one today evening. - dd copy on SD card - make copy operation mentioned by You above, with result root@wolf > ls -l /tmp/sd2/dtb-4.16.0-0.rc4.git0.1.fc28.aarch64/broadcom total 48 -rw-r--r--. 1 root root 12667 Mar 5 06:50 bcm2837-rpi-3-b.dtb -rw-r--r--. 1 root root 12667 Mar 25 22:28 bcm2837-rpi-3-b-plus.dtb - SD card into RPi 3+ and power on
RPi 3+ reaches during its startup Grub menu, after kernel selection is confirmed blank screen follows and that is all. There has to be something more to do or I made a mistake somewhere.
Tom
Thank you, Peter Robinson, your instructions worked beautifully.
Perhaps this will not work with the aarch64 version used by Tomáš Frolík, but you already explained in an earlier post why there is little reason to use that on a Raspberry Pi.
I used the following to install on a SD card:
fedora-arm-image-installer --image=fedora/F28/Fedora-Workstation-armhfp-28-20180324.n.0-sda.raw.xz --target=rpi3 --media=/dev/sde --norootpass --resizefs --selinux=off
and copied the dtb file to bcm2837-rpi-3-b-plus.dtb as described, and then successfully booted my Raspberry Pi 3B+.
After completion of the first-boot dialog, things pretty much fell apart. I saw the expected pointer on my screen, but the machine stuck before it displayed the graphical login screen. There was no response to my attempt to switch to another terminal with Ctrl-Alt-F4 or Alt-F4.
I mounted my SD card on my regular Fedora workstation, then manually changed the default target to multi-user.target. This worked much better, I could log in and discover the RPi wired Ethernet is not operational.
Bypass this problem with a USB Ethernet dongle (which is automatically configured without any problems), and I can run "dnf upgrade" which mostly succeeds (there is a problem with libvirt-daemon, but that occurs with the RPi 3B also.)
Reboot, and I now have an (except for libvirt-daemon) up-to-date F28 on my Raspberry Pi 3B+.
No graphical login and no wired Ethernet are problems to be solved, but at least there is a path to get a current F28 environment on the 3B+ for those who want to work on this machine.
On Mon, Mar 26, 2018 at 2:56 AM, Richard Ryniker ryniker@alum.mit.edu wrote:
Thank you, Peter Robinson, your instructions worked beautifully.
Perhaps this will not work with the aarch64 version used by Tomáš Frolík, but you already explained in an earlier post why there is little reason to use that on a Raspberry Pi.
It should work in exactly the same way, the only difference on aarch64 is that the DT is in a broadcom sub directory.
I used the following to install on a SD card:
fedora-arm-image-installer --image=fedora/F28/Fedora-Workstation-armhfp-28-20180324.n.0-sda.raw.xz --target=rpi3 --media=/dev/sde --norootpass --resizefs --selinux=off
and copied the dtb file to bcm2837-rpi-3-b-plus.dtb as described, and then successfully booted my Raspberry Pi 3B+.
After completion of the first-boot dialog, things pretty much fell apart. I saw the expected pointer on my screen, but the machine stuck before it displayed the graphical login screen. There was no response to my attempt to switch to another terminal with Ctrl-Alt-F4 or Alt-F4.
I mounted my SD card on my regular Fedora workstation, then manually changed the default target to multi-user.target. This worked much better, I could log in and discover the RPi wired Ethernet is not operational.
Bypass this problem with a USB Ethernet dongle (which is automatically configured without any problems), and I can run "dnf upgrade" which mostly succeeds (there is a problem with libvirt-daemon, but that occurs with the RPi 3B also.)
Reboot, and I now have an (except for libvirt-daemon) up-to-date F28 on my Raspberry Pi 3B+.
No graphical login and no wired Ethernet are problems to be solved, but at least there is a path to get a current F28 environment on the 3B+ for those who want to work on this machine. _______________________________________________ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org
Peter, I would like to as You, whether the onboard-wired-ethernet problem on RPi3+ was solved in current F28 test release (31.3.2018). If not, can You provide any indication when it could be?
On Mon, Apr 2, 2018 at 7:42 PM, Tomáš Frolík tomas.frolik2@gmail.com wrote:
Peter, I would like to as You, whether the onboard-wired-ethernet problem on RPi3+ was solved in current F28 test release (31.3.2018). If not, can You provide any indication when it could be?
I don't know what you mean by "I would like to as You", please note that I provide the support for RPi in my own time as and when I have spare time.
That said I did pull in some patches that should improve a bunch of things on the 3+but they're not in an official build just yet, you can get a scratch kernel [1] and report back whether they improved your situation. There's a couple of patches that might improve the wired lan but I've not currently got access to ethernet to test as I'm currently traveling.
[1] https://koji.fedoraproject.org/koji/taskinfo?taskID=26121358
On 4/2/18 7:05 PM, Peter Robinson wrote:
On Mon, Apr 2, 2018 at 7:42 PM, Tomáš Frolík tomas.frolik2@gmail.com wrote:
Peter, I would like to as You, whether the onboard-wired-ethernet problem on RPi3+ was solved in current F28 test release (31.3.2018). If not, can You provide any indication when it could be?
I don't know what you mean by "I would like to as You", please note that I provide the support for RPi in my own time as and when I have spare time.
That said I did pull in some patches that should improve a bunch of things on the 3+but they're not in an official build just yet, you can get a scratch kernel [1] and report back whether they improved your situation. There's a couple of patches that might improve the wired lan but I've not currently got access to ethernet to test as I'm currently traveling.
[1] https://koji.fedoraproject.org/koji/taskinfo?taskID=26121358
That kernel did fix the "mac address changes every reboot" for me. And yes, the ethernet port does still work. ;) Thanks!
And the ethernet port LEDS ... I seem to have a flashing amber activity LED, and the green LED is off.
-Eric
I followed steps you described above. I've gotten over before but not to the text login prompt as you. First time I was prompted in GUI env. to create account, set password etc. Then the machine was stucked. During 2nd, 3rd... reboot RPi stucks after following lines: [84.352264] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [84.615587] lan78xx 1-1.1.1:1.0 eth0: kevent 4 may have been dropped [84.634601] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [84.932181] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this ...and that was all.
I have no ethernet dongle. LAN cable was disconnected. That is the difference between my and your hardware setup. Maybe it could be the reason.
Probably I will stop to spend time with attempts to boot just developed F28 distribution and will wait for official release, which should be available and hopefully prepared for RPi3+ without manual intervention (based on road map info) at the beginning of May 2018 - it is not so long.
Did you change the default boot target from graphical.target to mult-user.target? That is what I had to do to avoid the problem with graphical login to my RPi.
Of course, without a working network connection, you might feel it is not worth the bother, but my machine boots OK to a text console login without any Ethernet cable connected to it.
Finally, I also succeeded. As hopeless act I tried an image I has never used before (Fedora-KDE-armhfp-28-20180325.n.0-sda.raw.xz). And it works. By mistake I changed /etc/systemd/system/default.target by wrong way, but RPi was able to launch KDE GUI. It is not so spry as on PC but it works. When I have changed default.target link to multi-user, it boots into text mode. Perfect! The only essential thing which is still not working is ethernet. I hope it will be solved in some next releases, without the functionality I can do "nearly nothing" on my RPi. But following the steps on the way to booting RPi 3+ was for me very instructive, I learned a lot of. Thank You both, guys!
At the end, for potential followers, I wrote down all the necessary steps, how to prepare SD card before you insert it into your RPi 3+. It is valid for now, for Fedora versions, which are available nowadays, for some stable versions, which will come in the future, it will be valid no more (I guess0. It is know-how I acquired from the thread.
fedora-arm-image-installer --image=Fedora-KDE-armhfp-28-20180325.n.0-sda.raw.xz --target=rpi3 --media=/dev/mmcblk0 --norootpass --resizefs --selinux=off mount /dev/mmcblk0p2 /tmp/sd2;mount /dev/mmcblk0p4 /tmp/sd4 cp -p /tmp/sd2/dtb-4.16.0-0.rc4.git0.1.fc28.armv7hl
/bcm2837-rpi-3-b.dtb bcm2837-rpi-3-b-plus.dtb /tmp/sd2/dtb-4.16.0-0.rc4.git0.1.fc28.armv7hl /bcm2837-rpi-3-b-plus.dtb
rm -f /tmp/sd4/etc/systemd/system/default.target ln -s /lib/systemd/system/multi-user.target /tmp/sd4/etc/systemd/system/default.target umount /dev/mmcblk0p2;umount /dev/mmcblk0p4
I tried an image I has never used before (Fedora-KDE-armhfp-28-20180325.n.0-sda.raw.xz). And it works.
Good to hear. It seems only gdm (or maybe gnome-shell) is broken (fails to display the graphical login screen.) I just tried the LXDE image Fedora-LXDE-armhfp-28-20180325.n.0-sda.raw.xz and it works fine. The wired Ethernet connection is still broken, but my USB wired Ethernet adapter has no problem.
Peter have you created the wifi RPM yet if to where can it be obtained.
On Wed, Apr 11, 2018 at 3:04 AM, Chris Hall chrisoswaldhall@gmail.com wrote:
Peter have you created the wifi RPM yet if to where can it be obtained.
rpm to what? You've trimmed any context, I deal with literally 100s of rpms a day in all sorts of context so it's kind of useful to have that ;-)
-
Chris Hall -
Eric Sandeen -
Patrick Pichon -
Peter Robinson -
Richard Ryniker -
Tomáš Frolík