Boot from USB Causes Kernel Panic on gru-kevin #255

New issue

Closed

opened 2020-12-05 10:55:45 +01:00 by polarisfm · 5 comments

polarisfm commented

2020-12-05 10:55:45 +01:00

(Migrated from github.com)

Attempting to boot PrawnOS arm64 on gru-kevin causes the kernel to panic. I have tried this on multiple USB flash drives (both USB C and USB A with an adapter) and it causes the same issue each time.

This occurs on 1.1, 1.2, and 1.3. I really hope this isn't a silly configuration issue, I followed the instructions quite carefully.

switch_root fails because it fails to find new_root but I'm really not familiar enough with the boot process to figure out why this is happening without some level of guidance. The fact this only seems to be happening to me (at least judging my the other reported issues) makes me think I've just done something dumb, so I'm really sorry if that's the case. I'm very new to ARMv8 computing and even newer to using machines that use depthcharge.

Just to be clear, I am not running Coreboot (yet).

A photo of the error is attached below. It is mostly the same on each OS version (besides the things you would expect to be different like the kernel version).

Attempting to boot PrawnOS arm64 on gru-kevin causes the kernel to panic. I have tried this on multiple USB flash drives (both USB C and USB A with an adapter) and it causes the same issue each time. This occurs on 1.1, 1.2, and 1.3. I really hope this isn't a silly configuration issue, I followed the instructions quite carefully. `switch_root` fails because it fails to find `new_root` but I'm really not familiar enough with the boot process to figure out why this is happening without some level of guidance. The fact this only seems to be happening to me (at least judging my the other reported issues) makes me think I've just done something dumb, so I'm really sorry if that's the case. I'm very new to ARMv8 computing and even newer to using machines that use depthcharge. Just to be clear, I am not running Coreboot (yet). A photo of the error is attached below. It is mostly the same on each OS version (besides the things you would expect to be different like the kernel version). ![panic](https://user-images.githubusercontent.com/31363321/101239310-205a5d80-36ac-11eb-8289-add6fbb1508a.jpg)

polarisfm commented

2020-12-07 19:09:20 +01:00

(Migrated from github.com)

Update: Booting from a microSD card works fine and allows installation to other attached media (internal and external work well).

This issue seems to be specific to USB booting.

Update: Booting from a microSD card works fine and allows installation to other attached media (internal and external work well). This issue seems to be specific to USB booting.

SolidEva commented

2020-12-09 01:34:53 +01:00

(Migrated from github.com)

Interesting! Thank you for the detailed report @polarisfm
Let me look into this and get back to you.

FYI, unless you specifically reflashed your kevin, you are already running coreboot with depthcharge :)

Interesting! Thank you for the detailed report @polarisfm Let me look into this and get back to you. FYI, unless you specifically reflashed your kevin, you are already running coreboot with depthcharge :)

👍 1

polarisfm commented

2020-12-09 02:48:50 +01:00

(Migrated from github.com)

Thanks!

Also my bad, I meant deblobbed Coreboot. From what I can tell it ships with some blobs in ARM TPM but based on my experience with another RK3399 machine they aren't hard to remove and don't significantly impact usability.

Edit: I marked this as an off topic response for (hopefully) obvious reasons. I didn't remove it because I thought the information may be useful to someone at some point.

Thanks! Also my bad, I meant deblobbed Coreboot. From what I can tell it ships with some blobs in ARM TPM but based on my experience with another RK3399 machine they aren't hard to remove and don't significantly impact usability. Edit: I marked this as an off topic response for (hopefully) obvious reasons. I didn't remove it because I thought the information may be useful to someone at some point.

SolidEva commented

2020-12-09 06:57:30 +01:00

(Migrated from github.com)

This behavior seems to be the result of a race condition. The kernel seems to not be mapping USB devices quick enough, meaning when we try to get the list of connected devices using blkid the usb flash drive we are booting from is missing!

This behavior seems to be the result of a race condition. The kernel seems to not be mapping USB devices quick enough, meaning when we try to get the list of connected devices using `blkid` the usb flash drive we are booting from is missing!

SolidEva commented

2020-12-09 07:32:08 +01:00

(Migrated from github.com)

Created release with this fix: https://github.com/SolidHal/PrawnOS/releases/tag/v1.3.1