Hi, Just a quick update regarding how it's going with bootmenu and kexec. I have successfully gotten a kernel to kexec using bootmenu-n900, kexec-tools and kernel-power from extras-devel.
There are currently two blockers to dual-boot in this fashion and maybe others have insight to these as well: * DSS2/DISPC complains heavily when being re-initialised it looks like: [ 24.949859] regulator_init_complete: incomplete constraint [ 24.957458] Waiting 5sec before mounting root device... [ 24.962829] omapdss DISPC error: OCP_ERR [ 24.979614] omapdss DISPC error: OCP_ERR (OCP_ERR repeating over and over) * Biggest blocker: external MMC access does not seem to reinitalise properly, meaning we cannot boot off external MMC. Internal MMC works though.. [ 26.993621] mmc1: new high speed MMC card at address 0001 [ 27.011322] mmcblk0: mmc1:0001 MMC32G 29.8 GiB [ 27.020263] mmcblk0: [ 27.034606] p1 p2 p3 [ 27.332946] mmc0: host does not support reading read-only switch. assuming write-enable. [ 27.343750] mmc0: new high speed SDHC card at address 4b95 [ 27.359436] mmcblk1: mmc0:4b95 SD04G 3.69 GiB [ 27.366912] mmcblk1: [ 27.378814] mmcblk1: retrying using single block read [ 27.393218] mmcblk1: error -110 sending status comand [ 27.398437] mmcblk1: error -110 sending read/write command, response 0x0, card status 0x0 [ 27.412567] mmcblk1: error -110 transferring data, sector 0, nr 8, card status 0x0 [ 27.423583] end_request: I/O error, dev mmcblk1, sector 0 [ 27.440185] mmcblk1: error -110 sending status comand [ 27.445373] mmcblk1: error -110 sending read/write command, response 0x0, card status 0x0 [ 27.461486] mmcblk1: error -110 transferring data, sector 1, nr 7, card status 0x0 [ 27.473449] end_request: I/O error, dev mmcblk1, sector 1 [ 27.492065] mmcblk1: error -110 sending status comand [ 27.497283] mmcblk1: error -110 sending read/write command, response 0x0, card status 0x0 [ 27.515441] mmcblk1: error -110 transferring data, sector 2, nr 6, card status 0x0 [ 27.528442] end_request: I/O error, dev mmcblk1, sector 2 [ 27.549102] mmcblk1: error -110 sending status comand [ 27.554321] mmcblk1: error -110 sending read/write command, response 0x0, card status 0x0 [ 27.574127] mmcblk1: error -110 transferring data, sector 3, nr 5, card status 0x0 [ 27.587554] end_request: I/O error, dev mmcblk1, sector 3 [ 27.608581] mmcblk1: error -110 sending status comand [ 27.613830] mmcblk1: error -110 sending read/write command, response 0x0, card status 0x0 [ 27.633911] mmcblk1: error -110 transferring data, sector 4, nr 4, card status 0x0 [ 27.647674] end_request: I/O error, dev mmcblk1, sector 4 [ 27.669372] mmcblk1: error -110 sending status comand [ 27.674621] mmcblk1: error -110 sending read/write command, response 0x0, card status 0x0 [ 27.695068] mmcblk1: error -110 transferring data, sector 5, nr 3, card status 0x0 [ 27.708831] end_request: I/O error, dev mmcblk1, sector 5 [ 27.730499] mmcblk1: error -110 sending status comand [ 27.735748] mmcblk1: error -110 sending read/write command, response 0x0, card status 0x0 [ 27.756195] mmcblk1: error -110 transferring data, sector 6, nr 2, card status 0x0 [ 27.769958] end_request: I/O error, dev mmcblk1, sector 6 [ 27.791625] mmcblk1: error -110 sending status comand [ 27.796813] mmcblk1: error -110 sending read/write command, response 0x0, card status 0x0 [ 27.817230] mmcblk1: error -110 transferring data, sector 7, nr 1, card status 0x0 [ 27.830993] end_request: I/O error, dev mmcblk1, sector 7 [ 27.842559] Buffer I/O error on device mmcblk1, logical block 0 [ 27.865081] mmcblk1: retrying using single block read [ 27.886230] mmcblk1: error -110 sending status comand [ 27.891418] mmcblk1: error -110 sending read/write command, response 0x0, card status 0x0 [ 27.911651] mmcblk1: error -110 transferring data, sector 0, nr 8, card status 0x0 [ 27.925445] end_request: I/O error, dev mmcblk1, sector 0 [ 27.946990] mmcblk1: error -110 sending status comand [ 27.952178] mmcblk1: error -110 sending read/write command, response 0x0, card status 0x0 [ 27.972412] mmcblk1: error -110 transferring data, sector 1, nr 7, card status 0x0 [ 27.986206] end_request: I/O error, dev mmcblk1, sector 1 [ 28.007751] mmcblk1: error -110 sending status comand [ 28.013000] mmcblk1: error -110 sending read/write command, response 0x0, card status 0x0 [ 28.033264] mmcblk1: error -110 transferring data, sector 2, nr 6, card status 0x0 [ 28.047088] end_request: I/O error, dev mmcblk1, sector 2 [ 28.068695] mmcblk1: error -110 sending status comand [ 28.073913] mmcblk1: error -110 sending read/write command, response 0x0, card status 0x0 [ 28.094238] mmcblk1: error -110 transferring data, sector 3, nr 5, card status 0x0 [ 28.108062] end_request: I/O error, dev mmcblk1, sector 3 [ 28.129669] mmcblk1: error -110 sending status comand [ 28.134918] mmcblk1: error -110 sending read/write command, response 0x0, card status 0x0 [ 28.155151] mmcblk1: error -110 transferring data, sector 4, nr 4, card status 0x0 [ 28.168945] end_request: I/O error, dev mmcblk1, sector 4 [ 28.190704] mmcblk1: error -110 sending status comand [ 28.195892] mmcblk1: error -110 sending read/write command, response 0x0, card status 0x0 [ 28.216400] mmcblk1: error -110 transferring data, sector 5, nr 3, card status 0x0 [ 28.230224] end_request: I/O error, dev mmcblk1, sector 5 [ 28.251983] mmcblk1: error -110 sending status comand [ 28.257202] mmcblk1: error -110 sending read/write command, response 0x0, card status 0x0 [ 28.277679] mmcblk1: error -110 transferring data, sector 6, nr 2, card status 0x0 [ 28.291473] end_request: I/O error, dev mmcblk1, sector 6 [ 28.313201] mmcblk1: error -110 sending status comand [ 28.318450] mmcblk1: error -110 sending read/write command, response 0x0, card status 0x0 [ 28.338928] mmcblk1: error -110 transferring data, sector 7, nr 1, card status 0x0 [ 28.352691] end_request: I/O error, dev mmcblk1, sector 7 [ 28.364257] Buffer I/O error on device mmcblk1, logical block 0 [ 28.386535] unable to read partition table An alternative to dual-booting is simply using flasher and having the system on external SD: flasher -k <our 2.6.33 kernel> -l -b - not pretty, but it works. I have agreed with Roger that our primary kernel functions (sound, etc) are first priority before we start fixing the kexec issues. Regards, Carsten Munk _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
