image will not boot

Bug #789758 reported by JC Hulce
This bug affects 2 people
Affects Status Importance Assigned to Milestone
JC Hulce

Bug Description

The built image will not boot. I have tried using different kernels in config, to no avail. My cd, natty beta 1, has -7, the one in updates is -8. 8 will not install correctly. When 7 is used in config, the iso boots to a blank screen. When 8 is used, it spools error messages about 8's missing modules (because they didn't install)

Revision history for this message
JC Hulce (soaringsky) wrote :

There are a few solutions i can think of:
-use the most recent natty cd as the base
-find out what kernel is on the base, and use that in config
-get a base with the most recent kernel
-remove old kernels
-install multiple times to make sure it works
Combinig all of these should do the trick

Changed in ugr-ebuild:
assignee: nobody → JC Hulce (soaringsky)
importance: Undecided → Critical
Revision history for this message
Martin Simon (martin.simon) wrote :

can't get it to boot neither...
have most recent kernel and stuff but won' work.

Revision history for this message
JC Hulce (soaringsky) wrote :

@Martin this issue is about building cd images, not regular ugr

Revision history for this message
JC Hulce (soaringsky) wrote :

I have used the ideas above. There are now no more kernel or other major issues upon startup. However, the cd boots to a blank black screen.

We need to resync with the original ebuild anyways: the one we are using is meant for 10.10. They have since updated it for 11.04 at

Revision history for this message
JC Hulce (soaringsky) wrote :

Resynced to elementary's new code. The image now boots to a blue screen with a cursor. If you press ctrl+alt+f1 you can get a console. Just about every command fails with the mysterious message "cannot close file descriptor: Input/ output error". This message is also the reason why gdm won't load, hence the blue screen.

Perhaps we should ask the elementary team for help in #elementary or #elementary-dev?

Revision history for this message
JC Hulce (soaringsky) wrote :

Asked for help. This was caused by bug 797590

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.