On 11/22/2020 05:25 PM, Michael wrote: > On Sunday, 22 November 2020 23:39:44 GMT the...@sys-concept.com wrote: >> OK, I used Gparted (Bootable usb) to copy partition from: >> Western Digital driver, usually: >> /dev/sda1 etc >> >> to M.2 SSD >> /dev/ nvme0n1p1 etc >> >> I can boot M.2 drive, but the x-server doesn't work (even though I use >> same graphical card). Network is not working (easy fix, new driver >> needs to be compiled IN) but there is a bigger problem. > > If you have cloned each partition from the old to the new disk, then the new > disk should work exactly as the old disk does. I mean, it should have the > same kernel, the same / filesystem, the same modules, etc. > > Since the new disk is an nvme drive, you will need additional drivers - > should > these not be available in the old kernel. > > >> Duplicating was easy, but when I try to recompile a kernel I get an error: >> >> make menuconfig >> HOSTCC script/kconfig/mconf.o >> <build-in> : internal compiler error: Illegal instruction >> >> Even if I try to run: emerge --info I get: >> Illegal instruction >> >> In addition my fstab doesn't look correct (but it works) >> /dev/sda1 /boot ext2 >> >> It should be something like: >> /dev/nvme0n1p1 /boot ext2 > > Do you have both disks connected to the MoBo when you're trying to boot from > the new disk?
Yes, they are both connected > Have you changed the UUIDs on the new partitions? Never used UUID in fstab. Do I just run: blkid|grep UUID and copy it to fstab. > Have you installed the boot manager on the new disk (if using MBR)? I just copied the whole MBR to a new disk and it worked, the system boots, but nothing can be compiled.
