After installation the system boots to recovery mode

I succesfully built the devsus images from Devuan 1.0, resulting in the following file (and corresponding MD5 checksum):

bbccae6213664fabde526b868150eeac  devuan-jessie-c201-libre-2GB.img

After flashing it to a USB key I was able to boot from it, and found the 16GB image to flash on internal memory. I flashed it as instructed:

# dd if=/devuan-jessie-c201-libre-16GB.img of=/dev/mmcblk0 bs=50M

After rebooting I get to a black screen with the following text:

Welcome to recovery mode!

Useful key combinations:
- Ctrl + D: Enable developer mode (if possible)

Please insert an external recovery media

I am not sure what this is expected to boot into, what would be the next steps normally? There is no mention of it in the documentation, it seems I may have missed a step (or more).

Thanks for any help or clarification.

Few suggestions:

Have you enabled developer mode and flashed Libreboot?
Run fdisk -l. Is the SSD exactly 15762194432 bytes?
Run cgpt show. Do you see any errors?
Do you see any errors in dmesg, during the dd of both images (2GB/16GB) or after booting through the 2GB one?
Try to dd the 16 GB image without the bs=50M.

Yes, Libreboot was installed without issue.

I will test the rest later today, many thanks for the suggestions.

So I had some time to verify what you asked about:

No, /dev/mmcblk0 is 15758000128 bytes
cgpt show /dev/mmcblk0 throws GPT_ERROR_INVALID_HEADERS
There is mmcblk0: unknown partition table
Tried that with the same results

I changed line 117 of devsus.sh to match the size of the SSD my system shows (15758000128/512 = 30777344), as follows:

create_image devuan-jessie-c201-libre-16GB.img $indev 512 30777344 $inmnt

I am generating the new image, flashing to USB, etc. and will report back here.

Thanks for the willingness to perform thorough investigation :)

Now we know that there are at least two SSD sizes! I have a 2GB C201 from 2015 and a 4GB one which I bought very recently for the sole purpose of testing Devsus - both have exactly the same SSD size and I double-checked the manufacturing date (to make sure I have both hardware revisions, in case something changed in component sourcing or the manufacturing process since 2015, etc').

I'm curious what's the root cause of the problem we're seeing on your machine.

Thanks for your patience :) Your hints helped.

I just bought this system a few days ago, if you have a recent libreboot maybe we can compare dmidecode / other info to determine if they're the same.

What Libreboot version are you using?

Latest stable: libreboot-r20160907 from https://mirror.math.princeton.edu/pub/libreboot/stable/20160907/rom/depthcharge/

Could someone help me with setting up wi-fi? I followed the instructions here: https://linuxcommando.blogspot.com/2013/10/how-to-connect-to-wpawpa2-wifi-network.html, but I keep getting kernel panics when running # wpa_supplicant -B -D wext -i wlan0 -c /etc/wpa_supplicant.conf.

Try wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf.

I tried that, but I still get kernel panics. By the way, I wanted to let you know that I was using a USB wireless adapter found here: https://www.thinkpenguin.com/gnu-linux/penguin-wireless-n-usb-adapter-gnu-linux-tpe-n150usb.

Could you, perhaps, type out the exact steps that you used to connect your Asus C201 to wi-fi? It would be greatly appreciated.

wpa_passphrase $ssid $passphrase > /tmp/1
wpa_supplicant -c/tmp/1 -iwlan0 -B
dhclient wlan0

I entered these instructions exactly, but the command wpa_supplicant -c/tmp/1 -iwlan0 -B hasn't returned yet, and it's been about two hours since I ran it. Is that normal? It's giving several messages like this:

dwc2 ff540000.usb: dwc2_hc_chhltd_intr_dma: Channel $number - ChHtld set, but reason is unknown.

Followed by dwc2 ff540000.usb: hcint 0x00000002, intsts 0x04400009

wpa_supplicant should exit immediately because of -B.

It technically does exit immediately, but shortly after, before I type in anything else, the aforementioned code starts appearing on the screen, as if the command's still running.

I got the wi-fi to connect; apparently, the problem is with my adapter, because using another adapter allowed me to instantly connect.

@MagicFab, I am having the exact same problem: I got to recovery mode after doing the dd to the internal drive. Did you solve that? If so, how did you manage?

I was wondering if there has been any progress made with this thread. I have the live boot of devsus working but after i tried dd to internal memory it boots to recovery mode. Just like MagicFab i am getting mmcblk0: unknown partition table. My SSD is 15762194432 bytes. I have tried dd without the bs=50M and it still doesn't work. Any assistance would be greatly appreciated.

I'm also having this issue when building from either mainline or master branches.

I seem to have the standard size SSD as jogree does. Libreboot r20160907 is installed.

cgpt show /dev/mmcblk2 gives:

WARNING: Primary GPT header is being ignored

booting from usb, dmesg shows:

GPT:Primary header thinks Alt. header is not at the end of the disk.
GPT:4095999 != 3116287
GPT:Alternate GPT header not at the end of the disk.

fdisk -l /dev/mmcblk2 gives:

The primary GPT table is corrupt, but the backup appears OK, so that will be used.

fdisk shows /dev/mmcblk2p2 starts 737727 ends 30785502

#10 After installation the system boots to recovery mode