Dear all,
You are kindly invited to the meeting: IoT Working Group weekly meeting on 2018-11-14 from 14:00:00 to 15:00:00 UTC At fedora-meeting@irc.freenode.net
The meeting will be about: Fedora IoT weekly status meeting.
More information available at: [https://pagure.io/fedora-iot/%5D(https://pagure.io/fedora-iot/)
Source: https://apps.fedoraproject.org/calendar/meeting/9245/
Good morning all,
Apologies, there was a miscommunication about the IoT meeting this week and we missed our allotted time in #fedora-meeting.
We wanted to go over the list of blockers for Fedora 29 IoT and to check on testing results. The list currently includes:
1) initial-setup hangs during boot after IoT installation https://bugzilla.redhat.com/show_bug.cgi?id=1646568
2) WARNING at drivers/mmc/bcm2835_sdhost.c:408/bcm2835_send_command()! https://bugzilla.redhat.com/show_bug.cgi?id=1644873
3) ttyAMA ttyAMA0: tty_open: tty->count(2) != (#fd's(1) + #kopen's(0)) https://bugzilla.redhat.com/show_bug.cgi?id=1644884
4) The 35network-legacy is still used even if network-scripts isn't installed in Fedora 29 https://github.com/dracutdevs/dracut/issues/488
It would be great to get some feedback on the most recent composes and any new issues encountered or anything else we may have missed.
Thanks, Paul
----- Original Message -----
Dear all,
You are kindly invited to the meeting: IoT Working Group weekly meeting on 2018-11-14 from 14:00:00 to 15:00:00 UTC At fedora-meeting@irc.freenode.net
The meeting will be about: Fedora IoT weekly status meeting.
More information available at: [https://pagure.io/fedora-iot/%5D(https://pagure.io/fedora-iot/)
Source: https://apps.fedoraproject.org/calendar/meeting/9245/
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
I've tested on VM (x86_64) and RPI3 (aarch64) I used images Fedora-IoT-29-20181114.0.aarch64.raw.xz Fedora-IoT-29-20181114.0.x86_64.raw.xz
Both machines booted up properly and ran me through firstboot to create my user. I was able to login, and use sudo to become root. On Wed, Nov 14, 2018 at 7:24 AM Paul Whalen pwhalen@redhat.com wrote:
Good morning all,
Apologies, there was a miscommunication about the IoT meeting this week and we missed our allotted time in #fedora-meeting.
We wanted to go over the list of blockers for Fedora 29 IoT and to check on testing results. The list currently includes:
- initial-setup hangs during boot after IoT installation https://bugzilla.redhat.com/show_bug.cgi?id=1646568
I'm confused about this one because it looks like it's talking about installing using the normal anaconda installation method. If this is going to be a supported way of installing, then we need to list it as such. But, it booted up for me and didn't get hung on firstboot. So to me this looks good.
- WARNING at drivers/mmc/bcm2835_sdhost.c:408/bcm2835_send_command()! https://bugzilla.redhat.com/show_bug.cgi?id=1644873
I was not getting the BCM stuff during my bootup. Just incase I was missing it I looked with the command journalctl | grep BCM
I was getting some BCM messages, but that was for bluetooth Perhaps it's fixed, but I wasn't seeing the problem to begin with.
- ttyAMA ttyAMA0: tty_open: tty->count(2) != (#fd's(1) + #kopen's(0)) https://bugzilla.redhat.com/show_bug.cgi?id=1644884
Similar to above. It might be fixed, but I wasn't able to see the problem in the first place.
- The 35network-legacy is still used even if network-scripts isn't installed in Fedora 29 https://github.com/dracutdevs/dracut/issues/488
I didn't understand what I was supposed to check with this one.
It would be great to get some feedback on the most recent composes and any new issues encountered or anything else we may have missed.
I haven't gotten beyond "Initial Setup Service" https://docs.fedoraproject.org/en-US/iot/release-criteria/ But thus far, it's been looking good for my two test platforms.
Thanks, Paul
----- Original Message -----
Dear all,
You are kindly invited to the meeting: IoT Working Group weekly meeting on 2018-11-14 from 14:00:00 to 15:00:00 UTC At fedora-meeting@irc.freenode.net
The meeting will be about: Fedora IoT weekly status meeting.
More information available at: [https://pagure.io/fedora-iot/%5D(https://pagure.io/fedora-iot/)
Source: https://apps.fedoraproject.org/calendar/meeting/9245/
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
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
----- Original Message -----
I've tested on VM (x86_64) and RPI3 (aarch64) I used images Fedora-IoT-29-20181114.0.aarch64.raw.xz Fedora-IoT-29-20181114.0.x86_64.raw.xz
Both machines booted up properly and ran me through firstboot to create my user. I was able to login, and use sudo to become root. On Wed, Nov 14, 2018 at 7:24 AM Paul Whalen pwhalen@redhat.com wrote:
Good morning all,
Apologies, there was a miscommunication about the IoT meeting this week and we missed our allotted time in #fedora-meeting.
We wanted to go over the list of blockers for Fedora 29 IoT and to check on testing results. The list currently includes:
- initial-setup hangs during boot after IoT installation https://bugzilla.redhat.com/show_bug.cgi?id=1646568
I'm confused about this one because it looks like it's talking about installing using the normal anaconda installation method. If this is going to be a supported way of installing, then we need to list it as such.
Yes, this is happening when using the ISO and anaconda. It should be listed as a supported installation method, if not we should correct the documentation.
But, it booted up for me and didn't get hung on firstboot. So to me this looks good.
- WARNING at drivers/mmc/bcm2835_sdhost.c:408/bcm2835_send_command()! https://bugzilla.redhat.com/show_bug.cgi?id=1644873
I was not getting the BCM stuff during my bootup. Just incase I was missing it I looked with the command journalctl | grep BCM
I was getting some BCM messages, but that was for bluetooth Perhaps it's fixed, but I wasn't seeing the problem to begin with.
Seems to only happen with some media. Samsung EVO 16G cards are fine for me, but using brands like Adata or Silcon & Power fail. Perhaps we recommend only using certain media?
- ttyAMA ttyAMA0: tty_open: tty->count(2) != (#fd's(1) + #kopen's(0)) https://bugzilla.redhat.com/show_bug.cgi?id=1644884
Similar to above. It might be fixed, but I wasn't able to see the problem in the first place.
This was fixed by removing all consoles from the kernel args. Oddly, in the most recent images we still have 'console=tty0' which causes all output to go to the display and none on serial console (at least on the rpi). The original issue is fixed, but I included it to keep track of the new console issue, apologies for the confusion.
- The 35network-legacy is still used even if network-scripts isn't
installed in Fedora 29 https://github.com/dracutdevs/dracut/issues/488
I didn't understand what I was supposed to check with this one.
Boot fails when no wired network is available.
Thanks for testing! Paul
It would be great to get some feedback on the most recent composes and any new issues encountered or anything else we may have missed.
I haven't gotten beyond "Initial Setup Service" https://docs.fedoraproject.org/en-US/iot/release-criteria/ But thus far, it's been looking good for my two test platforms.
Thanks, Paul
----- Original Message -----
Dear all,
You are kindly invited to the meeting: IoT Working Group weekly meeting on 2018-11-14 from 14:00:00 to 15:00:00 UTC At fedora-meeting@irc.freenode.net
The meeting will be about: Fedora IoT weekly status meeting.
More information available at: [https://pagure.io/fedora-iot/%5D(https://pagure.io/fedora-iot/)
Source: https://apps.fedoraproject.org/calendar/meeting/9245/
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
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
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
NB I have also had problems with Samsung SD cards booting as reported some weeks ago
On Thu, 15 Nov 2018 at 14:43, Paul Whalen pwhalen@redhat.com wrote:
----- Original Message -----
I've tested on VM (x86_64) and RPI3 (aarch64) I used images Fedora-IoT-29-20181114.0.aarch64.raw.xz Fedora-IoT-29-20181114.0.x86_64.raw.xz
Both machines booted up properly and ran me through firstboot to create
my
user. I was able to login, and use sudo to become root. On Wed, Nov 14, 2018 at 7:24 AM Paul Whalen pwhalen@redhat.com wrote:
Good morning all,
Apologies, there was a miscommunication about the IoT meeting this week and we missed our allotted time in #fedora-meeting.
We wanted to go over the list of blockers for Fedora 29 IoT and to
check
on testing results. The list currently includes:
- initial-setup hangs during boot after IoT installation https://bugzilla.redhat.com/show_bug.cgi?id=1646568
I'm confused about this one because it looks like it's talking about installing using the normal anaconda installation method. If this is going to be a supported way of installing, then we need to list it as such.
Yes, this is happening when using the ISO and anaconda. It should be listed as a supported installation method, if not we should correct the documentation.
But, it booted up for me and didn't get hung on firstboot. So to me this looks good.
- WARNING at drivers/mmc/bcm2835_sdhost.c:408/bcm2835_send_command()! https://bugzilla.redhat.com/show_bug.cgi?id=1644873
I was not getting the BCM stuff during my bootup. Just incase I was missing it I looked with the command journalctl | grep BCM
I was getting some BCM messages, but that was for bluetooth Perhaps it's fixed, but I wasn't seeing the problem to begin with.
Seems to only happen with some media. Samsung EVO 16G cards are fine for me, but using brands like Adata or Silcon & Power fail. Perhaps we recommend only using certain media?
- ttyAMA ttyAMA0: tty_open: tty->count(2) != (#fd's(1) + #kopen's(0)) https://bugzilla.redhat.com/show_bug.cgi?id=1644884
Similar to above. It might be fixed, but I wasn't able to see the problem in the first
place.
This was fixed by removing all consoles from the kernel args. Oddly, in the most recent images we still have 'console=tty0' which causes all output to go to the display and none on serial console (at least on the rpi). The original issue is fixed, but I included it to keep track of the new console issue, apologies for the confusion.
- The 35network-legacy is still used even if network-scripts isn't
installed in Fedora 29 https://github.com/dracutdevs/dracut/issues/488
I didn't understand what I was supposed to check with this one.
Boot fails when no wired network is available.
Thanks for testing! Paul
It would be great to get some feedback on the most recent composes and
any
new issues encountered or anything else we may have missed.
I haven't gotten beyond "Initial Setup Service" https://docs.fedoraproject.org/en-US/iot/release-criteria/ But thus far, it's been looking good for my two test platforms.
Thanks, Paul
----- Original Message -----
Dear all,
You are kindly invited to the meeting: IoT Working Group weekly meeting on 2018-11-14 from 14:00:00 to 15:00:00 UTC At fedora-meeting@irc.freenode.net
The meeting will be about: Fedora IoT weekly status meeting.
More information available at: [https://pagure.io/fedora-iot/%5D(https://pagure.io/fedora-iot/)
Source: https://apps.fedoraproject.org/calendar/meeting/9245/
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
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
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
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
I don’t know whether you’d consider it a blocker as it could just be the way that I’m using fedora-iot, but on several rpi3s with different sdcards `rpm-ostree install <blah>` is not reliable: https://u8538325.ct.sendgrid.net/wf/click?upn=0nhH4OIYFtatOO7tDf-2BEy6sS6Gpn... (sorry, format all broken there). More specifically/easier to follow: https://u8538325.ct.sendgrid.net/wf/click?upn=YKnOrpjBkiBX5bFl4-2BXAlIIzCQM2...
As this issue isn’t reported on others’ h/w, it could well be the way that we’re using pi’s. otoh, I think that we’ve got very standard h/w and media.
Also, is it expected that ethernet is plugged in? I accidentally booted yesterday’s latest image on a standalone pi and it dropped back to a dracut shell (no bug filed, yet).
tc
On 14 Nov 2018, at 15:24, Paul Whalen pwhalen@redhat.com wrote:
Good morning all,
Apologies, there was a miscommunication about the IoT meeting this week and we missed our allotted time in #fedora-meeting.
We wanted to go over the list of blockers for Fedora 29 IoT and to check on testing results. The list currently includes:
- initial-setup hangs during boot after IoT installation
https://u8538325.ct.sendgrid.net/wf/click?upn=0nhH4OIYFtatOO7tDf-2BEy6sS6Gpn...
- WARNING at drivers/mmc/bcm2835_sdhost.c:408/bcm2835_send_command()!
https://u8538325.ct.sendgrid.net/wf/click?upn=0nhH4OIYFtatOO7tDf-2BEy6sS6Gpn...
- ttyAMA ttyAMA0: tty_open: tty->count(2) != (#fd's(1) + #kopen's(0))
https://u8538325.ct.sendgrid.net/wf/click?upn=0nhH4OIYFtatOO7tDf-2BEy6sS6Gpn...
- The 35network-legacy is still used even if network-scripts isn't installed in Fedora 29
https://u8538325.ct.sendgrid.net/wf/click?upn=0nhH4OIYFtatOO7tDf-2BEy2v1lDwt...
It would be great to get some feedback on the most recent composes and any new issues encountered or anything else we may have missed.
Thanks, Paul
----- Original Message -----
Dear all,
You are kindly invited to the meeting: IoT Working Group weekly meeting on 2018-11-14 from 14:00:00 to 15:00:00 UTC At fedora-meeting@irc.freenode.net
The meeting will be about: Fedora IoT weekly status meeting.
More information available at: [https://u8538325.ct.sendgrid.net/wf/click?upn=0nhH4OIYFtatOO7tDf-2BEy8fb7wr0...
Source: https://u8538325.ct.sendgrid.net/wf/click?upn=0nhH4OIYFtatOO7tDf-2BEy-2B6bgu...
IoT mailing list -- iot@lists.fedoraproject.org To unsubscribe send an email to iot-leave@lists.fedoraproject.org Fedora Code of Conduct: https://u8538325.ct.sendgrid.net/wf/click?upn=0nhH4OIYFtatOO7tDf-2BEy2SVXKL1... List Guidelines: https://u8538325.ct.sendgrid.net/wf/click?upn=0nhH4OIYFtatOO7tDf-2BEy-2FVKLK... List Archives: https://u8538325.ct.sendgrid.net/wf/click?upn=0nhH4OIYFtatOO7tDf-2BEy8cASbxx...
IoT mailing list -- iot@lists.fedoraproject.org To unsubscribe send an email to iot-leave@lists.fedoraproject.org Fedora Code of Conduct: https://u8538325.ct.sendgrid.net/wf/click?upn=0nhH4OIYFtatOO7tDf-2BEy2SVXKL1... List Guidelines: https://u8538325.ct.sendgrid.net/wf/click?upn=0nhH4OIYFtatOO7tDf-2BEy-2FVKLK... List Archives: https://u8538325.ct.sendgrid.net/wf/click?upn=0nhH4OIYFtatOO7tDf-2BEy8cASbxx...
On Thu, Nov 15, 2018 at 10:58 AM Tim Coote tim+fedoraproject.org@coote.org wrote:
I don’t know whether you’d consider it a blocker as it could just be the way that I’m using fedora-iot, but on several rpi3s with different sdcards `rpm-ostree install <blah>` is not reliable: https://bugzilla.redhat.com/show_bug.cgi?id=1648112 https://u8538325.ct.sendgrid.net/wf/click?upn=0nhH4OIYFtatOO7tDf-2BEy6sS6GpnNqkzV0K0UmYueBh8gVU07vn0caxsIoFZQb-2FewHlmXVkAuKP3X-2FP04RX6ig-3D-3D_F6S8EWobU9vyJEk1cEkDmBVnQaoGj4VAs39boBnGMrujtWm1TENArCgSEOGWeSGlBe53uGUtYaF61o3O3nk-2FsKvaOscC5q00gVbANuQfIzMoFvKf-2FE8ivkzJw9zfLiWWyFIxQhqES3n5LYPKPur-2FWN6nueCH5qJ6fpTwcGn9-2FOixwNi47KEYWrMN0dR0DLzFbkzycNjYjU37rIK4SIh-2Bg85LGih-2BGmTvCLpEYTRk0UU-3D (sorry, format all broken there). More specifically/easier to follow: http://bit.ly/2Da2eYT https://u8538325.ct.sendgrid.net/wf/click?upn=YKnOrpjBkiBX5bFl4-2BXAlIIzCQM20S-2Fw7YhZuNME09g-3D_F6S8EWobU9vyJEk1cEkDmBVnQaoGj4VAs39boBnGMrujtWm1TENArCgSEOGWeSGlBe53uGUtYaF61o3O3nk-2FsHHj6yAdB3Vgr1IEvtkNyggRv7wzf8Dk4tQ33sx7zNgnLrt14rpOw6tAdh8MM9hrF4x0rq7VsqtC4V1ehCTBOH-2BznXh2Y5bGPuYNjQrwF6pUMV7sJbUM16Ko6zH4BtMd4-2BRK6Fld6S5GmXJ7n3S69LY-3D
As this issue isn’t reported on others’ h/w, it could well be the way that we’re using pi’s. otoh, I think that we’ve got very standard h/w and media.
Also, is it expected that ethernet is plugged in? I accidentally booted yesterday’s latest image on a standalone pi and it dropped back to a dracut shell (no bug filed, yet).
That's actually issue 4 below.
tc
On 14 Nov 2018, at 15:24, Paul Whalen pwhalen@redhat.com wrote:
Good morning all,
Apologies, there was a miscommunication about the IoT meeting this week and we missed our allotted time in #fedora-meeting.
We wanted to go over the list of blockers for Fedora 29 IoT and to check on testing results. The list currently includes:
- initial-setup hangs during boot after IoT installation
https://bugzilla.redhat.com/show_bug.cgi?id=1646568
- WARNING at drivers/mmc/bcm2835_sdhost.c:408/bcm2835_send_command()!
https://bugzilla.redhat.com/show_bug.cgi?id=1644873
- ttyAMA ttyAMA0: tty_open: tty->count(2) != (#fd's(1) + #kopen's(0))
https://bugzilla.redhat.com/show_bug.cgi?id=1644884
- The 35network-legacy is still used even if network-scripts isn't
installed in Fedora 29
https://github.com/dracutdevs/dracut/issues/488
It would be great to get some feedback on the most recent composes and any new issues encountered or anything else we may have missed.
Thanks, Paul
----- Original Message -----
Dear all,
You are kindly invited to the meeting:
IoT Working Group weekly meeting on 2018-11-14 from 14:00:00 to 15:00:00 UTC At fedora-meeting@irc.freenode.net
The meeting will be about: Fedora IoT weekly status meeting.
More information available at: [ https://pagure.io/fedora-iot/%5D(https://pagure.io/fedora-iot/) https://u8538325.ct.sendgrid.net/wf/click?upn=0nhH4OIYFtatOO7tDf-2BEy8fb7wr05Z3yyfTZwmYTqdZCDsdZRNW4k4Ec0RzL5hnM0upO-2FScYzoSauT3SE1JaI2o9uz2ltdyOHpTsVlSvxH0-3D_F6S8EWobU9vyJEk1cEkDmBVnQaoGj4VAs39boBnGMrujtWm1TENArCgSEOGWeSGlBe53uGUtYaF61o3O3nk-2FsCbeKFXDTXTycMtHKt3BBjWgiu-2FIBAXk2MNrooSJgBq0BdGO-2FrqOoAiabIDJ-2FmLqSQAMXSDzUxuXPb34oogYjC9H-2FIowWrte1aROtEinsvb6mZfk6OynjaFDbHDCx41u8toewHLNouUu8zJ21lhRve0-3D
Source: https://apps.fedoraproject.org/calendar/meeting/9245/ https://u8538325.ct.sendgrid.net/wf/click?upn=0nhH4OIYFtatOO7tDf-2BEy-2B6bgux-2F9F1BmjgR9GI1ph32VTQJYtCkOt-2Fx1zH-2BrE8OWfMhDT8cWLZxwU43OAaQMQ-3D-3D_F6S8EWobU9vyJEk1cEkDmBVnQaoGj4VAs39boBnGMrujtWm1TENArCgSEOGWeSGlBe53uGUtYaF61o3O3nk-2FsL6PdxZ-2BofCCbN1l2FqLpDjL1dqIrpvYitvnB2WcYLyd8w9ivuTcPP8bhs2G9OzYbFQjMENQRfdDABQ-2BrumhpQ-2BanoGqVVNB-2FfsbK4GuLqi9M3E4gwTWwKKLt2KClLw70NQrZuqC-2F3RY-2F3WuSb61cpI-3D
*____________________________________________*_ 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 https://u8538325.ct.sendgrid.net/wf/click?upn=0nhH4OIYFtatOO7tDf-2BEy2SVXKL1YhbBEcK7H0ydXMO60ZJBy5POEXdDOjGnLHc4Nt4Kh3y6bDWTckEVXt5i1g-3D-3D_F6S8EWobU9vyJEk1cEkDmBVnQaoGj4VAs39boBnGMrujtWm1TENArCgSEOGWeSGlBe53uGUtYaF61o3O3nk-2FsG8f441q2FMnHwv11doSM5dNKiCPqeb-2BP1KFFB1XdrK2-2FHFinZHBVDiiQ1FPOY5sPmt7UwoAmuIJlizHVOdzixujwBa5fYZYK-2F4mpdT-2FFXjD-2BodioOHybF2Qhi47lXu7jF9WeTdFcHgDwgWlDPgGNyM-3D List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines https://u8538325.ct.sendgrid.net/wf/click?upn=0nhH4OIYFtatOO7tDf-2BEy-2FVKLKZwPHMgxOz0OqT2Kd0B-2Bi3OsAU3YX7sY4alWvAntAo6w-2B4zFZOqYr2buaKgAg-3D-3D_F6S8EWobU9vyJEk1cEkDmBVnQaoGj4VAs39boBnGMrujtWm1TENArCgSEOGWeSGlBe53uGUtYaF61o3O3nk-2FsLqll-2F0-2FfVHDZTI5ySyktfov3cJZVG3IIS2BTs4m7-2F6XOUZmAoiYoJ6fv01aiuL6cM9yZst-2BicyY-2FgD6MpFtlO3Vy-2FDQFybZ9vB7Nh2tR-2BEePBrV6QSNN-2F3dW3TGugxAeFAmmY-2FmTnMDB7Xn5pLYyZI-3D List Archives: https://lists.fedoraproject.org/archives/list/iot@lists.fedoraproject.org https://u8538325.ct.sendgrid.net/wf/click?upn=0nhH4OIYFtatOO7tDf-2BEy8cASbxxFR6zHB1gY4RMF-2B-2BFpGNJ9pfl4PsJnBFPsIt9hSq3SISACb303HXMdmctdgGLaaw5I3ffdLnzLgUIMAbAQMVLL9nhhUJDqSSXipBW_F6S8EWobU9vyJEk1cEkDmBVnQaoGj4VAs39boBnGMrujtWm1TENArCgSEOGWeSGlBe53uGUtYaF61o3O3nk-2FsN10c6O1-2BTSfirxwuelNFIJ7ZbfN8758pRce26A2DaWwxfFlv710uZkyoT-2B4EKrTKSRDvZ0P4eun3O3hivJm1CQ0jGEnOl7iWgIZ9-2Fz63ALGjDSJz7jmYhoAvYagcQwkOdPRdBspUF1bsnyScBf2KHk-3D
*____________________________________________*_ 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 https://u8538325.ct.sendgrid.net/wf/click?upn=0nhH4OIYFtatOO7tDf-2BEy2SVXKL1YhbBEcK7H0ydXMO60ZJBy5POEXdDOjGnLHc4Nt4Kh3y6bDWTckEVXt5i1g-3D-3D_F6S8EWobU9vyJEk1cEkDmBVnQaoGj4VAs39boBnGMrujtWm1TENArCgSEOGWeSGlBe53uGUtYaF61o3O3nk-2FsO4NCmEtdPv2P-2FfktWqIGhM7ehk4tKc8N5TE4aiw2eUzNbXbZGqpPc0muGadwJ4OaAQfJ7DiABzFHIhZyFPSoRdv9NrY0geEqeO7rT73x-2B0KO3NbUwwSJYlG1IrLQjL5BFySdFjQ6W-2BjVS2lmfYk2-2Bs-3D List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines https://u8538325.ct.sendgrid.net/wf/click?upn=0nhH4OIYFtatOO7tDf-2BEy-2FVKLKZwPHMgxOz0OqT2Kd0B-2Bi3OsAU3YX7sY4alWvAntAo6w-2B4zFZOqYr2buaKgAg-3D-3D_F6S8EWobU9vyJEk1cEkDmBVnQaoGj4VAs39boBnGMrujtWm1TENArCgSEOGWeSGlBe53uGUtYaF61o3O3nk-2FsAsEk8dAWxin4a-2FMu9ejPM4Ey4zJPn49y2HsX0G9myQgfMz57vv4PtOmNlYRCQ8LVXcpUG0OOMNKuRkltV02gPcDJ-2BSljNEvi9j46GZYlGOWZs7s4-2FK4dwGTdYdwv0mOJOYNDcGiZER1PYsTob5-2FpMs-3D List Archives: https://lists.fedoraproject.org/archives/list/iot@lists.fedoraproject.org https://u8538325.ct.sendgrid.net/wf/click?upn=0nhH4OIYFtatOO7tDf-2BEy8cASbxxFR6zHB1gY4RMF-2B-2BFpGNJ9pfl4PsJnBFPsIt9hSq3SISACb303HXMdmctdgGLaaw5I3ffdLnzLgUIMAbAQMVLL9nhhUJDqSSXipBW_F6S8EWobU9vyJEk1cEkDmBVnQaoGj4VAs39boBnGMrujtWm1TENArCgSEOGWeSGlBe53uGUtYaF61o3O3nk-2FsLzs3xRQoBZFYUN0TQzI30AqTbYpmFBV9MGTpkC3MJqvL3nrKfVcnMoVkvrUwCj5sWtJkcAWzrXYilHDubo7c-2FkjYuN4nZ6-2FXiRJrQIL-2Baza88awOcI6QVX5FlHpE0dX0tQFhj2senj1X9ryBCvNtXA-3D
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
Hi Tim,
----- Original Message -----
I don’t know whether you’d consider it a blocker as it could just be the way that I’m using fedora-iot, but on several rpi3s with different sdcards `rpm-ostree install <blah>` is not reliable: https://bugzilla.redhat.com/show_bug.cgi?id=1648112 (sorry, format all broken there). More specifically/easier to follow: http://bit.ly/2Da2eYT
Thanks, I missed that one. I have only seen it on the Raspberry Pi 3, but does indeed seem like a blocker.
Paul
As this issue isn’t reported on others’ h/w, it could well be the way that we’re using pi’s. otoh, I think that we’ve got very standard h/w and media.
Also, is it expected that ethernet is plugged in? I accidentally booted yesterday’s latest image on a standalone pi and it dropped back to a dracut shell (no bug filed, yet).
tc
On 14 Nov 2018, at 15:24, Paul Whalen pwhalen@redhat.com wrote:
Good morning all,
Apologies, there was a miscommunication about the IoT meeting this week and we missed our allotted time in #fedora-meeting.
We wanted to go over the list of blockers for Fedora 29 IoT and to check on testing results. The list currently includes:
- initial-setup hangs during boot after IoT installation
https://bugzilla.redhat.com/show_bug.cgi?id=1646568
- WARNING at drivers/mmc/bcm2835_sdhost.c:408/bcm2835_send_command()!
https://bugzilla.redhat.com/show_bug.cgi?id=1644873
- ttyAMA ttyAMA0: tty_open: tty->count(2) != (#fd's(1) + #kopen's(0))
https://bugzilla.redhat.com/show_bug.cgi?id=1644884
- The 35network-legacy is still used even if network-scripts isn't installed
in Fedora 29 https://github.com/dracutdevs/dracut/issues/488
It would be great to get some feedback on the most recent composes and any new issues encountered or anything else we may have missed.
Thanks, Paul
----- Original Message -----
Dear all,
You are kindly invited to the meeting: IoT Working Group weekly meeting on 2018-11-14 from 14:00:00 to 15:00:00 UTC At fedora-meeting@irc.freenode.net
The meeting will be about: Fedora IoT weekly status meeting.
More information available at: [ https://pagure.io/fedora-iot/%5D(https://pagure.io/fedora-iot/)
Source: https://apps.fedoraproject.org/calendar/meeting/9245/
____________________________________________ _ 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
____________________________________________ _ 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
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 Wed, Nov 14, 2018 at 4:14 PM Paul Whalen pwhalen@redhat.com wrote:
Good morning all,
Apologies, there was a miscommunication about the IoT meeting this week and we missed our allotted time in #fedora-meeting.
We wanted to go over the list of blockers for Fedora 29 IoT and to check on testing results. The list currently includes:
- initial-setup hangs during boot after IoT installation https://bugzilla.redhat.com/show_bug.cgi?id=1646568
There's a fix pending review of this upstream here: https://github.com/rhinstaller/anaconda/pull/1692
- WARNING at drivers/mmc/bcm2835_sdhost.c:408/bcm2835_send_command()! https://bugzilla.redhat.com/show_bug.cgi?id=1644873
I've not managed to recreate this one, I also believe it's actually closely related to this one which Tim bought up on the thread too. Tim can you confirm that if you see this error it also causes issues with "rpm-ostree install" on the SD cards? There's been a few issues reported upstream around MMC stability on the bcm2835 driver and I wonder if there's something special happening with the way rpm-ostree hits the HW that is making this more likely to trigger. I also wonder if it's improved with v4.19.x kernel.
https://bugzilla.redhat.com/show_bug.cgi?id=1648112
- ttyAMA ttyAMA0: tty_open: tty->count(2) != (#fd's(1) + #kopen's(0)) https://bugzilla.redhat.com/show_bug.cgi?id=1644884
This is fixed, it was the console=ttyAMA0 option we had enabled which cause it to fight with bluetooth over who owned the serial device.
- The 35network-legacy is still used even if network-scripts isn't installed in Fedora 29 https://github.com/dracutdevs/dracut/issues/488
I've been traveling this week so I've not had time to dig further on this, hoping to catch up on the weekend.
It would be great to get some feedback on the most recent composes and any new issues encountered or anything else we may have missed.
Does anyone else have anything that might be a blocker here?
Peter
Peter,
Wondering if you have any magical insight in #4. For us this is the main blocker and something that we would like to wrap soon so that we can progress with testing.
- The 35network-legacy is still used even if network-scripts isn't
installed in Fedora 29
Dave
On Fri, Nov 16, 2018 at 2:07 PM Peter Robinson pbrobinson@gmail.com wrote:
On Wed, Nov 14, 2018 at 4:14 PM Paul Whalen pwhalen@redhat.com wrote:
Good morning all,
Apologies, there was a miscommunication about the IoT meeting this week and we missed our allotted time in #fedora-meeting.
We wanted to go over the list of blockers for Fedora 29 IoT and to check on testing results. The list currently includes:
- initial-setup hangs during boot after IoT installation https://bugzilla.redhat.com/show_bug.cgi?id=1646568
There's a fix pending review of this upstream here: https://github.com/rhinstaller/anaconda/pull/1692
- WARNING at drivers/mmc/bcm2835_sdhost.c:408/bcm2835_send_command()! https://bugzilla.redhat.com/show_bug.cgi?id=1644873
I've not managed to recreate this one, I also believe it's actually closely related to this one which Tim bought up on the thread too. Tim can you confirm that if you see this error it also causes issues with "rpm-ostree install" on the SD cards? There's been a few issues reported upstream around MMC stability on the bcm2835 driver and I wonder if there's something special happening with the way rpm-ostree hits the HW that is making this more likely to trigger. I also wonder if it's improved with v4.19.x kernel.
https://bugzilla.redhat.com/show_bug.cgi?id=1648112
- ttyAMA ttyAMA0: tty_open: tty->count(2) != (#fd's(1) + #kopen's(0)) https://bugzilla.redhat.com/show_bug.cgi?id=1644884
This is fixed, it was the console=ttyAMA0 option we had enabled which cause it to fight with bluetooth over who owned the serial device.
- The 35network-legacy is still used even if network-scripts isn't
installed in Fedora 29
I've been traveling this week so I've not had time to dig further on this, hoping to catch up on the weekend.
It would be great to get some feedback on the most recent composes and
any
new issues encountered or anything else we may have missed.
Does anyone else have anything that might be a blocker here?
Peter _______________________________________________ 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 Tue, Nov 27, 2018 at 12:48 AM Dave Hedge itswag7@gmail.com wrote:
Peter,
Wondering if you have any magical insight in #4. For us this is the main blocker and something that we would like to wrap soon so that we can progress with testing.
I do. It's an issue as a direct result of adding in the support for TPM2, I'm trying to get to the bottom of it, it's unclear where the fix/bug lies and I'm trying to get to the bottom of this so we can get the release out and we can move on.
Peter
- The 35network-legacy is still used even if network-scripts isn't installed in Fedora 29 https://github.com/dracutdevs/dracut/issues/488
Dave
On Fri, Nov 16, 2018 at 2:07 PM Peter Robinson pbrobinson@gmail.com wrote:
On Wed, Nov 14, 2018 at 4:14 PM Paul Whalen pwhalen@redhat.com wrote:
Good morning all,
Apologies, there was a miscommunication about the IoT meeting this week and we missed our allotted time in #fedora-meeting.
We wanted to go over the list of blockers for Fedora 29 IoT and to check on testing results. The list currently includes:
- initial-setup hangs during boot after IoT installation https://bugzilla.redhat.com/show_bug.cgi?id=1646568
There's a fix pending review of this upstream here: https://github.com/rhinstaller/anaconda/pull/1692
- WARNING at drivers/mmc/bcm2835_sdhost.c:408/bcm2835_send_command()! https://bugzilla.redhat.com/show_bug.cgi?id=1644873
I've not managed to recreate this one, I also believe it's actually closely related to this one which Tim bought up on the thread too. Tim can you confirm that if you see this error it also causes issues with "rpm-ostree install" on the SD cards? There's been a few issues reported upstream around MMC stability on the bcm2835 driver and I wonder if there's something special happening with the way rpm-ostree hits the HW that is making this more likely to trigger. I also wonder if it's improved with v4.19.x kernel.
https://bugzilla.redhat.com/show_bug.cgi?id=1648112
- ttyAMA ttyAMA0: tty_open: tty->count(2) != (#fd's(1) + #kopen's(0)) https://bugzilla.redhat.com/show_bug.cgi?id=1644884
This is fixed, it was the console=ttyAMA0 option we had enabled which cause it to fight with bluetooth over who owned the serial device.
- The 35network-legacy is still used even if network-scripts isn't installed in Fedora 29 https://github.com/dracutdevs/dracut/issues/488
I've been traveling this week so I've not had time to dig further on this, hoping to catch up on the weekend.
It would be great to get some feedback on the most recent composes and any new issues encountered or anything else we may have missed.
Does anyone else have anything that might be a blocker here?
Peter _______________________________________________ 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
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 Tue, Nov 27, 2018 at 10:02 AM Peter Robinson pbrobinson@gmail.com wrote:
On Tue, Nov 27, 2018 at 12:48 AM Dave Hedge itswag7@gmail.com wrote:
Peter,
Wondering if you have any magical insight in #4. For us this is the main blocker and something that we would like to wrap soon so that we can progress with testing.
I do. It's an issue as a direct result of adding in the support for TPM2, I'm trying to get to the bottom of it, it's unclear where the fix/bug lies and I'm trying to get to the bottom of this so we can get the release out and we can move on.
I think I have this fixed, or at least worked around in a reasonable and usable means. I'm just just putting some other pieces in place and we should have a RC.
P
Peter
- The 35network-legacy is still used even if network-scripts isn't installed in Fedora 29 https://github.com/dracutdevs/dracut/issues/488
Dave
On Fri, Nov 16, 2018 at 2:07 PM Peter Robinson pbrobinson@gmail.com wrote:
On Wed, Nov 14, 2018 at 4:14 PM Paul Whalen pwhalen@redhat.com wrote:
Good morning all,
Apologies, there was a miscommunication about the IoT meeting this week and we missed our allotted time in #fedora-meeting.
We wanted to go over the list of blockers for Fedora 29 IoT and to check on testing results. The list currently includes:
- initial-setup hangs during boot after IoT installation https://bugzilla.redhat.com/show_bug.cgi?id=1646568
There's a fix pending review of this upstream here: https://github.com/rhinstaller/anaconda/pull/1692
- WARNING at drivers/mmc/bcm2835_sdhost.c:408/bcm2835_send_command()! https://bugzilla.redhat.com/show_bug.cgi?id=1644873
I've not managed to recreate this one, I also believe it's actually closely related to this one which Tim bought up on the thread too. Tim can you confirm that if you see this error it also causes issues with "rpm-ostree install" on the SD cards? There's been a few issues reported upstream around MMC stability on the bcm2835 driver and I wonder if there's something special happening with the way rpm-ostree hits the HW that is making this more likely to trigger. I also wonder if it's improved with v4.19.x kernel.
https://bugzilla.redhat.com/show_bug.cgi?id=1648112
- ttyAMA ttyAMA0: tty_open: tty->count(2) != (#fd's(1) + #kopen's(0)) https://bugzilla.redhat.com/show_bug.cgi?id=1644884
This is fixed, it was the console=ttyAMA0 option we had enabled which cause it to fight with bluetooth over who owned the serial device.
- The 35network-legacy is still used even if network-scripts isn't installed in Fedora 29 https://github.com/dracutdevs/dracut/issues/488
I've been traveling this week so I've not had time to dig further on this, hoping to catch up on the weekend.
It would be great to get some feedback on the most recent composes and any new issues encountered or anything else we may have missed.
Does anyone else have anything that might be a blocker here?
Peter _______________________________________________ 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
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
Awesome! Looking forward to testing!
Sent from my iPhone
On Nov 27, 2018, at 11:09 AM, Peter Robinson pbrobinson@gmail.com wrote:
On Tue, Nov 27, 2018 at 10:02 AM Peter Robinson pbrobinson@gmail.com wrote:
On Tue, Nov 27, 2018 at 12:48 AM Dave Hedge itswag7@gmail.com wrote:
Peter,
Wondering if you have any magical insight in #4. For us this is the main blocker and something that we would like to wrap soon so that we can progress with testing.
I do. It's an issue as a direct result of adding in the support for TPM2, I'm trying to get to the bottom of it, it's unclear where the fix/bug lies and I'm trying to get to the bottom of this so we can get the release out and we can move on.
I think I have this fixed, or at least worked around in a reasonable and usable means. I'm just just putting some other pieces in place and we should have a RC.
P
Peter
- The 35network-legacy is still used even if network-scripts isn't installed in Fedora 29
Dave
On Fri, Nov 16, 2018 at 2:07 PM Peter Robinson pbrobinson@gmail.com wrote:
On Wed, Nov 14, 2018 at 4:14 PM Paul Whalen pwhalen@redhat.com wrote:
Good morning all,
Apologies, there was a miscommunication about the IoT meeting this week and we missed our allotted time in #fedora-meeting.
We wanted to go over the list of blockers for Fedora 29 IoT and to check on testing results. The list currently includes:
- initial-setup hangs during boot after IoT installation
There's a fix pending review of this upstream here: https://github.com/rhinstaller/anaconda/pull/1692
- WARNING at drivers/mmc/bcm2835_sdhost.c:408/bcm2835_send_command()!
I've not managed to recreate this one, I also believe it's actually closely related to this one which Tim bought up on the thread too. Tim can you confirm that if you see this error it also causes issues with "rpm-ostree install" on the SD cards? There's been a few issues reported upstream around MMC stability on the bcm2835 driver and I wonder if there's something special happening with the way rpm-ostree hits the HW that is making this more likely to trigger. I also wonder if it's improved with v4.19.x kernel.
https://bugzilla.redhat.com/show_bug.cgi?id=1648112
- ttyAMA ttyAMA0: tty_open: tty->count(2) != (#fd's(1) + #kopen's(0))
This is fixed, it was the console=ttyAMA0 option we had enabled which cause it to fight with bluetooth over who owned the serial device.
- The 35network-legacy is still used even if network-scripts isn't installed in Fedora 29
I've been traveling this week so I've not had time to dig further on this, hoping to catch up on the weekend.
It would be great to get some feedback on the most recent composes and any new issues encountered or anything else we may have missed.
Does anyone else have anything that might be a blocker here?
Peter _______________________________________________ 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
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
-
Dave Hedge -
Paul Whalen -
pbrobinson＠fedoraproject.org -
Peter Robinson -
Tim Coote -
Tim Jones -
Troy Dawson