Crown Beach install image doesn't boot

Bug #221157 reported by Clayne Robison
4
Affects Status Importance Assigned to Milestone
Moblin Image Creator
Incomplete
Undecided
Unassigned

Bug Description

I pulled down the latest MIC changes on 23 Apr 2008. I have created Gutsy and Hardy images for my CrownBeach system (with screen kit). The Hardy image has the crownbeach-full-mobile-stack-with-proprietary fset(s); the Gutsy image has the moblin-crownbeach-full-mobile-stack-with-proprietary fsets. After creating install images for both and putting the images on USB keys, the images install correctly, but during initial reboot, the loader splash image disappears and the screen starts flashing on and off at

*Starting MoblinSystemDaemon moblin-system-daemon [OK]

and keeps flashing until:

*Running local boot scripts(/etc/rc.local) [OK]
FATAL: Error inserting g_file_storage(/lib/modules/2.6.22-14-lpia/kernel/drivrs/usb/gadget/g_file_storage.ko): Unknown symbol in module, or unknown parameter (see dmesg)
* Starting Bluetooth services [OK]

And then the screen stops flashing and remains on. REbooting again doesn't fix anything.

Revision history for this message
Praj (prajwal-linux) wrote :

Can you provide more details on what platforms were used on the crown-beach system:
There are many platforms which use Hardy (ex menlow-lpia-ubuntu-hardy, menlow-lpia-ubuntu-hardy-ppa and menlow-lpia-ubuntu-hardy-ppa-snapshot)

Changed in moblin-image-creator:
status: New → Incomplete
Revision history for this message
Clayne Robison (clayne-b-robison) wrote :

Actually, you can scratch the Hardy part of this bug. The Gutsy target still has the problem. The project/platform info: mccaslin-lpia.

Revision history for this message
Clayne Robison (clayne-b-robison) wrote :

You can close this bug. I just found out that the problem is that my hardware is too old. I'll get upgraded next week.

Revision history for this message
navquest (michaeline-stanley) wrote :

Hi,

I tried to install CrownBeach in an Intel atom Board using cb-7-i386-CD.iso. What comes up is

the command prompt and there is no gui.Can anyone please let me know how to get the gui? Should

login in as root? Please help..

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

Other bug subscribers

Remote bug watches

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