johs
9 January 2025 19:10
1
Have tried a number of times to install Manjaro KDE Stable but consistently end up with the installer shutting down after language setting.
The PC is a Lenovo Ideascentre 630 and had Win 10 and Manjaro installed on the original HDD. Changed that to a SSD, installed Win 11, Linux Mint and Refind, all working fine.
Have tried many ways to install Manjaro with different USB sticks, different USB slots, different downloads including Manjaro iso downloader/writer and Ventoy with forced EFI as descibed in (Live plasma iso can't boot from Ventoy )
I am stuck here and hope someone can help me solve this problem.
⌠and you did check and verify the integrity of the downloaded ISO?
1 Like
Pille
9 January 2025 19:34
3
I have an external SSD with several Linux ISO managed by Ventoy (latest release). It never showed issues while installing one of them.
So i would suggest following @Nachlese and download it again with verification of the ISO file.
It may save unnecessary effort downloading a fresh copy of Manjaro if you first verify the ISO you have. The checksum (SHA256) file for your chosen edition can be found at the official Manjaro download page:
Basically you have said âI tried this and that but it didnât workâ (paraphrasing). Before we can know exactly what your issue is, more information is needed.
Welcome to the Manjaro community.
As a new or infrequent forum user, please take some time to familiarise yourself with Forum requirements; in particular, the many ways to use the forum to your benefit:
Required Reading:
Resources:
Update Announcements:
The Update Announcements contain update related information and a Known Issues and Solutions section that should generally be checked before posting a request for support.
System Information:
Output of the following command (formatted according to forum requirements) may be useful for those wishing to help:
inxi --admin --verbosity=8 --filter --no-host --width
Be prepared to provide more information and outputs from other commands when asked.
Regards.
Note that the above text is partially pre-prepared as a general introduction for new forum Users. Please take the time to follow links given and learn how to create effective Support requests and encourage quality responses.
1 Like
Pille
10 January 2025 07:34
5
Agreed.
My bad
1 Like
I think your issue is with the integrity of the ISO - I cannot be sure though, but it is the most common cause of weird issues with the installer.
We have a couple of tools which can download and verify a Manjaro ISO.
Products â Manjaro .
Neither Sway nor ARM is supported, sway because the files is located elsewhere and ARM because there is no signature.
The script has options to fetch the latest stable release review ISO or unstable developer previews from Manjaro Github .
The source is available at Manjaro Gitlab
3 Likes
BG405
10 January 2025 09:28
10
I would typically use, after navigating to the desired download directory:
wget https://download.manjaro.org/kde/24.2.1/manjaro-kde-24.2.1-241216-linux612.iso
then
wget https://download.manjaro.org/kde/24.2.1/manjaro-kde-24.2.1-241216-linux612.iso.sha256
⌠followed with:
sha256sum -c --ignore-missing manjaro-kde-24.2.1-241216-linux612.iso.sha256
This method hasnât failed me yet. I got the links from the Download Page as shown in @soundofthunder âs post above.
1 Like
Ben
10 January 2025 13:15
13
For this reason - though sadly not highlighted - I generally prefer to use torrents for large downloads on a slower connection.
So next to âDownloadâ thereâs a 'More â tab which adds the options for Torrents, Image, Signature and Checksum - also a toggle for âFull
2 Likes
johs
11 January 2025 09:21
17
Thankâs for your input, have tried out BG405âs way, put iso on a Ventoy stick with GPT ticked and sad to say same thing happens.
but you can - just format them as âpreformatted textâ â this symbol: </>
johs
11 January 2025 11:04
19
Ok I will try again, output from inxiâŚ
System:
Kernel: 6.12.4-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us tz=UTC
lang=en_US keytable=no tz=UTC misobasedir=manjaro
misolabel=MANJARO_KDE_2421 quiet systemd.show_status=1 splash driver=free
nouveau.modeset=1 i915.modeset=1 radeon.modeset=1 rdinit=/vtoy/vtoy
Desktop: KDE Plasma v: 6.2.4 tk: Qt v: N/A wm: kwin_x11 dm: SDDM
Distro: Manjaro base: Arch Linux
Machine:
Type: Desktop System: LENOVO product: 90HC001NMW v: ideacentre 620S-03IKL
serial: <filter> Chassis: type: 3 serial: <filter>
Mobo: LENOVO model: 36E2 v: SDK0J40700 WIN 3258103362950 serial: N/A
part-nu: LENOVO_MT_90HC_BU_LENOVO_FM_ideacentre 620S-03IKL
uuid: b6f9b698-e6df-11e7-bb2d-2285f029bf01 UEFI: LENOVO v: O3GKT22A
date: 04/08/2019
Battery:
Message: No system battery data found. Is one present?
Memory:
System RAM: total: 8 GiB available: 7.65 GiB used: 2.66 GiB (34.8%)
igpu: 32 MiB
Array-1: capacity: 32 GiB slots: 2 modules: 1 EC: None
max-module-size: 16 GiB note: est.
Device-1: ChannelA-DIMM0 type: no module installed
Device-2: ChannelB-DIMM0 type: DDR4 detail: synchronous unbuffered
(unregistered) size: 8 GiB speed: 2400 MT/s volts: curr: 1.2 min: 1.2
max: 1.2 width (bits): data: 64 total: 64 manufacturer: Samsung
part-no: M471A1K43CB1-CRC serial: <filter>
PCI Slots:
Slot: 0 type: PCIe status: in use info: J6B2 length: long volts: 3.3
bus-ID: 00:01.0
Slot: 1 type: PCIe status: in use info: J6B1 length: short volts: 3.3
bus-ID: 00:1c.3
Slot: 2 type: PCIe status: in use info: J6D1 length: short volts: 3.3
bus-ID: 00:1c.4
Slot: 3 type: PCIe status: in use info: J7B1 length: short volts: 3.3
bus-ID: 00:1c.5
Slot: 4 type: PCIe status: in use info: J8B4 length: short volts: 3.3
bus-ID: 00:1c.6
CPU:
Info: model: Intel Core i5-7400T socket: U3E1 bits: 64 type: 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: 0xF8
Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 smt: <unsupported> cache:
L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
L3: 6 MiB desc: 1x6 MiB
Speed (MHz): avg: 800 min/max: 800/3000 base/boost: 2300/3000 scaling:
driver: intel_pstate governor: powersave volts: 0.8 V ext-clock: 100 MHz
cores: 1: 800 2: 800 3: 800 4: 800 bogomips: 19204
Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
arch_capabilities arch_perfmon art avx avx2 bmi1 bmi2 bts clflush
clflushopt cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64
dtherm dts epb erms est f16c flush_l1d fma fpu fsgsbase fxsr ht hwp
hwp_act_window hwp_epp hwp_notify ibpb ibrs ida intel_pt invpcid lahf_lm
lm mca mce md_clear mmx monitor movbe mpx msr mtrr nonstop_tsc nopl nx pae
pat pbe pcid pclmulqdq pdcm pdpe1gb pebs pge pln pni popcnt pse pse36 pti
pts rdrand rdseed rdtscp rep_good sdbg sep smap smep ss ssbd sse sse2
sse4_1 sse4_2 ssse3 stibp syscall tm tm2 tsc tsc_adjust tsc_deadline_timer
vme x2apic xgetbv1 xsave xsavec xsaveopt xsaves xtopology xtpr
Vulnerabilities:
Type: gather_data_sampling mitigation: Microcode
Type: itlb_multihit status: KVM: VMX unsupported
Type: l1tf mitigation: PTE Inversion
Type: mds mitigation: Clear CPU buffers; SMT disabled
Type: meltdown mitigation: PTI
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT disabled
Type: reg_file_data_sampling status: Not affected
Type: retbleed mitigation: IBRS
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: IBRS; IBPB: conditional; STIBP: disabled; RSB
filling; PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel HD Graphics 630 vendor: Lenovo driver: i915 v: kernel
arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: HDMI-A-2
empty: DP-1,HDMI-A-1,HDMI-A-3 bus-ID: 00:02.0 chip-ID: 8086:5912
class-ID: 0300
Display: unspecified server: X.Org v: 21.1.14 with: Xwayland v: 24.1.4
compositor: kwin_x11 driver: X: loaded: modesetting alternate: fbdev,vesa
dri: iris gpu: i915 display-ID: :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-2 mapped: HDMI-2 model: BenQ T2200HD serial: <filter>
built: 2009 res: 1920x1080 hz: 60 dpi: 102 gamma: 1.2 chroma: red: x: 0.651
y: 0.337 green: x: 0.282 y: 0.604 blue: x: 0.141 y: 0.071 white: x: 0.314
y: 0.329 size: 477x268mm (18.78x10.55") diag: 547mm (21.5") ratio: 16:9
modes: 1920x1080, 1280x1024, 1152x864, 1024x768, 800x600, 640x480, 720x400
API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris x11: drv: iris
inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.2.8-arch1.1
glx-v: 1.4 direct-render: yes renderer: Mesa Intel HD Graphics 630 (KBL GT2)
device-ID: 8086:5912 memory: 3.73 GiB unified: yes
API: Vulkan v: 1.4.303 layers: N/A device: 0 type: integrated-gpu
name: Intel HD Graphics 630 (KBL GT2) driver: N/A device-ID: 8086:5912
surfaces: xcb,xlib
Audio:
Device-1: Intel 200 Series PCH HD Audio vendor: Lenovo driver: snd_hda_intel
v: kernel alternate: snd_soc_avs bus-ID: 00:1f.3 chip-ID: 8086:a2f0
class-ID: 0403
API: ALSA v: k6.12.4-1-MANJARO status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: JACK v: 1.9.22 status: off tools: N/A
Server-2: PipeWire v: 1.2.7 status: n/a (root, process) with:
1: pipewire-pulse status: active 2: wireplumber status: active
3: pipewire-alsa type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Ethernet I219-V vendor: Lenovo driver: e1000e v: kernel
port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200
IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter>
IP v4: <filter> type: dynamic noprefixroute scope: global
broadcast: <filter>
IP v6: <filter> type: dynamic noprefixroute scope: global
IP v6: <filter> type: noprefixroute scope: link
Device-2: Intel Dual Band Wireless-AC 3165 Plus Bluetooth driver: iwlwifi
v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 02:00.0
chip-ID: 8086:3166 class-ID: 0280
IF: wlp2s0 state: down mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
WAN IP: <filter>
Bluetooth:
Device-1: Intel Bluetooth wireless interface driver: btusb v: 0.8 type: USB
rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-3:3 chip-ID: 8087:0a2a
class-ID: e001
Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Logical:
Message: No logical block device data found.
RAID:
Device-1: md127 maj-min: 9:127 type: mdraid level: N/A status: inactive
size: N/A
Info: report: N/A blocks: 2944 chunk-size: N/A
Components: Online: N/A Spare:
0: nvme0n1 maj-min: 259:0 size: 13.41 GiB state: S
Drives:
Local Storage: total: 486.63 GiB used: 146.69 GiB (30.1%)
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Intel model: MEMPEK1W016GAL
size: 13.41 GiB block-size: physical: 512 B logical: 512 B speed: 15.8 Gb/s
lanes: 2 tech: SSD serial: <filter> fw-rev: K3110311 temp: 46.9 C
SMART: yes health: PASSED on: 42d 22h cycles: 563
read-units: 5,384,090 [2.75 TB] written-units: 4,004,610 [2.05 TB]
ID-2: /dev/sda maj-min: 8:0 vendor: PNY model: CS900 500GB SSD
family: Driven SSDs size: 465.76 GiB block-size: physical: 512 B
logical: 512 B sata: 3.2 speed: 6.0 Gb/s tech: SSD serial: <filter>
fw-rev: 0615 temp: 33 C scheme: GPT
SMART: yes state: enabled health: PASSED on: 57 hrs cycles: 48
written: 349 GiB
ID-3: /dev/sdb maj-min: 8:16 vendor: SanDisk model: Cruzer Blade
size: 7.45 GiB block-size: physical: 512 B logical: 512 B type: USB rev: 2.1
spd: 480 Mb/s lanes: 1 mode: 2.0 tech: N/A serial: <filter> fw-rev: 1.00
scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Message: No optical or floppy data found.
Partition:
ID-1: /run/media/manjaro/Data raw-size: 279.18 GiB size: 279.18 GiB (100.00%)
used: 146.69 GiB (52.5%) fs: ntfs block-size: 4096 B dev: /dev/sda7
maj-min: 8:7 label: Data uuid: B8349AEA349AAB40
Swap:
Alert: No swap data was found.
Unmounted:
ID-1: /dev/dm-0 maj-min: 254:0 mapped: ventoy size: 4.03 GiB fs: iso9660
ID-2: /dev/sda1 maj-min: 8:1 size: 100 MiB fs: vfat label: N/A
uuid: 7237-C4BF
ID-3: /dev/sda2 maj-min: 8:2 size: 16 MiB fs: N/A label: N/A uuid: N/A
ID-4: /dev/sda3 maj-min: 8:3 size: 107.71 GiB fs: ntfs label: Win11
uuid: 44A8395BA8394D24
ID-5: /dev/sda4 maj-min: 8:4 size: 644 MiB fs: ntfs label: N/A
uuid: DEC24689C246663D
ID-6: /dev/sda5 maj-min: 8:5 size: 39.06 GiB fs: ntfs label: Manjaro
uuid: DECE6BB5CE6B851D
ID-7: /dev/sda6 maj-min: 8:6 size: 39.06 GiB fs: ext4 label: N/A
uuid: b5e216a8-cdd7-4369-a8f7-8ab80081dc98
ID-8: /dev/sdb1 maj-min: 8:17 size: 7.42 GiB fs: exfat label: Ventoy
uuid: 1CEB-F69E
ID-9: /dev/sdb2 maj-min: 8:18 size: 32 MiB fs: vfat label: VTOYEFI
uuid: 223C-F3F8
USB:
Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 12 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Device-1: 1-1:2 info: Realtek RTS5129 Card Reader Controller
type: <vendor specific> driver: rtsx_usb,rtsx_usb_ms,rtsx_usb_sdmmc
interfaces: 1 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0
power: 500mA chip-ID: 0bda:0129 class-ID: ff00 serial: <filter>
Device-2: 1-3:3 info: Intel Bluetooth wireless interface type: bluetooth
driver: btusb interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1
mode: 1.1 power: 100mA chip-ID: 8087:0a2a class-ID: e001
Device-3: 1-6:4 info: SiGma Micro Keyboard TRACER Gamma Ivory
type: keyboard,HID driver: hid-generic,usbhid interfaces: 2 rev: 1.1
speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 98mA
chip-ID: 1c4f:0002 class-ID: 0300
Device-4: 1-7:5 info: SiGma Micro XM102K Optical Wheel Mouse type: mouse
driver: hid-generic,usbhid interfaces: 1 rev: 1.1 speed: 1.5 Mb/s (183 KiB/s)
lanes: 1 mode: 1.0 power: 100mA chip-ID: 1c4f:0034 class-ID: 0301
Device-5: 1-8:6 info: SanDisk Cruzer Blade type: mass storage
driver: usb-storage interfaces: 1 rev: 2.1 speed: 480 Mb/s (57.2 MiB/s)
lanes: 1 mode: 2.0 power: 224mA chip-ID: 0781:5567 class-ID: 0806
serial: <filter>
Hub-2: 2-0:1 info: super-speed hub ports: 6 rev: 3.0
speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d6b:0003
class-ID: 0900
Sensors:
System Temperatures: cpu: 40.0 C mobo: N/A
Fan Speeds (rpm): N/A
Repos:
Packages: pm: pacman pkgs: 1248 libs: 327 tools: pamac pm: flatpak pkgs: 0
Active pacman repo servers in: /etc/pacman.d/mirrorlist
Processes:
CPU top: 5 of 220
1: cpu: 13.7% command: firefox pid: 3250 mem: 444.8 MiB (5.6%)
2: cpu: 9.6% command: firefox pid: 3678 mem: 276.0 MiB (3.5%)
3: cpu: 3.6% command: kwin_x11 pid: 1499 mem: 176.2 MiB (2.2%)
4: cpu: 3.3% command: Xorg pid: 1366 mem: 92.7 MiB (1.1%)
5: cpu: 0.9% command: kwrite pid: 4618 mem: 140.6 MiB (1.7%)
Memory top: 5 of 220
1: mem: 444.8 MiB (5.6%) command: firefox pid: 3250 cpu: 13.7%
2: mem: 311.4 MiB (3.9%) command: plasmashell pid: 1530 cpu: 0.5%
3: mem: 276.0 MiB (3.5%) command: firefox pid: 3678 cpu: 9.6%
4: mem: 176.2 MiB (2.2%) command: kwin_x11 pid: 1499 cpu: 3.6%
5: mem: 173.6 MiB (2.2%) command: firefox pid: 3658 cpu: 0.1%
Info:
Processes: 220 Power: uptime: 31m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 3.01 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
tool: systemctl
Compilers: N/A Shell: Sudo (sudo) v: 1.9.16p2 default: Bash v: 5.2.37
running-in: konsole inxi: 3.3.36
1 Like
johs:
The PC is a Lenovo Ideascentre 630 and had Win 10 and Manjaro installed on the original HDD. Changed that to a SSD, installed Win 11, Linux Mint and Refind, all working fine.
So Linux works on this machine, and only the installer fails with what you selected.
Does the Linux from the live ISO work reliably (without installing)?
Do the other installations (Manjaro/Mint) have special kernel parameters to make them work?
Is this a UEFI-Install ? (Are the other systems also UEFI installed ?)
What kernels do these installations have?
Can you enable swap before starting the installer?
Do you select anything special in the installer
What happens if you start the installer from the command line ?
Are there any actionable error messages then? (please post in full here)
1 Like
johs
13 January 2025 11:27
22
Started Calamares from command line and got this message;
calamares î˛ 127 â
/dev/mapper/control: open failed: Permission denied
Failure to communicate with kernel device-mapper driver.
Incompatible libdevmapper 1.02.203 (2024-12-09) and kernel driver (unknown version).
11:23:13 [1]: ERROR (Qt): ASSERT: "efiSectorCount > 0" in file /build/calamares/src/calamares-3.3.12/src/modules/partition/core/PartitionActions.cpp, line 125
zsh: IOT instruction (core dumped) calamares
Moderator edit: Fixed formatting typos. Please review [HowTo] Post command output and file content as formatted text
Calamares does not support LVM nor does it support RAID constructs.
You may succeed if you assemble the RAID beforehand - then target /dev/mapper/md127 for installation - but it is unsupported.
If you have no data and just want to install Manjaro I suggest you wipe disk signatures before launching the installer.
Use lsblk to identify your physical devices
lsblk
Devices will have names like nvme* or sd*
Use sgdisk to wipe all signatures
sudo sgdisk /dev/nvmeYn1 --zap-all
Or in case of sata
sudo sgdisk /dev/sdx --zap-all
It doesnât?
I thought it even offered it as a choice during install.
If lvm is a problem:gparted (or dd ⌠or anything that can wipe out the disk)
Nope - not in the default Manjaro installer.
It is possible if you know how to setup LVM or RAID manually - but it is generally unsupported.
Calamares is an installer framework - so it is possible to create custom modules for Calamares to achieve such setup - and other distributions may have done so - Manjaro is not one of those.
o.k. - I just looked at it and you are right!
So the only option (to me) seems to be to wipe the disk (to remove any notion of an LVM)
johs
13 January 2025 12:16
27
I am confused here, againâŚ
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 90.1M 1 loop /run/miso/sfs/livefs
loop1 7:1 0 1.1G 1 loop /run/miso/sfs/mhwdfs
loop2 7:2 0 1.8G 1 loop /run/miso/sfs/desktopfs
loop3 7:3 0 858.9M 1 loop /run/miso/sfs/rootfs
sda 8:0 0 465.8G 0 disk
ââsda1 8:1 0 100M 0 part
ââsda2 8:2 0 16M 0 part
ââsda3 8:3 0 107.7G 0 part
ââsda4 8:4 0 644M 0 part
ââsda5 8:5 0 39.1G 0 part
ââsda6 8:6 0 39.1G 0 part
ââsda7 8:7 0 279.2G 0 part
sdb 8:16 1 7.5G 0 disk
ââsdb1 8:17 1 7.4G 0 part
â ââventoy 254:0 0 4G 1 dm /run/miso/bootmnt
ââsdb2 8:18 1 32M 0 part
nvme0n1 259:0 0 13.4G 0 disk
ââmd127 9:127 0 0B 0 md
the above seems to be the output of
lsblk
What is confusing about it to you?
A more helpful, more verbose, command would be:
lsblk -f
or
blkid
⌠the lvm you mentioned could be on the nvme ssd (probably âŚ)/dev/sda âŚ
loop (0 through 3) is the mounted file systems on the ISO you booted up/dev/sdb is the drive you booted from - your Ventoy drive
