Boot with boot helper fails for Blueberry

[Caroline]

Just tried it on one of my PCs will attempt to replicate.

The last two dots seem to go very slowly and it never seems to actually boot.

[Caroline (cmeeks)]

Replicated this on an IBM desktop at a school in NH today. Stopped at the same point.

However, the boot with helper did work on a laptop there. Bernie will be going with me to GPA on Friday I hope and we shall see if it effects their computers.

[Caroline (cmeeks)]

This appears to be an upstream issue. I get the same results with a F12 CD. These machines used to boot fine.

Bernie was able to get them to work by commenting out some of the video drivers.

I've seen this problem on several Dell computers.

On a Thinkpad laptop I saw an issue that is probably related where the screen flashed on and off.

No upstream ticket has been filed yet as Bernie is on vacation.

[Hermann (haertel)]

I get the same problem with all my three computers. When activating the down arrow button I see the following error messages:
grep not found
Unable to find persistent overlay
Machine in enforced mode and cannot execute load_policy
Not continuing

Any hint?

[Thomas C Gilliard (satellit-)]

Blueberry needed"selinux=0" set by <esc><tab> on blue boot screen on startup.
edit and add boot parameter selinux=0
-----------------------------------------------------------
permanent fix:
edit /etc/sysconfig/selinx
setlinux=disabled

This worked for me.... This could fix this also though I have not used boot disk.

[Hermann (haertel)]

Sorry, but this does not work for me.
When I do <esc><tab> on blue boot screen I get a boot: prompt.
But what ever I type in is answered with: "can not find kernel immage"
and the boot process continues and hangs up.
When I hit the arrow down button I see the error message which I have reportet before.
On my FEDORE USB-stick within /Efi/boot/grub I find the line:
 kernel /EFI/boot/vmlinuz0 root=live:LABEL=soas-2-blueberry rootfstype=auto rw liveimg overlay=UUID=086E-0B3F quiet selinux=0 rhgb
To my understanding this mean that selinux=0 is set.
More help needed
Hermann

[Hermann (haertel)]

Since there was no answer on my previous message I wonder if I can still expect a reaction.
To have a functioning boot helper would be a great help because there are many older computers around which do not allow to boot from an USB-stick.
Hoping for a helpful reaction.

Hermann

[Sebastian Dziallas (sdziallas)]

I would like to apologize for the delay in response here. Our official bug tracker has been moved to bugs.sugarlabs.org and I have been lately swamped with a good amount of tasks - while this is really not the ideal thing to happen, it does, since we are all just volunteers.

Concerning your question: It seems like this problem is indeed very common and somebody already filed a new ticket at bugs.sugarlabs.org: http://bugs.sugarlabs.org/ticket/1626

I have talked to a number of people this morning and rebuilt the boot helper to include the selinux parameter: http://download.sugarlabs.org/soas/releases/soas-2-boot.iso

For the build itself, it should already contain it. The EFI folders are for Macs only - there should be a syslinux directory together with a syslinux.cfg file, which should show the parameters there.

Hoping this helps.

[Hermann (haertel)]

This was a great help. Now everything works fine.
Thanks a lot.