On Wed, Feb 1, 2017 at 2:01 PM, Robert Moskowitz <rgm@xxxxxxxxxxxxxxx> wrote: > Dennis, > > Thanks for the response. > > On 01/30/2017 08:16 AM, Dennis Gilmore wrote: >> >> El mié, 25-01-2017 a las 10:37 -0500, Robert Moskowitz escribió: >>> >>> I build a CubieTruck image using the installer script with the >>> following >>> options: >>> >>> --target=Cubietruck --media=/dev/sdb --norootpass --selinux=OFF >>> --addconsole --resizefs >> >> allwinner automatically outputs to the serial console without a boot >> argument to set it, that step is not necessary. > > > I guess just one of those things you have to know. So far, all I am working > with are allwinner boards. > > Will add this to my notes. > > >> >>> I booted up the image with a UDB keyboard and VGA monitor attached >>> plus >>> the TTY console. >>> >>> After I logged into the console as root, I set the root password, >>> and >>> added myself as a user. I then used this userID to log into the Xfce >>> login. >>> >>> Next I did 'dnf update' Of course this took time to run. But a >>> VERY >>> long time between the cleanup and verify phases. During these I got >>> the >>> message: >>> >>> >>> Image Name: 4.10.0-0.rc5.git0.1.fc26.armv7hl >>> Created: Wed Jan 25 10:04:59 2017 >>> Image Type: ARM Linux Kernel Image (uncompressed) >>> Data Size: 6054568 Bytes = 5912.66 kB = 5.77 MB >>> Load Address: 00008000 >>> Entry Point: 00008000 >>> Image Name: initramfs >>> Created: Wed Jan 25 10:05:01 2017 >>> Image Type: ARM Linux RAMDisk Image (uncompressed) >>> Data Size: 16525173 Bytes = 16137.86 kB = 15.76 MB >>> Load Address: 00000000 >>> Entry Point: 00000000 >>> dracut: Disabling early microcode, because kernel does not support >>> it. >>> CONFIG_MICROCODE_[AMD|INTEL]!=y >>> >>> >>> eventually the update finished. The system SEEMS to be working, but >>> what is with this message? >> >> What part of the message? the dracut part is a message saying that an >> x86 only opton for firmware patching is not set. it is just noise on >> non x86 but could be useful on x86. the other messages are from >> mkimage, for historical reasons we make wrapped kernels and initramfs's >> which we do not actually use. > > > So basically I just ignore this. But it seemed that dracut ran a very long > time before it spit out this information and finished up. Like it was not > happy about something and finally gave up. It's not just dracut, it's the install of the contents of the rpm and then the dracut process that generates the new host specific initrd. It's a IO heavy task. _______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
