Problem with Sourceforge’s antiX-19.4_x64-core.iso [solved]

[Member mikey777]

Just downloaded antiX-19.4_x64-core.iso, copied it to a USB stick, and started a fresh install onto a laptop. However. the installation got stuck before it got to logging in as user (root), password (root) and cli-installer stage. It got stuck at this line:

[....] Waiting for /dev to be fully populated ...

Any ideas on how to fix this, or should I wait till Evowise repository releases the 19.4 iso ?

• This topic was modified 1 year, 11 months ago by mikey777.
• This topic was modified 1 year, 11 months ago by anticapitalista. Reason: edited title to solved

▪ 32-bit antix19.4-core+LXDE installed on :
- (2011) Samsung NP-N145 Plus (JP04UK) – single-core CPU Intel Atom N455@1.66GHz, 2GB RAM, integrated graphics.
▪ 64-bit antix21-base+LXDE installed on:
- (2008) Asus X71Q (7SC002) – dual CPU Intel T3200@2.0GHz, 4GB RAM. Graphics: Intel Mobile 4 Series, integrated graphics
- (2007) Packard Bell Easynote MX37 (ALP-Ajax C3) – dual CPU Intel T2310@1.46GHz, 2GB RAM. Graphics: Silicon Integrated Systems.

[Moderator christophe]

Helpful

Up

0

::

Hello, mikey777.

Some time ago, I remember having live bootup hanging at someplace on at least one of my computers — it may have been at /dev being populated.

Someone suggested to delete the “splash” boot parameter on the live-usb boot screen.

And that took care of it on my computer(s). Try that. 🙂

• This reply was modified 1 year, 11 months ago by christophe.

confirmed antiX frugaler, since 2019

[Member Xecure]

Helpful

Up

0

::

If your device is very new, kernel 4.9 will not be able to support it, so if you remove splasht or failsafe mode doesn’t work, you could share computer info (mainly processor and GPU) for us to check.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member mikey777]

Helpful

Up

0

::

christophe wrote:

Someone suggested to delete the “splash” boot parameter on the live-usb boot screen.

And that took care of it on my computer(s). Try that.

Christophe, I deleted the entire “splash” boot paramter line on the live-usb boot screen and then the install worked flawlessly :-). I now have 19.4 core + LXDE set up on a 14-year-old Asus 17″ X71Q laptop (2GHz dual-core Pentium T3200 CPU; 4GB RAM), idling nicely at 0-2% CPU activity, using 150-155MB of RAM. It’s using Kernel 4.4.264.

Many thanks again Christophe – really appreciative of your help.

• This reply was modified 1 year, 11 months ago by mikey777.

▪ 32-bit antix19.4-core+LXDE installed on :
- (2011) Samsung NP-N145 Plus (JP04UK) – single-core CPU Intel Atom N455@1.66GHz, 2GB RAM, integrated graphics.
▪ 64-bit antix21-base+LXDE installed on:
- (2008) Asus X71Q (7SC002) – dual CPU Intel T3200@2.0GHz, 4GB RAM. Graphics: Intel Mobile 4 Series, integrated graphics
- (2007) Packard Bell Easynote MX37 (ALP-Ajax C3) – dual CPU Intel T2310@1.46GHz, 2GB RAM. Graphics: Silicon Integrated Systems.

[Member mikey777]

Helpful

Up

0

::

Xecure wrote:

If your device is very new, kernel 4.9 will not be able to support it, so if you remove splasht or failsafe mode doesn’t work, you could share computer info (mainly processor and GPU) for us to check.

Many thanks for your reply Xecure and continued support. As mentioned to Christophe, it’s not a new machine (14-years-old). Being old hardware, I had the opposite problem to the one you suggested for a newer machine. I tried different Kernels: with 5.10, the laptop boots to a blank screen and stays stuck there, with 4.9 and 4.4 there are no problems, RAM consumption being significantly lower at 4.4 (154MB) than with 4.9 (190MB).

I notice LTS Kernel version 5.4 is not listed in cli-aptiX – is there a reason for that ?

Could the booting to a blank screen with Kernel 5.10 have anything to do with me deleting the entire “splash line” on the live-USB boot screen ?

▪ 32-bit antix19.4-core+LXDE installed on :
- (2011) Samsung NP-N145 Plus (JP04UK) – single-core CPU Intel Atom N455@1.66GHz, 2GB RAM, integrated graphics.
▪ 64-bit antix21-base+LXDE installed on:
- (2008) Asus X71Q (7SC002) – dual CPU Intel T3200@2.0GHz, 4GB RAM. Graphics: Intel Mobile 4 Series, integrated graphics
- (2007) Packard Bell Easynote MX37 (ALP-Ajax C3) – dual CPU Intel T2310@1.46GHz, 2GB RAM. Graphics: Silicon Integrated Systems.

[Member Xecure]

Helpful

Up

0

::

mikey777 wrote:

I notice LTS Kernel version 5.4 is not listed in cli-aptiX – is there a reason for that ?

antiX kernels are built by the main developer. Keeping just 4 main versions is more than enough work, so if a new kernel is required, switch to 5.10. Alternatively, you can use Debian kernels if you need a specific version and they have it available (in repos).

mikey777 wrote:

Could the booting to a blank screen with Kernel 5.10 have anything to do with me deleting the entire “splash line” on the live-USB boot screen ?

Is this after installing, after remastering + live-kernel-update or is this a different ISO?

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Forum Admin anticapitalista]

Helpful

Up

0

::

RAM. It’s using Kernel 4.4.264.

You should use 4.4.0-264

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member mikey777]

Helpful

Up

0

::

Xecure wrote:

<a href=”https://www.antixforum.com/forums/topic/problem-with-sourceforges-antix-19-4_x64-core-iso/#post-59938&#8243;
Is this after installing, after remastering + live-kernel-update or is this a different ISO?

This is the same 19.4-corex64+LXDE setup on the same machine that I mentioned already, the OS being installed onto the laptop’s internal SSD. Following installing and booting to the desktop, using the preinstalled 4.9 kernel, I used cli-aptiX to install two further kernels (4.4.0 and 5.10), just to compare CPU & RAM performance with each kernel. When I booted into 5.10, I selected this kernel from the grubscreen. No problems booting the OS with 4.4.0 and 4.9 – only 5.10 gives the blank screen.

• This reply was modified 1 year, 11 months ago by mikey777.

▪ 32-bit antix19.4-core+LXDE installed on :
- (2011) Samsung NP-N145 Plus (JP04UK) – single-core CPU Intel Atom N455@1.66GHz, 2GB RAM, integrated graphics.
▪ 64-bit antix21-base+LXDE installed on:
- (2008) Asus X71Q (7SC002) – dual CPU Intel T3200@2.0GHz, 4GB RAM. Graphics: Intel Mobile 4 Series, integrated graphics
- (2007) Packard Bell Easynote MX37 (ALP-Ajax C3) – dual CPU Intel T2310@1.46GHz, 2GB RAM. Graphics: Silicon Integrated Systems.

[Member mikey777]

Helpful

Up

0

::

anticapitalista wrote:

RAM. It’s using Kernel 4.4.264.

You should use 4.4.0-264

Typo! Yes, I’m using 4.4.0-264.

• This reply was modified 1 year, 11 months ago by mikey777.

▪ 32-bit antix19.4-core+LXDE installed on :
- (2011) Samsung NP-N145 Plus (JP04UK) – single-core CPU Intel Atom N455@1.66GHz, 2GB RAM, integrated graphics.
▪ 64-bit antix21-base+LXDE installed on:
- (2008) Asus X71Q (7SC002) – dual CPU Intel T3200@2.0GHz, 4GB RAM. Graphics: Intel Mobile 4 Series, integrated graphics
- (2007) Packard Bell Easynote MX37 (ALP-Ajax C3) – dual CPU Intel T2310@1.46GHz, 2GB RAM. Graphics: Silicon Integrated Systems.

[Forum Admin anticapitalista]

Helpful

Up

0

::

I’ll mark the thread as solved since there is no issue with Sourceforge’s antiX-19.4_x64-core.iso

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Author]

Posts