On 13 September 2015 at 18:34, Toby Slight <[email protected]> wrote:

> OK, so I finally managed to boot the 12th's snapshot on an EFI only T430.
> Weirdly enough one time it just worked, but when I tried again I got the
> same results as the 9th's snapshot installer.
>
> It seems that sometime the bootblocks get loaded, sometimes not, 9 times
> out of 10 I get http://i.imgur.com/Apfoe8r.jpg, then suddenly it will
> just work. Any idea why a successful boot appears to be so random? Also, is
> it normal that the resolution is a tiny cropped box in the middle of the
> screen?
>
> Anyway, once I'd apparently (and very much obliviously) cast the right
> mystical invocations to successfully boot the installer, I followed Chris'
> very clear and useful instructions, with some slight alterations, to do my
> usual encrypted softraid0 setup on one disk.
>
> One point I should note is that the newfs_msdos command was not available
> in the installer's path, I had to wait until after install and then call
> the binary from the installed sets - ie) /mnt/sbin/newfs_mkdos.
>
> Anyway, apart from that tiny hiccup, everything else worked as expected.
> However when I tried to boot the new install I ended up almost immediately
> at the ddb prompt, as pictured below:
>
> http://i.imgur.com/1sfqYQ8.jpg
>
> http://i.imgur.com/OcRNUyI.jpg
>
> I'm not a developer and don't know how to use ddb, so is there anything
> else I could do to provide you guys information and help debug the issue?
>
> When I rebooted again it seemed the process hung in a slightly different
> way:
>
> http://i.imgur.com/1Am1qNB.jpg
>
> Hope some of that might be helpful to some of you EFI wizards, and if not,
> I haven't nuked the disk yet, so if there's any ddb poking you'd like me to
> do, let me know. Cheers!
>

Perhaps this may also be of interest - I get yet again different results
when booting the sp kernel from the bootloader prompt (the boot process got
a lot further this time strangely enough):

http://i.imgur.com/bAE0qWp.jpg

http://i.imgur.com/sg7Rxgv.jpg


-- 
0x2b || !0x2b

Reply via email to