Switching to EOS, what configs or files can I keep?

Hey all,

I’m still somewhat of a Linux noob at about 7 months of daily driving it.
I’ve been on Manjaro for all that time and now I’m looking to switch to EOS.

I’ve never intended to distro hop, so I have very little idea what to do in that arena.
I want to save myself some time in setting up my system after a fresh install of EOS.
I wonder what configs or files am I able to keep from my current system that I can bring over to the fresh install?

Thanks for the advice in advanced.

If you really want to switch from a working Manjaro to EndeavorOS, then follow this description. [HowTo] Convert Manjaro to EndeavourOS Anyway, I think it’s much more correct to do a clean EndeavorOS installation, and then gradually install the programs you need. You will get a lot of help with this in this great forum.

1 Like

Welcome to the forum @Zer0sVoid :enos_flag: :partying_face:

I would do a clean install of EndeavourOS.

3 Likes

Anything in /home. If your /home resides on seperate partition, mount /home and install normally.
If /home doesn’t have seperate partition, check if your UID is 1000 on Manjaro with id command. Boot EndeavourOS, mount Manjaro partition, delete anything but /home. During installation, choose to install to your Manjaro partition without formatting. If your UID is 1000, create a new user with the same name as the old user. If it isn’t, create a user with a different name, after installation completes create a user with old same username and UID then log in to that user.
If you do this right, any personal data will remain.

1 Like

With Gnome and GTK apps, I make a backup of the .config folder.
When the system and my new apps are installed, I put one by one my config apps folder in the new .config folder as I need them.
So the system is clear and I keep my app configuration.

1 Like

Before I switched away from Mint (Cinnamon/Debian) I ran Timeshift to get the entire gamut… I set it to rsync, and to include everything - as this wasn’t intended for a restoration, just for manual copying. It’s surprising how many things you’d miss if you didn’t get them…

So you can do a fresh install, then it’s up to you to carefully build… I set up one desktop with dual pane dolphin to compare /home with /timeshift/…/home. Using meld is one way to compare things, but for a lot of stuff (like .mozilla) you can just throw it back and test it.

If you set zsh, then you could import the .zshrc - but also you can take time to only copy in what you understand and want (of course, some of that will need installation work - I started learning this when I dropped ‘oh-my-zsh’ and set it up those functions manually). Manjaro has a nice zsh config - there’s a lot worth stealing from that.

There’s gonna be stuff you never realized you’d miss too - so I’d just capture the whole shebang… maybe omit a few .cache folders (and if you have PLEX, that could cut it down by maybe 2 million files).

1 Like

Welcome to the forum! :smile:

Whatever you do, first remember to backup everything you want to save, preferably to an external disk, especially your personal data.

4 Likes

I would start with a clean slate, you will save yourself time later on…

1 Like

If you decide to do a clean install of EndeavourOS then I assume you have a backup.

But most important from a system point of view. Save your /etc directory from Manjaro. Also have a list of installed packages in Manjaro. Then it is easier to re-build things.

1 Like

It is always a good idea to have a separate partition for /home with all your user data and user configs. This can stay untouched during a fresh install. Everything else should be wiped and replaced.

1 Like

Hey all,

I’m extremely thankful for so many responses, I’m quite surprised.

For those recommending a clean install, that is definitely the plan.
To clarify, I wanted to know what universal configs or files I could bring over to the fresh install.
I don’t plan on keeping all files and programs one to one over, I think that could end up in disaster and give me more of a headache than necessary.

I believe that’s how I have my system setup, I have all my documents, downloads etc directories on a separate drive and my UID does show 1000. My concern is that my etc and other similar folders are in the same partition.

Noted, I am running on Gnome at the moment with my Manjaro installation.

I do have some alias I want to keep I may put the .zshrc config onto a USB to copy the ones I can use over. I did love the zsh config, I’ll take a look around on how to customize the bash config when I find the time.

Happily all my personal data is already on different disks, but definitely a good reminder!

Not the the first time I had to build from a clean install. It’s not been too long and it’s an adventure in itself!

Manjaro has different way of managing certain drivers.
Could you show the output of

inxi -Faz

Sure thing, the output is as follows

System:
  Kernel: 5.15.60-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.1.1
    parameters: BOOT_IMAGE=/boot/vmlinuz-5.15-x86_64
    root=UUID=4fe816b8-724f-4798-a934-80245ca84471 rw splash apparmor=1
    security=apparmor udev.log_priority=3 intel_iommu=on iommu=pt
    vfio-pci.ids=10de:13c2,10de:0fbb rd.driver.pre=vfio_pci
  Desktop: GNOME v: 42.4 tk: GTK v: 3.24.34 wm: gnome-shell dm: GDM v: 42.0
    Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: ROG STRIX Z590-E GAMING WIFI v: Rev 1.xx
    serial: <superuser required> UEFI: American Megatrends v: 1007
    date: 07/13/2021
CPU:
  Info: model: 11th Gen Intel Core i7-11700K bits: 64 type: MT MCP
    arch: Rocket Lake gen: core 11 level: v4 built: 2021+ process: Intel 14nm
    family: 6 model-id: 0xA7 (167) stepping: 1 microcode: 0x54
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
    L1: 640 KiB desc: d-8x48 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
    L3: 16 MiB desc: 1x16 MiB
  Speed (MHz): avg: 1393 high: 4900 min/max: 800/4900:5000 scaling:
    driver: intel_pstate governor: powersave cores: 1: 800 2: 800 3: 4899
    4: 4900 5: 800 6: 801 7: 800 8: 800 9: 800 10: 801 11: 801 12: 801
    13: 801 14: 801 15: 801 16: 2090 bogomips: 115232
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: retbleed mitigation: Enhanced IBRS
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl and seccomp
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 status: Vulnerable: eIBRS with unprivileged eBPF
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GA104 [GeForce RTX 3070 Lite Hash Rate] vendor: eVga.com.
    driver: nvidia v: 515.65.01 alternate: nouveau,nvidia_drm non-free: 515.xx+
    status: current (as of 2022-08) arch: Ampere code: GAxxx process: TSMC n7
    (7nm) built: 2020-22 pcie: gen: 1 speed: 2.5 GT/s lanes: 8 link-max:
    gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:2488
    class-ID: 0300
  Device-2: NVIDIA GM204 [GeForce GTX 970] vendor: eVga.com.
    driver: vfio-pci v: N/A alternate: nouveau,nvidia_drm,nvidia
    non-free: 515.xx+ status: current (as of 2022-08) arch: Maxwell
    code: GMxxx process: TSMC 28nm built: 2014-19 pcie: gen: 1
    speed: 2.5 GT/s lanes: 8 link-max: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 02:00.0 chip-ID: 10de:13c2 class-ID: 0300
  Device-3: Razer USA Gaming Webcam [Kiyo] type: USB
    driver: snd-usb-audio,uvcvideo bus-ID: 1-11:6 chip-ID: 1532:0e03
    class-ID: 0102
  Device-4: Logitech BRIO Ultra HD Webcam type: USB
    driver: hid-generic,snd-usb-audio,usbhid,uvcvideo bus-ID: 2-8.4:6
    chip-ID: 046d:085e class-ID: 0300 serial: <filter>
  Display: x11 server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.3
    compositor: gnome-shell driver: X: loaded: nvidia gpu: nvidia,vfio-pci
    display-ID: :1 screens: 1
  Screen-1: 0 s-res: 4480x1200 s-size: <missing: xdpyinfo>
  Monitor-1: DP-1 pos: primary,bottom-r res: 2560x1080 hz: 60 dpi: 97
    size: 673x284mm (26.5x11.18") diag: 730mm (28.76") modes: N/A
  Monitor-2: DP-2 pos: primary,top-left res: 1920x1200 hz: 60 dpi: 94
    size: 518x324mm (20.39x12.76") diag: 611mm (24.05") modes: N/A
  OpenGL: renderer: NVIDIA GeForce RTX 3070/PCIe/SSE2 v: 4.6.0 NVIDIA
    515.65.01 direct render: Yes
Audio:
  Device-1: Intel Tiger Lake-H HD Audio vendor: ASUSTeK driver: snd_hda_intel
    bus-ID: 1-11:6 v: kernel chip-ID: 1532:0e03
    alternate: snd_sof_pci_intel_tgl class-ID: 0102 bus-ID: 00:1f.3
    chip-ID: 8086:43c8 class-ID: 0403
  Device-2: NVIDIA GA104 High Definition Audio vendor: eVga.com.
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 8
    link-max: lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:228b class-ID: 0403
  Device-3: NVIDIA GM204 High Definition Audio vendor: eVga.com.
    driver: vfio-pci alternate: snd_hda_intel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 8 link-max: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 02:00.1
    chip-ID: 10de:0fbb class-ID: 0403
  Device-4: Razer USA Gaming Webcam [Kiyo] type: USB
    driver: snd-usb-audio,uvcvideo
  Device-5: ASUSTek USB Audio type: USB
    driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-14:11 chip-ID: 0b05:1996
    class-ID: 0300
  Device-6: Native Instruments Komplete Audio 1 type: USB
    driver: snd-usb-audio bus-ID: 1-5:4 chip-ID: 17cc:1830 class-ID: fe01
    serial: <filter>
  Device-7: Logitech BRIO Ultra HD Webcam type: USB
    driver: hid-generic,snd-usb-audio,usbhid,uvcvideo bus-ID: 2-8.4:6
    chip-ID: 046d:085e class-ID: 0300 serial: <filter>
  Sound Server-1: ALSA v: k5.15.60-1-MANJARO running: yes
  Sound Server-2: JACK v: 1.9.21 running: no
  Sound Server-3: PulseAudio v: 16.1 running: yes
  Sound Server-4: PipeWire v: 0.3.56 running: yes
Network:
  Device-1: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel pcie:
    gen: 2 speed: 5 GT/s lanes: 1 port: N/A bus-ID: 06:00.0 chip-ID: 8086:15f3
    class-ID: 0200
  IF: enp6s0 state: down mac: <filter>
  Device-2: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel
    pcie: gen: 2 speed: 5 GT/s lanes: 1 port: N/A bus-ID: 07:00.0
    chip-ID: 8086:15f3 class-ID: 0200
  IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-3: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi
    v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 08:00.0
    chip-ID: 8086:2725 class-ID: 0280
  IF: wlp8s0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel AX210 Bluetooth type: USB driver: btusb v: 0.8
    bus-ID: 1-2:2 chip-ID: 8087:0032 class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 1 state: up address: see --recommends
Drives:
  Local Storage: total: 6.02 TiB used: 2.75 TiB (45.6%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Sabrent model: Rocket 4.0 1TB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B
    speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter> rev: RKT401.3
    temp: 37.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital
    model: WD10EZEX-00WN4A0 size: 931.51 GiB block-size: physical: 4096 B
    logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: 1A01 scheme: MBR
  ID-3: /dev/sdb maj-min: 8:16 vendor: Patriot model: Blast
    size: 111.79 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: 12.2 scheme: GPT
  ID-4: /dev/sdc maj-min: 8:32 vendor: Hitachi model: HUA723020ALA641
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    type: HDD rpm: 7200 serial: <filter> rev: A840 scheme: MBR
  ID-5: /dev/sdd maj-min: 8:48 type: USB vendor: Seagate model: ST9500325AS
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B type: HDD
    rpm: 5400 serial: <filter> rev: 0001 scheme: MBR
  ID-6: /dev/sde maj-min: 8:64 type: USB vendor: Western Digital model: WD
    My Passport 2627 size: 1.82 TiB block-size: physical: 512 B
    logical: 512 B type: N/A serial: <filter> rev: 4008 scheme: GPT
Partition:
  ID-1: / raw-size: 931.22 GiB size: 915.53 GiB (98.32%) used: 825.05 GiB
    (90.1%) fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 25.5 MiB
    (8.5%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 38.0 C mobo: N/A gpu: nvidia temp: 40 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Info:
  Processes: 435 Uptime: 4m wakeups: 0 Memory: 31.15 GiB used: 3.37 GiB
  (10.8%) Init: systemd v: 251 default: graphical tool: systemctl
  Compilers: gcc: 12.1.1 clang: 14.0.6 Packages: 1575 pm: pacman pkgs: 1535
  libs: 427 tools: gnome-software,pamac,yay pm: rpm pkgs: 0 pm: flatpak
  pkgs: 40 Shell: Zsh v: 5.9 running-in: gnome-terminal inxi: 3.3.21

Thanks!
Note that you may need some of those kernel parameters, and ibt=off as well.
Also if you have any blacklistings in /etc/modprobe.d or elsewhere, you may need them too.

If you backup your current /etc tree, you may need to check if you have any special settings there, if EndeavourOS is not working as expected.

Are you actively using both of those Nvidia cards?

1 Like

I definitely know kernel parameters I added will be needed haha.
I’m not familiar with the ibt=off parameter, what does it do?

I do have a blacklist in etc/modprobe.d, one that is confusing me is mhwd-gpu.conf.
The file tells me it is Generated by mhwd - Manjaro Hardware Detection.
I’m guessing there is a EOS equivalent where I can place those same blacklist entries?

I am actively using the 3070 as main GPU, while the 970 has been setup as a pass-through for virtual machines.

Prevents Nvidia driver from crashimg on certain systems, including yours.

1 Like

Likely you can copy (all or some of) those blackists to /etc/modprobe.d or
/usr/lib/modprobe.d.
EndeavourOS does not have a toolset similar to mhwd, but does certain hardware detection at install time.

1 Like

That does make sense, my question about that is should those blacklist entries be in modprobe.d itself or a file within that directory?

File(s) under the existing /etc/modprobe.d/ folder.
I guess this is what you meant
Could you show that blacklist file?

Sure thing, the file in question within etc/modprobe.d is called mhwd-gpu.conf

##
## Generated by mhwd - Manjaro Hardware Detection
##
 
blacklist nouveau
blacklist ttm
blacklist drm_kms_helper
blacklist drm

The other two files within that same directory are firewalld-sysctls.conf and vfio.conf