Page 1 of 1
Installation fails on Phase 2
Posted: Fri Nov 22, 2024 7:01 am
by Tuhoiisa
Im trying to install mx 23.4 ahs 64bit on my 256gb usb 3.0 pendrive however when i select my disk on installer and confirm it fails.
screenshot from installation log;
https://imgur.com/cyZ3UlL.png
system info;
Code: Select all
System:
Kernel: 6.10.10-1-liquorix-amd64 [6.10-12~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
intel_pstate=disable BOOT_IMAGE=/antiX/vmlinuz quiet splasht nosplash vcard=on
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.4_ahs_x64 Libretto September 15 2024 base: Debian GNU/Linux
12 (bookworm)
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: PRIME H610M-R D4 v: Rev 1.xx serial: <superuser required>
UEFI: American Megatrends v: 3212 date: 05/24/2024
CPU:
Info: model: 13th Gen Intel Core i3-13100F bits: 64 type: MT MCP arch: Raptor Lake gen: core 13
level: v3 note: check built: 2022+ process: Intel 7 (10nm) family: 6 model-id: 0xBF (191)
stepping: 5 microcode: 0x34
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 320 KiB
desc: d-4x48 KiB; i-4x32 KiB L2: 5 MiB desc: 4x1.2 MiB L3: 12 MiB desc: 1x12 MiB
Speed (MHz): avg: 889 high: 1152 min/max: 800/3401 boost: enabled scaling: driver: acpi-cpufreq
governor: ondemand cores: 1: 800 2: 800 3: 989 4: 800 5: 801 6: 975 7: 1152 8: 800
bogomips: 54681
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: gather_data_sampling status: Not affected
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: reg_file_data_sampling status: Not affected
Type: retbleed status: Not affected
Type: spec_rstack_overflow status: Not affected
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: Enhanced / Automatic IBRS; IBPB: conditional; RSB filling;
PBRSB-eIBRS: SW sequence; BHI: BHI_DIS_S
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Navi 23 [Radeon RX 6650 XT / 6700S 6800S] vendor: ASUSTeK driver: amdgpu v: kernel
arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s
lanes: 16 ports: active: HDMI-A-1 empty: DP-1, DP-2, DP-3, Writeback-1 bus-ID: 03:00.0
chip-ID: 1002:73ef class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: amdgpu
unloaded: fbdev,modesetting,radeon,vesa dri: radeonsi gpu: amdgpu 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-A-0 model: Asus VP228 serial: <filter> built: 2018
res: 1920x1080 hz: 60 dpi: 102 gamma: 1.2 size: 476x268mm (18.74x10.55") diag: 546mm (21.5")
ratio: 16:9 modes: max: 1920x1080 min: 720x400
API: OpenGL v: 4.6 Mesa 23.1.2-1~mx23ahs renderer: AMD Radeon RX 6650 XT (navi23 LLVM 15.0.6
DRM 3.57 6.10.10-1-liquorix-amd64) direct-render: Yes
Audio:
Device-1: Intel Alder Lake-S HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
bus-ID: 1-3:2 alternate: snd_soc_avs,snd_sof_pci_intel_tgl chip-ID: 1b3f:2008 bus-ID: 00:1f.3
class-ID: 0300 chip-ID: 8086:7ad0 class-ID: 0403
Device-2: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie: gen: 4
speed: 16 GT/s lanes: 16 bus-ID: 03:00.1 chip-ID: 1002:ab28 class-ID: 0403
Device-3: Generalplus USB Audio Device type: USB driver: hid-generic,snd-usb-audio,usbhid
API: ALSA v: k6.10.10-1-liquorix-amd64 status: kernel-api tools: alsamixer,amixer
Server-1: PipeWire v: 1.0.0 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: 3000 bus-ID: 05:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
RAID:
Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd v: 0.6 port: N/A
bus-ID: 00:0e.0 chip-ID: 8086:467f rev: class-ID: 0104
Drives:
Local Storage: total: 839.98 GiB used: 0 KiB (0.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: KIOXIA model: EXCERIA SSD size: 465.76 GiB
block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: ECFA15.3 temp: 40.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Apacer model: APS-SL3N-120 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-3: /dev/sdb maj-min: 8:16 type: USB vendor: Generic model: Flash Disk size: 29.3 GiB
block-size: physical: 512 B logical: 512 B type: SSD serial: <filter> rev: 8.07 scheme: GPT
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
ID-4: /dev/sdc maj-min: 8:32 type: USB vendor: SanDisk model: SanDisk 3.2 Gen1 size: 233.13 GiB
block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: DL17 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
Message: No partition data found.
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 15.44 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 31.0 C mobo: N/A gpu: amdgpu temp: 34.0 C mem: 30.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 0
Repos:
Packages: pm: dpkg pkgs: 2119 libs: 1052 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 non-free-firmware
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 non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb https://mxrepo.com/mx/repo/ bookworm main non-free
2: deb https://mxrepo.com/mx/repo/ bookworm ahs
Info:
Processes: 374 Uptime: 14m wakeups: 10 Memory: 15.44 GiB used: 3.22 GiB (20.8%) 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: UEFI
Re: Installation fails on Phase 2
Posted: Fri Nov 22, 2024 7:13 am
by j2mcgreg
What utility are you using to write the ISO to the pen drive? Are you specifying that this utility use GPT partitioning?
Re: Installation fails on Phase 2
Posted: Fri Nov 22, 2024 7:18 am
by Tuhoiisa
I used ventoy on my 32gb pendrive that holds the mx linux iso and yea i think it uses gpt not mbr
Re: Installation fails on Phase 2
Posted: Fri Nov 22, 2024 7:26 am
by j2mcgreg
Tuhoiisa wrote: Fri Nov 22, 2024 7:18 am
I used ventoy on my 32gb pendrive that holds the mx linux iso and yea i think it uses gpt not mbr
With Ventoy, you must use the very latest version. We found during the Release Candidate phase of MX 23's development that the earlier versions of Ventoy were incompatible.
Re: Installation fails on Phase 2
Posted: Fri Nov 22, 2024 7:29 am
by Tuhoiisa
yes the ventoy version is the latest
Re: Installation fails on Phase 2
Posted: Fri Nov 22, 2024 7:40 am
by pixie
I ran into this with ventoy. Should you have another pendrive use Balena
Re: Installation fails on Phase 2
Posted: Fri Nov 22, 2024 7:41 am
by Tuhoiisa
pixie wrote: Fri Nov 22, 2024 7:40 am
I ran into this with ventoy. Should you have another pendrive use Balena
Sure i can try that
Re: Installation fails on Phase 2
Posted: Fri Nov 22, 2024 7:53 am
by j2mcgreg
pixie wrote: Fri Nov 22, 2024 7:40 am
I ran into this with ventoy. Should you have another pendrive use Balena
Or if you have access to a Windows machine, use Rufus.
Re: Installation fails on Phase 2
Posted: Fri Nov 22, 2024 7:57 am
by Tuhoiisa
same issue with balena will try rufus next
Re: Installation fails on Phase 2
Posted: Fri Nov 22, 2024 8:00 am
by Tuhoiisa
Should i use ISO Image mode or dd on rufus?
Re: Installation fails on Phase 2
Posted: Fri Nov 22, 2024 8:00 am
by dolphin_oracle
supplying the /var/log/minstall.log file from an attempt is probably more valuable than trying to a different liveusb for the source.
Re: Installation fails on Phase 2
Posted: Fri Nov 22, 2024 8:06 am
by Tuhoiisa
dolphin_oracle wrote: Fri Nov 22, 2024 8:00 am
supplying the /var/log/minstall.log file from an attempt is probably more valuable than trying to a different liveusb for the source.
Sure here it is
Re: Installation fails on Phase 2
Posted: Fri Nov 22, 2024 8:16 am
by dolphin_oracle
what sort of device is sdb?
what is output of
Re: Installation fails on Phase 2
Posted: Fri Nov 22, 2024 8:18 am
by Tuhoiisa
Re: Installation fails on Phase 2
Posted: Fri Nov 22, 2024 8:20 am
by Tuhoiisa
Code: Select all
00:00.0 0600: 8086:4630 (rev 05)
00:01.0 0604: 8086:460d (rev 05)
00:04.0 1180: 8086:461d (rev 05)
00:0a.0 1180: 8086:467d (rev 01)
00:0e.0 0104: 8086:467f
00:14.0 0c03: 8086:7ae0 (rev 11)
00:14.2 0500: 8086:7aa7 (rev 11)
00:15.0 0c80: 8086:7acc (rev 11)
00:16.0 0780: 8086:7ae8 (rev 11)
00:17.0 0106: 8086:7ae2 (rev 11)
00:1c.0 0604: 8086:7ab8 (rev 11)
00:1c.3 0604: 8086:7abb (rev 11)
00:1c.4 0604: 8086:7abc (rev 11)
00:1f.0 0601: 8086:7a87 (rev 11)
00:1f.3 0403: 8086:7ad0 (rev 11)
00:1f.4 0c05: 8086:7aa3 (rev 11)
00:1f.5 0c80: 8086:7aa4 (rev 11)
01:00.0 0604: 1002:1478 (rev c1)
02:00.0 0604: 1002:1479
03:00.0 0300: 1002:73ef (rev c1)
03:00.1 0403: 1002:ab28
05:00.0 0200: 10ec:8168 (rev 15)
06:00.0 0108: 1e0f:0009 (rev 01)
Re: Installation fails on Phase 2
Posted: Fri Nov 22, 2024 8:26 am
by dolphin_oracle
Re: Installation fails on Phase 2
Posted: Fri Nov 22, 2024 8:28 am
by Tuhoiisa
Code: Select all
P: /devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/host7/target7:0:0/7:0:0:0/block/sdb
M: sdb
U: block
T: disk
D: b 8:16
N: sdb
L: 0
S: disk/by-diskseq/3
S: disk/by-id/usb-SanDisk_SanDisk_3.2_Gen1_A2003CC1F1095D98-0:0
S: disk/by-path/pci-0000:00:14.0-usb-0:1:1.0-scsi-0:0:0:0
Q: 3
E: DEVPATH=/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/host7/target7:0:0/7:0:0:0/block/sdb
E: DEVNAME=/dev/sdb
E: DEVTYPE=disk
E: DISKSEQ=3
E: MAJOR=8
E: MINOR=16
E: SUBSYSTEM=block
E: USEC_INITIALIZED=738597496
E: ID_BUS=usb
E: ID_MODEL=SanDisk_3.2_Gen1
E: ID_MODEL_ENC=SanDisk\x203.2\x20Gen1
E: ID_MODEL_ID=55b1
E: ID_SERIAL=SanDisk_SanDisk_3.2_Gen1_A2003CC1F1095D98-0:0
E: ID_SERIAL_SHORT=A2003CC1F1095D98
E: ID_VENDOR=SanDisk
E: ID_VENDOR_ENC=SanDisk\x20
E: ID_VENDOR_ID=0781
E: ID_REVISION=DL17
E: ID_TYPE=disk
E: ID_INSTANCE=0:0
E: ID_USB_MODEL=SanDisk_3.2_Gen1
E: ID_USB_MODEL_ENC=SanDisk\x203.2\x20Gen1
E: ID_USB_MODEL_ID=55b1
E: ID_USB_SERIAL=SanDisk_SanDisk_3.2_Gen1_A2003CC1F1095D98-0:0
E: ID_USB_SERIAL_SHORT=A2003CC1F1095D98
E: ID_USB_VENDOR=SanDisk
E: ID_USB_VENDOR_ENC=SanDisk\x20
E: ID_USB_VENDOR_ID=0781
E: ID_USB_REVISION=DL17
E: ID_USB_TYPE=disk
E: ID_USB_INSTANCE=0:0
E: ID_USB_INTERFACES=:080650:
E: ID_USB_INTERFACE_NUM=00
E: ID_USB_DRIVER=usb-storage
E: ID_PATH=pci-0000:00:14.0-usb-0:1:1.0-scsi-0:0:0:0
E: ID_PATH_TAG=pci-0000_00_14_0-usb-0_1_1_0-scsi-0_0_0_0
E: ID_PART_TABLE_UUID=99731c0e
E: ID_PART_TABLE_TYPE=dos
E: DEVLINKS=/dev/disk/by-diskseq/3 /dev/disk/by-id/usb-SanDisk_SanDisk_3.2_Gen1_A2003CC1F1095D98-0:0 /dev/disk/by-path/pci-0000:00:14.0-usb-0:1:1.0-scsi-0:0:0:0
E: TAGS=:systemd:
E: CURRENT_TAGS=:systemd:
~
~
lines 1-53/53 (END)
Re: Installation fails on Phase 2
Posted: Fri Nov 22, 2024 8:37 am
by dolphin_oracle
Ok what's happening is that the blkdiscard command we use to clear partition tables is failing. why I do not know.
The auto-install isnt' going to work without some modification to the installer. Neither will manual partitioning inside the installer.
however, I think it will work if you do the partitioning manually before launching the installer, then use the "custom" option to choose partitions.
looking at the minstall.log file, you'll probably want the following:
1. 512 MB vfat partition, marked ESP,boot, for the UEFI boot stuff.
2. remainder partition you want, format ext4.
Re: Installation fails on Phase 2
Posted: Fri Nov 22, 2024 8:40 am
by Tuhoiisa
like this?
Re: Installation fails on Phase 2
Posted: Fri Nov 22, 2024 8:49 am
by dolphin_oracle
yes, as long as you used gparted to make the partitions. making them in the installer won't work, for the same reason the auto-install fails.
Re: Installation fails on Phase 2
Posted: Fri Nov 22, 2024 8:50 am
by j2mcgreg
Sandisk flash drives are notorious for a write protection problem. See here:
https://www.google.com/search?q=sandisk ... BiGAxiABBi
You probably should try a drive from another manufacturer.
Re: Installation fails on Phase 2
Posted: Fri Nov 22, 2024 8:59 am
by Tuhoiisa
trying gparted now if it fails too i will try another disk i guess
Re: Installation fails on Phase 2
Posted: Fri Nov 22, 2024 11:02 am
by fehlix
dolphin_oracle wrote: Fri Nov 22, 2024 8:37 am
Ok what's happening is that the blkdiscard command we use to clear partition tables is failing. why I do not know.
The wrongly reported TRIM supported of the attached device, is misleading and makes blkdiscard fail.
The currently detection of running in VirtualBox for known wrongly reported trim-support is not sufficient,
but with adding a catch all.
So instead of a big Failure popup:
Code: Select all
2024-11-22 16:38:40.977 DBG default: SErr #32: "blkdiscard: Operation forced, data will be lost!\nblkdiscard: /dev/sdb: BLKDISCARD ioctl failed: Operation not supported\n"
2024-11-22 16:38:40.977 DBG default: Exit #32: 1
2024-11-22 16:38:40.977 DBG default: -- FAILED Phase 2 - Failed to prepare required partitions. --
it uses catch all which looks within the log like this:
Code: Select all
2024-11-22 16:42:48.948 DBG default: Exec #30: blkdiscard -fv -l 4194304 /dev/sdb
2024-11-22 16:42:48.951 DBG default: SErr #30: "blkdiscard: Operation forced, data will be lost!\nblkdiscard: /dev/sdb: BLKDISCARD ioctl failed: Operation not supported\n"
2024-11-22 16:42:48.951 DBG default: Exit #30: 1
2024-11-22 16:42:48.951 DBG default: Exec #31: blkdiscard -fvz -l 4194304 /dev/sdb
2024-11-22 16:42:49.139 DBG default: SOut #31: "/dev/sdb: Zero-filled 4194304 bytes from the offset 0\n"
2024-11-22 16:42:49.140 DBG default: SErr #31: "blkdiscard: Operation forced, data will be lost!\n"
2024-11-22 16:42:49.140 DBG default: Exit #31: 0
when it fails due to wrongly reported trim-support, it retreis w/o trim but dump-zeros.
I do rather ask first, in case you have already fixed it in another way, otherwise
let me send a PR to the installer (gazelle-installer) on github.
The fix was tested where the original install fail on an attached USB-device (64Gb Sandisk stick),
and fix worked also to install on entire drive, probably also with manually partitioning within the Installer.
Re: Installation fails on Phase 2
Posted: Fri Nov 22, 2024 11:17 am
by dolphin_oracle
@fehlix go ahead. I haven't fixed it yet. there are a number of blkdiscard calls.
although given that gparted also failed, I'm not sure it will help the OP, but I think it is the right thing to do.
Re: Installation fails on Phase 2
Posted: Fri Nov 22, 2024 11:25 am
by fehlix
dolphin_oracle wrote: Fri Nov 22, 2024 11:17 am
@fehlix go ahead. I haven't fixed it yet. there are a number of blkdiscard calls.
I think I catched all. So yes it is a reproducable "bug" which get fixed with the catch all.
dolphin_oracle wrote: Fri Nov 22, 2024 11:17 am
although given that gparted also failed, I'm not sure it will help the OP, but I think it is the right thing to do.
OP hasn't reported gparted fails, at least I can't see.
+++EDIT+++
Send a PR.
Done!
Re: Installation fails on Phase 2
Posted: Fri Nov 22, 2024 12:08 pm
by dolphin_oracle
@fehlix will check out PR tonight.
I read this post
viewtopic.php?p=799110#p799110 as saying gparted failed. Maybe teh OP meant the installer after partitioning but the picture included is gparted.
Re: Installation fails on Phase 2
Posted: Fri Nov 22, 2024 12:20 pm
by fehlix
dolphin_oracle wrote: Fri Nov 22, 2024 12:08 pm
@fehlix will check out PR tonight.
I read this post
viewtopic.php?p=799110#p799110 as saying gparted failed. Maybe teh OP meant the installer after partitioning but the picture included is gparted.
That's a "if it fails too" not a "it failed too"
trying gparted now if it fails too i will try another disk i guess
Re: Installation fails on Phase 2
Posted: Fri Nov 22, 2024 12:48 pm
by dolphin_oracle
fehlix wrote: Fri Nov 22, 2024 12:20 pm
dolphin_oracle wrote: Fri Nov 22, 2024 12:08 pm
@fehlix will check out PR tonight.
I read this post
viewtopic.php?p=799110#p799110 as saying gparted failed. Maybe teh OP meant the installer after partitioning but the picture included is gparted.
That's a "if it fails too" not a "it failed too"
trying gparted now if it fails too i will try another disk i guess
lol.
Re: Installation fails on Phase 2
Posted: Fri Nov 22, 2024 2:29 pm
by fehlix
Booting now from the MX-Installer-to-USB stick:
Code: Select all
Snapshot created on: 20241121_1904
System:
Kernel: 6.11.9-1-liquorix-amd64 [6.11-14~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
intel_pstate=disable BOOT_IMAGE=/boot/vmlinuz-6.11.9-1-liquorix-amd64 root=UUID=<filter> ro
quiet menu_timeout=6 module_blacklist=floppy overlay.index=0 splash init=/lib/systemd/systemd
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.4_ahs_x64 Libretto September 15 2024 base: Debian GNU/Linux
12 (bookworm)
Machine:
Type: Desktop Mobo: AZW model: SER v: V1 serial: <superuser required> UEFI: American Megatrends
LLC. v: SER6proMax_P5C8V20 date: 08/15/2023
CPU:
Info: model: AMD Ryzen 7 7735HS with Radeon Graphics bits: 64 type: MT MCP arch: Zen 3+ gen: 4
level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25) model-id: 0x44 (68)
stepping: 1 microcode: 0xA404102
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache: L1: 512 KiB
desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB L3: 16 MiB desc: 1x16 MiB
Speed (MHz): avg: 1293 high: 3651 min/max: 400/4829 boost: enabled scaling:
driver: amd-pstate-epp governor: performance cores: 1: 400 2: 400 3: 400 4: 400 5: 3169 6: 400
7: 400 8: 400 9: 3651 10: 400 11: 3150 12: 400 13: 3159 14: 400 15: 3167 16: 400
bogomips: 102210
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: gather_data_sampling status: Not affected
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: reg_file_data_sampling status: Not affected
Type: retbleed status: Not affected
Type: spec_rstack_overflow status: Vulnerable: Safe RET, no microcode
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; IBRS_FW; STIBP: always-on; RSB
filling; PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Rembrandt [Radeon 680M] driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x
process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports:
active: HDMI-A-1 empty: DP-1, DP-2, DP-3, DP-4, DP-5, DP-6, DP-7, Writeback-1 bus-ID: e6:00.0
chip-ID: 1002:1681 class-ID: 0300 temp: 34.0 C
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: amdgpu
unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu 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-A-0 model: MD20581 built: 2016 res: 1920x1080 hz: 60 dpi: 82
gamma: 1.2 size: 597x336mm (23.5x13.23") diag: 676mm (26.6") ratio: 16:9 modes: max: 1920x1080
min: 720x400
API: OpenGL v: 4.6 Mesa 24.2.2-1~mx23ahs renderer: AMD Radeon 680M (radeonsi rembrandt LLVM
15.0.6 DRM 3.59 6.11.9-1-liquorix-amd64) direct-render: Yes
Audio:
Device-1: AMD Rembrandt Radeon High Definition Audio driver: snd_hda_intel v: kernel pcie: gen: 4
speed: 16 GT/s lanes: 16 bus-ID: e6:00.1 chip-ID: 1002:1640 class-ID: 0403
Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor driver: snd_pci_acp6x v: kernel
alternate: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x, snd_acp_pci, snd_rpl_pci_acp6x,
snd_pci_ps, snd_sof_amd_renoir, snd_sof_amd_rembrandt, snd_sof_amd_vangogh, snd_sof_amd_acp63
pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: e6:00.5 chip-ID: 1022:15e2 class-ID: 0480
Device-3: AMD Family 17h/19h HD Audio driver: snd_hda_intel v: kernel pcie: gen: 4
speed: 16 GT/s lanes: 16 bus-ID: e6:00.6 chip-ID: 1022:15e3 class-ID: 0403
API: ALSA v: k6.11.9-1-liquorix-amd64 status: kernel-api tools: alsamixer,amixer
Server-1: PipeWire v: 1.0.0 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 I225-V driver: igc v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1
port: N/A bus-ID: 02:00.0 chip-ID: 8086:15f3 class-ID: 0200
IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1
bus-ID: 03:00.0 chip-ID: 8086:2723 class-ID: 0280
IF: wlan0 state: down mac: <filter>
Bluetooth:
Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 3-3:2 chip-ID: 8087:0029
class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2
sub-v: 2184 hci-v: 5.2 rev: 2184
Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: peripheral accept
service-classes: rendering, capturing, object transfer, audio, telephony
Drives:
Local Storage: total: 2.78 TiB used: 17.89 GiB (0.6%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:12 vendor: Crucial model: CT1000P3PSSD8 size: 931.51 GiB
block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
rev: P9CR40A temp: 25.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 2TB size: 1.82 TiB
block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
rev: 5B2QGXA7 temp: 24.9 C scheme: GPT
ID-3: /dev/sda maj-min: 8:0 type: USB vendor: SanDisk model: USB 3.2Gen1 size: 57.3 GiB
block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1.00 scheme: GPT
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 57.05 GiB size: 55.86 GiB (97.90%) used: 17.89 GiB (32.0%) fs: ext4
dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
dev: /dev/sda1 maj-min: 8:1
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 8 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
System Temperatures: cpu: 40.4 C mobo: 29.5 C gpu: amdgpu temp: 34.0 C
Fan Speeds (RPM): N/A
Repos:
Packages: pm: dpkg pkgs: 2350 libs: 1201 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
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 non-free-firmware
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 non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bookworm main non-free
2: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bookworm ahs
Active apt repos in: /etc/apt/sources.list.d/nala-sources.list
1: deb http://debian.intergenia.de/debian/ bookworm main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/extrepo_librewolf.sources
1: deb [arch=amd64] https://repo.librewolf.net librewolf main
Active apt repos in: /etc/apt/sources.list.d/mx-repo-ahs.nl-hh-fau-bookworm.sources
1: deb https://mirror.plusserver.com/mxlinux/mxlinux/mx/repo/ bookworm main non-free ahs
2: deb https://ftp.fau.de/mxlinux-packages/mx/repo bookworm main non-free ahs
3: deb https://mxlinux.mirror.iphh.net/packages/mx/repo bookworm main non-free ahs
Info:
Processes: 397 Uptime: 2m wakeups: 1 Memory: 58.6 GiB used: 2.09 GiB (3.6%) Init: systemd v: 252
target: graphical (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: UEFI
TBH, I'd rather prefer creating an MX LiveUSB instead of directly installing onto a USB-stick,
but anyway seems to work now.
Re: Installation fails on Phase 2
Posted: Fri Nov 22, 2024 6:25 pm
by FullScale4Me
Sandisk, like the PC makers, has a bargain offering and a better one. In Sandisk's case, in general, you can use their 'Ultra' (vs. 'Cruiser') as being OK. USB drives should NEVER be price-shopped. I use reviews exclusively, regardless of whether another is $1-3 USD cheaper. There are some duds in their 'Ultra' offering. The aggrevation is NOT worth it to me!
My recent Sandisk USB purchase - $11.99 USD
https://www.newegg.com/sandisk-model-sdcz48-128g-u46-128gb/p/0BD-000B-002P0?Item=0BD-000B-002P0
Sandisk 256 Gb - $21.22 USD
https://www.newegg.com/sandisk-model-sdcz48-256g-u46-256gb/p/0BD-000B-004W6?Item=9SIA12KJSX7752&cm_sp=product-_-from-price-options
Re: Installation fails on Phase 2
Posted: Sun Nov 24, 2024 7:52 am
by Tuhoiisa
Sorry i forgot to inform lol creating partitions manually worked but mx linux was soo laggy so i deleted it (probably pendrive issue)
Re: Installation fails on Phase 2
Posted: Sun Nov 24, 2024 8:30 am
by Tuhoiisa
fehlix wrote: Fri Nov 22, 2024 2:29 pm
Booting now from the MX-Installer-to-USB stick:
Code: Select all
Snapshot created on: 20241121_1904
System:
Kernel: 6.11.9-1-liquorix-amd64 [6.11-14~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
intel_pstate=disable BOOT_IMAGE=/boot/vmlinuz-6.11.9-1-liquorix-amd64 root=UUID=<filter> ro
quiet menu_timeout=6 module_blacklist=floppy overlay.index=0 splash init=/lib/systemd/systemd
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.4_ahs_x64 Libretto September 15 2024 base: Debian GNU/Linux
12 (bookworm)
Machine:
Type: Desktop Mobo: AZW model: SER v: V1 serial: <superuser required> UEFI: American Megatrends
LLC. v: SER6proMax_P5C8V20 date: 08/15/2023
CPU:
Info: model: AMD Ryzen 7 7735HS with Radeon Graphics bits: 64 type: MT MCP arch: Zen 3+ gen: 4
level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25) model-id: 0x44 (68)
stepping: 1 microcode: 0xA404102
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache: L1: 512 KiB
desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB L3: 16 MiB desc: 1x16 MiB
Speed (MHz): avg: 1293 high: 3651 min/max: 400/4829 boost: enabled scaling:
driver: amd-pstate-epp governor: performance cores: 1: 400 2: 400 3: 400 4: 400 5: 3169 6: 400
7: 400 8: 400 9: 3651 10: 400 11: 3150 12: 400 13: 3159 14: 400 15: 3167 16: 400
bogomips: 102210
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: gather_data_sampling status: Not affected
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: reg_file_data_sampling status: Not affected
Type: retbleed status: Not affected
Type: spec_rstack_overflow status: Vulnerable: Safe RET, no microcode
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; IBRS_FW; STIBP: always-on; RSB
filling; PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Rembrandt [Radeon 680M] driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x
process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports:
active: HDMI-A-1 empty: DP-1, DP-2, DP-3, DP-4, DP-5, DP-6, DP-7, Writeback-1 bus-ID: e6:00.0
chip-ID: 1002:1681 class-ID: 0300 temp: 34.0 C
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: amdgpu
unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu 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-A-0 model: MD20581 built: 2016 res: 1920x1080 hz: 60 dpi: 82
gamma: 1.2 size: 597x336mm (23.5x13.23") diag: 676mm (26.6") ratio: 16:9 modes: max: 1920x1080
min: 720x400
API: OpenGL v: 4.6 Mesa 24.2.2-1~mx23ahs renderer: AMD Radeon 680M (radeonsi rembrandt LLVM
15.0.6 DRM 3.59 6.11.9-1-liquorix-amd64) direct-render: Yes
Audio:
Device-1: AMD Rembrandt Radeon High Definition Audio driver: snd_hda_intel v: kernel pcie: gen: 4
speed: 16 GT/s lanes: 16 bus-ID: e6:00.1 chip-ID: 1002:1640 class-ID: 0403
Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor driver: snd_pci_acp6x v: kernel
alternate: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x, snd_acp_pci, snd_rpl_pci_acp6x,
snd_pci_ps, snd_sof_amd_renoir, snd_sof_amd_rembrandt, snd_sof_amd_vangogh, snd_sof_amd_acp63
pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: e6:00.5 chip-ID: 1022:15e2 class-ID: 0480
Device-3: AMD Family 17h/19h HD Audio driver: snd_hda_intel v: kernel pcie: gen: 4
speed: 16 GT/s lanes: 16 bus-ID: e6:00.6 chip-ID: 1022:15e3 class-ID: 0403
API: ALSA v: k6.11.9-1-liquorix-amd64 status: kernel-api tools: alsamixer,amixer
Server-1: PipeWire v: 1.0.0 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 I225-V driver: igc v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1
port: N/A bus-ID: 02:00.0 chip-ID: 8086:15f3 class-ID: 0200
IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1
bus-ID: 03:00.0 chip-ID: 8086:2723 class-ID: 0280
IF: wlan0 state: down mac: <filter>
Bluetooth:
Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 3-3:2 chip-ID: 8087:0029
class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2
sub-v: 2184 hci-v: 5.2 rev: 2184
Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: peripheral accept
service-classes: rendering, capturing, object transfer, audio, telephony
Drives:
Local Storage: total: 2.78 TiB used: 17.89 GiB (0.6%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:12 vendor: Crucial model: CT1000P3PSSD8 size: 931.51 GiB
block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
rev: P9CR40A temp: 25.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 2TB size: 1.82 TiB
block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
rev: 5B2QGXA7 temp: 24.9 C scheme: GPT
ID-3: /dev/sda maj-min: 8:0 type: USB vendor: SanDisk model: USB 3.2Gen1 size: 57.3 GiB
block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1.00 scheme: GPT
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 57.05 GiB size: 55.86 GiB (97.90%) used: 17.89 GiB (32.0%) fs: ext4
dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
dev: /dev/sda1 maj-min: 8:1
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 8 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
System Temperatures: cpu: 40.4 C mobo: 29.5 C gpu: amdgpu temp: 34.0 C
Fan Speeds (RPM): N/A
Repos:
Packages: pm: dpkg pkgs: 2350 libs: 1201 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
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 non-free-firmware
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 non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bookworm main non-free
2: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bookworm ahs
Active apt repos in: /etc/apt/sources.list.d/nala-sources.list
1: deb http://debian.intergenia.de/debian/ bookworm main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/extrepo_librewolf.sources
1: deb [arch=amd64] https://repo.librewolf.net librewolf main
Active apt repos in: /etc/apt/sources.list.d/mx-repo-ahs.nl-hh-fau-bookworm.sources
1: deb https://mirror.plusserver.com/mxlinux/mxlinux/mx/repo/ bookworm main non-free ahs
2: deb https://ftp.fau.de/mxlinux-packages/mx/repo bookworm main non-free ahs
3: deb https://mxlinux.mirror.iphh.net/packages/mx/repo bookworm main non-free ahs
Info:
Processes: 397 Uptime: 2m wakeups: 1 Memory: 58.6 GiB used: 2.09 GiB (3.6%) Init: systemd v: 252
target: graphical (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: UEFI
TBH, I'd rather prefer creating an MX LiveUSB instead of directly installing onto a USB-stick,
but anyway seems to work now.
i looked about creating mx liveusb but that looked complicated so i directly installed it
Re: Installation fails on Phase 2
Posted: Sun Nov 24, 2024 8:38 am
by fehlix
Tuhoiisa wrote: Sun Nov 24, 2024 7:52 am
Sorry i forgot to inform lol creating partitions manually worked but mx linux was soo laggy so i deleted it (probably pendrive issue)
We have meanwhile a fixed version of the MX Installer within the repos.
Note: With this amount of ram:
Code: Select all
Info:
Processes: 374 Uptime: 14m wakeups: 10 Memory: 15.44 GiB used: 3.22 GiB (20.8%) 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: UEFI
Instead of directly installing onto USB-key, you may consider to create a MX LiveUSB, with help of MX LiveUSB Maker,
where you can choose dynamic root persistence, which makes
the system work from ram and any changes can be saved at once, reducing permanent read/write to the USB.
So, you have two advantages: Faster I/O and reduced write cycles onto the USB.
One disadvantage is that you would have to remaster regularly to squeeze back system changes into the read-only, squashed linuxfs file,
thereby releasing the accumulated changes in the rootfs persistence file.
Re: Installation fails on Phase 2
Posted: Sun Nov 24, 2024 8:40 am
by Tuhoiisa
fehlix wrote: Sun Nov 24, 2024 8:38 am
Tuhoiisa wrote: Sun Nov 24, 2024 7:52 am
Sorry i forgot to inform lol creating partitions manually worked but mx linux was soo laggy so i deleted it (probably pendrive issue)
We have meanwhile a fixed version of the MX Installer within the repos.
Note: With this amount of ram:
Code: Select all
Info:
Processes: 374 Uptime: 14m wakeups: 10 Memory: 15.44 GiB used: 3.22 GiB (20.8%) 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: UEFI
You may consider to create a MX LiveUSB, where you can choose dynamic root persistence, which makes
the system work from ram and any changes can be saved at once, reducing permanent read/write to the USB.
So, you have two advantages: Faster I/O and reduced write cycles onto the USB.
One disadvantage is that you would have to remaster regularly to squeeze back system changes into the read-only, squashed linuxfs file,
thereby releasing the accumulated changes in the rootfs persistence file.
like in this video?
https://www.youtube.com/watch?v=sGVgGMhP1d4
Re: Installation fails on Phase 2
Posted: Sun Nov 24, 2024 8:43 am
by fehlix
Tuhoiisa wrote: Sun Nov 24, 2024 8:40 am
fehlix wrote: Sun Nov 24, 2024 8:38 am
Tuhoiisa wrote: Sun Nov 24, 2024 7:52 am
Sorry i forgot to inform lol creating partitions manually worked but mx linux was soo laggy so i deleted it (probably pendrive issue)
We have meanwhile a fixed version of the MX Installer within the repos.
Note: With this amount of ram:
Code: Select all
Info:
Processes: 374 Uptime: 14m wakeups: 10 Memory: 15.44 GiB used: 3.22 GiB (20.8%) 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: UEFI
You may consider to create a MX LiveUSB, where you can choose dynamic root persistence, which makes
the system work from ram and any changes can be saved at once, reducing permanent read/write to the USB.
So, you have two advantages: Faster I/O and reduced write cycles onto the USB.
One disadvantage is that you would have to remaster regularly to squeeze back system changes into the read-only, squashed linuxfs file,
thereby releasing the accumulated changes in the rootfs persistence file.
like in this video?
https://www.youtube.com/watch?v=sGVgGMhP1d4
You would use MX Live USB Maker with full featured mode (the default) to create a MX LiveUSB.
Also I do always change under "Advanced.." to GPT and instead of MSDOS/MBR partition table.
Persistence option and other LiveUSB boot options can be set during Liveboot, and also "saved" be be pre-set next live boot.
Re: Installation fails on Phase 2
Posted: Sun Nov 24, 2024 8:49 am
by Tuhoiisa
doing it now
Re: Installation fails on Phase 2
Posted: Sun Nov 24, 2024 8:55 am
by fehlix
Tuhoiisa wrote: Sun Nov 24, 2024 8:49 am
doing it now
You can boot with toram live boot options (found with the live boot options sub menu.)
just for test, which make the whole system running from ram - even faster then installed onto an internal drive.
Re: Installation fails on Phase 2
Posted: Sun Nov 24, 2024 9:00 am
by Tuhoiisa
fehlix wrote: Sun Nov 24, 2024 8:55 am
Tuhoiisa wrote: Sun Nov 24, 2024 8:49 am
doing it now
You can boot with toram live boot options (found with the live boot options sub menu.)
just for test, which make the whole system running from ram - even faster then installed onto an internal drive.
so if i choose dynamic persistance my system will run on ram and save changes to disk when i shutdown it?
Re: Installation fails on Phase 2
Posted: Sun Nov 24, 2024 9:03 am
by Tuhoiisa
Also do u mean static? Because there is no dynamic option
Re: Installation fails on Phase 2
Posted: Sun Nov 24, 2024 10:07 am
by fehlix
Tuhoiisa wrote: Sun Nov 24, 2024 9:03 am
Also do u mean static? Because there is no dynamic option
root to RAM = dynamic, else static ( this the original terminologie, which we tried to avoid using)
