#10484 LOW 1.75-so: XO-1.75 os1 pause with prompts during boot, entering interactive startup
Zarro Boogs per Child
bugtracker at laptop.org
Thu Nov 25 16:30:13 EST 2010
#10484: XO-1.75 os1 pause with prompts during boot, entering interactive startup
--------------------------+-------------------------------------------------
Reporter: Quozl | Owner:
Type: defect | Status: new
Priority: low | Milestone: 1.75-software
Component: not assigned | Version: Development build as of this date
Keywords: | Next_action: reproduce
Verified: 0 | Deployment_affected:
Blockedby: | Blocking:
--------------------------+-------------------------------------------------
{{{
[ 3.453975] mmc1: new SDIO card at address 0001
[ 64.161692] libertas: can't load helper firmware
[ 64.175822] libertas: failed to load helper firmware
[ 64.190354] libertas_sdio: probe of mmc1:0001:1 failed with error -2
[ 64.282079] mmc2: new high speed SDHC card at address e0b2
[ 64.297237] mmcblk0: mmc2:e0b2 SU04G 3.69 GiB
[ 64.312580] mmcblk0: p1 p2
[ 64.404299] EXT3-fs: barriers not enabled
[ 79.635441] kjournald starting. Commit interval 5 seconds
[ 80.167733] EXT3-fs (mmcblk0p2): using internal journal
[ 80.182249] EXT3-fs (mmcblk0p2): recovery complete
[ 80.197928] EXT3-fs (mmcblk0p2): mounted filesystem with ordered data
mode
[ 80.214264] VFS: Mounted root (ext3 filesystem) on device 179:2.
[ 80.229585] Freeing init memory: 112K
modprobe: FATAL: Could not load
/lib/modules/2.6.36-00119-gb724297-dirty/modules.dep: No such file or
directory
modprobe: FATAL: Could not load
/lib/modules/2.6.36-00119-gb724297-dirty/modules.dep: No such file or
directory
** (process:327): WARNING **: Couldn't create log file
/var/log/ConsoleKit/history (No such file or directory)
init: ck-log-system-start main process (327) terminated with status 1
modprobe: FATAL: Could not load
/lib/modules/2.6.36-00119-gb724297-dirty/modules.dep: No such file or
directory
Entering interactive startup
Start service rsyslog (Y)es/(N)o/(C)ontinue? [Y]
}}}
There was no output on the panel, the interaction was on serial port only.
System booted normally after C to continue was provided.
I do not recall pressing keyboard keys during boot, but it might have
happened.
--
Ticket URL: <http://dev.laptop.org/ticket/10484>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system
More information about the Bugs
mailing list