Okay, so, my holiday hobby project is setting up Fedora IoT as a home gateway device. Gonna control some Z-wave devices and Ecobee thermostats and sensors.
I have a Rock960 device as suggested by https://docs.fedoraproject.org/en-US/iot/reference-platforms/.
And I'm following https://docs.fedoraproject.org/en-US/iot/physical-device-setup/ ... where I immediately ran into two problems.
First, there's no link to where to download the image. I know there's website in (slow) development, but in the meantime, shouldn't we link to https://dl.fedoraproject.org/pub/alt/iot/?
Second, despite being listed as a reference platform, there's no "rocks960".
I discovered that the arm-image-installer program actually works *without* target, but that's not at all clear from the docs.
... and then this happened:
= Writing image complete! Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on /dev/sdb1 have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes. Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on /dev/sdb1 have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes. = Resizing /dev/sdb1 .... Checking that no-one is using this disk right now ... FAILED
This disk is currently in use - repartitioning is probably a bad idea. Umount all file systems, and swapoff all swap partitions on this disk. Use the --no-reread flag to suppress this check.
sfdisk: Use the --force flag to overrule all checks. Checking that no-one is using this disk right now ... FAILED
This disk is currently in use - repartitioning is probably a bad idea. Umount all file systems, and swapoff all swap partitions on this disk. Use the --no-reread flag to suppress this check.
sfdisk: Use the --force flag to overrule all checks. Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on /dev/sdb1 have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes. Error: mount /dev/sdb12 /tmp/boot failed
On Sat, Dec 22, 2018 at 02:13:19PM -0500, Matthew Miller wrote:
= Writing image complete! = Resizing /dev/sdb1 ....
Oh wait this is my fault. sdb1 instead of sdb. Let me try that again :)
On Sat, Dec 22, 2018 at 02:06:45PM -0500, Matthew Miller wrote:
I discovered that the arm-image-installer program actually works *without* target, but that's not at all clear from the docs.
.... and despite writing okay, it doesn't actually *boot*. So I guess maybe something special is needed? No idea what, though.
Hi Matthew,
have you tried just dd instead of the arm-installer?
By the way I had the same problems as you, but I haven’t found time to investigate this and was thinking I’m just not proficient enough.
On 22 Dec 2018, at 20:39, Matthew Miller mattdm@fedoraproject.org wrote:
On Sat, Dec 22, 2018 at 02:06:45PM -0500, Matthew Miller wrote:
I discovered that the arm-image-installer program actually works *without* target, but that's not at all clear from the docs.
.... and despite writing okay, it doesn't actually *boot*. So I guess maybe something special is needed? No idea what, though.
-- Matthew Miller mattdm@fedoraproject.org Fedora Project Leader _______________________________________________ IoT mailing list -- iot@lists.fedoraproject.org To unsubscribe send an email to iot-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/iot@lists.fedoraproject.org
On Sat, Dec 22, 2018 at 09:00:34PM +0100, Frank Zimmer wrote:
Hi Matthew, have you tried just dd instead of the arm-installer?
Yes -- same result. I also tried the F29 ARM Minimal image. There must be something special that needs to be done. I notice that the script says:
= Writing image complete! = No U-boot will be written.
... I dunno what I u-boot is and whether this a problem.
By the way I had the same problems as you, but I haven’t found time to investigate this and was thinking I’m just not proficient enough.
Hey, you and me both. :) I think, though, there are just some things which are obvious to the people working on this which need a little figuring out and documenting.
On 22 Dec 2018, at 21:07, Matthew Miller mattdm@fedoraproject.org wrote:
On Sat, Dec 22, 2018 at 09:00:34PM +0100, Frank Zimmer wrote:
Hi Matthew, have you tried just dd instead of the arm-installer?
Yes -- same result. I also tried the F29 ARM Minimal image. There must be something special that needs to be done. I notice that the script says:
= Writing image complete! = No U-boot will be written.
When I tried dd if just went through without any problems, but the image didn’t boot. I tried another card (with Raspbian) to make sure that the newly bought RP3+ works at all. The device booted in with my friend’s card.
... I dunno what I u-boot is and whether this a problem.
By the way I had the same problems as you, but I haven’t found time to investigate this and was thinking I’m just not proficient enough.
Hey, you and me both. :) I think, though, there are just some things which are obvious to the people working on this which need a little figuring out and documenting.
Indeed :-)
-- Matthew Miller mattdm@fedoraproject.org Fedora Project Leader _______________________________________________ IoT mailing list -- iot@lists.fedoraproject.org To unsubscribe send an email to iot-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/iot@lists.fedoraproject.org
On Sat, Dec 22, 2018 at 09:13:09PM +0100, Frank Zimmer wrote:
On Sat, Dec 22, 2018 at 09:00:34PM +0100, Frank Zimmer wrote:
Hi Matthew, have you tried just dd instead of the arm-installer?
Yes -- same result. I also tried the F29 ARM Minimal image. There must be something special that needs to be done. I notice that the script says: = Writing image complete! = No U-boot will be written.
When I tried dd if just went through without any problems, but the image didn’t boot. I tried another card (with Raspbian) to make sure that the newly bought RP3+ works at all. The device booted in with my friend’s card.
Ah, so it sounds like you have a raspberry pi 3? Did you use `--target=rpi3`?
Which image are you using? Be sure to use the F29 aarch64 one, The latest (RC2) is here https://dl.fedoraproject.org/pub/alt/iot/29/IoT/aarch64/images/Fedora-IoT-29... I have personally tested that on a RPI3B+ and RPI3B. When creating the image, I always use the manual way. cat /proc/partitions #figure out which drive it is, for example sdf xzcat Fedora-IoT-29-20181206.0.aarch64.raw.xz | dd status=progress bs=4M of=/dev/sdf # Very important, be sure to do a sync or two before taking out the micro-sd card. sync sync
With that, I've just put the card in my RPI3 and away it goes.
Note: With the rpi3b, there will be a rather long pause with a blank screen while booting up. Be patient. There is still a pause with the rpi3b+, but not nearly as bad. How long? rpi3b+ 15-30 seconds. rpi3b 2-5 minutes. (It's better than the F29 Server edition pause which is ... go make and eat breakfast/lunch and come back)
Sorry I haven't tested on the Rock960, but I don't have one to test on. Troy
On Sat, Dec 22, 2018 at 12:24 PM Frank Zimmer frank.e.zimmer@gmail.com wrote:
Hi Matthew,
Ah, so it sounds like you have a raspberry pi 3? Did you use `--target=rpi3`?
Yes I did. _______________________________________________ IoT mailing list -- iot@lists.fedoraproject.org To unsubscribe send an email to iot-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/iot@lists.fedoraproject.org
On Sat, Dec 22, 2018 at 12:48:24PM -0800, Troy Dawson wrote:
Which image are you using? Be sure to use the F29 aarch64 one, The latest (RC2) is here https://dl.fedoraproject.org/pub/alt/iot/29/IoT/aarch64/images/Fedora-IoT-29...
Yeah, that's the one. Tried with both the arm-image-installer and direct dd as you showed.
With that, I've just put the card in my RPI3 and away it goes. Note: With the rpi3b, there will be a rather long pause with a blank screen while booting up. Be patient. There is still a pause with the rpi3b+, but not nearly as bad. How long? rpi3b+ 15-30 seconds. rpi3b 2-5 minutes. (It's better than the F29 Server edition pause which is ... go make and eat breakfast/lunch and come back)
It's not even trying to boot from the SD card. Instead, it goes right to the Android system pre-installed on the internal storage. It's my understanding that it will prioritize an SD card if one is present. I'll test with a Debian image to see if that is the case.
Sorry I haven't tested on the Rock960, but I don't have one to test on.
Let's fix that! According to the docs, it's supposed to be one of our reference platforms (and in fact Peter told me it was the best option). Order one and I'll make sure you get reimbursed. (This offer probably also applies to anyone else who is involved in Fedora IoT for development, qa, or docs. But I should get council approval before saying yes to too many people. Let me know if you're interested though.)
Hi Matthew, have you tried just dd instead of the arm-installer?
Yes -- same result. I also tried the F29 ARM Minimal image. There must be something special that needs to be done. I notice that the script says:
= Writing image complete! = No U-boot will be written.
... I dunno what I u-boot is and whether this a problem.
By the way I had the same problems as you, but I haven’t found time to investigate this and was thinking I’m just not proficient enough.
Hey, you and me both. :) I think, though, there are just some things which are obvious to the people working on this which need a little figuring out and documenting.
I completely agree, the docs were converted from the wiki and when I did them it was a quick throw something together to get it to a point where people can start to play. We need to get the docs to a point where anyone can get started with docs for Fedora, general Linux, Mac and Windows. I would love assistance from basic feedback to asciidoc pull requests :)
Peter
-
Frank Zimmer -
Matthew Miller -
Peter Robinson -
Troy Dawson