Kernel Panic on real hardware. (not a dupe)

[SamHep0803]

I keep getting the same error as with the other issue, but the only difference is that I'm trying it on real hardware.

To be specific a PC with windows installed on it. However, I'm having trouble getting it to even boot as I'm getting a kernel panic. Also, I'm using the Makefile provided.

To be honest, I have no clue what to do.

Thanks, Sam.

[MichielDerhaeg]

My guess would be that the kernel doesn't have the required components built in to support your system. But I can only speculate without more information. What are you using to boot? What does the kernel panic say exactly?

…

On 26/05 05:21, SamHep0803 wrote: I keep getting the same error as with the other issue, but the only difference is that I'm trying it on real hardware. To be specific a PC with windows installed on it. However, I'm having trouble getting it to even boot as I'm getting a kernel panic. To be honest, I have no clue what to do. Thanks, Sam. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: #21

[SamHep0803]

As I said, it's the same error as the last kernel panic issue. However, It works in qemu, just not my test system.

kernel panic - not syncing vfs unable to mount root fs on unknown-block (0 0)

There.

[SamHep0803]

I'm using a custom build system

[SamHep0803]

Would be grateful for a reply?

[MichielDerhaeg]

Sorry, I have very little time these days. I may be overlooking something, but which previous kernel panic issue are you referring to?

…

On 26/05 10:22, SamHep0803 wrote: Would be grateful for a reply? -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: #21 (comment)

[SamHep0803]

As issued in #8 .

[MichielDerhaeg]

Ah, i see, could you tell me what kind of system you're currently using to build and could you give me the output of 'fdisk -l image'?

…

On 26/05 11:12, SamHep0803 wrote: As issued in #8 . -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: #21 (comment)

[SamHep0803]

I'm currently using Ubuntu 18.04 LTS and fdisk shows:

Disk build-linux/image: 100 MiB, 104857600 bytes, 204800 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xb8e75e52

Device             Boot Start    End Sectors Size Id Type
build-linux/image1       2048 204799  202752  99M 83 Linux

[MichielDerhaeg]

It might not be able to interpret PARTUUIDs, i suggest editting gen_image.sh to set root=PARTUUID=..
to root=/dev/sda1 or root=/dev/sdb1, whatever works, and trying again.

[SamHep0803]

ok

[MichielDerhaeg]

Or just by mounting, and manually editting /boot/grub/grub.cfg, whatever floats your boat.

[SamHep0803]

So should I set it to what my USB drive is mounted at now?

[MichielDerhaeg]

If you're using the same system to boot it, yes. It might be slightly non-deterministic but it's probably right.

[SamHep0803]

No, I'm not using the same system. It's a different system with a windows SSD in it.

[MichielDerhaeg]

In that case you'll have to do some trial and error.

[SamHep0803]

i seem to be getting the same error o
in vbox now.

[MichielDerhaeg]

It's hardware specific, so trying it first in vbox has no use.

[SamHep0803]

the only reason im trying it in vbox is bc it was working before

[SamHep0803]

So, I booted it up on my machine again only to find out I have another kernel panic. Buuut it's a different error. I can't see the whole error but the last line reads.

[ 0.989140] ---[end trace efb985e050e98130 ]---

[MichielDerhaeg]

Have you tried other options? You might have selected the Windows disk. Also, it just occurred to me that the kernel configuration you used might not have the required components enabled to boot from your particular system and USB drive. Configuring that correctly might be difficult for someone who hasn't done that before.

[MichielDerhaeg]

Usually kernels are built to support all sorts of hardware, but in this case it's mainly to support VM's.

[SamHep0803]

Hmm I’m sure I didn’t select my windows drive and even after changing the gen-image.sh file my vm still didn’t work. I’m stumped at this point.

[MichielDerhaeg]

Well, so am I, I'm guessing it's a kernel configuration issue. And those sorts of things are way to hard to diagnose like this :S

[SamHep0803]

Ugh... Well I’ll have to call it a day till I get back to my PC, do you have discord?

[MichielDerhaeg]

Yep, send me a mail about it when you want to get in touch.
I'm going to close this issue for now.