[Boot error] antix 22 – waiting for /dev to be fully populated

[Member imnull]

Hi,

I’m facing this issue while I’m trying to boot with anti beat me.

It’s just stucks at this message:
‘waiting for /dev to be fully populated’

First i have tried other boot methods (safe boot and fail boot)
But both leads to same message.

After searching little bit i have found that
the ‘waiting for /dev to be fully populated’ are releated to incompatible hardware drivers.
Because the hardware drivers (e.g bluetooth graphics card) are gets installed extactly at this point.

While it’s stucks at this point my graphics card are just installs fine (I can notice that because the screen resolution changes).
And then it’s just remains there ‘waiting for /dev to be fully populated’.
I think it’s hangs there because the process animation stops.

The thing i have tried with a result was removing all boot arguments (e.g quite).
I was able to boot after removing all boot arguments,
i was also able to pass the ‘waiting for /dev to be fully populated’ message,
but again it’s just stucks at some point and then i get terminal access.
at this point i have tried to install it (anti beat me) from the terminal using ‘cli-installer’.
I have selected my already prepared volume that are ext4 formatted.
After the installation completes and then reboot, the grub menu doesn’t appears it’s just boots into windows.
I have tried to boot from the usb using ‘boot from hard drive’ option but again it’s just boots to windows.

I’m suspecting my computer usb ports, because my computer can’t run libusbk properly on Windows.
Tho linusb runs properly on xubuntu 18

I’m using anti beat me version 22 core edition amd64

That’s all i have, thank you!

[Moderator christophe]

Helpful

Up

0

::

imnull wrote:

I’m facing this issue while I’m trying to boot with anti beat me.

Hi imnull. I’m not sure what that means (unless you are posting from a phone with autocorrect/gestures). 😉

imnull wrote:

I’m using anti beat me version 22 core edition amd64

I assume here that you mean antiX core. The “core” version does not have x-windows pre-installed, so you can only boot to the command line on that one.
“Base” and “full” versions have x-windows installed, so you would go straight to the dektop session with those editions.

Regarding booting into Windows after install:
I think you may have installed the grub bootloader in the wrong place. For “mbr” (legacy) partitions, your should install to mbr (then it gives you a choice of operating systems at boot). If you boot with “uefi,” then you can install grub to the “esp” partition.

But try base or full editions, to install antiX in its full glory. 🙂

• This reply was modified 5 months, 1 week ago by christophe.

confirmed antiX frugaler, since 2019

[Member imnull]

Helpful

Up

0

::

Thanks you @christophe for reply!

Maybe you noticed it my grammar are too fair,
and no I’m not using auto correction i used ‘anti beat me’ just to avoid wordpress filters. Because i thought that antiX are a banned word.

I forgot to mention that i have installed grub on root partition (i have made some modifications to my disk so that’s reason why i chose the default option). I’m going later to install it into MBR and see if it’s works.

I thought removing all boot arguments caused me to not boot into desktop but now i understand that core version are fully for a terminal use.

Now i need to know how could i convert antiX core edition into base edtion (i would like to do that manually). at least i need to put the GENOME desktop with a file manager into it.

I need to be able to normally boot into screen which there’s a GUI so i can easily use it.

My question is which packages do i need to enable the x-windows on the core edition of antiX ?

[Moderator christophe]

Helpful

Up

0

::

Look at this post: https://www.antixforum.com/forums/topic/could-anyone-please-briefly-outline-process-from-sid-core-to-sid-base/#post-94643

The thread is about sid (unstable), but I use my advice on “regular” antiX core.

confirmed antiX frugaler, since 2019

[Member imnull]

Helpful

Up

0

::

After trying each boot argument i found the argument which caues to not boot.
The argument ‘spalsh=v’ is the one which causes my system to hang at:
‘waiting for /dev to be fully populated’

So rather than removing all boot arguments i have just removed the splash argument.

To make idea clear:
i have change this ‘quite splash=v disable=lx’ to this ‘quite disable=lx’
And now I’m able to boot without any issues.

@christophe
I have check your post and that’s what I’m exactly trying to do.
I’m trying to install the minimal version of antiX (which is the core edition) + desktop manager (i don’t want to use library office or even firefox).
I was like to install GNOME desktop because i like their design, but i really don’t mind to use any other desktop manager.
I have read that GNOME requires more RAM to run and that will enforce the system to spend more device resources (GNOME are not recommended for old devices).

Now what I’m trying to do is, to install the minimal desktop manager that are suggested by @christophe
But the problem is my computer are always offline and it’s hard to get it connected to the internet.
So there’s two options that I’m thinking about.

– First option is to download all packages from a online computer, move it to usb, and finally install these packages on the offline computer.

– Extract the required libs and packages (minimal desktop manager) from the full version of antix then i copy it manaully to the core version.
I know somebody will ask why you like to complicate it?
And the answer is i have two images of antiX one are core edition v22 (this one are not checksum mismatched) and the other one are antiX full v22 this one are checksum mismatched (maybe corrupted ?).
However i can still extract all files from the mismatched one and winrar doesn’t throws me any error.

The last thing i want to see is that i have installed the core version into my hard disk. I have also installed grub into MBR partition
Now i have grub menu and i can swap between the core version and the Windows 7.
But i would like to mention that the gradient background in grub makes it hard to see grub options from my computer screen.
I think the black background will be much better on it.
I have check the glibc version using ‘ldd –version’
and it’s glibc 2.31 i have expected the glibc version to be the latest one which is 2.36
How can i upgrade glibc version but in offline mode ?

Sorry for long write…
Thank you!

[Moderator christophe]

Helpful

Up

1

::

I have done this trick to change the grub image. It’s a “cheap hack” but it works:
The grub image is /usr/share/wallpaper/grub/back.png

I’ve had good results simply substituting a different image (named back.png) in its place. I replaced it with an image of a plain dark blue color instead, on my recent antiX core build.

After you switch the image, run
sudo update-grub

Then on next boot, grub should use your new image. 🙂

confirmed antiX frugaler, since 2019

[Member techore]

Helpful

Up

2

::

imnull wrote:

The argument ‘spalsh=v’ is the one which causes my system to hang at:
‘waiting for /dev to be fully populated’

+1

I have this same issue on two or three computers in my household. My resolution was to do the same and remove the splash parameter then save the change on the antiX usb install media. As far as I can tell, splash is eye candy and serves no useful purpose, however, someone else may know different.

[Member imnull]

Helpful

Up

0

::

@christophe
Thanks you your trick has worked perfectly!

I have done it like this:
# First remove the background
mv /usr/share/wallpaper/grub/back.png /usr/share/wallpaper/grub/back.png.bak
# Then update grub
sudo update-grub

Now my grub background are black from all edges and blue in the center and that’s are better.

• This reply was modified 5 months, 1 week ago by imnull.

[Author]

Posts