| View previous topic :: View next topic |
| Author |
Message |
jserink
Veteran
Joined: 30 Jan 2004
Posts: 1008
|
 Posted: Thu Mar 01, 2018 1:05 am Post subject: New Laptop |
 |
|
Hi All:
New laptop and wanted to share the config details (next message) but some performance details as compare to my old laptop.
Old laptop:
Dell M4600 i7-2720QM, 2.2GHz 6M cache, 32GB ram, 7200-rpm drive, not used tmpfs for portage tmp files.
New laptop:
Dell latitude 5580 i7-7820HQ, 2.9GHz, 8M cache, 32GB ram, 525GB pcie NVME disk, using tmpfs for portage tmp files.
Check out the build time differences:
Sat Feb 17 01:00:30 2018 >>> app-office/libreoffice-5.4.5.1
merge time: 2 hours, 15 minutes and 55 seconds.
Mon Feb 26 00:55:03 2018 >>> app-office/libreoffice-5.4.5.1
merge time: 1 hour, 18 minutes and 44 seconds.
Knocked an hour off a libreoffice build.
Tue Feb 20 14:48:56 2018 >>> www-client/chromium-64.0.3282.167
merge time: 3 hours, 21 minutes and 12 seconds.
Tue Feb 27 15:17:02 2018 >>> www-client/chromium-64.0.3282.167
merge time: 2 hours, 8 minutes and 30 seconds.
Knocked 1 hour and 13 minutes off a chromium build.
I'm liking this.
John |
|
| Back to top |
|
 |
snkmoorthy
Guru
Joined: 19 Nov 2002
Posts: 376
|
|
| Back to top |
|
|
jserink
Veteran
Joined: 30 Jan 2004
Posts: 1008
|
| Posted: Mon Mar 05, 2018 5:38 am Post subject: Transfer to new laptop |
|
|
Hi All:
This post chronicles the saga of moving from my Dell M4600 laptop to my new Dell Latitude 5580 laptop.
The major error I made in the whole mess was assuming my new laptop, as supplied by the company IS dept, had a HDD as my
cunning plan was to simply compile some new drivers into my running kernel in the M4600 and then move the HDD over.
Was foiled on two counts:
1. The 5580 come with a 515GB PCI SSD,
2. Because of item 1, there was no 2.5" HDD cradle or mini SATA cable included.
As such, I couldn't transfer the HDD over even if I wanted to without those bits.
Fine, go with the SSD.
As the new 5580 has a dual graphics setup with an Nvidia 940MX + and Intel HD630, the only bootable distro I could find that would properly detect
the video on a USB boot was Calculate Linux. I also made use of SystemRecueCD later on both built using Unetbootlin. Notes on using unetbootlin for
perfectly reliable boot USBs:
1. Always run gparted on the target USB drive,
2. Remove the existing partition and save,
3. Create a new F32 new partition and save,
4. Run unnetbootlin and push whatever ISO you want onto the USB,
5. Will work perfectly everytime but you MUST go through steps 1-4. If you skip steps 1-3, it won't work.
Problem, I have a 700GB HDD in the M4600 and didn't want to rebuild from scratch. Did the following:
1. Emptied my trash folder,
2. removed a bunch of 5G ISO files I had kicking around.
The above two dropped my used disk to ~440GB.
3. Booted the 5580 from USB and partitioned the disk following with the first two partitions exactly as on my M4600 as follows:
| Code: |
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 34815 32768 16M BIOS boot
/dev/nvme0n1p2 34816 296959 262144 128M Linux filesystem
/dev/nvme0n1p3 296960 10536959 10240000 4.9G Linux swap
/dev/nvme0n1p4 10536960 1000214527 989677568 471.9G Linux filesystem
|
4. Ran Gparted on my M4600 and resized p4 to exactly the same size as /dev/nvme0n1p4 on the 5580.
Note that this resizing to ~2.5 hours,
5. Recompiled the kernel on the M4600 to include most drivers on the 5580 LEAVING OUT the nouveau for the moment.
6. using this:
| Code: |
dd if=/dev/sda2 | ssh root@10.3.36.68 'dd of=/dev/nvme0n1p2' bs=8192 conv=notrunc status=progress
dd if=/dev/sda4 | ssh root@10.3.36.68 'dd of=/dev/nvme0n1p4' bs=8192 conv=notrunc status=progress
|
I copied over everything from the M4600 to the 5580. Note that p4 took about 1h20m on a 1G LAN.
7. Fired up systemrescueCD fro mUSB which required the following kernel parameter to boot properly on the 5580:
nouveau.blacklist=yes
Which was required as the systemrecueCD has the nouveau drived compiled as a module and the screen goes black every time if it loads.
8. Marked the first partition on the 5580 as bios_grub,
9. Set the bios for legacy boot, from Gparted,
10. While in systemrescueCD, did the following:
| Code: |
root@sysresccd /root % mkdir /mnt/linux
root@sysresccd /root % mount /dev/nvme0n1p4 /mnt/linux
root@sysresccd /root % mount -o bind /proc /mnt/linux/proc
root@sysresccd /root % mount -o bind /dev /mnt/linux/dev
root@sysresccd /root % mount -o bind /sys /mnt/linux/sys
root@sysresccd /root % mkdir /mnt/linux/boot
root@sysresccd /root % mount /dev/nvme0n1p2 /mnt/linux/boot
root@sysresccd /root % chroot /mnt/linux /bin/bash
|
Then ran the following:
| Code: |
grub-install /dev/nvme0n1 --target i386-pc
cp /home/jserink/folders/downloads/backgroundPhotos/KidsPool.jpg /boot/grub/KidsPool.jpg
grub-mkconfig -o /boot/grub/grub.cfg
|
11. Rebooted without the USB stick in,
12. System when to grub (success),
13. kernel panel just after boot, message "Cannot find root",
14. Examine my kernel on the M4600...Oops, compiled in the nvme driver as a module which is a no-no if root is on the nvme.
Recompiled the kernel with the nvme stuff compiled in and installed it on the M4600. Then did this again:
| Code: |
dd if=/dev/sda2 | ssh root@10.3.36.68 'dd of=/dev/nvme0n1p2' bs=8192 conv=notrunc status=progress
|
15. Redid steps 7-11.....
16. SUCCESS!!!
17. In the new machine. Clean up /etc/init.d/net.x init scripts as all of the interfaces have changed names, tidy up kernels issues and drivers.
Here is the machine:
| Code: |
jserinki7 /home/jserink # lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 05)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 05)
00:02.0 VGA compatible controller: Intel Corporation Device 591b (rev 04)
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 05)
00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31)
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H Serial IO I2C Controller #0 (rev 31)
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-H Serial IO I2C Controller #1 (rev 31)
00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31)
00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller [AHCI mode] (rev 31)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #2 (rev f1)
00:1c.2 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #3 (rev f1)
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #5 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #9 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
00:1f.3 Audio device: Intel Corporation CM238 HD Audio Controller (rev 31)
00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (5) I219-LM (rev 31)
01:00.0 3D controller: NVIDIA Corporation Device 179c (rev a2)
02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01)
3d:00.0 Non-Volatile memory controller: Device 1c5c:1284
jserinki7 /home/jserink # lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2b Intel Corp.
Bus 001 Device 003: ID 046d:c045 Logitech, Inc. Optical Mouse
Bus 001 Device 006: ID 0bda:568c Realtek Semiconductor Corp.
Bus 001 Device 005: ID 0a5c:5832 Broadcom Corp.
Bus 001 Device 002: ID 413c:2113 Dell Computer Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
|
Was a bit short on SSD space so purchased a 128G U3 flash disk and plugged it into the SD4.0 flash card slot
and copied a bunch of stuff over to it. Set a soft link and adjusted mu rsync backup scripts so that the backups
worked like they used to...
And its all running.
When I have time I'll fiddle with the Nvidia Optimus system but for now am running with 3D on the Intel 915 driver just fine.
All good. the machine is really quick.
When I figure out the dual video, will post that.
John
PS: Because of the new support for gmail in evolution, I no longer required gnome-control-centre which meant NO MORE PULSEAUDIO!!!! Yippiee!!!!
That has been peeled out of my system and EVERYTHING, skype, gotomeeting, etc is working just fine. No more booting and fiddling with settings
everytime I have a conf call, it just works...go old reliable alsa. |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 21724
|
| Posted: Tue Mar 06, 2018 3:38 am Post subject: Re: Transfer to new laptop |
|
|
| jserink wrote: | This post chronicles the saga of moving from my Dell M4600 laptop to my new Dell Latitude 5580 laptop.
1. The 5580 come with a 515GB PCI SSD, | Code: | dd if=/dev/sda2 | ssh root@10.3.36.68 'dd of=/dev/nvme0n1p2' bs=8192 conv=notrunc status=progress
dd if=/dev/sda4 | ssh root@10.3.36.68 'dd of=/dev/nvme0n1p4' bs=8192 conv=notrunc status=progress
|
|
This may have worked, but was severely suboptimal. First, copying whole block devices is inefficient, as you found. Second, when the target is an SSD, this marks unused sectors as busy, forcing the firmware to work harder without good cause. Modern SSDs are presumably reliable enough that you will still retire the drive before the negative effects of this extra work become visible, but it's generally bad practice, and may slightly reduce write performance. You should instead have copied at the filesystem layer, not the block layer. There is likely no point in redoing this now.
It is rare that using dd to copy a block device is the right solution. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54328
Location: 56N 3W
|
| Posted: Tue Mar 06, 2018 11:01 am Post subject: |
|
|
jserink,
After that dd, which will have written the entire SSD, its worth runningso the drive can pre erase the unused space again.
Writes will be slow otherwise as erase is a very slow operation compared to read and write.
When you write to a 'dirty' area on a SSD, you must wait for the erase to complete before the write can start.
When you have the RAM to put /var/tmp/portage into tmpfs, you don't gut any speed gain by actually doing it.
The kernel will save everything in disk buffers anyway.
However, it does save all the writes that will never be read, which is good for SSDs.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
jserink
Veteran
Joined: 30 Jan 2004
Posts: 1008
|
| Posted: Wed Mar 07, 2018 12:20 am Post subject: |
|
|
Needy and Hu:
Good tips, thanx for the info.
Just ran fstrim -a now.
I'll get setup a cron job to run that once a week or so.
cheers,
john |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Other Things Gentoo
