SoaS Blueberry boot failure

Bug #492936 reported by SeanDaly
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Sugar on a Stick
Fix Released
Undecided
Unassigned

Bug Description

I just generated a Blueberry SD Card under WinXP with liveusbcreator v3.9. On boot of Dell Latitude 2100, boot halts with following message:

[drm:drm_mode_rmfb] *ERROR* tried to remove a fb that we didn't own

Boot has failed, sleeping forever.

Revision history for this message
Sebastian Dziallas (sdziallas) wrote :

I've seen this at FUDCon sporadically on different machines, but I'm not exactly sure what's causing it. Maybe you could try following these instructions from Strawberry to see whether it helps:

# Press the <Escape> key at the blue screen, which appears for a second before the normal boot process starts. You'll be presented a short menu, at which you can directly press <Tab>, then just add the "nomodeset" argument in the appearing line, and then boot by pressing the <Enter> key.

Revision history for this message
Thomas C Gilliard (satellit-) wrote : Re: [Bug 492936] Re: SoaS Blueberry boot failure

I also see this message on restart of sh generated 2 GB usb of
Blueberry-v2-.iso on EeePC 900

If I enter nomodeset at <TAB>

nomodeset command results in message:

 "mount: you must specify the file system type can't mount root filesystem"

Boot has failed, sleeping forever
=======================
USB worked on first run

(left out 3 /home commands in sh script)

Sebastian Dziallas wrote:
> I've seen this at FUDCon sporadically on different machines, but I'm not
> exactly sure what's causing it. Maybe you could try following these
> instructions from Strawberry to see whether it helps:
>
> # Press the <Escape> key at the blue screen, which appears for a second
> before the normal boot process starts. You'll be presented a short menu,
> at which you can directly press <Tab>, then just add the "nomodeset"
> argument in the appearing line, and then boot by pressing the <Enter>
> key.
>
>

Revision history for this message
Thomas C Gilliard (satellit-) wrote :

This may be caused by having used a (--overlay-size-mb200) and downloading 2 large e-books to the journal.
Ran out of space in overlay as there was an error on shutting down.
 I re-made the USB with a larger overlay (1400mb)and this has not occurred again.
I think the overlay got corrupted.

Revision history for this message
SeanDaly (sdaly-be) wrote :

The same SD Card fails boot on Dell Inspiron Mini10:

mount: unknown filesystem type 'DM_snapshot_cow'
mount: unknown filesystem type 'DM_snapshot_cow'
mount: unknown filesystem type 'DM_snapshot_cow'
mount: unknown filesystem type 'DM_snapshot_cow'
mount: unknown filesystem type 'DM_snapshot_cow'
mount: unknown filesystem type 'DM_snapshot_cow'
mount: unknown filesystem type 'DM_snapshot_cow'
mount: unknown filesystem type 'DM_snapshot_cow'

Can't mount root filesystem

Boot has failed, sleeping forever.

Revision history for this message
SeanDaly (sdaly-be) wrote :

I loaded a new blank 4 Gb USB stick with live-usbcreator v3.9, boot failed however additional CLI text is visible having scrolled into the white boot dots animation sequence:

/squashfs/LiveOS/ext3fs.img: No such file or directory
umount: /squashfs: not mounted
/sbin/dmsquash-live-root: 166: grep: not found
[: 166: /overlayfs/LiveOS/overlay-USB: unexpected operator
dracut Warning: Unable to find persistent overlay; using temporary
mount: unknown filesystem type 'DM_snapshot_cow'
mount: unknown filesystem type 'DM_snapshot_cow'
mount: unknown filesystem type 'DM_snapshot_cow'
mount: unknown filesystem type 'DM_snapshot_cow'
mount: unknown filesystem type 'DM_snapshot_cow'
mount: unknown filesystem type 'DM_snapshot_cow'
mount: unknown filesystem type 'DM_snapshot_cow'
mount: unknown filesystem type 'DM_snapshot_cow'
mount: unknown filesystem type 'DM_snapshot_cow'
mount: unknown filesystem type 'DM_snapshot_cow'

Can't mount root filesystem
[drm:drm_mode_rmfb] *ERROR* tried to remove a fb that we didn't own

Boot has failed, sleeping forever.

Revision history for this message
SeanDaly (sdaly-be) wrote :

When booting 4 Gb USB stick on Eee PC 4G, same as immediately above, but right before boot animation, following message scrolls up then disappears. I photographed it:

render error detected, EIR: 0x00000010
page table error
  PGTBL_ER: 0x00000100
[drm:i915_handle_error] *ERROR* EIR stuck: 0x00000010, masking
render error detected, EIR: 0x00000010
page table error
  PGTBL_ER: 0x00000100

Revision history for this message
Thomas C Gilliard (satellit-) wrote :

I get the same error message on all 4 types of my sticks after hitting
"Boot" but then they go on to work properly.
All booting in EeePC900 wirelessly.

1.} sh script on 2GB USB (1400 mb persistence)
2.) image-writer 2GB USB (no persistence)
3.) dd created 2 GB USB (no persistence)
4.) zyx=liveinstaller created 4GB USB (persistent)

I do not think this message is related to your problem

SeanDaly wrote:
> When booting 4 Gb USB stick on Eee PC 4G, same as immediately above, but
> right before boot animation, following message scrolls up then
> disappears. I photographed it:
>
> render error detected, EIR: 0x00000010
> page table error
> PGTBL_ER: 0x00000100
> [drm:i915_handle_error] *ERROR* EIR stuck: 0x00000010, masking
> render error detected, EIR: 0x00000010
> page table error
> PGTBL_ER: 0x00000100
>
>

Revision history for this message
SeanDaly (sdaly-be) wrote :

This problem solved... the ISO image I had was missing over 100 Mb!

To be filed under: Never trust a GUI file manager message...

I am sure doing a checksum should have been my next step... but I confess I've only done this once some time ago

I think there were checksum instructions for Strawberry, is there anyone who could update that procedure for Blueberry?

thanks

Sean

Revision history for this message
Sebastian Dziallas (sdziallas) wrote :

They're on the Blueberry page now, too! :) Closing this one.

Changed in soas:
status: New → Fix Released
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.