<div dir="ltr"><div><div><div><div>One more questions about the Grub2 and EFI system for /dev/sda1<br></div>Is it actually possible to boot the system without initrd set?<br></div>It is not set during installation process in grub.cfg<br></div>It was also not in the FIDO install.sh, but FIDO was not:<br>parted ${device} mktable gpt<br></div>but:<br><div><div><div><div><div>parted /dev/${device} mklabel msdos<div class="gmail_extra"><br></div><div class="gmail_extra">and the grub.cfg worked OK:<br>menuentry "Linux" {<br>Â Â Â set root=(hd0,1)<br>Â Â Â linux /vmlinuz root=/dev/sda2 rw quiet<br>}<br><br></div><div class="gmail_extra">So the initramfs you are talking about is actually missing now?<br><br></div><div class="gmail_extra">kind regards<br></div><div class="gmail_extra">Simon :-)<br></div><div class="gmail_extra"><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Jul 23, 2016 at 8:31 PM, Simon Bolek <span dir="ltr"><<a href="mailto:simon.bolek@googlemail.com" target="_blank">simon.bolek@googlemail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class="">On Sat, Jul 23, 2016 at 7:33 PM, Khem Raj <span dir="ltr"><<a href="mailto:raj.khem@gmail.com" target="_blank">raj.khem@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span>On Sat, Jul 23, 2016 at 9:49 AM, Simon Bolek <<a href="mailto:simon.bolek@googlemail.com" target="_blank">simon.bolek@googlemail.com</a>> wrote:<br>
> Thanks, sorry that I bother you all the time, but I do not seem to make any<br>
> progress :(<br>
> Is there anything else I can check?<br>
> It seems, on boot time this device is not mounted, only ram0...15.<br>
<br>
</span>It so seems that driver may be missing in initramfs could be one<br>
reason. </blockquote></span><div>You mean in on the boot partition under /grub/i386-pc/ among *.mod files?<br>In this case, that would be /dev/sda2.<br></div><div>Or am should I look for that somewhere else?<br></div><span class=""><div><br>Â </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">other reason could<br>
be that udev is not settling down for this device. So may be changing<br>
the udevadm to wait<br>
a bit for devices to mount might help<br></blockquote></span><div>Could you tell me where would I do that? I mean, where exactly is the udevadm set-up at boot? I cannot find the place. Is it somewhere inside /vmlinuz on /dev/sda2 ?<br><br></div><div>thanks<span class=""><font color="#888888"><br></font></span></div><span class=""><font color="#888888"><div>s:-)<br></div></font></span><div><div class="h5"><div>Â </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div><div><br>
><br>
> thank you<br>
> Simon :-)<br>
><br>
><br>
><br>
> On Sat, Jul 23, 2016 at 6:07 PM, Khem Raj <<a href="mailto:raj.khem@gmail.com" target="_blank">raj.khem@gmail.com</a>> wrote:<br>
>><br>
>> On Sat, Jul 23, 2016 at 8:57 AM, Simon Bolek <<a href="mailto:simon.bolek@googlemail.com" target="_blank">simon.bolek@googlemail.com</a>><br>
>> wrote:<br>
>> > Hi,<br>
>> ><br>
>> > Well it is, as far as what<br>
>> > parted /dev/sda print<br>
>> >Â says.<br>
>> ><br>
>> > generated grub.cfg matches that with PARTUUID, so it looks fine.<br>
>> ><br>
>> > menuentry "Linux" {<br>
>> >Â Â Â search --no-floppy --fs-uuid e88ec2c7-3438-4fe3-9033-83eb81957875<br>
>> > --set<br>
>> > root<br>
>> >Â Â Â linux /vmlinuz root=PARTUUID=8316255c-f839-43fa-b2c6-d83bbed80962<br>
>> > rw<br>
>> > quiet<br>
>><br>
>> this seems ok to me.<br>
>><br>
>> ><br>
>> > }<br>
>> ><br>
>> > However fdisks -l shows only /dev/sda1, which ist strange.<br>
>> ><br>
>> > Is there something wrong with install.sh script?<br>
>> > Compared to FIDO, it is GPT, not MSDOS. But i did not touch anything<br>
>> > there.<br>
>> > Maybe you can take a look at it?<br>
>> ><br>
>> > <a href="http://git.yoctoproject.org/cgit.cgi/poky/plain/meta/recipes-core/initrdscripts/files/init-install.sh?h=jethro" rel="noreferrer" target="_blank">http://git.yoctoproject.org/cgit.cgi/poky/plain/meta/recipes-core/initrdscripts/files/init-install.sh?h=jethro</a><br>
>> > It always checks the grub version, however in FIDO Grub was also 2.00,<br>
>> > so I<br>
>> > do not get the IFs.<br>
>> ><br>
>> > thank you!<br>
>> > Simon :-)<br>
>> ><br>
>> ><br>
>> > On Sat, Jul 23, 2016 at 4:52 PM, Khem Raj <<a href="mailto:raj.khem@gmail.com" target="_blank">raj.khem@gmail.com</a>> wrote:<br>
>> >><br>
>> >><br>
>> >> > On Jul 23, 2016, at 5:25 AM, Simon Bolek <<a href="mailto:simon.bolek@googlemail.com" target="_blank">simon.bolek@googlemail.com</a>><br>
>> >> > wrote:<br>
>> >> ><br>
>> >> > Hello!<br>
>> >> ><br>
>> >> > I am trying to install genericx86 core-image-sato on a atom-pc device<br>
>> >> > with 80GB Intel SSD drive.<br>
>> >> > I have created an image with<br>
>> >> > bitbake core-image-sato<br>
>> >> > without changing anything in the kernel via menuconfig, etc.<br>
>> >> ><br>
>> >> > ps. after installation I had to set /dev/sda1 to bootable with disk<br>
>> >><br>
>> >> it seems your rootfs is on /dev/sda3 can you check kernel parameters<br>
>> >> what<br>
>> >> is it passing for root=<br>
>> >><br>
>> >> ><br>
>> >> > After installation I have got this ugly error while booting the<br>
>> >> > device.<br>
>> >> > PLEASE HELP ME!<br>
>> >> ><br>
>> >> ><br>
>> >> > "...<br>
>> >> > VFS: Cannot open root device "PARTUUID=8316.." or unknown-block(0,0):<br>
>> >> > error -6<br>
>> >> > Pease append a correct "root=" boot option; here are the available<br>
>> >> > partitions:<br>
>> >> > 0100 4096 ram0 (driver?)<br>
>> >> > ...<br>
>> >> > 010f 4096 ram15 (driver?)<br>
>> >> > ..."<br>
>> >> ><br>
>> >> ><br>
>> >> > I noticed that install.sh script is creating GPT<br>
>> >> > parted ${device} mktable gpt<br>
>> >> > not MSDOS as in previous yocto versions, e.g. fido.<br>
>> >> ><br>
>> >> > Any hint is more than welcome. The device will just not boot :((((<br>
>> >> ><br>
>> >> > Here are some details about the device:<br>
>> >> ><br>
>> >> ><br>
>> >> > +++<br>
>> >> > blkid says:<br>
>> >> > /dev/sda2: UUID="e88ec2c7-3438-4fe3-9033-83eb81957875" TYPE="ext3"<br>
>> >> > PARTLABEL="boot" PARTUUID="57f43ab0-6e30-4721-81e2-c565f6c184c8"<br>
>> >> > /dev/sda3: UUID="cbb77742-c9fe-4f19-85d7-399af99c3aa8" TYPE="ext3"<br>
>> >> > PARTLABEL="root" PARTUUID="8316255c-f839-43fa-b2c6-d83bbed80962"<br>
>> >> > /dev/sda4: TYPE="swap" PARTLABEL="swap"<br>
>> >> > PARTUUID="15ddbd73-15b3-40a8-97e7-6377048a79eb"<br>
>> >> > /dev/sdb: SEC_TYPE="msdos" LABEL="boot" UUID="3C80-C1D7" TYPE="vfat"<br>
>> >> > /dev/sda1: PARTLABEL="bios_boot"<br>
>> >> > PARTUUID="11cf26d2-2333-4c5b-a876-59d65929085f"<br>
>> >> ><br>
>> >> > +++<br>
>> >> > /etc/fstab says<br>
>> >> > # stock fstab - you probably want to override this with a machine<br>
>> >> > specific one<br>
>> >> ><br>
>> >> > /dev/root      /          auto    defaults<br>
>> >> > 1Â 1<br>
>> >> > proc         /proc        proc    defaults<br>
>> >> > 0Â 0<br>
>> >> > devpts        /dev/pts       devpts   mode=0620,gid=5<br>
>> >> > 0Â 0<br>
>> >> > tmpfs        /run         tmpfs<br>
>> >> > mode=0755,nodev,nosuid,strictatime 0Â 0<br>
>> >> > tmpfs        /var/volatile    tmpfs   defaults<br>
>> >> > 0Â 0<br>
>> >> ><br>
>> >> > # uncomment this if your device has a SD/MMC/Transflash slot<br>
>> >> > #/dev/mmcblk0p1    /media/card     auto<br>
>> >> > defaults,sync,noauto 0 0<br>
>> >> ><br>
>> >> > /dev/sda2Â Â Â Â Â /Â Â Â Â Â Â Â Â Â Â Â ext3Â Â Â Â Â rw<br>
>> >> > 0Â 1<br>
>> >> > /dev/disk/by-partuuid/15ddbd73-15b3-40a8-97e7-6377048a79eb<br>
>> >> > swap       swap    defaults       0 0<br>
>> >> > UUID=e88ec2c7-3438-4fe3-9033-83eb81957875Â Â Â Â Â Â Â /boot<br>
>> >> > ext3    defaults       1 2<br>
>> >> ><br>
>> >> ><br>
>> >> > +++<br>
>> >> > fdisk -l says<br>
>> >> > Disk /dev/sda: 80.0 GB, 80026361856 bytes<br>
>> >> > 255 heads, 63 sectors/track, 9729 cylinders<br>
>> >> > Units = cylinders of 16065 * 512 = 8225280 bytes<br>
>> >> ><br>
>> >> >  Device Boot   Start     End   Blocks Id System<br>
>> >> > /dev/sda1Â Â *Â Â Â Â Â Â 1Â Â Â Â 9730Â Â 78150743+ ee EFI GPT<br>
>> >> ><br>
>> >> > +++<br>
>> >> > parted /dev/sda says<br>
>> >> > Model: ATA INTEL SSDSA2M080 (scsi)<br>
>> >> > Disk /dev/sda: 80.0GB<br>
>> >> > Sector size (logical/physical): 512B/512B<br>
>> >> > Partition Table: gpt<br>
>> >> > Disk Flags: pmbr_boot<br>
>> >> ><br>
>> >> > Number Start  End   Size  File system   Name    Flags<br>
>> >> > 1   1049kB 2097kB 1049kB         bios_boot bios_grub<br>
>> >> >Â 2Â Â Â 2097kBÂ 19.9MBÂ 17.8MBÂ ext3Â Â Â Â Â Â boot<br>
>> >> >Â 3Â Â Â 22.0MBÂ 76.0GBÂ 76.0GBÂ ext3Â Â Â Â Â Â root<br>
>> >> >Â 4Â Â Â 76.0GBÂ 80.0GBÂ 4001MBÂ linux-swap(v1)Â swap<br>
>> >> ><br>
>> >> > +++<br>
>> >> > lspci says<br>
>> >> > Device:Â Â 00:1f.2<br>
>> >> > Class:Â Â IDE interface<br>
>> >> > Vendor:Â Â Intel Corporation<br>
>> >> > Device:Â Â NM10/ICH7 Family SATA Controller [IDE mode]<br>
>> >> > SVendor:Â Â Intel Corporation<br>
>> >> > SDevice:Â Â Device 464c<br>
>> >> > Rev:Â Â 01<br>
>> >> > ProgIf:Â Â 8a<br>
>> >> > Driver:Â Â ata_piix<br>
>> >> > Module:Â Â ata_piix<br>
>> >> ><br>
>> >> ><br>
>> >> > thank you<br>
>> >> > Simon :-)<br>
>> >> ><br>
>> >> ><br>
>> >> ><br>
>> >><br>
>> ><br>
><br>
><br>
</div></div></blockquote></div></div></div><br></div></div>
</blockquote></div><br></div></div></div></div></div></div></div>