Fehlix wrote:
"Hmme, the QSI shows you booted in UEFI. The F2-language selection is only available in BIOS/MBR mode - not within UEFI GRUB menu. So that's a bit unclear within your report."
As I said, this QSI belongs to my desktop computer and it is not relevant for this issue. It is NOT the QSI of the beta 1. Only posted to insure that the report was accepted.
Are you saying that only the displayed text "Alt-F1 Vides spousteci proces" and "Alt-F10 vratit se sem". is within the wrong language? Is it translated with another language, or is the line untranslated in English? (Ooops re-read it again:) You are saying it is displayed in Czech, not in Catalan and not in English. OK.
Yes, other texts appear in Catalan.
But the system booted further into the correct selected language?
Another Yes, the system starts in Catalan whenever possible.
And does happen in both UEFI-boot and BIOS/MBR or only within one?
It happened from MX-21 (not in previous issues) on different hardware: Desktop, laptop, BIOS, UEFI...
MX-23 beta 1 feedback thread
Re: MX-23 beta 1 feedback thread
MX-21.3_x64 KDE Plasma / ASUSTeK PRIME B250M-A / Intel Core i5-7500 / Intel HD Graphics 630 + i915 /1920 x 1080 pxl
Net: Realtek RTL8192EE + Realtek RTL8111/8168/8411 / HDD: 1 x SSD PLUS (1 TB); 2xST2000 (2x2 TB) / DVDRAM HL-DT.
Net: Realtek RTL8192EE + Realtek RTL8111/8168/8411 / HDD: 1 x SSD PLUS (1 TB); 2xST2000 (2x2 TB) / DVDRAM HL-DT.
Re: MX-23 beta 1 feedback thread
OK, thanks. Good, you mentioned the issue again - so I guess time to fix it. Will put onto the todo list to get fixed before MX23 got released.eselma wrote: ↑Mon May 29, 2023 5:05 pm Fehlix wrote:
"Hmme, the QSI shows you booted in UEFI. The F2-language selection is only available in BIOS/MBR mode - not within UEFI GRUB menu. So that's a bit unclear within your report."
As I said, this QSI belongs to my desktop computer and it is not relevant for this issue. It is NOT the QSI of the beta 1. Only posted to insure that the report was accepted.
Are you saying that only the displayed text "Alt-F1 Vides spousteci proces" and "Alt-F10 vratit se sem". is within the wrong language? Is it translated with another language, or is the line untranslated in English? (Ooops re-read it again:) You are saying it is displayed in Czech, not in Catalan and not in English. OK.
Yes, other texts appear in Catalan.
But the system booted further into the correct selected language?
Another Yes, the system starts in Catalan whenever possible.
And does happen in both UEFI-boot and BIOS/MBR or only within one?
It happened from MX-21 (not in previous issues) on different hardware: Desktop, laptop, BIOS, UEFI...
Re: MX-23 beta 1 feedback thread
@Jerry3904 OK, thanks. I use lxappearance to be able to change mouse cursors I've installed from the repo or from my back-up drive.Jerry3904 wrote: It will not--which is why it's not in this b1.
I tried the terminal command below (in beta1) but not all windows respect the change. (Librewolf come to mind).
Code: Select all
sudo update-alternatives --config x-cursor-themeI will definitely test those out and report my findings.Jerry3904 wrote: But it'd be great if for the sake of testing you could look carefully at the the Font and Theme for MX-23 (starting tomorrow, after the updated Font comes through). DO has done a great job with MX Tweak and our "user-devs" have done a huge amount of work on Font.
This is my Fluxbox . There are many others like it, but this one is mine. My Fluxbox is my best friend. It is my life.
I must master it as I must master my life. Without me, my Fluxbox is useless. Without my Fluxbox, I am useless.
I must master it as I must master my life. Without me, my Fluxbox is useless. Without my Fluxbox, I am useless.
Re: MX-23 beta 1 feedback thread
mxfluxbox (Will X and K any difference?)
minstall --oem, minstall -o
i am not getting anything different than a normal installation.
it gets to the page to fill in username and password, so i abort and try again --oem. no luck. What does --oem success start with?
this with su-to-root -X -c minstall --oem; root author password accepted.
minstall --oem, minstall -o
i am not getting anything different than a normal installation.
it gets to the page to fill in username and password, so i abort and try again --oem. no luck. What does --oem success start with?
this with su-to-root -X -c minstall --oem; root author password accepted.
You do not have the required permissions to view the files attached to this post.
Last edited by i_ri on Mon May 29, 2023 9:19 pm, edited 1 time in total.
Re: MX-23 beta 1 feedback thread
Updates just came through for me. We have fixed the dock function, but the location is TopLeft (was short of time, just copied what had been posted). Will change.
Font looks correct now.
EDIT: uploaded corrected dock location, changed desktop icons to Papirus
Font looks correct now.
EDIT: uploaded corrected dock location, changed desktop icons to Papirus
Production: 5.10, MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Re: MX-23 beta 1 feedback thread
Coming to you LIVE from MX-23 Xfce x64 Beta-1. QSI:
Issue: Tried to use this live USB (Micro SD) on a Legacy Machine -- Asus P5KPL.
Result: Boot starts, GRUB loads, able to traverse menu items. But...
====> Boot Hangs at "udev" and never completes
Here's the LUM log:
So, near the top of the log:
Live USB made with MX-LUM on this (UEFI) machine; checksums all OK; using it now on this machine. However, when creating using LUM, I did notice that there are only 2 partitions, not the usual 3:
When using MX-LUM, I usually see something like this:
However, from the LUM log for Beta-1, I get this:
Is the BIOS partition missing? Is a missing BIOS partition causing GRUB to hang on the Asus P5KPL? Do I need to use MX-LUM from the BIOS machine (Asus P5KPL)?
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=/antiX/vmlinuz quiet splasht nosplash
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_beta1_x64 Libretto May 28 2023 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Desktop System: Gigabyte product: H270-HD3 v: N/A serial: <superuser required>
Mobo: Gigabyte model: H270-HD3-CF v: x.x serial: <superuser required> UEFI: American Megatrends
v: F5 date: 04/24/2017
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse PID:0080 serial: N/A
charge: 55% (should be ignored) rechargeable: yes status: discharging
CPU:
Info: model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake gen: core 7 level: v3
note: check built: 2018 process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 9
microcode: 0x42
Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
Speed (MHz): avg: 1600 min/max: 800/3900 scaling: driver: intel_pstate governor: powersave
cores: 1: 1600 2: 1600 3: 1600 4: 1600 bogomips: 31199
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
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: mmio_stale_data status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT
vulnerable
Type: retbleed status: Vulnerable
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Retpolines, STIBP: disabled, RSB filling, PBRSB-eIBRS: Not
affected
Type: srbds status: Vulnerable: No microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Oland PRO [Radeon R7 240/340 / Radeon 520] vendor: Micro-Star MSI driver: radeon
v: kernel alternate: amdgpu arch: GCN-1 code: Southern Islands process: TSMC 28nm built: 2011-20
pcie: gen: 3 speed: 8 GT/s lanes: 8 ports: active: HDMI-A-1 empty: DVI-D-1,VGA-1
bus-ID: 01:00.0 chip-ID: 1002:6613 class-ID: 0300 temp: 40.0 C
Device-2: HD WEBCAM NexiGo N660 FHD type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-8:7
chip-ID: 1d6c:1278 class-ID: 0102 serial: <filter>
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: radeon
unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: radeon display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
Monitor-1: HDMI-A-1 mapped: HDMI-0 model: Samsung built: 2007 res: 1920x1080 hz: 60 dpi: 305
gamma: 1.2 size: 160x90mm (6.3x3.54") diag: 184mm (7.2") ratio: 16:9 modes: max: 1920x1080
min: 640x480
API: OpenGL v: 4.5 Mesa 22.3.6 renderer: OLAND ( LLVM 15.0.6 DRM 2.50 6.1.0-9-amd64)
direct-render: Yes
Audio:
Device-1: Intel 200 Series PCH HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel
bus-ID: 1-8:7 chip-ID: 1d6c:1278 bus-ID: 00:1f.3 chip-ID: 8086:a2f0 class-ID: 0102
serial: <filter> class-ID: 0403
Device-2: AMD Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000 Series]
vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 8
bus-ID: 01:00.1 chip-ID: 1002:aab0 class-ID: 0403
Device-3: HD WEBCAM NexiGo N660 FHD 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: Intel Ethernet I219-V vendor: Gigabyte driver: e1000e v: kernel port: N/A
bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 7.75 TiB used: 1.96 GiB (0.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO 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: 1B2QEXE7 temp: 32.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37120G size: 111.79 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 61K1 scheme: MBR
ID-3: /dev/sdb maj-min: 8:16 vendor: Toshiba model: DT01ACA050 size: 465.76 GiB block-size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: A750
scheme: GPT
ID-4: /dev/sdc maj-min: 8:32 model: SATA SSD size: 111.79 GiB block-size: physical: 512 B
logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 61.3 scheme: GPT
ID-5: /dev/sdd maj-min: 8:48 vendor: Seagate model: ST3000DM001-1ER166 size: 2.73 TiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
rev: CC25 scheme: GPT
ID-6: /dev/sde maj-min: 8:64 vendor: Western Digital model: WD5000AADS-00S9B0 size: 465.76 GiB
block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: N/A serial: <filter> rev: 0A01
scheme: GPT
ID-7: /dev/sdf maj-min: 8:80 type: USB model: Mass Storage Device size: 29.49 GiB block-size:
physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1.00 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
ID-8: /dev/sdl maj-min: 8:176 type: USB vendor: Seagate model: Expansion Desk size: 3.64 TiB
block-size: physical: 4096 B logical: 4096 B type: N/A serial: <filter> rev: 0739 scheme: MBR
Partition:
Message: No partition data found.
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 38.0 C mobo: N/A gpu: radeon temp: 40.0 C
Fan Speeds (RPM): N/A
Repos:
Packages: pm: dpkg pkgs: 2032 libs: 1032 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
pkgs: 0 pm: flatpak pkgs: 0
No active apt repos in: /etc/apt/sources.list
No active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
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/mx.list
1: deb http://mxrepo.com/mx/repo/ bookworm main non-free
Info:
Processes: 223 Uptime: 6m wakeups: 3 Memory: 31.3 GiB used: 2.06 GiB (6.6%) 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: UEFIResult: Boot starts, GRUB loads, able to traverse menu items. But...
====> Boot Hangs at "udev" and never completes
Here's the LUM log:
Code: Select all
=====================================================================
/usr/local/bin/live-usb-maker gui -N --label=MX23_XFCE_BETA1 -C off --from=/media/opera-dude/Seagate Expansion Drive/Documents/Computer/OS/Linux Distros/MX Linux/MX-23_Beta1/XFCE/x64/MX-23_beta1_x64.iso -t /dev/sdk
program: live-usb-maker
started: Mon 29 May 2023 11:45:05 AM IDT
version: 2.41.19-2302 (Sat, 25 Feb 2023 12:45:10 -0500)
kernel: 5.10.0-23-amd64
OS: MX 21.3 (Wildflower)
found lib: /usr/local/lib/cli-shell-utils/cli-shell-utils.bash
lib version: 2.41.05-2302 (Sat, 25 Feb 2023 12:45:10 -0500)
---------------------------------------------------------------------
Found man page: live-usb-maker.1
Will use target device /dev/sdk (29.5G Generic STORAGE_DEVICE)
Will use source file /media/opera-dude/Seagate Expansion Drive/Documents/Computer/OS/Linux Distros/MX Linux/MX-23_Beta1/XFCE/x64/MX-23_beta1_x64.iso
Distro: MX-23_beta1_x64 Libretto May 28, 2023
Found grub config 2.0
Estimated extfs overhead for 30149M is 44M
Total Used Extra
entire drive 29.5 GiB 29.5 GiB 1 MiB
main partition 29.4 GiB 2.00 GiB 27.4 GiB
uefi partition 50 MiB 32 MiB 18 MiB
Ready to make live-usb on device sdk
... by copying file /media/opera-dude/Seagate Expansion Drive/Documents/Computer/OS/Linux Distros/MX Linux/MX-23_Beta1/XFCE/x64/MX-23_beta1_x64.iso
>> partition-clear
Total bytes: 31666995200
Total blocks: 61849600
> dd status=none if=/dev/zero of=/dev/sdk bs=512 count=34
> dd status=none if=/dev/zero of=/dev/sdk bs=512 count=34 seek=64
> dd status=none conv=notrunc if=/dev/zero of=/dev/sdk bs=512 count=34 seek=61849566
> partprobe /dev/sdk
>> partition-make
Using msdos partitioning
> parted --script --align optimal /dev/sdk unit MiB mklabel msdos
> dd status=none if=/dev/zero of=/dev/sdk seek=1024 bs=1K count=128
> parted --script --align optimal /dev/sdk unit MiB mkpart primary 1 30149
> parted --script --align optimal /dev/sdk unit MiB set 1 boot on
> dd status=none if=/dev/zero of=/dev/sdk seek=30872576 bs=1K count=128
> parted --script --align optimal /dev/sdk unit MiB mkpart primary 30149 30198
> parted --script --align optimal /dev/sdk unit MiB set 2 esp on
> partprobe /dev/sdk
> wait_for_file /dev/sdk1
>> makefs-bios
> mkfs.ext4 -O ^64bit -m0 -i16384 -J size=32 /dev/sdk1
mke2fs 1.46.2 (28-Feb-2021)
64-bit filesystem support is not enabled. The larger fields afforded by this feature enable full-strength checksumming. Pass -O 64bit to rectify.
Creating filesystem with 7717888 4k blocks and 1929536 inodes
Filesystem UUID: bc2eda53-a117-4b21-8119-e13975c9d51d
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Allocating group tables: 0/236 done
Writing inode tables: 0/236 done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: 0/236 done
> tune2fs -L MX23_XFCE_BETA1 /dev/sdk1
tune2fs 1.46.2 (28-Feb-2021)
> wait_for_file /dev/sdk2
>> makefs-uefi
> mkfs.vfat -F 32 -n MX-UEFI /dev/sdk2
mkfs.fat 4.2 (2021-01-31)
> partprobe /dev/sdk
> wait_for_file /dev/sdk1
> mkdir -p /run/live-usb-maker/main
> mount -t ext4 /dev/sdk1 /run/live-usb-maker/main
> wait_for_file /dev/sdk2
> mkdir -p /run/live-usb-maker/uefi
> mount -t vfat /dev/sdk2 /run/live-usb-maker/uefi
Filesystem Type Size Used Avail Use% Mounted on
/dev/sdk1 ext4 29G 24K 29G 1% /run/live-usb-maker/main
/dev/sdk2 vfat 49M 512 49M 1% /run/live-usb-maker/uefi
>> copy-uefi
copy from iso to uefi partition
files [Ee][Ff][Ii] version
> cp --no-dereference --preserve=mode,links --recursive /run/live-usb-maker/iso/EFI /run/live-usb-maker/uefi/.
> cp --no-dereference --preserve=mode,links --recursive /run/live-usb-maker/iso/version /run/live-usb-maker/uefi/.
Fix Dell uefi memtest bug
> cp /run/live-usb-maker/uefi/EFI/BOOT/grubx64.efi /run/live-usb-maker/uefi/EFI/BOOT/fallback.efi
>> copy-main
> rm -rf /run/live-usb-maker/main/boot.orig
copy from iso to main partition
vm.dirty_bytes = 20000000
copy /antiX/vmlinuz
> cpio -pdm --quiet /run/live-usb-maker/main/
> e4defrag -v ./antiX/vmlinuz
e4defrag 1.46.2 (28-Feb-2021)
ext4 defragmentation for ./antiX/vmlinuz
[1/1][1/1]./antiX/vmlinuz: 100% extents: 1 -> 1 [ OK ]
Success: [1/1]
copy /antiX/initrd.gz
> cpio -pdm --quiet /run/live-usb-maker/main/
> e4defrag -v ./antiX/initrd.gz
e4defrag 1.46.2 (28-Feb-2021)
ext4 defragmentation for ./antiX/initrd.gz
[1/1][1/1]./antiX/initrd.gz: 100% extents: 1 -> 1 [ OK ]
Success: [1/1]
copy remaining files ...
> cpio -pdm --quiet /run/live-usb-maker/main/
copy pids: 40267 40270
vm.dirty_bytes = 20000000
vm.dirty_ratio = 0
> write_file /run/live-usb-maker/main/made-by-live-usb-maker created: Mon 29 May 2023 11:47:03 AM IDT
program: live-usb-maker
version: 2.41.19-2302 (Sat, 25 Feb 2023 12:45:10 -0500)
> dd status=none if=/dev/urandom of=/run/live-usb-maker/main/antiX/random-seed bs=512 count=1
> chmod 600 /run/live-usb-maker/main/antiX/random-seed
> rm -rf /run/live-usb-maker/main/.disk
>> check-usb-md5
check md5 for initrd.gz
> md5sum -c initrd.gz.md5
initrd.gz: OK
check md5 for linuxfs
> md5sum -c linuxfs.md5
linuxfs: OK
check md5 for vmlinuz
> md5sum -c vmlinuz.md5
vmlinuz: OK
>> uuids
Using antiX/MX grub config 2.0
> mkdir -p /run/live-usb-maker/uefi/boot/grub
> cp /run/live-usb-maker/main/boot/grub/config/efi-grub.cfg /run/live-usb-maker/uefi/boot/grub/grub.cfg
> touch /run/live-usb-maker/main/boot/grub/config/did-efi-grub
> sed -i /^\s*#/! s/%UUID%/bc2eda53-a117-4b21-8119-e13975c9d51d/ /run/live-usb-maker/uefi/boot/grub/grub.cfg
> rm -f /run/live-usb-maker/main/boot/grub/config/*.id
> touch /run/live-usb-maker/main/boot/grub/config/9ab18e6ef8b39b65d4da28d5a66c2476.id
> sed -i /^\s*#/! s|%ID_FILE%|/boot/grub/config/9ab18e6ef8b39b65d4da28d5a66c2476.id| /run/live-usb-maker/uefi/boot/grub/grub.cfg
>> install
extlinux version 6.04
> dd status=none bs=440 conv=notrunc count=1 if=/usr/lib/syslinux/mbr/mbr.bin of=/dev/sdk
> rm -f /run/live-usb-maker/main/boot/syslinux/chain.c32
> rm -f /run/live-usb-maker/main/boot/syslinux/gfxboot.c32
> rm -f /run/live-usb-maker/main/boot/syslinux/ldlinux.c32
> rm -f /run/live-usb-maker/main/boot/syslinux/libcom32.c32
> rm -f /run/live-usb-maker/main/boot/syslinux/libmenu.c32
> rm -f /run/live-usb-maker/main/boot/syslinux/libutil.c32
> rm -f /run/live-usb-maker/main/boot/syslinux/menu.c32
> rm -f /run/live-usb-maker/main/boot/syslinux/syslinux.bin
> rm -f /run/live-usb-maker/main/boot/syslinux/version
> cp /usr/lib/syslinux/modules/bios/chain.c32 /run/live-usb-maker/main/boot/syslinux/
> cp /usr/lib/syslinux/modules/bios/gfxboot.c32 /run/live-usb-maker/main/boot/syslinux/
> cp /usr/lib/syslinux/modules/bios/vesamenu.c32 /run/live-usb-maker/main/boot/syslinux/
> cp /usr/lib/syslinux/modules/bios/ldlinux.c32 /run/live-usb-maker/main/boot/syslinux/
> cp /usr/lib/syslinux/modules/bios/libcom32.c32 /run/live-usb-maker/main/boot/syslinux/
> cp /usr/lib/syslinux/modules/bios/libmenu.c32 /run/live-usb-maker/main/boot/syslinux/
> cp /usr/lib/syslinux/modules/bios/libutil.c32 /run/live-usb-maker/main/boot/syslinux/
> cp /usr/lib/syslinux/modules/bios/linux.c32 /run/live-usb-maker/main/boot/syslinux/
> cp /usr/lib/syslinux/modules/bios/menu.c32 /run/live-usb-maker/main/boot/syslinux/
> write_file /run/live-usb-maker/main/boot/syslinux/version 6.04
> extlinux -i /run/live-usb-maker/main/boot/syslinux
/run/live-usb-maker/main/boot/syslinux is device /dev/sdk1
Filesystem Type Size Used Avail Use% Mounted on
/dev/sdk1 ext4 29G 2.0G 27G 7% /run/live-usb-maker/main
/dev/sdk2 vfat 49M 13M 36M 26% /run/live-usb-maker/uefi
>> done
live-usb-maker took 2 minutes.
Code: Select all
>> makefs-bios
> mkfs.ext4 -O ^64bit -m0 -i16384 -J size=32 /dev/sdk1
mke2fs 1.46.2 (28-Feb-2021)When using MX-LUM, I usually see something like this:
Code: Select all
Total Used Extra
entire drive 29.5 GiB 29.5 GiB 1 MiB
main partition 29.3 GiB 19.2 GiB 10.1 GiB
bios partition 150 MiB 46 MiB 104 MiB
uefi partition 50 MiB 30 MiB 20 MiB
Code: Select all
entire drive 29.5 GiB 29.5 GiB 1 MiB
main partition 29.4 GiB 2.00 GiB 27.4 GiB
uefi partition 50 MiB 32 MiB 18 MiB
Last edited by operadude on Tue May 30, 2023 3:43 am, edited 1 time in total.
Re: MX-23 beta 1 feedback thread
Did you try manually editing these entries in ~/gtkrc-2.0siamhie wrote: ↑Sun May 28, 2023 6:42 pm ...Changing mouse cursors. I installed the oxygen cursor set but couldn't change the cursors from Appearance>Theme and Customize Look and Feel is missing from All Apps>Settings.
I changed it from the terminal but the mouse cursor changes back to DMX-Black when using my browser.
Code: Select all
gtk-cursor-theme-name="DMZ-Black"
gtk-cursor-theme-size=0
Code: Select all
gtk-cursor-theme-name=DMZ-Black
gtk-cursor-theme-size=0
Re: MX-23 beta 1 feedback thread
Still having issues with the updated mx-dockmaker.
When selecting a file, then mx-dockmaker will create a correct wmalauncher command line in the target *.mxdk script : But when instead setting a command and selecting an appropriate icon (as shown in below screenshot), then that custom command is written as icon name to the *.mxdk file :
... and subsequently, that entry will not appear in the dock.
Hope this can be resolved by @Adrian ?
When selecting a file, then mx-dockmaker will create a correct wmalauncher command line in the target *.mxdk script :
Code: Select all
wmalauncher --desktop-file thunar.desktop --background-color "#ff4a4a" --hover-background-color "#ff0000" --border-color "#2a2a2a" --hover-border-color "#8a8a8a" --window-size 48& sleep 0.1 Code: Select all
wmalauncher --command pkexec Thunar --icon pkexec Thunar --background-color "#ff4a4a" --hover-background-color "#ff0000" --border-color "#2a2a2a" --hover-border-color "#8a8a8a" --window-size 48& sleep 0.1Hope this can be resolved by @Adrian ?
You do not have the required permissions to view the files attached to this post.
Sony Vaio VPCF23P (2011), Intel Core i7-2670, 6gb RAM, 240gb SSD, MX-Linux 23 based Fluxbox v/1.3.7+
Lenovo Thinkpad L560 (2016), Intel Core i5-6200, 16gb RAM, 240gb SSD, Devuan Daedalus based Fluxbox v/1.3.7+
Lenovo Thinkpad L560 (2016), Intel Core i5-6200, 16gb RAM, 240gb SSD, Devuan Daedalus based Fluxbox v/1.3.7+
Re: MX-23 beta 1 feedback thread
Good catch. I thought I had seen such an extension once but then couldn't find it again and decided my eyes were crossed.
Production: 5.10, MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Re: MX-23 beta 1 feedback thread
[SOLVED]:operadude wrote: ↑Mon May 29, 2023 11:23 pm Coming to you LIVE from MX-23 Xfce x64 Beta-1. QSI:Issue: Tried to use this live USB (Micro SD) on a Legacy Machine -- Asus P5KPL.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=/antiX/vmlinuz quiet splasht nosplash 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_beta1_x64 Libretto May 28 2023 base: Debian GNU/Linux 12 (bookworm) Machine: Type: Desktop System: Gigabyte product: H270-HD3 v: N/A serial: <superuser required> Mobo: Gigabyte model: H270-HD3-CF v: x.x serial: <superuser required> UEFI: American Megatrends v: F5 date: 04/24/2017 Battery: Device-1: hidpp_battery_0 model: Logitech Wireless Mouse PID:0080 serial: N/A charge: 55% (should be ignored) rechargeable: yes status: discharging CPU: Info: model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake gen: core 7 level: v3 note: check built: 2018 process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 9 microcode: 0x42 Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB Speed (MHz): avg: 1600 min/max: 800/3900 scaling: driver: intel_pstate governor: powersave cores: 1: 1600 2: 1600 3: 1600 4: 1600 bogomips: 31199 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 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: mmio_stale_data status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable Type: retbleed status: Vulnerable Type: spec_store_bypass status: Vulnerable Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Retpolines, STIBP: disabled, RSB filling, PBRSB-eIBRS: Not affected Type: srbds status: Vulnerable: No microcode Type: tsx_async_abort status: Not affected Graphics: Device-1: AMD Oland PRO [Radeon R7 240/340 / Radeon 520] vendor: Micro-Star MSI driver: radeon v: kernel alternate: amdgpu arch: GCN-1 code: Southern Islands process: TSMC 28nm built: 2011-20 pcie: gen: 3 speed: 8 GT/s lanes: 8 ports: active: HDMI-A-1 empty: DVI-D-1,VGA-1 bus-ID: 01:00.0 chip-ID: 1002:6613 class-ID: 0300 temp: 40.0 C Device-2: HD WEBCAM NexiGo N660 FHD type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-8:7 chip-ID: 1d6c:1278 class-ID: 0102 serial: <filter> Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: radeon unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: radeon display-ID: :0.0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93") Monitor-1: HDMI-A-1 mapped: HDMI-0 model: Samsung built: 2007 res: 1920x1080 hz: 60 dpi: 305 gamma: 1.2 size: 160x90mm (6.3x3.54") diag: 184mm (7.2") ratio: 16:9 modes: max: 1920x1080 min: 640x480 API: OpenGL v: 4.5 Mesa 22.3.6 renderer: OLAND ( LLVM 15.0.6 DRM 2.50 6.1.0-9-amd64) direct-render: Yes Audio: Device-1: Intel 200 Series PCH HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel bus-ID: 1-8:7 chip-ID: 1d6c:1278 bus-ID: 00:1f.3 chip-ID: 8086:a2f0 class-ID: 0102 serial: <filter> class-ID: 0403 Device-2: AMD Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000 Series] vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 8 bus-ID: 01:00.1 chip-ID: 1002:aab0 class-ID: 0403 Device-3: HD WEBCAM NexiGo N660 FHD 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: Intel Ethernet I219-V vendor: Gigabyte driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200 IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> Drives: Local Storage: total: 7.75 TiB used: 1.96 GiB (0.0%) SMART Message: Unable to run smartctl. Root privileges required. ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO 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: 1B2QEXE7 temp: 32.9 C scheme: GPT ID-2: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37120G size: 111.79 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 61K1 scheme: MBR ID-3: /dev/sdb maj-min: 8:16 vendor: Toshiba model: DT01ACA050 size: 465.76 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: A750 scheme: GPT ID-4: /dev/sdc maj-min: 8:32 model: SATA SSD size: 111.79 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 61.3 scheme: GPT ID-5: /dev/sdd maj-min: 8:48 vendor: Seagate model: ST3000DM001-1ER166 size: 2.73 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: CC25 scheme: GPT ID-6: /dev/sde maj-min: 8:64 vendor: Western Digital model: WD5000AADS-00S9B0 size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: N/A serial: <filter> rev: 0A01 scheme: GPT ID-7: /dev/sdf maj-min: 8:80 type: USB model: Mass Storage Device size: 29.49 GiB block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1.00 scheme: MBR SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure? ID-8: /dev/sdl maj-min: 8:176 type: USB vendor: Seagate model: Expansion Desk size: 3.64 TiB block-size: physical: 4096 B logical: 4096 B type: N/A serial: <filter> rev: 0739 scheme: MBR Partition: Message: No partition data found. Swap: Alert: No swap data was found. Sensors: System Temperatures: cpu: 38.0 C mobo: N/A gpu: radeon temp: 40.0 C Fan Speeds (RPM): N/A Repos: Packages: pm: dpkg pkgs: 2032 libs: 1032 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm pkgs: 0 pm: flatpak pkgs: 0 No active apt repos in: /etc/apt/sources.list No active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 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/mx.list 1: deb http://mxrepo.com/mx/repo/ bookworm main non-free Info: Processes: 223 Uptime: 6m wakeups: 3 Memory: 31.3 GiB used: 2.06 GiB (6.6%) 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
Result: Boot starts, GRUB loads, able to traverse menu items. But...
====> Boot Hangs at "udev" and never completes
Here's the LUM log:So, near the top of the log:Code: Select all
===================================================================== /usr/local/bin/live-usb-maker gui -N --label=MX23_XFCE_BETA1 -C off --from=/media/opera-dude/Seagate Expansion Drive/Documents/Computer/OS/Linux Distros/MX Linux/MX-23_Beta1/XFCE/x64/MX-23_beta1_x64.iso -t /dev/sdk program: live-usb-maker started: Mon 29 May 2023 11:45:05 AM IDT version: 2.41.19-2302 (Sat, 25 Feb 2023 12:45:10 -0500) kernel: 5.10.0-23-amd64 OS: MX 21.3 (Wildflower) found lib: /usr/local/lib/cli-shell-utils/cli-shell-utils.bash lib version: 2.41.05-2302 (Sat, 25 Feb 2023 12:45:10 -0500) --------------------------------------------------------------------- Found man page: live-usb-maker.1 Will use target device /dev/sdk (29.5G Generic STORAGE_DEVICE) Will use source file /media/opera-dude/Seagate Expansion Drive/Documents/Computer/OS/Linux Distros/MX Linux/MX-23_Beta1/XFCE/x64/MX-23_beta1_x64.iso Distro: MX-23_beta1_x64 Libretto May 28, 2023 Found grub config 2.0 Estimated extfs overhead for 30149M is 44M Total Used Extra entire drive 29.5 GiB 29.5 GiB 1 MiB main partition 29.4 GiB 2.00 GiB 27.4 GiB uefi partition 50 MiB 32 MiB 18 MiB Ready to make live-usb on device sdk ... by copying file /media/opera-dude/Seagate Expansion Drive/Documents/Computer/OS/Linux Distros/MX Linux/MX-23_Beta1/XFCE/x64/MX-23_beta1_x64.iso >> partition-clear Total bytes: 31666995200 Total blocks: 61849600 > dd status=none if=/dev/zero of=/dev/sdk bs=512 count=34 > dd status=none if=/dev/zero of=/dev/sdk bs=512 count=34 seek=64 > dd status=none conv=notrunc if=/dev/zero of=/dev/sdk bs=512 count=34 seek=61849566 > partprobe /dev/sdk >> partition-make Using msdos partitioning > parted --script --align optimal /dev/sdk unit MiB mklabel msdos > dd status=none if=/dev/zero of=/dev/sdk seek=1024 bs=1K count=128 > parted --script --align optimal /dev/sdk unit MiB mkpart primary 1 30149 > parted --script --align optimal /dev/sdk unit MiB set 1 boot on > dd status=none if=/dev/zero of=/dev/sdk seek=30872576 bs=1K count=128 > parted --script --align optimal /dev/sdk unit MiB mkpart primary 30149 30198 > parted --script --align optimal /dev/sdk unit MiB set 2 esp on > partprobe /dev/sdk > wait_for_file /dev/sdk1 >> makefs-bios > mkfs.ext4 -O ^64bit -m0 -i16384 -J size=32 /dev/sdk1 mke2fs 1.46.2 (28-Feb-2021) 64-bit filesystem support is not enabled. The larger fields afforded by this feature enable full-strength checksumming. Pass -O 64bit to rectify. Creating filesystem with 7717888 4k blocks and 1929536 inodes Filesystem UUID: bc2eda53-a117-4b21-8119-e13975c9d51d Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000 Allocating group tables: 0/236 done Writing inode tables: 0/236 done Creating journal (8192 blocks): done Writing superblocks and filesystem accounting information: 0/236 done > tune2fs -L MX23_XFCE_BETA1 /dev/sdk1 tune2fs 1.46.2 (28-Feb-2021) > wait_for_file /dev/sdk2 >> makefs-uefi > mkfs.vfat -F 32 -n MX-UEFI /dev/sdk2 mkfs.fat 4.2 (2021-01-31) > partprobe /dev/sdk > wait_for_file /dev/sdk1 > mkdir -p /run/live-usb-maker/main > mount -t ext4 /dev/sdk1 /run/live-usb-maker/main > wait_for_file /dev/sdk2 > mkdir -p /run/live-usb-maker/uefi > mount -t vfat /dev/sdk2 /run/live-usb-maker/uefi Filesystem Type Size Used Avail Use% Mounted on /dev/sdk1 ext4 29G 24K 29G 1% /run/live-usb-maker/main /dev/sdk2 vfat 49M 512 49M 1% /run/live-usb-maker/uefi >> copy-uefi copy from iso to uefi partition files [Ee][Ff][Ii] version > cp --no-dereference --preserve=mode,links --recursive /run/live-usb-maker/iso/EFI /run/live-usb-maker/uefi/. > cp --no-dereference --preserve=mode,links --recursive /run/live-usb-maker/iso/version /run/live-usb-maker/uefi/. Fix Dell uefi memtest bug > cp /run/live-usb-maker/uefi/EFI/BOOT/grubx64.efi /run/live-usb-maker/uefi/EFI/BOOT/fallback.efi >> copy-main > rm -rf /run/live-usb-maker/main/boot.orig copy from iso to main partition vm.dirty_bytes = 20000000 copy /antiX/vmlinuz > cpio -pdm --quiet /run/live-usb-maker/main/ > e4defrag -v ./antiX/vmlinuz e4defrag 1.46.2 (28-Feb-2021) ext4 defragmentation for ./antiX/vmlinuz [1/1][1/1]./antiX/vmlinuz: 100% extents: 1 -> 1 [ OK ] Success: [1/1] copy /antiX/initrd.gz > cpio -pdm --quiet /run/live-usb-maker/main/ > e4defrag -v ./antiX/initrd.gz e4defrag 1.46.2 (28-Feb-2021) ext4 defragmentation for ./antiX/initrd.gz [1/1][1/1]./antiX/initrd.gz: 100% extents: 1 -> 1 [ OK ] Success: [1/1] copy remaining files ... > cpio -pdm --quiet /run/live-usb-maker/main/ copy pids: 40267 40270 vm.dirty_bytes = 20000000 vm.dirty_ratio = 0 > write_file /run/live-usb-maker/main/made-by-live-usb-maker created: Mon 29 May 2023 11:47:03 AM IDT program: live-usb-maker version: 2.41.19-2302 (Sat, 25 Feb 2023 12:45:10 -0500) > dd status=none if=/dev/urandom of=/run/live-usb-maker/main/antiX/random-seed bs=512 count=1 > chmod 600 /run/live-usb-maker/main/antiX/random-seed > rm -rf /run/live-usb-maker/main/.disk >> check-usb-md5 check md5 for initrd.gz > md5sum -c initrd.gz.md5 initrd.gz: OK check md5 for linuxfs > md5sum -c linuxfs.md5 linuxfs: OK check md5 for vmlinuz > md5sum -c vmlinuz.md5 vmlinuz: OK >> uuids Using antiX/MX grub config 2.0 > mkdir -p /run/live-usb-maker/uefi/boot/grub > cp /run/live-usb-maker/main/boot/grub/config/efi-grub.cfg /run/live-usb-maker/uefi/boot/grub/grub.cfg > touch /run/live-usb-maker/main/boot/grub/config/did-efi-grub > sed -i /^\s*#/! s/%UUID%/bc2eda53-a117-4b21-8119-e13975c9d51d/ /run/live-usb-maker/uefi/boot/grub/grub.cfg > rm -f /run/live-usb-maker/main/boot/grub/config/*.id > touch /run/live-usb-maker/main/boot/grub/config/9ab18e6ef8b39b65d4da28d5a66c2476.id > sed -i /^\s*#/! s|%ID_FILE%|/boot/grub/config/9ab18e6ef8b39b65d4da28d5a66c2476.id| /run/live-usb-maker/uefi/boot/grub/grub.cfg >> install extlinux version 6.04 > dd status=none bs=440 conv=notrunc count=1 if=/usr/lib/syslinux/mbr/mbr.bin of=/dev/sdk > rm -f /run/live-usb-maker/main/boot/syslinux/chain.c32 > rm -f /run/live-usb-maker/main/boot/syslinux/gfxboot.c32 > rm -f /run/live-usb-maker/main/boot/syslinux/ldlinux.c32 > rm -f /run/live-usb-maker/main/boot/syslinux/libcom32.c32 > rm -f /run/live-usb-maker/main/boot/syslinux/libmenu.c32 > rm -f /run/live-usb-maker/main/boot/syslinux/libutil.c32 > rm -f /run/live-usb-maker/main/boot/syslinux/menu.c32 > rm -f /run/live-usb-maker/main/boot/syslinux/syslinux.bin > rm -f /run/live-usb-maker/main/boot/syslinux/version > cp /usr/lib/syslinux/modules/bios/chain.c32 /run/live-usb-maker/main/boot/syslinux/ > cp /usr/lib/syslinux/modules/bios/gfxboot.c32 /run/live-usb-maker/main/boot/syslinux/ > cp /usr/lib/syslinux/modules/bios/vesamenu.c32 /run/live-usb-maker/main/boot/syslinux/ > cp /usr/lib/syslinux/modules/bios/ldlinux.c32 /run/live-usb-maker/main/boot/syslinux/ > cp /usr/lib/syslinux/modules/bios/libcom32.c32 /run/live-usb-maker/main/boot/syslinux/ > cp /usr/lib/syslinux/modules/bios/libmenu.c32 /run/live-usb-maker/main/boot/syslinux/ > cp /usr/lib/syslinux/modules/bios/libutil.c32 /run/live-usb-maker/main/boot/syslinux/ > cp /usr/lib/syslinux/modules/bios/linux.c32 /run/live-usb-maker/main/boot/syslinux/ > cp /usr/lib/syslinux/modules/bios/menu.c32 /run/live-usb-maker/main/boot/syslinux/ > write_file /run/live-usb-maker/main/boot/syslinux/version 6.04 > extlinux -i /run/live-usb-maker/main/boot/syslinux /run/live-usb-maker/main/boot/syslinux is device /dev/sdk1 Filesystem Type Size Used Avail Use% Mounted on /dev/sdk1 ext4 29G 2.0G 27G 7% /run/live-usb-maker/main /dev/sdk2 vfat 49M 13M 36M 26% /run/live-usb-maker/uefi >> done live-usb-maker took 2 minutes.Live USB made with MX-LUM on this (UEFI) machine; checksums all OK; using it now on this machine. However, when creating using LUM, I did notice that there are only 2 partitions, not the usual 3:Code: Select all
>> makefs-bios > mkfs.ext4 -O ^64bit -m0 -i16384 -J size=32 /dev/sdk1 mke2fs 1.46.2 (28-Feb-2021)
When using MX-LUM, I usually see something like this:However, from the LUM log for Beta-1, I get this:Code: Select all
Total Used Extra entire drive 29.5 GiB 29.5 GiB 1 MiB main partition 29.3 GiB 19.2 GiB 10.1 GiB bios partition 150 MiB 46 MiB 104 MiB uefi partition 50 MiB 30 MiB 20 MiBIs the BIOS partition missing? Is a missing BIOS partition causing GRUB to hang on the Asus P5KPL? Do I need to use MX-LUM from the BIOS machine (Asus P5KPL)?Code: Select all
entire drive 29.5 GiB 29.5 GiB 1 MiB main partition 29.4 GiB 2.00 GiB 27.4 GiB uefi partition 50 MiB 32 MiB 18 MiB
MY BAD!!!
Bad USB Port on Asus P5KPL!
Switched to a rear port. All is Good!
New Issue:
MX-Tools -> MX System Sounds:
On Right-Hand Side: "Session Sounds":
Only a CheckBox for "Login".
No Session Sounds for "Logout" ???