I think this is where your problem lies.. the checks match for me.Wallon wrote: Mon Jul 10, 2023 11:08 am Dear developers,
I have installed MX Linux KDE beta 2 in [fr_BE] on USB key (format "f2fs")
All is good.
I noticed that the SHA256 and MD5 checks on the SourceForge website do not match the ISO.
Best regards,
Wallon
MX-23 beta 2 feedback thread
- Eadwine Rose
- Administrator
- Posts: 14463
- Joined: Wed Jul 12, 2006 2:10 am
Re: MX-23 beta 2 feedback thread
MX-23.6_x64 July 31 2023 * 6.1.0-34amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Re: MX-23 beta 2 feedback thread
Dear @Eadwine Rose ,
Regarding : SHA256 and MD5 checks
It wasn't a problem for me because I installed MX KDE beta 2 - 64 bits without any problems.
Kind regards,
Wallon
Regarding : SHA256 and MD5 checks
It wasn't a problem for me because I installed MX KDE beta 2 - 64 bits without any problems.
Kind regards,
Wallon
- Eadwine Rose
- Administrator
- Posts: 14463
- Joined: Wed Jul 12, 2006 2:10 am
Re: MX-23 beta 2 feedback thread
If the numbers don't match you are bound to run into issues. Hunting those down basically are a waste of time as the iso you installed from was faulty, even though it did install. Been there, done that, just a tip for the future.
MX-23.6_x64 July 31 2023 * 6.1.0-34amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Re: MX-23 beta 2 feedback thread
This isn't really a bug report, but rather a general question about using the beta live with persistence. Once the beta period is over and the official release is out, is there any reason why I can't continue to use it? Will the beta automatically transition into the production version? I'm just curious if I'll need to re-image my USB drive once the beta is over. Thanks for all your hard work!
Re: MX-23 beta 2 feedback thread
You could use it but it wouldn't be complete. Already there are adjustments that are introduced at the build stage for the next RC1 when it comes available. Your best option is the use our "User Installed Packages" to make a list of your package modifications and reinstall when the final is released, however, we usually support RC1 and later through to full release status unless there are any major show-stoppers.
Note for reinstalling, if you've heavily modified your users accounts home folder, you can back it up and selectively restore elements that do not overwrite critical configs. If you use Firefox, you can restore your entire ~/.mozilla folder in full to the same location in your fresh install provided you have not yet opened firefox and it will be exactly as you remember it, but if you restore by overwriting the primary folders like Documents, Pictures, etc, then you may experience some oddities, however, it is perfectly safe to restore the contents of each folder without overwriting the folder itself.
Note for reinstalling, if you've heavily modified your users accounts home folder, you can back it up and selectively restore elements that do not overwrite critical configs. If you use Firefox, you can restore your entire ~/.mozilla folder in full to the same location in your fresh install provided you have not yet opened firefox and it will be exactly as you remember it, but if you restore by overwriting the primary folders like Documents, Pictures, etc, then you may experience some oddities, however, it is perfectly safe to restore the contents of each folder without overwriting the folder itself.
Mike P
Regd Linux User #472293
(Daily) Lenovo T560, i7-6600U, 16GB, 2.0TB SSD, MX_ahs
(ManCave) AMD Ryzen 5 5600G, 32G, 8TB mixed, MX_ahs
(Spare)2017 Macbook Air 7,2, 8GB, 256GB SSD, MX_ahs
Regd Linux User #472293
(Daily) Lenovo T560, i7-6600U, 16GB, 2.0TB SSD, MX_ahs
(ManCave) AMD Ryzen 5 5600G, 32G, 8TB mixed, MX_ahs
(Spare)2017 Macbook Air 7,2, 8GB, 256GB SSD, MX_ahs
Re: MX-23 beta 2 feedback thread
Dear @Eadwine Rose , Dear @dolphin_oracle , Dear @Melber , Dear @Jerry3904 , Dear @m_pav , Dear @fehlix ,
I've found the solution for using Live USB sticks with MX Fluxbox Beta 2 - 64 bits with language [fr] or [fr_BE] and with an Azerty keyboard!
I've tried several Live sticks. I always had the same problem, the icons on the desktop are not active.
I tested my Live keys on my Dell Latitude Pro 5590 laptop (i5-8350U - 16 GO ram - no graphics card - Intel UHD Graphics 620 - i915 driver). Still the same problem, the icons on the desktop are not active!
So it's not linked to the « nouveau » driver for Nvidia graphics cards!
Here's the solution for my computers;
F2 Language = French or French (BE)
F3 Time Zone = Paris or Brussels
F7 Console = ask
Press " Enter
Choose 1920x1080x8 resolution or 1920x1080x16 resolution or 1920x1080x32 resolution.
All the icons on the desktop are active on all my Live USB sticks.
Remark;
I should never do this with antiX.
I should never do this with MX Linux XFCE or MX Linux KDE.
I should never do this with Debian 12 Gnome or Debian 12 IceWm (net install each time, I don't use Calamarès).
Thank you for your patience, I know this has upset many people on the forum.
Kind regards,
Wallon
I've found the solution for using Live USB sticks with MX Fluxbox Beta 2 - 64 bits with language [fr] or [fr_BE] and with an Azerty keyboard!
I've tried several Live sticks. I always had the same problem, the icons on the desktop are not active.
I tested my Live keys on my Dell Latitude Pro 5590 laptop (i5-8350U - 16 GO ram - no graphics card - Intel UHD Graphics 620 - i915 driver). Still the same problem, the icons on the desktop are not active!
So it's not linked to the « nouveau » driver for Nvidia graphics cards!
Here's the solution for my computers;
F2 Language = French or French (BE)
F3 Time Zone = Paris or Brussels
F7 Console = ask
Press " Enter
Choose 1920x1080x8 resolution or 1920x1080x16 resolution or 1920x1080x32 resolution.
All the icons on the desktop are active on all my Live USB sticks.
Remark;
I should never do this with antiX.
I should never do this with MX Linux XFCE or MX Linux KDE.
I should never do this with Debian 12 Gnome or Debian 12 IceWm (net install each time, I don't use Calamarès).
Thank you for your patience, I know this has upset many people on the forum.
Kind regards,
Wallon
- dolphin_oracle
- Developer
- Posts: 22066
- Joined: Sun Dec 16, 2007 12:17 pm
Re: MX-23 beta 2 feedback thread
not upset, just puzzled.Wallon wrote: Tue Jul 11, 2023 7:51 am Dear @Eadwine Rose , Dear @dolphin_oracle , Dear @Melber , Dear @Jerry3904 , Dear @m_pav , Dear @fehlix ,
I've found the solution for using Live USB sticks with MX Fluxbox Beta 2 - 64 bits with language [fr] or [fr_BE] and with an Azerty keyboard!
I've tried several Live sticks. I always had the same problem, the icons on the desktop are not active.
I tested my Live keys on my Dell Latitude Pro 5590 laptop (i5-8350U - 16 GO ram - no graphics card - Intel UHD Graphics 620 - i915 driver). Still the same problem, the icons on the desktop are not active!
So it's not linked to the « nouveau » driver for Nvidia graphics cards!
Here's the solution for my computers;
F2 Language = French or French (BE)
F3 Time Zone = Paris or Brussels
F7 Console = ask
Press " Enter
Choose 1920x1080x8 resolution or 1920x1080x16 resolution or 1920x1080x32 resolution.
All the icons on the desktop are active on all my Live USB sticks.
Remark;
I should never do this with antiX.
I should never do this with MX Linux XFCE or MX Linux KDE.
I should never do this with Debian 12 Gnome or Debian 12 IceWm (net install each time, I don't use Calamarès).
Thank you for your patience, I know this has upset many people on the forum.
Kind regards,
Wallon
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-23 beta 2 feedback thread
I am having issues with MXPI.
See screenshots below.
It says no internet, but I have internet:
See screenshots below.
It says no internet, but I have internet:
Code: Select all
sudo apt update && sudo apt upgrade 18:57:44
[sudo] password for Shmuel:
Hit:1 https://dl.google.com/linux/chrome/deb stable InRelease
Hit:2 http://deb.debian.org/debian bookworm-updates InRelease
Hit:4 http://deb.debian.org/debian bookworm InRelease
Hit:5 https://linux.teamviewer.com/deb stable InRelease
Hit:3 https://mxrepo.com/mx/repo bookworm InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
4 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
apt-notifier mx-docs mx-installer mx-user
4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 0 B/116 MB of archives.
After this operation, 1,852 kB of additional disk space will be used.
Do you want to continue? [Y/n]
(Reading database ... 362400 files and directories currently installed.)
Preparing to unpack .../apt-notifier_23.07.02_all.deb ...
Unpacking apt-notifier (23.07.02) over (23.07.01) ...
Preparing to unpack .../mx-docs_20230710_all.deb ...
Unpacking mx-docs (20230710) over (20230701+1) ...
Preparing to unpack .../mx-installer_23.7.02mx23_amd64.deb ...
Unpacking mx-installer (23.7.02mx23) over (23.7.01mx23) ...
Preparing to unpack .../mx-user_23.7.03_amd64.deb ...
Unpacking mx-user (23.7.03) over (23.7.02) ...
Setting up mx-user (23.7.03) ...
Setting up mx-installer (23.7.02mx23) ...
Setting up appimagelauncher (2.2.0-travis995~0f91801+bionic) ...
Installing AppImageLauncher as interpreter for AppImages
+ systemctl restart systemd-binfmt
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
dpkg: error processing package appimagelauncher (--configure):
installed appimagelauncher package post-installation script subprocess returned error exit status 1
Setting up apt-notifier (23.07.02) ...
Setting up mx-docs (20230710) ...
Processing triggers for desktop-file-utils (0.26-1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for gnome-menus (3.36.0-1.1) ...
Processing triggers for mailcap (3.70+nmu1) ...
Errors were encountered while processing:
appimagelauncher
E: Sub-process /usr/bin/dpkg returned an error code (1)
Code: Select all
System:
Kernel: 6.1.0-9-amd64 [6.1.27-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-9-amd64 root=UUID=<filter> ro quiet splash
Desktop: KDE Plasma v: 5.27.5 tk: Qt v: 5.15.8 wm: kwin_x11 vt: 7 dm: SDDM
Distro: MX-23_beta2_x64 Libretto June 15 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Desktop Mobo: ASUSTeK model: PRIME B365M-A v: Rev X.0x serial: <superuser required>
UEFI: American Megatrends v: 2208 date: 07/09/2021
Battery:
ID-1: hidpp_battery_0 charge: 56% condition: N/A volts: 3.8 min: N/A model: Logitech G903
LIGHTSPEED Wireless Gaming Mouse w/ HERO type: N/A serial: <filter> status: discharging
CPU:
Info: model: Intel Core i7-9700 bits: 64 type: MCP arch: Coffee Lake gen: core 9 level: v3
note: check built: 2018 process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 0xD (13)
microcode: 0xF8
Topology: cpus: 1x cores: 8 smt: <unsupported> cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB
L2: 2 MiB desc: 8x256 KiB L3: 12 MiB desc: 1x12 MiB
Speed (MHz): avg: 800 min/max: 800/4700 scaling: driver: intel_pstate governor: powersave
cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 bogomips: 48000
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel CoffeeLake-S GT2 [UHD Graphics 630] vendor: ASUSTeK driver: i915 v: kernel
arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: HDMI-A-1,HDMI-A-2 empty: DP-1
bus-ID: 00:02.0 chip-ID: 8086:3e98 class-ID: 0300
Device-2: USB C Video Adaptor type: USB driver: N/A bus-ID: 1-3.1.1:8 chip-ID: 25a4:9321
class-ID: 1100 serial: <filter>
Device-3: Microdia USB Live camera type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-3.4:7
chip-ID: 0c45:636b class-ID: 0102 serial: <filter>
Display: x11 server: X.Org v: 1.21.1.7 compositor: kwin_x11 driver: X: loaded: modesetting
unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1016x285mm (40.00x11.22")
s-diag: 1055mm (41.54")
Monitor-1: HDMI-A-1 mapped: HDMI-1 pos: primary,left model: VG27AQ1A serial: <filter>
built: 2020 res: 1920x1080 dpi: 82 gamma: 1.2 size: 596x336mm (23.46x13.23") diag: 685mm (27")
ratio: 16:9 modes: max: 2560x1440 min: 720x400
Monitor-2: HDMI-A-2 mapped: HDMI-2 pos: right model: Samsung S24B300 serial: <filter>
built: 2013 res: 1920x1080 hz: 60 dpi: 94 gamma: 1.2 size: 521x293mm (20.51x11.54")
diag: 598mm (23.5") ratio: 16:9 modes: max: 1920x1080 min: 720x400
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
direct-render: Yes
Audio:
Device-1: Intel 200 Series PCH HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
bus-ID: 1-3.4:7 bus-ID: 00:1f.3 chip-ID: 0c45:636b chip-ID: 8086:a2f0 class-ID: 0102
class-ID: 0403 serial: <filter>
Device-2: Microdia USB Live camera type: USB driver: snd-usb-audio,uvcvideo
API: ALSA v: k6.1.0-9-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: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK PRIME B450M-A
driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 03:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Realtek RTL8153 Gigabit Ethernet Adapter type: USB driver: r8152 bus-ID: 2-4.1:7
chip-ID: 0bda:8153 class-ID: 0000 serial: <filter>
IF: eth1 state: down mac: <filter>
Bluetooth:
Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB driver: btusb v: 0.8
bus-ID: 1-10:6 chip-ID: 0a12:0001 class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 2.1 lmp-v: 4.0
sub-v: 22bb hci-v: 4.0 rev: 22bb
Info: acl-mtu: 310:10 sco-mtu: 64:8 link-policy: rswitch hold sniff park
link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
telephony
Drives:
Local Storage: total: 2.26 TiB used: 916.56 GiB (39.7%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37480G size: 447.13 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: K1B3 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Toshiba model: HDWD120 size: 1.82 TiB block-size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: ACF0
scheme: GPT
Partition:
ID-1: / raw-size: 46.96 GiB size: 45.92 GiB (97.79%) used: 13.07 GiB (28.5%) fs: ext4
dev: /dev/sda7 maj-min: 8:7
ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%) used: 26.7 MiB (27.8%) fs: vfat
dev: /dev/sda1 maj-min: 8:1
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 42.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos:
Packages: pm: dpkg pkgs: 2673 libs: 1431 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
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/mx.list
1: deb http://mxrepo.com/mx/repo/ bookworm main non-free
Active apt repos in: /etc/apt/sources.list.d/teamviewer.list
1: deb [signed-by=/usr/share/keyrings/teamviewer-keyring.gpg] https://linux.teamviewer.com/deb stable main
Info:
Processes: 265 Uptime: 16m wakeups: 8 Memory: 15.49 GiB used: 3.67 GiB (23.7%) Init: SysVinit
v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12 Client: shell wrapper
v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
You do not have the required permissions to view the files attached to this post.
Re: MX-23 beta 2 feedback thread
After the errors with MXPI, the desktop freezes
Re: MX-23 beta 2 feedback thread
Thanks! I'll probably do a re-install, it's a little bit of work to get things back to where I am now on the beta but it's probably the best thing to do. I'm not too customized at this point that I couldn't re-create things in a hour or so (or less). The beta has been pretty solid thus far for me, other than the issue I had with not having the correct zram init script installed because I didn't have zramswap-sysvinit-compat installed and was using the script that came by default.m_pav wrote: Tue Jul 11, 2023 7:41 am You could use it but it wouldn't be complete. Already there are adjustments that are introduced at the build stage for the next RC1 when it comes available. Your best option is the use our "User Installed Packages" to make a list of your package modifications and reinstall when the final is released, however, we usually support RC1 and later through to full release status unless there are any major show-stoppers.
Note for reinstalling, if you've heavily modified your users accounts home folder, you can back it up and selectively restore elements that do not overwrite critical configs. If you use Firefox, you can restore your entire ~/.mozilla folder in full to the same location in your fresh install provided you have not yet opened firefox and it will be exactly as you remember it, but if you restore by overwriting the primary folders like Documents, Pictures, etc, then you may experience some oddities, however, it is perfectly safe to restore the contents of each folder without overwriting the folder itself.
Really looking forward to the release!