[spoonlarry]

I have the latest build installed on a NVMe drive and I'm getting (Kernel panic - not syncing: unable to mount root) from what I've read this is usually caused by sata/IDE configuration which I'm not using, I don't have anything else to test with atm that isn't in use but is it even possible to run DD-WRT on a NVMe drive? If it is possible I cannot find anything about getting it to work, if anyone knows a way it would be appreciated, thank you.

[kernel-panic69]

What does the wiki say? https://wiki.dd-wrt.com/wiki/index.php/X86

[spoonlarry]

I read it, it doesn't mention anything about NVMe or M.2, I'm aware that it says PATA/SATA drives, and it also does not state it under limitations, what I was asking is if anyone knew of a way to get NVMe drives to work.

[kernel-panic69]

[spoonlarry]

Yes 47033 is the version I have on the NVMe drive, and I got it from the same index you linked. It does seem that the kernel allows for it so the question is no longer if it supports it I suppose. I scoured the internet for anyone trying to use an NVMe with dd-wrt and I found nothing, only some posts of people successfully using OpenWrt on a NVMe. The only solution I could find on here is making sure SATA mode was set to legacy IDE compatibility, but that's not applicable to M.2 drives, my motherboard doesn't even let me change the SATA modes cause I have no SATA devices attached to it. MSI H410I PRO Wifi

[kernel-panic69]

So, you are writing the image to the drive in a computer running Linux or Windows, image is written to the drive, and you plug it into the target machine, and it doesn't boot. Is that the gist of this scenario?

[spoonlarry]

Yes I followed the wiki for installing it on my windows machine then I put drive into my target machine and it reads it no problem but it just fails to mount. The drive is brand new too, nothing has ever been written to it before and I did not format on windows as I heard that could cause issues too. I could try Zeroing the drive and trying again, its a bit of a pain to get it out of my target machine and then put it back in my windows PC, I have no external methods of reading M.2 drives so I haven't tried that just yet but its the next thing I will do when I have some free time again if something else cannot be tried. https://imgur.com/a/el1W82W

[kernel-panic69]

It would be great to have the full console boot log, but I will contact the developer on this.

EDIT 07.11.21:

[spoonlarry]

I will have it later today, I haven't had much free time since I last played with it, also it will have to be a video recording, I'm not sure how to extract it as a log file, and pictures wont work either once it finishes and gives me the Kernel Panic and attempts to restart it just hangs there indefinitely never restarts.

[kernel-panic69]

I presume there is no UART header on the motherboard or no way to enable a USB serial console on this; I honestly have no direct experience with installing x86/x86_64 version of this firmware. Any means to have a boot log would be quite helpful in determining a resolution, though.

[spoonlarry]

sorry for taking so long I haven't gone back to this project until this morning. I zeroed the drive and flashed the newest version r47090 and the exact same thing is happening. I wish I could give you something better but it boots so fast and hangs at the end so I cant take pictures. https://imgur.com/a/NUUSdma

[kernel-panic69]

Totally unreadable and likely of no use. Would need to figure out how to run a serial console or capture a human readable boot log.

[BrainSlayer]

yeah unreadable.

but i believe i know the reason. nvme devices are not shown as /dev/sda etc. but /dev/nvme0 etc. need to look into this

[BrainSlayer]

try this image

https://forum.dd-wrt.com/dd-wrt_x64_public_vga.image

[spoonlarry]

Tried your image and now I'm getting this, different is good I hope at least. https://imgur.com/a/bCwFo9F