Kali Linux Desktop PC Initial Setup: Difference between revisions

From WikiMLT
Line 9: Line 9:
* Boot into Windows 10 and repair the file system. Within This PC application - {{Media-cite|sf|1}}, right click on the shrieked system partition an choose properties {{Pti|s=1|i=1|c=green}}, then from the system properties dialogue choose the Tools tab {{Pti|s=1|i=2|c=green}} and click on the Check button {{Pti|s=1|i=3|c=green}}, after that confirm the error checking dialogue {{Pti|s=1|i=4|c=green}}. Repairing the file system from Windows is important, otherwise CloneZilla may throw errors despite the system is fully operational at first glance.  
* Boot into Windows 10 and repair the file system. Within This PC application - {{Media-cite|sf|1}}, right click on the shrieked system partition an choose properties {{Pti|s=1|i=1|c=green}}, then from the system properties dialogue choose the Tools tab {{Pti|s=1|i=2|c=green}} and click on the Check button {{Pti|s=1|i=3|c=green}}, after that confirm the error checking dialogue {{Pti|s=1|i=4|c=green}}. Repairing the file system from Windows is important, otherwise CloneZilla may throw errors despite the system is fully operational at first glance.  
* Then use [https://clonezilla.org/downloads.php CloneZilla] live image and clone the disk (1TB NVMe > 250GB SSD). You need to disable the disk size check within the advanced options.  
* Then use [https://clonezilla.org/downloads.php CloneZilla] live image and clone the disk (1TB NVMe > 250GB SSD). You need to disable the disk size check within the advanced options.  
* When the Windows 10 installation is cloned - optionally turn-off the system and disconnect the drive with the original installation, - boot in to the new cloned instance, repair the file system once again. After that, tight click on This PC and choice the Manage option from the context menu. Go to the disks section and extend the system partition to occupied the free space. Then you may check for error once again.
* When the Windows 10 installation is cloned - optionally turn-off the system and disconnect the drive with the original installation, - boot in to the new cloned instance, repair the file system once again. After that, right click on "This PC" and choice the Manage option from the context menu. Go to the disks section and extend the system partition to occupied the free space. Then you may check for error once again.
{{sform|1|Windos10-repair-file-system.png|1|{{pt|s=1|i=1|c=green|a=270|x=286|y=126|z=1.2}}{{pt|s=1|i=2|c=green|a=0|x=864|y=610|z=1.2}}{{pt|s=1|i=3|c=green|a=0|x=1070|y=520|z=1.2}}
{{sform|1|Windos10-repair-file-system.png|1|{{pt|s=1|i=1|c=green|a=270|x=286|y=126|z=1.2}}{{pt|s=1|i=2|c=green|a=0|x=864|y=610|z=1.2}}{{pt|s=1|i=3|c=green|a=0|x=1070|y=520|z=1.2}}
{{pt|s=1|i=4|c=green|a=0|x=736|y=214|z=1.2}}
{{pt|s=1|i=4|c=green|a=0|x=736|y=214|z=1.2}}

Revision as of 15:41, 11 November 2022

This is a short guide which cov­ers my set­up of Kali Lin­ux as desk­top en­vi­ron­ment. It doesn't cov­er the in­stal­la­tion process of Kali Lin­ux it­self. Cur­rent­ly Kali Lin­ux is dual-boot width Win­dows 10 and some­thing more Win­dows 10 is turned (al­so) to a QEMU/KVM guest op­er­at­ing sys­tem and can be ac­cessed from in­side Kali Lin­ux, more de­tails about this point are pro­vid­ed in the ar­ti­cle: QEMU/KVM on AMD Ryzen 9 Desk­top with Dual-boot and Passthrough.

Prepa­ra­tion

At this par­tic­u­lar sys­tem are in­stalled 1TB NVMe de­vice and 250GB SSD de­vice. Ini­tial­ly Win­dows 10 was oc­cu­pied the en­tire 1TB NVMe. I was able to shrink it and move it to the 250GB SSD by the fol­low­ing steps.

  • Boot in­to live Lin­ux im­age (Ubun­tu/Kali Lin­ux) from USB and use the GPart­ed tool to shrink the Win­dows 10 main par­ti­tion un­der 240 GB. With­in the na­tive disk man­age­ment it was not pos­si­ble to shrink the par­ti­tion un­der 300GB.
  • Boot in­to Win­dows 10 and re­pair the file sys­tem. With­in This PC ap­pli­ca­tion – Screen 1, right click on the shrieked sys­tem par­ti­tion an choose prop­er­ties 1, then from the sys­tem prop­er­ties di­a­logue choose the Tools tab 2 and click on the Check but­ton 3, af­ter that con­firm the er­ror check­ing di­a­logue 4. Re­pair­ing the file sys­tem from Win­dows is im­por­tant, oth­er­wise CloneZil­la may throw er­rors de­spite the sys­tem is ful­ly op­er­a­tional at first glance.
  • Then use CloneZil­la live im­age and clone the disk (1TB NVMe > 250GB SSD). You need to dis­able the disk size check with­in the ad­vanced op­tions.
  • When the Win­dows 10 in­stal­la­tion is cloned – op­tion­al­ly turn-off the sys­tem and dis­con­nect the dri­ve with the orig­i­nal in­stal­la­tion, – boot in to the new cloned in­stance, re­pair the file sys­tem once again. Af­ter that, right click on "This PC" and choice the Man­age op­tion from the con­text menu. Go to the disks sec­tion and ex­tend the sys­tem par­ti­tion to oc­cu­pied the free space. Then you may check for er­ror once again.
Screen 1. Win­dows 10 check for er­rors and re­pair the file sys­tem. Screen 1. Windows 10 check for errors and repair the file system.

In­stal­la­tion

How to in­stall Kali Lin­ux along­side Win­dows is well de­scribe in the fol­low­ing re­sources. In ad­di­tion, I would phys­i­cal­ly dis­con­nect the Win­dows' dri­ve when this is pos­si­ble.

Post In­stal­la­tion

En­able Blue­tooth

In Kali Lin­ux 2022 the Blue­tooth ser­vice is dis­abled by de­fault. In or­der to en­able it run thew fol­low­ing com­mand.

sudo systemctl enable --now bluetooth.service

Add Win­dows 10 en­try in­to the Grub menu

sudo nano /etc/default/grub
# SZS: https://wiki.metalevel.tech/wiki/Kali_Linux_Desktop_PC_Initial_Setup
GRUB_DISABLE_OS_PROBER=false
sudo update-grub

Ref­er­ences

In­stall the lat­est Nvidia Dri­ver

Here I'm go­ing to in­stall the Lat­est NVIDIA Dri­ver, rec­om­mend­ed for Quadro T600, which is not pre­sent­ed in the Kali's repos­i­to­ry. The first step is to down­load the lat­est dri­ver: NVIDIA Dri­ver Down­loads > Quadr/​​​RTX T600 > LIN­UX X64 (AMD64/EM64T) DIS­PLAY DRI­VER.

Then Black­list the de­fault Nou­veau dri­ver:

sudo nano /etc/modprobe.d/blacklist-nouveau.conf
blacklist nouveau
options nouveau modeset=0
sudo update-initramfs -u

Af­ter that re­boot the sys­tem. If the log-in screen come back – don't log-in, but prob­a­bly there will be blank screen wit blink­ing cur­sor. In both cas­es, press Ctrl+Alt+F3, log-in to a TTY, and re­move any ex­ist­ing NVIDIA Dri­ver:

sudo apt remove '*nvidia*'

And then in­stall the dri­ver.

cd ~/Downloads
chmod +x NVIDIA-Linux-x86_64-515.65.01.run
sudo ./NVIDIA-Linux-x86_64-515.65.01.run
sudo nvidia-xconfig

Fi­nal­ly re­boot the sys­tem once again. If there are some per­for­mance is­sues check NVIDIA Set­tings > Pow­er­Miz­er > Per­for­mance Mode. You can change the de­fault per­for­mance mode by chang­ing xorg.conf or you can change it via the CLI by the fol­low­ing com­mands.

nvidia-settings -a [gpu:0]/GPUPowerMizerMode=0  # Adaptive
nvidia-settings -a [gpu:0]/GPUPowerMizerMode=1  # Prefer Maximum Performance
nvidia-settings -a [gpu:0]/GPUPowerMizerMode=2  # Auto
nvidia-settings -a [gpu:0]/GPUPowerMizerMode=3  # Prefer Consistent Performance

Ref­er­ences

Gnome Ex­ten­sions

Don't up­date the ex­ten­sions de­liv­ered by Kali Lin­ux from the GNOME Shell Ex­ten­sions page! The pack­age gnome-brows­er-con­nec­tor is not yet avail­able to the Kali's repos­i­to­ry – that cause the mes­sage: Your na­tive host con­nec­tor do not sup­port fol­low­ing APIs: v6., – in the brows­er. Cur­rent­ly every­thing works de­spite the men­tioned mes­sage. In case there is a prob­lem, in­stead of adding new ex­ten­sions via the brows­er we can use gnome-shell-ex­ten­sion-man­ag­er.

sudo apt install gnome-shell-extension-manager

An­oth­er way is to down­load and in­stall the ex­ten­sions man­u­al­ly – ref­er­ence.

gnome-extensions install -f <name of downloaded zip file>.zip

Al­so keep in mind there is a cou­ple of de­fault ex­ten­sions avail­able in the OS' repos­i­to­ry.

sudo apt install gnome-shell-extension-[Press TAB]
#Out­put
gnome-shell-extension-appindicator             gnome-shell-extension-impatience
gnome-shell-extension-arc-menu                 gnome-shell-extension-kimpanel
gnome-shell-extension-autohidetopbar           gnome-shell-extension-manager
gnome-shell-extension-bluetooth-quick-connect  gnome-shell-extension-panel-osd
gnome-shell-extension-caffeine                 gnome-shell-extension-pixelsaver
gnome-shell-extension-dashtodock               gnome-shell-extension-prefs
gnome-shell-extension-dash-to-panel            gnome-shell-extension-proxyswitcher
gnome-shell-extension-desktop-icons-ng         gnome-shell-extension-shortcuts
gnome-shell-extension-easyscreencast           gnome-shell-extension-sound-device-chooser
gnome-shell-extension-freon                    gnome-shell-extension-system-monitor
gnome-shell-extension-gamemode                 gnome-shell-extension-tiling-assistant
gnome-shell-extension-gpaste                   gnome-shell-extension-top-icons-plus
gnome-shell-extension-hamster                  gnome-shell-extension-vertical-overview
gnome-shell-extension-hard-disk-led            gnome-shell-extension-volume-mixer
gnome-shell-extension-hide-activities          gnome-shell-extension-weather

Notes about some ex­ten­sions:

De­ploy Se­goe UI Font

bash <(curl -s https://raw.githubusercontent.com/mrbvrz/segoe-ui-linux/master/install.sh)

Ad­di­tion­al Soft­ware In­stal­la­tion and Tweaks