ISO problems (on specific hardware)

Hi, I don’t know if this is the place for this topic, I think it is as it is related to installation problems.
I downloaded 3 different isos from Mabox to test the one that worked best on my PC and to keep it as a rescue tool.

This is the ISO I’m using today.

mabox-linux-24.01-Istredd-240114-linux61.iso

None of the three get past the lightdm error.
I took some screenshots with my cell phone to show you the problem I’m having.
I checked them with cheksum and on other pcs and it works only on the notebook.
I am worried that none of them work in my system and it is strange because in this machine I have Mabox installed since 2023.
On the installed Mabox I was able to solve the problem, but what if no iso works for me and I would like to do a reinstall or put it on another machine?
I tried in Spanish and English and it does not load.



How do you boot from ISO?

How do you prepare ISO to boot?

What is the point to use 1 year 3 months old ISO of rolling-release distro, when refreshed ISO images are published monthly?

Edit:
I specifically downloaded that old ISO you mentioned. To test it again - of course ISO images are always carefully tested before publication.

And… it works, of course.

Maybe your Hardware is very specific and does not work well with modern kernels/drivers…

So maybe try to install another lightweight distro on this computer… Something Debian based might be a good choice… there are tens of them :wink:

1 Like

I answer your questions in order.

To boot the pendrive with the iso image I turn on the PC, with the pendrive in the USB port, interrupt the booting with F8, from the list of options I choose the pendrive created with (https://www.ventoy.net/en/index.html)
Para crear el usb de arranque sigo las instrucciones de ventoy, luego copio las isos al pendrive y las ejecuto como mencioné anteriormente.
En ese mismo pendrive tengo la iso de Manjaro, la de Antix y la de Mabox.
Como ya dije en posteos anteriores, primero bajé la última iso disponible, la más actual, como falló, bajé la anterior, volvió a fallar entonces bajé esta última, precisamente pensando que el problema podría ser el kernel, pero según veo en mi Conky, estoy usando el 6.12.20 así que ese no es el problema, durante mucho tiempo usé el 5.10…, descartados problemas con el kernel luego de probar otros, dejo que Mabox decida cual usar.


I rule out problems with the pendrive since I was able to install Manjaro on my other PC with exactly the same hardware as this one I use with Mabox, I used the pendrive with Mabox on the Dell Vostro notebook and it worked perfect, it also works with Antix, in fact, I have another pendrive with persistence to take with me when I travel and for testing that also works perfectly fine.

I tried the 4 USB ports of the pc and in all of them I got the same error.
If I insist on using Mabox is because I really put my heart in the Distro, I find it excellent and of those I have used and have in use is the one that gives me more satisfaction.
I understand that there is a learning curve and that you, like many in the Manjaro Forum believe that they are not Distros for beginners, and possibly they are right, but I am willing to go the way to learn. I’m just asking for a little guidance, and I don’t think I’m doing too badly. in fact, I’ve been using Mabox since 2022, I inadvertently dragged the mouse with my arm one night while I had the file manager open and moved system files all over the tree and was forced to perform a new installation.
At no time do I doubt your knowledge, your work, your effort and the quality of Mabox.
I really wish I could dedicate more time to my learning, but I have a disabled daughter who requires my attention and to whom I dedicate my life, in the times she leaves me free I try to work and study, my wife is the breadwinner, she is retiring in 2 years and we will change roles, i.e. I will work more and she will take care of the child. I am 64 years old, I do the best I can.

I also spend time in my talks with friends to spread the use of Linux in general and Mabox in particular. Anyway, this is getting offtopic.
I understand that the conflict is in my hardware, here is the result of inxi -zv8

claudio@Claudio-Mabox ~ $ inxi -zv8
System:
  Kernel: 6.12.20-2-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.12-x86_64
    root=UUID=eaf47a78-5bb0-45b8-9857-8d7edfaebf7b rw quiet
    resume=UUID=b6c8299f-6640-47b8-8545-24e0f88a4203 udev.log_priority=3
  Desktop: Xfce v: N/A wm: Openbox v: 3.6.1 with: tint2 tools: avail: i3lock
    vt: 7 dm: LightDM v: 1.32.0 Distro: Mabox base: Arch Linux
Machine:
  Type: Desktop Mobo: ASUSTeK model: P5KPL-AM SE v: X.0x
    serial: <superuser required> uuid: <superuser required>
    BIOS: American Megatrends v: 0702 date: 08/20/2010
Battery:
  Message: No system battery data found. Is one present?
Memory:
  System RAM: total: 4 GiB available: 3.81 GiB used: 1.45 GiB (38.0%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 4 GiB slots: 2 modules: 2 EC: None
    max-module-size: 2 GiB note: est.
  Device-1: DIMM A1 type: DDR2 detail: synchronous size: 2 GiB
    speed: 667 MT/s volts: N/A width (bits): data: 64 total: 64
    manufacturer: N/A part-no: N/A serial: N/A
  Device-2: DIMM B1 type: DDR2 detail: synchronous size: 2 GiB
    speed: 667 MT/s volts: N/A width (bits): data: 64 total: 64
    manufacturer: N/A part-no: N/A serial: N/A
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: Pentium E5200 bits: 64 type: MCP arch: Penryn level: v1
    built: 2008 process: Intel 45nm family: 6 model-id: 0x17 (23) stepping: 6
    microcode: 0x60F
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 2 smt: <unsupported> cache:
    L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 2 MiB desc: 1x2 MiB
  Speed (MHz): avg: 1343 min/max: 1200/2500 scaling: driver: acpi-cpufreq
    governor: schedutil cores: 1: 1343 2: 1343 bogomips: 10002
  Flags: acpi aperfmperf apic arch_perfmon bts clflush cmov constant_tsc
    cpuid cx16 cx8 de ds_cpl dtes64 dtherm dts est fpu fxsr ht lahf_lm lm mca
    mce mmx monitor msr mtrr nopl nx pae pat pbe pdcm pebs pge pni pse pse36
    pti rep_good sep sse sse2 ssse3 syscall tm tm2 tsc vme xtpr
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: KVM: VMX unsupported
  Type: l1tf mitigation: PTE Inversion
  Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode;
    SMT disabled
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  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; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel 82G33/G31 Express Integrated Graphics
    vendor: ASUSTeK P5KPL-VM driver: i915 v: kernel arch: Gen-4
    process: Intel 65n built: 2006-07 ports: active: VGA-1 empty: none
    bus-ID: 00:02.0 chip-ID: 8086:29c2 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.16 with: Xwayland v: 24.1.6 driver: X:
    loaded: intel unloaded: fbdev,modesetting alternate: vesa dri: i915
    gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1600x900 s-dpi: 96 s-size: 423x238mm (16.65x9.37")
    s-diag: 485mm (19.11")
  Monitor-1: VGA-1 mapped: VGA1 model: Samsung SA300/SA350 serial: <filter>
    built: 2010 res: mode: 1600x900 hz: 60 scale: 100% (1) dpi: 92 gamma: 1.2
    chroma: red: x: 0.639 y: 0.341 green: x: 0.325 y: 0.624 blue: x: 0.153
    y: 0.039 white: x: 0.314 y: 0.329 size: 440x250mm (17.32x9.84")
    diag: 508mm (20") ratio: 16:9 modes: 1600x900, 1440x900, 1280x800,
    1152x864, 1024x768, 832x624, 800x600, 640x480, 720x400
  API: EGL v: 1.5 hw: drv: intel i915 platforms: device: 0 egl: 1.4
    drv: i915 device: 1 drv: swrast gbm: egl: 1.4 drv: i915 surfaceless:
    egl: 1.4 drv: i915 x11: drv: swrast inactive: wayland
  API: OpenGL v: 4.5 compat-v: 2.1 vendor: mesa v: 25.0.2-arch1.2 glx-v: 1.4
    direct-render: yes renderer: llvmpipe (LLVM 19.1.7 128 bits)
    device-ID: ffffffff:ffffffff memory: 3.72 GiB unified: yes
  Info: Tools: api: eglinfo,glxinfo de: kscreen-doctor
    x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel NM10/ICH7 Family High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:27d8
    class-ID: 0403
  API: ALSA v: k6.12.20-2-MANJARO status: kernel-api
    tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: JACK v: 1.9.22 status: off tools: N/A
  Server-3: PipeWire v: 1.4.1 status: off with: wireplumber status: active
    tools: pw-cli,wpctl
  Server-4: PulseAudio v: 17.0-43-g3e2bb status: active
    with: pulseaudio-alsa type: plugin tools: pacat,pactl,pamixer,pavucontrol
Network:
  Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: ASUSTeK
    driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e800
    bus-ID: 01:00.0 chip-ID: 10ec:8136 class-ID: 0200
  IF: enp1s0 state: up speed: 100 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: link
  Info: services: NetworkManager,systemd-timesyncd
  WAN IP: <filter>
Bluetooth:
  Message: No bluetooth data found.
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 225.74 GiB used: 28.65 GiB (12.7%)
  ID-1: /dev/sda maj-min: 8:0 vendor: Hitachi model: HDS728080PLAT20
    size: 76.69 GiB block-size: physical: 512 B logical: 512 B speed: <unknown>
    tech: N/A serial: <filter> fw-rev: A21B scheme: MBR
  SMART Message: Unknown smartctl error. Unable to generate data.
  ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital
    model: WD1600AABS-61PRA0 size: 149.05 GiB block-size: physical: 512 B
    logical: 512 B speed: <unknown> tech: N/A serial: <filter> fw-rev: 6H05
    scheme: MBR
  SMART Message: Unknown smartctl error. Unable to generate data.
  Optical-1: /dev/sr0 vendor: TSSTcorp model: CDDVDW SH-S203D rev: SB00
    dev-links: cdrom
  Features: speed: 48 multisession: yes audio: yes dvd: yes
    rw: cd-r,cd-rw,dvd-r,dvd-ram state: running
Partition:
  ID-1: / raw-size: 28.32 GiB size: 27.71 GiB (97.83%) used: 11.16 GiB (40.3%)
    fs: ext4 block-size: 4096 B dev: /dev/sda3 maj-min: 8:3 label: N/A
    uuid: eaf47a78-5bb0-45b8-9857-8d7edfaebf7b
  ID-2: /home raw-size: 46.41 GiB size: 45.38 GiB (97.78%)
    used: 17.49 GiB (38.5%) fs: ext4 block-size: 4096 B dev: /dev/sda1
    maj-min: 8:1 label: N/A uuid: f0ef4674-ef5a-47f0-b140-84966410292f
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: partition size: 1.95 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/sda2 maj-min: 8:2 label: N/A
    uuid: b6c8299f-6640-47b8-8545-24e0f88a4203
Unmounted:
  ID-1: /dev/sdb1 maj-min: 8:17 size: 29.53 GiB fs: vfat label: MARTE
    uuid: EF71-4BE5
  ID-2: /dev/sdb2 maj-min: 8:18 size: 78.13 GiB fs: vfat label: JUPITER
    uuid: 98C0-D06A
  ID-3: /dev/sdb3 maj-min: 8:19 size: 38.83 GiB fs: vfat label: SAGITARIO
    uuid: EEE4-4FDC
USB:
  Hub-1: 1-0:1 info: full speed or root hub ports: 2 rev: 1.1
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 chip-ID: 1d6b:0001
    class-ID: 0900
  Device-1: 1-1:2 info: Holtek Keyboard 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: 100mA
    chip-ID: 04d9:1503 class-ID: 0300
  Device-2: 1-2:3 info: Silicon Labs USB OPTICAL MOUSE type: mouse
    driver: hid-generic,usbhid interfaces: 1 rev: 2.0
    speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 100mA
    chip-ID: 10c4:8108 class-ID: 0301
  Hub-2: 2-0:1 info: full speed or root hub ports: 8 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-3: 3-0:1 info: full speed or root hub ports: 2 rev: 1.1
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 chip-ID: 1d6b:0001
    class-ID: 0900
  Hub-4: 4-0:1 info: full speed or root hub ports: 2 rev: 1.1
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 chip-ID: 1d6b:0001
    class-ID: 0900
  Hub-5: 5-0:1 info: full speed or root hub ports: 2 rev: 1.1
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 chip-ID: 1d6b:0001
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 31.0 C mobo: 38.0 C
  Fan Speeds (rpm): cpu: 964 case-1: 0
  Power: 12v: 12.62 5v: N/A 3.3v: 3.39 vbat: N/A
Repos:
  Packages: pm: pacman pkgs: 1287 libs: 301 tools: pamac,yay
  Active pacman repo servers in: /etc/pacman.conf
    1: https://repo.maboxlinux.org/stable/$arch/
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://cofractal-ewr.mm.fcix.net/manjaro/stable/$repo/$arch
    2: https://manjaro.ipacct.com/manjaro/stable/$repo/$arch
    3: https://ask4.mm.fcix.net/manjaro/stable/$repo/$arch
    4: https://mirror.netcologne.de/manjaro/stable/$repo/$arch
    5: https://mirror1.sox.rs/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 149
  1: cpu: 20.6% command: firefox pid: 82800 mem: 681.4 MiB (17.4%)
  2: cpu: 16.0% command: firefox pid: 83247 mem: 326.8 MiB (8.3%)
  3: cpu: 4.4% command: firefox pid: 83364 mem: 297.9 MiB (7.6%)
  4: cpu: 3.1% command: pulseaudio pid: 81967 mem: 41.4 MiB (1.0%)
  5: cpu: 2.3% command: firefox pid: 83115 mem: 168.4 MiB (4.3%)
  Memory top: 5 of 149
  1: mem: 681.4 MiB (17.4%) command: firefox pid: 82800 cpu: 20.6%
  2: mem: 326.8 MiB (8.3%) command: firefox pid: 83247 cpu: 16.0%
  3: mem: 297.9 MiB (7.6%) command: firefox pid: 83364 cpu: 4.4%
  4: mem: 168.4 MiB (4.3%) command: firefox pid: 83115 cpu: 2.3%
  5: mem: 148.2 MiB (3.7%) command: firefox pid: 87010 cpu: 0.2%
Info:
  Processes: 149 Power: uptime: 59m states: freeze,standby,mem,disk
    suspend: deep avail: s2idle,shallow wakeups: 0 hibernate: platform
    avail: shutdown, reboot, suspend, test_resume image: 1.51 GiB
    Init: systemd v: 257 default: graphical tool: systemctl
  Compilers: gcc: 14.2.1 Shell: Bash v: 5.2.37 running-in: terminator
    inxi: 3.3.38

I hope I have answered your questions.
Some changes in Mabox are not in my favour so I will try to disable them like screen lock, hibernation, etc.

@Claudio

I’m gonna jump in a leg here but, did you check the RAM with memtest?

I have the impression that all your problems seem hardware related. RAM or motherboard are my bets. :thinking:

2 Likes

Hi @M0nst3r thank you very much for your intervention.

When I started with the problems, I took the trouble to disassemble the pc, changed thermal paste, cleaned contacts, checked cables, coolers, ports, etc. and reassembled. The memory was the first thing I thought, I had not mentioned it because I knew it was not that or the hard drive that I also checked with gsmart, I found no problems in Bios, and the battery is in good condition, if I notice that when you boot an iso, no matter which, the time is different, ruled out the internal problems of the machine I assumed that is due to the time and place where the iso was created, I also thought it might be a language problem so I also tried in English.

The strange thing is that it’s the isos that are failing, not the installed Mabox, except for that lightdm problem that is already solved and some mistakes that I made in my desire to recover the system.

Now it runs perfect, fully updated. If I put an iso from another distro it works, only the Mabox one fails and that’s what I don’t know how to solve it.

Hi @muzqs thank you very much for your contribution.
My system is not UEFI compatible, only Bios and it doesn’t receive any more updates, the last one is from 2010 and I did it myself.
The USB is in legacy mode, although Ventoy offers the possibility of booting in UEFI mode, both systems work, I tried it on my wife’s machine that that UEFI, same pendrive, same isos, and it worked, I recently recovered a netbook from a friend who by the characteristics of the machine and because he does not want to complicate with the constant development, I put Antix for his 1.6 Ghz processor and 2 Gigas of RAM was very comfortable, attractive and according to his words never worked so well and so fast. I mention this because I know my limitations as a user.
If that were the problem, it should also fail on the other PC with identical hardware, BIOS, etc., and yet the only ISO that fails is the Mabox one. I tried the three ISOs I downloaded on different machines, and it worked on the DELL, my wife’s Asus, and a friend’s HP.
This problem is new to me because I’ve had Mabox installed since 2022, with a reinstallation in 2023, and I haven’t had any issues. My old hardware has successfully passed all the updates. I usually use programs like Gimp and Inkscape that are quite demanding, and it works. Right now, with Firefox with two tabs open, it’s at 12%, fluctuating to 24% CPU usage, and 1.26 GB of RAM, without requiring swap.


If that were the problem, it should also fail on the other PC with identical hardware, BIOS, etc., and yet the only ISO that fails is the Mabox one. I tried the three ISOs I downloaded on different machines, and it worked on the DELL, my wife’s Asus, and a friend’s HP.
This problem is new to me because I’ve had Mabox installed since 2022, with a reinstallation in 2023, and I haven’t had any issues. My old hardware has successfully passed all the updates. I usually use programs like Gimp and Inkscape that are quite demanding, and it works. Right now, with Firefox with two tabs open, it’s at 12%, fluctuating to 24% CPU usage, and 1.26 GB of RAM, without requiring swap.

1 Like

Hi @Claudio ,

I removed my post, because your system is working.

I don’t see a problem.

Your system is running fine since 2023. :wink:

Or iam now confussed between all hardwares…

:bird:

1 Like

Hahaha, after the last March update, the problems with LightDM started on the PC. That’s now fixed, but it persists on the ISOs. So, I wouldn’t be able to reinstall Mabox if necessary. I also can’t get a recovery ISO unless I create one myself with my system installed, but I don’t trust my skills for that.

1 Like

No worries. When the moment is there, there will be a solution.
Backup. To kick in an open door :leg: .

Relax, be mindfull with the system. :alien_monster:

Note: Looking at your comp specs. It could do with a SSD. This is worth the money and makes the system really mutch quicker. specialy for older hardware this is a good upgrade.

:bird:

Please stop mixing languages here. Only English, please.
If you like to write in Spanish use Spanish category.

I’m just trying to keep the forum useful.
This is the last warning.

1 Like

I corrected it there.
I changed the translator and the fields were all wrong.
Thanks for letting me know.