MX-21 beta 1 feedback thread
Re: MX-21 beta 1 feedback thread
hello fehlix
In the cases of freeze at bios splash,
Unable to try e adding a boot parameter on boot screen. It did not progress that far.
Can the parameter be added into some file?
still here. it can be tested?
if you wish testing by adding blab= somewhere besides the boot screen, then i can happpily try it. add parameter to a file?
In the cases of freeze at bios splash,
Unable to try e adding a boot parameter on boot screen. It did not progress that far.
Can the parameter be added into some file?
still here. it can be tested?
if you wish testing by adding blab= somewhere besides the boot screen, then i can happpily try it. add parameter to a file?
Re: MX-21 beta 1 feedback thread
hello dolphin_oracle
MX21 installed system on, [WallE]
MX21 installed system on, [WallE]
Code: Select all
System: Host: WallE Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A Desktop: Xfce 4.16.0
tk: Gtk 3.24.24 wm: xfwm4 dm: LightDM
Distro: MX-21_beta1_x64 Wildflower July 27 2021 base: Debian GNU/Linux 11 (bullseye)
Machine: Type: Desktop System: HP-Pavilion product: AY022AA-ABA p6330f v: N/A
serial: <root required> Chassis: Hewlett-Packard type: 3 serial: <root required>
Mobo: MSI model: IONA v: 1.0 serial: <root required> BIOS: American Megatrends
v: 5.15 date: 06/25/2010
CPU: Dual Core: Intel Core i3 530 type: MT MCP arch: Nehalem speed: 1208 MHz
min/max: 1200/2933 MHz
Graphics: Device-1: Intel Core Processor Integrated Graphics vendor: Hewlett-Packard
driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0042
Display: x11 server: X.Org 1.20.11 driver: intel resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics (ILK) v: 2.1 Mesa 20.3.5
direct render: Yes
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Hewlett-Packard driver: r8169 v: kernel port: d800 bus ID: 01:00.0
chip ID: 10ec:8168
Drives: Local Storage: total: 29.11 GiB used: 5.78 GiB (19.9%)
Info: Processes: 203 Uptime: 8m Memory: 7.64 GiB used: 589.0 MiB (7.5%) Init: SysVinit
v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: bash v: 5.1.4
running in: xfce4-terminal inxi: 3.0.36
Re: MX-21 beta 1 feedback thread
Can't find the nvidia driver with the MX tool as no candidate is found. Tried the Tauronga NZ repo and the Salt Lake City...
Code: Select all
System: Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A
parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-8-amd64
root=UUID=<filter> ro quiet splash
Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-21_beta1_x64 Wildflower July 27 2021 base: Debian GNU/Linux 11 (bullseye)
Machine: Type: Laptop System: Dell product: Latitude E6410 v: 0001 serial: <filter> Chassis:
type: 9 serial: <filter>
Mobo: Dell model: 07XJP9 v: A01 serial: <filter> BIOS: Dell v: A05 date: 08/10/2010
Battery: ID-1: BAT0 charge: 37.2 Wh condition: 37.2/48.8 Wh (76%) volts: 12.1/11.1
model: Samsung SDI DELL PT43699 type: Li-ion serial: <filter> status: Full
CPU: Topology: Dual Core model: Intel Core i5 M 540 bits: 64 type: MT MCP arch: Nehalem
family: 6 model-id: 25 (37) stepping: 5 microcode: 7 L2 cache: 3072 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 20217
Speed: 1460 MHz min/max: 1199/2534 MHz boost: enabled Core speeds (MHz): 1: 1436
2: 1388 3: 1414 4: 1396
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds
status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable
Type: meltdown mitigation: PTI
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 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW,
STIBP: conditional, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: NVIDIA GT218M [NVS 3100M] vendor: Dell driver: nouveau v: kernel
bus ID: 01:00.0 chip ID: 10de:0a6c
Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa
resolution: 1440x900~60Hz, 1280x1024~60Hz
OpenGL: renderer: NVA8 v: 3.3 Mesa 20.3.5 direct render: Yes
Audio: Device-1: Intel 5 Series/3400 Series High Definition Audio
vendor: Dell Latitude E6410 driver: snd_hda_intel v: kernel bus ID: 00:1b.0
chip ID: 8086:3b56
Device-2: NVIDIA High Definition Audio vendor: Dell driver: snd_hda_intel v: kernel
bus ID: 01:00.1 chip ID: 10de:0be3
Sound Server: ALSA v: k5.10.0-8-amd64
Network: Device-1: Intel 82577LM Gigabit Network vendor: Dell Latitude E6410 driver: e1000e
v: kernel port: 8040 bus ID: 00:19.0 chip ID: 8086:10ea
IF: eth0 state: down mac: <filter>
Device-2: Intel Centrino Ultimate-N 6300 driver: iwlwifi v: kernel port: 7000
bus ID: 03:00.0 chip ID: 8086:422b
IF: wlan0 state: up mac: <filter>
Drives: Local Storage: total: 931.51 GiB used: 5.83 GiB (0.6%)
ID-1: /dev/sda vendor: Samsung model: SSD 870 EVO 1TB size: 931.51 GiB block size:
physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 1B6Q scheme: MBR
RAID: Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci v: 3.0
port: 8020 bus ID: 00:1f.2 chip ID: 8086.282a rev: 05
Partition: ID-1: / raw size: 24.37 GiB size: 23.82 GiB (97.74%) used: 5.83 GiB (24.5%) fs: ext4
dev: /dev/sda5
Sensors: System Temperatures: cpu: 61.0 C mobo: N/A sodimm: 44.0 C gpu: nouveau temp: 70 C
Fan Speeds (RPM): cpu: 0
Repos: 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 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
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mxrepo.com/mx/repo/ bullseye main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 236 Uptime: 18m Memory: 7.76 GiB used: 1.23 GiB (15.9%) Init: SysVinit
v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in
running in: quick-system-in inxi: 3.0.36
Re: MX-21 beta 1 feedback thread
@dolphin_oracle Forget I ever mentioned it! I was expecting a more visible reaction and didn't notice the new icon appear.dolphin_oracle wrote: Fri Jul 30, 2021 1:35 pm@Gaer Boy thanks. so no icon in the systray? Looks like a little half-sun type icon
Gigabyte B550I Aorus Pro AX, Ryzen 5 5600G, 16GB, 250GB Samsung SSD (GPT), 2x1TB HDD (MBR), MX-21-AHS
Lenovo Thinkpad X220, dual-core i5, 4MB, 120GB Samsung SSD (GPT), MX-21
Re: MX-21 beta 1 feedback thread
Thanks for the info, it is not so easier to find a small .ics calendar into Linux (I used Rainlendar in the past, then Orage, and now ???) ... tryed also a yad calendar (without ics) here https://www.antixforum.com/forums/topic ... ed-update/ ... Yad is a good idea too for a calendar.SwampRabbit wrote: Fri Jul 30, 2021 11:35 pm Orage is dead, it’s probably never coming back unless someone picks it up, this will be for every Distro running Xfce 4.16.
python3-multibootusb Also seems abandoned by the developer, the GitHub has been stagnant almost a year and a half, the website has been taken over by someone as looks to be just a sink hole, a GitHub issue for it not working with MX-19 was opened back in November of last year.
For python3-multibootusb is sad too than this project is at this level. But I will try to find a workaround.
Pour les nouveaux utilisateurs: Alt+F1 pour le manuel, ou FAQS, MX MANUEL, et Conseils Debian - Info. système “quick-system-info-mx” (QSI) ... Ici: System: MX-19_x64 & antiX19_x32
Re: MX-21 beta 1 feedback thread
I installed on two machines and also in VirtualBox. I noticed this on all. I open Thunar in my normal user and then open another with "open root thunar here". I went to MX Tweak > Window Manager > Theme and made a change.It changes in the one that I opened a root thunar here, but NOT in the normal user thunar. Seems a bit odd.
Earl
Earl
- dolphin_oracle
- Developer
- Posts: 22100
- Joined: Sun Dec 16, 2007 12:17 pm
Re: MX-21 beta 1 feedback thread
I believe you, but I can't duplicate that here.old_guy wrote: Sat Jul 31, 2021 8:13 am I installed on two machines and also in VirtualBox. I noticed this on all. I open Thunar in my normal user and then open another with "open root thunar here". I went to MX Tweak > Window Manager > Theme and made a change.It changes in the one that I opened a root thunar here, but NOT in the normal user thunar. Seems a bit odd.
Earl
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
- dolphin_oracle
- Developer
- Posts: 22100
- Joined: Sun Dec 16, 2007 12:17 pm
Re: MX-21 beta 1 feedback thread
@Shifu please attach the output of "nvidia-detect" and "nvidia-detect-mx" please.Shifu wrote: Sat Jul 31, 2021 1:52 am Can't find the nvidia driver with the MX tool as no candidate is found. Tried the Tauronga NZ repo and the Salt Lake City...
Code: Select all
System: Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-8-amd64 root=UUID=<filter> ro quiet splash Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 Distro: MX-21_beta1_x64 Wildflower July 27 2021 base: Debian GNU/Linux 11 (bullseye) Machine: Type: Laptop System: Dell product: Latitude E6410 v: 0001 serial: <filter> Chassis: type: 9 serial: <filter> Mobo: Dell model: 07XJP9 v: A01 serial: <filter> BIOS: Dell v: A05 date: 08/10/2010 Battery: ID-1: BAT0 charge: 37.2 Wh condition: 37.2/48.8 Wh (76%) volts: 12.1/11.1 model: Samsung SDI DELL PT43699 type: Li-ion serial: <filter> status: Full CPU: Topology: Dual Core model: Intel Core i5 M 540 bits: 64 type: MT MCP arch: Nehalem family: 6 model-id: 25 (37) stepping: 5 microcode: 7 L2 cache: 3072 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 20217 Speed: 1460 MHz min/max: 1199/2534 MHz boost: enabled Core speeds (MHz): 1: 1436 2: 1388 3: 1414 4: 1396 Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable Type: meltdown mitigation: PTI 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 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling Type: srbds status: Not affected Type: tsx_async_abort status: Not affected Graphics: Device-1: NVIDIA GT218M [NVS 3100M] vendor: Dell driver: nouveau v: kernel bus ID: 01:00.0 chip ID: 10de:0a6c Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa resolution: 1440x900~60Hz, 1280x1024~60Hz OpenGL: renderer: NVA8 v: 3.3 Mesa 20.3.5 direct render: Yes Audio: Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Dell Latitude E6410 driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:3b56 Device-2: NVIDIA High Definition Audio vendor: Dell driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:0be3 Sound Server: ALSA v: k5.10.0-8-amd64 Network: Device-1: Intel 82577LM Gigabit Network vendor: Dell Latitude E6410 driver: e1000e v: kernel port: 8040 bus ID: 00:19.0 chip ID: 8086:10ea IF: eth0 state: down mac: <filter> Device-2: Intel Centrino Ultimate-N 6300 driver: iwlwifi v: kernel port: 7000 bus ID: 03:00.0 chip ID: 8086:422b IF: wlan0 state: up mac: <filter> Drives: Local Storage: total: 931.51 GiB used: 5.83 GiB (0.6%) ID-1: /dev/sda vendor: Samsung model: SSD 870 EVO 1TB size: 931.51 GiB block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 1B6Q scheme: MBR RAID: Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci v: 3.0 port: 8020 bus ID: 00:1f.2 chip ID: 8086.282a rev: 05 Partition: ID-1: / raw size: 24.37 GiB size: 23.82 GiB (97.74%) used: 5.83 GiB (24.5%) fs: ext4 dev: /dev/sda5 Sensors: System Temperatures: cpu: 61.0 C mobo: N/A sodimm: 44.0 C gpu: nouveau temp: 70 C Fan Speeds (RPM): cpu: 0 Repos: 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 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 Active apt repos in: /etc/apt/sources.list.d/mx.list 1: deb http://mxrepo.com/mx/repo/ bullseye main non-free No active apt repos in: /etc/apt/sources.list.d/various.list Info: Processes: 236 Uptime: 18m Memory: 7.76 GiB used: 1.23 GiB (15.9%) Init: SysVinit v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in running in: quick-system-in inxi: 3.0.36
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
Re: MX-21 beta 1 feedback thread
Here you go. Hope it helps:dolphin_oracle wrote: Sat Jul 31, 2021 8:19 am
@Shifu please attach the output of "nvidia-detect" and "nvidia-detect-mx" please.
$ vidia-detect
Command 'vidia-detect' not found, did you mean:
command 'nvidia-detect' from deb nvidia-detect
Try: sudo apt install <deb name>
$ vidia-detect-mx
vidia-detect-mx: command not found