I've just done a successful "copy" of my Mint18 instal to my whizzy new nvme/M.2 "on-the-m/b" ssd but I foolishly didn't situate the new partition in the exact same place on the new M.2drive as it was on the original (ancient ) sata3 ssd.
And so, of course , the Suspend function isn't working properly - it suspends OK but can't resume itself - all that I get is a black screen and I then have to get to a command prompt and do a Reboot (or just press the Restart button) to get the OS back again.
Which, with the whizzbang new nvme drive isn't too much of a problem (except that the UEFI bios does seem to take a helluva lot longer to go through its POST than on any m/b I've yet had).
Because, I guess, the "resume from Suspend" function is looking for a different "target" to resume to - ie I spose it's looking for the target in the "original" Mint18 OS that I copied.

Does anyone know how to change the "suspend target" - ie where in the filesystem to find it. I've had a bit of a look in /systemd etc etc but can't seem to find anything that might be appropriate.
I guess that I need to be able to change the target for the resume/wake function to point to the first sector of the new (& different) partiton on the nvme drive where the "copy" is running.

The alternative is just to copy my /home folder somewhere and just do a fresh new install - but that involves a lot of time re-installing everything etc etc so just changing the Resume target by editing a file somewhere in the filesystem seems like a simpler way to get the Suspend function working OK again.

Any suggestions, uplines??

TIA
Cheers
PaulMW

Asus ROG Strix 470-F Gaming m/b
AMD Ryzen5 2400G
8GB of Corsair Dominator 3200 RAM
Samsung 256GB 970EVO nvme M.2 boot drive
Corsair CS650M modular p/supply
Assorted whirlygig hdds for bulk storage

"cat /proc/cmdline" - adjust as required.

Thanx for that - but which of all that hex stuff there represents the starting sector that I should be altering??
And I see that on this system it's referring to a 4.14 kernel - and I early on made a point of installing a 4.17 one to (hopefully) mitigate the Spectre and Meltdown potential dangers.

I'm readingthis/replyingon the box that I originally took the "copy" from; and after going into GParted I can see that that line of hex is just the UUID of the ssd I took the copy from.
Should that instead be referring to the UUID of the nvme drive on the new box??

And what does the "cat" part of your reply refer to?

Read the manpage.
Let's see that output - the change will (likely) need to be made to your grub parameters. Let's see this as well

I got a bit confused about the kernel I was running on each machine - the older one that I took the "copy" offof was running a 4.14 kernel - it's the new machine that I had installed the 4.17 kernel on as soon as I put that Mint18 copy onto it.
The nvme drive does seem to cause a few odd "hiccups" here and there - the Mint18 instal starts out with a halfpage of assorted error messages for a few seconds before it then boots up OK - in about 10seconds or so total - ie quite noticeably quicker than the ssd it was installedon/copiedfrom.

Here's the /proc/cmdline on the new 2400G machine:

The line of hex in that ^ is the UUID of the partition on the nvme where the Mint18 copy was put - since /proc/cmdline does seem to be a dynamically altering file - as reading the manpage made clear to me. And with "only" 8GB of RAM I'd thought it a good idea to have a swap partition too - which I did - made it 10 or so GB in size.

Do you think that in the end it might be simplest to just copy my /home/.... onto another hdd or ssd and just do a new, "clean" install - and then copy the /home/.... page back and re-install everything??

I had just thought that somewhere in the filesystem that there must be a file with the sector on the UUID that the "resume from Suspend" function would refer to that I could alter to suit the new (&slightly different) partition structure on this new box.

TIA
Cheers
PaulMW
(Aotearoa/NZ)

Sorry - my bad. I made some assumption that are obviously not valid for Mint. Let me go find a system I can check.

No worries .
I'vw long been quite set on the various Mints - I want a Start button in the bottom left corner, thanx! - and not this not-so-configurable taskbar-across-the-top bizzo that Ubuntu seems to have now acquired - ie Gnome 2 for me,thanx!

On thinking about it I think the best option is just to save the /home/.... partition, wipe it all, and do a clean re-install. And then copy back whatever files and directories I want from the saved ones.

Because of the bunch of (mostly ACPI) error messages that initially come up and the fact that it occasionally does a total freeze - without even a (ctrl+Alt+F2) command prompt login possibility - it would suggest that this OS "copy" has a few "gears slipping" somewhere - ie some software calls seem to be going to the wrong addresses etc etc. And, of course, the lack of the Suspend option too.

One thing I have enjoyed about linuxes (until now!) has been the ability for any given instal to run +/- as well on whatever hardware it gets put onto - rather than having to do an "image copy" or the sysprep bizzo that one has to do with a winDoze (7) instal.
But it may be that the new (to me! ) M.2 nvme sdd has complicated things for linuxes in this area now .

So anyway thanx again for all your tips syg00

Clean re-install coming up!

Cheers
PaulMW

Thought I should finish off what I started in case anyone else comes across this problem - and a few others indeed are, so it seems.
It seems that either a new m/b UEFIBIOS and/or the linux kernel itself are what is possibly/hopefully going to have to change/update to fix this issue .

After doing the clean re-install of Mint18 yesterday it still won't resume from Suspend - and exactly the same halfscreen of (ACPI & AMD-Vi) errormessages are showing on bootup .
As a small consolation at least it's not doing the occasional "freeze" which the cloned "copy" version was doing - but that's about all that I've gained from quite a few hours of work!

To even get a booting M18 took a couple of hours of trying out various things: it would mostly install apparently OK but would crash when trying to write the Grub. I tried the install process twice - all the OS's files were there but it wouldn't even boot offof a Grub2 CD - it would just wind up with a "kernel panic" or somesuch.
It seems that installing to an nvme drive may be "a bridge too far" for the M18 install process.
The eventual solution was to use a BootRepairDisc which, after a fair bit of root-command-line stuff, succeeded in getting a working Grub and a working M18 instal. It seemed to involve purging and re-writing some sort of Grub - and maybe the kernel too.
Once having got to that point (ie a running OS/desktop) it was, of course, easy enough to configure everything to how I like it.
However to even get to be able to "see" the nvme drive involved first having to disconnect the whirlygig drive/s! - otherwise Gparted wouldn't even "see" it - and so I wasn't even able to format/clear the two potential linux partitions.

But after a bit of DuckDuckGo-ing it has become clear that this is a common enough bug/flaw in any 2400G+nvme setup. Apparently one has to have at least a 4.15kernel to get the integrated Ryzen5 2xxxG graphics working OK! - and others are suggesting using rc kernels etc etc to try and get aroung this glitch.
And, somewhere along the line, it became apparent to me that the bios on my Asus ROG Strix X-470-F m/b, good though it is (but very slo-o-o-o-w!), is still at the somewhat "flaky" stage.

So I will just have to live with being unable to use the Suspend function in my Mint18 instal until some later kernel and/or updated bios fixes this problem/bug.
At least winDoze10's Sleep function seems to be working reasonably well it seems.

It seems to me that these nvme drives, amazingly fast though they are, are maybe just a little bit ahead of the rest of the hardware and the software I am trying to use. Everything will catch up shortly I would guess .

But overall I have to say that I'm still quite pleased with this 2400G+nvme setup that I've built .