Changing from XFCE 64bit to Fluxbox 64bit [Solved]

[pete67]

Hi there,

I use Fluxbox on an old Laptop and use it at the moment with the liquorix-kernel and I like this frame manager most because of its features that you can see all the codes and get even more familiar with using the terminal more often.

Alongside I want to update MX 21.3 "Wildflower" with the liquorix-kernel to MX-23 „Libretto“ and keep the liquorix-kernel as it is or update it afterward I made the migration as it's described here (https://mxlinux.org/migration/).

So I assume that can be a special issue and I probably have to be careful and have to adapt the whole process to my situation.

Can anybody give me hints how I should do this whole process due to the fact that I want to keep the liquorix-kernel, please?

Here is my System-Info:

Code: Select all

System:    Kernel: 6.5.11-3-liquorix-amd64 [6.5-16mx21ahs] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: audit=0 intel_pstate=disable rcupdate.rcu_expedited=1 
           BOOT_IMAGE=/boot/vmlinuz-6.5.11-3-liquorix-amd64 root=UUID=<filter> ro 
           Desktop: Xfce 4.18.1 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.18.0 vt: 7 
           dm: LightDM 1.26.0 Distro: MX-21.3_ahs_x64 Wildflower September 18  2022 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop Mobo: ASUSTeK model: PRIME Z370-P v: Rev X.0x serial: <filter> 
           UEFI: American Megatrends v: 3004 date: 07/12/2021 
CPU:       Info: 6-Core model: Intel Core i5-8600K bits: 64 type: MCP arch: Kaby Lake note: check 
           family: 6 model-id: 9E (158) stepping: A (10) microcode: F4 cache: L2: 9 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 43200 
           Speed: 1200 MHz min/max: 800/3601 MHz boost: enabled Core speeds (MHz): 1: 1200 2: 1600 
           3: 1601 4: 1200 5: 1200 6: 1576 
           Vulnerabilities: Type: gather_data_sampling mitigation: Microcode 
           Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled 
           Type: mds mitigation: Clear CPU buffers; SMT disabled 
           Type: meltdown mitigation: PTI 
           Type: mmio_stale_data mitigation: Clear CPU buffers; SMT disabled 
           Type: retbleed mitigation: IBRS 
           Type: spec_rstack_overflow status: Not affected 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: IBRS, IBPB: conditional, STIBP: disabled, RSB filling, 
           PBRSB-eIBRS: Not affected 
           Type: srbds mitigation: Microcode 
           Type: tsx_async_abort mitigation: TSX disabled 
Graphics:  Device-1: NVIDIA GA106 [GeForce RTX 3060 Lite Hash Rate] vendor: Micro-Star MSI 
           driver: nvidia v: 525.125.06 bus-ID: 01:00.0 chip-ID: 10de:2504 class-ID: 0300 
           Display: x11 server: X.Org 1.20.14 compositor: compton v: 1 driver: loaded: nvidia 
           unloaded: fbdev,modesetting,nouveau,vesa alternate: nv display-ID: :0.0 screens: 1 
           Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.7x15.0") 
           s-diag: 777mm (30.6") 
           Monitor-1: DP-2 res: 2560x1440 hz: 60 dpi: 93 size: 700x390mm (27.6x15.4") 
           diag: 801mm (31.5") 
           OpenGL: renderer: NVIDIA GeForce RTX 3060/PCIe/SSE2 v: 4.6.0 NVIDIA 525.125.06 
           direct render: Yes 
Audio:     Device-1: Intel 200 Series PCH HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           alternate: snd_soc_avs bus-ID: 00:1f.3 chip-ID: 8086:a2f0 class-ID: 0403 
           Device-2: NVIDIA vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus-ID: 01:00.1 
           chip-ID: 10de:228e class-ID: 0403 
           Sound Server-1: ALSA v: k6.5.11-3-liquorix-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: ASUSTeK PRIME B450M-A driver: r8169 v: kernel port: d000 bus-ID: 04:00.0 
           chip-ID: 10ec:8168 class-ID: 0200 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Bluetooth: Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 bus-ID: 1-9:6 
           chip-ID: 0bda:8771 class-ID: e001 serial: <filter> 
           Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: N/A rfk-block: 
           hardware: no software: no address: <filter> 
           Info: acl-mtu: 1021:6 sco-mtu: 255:12 link-policy: rswitch hold sniff park 
           link-mode: slave accept 
RAID:      Hardware-1: Silicon Image SiI 3132 Serial ATA Raid II Controller driver: sata_sil24 
           v: kernel port: c000 bus-ID: 06:00.0 chip-ID: 1095.3132 rev: 01 class-ID: 0104 
Drives:    Local Storage: total: 5.46 TiB used: 680.34 GiB (12.2%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 1TB size: 931.51 GiB 
           block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD 
           serial: <filter> rev: 3B4QFXO7 temp: 28.9 C scheme: GPT 
           ID-2: /dev/nvme1n1 maj-min: 259:1 vendor: Samsung model: SSD 980 1TB size: 931.51 GiB 
           block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD 
           serial: <filter> rev: 3B4QFXO7 temp: 26.9 C scheme: GPT 
           ID-3: /dev/sda maj-min: 8:0 vendor: Samsung model: HD103UJ size: 931.51 GiB block-size: 
           physical: 512 B logical: 512 B speed: 3.0 Gb/s type: N/A serial: <filter> rev: 1118 
           scheme: GPT 
           ID-4: /dev/sdb maj-min: 8:16 vendor: Samsung model: HD103UJ size: 931.51 GiB 
           block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: N/A serial: <filter> 
           rev: 1118 scheme: GPT 
           ID-5: /dev/sdc maj-min: 8:32 vendor: Samsung model: SSD 870 QVO 1TB size: 931.51 GiB 
           block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: SSD serial: <filter> 
           rev: 2B6Q scheme: GPT 
           ID-6: /dev/sdd maj-min: 8:48 vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB 
           block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: SSD serial: <filter> 
           rev: 4B6Q scheme: GPT 
Partition: ID-1: / raw-size: 923.25 GiB size: 907.69 GiB (98.31%) used: 156.4 GiB (17.2%) fs: ext4 
           dev: /dev/sda2 maj-min: 8:2 
           ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 27.1 MiB (10.7%) 
           fs: vfat dev: /dev/sda1 maj-min: 8:1 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda3 
           maj-min: 8:3 
Sensors:   System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nvidia temp: 45 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 0% 
Repos:     Packages: 2162 note: see --pkg apt: 2151 lib: 1098 flatpak: 11 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list 
           1: deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg] https://brave-browser-apt-release.s3.brave.com/ stable main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
           1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/liquorix.list 
           1: deb [arch=amd64 signed-by=/etc/apt/keyrings/liquorix-keyring.gpg] https://liquorix.net/debian bullseye main
           2: deb-src [arch=amd64 signed-by=/etc/apt/keyrings/liquorix-keyring.gpg] https://liquorix.net/debian bullseye main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ bullseye main non-free
           2: deb http://mxrepo.com/mx/repo/ bullseye ahs
           No active apt repos in: /etc/apt/sources.list.d/steam-beta.list 
           Active apt repos in: /etc/apt/sources.list.d/steam-stable.list 
           1: deb [arch=amd64,i386 signed-by=/usr/share/keyrings/steam.gpg] https://repo.steampowered.com/steam/ stable steam
           2: deb-src [arch=amd64,i386 signed-by=/usr/share/keyrings/steam.gpg] https://repo.steampowered.com/steam/ stable steam
Info:      Processes: 318 Uptime: 2h 7m wakeups: 1 Memory: 31.3 GiB used: 4.19 GiB (13.4%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 10.2.1 
           alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: UEFI

[j2mcgreg]

@pete67
We have made it clear that an in-place upgrade is only for the most experienced users. Your statement:

I like this frame manager most because of its features that you can see all the codes and get even more familiar with using the terminal more often.

places you outside that category. Then you further say that you want to complicate the method by switching from XFCE to Fluxbox and from the standard kernel to a liquorix one in the process. You are welcome to try, but as we have clearly stated this upgrade method is unsupported and that means that you will get little to no help here.

[Charlie Brown]

You can install any kernel you like after the installation (and rebooting with the new system).

There's even a newer Liquorix now in MXPI : 6.6.1 , together with that 6.5.11-3-liquorix, ... just 2 clicks.

(Shortly, the current 6.5.11-3-liquorix kernel you have won't do any harm to the process and it'll be gone together with others ... )


You can also (after the reboot and "if you like only") install the MX Fluxbox package from MXPI - Popular Apps tab, under "Window Managers" section, and login with that whenever you like.


P.S. If you install the regular MX and still want AHS: after the reboot start "MX Repo Manager" , go to last tab and check this source:

deb http://mxrepo.com/mx/repo/ bookworm ahs

..." Apply" , then update as always using the MX Updater... it'll turn into "MX 23.1 AHS" next reboot.

[pete67]

@Charlie Brown thanx bro.

I will do as you mentioned and afterwards report, how it worked or not.

Greetings,
Peter

[pete67]

@Charlie Brown

Hi, my system updated the liquorix kernel to version 6.6.8-1-liquorix-amd64 x86_64 by the normal update process.

After reading bits of advice I suggest it's better to make a clean install for MX 23.1 AHS to prevent issues when updating out of MX 21.3.

So my question is can I save my settings with a snapshot and restore them later or should I try to update my system like the described steps on the MX-Linux-Homepage?

[Charlie Brown]

... can I save my settings ...

Yep. You may/may not take a snapshot (that will save the whole (current) system as an .iso).

But the simplest is:

If you have many installed programs you can create a list and then auto-install them with 1-2 clicks: "User Installed Packages" from menu. When you run it now, you'll save the "list" of them (by default to home folder).. After the new installation run it again, this time to install according to that list :)

You can of course skip that step if you like ...

Then you can either manually backup the current home folder to somewhere and also select "preserve home" during installation. The manually backing up will make you feel at ease, in case you do something wrong... All preferences etc. are there and your desktop will almost be the same ...

[pete67]

@Charlie Brown I have downloaded the MX 23.1 AHS after using User Installed Packages so that I can restore the Packages after updating to 23.1.

How can I start the installation from the ISO or do I have to put it on a USB-Drive and boot with this?

[Charlie Brown]

Normally the output (list) is in home folder, you can also copy (just that file: by default it has a name like uip-list-2023.12.29_... ) to another place (as a backup).. Then just install the new MX..

When installation (of MX 23.1) is done and then you boot with that .. run "User Installed Packages" again from menu.. and when it asks select your file (wherever it is)...

[pete67]

Hi @Charlie Brown , I have made a copy of the file uip-list-2023.12.30_120951.txt to another drive, that's always mounted so that I can use it in any case no matter out of my home directory or the other place where I've copied it.

Now again my question: How can I start the update with the iso MX-23.1_ahs_x64.iso directly out of my running system?

Thanx in advance for your help.
Peter

[Charlie Brown]

... update with the iso MX-23.1_ahs_x64.iso directly out of my running system?..

You need to fresh install (and the 21.3 will be wiped , hence we first take a copy of what we want to keep/use later). Yes, there's a method to "upgrade" from 21 to 23 however that's not recommended and generally problematic. Also (other than being "cleanest") re-installation is much more simpler and faster.

Once you boot with the 23.1 iso, you can either run a full upgrade before installation (to get the newest packages) or just install and later do the updates as always on the newly installed system.


Shortly: You can use the "MX Updater" or any of these commands when on live session (or later on the installed system):

Code: Select all

sudo nala upgrade

or

Code: Select all

sudo apt update ; sudo apt full-upgrade -y

(You know: on live session the sudo password is demo )


... Then you may/may not install the saved list of packages (up to you, you can install them later on the installed system if you like)

When all is finished start installation.

(When it asks: "There were changes with the system, would you like to keep them?" (or so) answer Yes. )


With the default (custom) installation, you'll see an option to keep home folder, check that...