On Fri, Sep 18, 2015 at 8:30 PM, Saul Wold <[email protected]> wrote:
> On 09/18/2015 02:57 AM, Prasant J wrote: > >> On Fri, Sep 18, 2015 at 2:57 AM, Saul Wold <[email protected]> wrote: >> >> On 09/17/2015 06:05 AM, Prasant J wrote: >>> >>> Hi, >>>> >>>> I'm using Intel Atom E3845 based hardware board for my embedded product >>>> and >>>> I'm using valleyisland-32 image. >>>> >>>> >>>> I want grub to auto start and not wait for user input. >>>> >>>> So, I manually added (appended) the following lines: >>>> GRUB_DEFAULT=0 (for the first menu entry, there is only one entry) >>>> GRUB_TIMEOUT=0 >>>> to /grub/grub.cfg file >>>> but it does not seem to work. >>>> >>>> >>>> Can you confirm which version of grub you are using? >>>> >>> >>> for grub2, you should be modifing /boot/grub/grub.cfg with >>> set default="0" >>> set timeout=<timeval> >>> >>> Sau! >>> >> >> >> >> Thanks Saul for the response. I tried your suggestion but does not work. >> >> >> The strange thing is I tried changing the menu entry name from "Linux" to >> "Linux test" even that does not change. >> Grub seems to be doing some black magic which I cannot get hold of. >> >> >> Any more suggestions. I'm kind of stuck. >> >> Where did you make the changes, to which file exactly? Was it on the > harddrive your booting from or USB stick your installing from? > > For me modifying the /boot/grub/grub.cfg file worked just fine and changed > the behavior. > > Sau! > >> >> I tried both the options. a) I changed on the SD Card (I boot from an SD Card) - no effect b) I changed the install.sh script in initrd - no effect Any of the above did not work. One more information: I have changed the first partition (on which GRUB resides) from ext3 to FAT32 partition. I made this change in the install.sh script. Would it have any impact? Would GRUB behave differently when run from FAT32 partition? Regards, Pj
-- _______________________________________________ meta-intel mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-intel
