Problem with copy existing system[SOLVED]

[mrhe]

Hi,
I have a working system, what I'm trying to do is to copy the whole system to another hardware.

Working system Info
processor

[Zucca]

You should maybe add -mtune=generic (or even -march=x86_64) to CFLAGS and then emerge -e @world on the old hardware.
Then move the files to the new system. Test it works. Change CFLAGS for the new system and emerge -e @world.
Yes. This method requires rebuilding of each package twice, but it's the safest way I've found.

Alternatively you could change CFLAGS to -mtune=generic -march=<whatever your new CPU likes>. Then emerge -e @world and move the files. On the new system just remove -mtune=generic. Now with every package you update or rebuild the "generic" CPU optimizations are removed.
_________________
..: Zucca :..
Gentoo IRC channels reside on Libera.Chat.
--

[Torro]

Zucca,

Do you happen to know if it's feasible to install stage3 in/on/over your current system, relocate it, reconfigure, and emerge -e @world?

[Zucca]

[Torro]

Zucca,

All right, thanks.
Maybe it'd be worthwhile if we (the Gentoo community) could take a look at the feasibility of creating a minimal system migration kit.

[Tony0945]

I'll have to differ with you, Zucca. This is how I create a new system. However, I do use only AMD processors which are backwards compatible (until Zen). I don't use rsync. I put the new hard drive into the old system, boot with sysrescuecd, mount both drives under /mnt and use "cp -a".
I then return the hard drive to the new system, boot the new system with sysrescuecd, chroot , change things like /etc/fstab and hostname ,rebuild the kernel using menuconfig to account for hardware differences, install the kernel and reboot. I generally do then "emerge -e @world" to tune the new system to the new CPU.
It's pretty much like moving the hard drive to new hardware. No need to do a new install.

Granted, the stage 3 or two emerge -e 's would be required if the new CPU is not backwards compatable.

How tedious and error prone is doing a fresh install, doing all the little things like setting the timezone, creating the users and passwords, installing X, the DE, all the applications et cetera.

[Tony0945]

[Zucca]

My method has always been

1. Adjust make.conf for the new and old system.
2. emerge -e @world (@system might be enough in most cases)
3. switch hardware / copy files to new hardware
4. remove the adjustments for the old system from make.conf
5. install bootloader if needed
6. edit /etc/fstab if needed
7. emerge -e @world (optional, unless you only did "emerge -e @system" earlier)

As I mentioned, I don't have enough knowledge of inner workings of Portage, but afaik untarring stage3 on the current system does install @system binaries which can be run on most hardware. If the portage database isn't a problem then one could skip the first emerge -e -operation by using stage3, I guess.
_________________
..: Zucca :..
Gentoo IRC channels reside on Libera.Chat.
--

[Hu]

Overwriting files outside Portage, especially when the overwriting package is not the same version, is asking for trouble. Use it only as a last resort to repair severely broken systems, and then only if you are prepared to clean up the inevitable mess. If your package manager is not broken, let it do the work for you.

[Tony0945]

Back to the original problem:

Mrhe, if I understand your situation correctly, you have copied the system, entered it via chroot, and rebuilt it with emerge -e world. This means that the hardware responded to your keyboard and possibly your mouse. Upon reboot you see a prompt. Is it an X11 DE login prompt or a virtual terminal prompt? At this point the keyboard does not respond. Is this correct?

1. If it's a DE prompt on Virtual Terminal 7, can you get to VT 1 by pressing CTRL-Alt-F1?

2. Is there any indication of error?

3. If you chroot back in, is there any sort of error or warning in /var/log/messages or any other file under /var/log?

4. If the problem involves X, while in the chroot, disable automatically entering X at boot. After rebooting without X, can you log in to Virtual terminal 1?

Don't worry about the network right now. Let's get the keyboard and display working first.

[mrhe]

[mrhe]

[Tony0945]

[Jaglover]

Emerging @system instead of @world should suffice, once on the new hardware you can do @world with -march=native.
_________________
My Gentoo installation notes.
Please learn how to denote units correctly!

[mrhe]

I try on old system

[Tony0945]

I think your problems are related to the virtualization not your kernel or software. Try installing a standard Ubuntu to the virtual machine and see if it acts the same.

[mrhe]

[mrhe]

It's a bit embarrassing but xhci was missing in the kernel. Thank You for Your help. To close

[Tony0945]

[Hu]

I always thought Kernel-Virtual-Machine was a terrible name for that Linux project, since the acronym collides with the much older Keyboard-Video-Mouse (multiplexer) usage, which is itself not a great name, but at least it was unique when it became popular.