Query re nvme addr in armbian boot.cmd

[mcfo]

Hi, SD card did not load Armbian_25.8.1_Orangepi5_trixie_current_6.12.41_xfce_desktop. I noticed that in boot.cmd line 9 , rootdev is defined as /dev/mmcblk0p1. Should that be  /dev/mmcblk0n1 or  /dev/mmcblk0n1p1?

I note that this file should not be edited and the armbianEnv.txt only refers to rootdev=UUID=7e27c862-0a39-41cd-891e-7d77ff7968fd.

 

Is this an error or am I off course?  If so where do I correct it?

cheers 

[mcfo]

Also in 25.8.2

[mcfo]

Belay that. I copied trixie to ssd and it fired up just fine without sd in slot.

However, I dont yet understand nvme addressing requirements, but I can now read up on it..  so, for me, solved. Thanks

 

[The Tall Man]

Type in the command:

lsblk

 

There, addressing the nvme should be obvious.

Edited October 5 by The Tall Man

[mcfo]

Thanks for the reply, Tall Man. In a way, that was the point. My experience is really only with my home network use and with nvme information displayed by  linux tools which seem to insist on the xnypz suffix on the root word nvme.

 

I continued reading up on the general topic overnight and it seems that in the dtb tree world, the focus is on structuring cohesion and delaying actuating instances, so I am guessing different (more general) descriptors are used. My query was whether the precise descriptor was correct as I could see other options possible, one of which had, I think, popped up elsewhere. Since I had seen other reports of difficulties in loading systems to devices, I thought it a remote possibility that a typo had crept in. 

I still havent found anything definitive in my reading re the formats of the abstractions in the dt stack.

I am interested in knowing about this but I as my Armbian is up and running now, and I identified the actual issue for me was a sd card error, the pressure is off .

So, I hope this ramble was not too tedious and I do appreciate that you took the time to answer, and again, thanh you

cheers