MX-23 RC3 (Xfce) Feedback thread

Message
Author
BV206
Posts: 499
Joined: Sat Mar 09, 2019 10:55 am

Re: MX-23 RC3 (Xfce) Feedback thread

#21 Post by BV206 »

I can't get pulseaudio volume control or alsamixer to remember the volume levels.
Before pipewire I could set my audio levels and "sudo alsactl store" but that no longer works on MX23.

User avatar
entropyfoe
Posts: 615
Joined: Thu Apr 19, 2007 11:42 am

Re: MX-23 RC3 (Xfce) Feedback thread

#22 Post by entropyfoe »


you're in a safe space, in the hands of people you can rely on and depend on
Yes, this is my experience with MX, a group of developers and forum members you can depend on. :happy:

OK, I downloaded the RC3, md5 was good, burned to the same 4G stick used for earlier tests with the MX live USB maker, from the RC2 installation.

Installation was fast and easy,. I think the most interest is in the installer, where most problems have been happening. I reused nvme0p2 for SWAP, and nvme0P4 for / as before for betas and earlier RCs.

But this time I got a warning when I started the install to the marked partitions...

"The system is uses EFI, but no valid EFI system partition was assigned to /boot/efi separately. Are you sure you want to continue?"

I answered yes, and the install proceeded normally. [I boot these test installs from the GRUB in my MX21. So GRUB of the install goes to PBR] I rebooted to the MX 21, updated grub and rebooted and I am posting from the new install now.

So far so good.
I will start tweaking and report more later.
MX 23.5 on Asus PRIME X470-PRO
AMD Ryzen 3600X (12 threads @ 3.8 GHz)
32 Gig DDR4 3600 (Crucial CL 16)
Nvidia GeForce GT 710
Samsung 970 NVMe nvme0n1 P1-3=MX-23.5, P4=testing
Samsung 980 NVMe =1TB Data, plus 2TB WD =backups
on-board ethernet & sound

BV206
Posts: 499
Joined: Sat Mar 09, 2019 10:55 am

Re: MX-23 RC3 (Xfce) Feedback thread

#23 Post by BV206 »

When booted in systemd I get a network manager failure but networking still works.

Code: Select all

$ systemctl --failed
  UNIT                   LOAD   ACTIVE SUB    DESCRIPTION    
● NetworkManager.service loaded failed failed Network Manager

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
1 loaded units listed.
Also I tried to make a wifi hotspot. For some reason it won't detect that I'm in the US.
I did "sudo iw reg set US" and it works for a while but won't persist after reboot.

Wi-Ffi Security settings don't seem to work right, at least in hotspot mode.
Somebody who is an expert should verify each setting and see if it's really broke.

User avatar
doodstecsonhere
Posts: 86
Joined: Sat Jun 17, 2023 10:44 am

Re: MX-23 RC3 (Xfce) Feedback thread

#24 Post by doodstecsonhere »

briainxyz wrote: Sun Jul 23, 2023 1:04 pm Hi guys and gals,

Just want to say thanks for MX-23. My 78 year old mother installed it on a Lenovo Carbon X1 Gen 6 with myself guiding the installation over the phone with the help of the MX User Manual. I've no significant issues to report (she had MX-18 on a T420s for the past 5 years. For my part, I'm a Debian user for >20 years).

My mom shared her experience after wiping Windows 10 completely. This is what she said:

"You get the feeling that you're part of something intelligent and all-embracing. And that your not just a would be consumer of all kinds of rubbish at the whim of Microsoft. You feel a sense of belonging and that its not out to use you, and manipulate you for its own ends. You feel a sense of gratitude and that you're in a safe space, in the hands of people you can rely on and depend on."

Consequently, I'm about to flash MX-23 onto an old 4gb machine for my girlfriend who has no prior experience with computers. Much obliged to the MX Linux and Debian focus groups ;)
:number1: Awesome! Thanks for sharing, @briainxyz . :) You're mom is pretty cool. Runs in the family looks like.

User avatar
doodstecsonhere
Posts: 86
Joined: Sat Jun 17, 2023 10:44 am

Re: MX-23 RC3 (Xfce) Feedback thread

#25 Post by doodstecsonhere »

j2mcgreg wrote: Sun Jul 23, 2023 1:47 pm Tell your mother to set up an account here.

Hahaha! That would be fun if she's game. :happy:

User avatar
doodstecsonhere
Posts: 86
Joined: Sat Jun 17, 2023 10:44 am

Re: MX-23 RC3 (Xfce) Feedback thread

#26 Post by doodstecsonhere »

Jerry3904 wrote: Sun Jul 23, 2023 8:34 pm I wish we could that on the front page of the website!
great idea! :number1:

User avatar
entropyfoe
Posts: 615
Joined: Thu Apr 19, 2007 11:42 am

Re: MX-23 RC3 (Xfce) Feedback thread

#27 Post by entropyfoe »

OK, looks like complete success from my view. Installed flawlessly, I did all tweaks, everything working, even fsearch [glad to see it back in the repo for the MX23], in RC1 [updated installer], fsearch would not run, giving an error, I was just going to post it, but I saw the RC3 announcement. It works now. The installer worked well for me.

Nice to see the fresh Debian stable kernel, 6.1.38-1, dated about a week ago.
For me it is ready to release ! :happy: Thanks to all who built this.

Code: Select all

System:
  Kernel: 6.1.0-10-amd64 [6.1.38-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-10-amd64 root=UUID=<filter> ro quiet splash
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23_RC3_x64 Libretto July 24  2023 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME X470-PRO v: Rev X.0x serial: <superuser required>
    UEFI-[Legacy]: American Megatrends v: 5204 date: 07/29/2019
CPU:
  Info: model: AMD Ryzen 5 3600X bits: 64 type: MT MCP arch: Zen 2 gen: 3 level: v3 note: check
    built: 2020-22 process: TSMC n7 (7nm) family: 0x17 (23) model-id: 0x71 (113) stepping: 0
    microcode: 0x8701013
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache: L1: 384 KiB
    desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB L3: 32 MiB desc: 2x16 MiB
  Speed (MHz): avg: 2197 high: 2200 min/max: 2200/4409 boost: enabled scaling:
    driver: acpi-cpufreq governor: ondemand cores: 1: 2200 2: 2200 3: 2200 4: 2195 5: 2196 6: 2196
    7: 2196 8: 2196 9: 2200 10: 2196 11: 2200 12: 2196 bogomips: 91029
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  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 status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT enabled with STIBP protection
  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: Retpolines, IBPB: conditional, STIBP: always-on, RSB filling,
    PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GK208B [GeForce GT 710] vendor: Micro-Star MSI driver: nvidia v: 470.199.02
    non-free: series: 470.xx+ status: legacy-active (EOL~2023/24) arch: Fermi 2 code: GF119/GK208
    process: TSMC 28nm built: 2010-16 pcie: gen: 2 speed: 5 GT/s lanes: 8 bus-ID: 09:00.0
    chip-ID: 10de:128b class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: nvidia
    gpu: nvidia display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.00x11.26") s-diag: 583mm (22.95")
  Monitor-1: HDMI-0 res: 1920x1080 hz: 60 dpi: 96 size: 509x286mm (20.04x11.26")
    diag: 584mm (22.99") modes: N/A
  API: OpenGL v: 4.6.0 NVIDIA 470.199.02 renderer: NVIDIA GeForce GT 710/PCIe/SSE2
    direct-render: Yes
Audio:
  Device-1: NVIDIA GK208 HDMI/DP Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie:
    gen: 2 speed: 5 GT/s lanes: 8 bus-ID: 09:00.1 chip-ID: 10de:0e0f class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie:
    gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 0b:00.4 chip-ID: 1022:1487 class-ID: 0403
  API: ALSA v: k6.1.0-10-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 07:00.0 chip-ID: 8086:1539 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 1.25 TiB used: 567.65 GiB (44.2%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO Plus 250GB
    size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD
    serial: <filter> rev: 2B2QEXM7 temp: 37.9 C scheme: MBR
  ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 840 PRO Series size: 119.24 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 5B0Q
    scheme: MBR
  ID-3: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 1B6Q
    scheme: MBR
Partition:
  ID-1: / raw-size: 88.35 GiB size: 86.41 GiB (97.80%) used: 8.56 GiB (9.9%) fs: ext4
    dev: /dev/nvme0n1p4 maj-min: 259:4
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 32.23 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p2 maj-min: 259:2
Sensors:
  System Temperatures: cpu: 48.0 C mobo: 33.0 C gpu: nvidia temp: 48 C
  Fan Speeds (RPM): cpu: 585 case-1: 0 case-2: 965 case-3: 859 gpu: nvidia fan: 50%
  Power: 12v: 12.23 5v: N/A 3.3v: N/A vbat: N/A
Repos:
  Packages: pm: dpkg pkgs: 2400 libs: 1318 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bookworm main non-free
Info:
  Processes: 317 Uptime: 42m wakeups: 1 Memory: 31.26 GiB used: 3.32 GiB (10.6%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: BIOS (legacy, CSM, MBR)
Here are my tweaks -which all worked normally. (maybe a user poll, should terminal opacity be set to 75%? I prefer much higher...)

Code: Select all

Re: 16 Things to do after installing MX
Updated
#6 Post by entropyfoe » 01 Aug 2019 15:19
1. Enable my data disk in the disk manager
2. Change my wall paper
3. Fire up synaptic and load about 30 programs (adds to maybe 240 packages with all dependencies) Such as audacity, k3b, ksnip, bleachbit, ripperx, handbrake, scid, stockfish, eboard, espeak....I really should automate this with aptik !
4. Run synaptic to get all updates [was only 7 packages]
5.Widen the panel, change the clock so it shows seconds
6. Install the NVidia driver with the MX NVIDIA Installer
7. Switch conky to the modified antiX conky
8. Set up a desktop short cut to the data drive
9. Run bleachbit to clear all the post install stuff out
10. Reboot and test stability after all the up dates
11. Configure Firefox, set home page to duckduckgo, set downloads to go to a folder on the data drive, import bookmarks, add noscript
12. Disable sudo -MX Tweak > Other tab > radial button at the bottom labeled accordingly root for admin
13. In power management set so no log-in is required from suspend
14. MX Tweak-enable compton compositing, and select MX comfort theme with thick boarders
15. set swappiness =1
16. Set terminal opacity to 99
MX 23.5 on Asus PRIME X470-PRO
AMD Ryzen 3600X (12 threads @ 3.8 GHz)
32 Gig DDR4 3600 (Crucial CL 16)
Nvidia GeForce GT 710
Samsung 970 NVMe nvme0n1 P1-3=MX-23.5, P4=testing
Samsung 980 NVMe =1TB Data, plus 2TB WD =backups
on-board ethernet & sound

User avatar
AlphaElwedritsch
Posts: 54
Joined: Fri Apr 28, 2023 5:49 am

Re: MX-23 RC3 (Xfce) Feedback thread

#28 Post by AlphaElwedritsch »

AlphaElwedritsch wrote: Sun Jul 23, 2023 2:39 pm @mklym sad, tried your suggestion with hibernation but don't work for me
@mklym do you use swap file or partition?

User avatar
Antediluvian
Posts: 346
Joined: Sun May 20, 2018 7:42 pm

Re: MX-23 RC3 (Xfce) Feedback thread

#29 Post by Antediluvian »

Can you achieve RC3 by applying MX Updater to RC2?

User avatar
mklym
Posts: 111
Joined: Fri May 03, 2019 11:54 am

Re: MX-23 RC3 (Xfce) Feedback thread

#30 Post by mklym »

AlphaElwedritsch wrote: Mon Jul 24, 2023 12:43 am
AlphaElwedritsch wrote: Sun Jul 23, 2023 2:39 pm @mklym sad, tried your suggestion with hibernation but don't work for me
@mklym do you use swap file or partition?
You must be referring to my last post in the RC2 feedback thread.
viewtopic.php?t=75984&start=120
Since I did a clean install of RC3 hibernation has not worked for me. See post #3 at the start of this thread.
viewtopic.php?p=734803#p734803
The installer set up a swap file.
CF-29LTQ, CF-30FCS, CF-31SBM, CF-52GUN, CF-53AAG, HP Z420

Life's Journey is not to arrive safely at the grave in a well preserved body, but rather to skid in sideways totally worn-out shouting 'Woo Hoo! What a ride!'

Locked

Return to “General”