Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.os.linux > #39313 > unrolled thread

How to Migrate Mint18 to another motherboard?

Back to article view | Back to alt.os.linux

Contents

  How to Migrate Mint18 to another motherboard? Vaso <branko.vasiljevSPAM@xnet.hr> - 2016-09-28 17:26 +0200
    Re: How to Migrate Mint18 to another motherboard? Mike Easter <MikeE@ster.invalid> - 2016-09-28 09:26 -0700
      Re: How to Migrate Mint18 to another motherboard? Wildman <best_lay@yahoo.com> - 2016-09-28 12:42 -0500
        Re: How to Migrate Mint18 to another motherboard? Mike Easter <MikeE@ster.invalid> - 2016-09-28 10:50 -0700
          Re: How to Migrate Mint18 to another motherboard? Paul <nospam@needed.invalid> - 2016-09-28 17:50 -0400
    Re: How to Migrate Mint18 to another motherboard? "J.O. Aho" <user@example.net> - 2016-09-28 18:44 +0200
      Re: How to Migrate Mint18 to another motherboard? Vaso <branko.vasiljevSPAM@xnet.hr> - 2016-09-28 19:16 +0200
        Re: How to Migrate Mint18 to another motherboard? Z <z@ajbchqjwrn.com> - 2016-09-28 19:20 +0200
        Re: How to Migrate Mint18 to another motherboard? "J.O. Aho" <user@example.net> - 2016-09-28 21:45 +0200
    Re: How to Migrate Mint18 to another motherboard? Alfred Myford <myford100@yahoo.com> - 2016-09-28 14:41 -0500
    Re: How to Migrate Mint18 to another motherboard? Mike Easter <MikeE@ster.invalid> - 2016-09-28 12:52 -0700
    Re: How to Migrate Mint18 to another motherboard? Marcel Mueller <news.5.maazl@spamgourmet.org> - 2016-09-29 07:46 +0200
      Re: How to Migrate Mint18 to another motherboard? William Unruh <unruh@invalid.ca> - 2016-09-29 08:09 +0000
        Re: How to Migrate Mint18 to another motherboard? Kirk_Von_Rockstein <Kirk_Von_Rockstein@nowhere.invalid> - 2016-09-29 12:53 +0000
        Re: How to Migrate Mint18 to another motherboard? Marcel Mueller <news.5.maazl@spamgourmet.org> - 2016-09-29 19:15 +0200
          Re: How to Migrate Mint18 to another motherboard? Jasen Betts <jasen@xnet.co.nz> - 2016-09-30 19:55 +0000

#39313 — How to Migrate Mint18 to another motherboard?

I've installed Mint 18.
Can I simply connect  that disk to another motherboard,
or I should to Install Mint again?

Thanks

-- 
Branko Vasiljev:
Vise se NIkada Nitko NECE Na Softveru
Obogatiti Kao g-din Bill Gates!!

[toc] | [next] | [standalone]

#39314

Vaso wrote:
> I've installed Mint 18.
> Can I simply connect  that disk to another motherboard,
> or I should to Install Mint again?

I predict it will work just fine, based on my 'research' (searching and 
reading, not personal experience) with people installing various distros 
to USB thumbdrives and using the installed distro thumb on alternate 
hardware/s.

Altho' an installation doesn't have the same algorithms for 'sussing' 
out the hardware, it seems to do OK.

If it doesn't work out as 'predicted', there's always Plan B.


-- 
Mike Easter

[toc] | [prev] | [next] | [standalone]

#39321

On Wed, 28 Sep 2016 09:26:55 -0700, Mike Easter wrote:

> Vaso wrote:
>> I've installed Mint 18.
>> Can I simply connect  that disk to another motherboard,
>> or I should to Install Mint again?
> 
> I predict it will work just fine, based on my 'research' (searching and 
> reading, not personal experience) with people installing various distros 
> to USB thumbdrives and using the installed distro thumb on alternate 
> hardware/s.
> 
> Altho' an installation doesn't have the same algorithms for 'sussing' 
> out the hardware, it seems to do OK.
> 
> If it doesn't work out as 'predicted', there's always Plan B.

I believe the most likely problem might be video.  It might be
necessary to delete xorg.conf.

-- 
<Wildman> GNU/Linux user #557453
The cow died so I don't need your bull!

[toc] | [prev] | [next] | [standalone]

#39322

Wildman wrote:
> I believe the most likely problem might be video.  It might be
> necessary to delete xorg.conf.

As long as we are 'guessing' here...

If the graphics don't 'work' on boot, one could do a little grub boot 
command intervention, the way we/I have to do sometimes for lives.

-- 
Mike Easter

[toc] | [prev] | [next] | [standalone]

#39332

Mike Easter wrote:
> Wildman wrote:
>> I believe the most likely problem might be video.  It might be
>> necessary to delete xorg.conf.
> 
> As long as we are 'guessing' here...
> 
> If the graphics don't 'work' on boot, one could do a little grub boot 
> command intervention, the way we/I have to do sometimes for lives.
> 

Xorg.conf isn't normally used on modern systems.

People insert one of those, if they need to override
Xorg behavior. I use that mechanism all the time here,
for Linux VMs on this machine. I have a "favorite
Xorg.conf" I use, with some mode lines in it.

A question I would have, is whether it's better to return
the video settings to "system defaults", instead of using
the tainted drivers. Go back to Nouveau instead of NVidia.
The NVidia cards used to be split into three groups,
and an appropriate file used for your current card.
I don't know if dynamic detection is clever enough
to do the right thing in all cases (like, if the new
computer has an NVidia card that falls under a different
binary file).

As proof it can do the right things, the LiveCD works
out of the box, on any platform you plug it into. Xorg
figures out the hardware, and what driver to use, than
plays with the resolution settings until it has a
set of resolutions the user sees in "Xrandr and friends".
And that would be my reason for attempting to return
to system defaults, before moving an install disk.

If you never customized your video at all, and just
let the system detect it all by itself, you likely
have nothing to fear from moving a disk. I've moved
a disk from the test machine over to this machine,
and booted, and no problemo. But then, I didn't
use any better video driver, and just left things
the way the system set them up. I'm a chicken I guess :-)

I would be surprised if you would find an actual
xorg.conf file sitting there. And if you did one
of those manually, you'd probably remember doing it.
There is something in the NVidia tainted package,
that will generate an xorg.conf for you, if you
want one as a template. That's how I got my
template for doing my own changes.

    "nvidia-xconfig:  version 256.53"

HTH,
    Paul

[toc] | [prev] | [next] | [standalone]

#39315

On 09/28/2016 05:26 PM, Vaso wrote:
> I've installed Mint 18.

Not used mint myself, but a bunch of other distributions.


> Can I simply connect  that disk to another motherboard,
> or I should to Install Mint again?

In most cases it's just to switch the driver to another system and it
will still work, you may have to remove the

/etc/udev/rules.d/70-persistent-net.rules

before you shut down the old machine if your installation has that file.

Also you may to check your /etc/fstab to see if it uses devices or
uuid/labels (the later you shouldn't need to change anything). It can be
a benefit to place the hard drive in an equivalent slot, so if it was in
SATA slot 1 on one machine, then you should set it in slot 1 on the
other machine too.

Other than that, the rest should be auto detected during boot up.


-- 

 //Aho

[toc] | [prev] | [next] | [standalone]

#39317

On 09/28/2016 06:44 PM, J.O. Aho wrote:
> On 09/28/2016 05:26 PM, Vaso wrote:
>> I've installed Mint 18.
>
> Not used mint myself, but a bunch of other distributions.
>
>
>> Can I simply connect  that disk to another motherboard,
>> or I should to Install Mint again?
>
> In most cases it's just to switch the driver to another system and it
> will still work, you may have to remove the
>
> /etc/udev/rules.d/70-persistent-net.rules
>
> before you shut down the old machine if your installation has that file.
>
> Also you may to check your /etc/fstab to see if it uses devices or
> uuid/labels (the later you shouldn't need to change anything). It can be
> a benefit to place the hard drive in an equivalent slot, so if it was in
> SATA slot 1 on one machine, then you should set it in slot 1 on the
> other machine too.
>
> Other than that, the rest should be auto detected during boot up.
>
>

It could be a problem?
On the old machine is IDE/PATA disc.
I intended to clone it to SATA disc and replace the motherboard?

-- 
Branko Vasiljev:
Vise se NIkada Nitko NECE Na Softveru
Obogatiti Kao g-din Bill Gates!!

[toc] | [prev] | [next] | [standalone]

#39318

Vaso wrote:
> On 09/28/2016 06:44 PM, J.O. Aho wrote:
>> On 09/28/2016 05:26 PM, Vaso wrote:
>>> I've installed Mint 18.
>>
>> Not used mint myself, but a bunch of other distributions.
>>
>>
>>> Can I simply connect  that disk to another motherboard,
>>> or I should to Install Mint again?
>>
>> In most cases it's just to switch the driver to another system and it
>> will still work, you may have to remove the
>>
>> /etc/udev/rules.d/70-persistent-net.rules
>>
>> before you shut down the old machine if your installation has that file.
>>
>> Also you may to check your /etc/fstab to see if it uses devices or
>> uuid/labels (the later you shouldn't need to change anything). It can be
>> a benefit to place the hard drive in an equivalent slot, so if it was in
>> SATA slot 1 on one machine, then you should set it in slot 1 on the
>> other machine too.
>>
>> Other than that, the rest should be auto detected during boot up.
>>
>>
>
> It could be a problem?
> On the old machine is IDE/PATA disc.
> I intended to clone it to SATA disc and replace the motherboard?
>

Try it. If it doesn't work, reinstall Mint.

-- 
Z

[toc] | [prev] | [next] | [standalone]

#39326

On 09/28/2016 07:16 PM, Vaso wrote:
> On 09/28/2016 06:44 PM, J.O. Aho wrote:
>> On 09/28/2016 05:26 PM, Vaso wrote:
>>> I've installed Mint 18.
>>
>> Not used mint myself, but a bunch of other distributions.
>>
>>
>>> Can I simply connect  that disk to another motherboard,
>>> or I should to Install Mint again?
>>
>> In most cases it's just to switch the driver to another system and it
>> will still work, you may have to remove the
>>
>> /etc/udev/rules.d/70-persistent-net.rules
>>
>> before you shut down the old machine if your installation has that file.
>>
>> Also you may to check your /etc/fstab to see if it uses devices or
>> uuid/labels (the later you shouldn't need to change anything). It can be
>> a benefit to place the hard drive in an equivalent slot, so if it was in
>> SATA slot 1 on one machine, then you should set it in slot 1 on the
>> other machine too.
>>
>> Other than that, the rest should be auto detected during boot up.
>>
>>
> 
> It could be a problem?
> On the old machine is IDE/PATA disc.
> I intended to clone it to SATA disc and replace the motherboard?
> 

There can be a slight issue if the fstab uses entries which starts with

/dev/hda1

if they start with

UUID=

or

LABEL=

then cloning the disk should be okey, it should keep the id/name for
partitions. You may need to boot from a rescue disk and reinstall the
bootloader as it may want to boot from the /dev/hda1.

If you have to reinstall bootloader (I assume grub), then boot the
rescue-cd, mount the partitions from the disk (/ and /boot should be
enough, the later only if you have it as a separate partition), then
chroot into your recently mounted partition

assume your / is located on /dev/sda2
assume your /boot is located on /dev/sda1

then:

mount /dev/sda2 /mnt
mount /dev/sda1 /mnt/boot
chroot /mnt /bin/bash

and then
grub-install

Never version of grub will need /dev /sys and /proc to work properly, so
those may need to be mounted before chroot. Take a look at Gentoo
installation manual for proper mount options.

Just remember that the worst thing that can happen, is that id don't
work for you and you have a last resort option, just see to backup your
/home so you can restore it afterwards.

-- 

 //Aho

[toc] | [prev] | [next] | [standalone]

#39325

On 09/28/2016 10:26 AM, Vaso wrote:
> I've installed Mint 18.
> Can I simply connect  that disk to another motherboard,
> or I should to Install Mint again?
>
> Thanks
>
I'm with the rest of them--try it.  And be sure you let us know the 
results.  I think it will work.  It might not be happy during the boot 
process and it might take a while for it to settle down and actually be 
ready to go to work.  It might even want to do some updates.

The problem I've had with Mint is that it works so much of the time, 
it's almost not interesting.  Part of it is that Clem says not to 
upgrade unless there is a reason and just keep using what works 
otherwise.  I have to read the messages from the trolls to get any 
excitement at all.

[toc] | [prev] | [next] | [standalone]

#39327

Vaso wrote:
> I've installed Mint 18.
> Can I simply connect  that disk to another motherboard,
> or I should to Install Mint again?

A lot of people don't do a great deal of tweaking and under those 
circumstances a fresh install would add only a few more minutes.

-- 
Mike Easter

[toc] | [prev] | [next] | [standalone]

#39335

On 28.09.16 17.26, Vaso wrote:
> I've installed Mint 18.
> Can I simply connect  that disk to another motherboard,
> or I should to Install Mint again?

Unless you have built your own Linux kernel that exactly matches you 
current hardware all Linux kernels in all standard distributions I know 
have no dependencies on the actual hardware. Only the architecture 
cannot change, e.g. moving from UltraSparc to x86/64 or moving from 
x86/64 to x86/32.

So just put your disk into the new computer and you are fine. If the new 
hardware is supported by a newly installed Mint 18 it will be supported 
by your existing installation as well.

There are a few configuration hacks that could break this compatibility. 
E.g. if you modified the kernel command line in grub in a way that 
conflicts with the new hardware or if you blacklisted some kernel 
modules that are mandatory for the new hardware. But nothing of that 
will be done by the standard installers.

Of course, you might need to do some adjustments in the new hardware. 
E.g. if the graphics chip changed and you used a proprietary binary 
driver like nvidia you should uninstall it if it no longer matches your 
hardware.

BTDTMT.


Marcel

[toc] | [prev] | [next] | [standalone]

#39336

On 2016-09-29, Marcel Mueller <news.5.maazl@spamgourmet.org> wrote:
> On 28.09.16 17.26, Vaso wrote:
>> I've installed Mint 18.
>> Can I simply connect  that disk to another motherboard,
>> or I should to Install Mint again?
>
> Unless you have built your own Linux kernel that exactly matches you 
> current hardware all Linux kernels in all standard distributions I know 
> have no dependencies on the actual hardware. Only the architecture 
> cannot change, e.g. moving from UltraSparc to x86/64 or moving from 
> x86/64 to x86/32.
>
> So just put your disk into the new computer and you are fine. If the new 
> hardware is supported by a newly installed Mint 18 it will be supported 
> by your existing installation as well.
>
> There are a few configuration hacks that could break this compatibility. 
> E.g. if you modified the kernel command line in grub in a way that 
> conflicts with the new hardware or if you blacklisted some kernel 
> modules that are mandatory for the new hardware. But nothing of that 
> will be done by the standard installers.
>
> Of course, you might need to do some adjustments in the new hardware. 
> E.g. if the graphics chip changed and you used a proprietary binary 
> driver like nvidia you should uninstall it if it no longer matches your 
> hardware.

Does Mint use initrd? If so that could be hardware specific.

>
> BTDTMT.
>
>
> Marcel

[toc] | [prev] | [next] | [standalone]

#39338

X-Face: #qJVhFD9mTcJIE6s;3%kN#,}PT`x;Qr`xIQ*z.T#^\C]/l$!a)P7;x}[cK_n"T:60cXgSz:yJ_&B0UiXiKr!)DSo8,A>]Lw^.<[0YaX0WZ6q#H_ri9t'|b[OR^a3G!qcX^.HV\

On 2016-09-29, William Unruh <unruh@invalid.ca> wrote:
<snip>
> Does Mint use initrd? If so that could be hardware specific.
>

Yes.
One can mount/bind-mount then chroot the filesystem(s) 
from a livecd or liveusb ect. then run:
update-initramfs -k all -u -v
from chroot environment and it will rebuild initrd.img

[toc] | [prev] | [next] | [standalone]

#39340

On 29.09.16 10.09, William Unruh wrote:
>> Of course, you might need to do some adjustments in the new hardware.
>> E.g. if the graphics chip changed and you used a proprietary binary
>> driver like nvidia you should uninstall it if it no longer matches your
>> hardware.
>
> Does Mint use initrd?

Yes.

> If so that could be hardware specific.

Only if you did manipulations. The standard Mint/Ubuntu/Debian installer 
does not use individually reduced drivers in the initrd image.


Marcel

[toc] | [prev] | [next] | [standalone]

#39357

On 2016-09-29, Marcel Mueller <news.5.maazl@spamgourmet.org> wrote:
> On 29.09.16 10.09, William Unruh wrote:
>>> Of course, you might need to do some adjustments in the new hardware.
>>> E.g. if the graphics chip changed and you used a proprietary binary
>>> driver like nvidia you should uninstall it if it no longer matches your
>>> hardware.
>>
>> Does Mint use initrd?
>
> Yes.
>
>> If so that could be hardware specific.
>
> Only if you did manipulations. The standard Mint/Ubuntu/Debian installer 
> does not use individually reduced drivers in the initrd image.

However, some drivers, and driver components are in optional packages; 
eg: firmware-nonfree1. So you probably want to make sure you have the
apropriate ones installed before changing the hardware.


-- 
This email has not been checked by half-arsed antivirus software 

[toc] | [prev] | [standalone]

Back to top | Article view | alt.os.linux

csiph-web