Good Day,

 I updated the x86_64 -> 29.20181021.0 via `rpm-ostree upgrade` and then a reboot (`systemctl reboot`).


The RPi3B+ is not working.  I am getting same issue as previous ( ...  "  drivers/mmc/bcm2835_sdchost.c:408/bcm_2835_send_command()!" ...) repeating

 This boot was from my SD Card doing the following :


  xzcat /usr/local/src/Fedora-IoT-29-20181021.0.aarch64.raw.xz | dd status=progress bs=4M of=/dev/sdb


What other specific details can I provide?
What is next?

Doug


On Wed, Oct 17, 2018 at 4:39 PM, Douglas E. Hopley Jr. <hopley@f6systems.com> wrote:
updates
 With some successes

A) I pulled down Fedora-IoT-ostree-x86_64-29-20181016.0.iso 
 Then booted a VirtualBox machine
 The  install was a success  
  IF you need any specific details let me know OK?

B) I used the same .iso file to a DVD and booted + installed and ran one of the Lenovo x100e to a running workstation.
 Another success

C) I pulled down Fedora-IoT-29-20181016.0.aarch64.raw.xz.  

booting my RPi3B+ has a repeating error:
 ~ 'NG at drivers/mmc/bcm2835_sdchost.c:408/bcm_2835_send_command()!

What other specific details can I provide?

Doug

On Fri, Oct 12, 2018 at 8:48 AM, Douglas E. Hopley Jr. <hopley@f6systems.com> wrote:
 A couple of updates inline below.  
On Thu, Oct 11, 2018 at 6:02 PM Peter Robinson <pbrobinson@gmail.com> wrote:
>> >  I  pulled down and burnt Fedora-IoT-dvd-x86_64-29-20181010.0.iso.  Booting for an install is not successful for me.
>> >
>> >  On lenovo x100e h/w resources I booted to the install and have an issue  ~-> "dracut init-queue timeout " .  That is similar to what I saw earlier with that machine and the ACER.
>>
>> Does a standard Fedora 29 install work on this device? Also what type
>> of storage are you trying to boot it from, or install it to?
>
>
> Same issue with a Fedora 29 Server x86 iso (specifically Fedora-Server-dvd-x86_64-29-20181010.n.0.iso)
> As a quick test, I had an older iso  (specifically Fedora-Server-dvd-x86_64-26-1.5.iso) and that booted - ready to install.   Not the same, though wanted to confirm boot.
>
>  I am booting off of an attached (USB) DVD Drive trying to boot the ISO I wrote to the inserted DVD.  The installation, for this machine, is onto the internal HDD (ATA ...)

OK, so this isn't a IoT specific problem then, we should report this
in the standard method, I think bugzilla against the kernel with the
appropriate bits would be a good start.

>> >  Should I ,and where , send the rdsosreport.txt ?  OR should I look to another path/method to install?
>> >
>> >  Can  I provide more details/information?  Any next steps I should follow?
>>
>> Let's try with a vanilla Fedora 29 install and we can then work out if
>> it's a generic or IoT specific issue. Laptops aren't really a targeted
>> device so it's not something that will have been tested widely. ATM
>> most of my x86_64 testing has actually been VMs.
>>
> What VM is recommended?  I have (sorry) VirtualBox ,  I can wipe that and move to another let me know OK?

That should be fine, it's a raw disk format so I'm not quite sure how
VB deals with that but I believe it should be straight forward to
import it.

 
Same issue in  VirtualBox ( v 5.2.18 )  ~-> "dracut init-queue timeout "   (Fedora-IoT-dvd-x86_64-29-20181010.0.iso).  I will revisit over the weekend.
 
>> >  I also pulled Fedora-IoT-29-20181010.0.aarch64.raw.xz and used arm-image-installer.  Using an SDCard that  I had put raspbian and booted the pi 3 B+ that ran.   Same card that worked for a raspbian boot was used  for the arm-image-installer process.  Booting with the SD card that the arm-image-installer wrote did  not work.
>>
>> I have Fedora IoT running OK on a standard RPi3, I'm awaiting more 3B+
>> devices but it should work, I need to re-provision mine again. What
>> options are you specifying for arm-image-installer (also what
>> version), serial console or HDMI?
>>
>  For my RPi3B+

Try with the 20181011 nightly and I think this should now work, there
was a bug that was a side effect of a fix that went in for a different
bug.

 
The RPi3B+ started to boot and failed.  I am off to some meetings, will look for new nightly.  This weekend
if that exists I will grab and boot the RPi3B+.  I will plan to update on this thread with more details.

 
> ## 20181010
>  wget http://mirrors.kernel.org/fedora-alt/iot/29/IoT/aarch64/images/Fedora-IoT-29-20181010.0.aarch64.raw.xz
>  ## 'try' arm-image-installer
>
>  arm-image-installer --image=/usr/local/src/Fedora-IoT-29-20181010.0.aarch64.raw.xz --target=rpi3 --media=/dev/sdb
>
> --> HDMI cable
>
> Is the option "--addconsole" for use with a serial cable?
>
>> > At this point I have no running instances as I have wiped old machines to move to the updates.
>> >
>> >  I was trying to get to recent version installed on the resources I have here for Fedora IoT to get to more current.
>> >
>> > If there is anything specific I can do to test or spend focus on, let me know.
>>
>> See above
>>
>> >  My goal is to see where I can start to add value.  I feel that I am having issues getting environments setup and am not able to get to working with IoT.  What am I missing?  Short term I wanted to see where I could help and right now I feel like a drag.
>> >
>> > It feels a little bit like I am struggling at almost to basic of a level.  I did not want to burden the list with trivia as I want to help and not be a drain.
>>
>> Feedback on things you might believe are missing in the getting
>> started guide would be a good start
>> https://docs.fedoraproject.org/en-US/iot/
>>
> Got it.  Over the weekend I will plan to review.

OK, I think you should be able to move forward on at least VirtualBox
and the RPi.

Peter

I hope you have a great weekend.
--
Douglas E. Hopley Jr. 



--
Douglas E. Hopley Jr. 



--
Douglas E. Hopley Jr.