Live-usb only boots with failsafe, crashes at "waiting /dev ... populated" [Solved]

[DukeComposed]

Forgot to mention that I've already done this. But since I have no way to install a diff. kernel due to no ethernet
What could I do to get the antix kernel on it?

It's pretty tough to get a new kernel on a machine when you have no way of downloading new kernels to it. You could try downloading the kernel debs on an identical machine with network connectivity with "apt-get install --download-only" and then manually copying over the .deb files and installing them by hand onto the target system with dpkg.

[kmiles]

I've only got one of this machine. I'll take my chances on the params first before trying the others' suggestions or more drastic measures. Looks like a bit of a hassle to do unless one has identical company machines.

[Kermit the Frog]

@kmiles

Just boot with failsafe then go on installation. (Yes, just do it.).

[DukeComposed]

I've only got one of this machine.
Looks like a bit of a hassle to do unless one has identical company machines.

They don't have to be completely identical devices of the same make and model, but you want to make sure they're both on the same architecture and running the same version of the OS. Even a USB live session is sufficient for contacting the right repos and getting the .deb files you need.

[kmiles]

@kmiles
Just boot with failsafe then go on installation. (Yes, just do it.).

Yes, I have mentioned that I did this already, and since overwritten with win10.

It seems like it really should be using the "radeon" driver, but you're saying it might not be working.
Have you tried forcing that in the boot options on the Live media?

@Stevo @j2mcgreg @fehlix @dolphin_oracle
I got the antix kernel on the usb with a snapshot of my current system booted with it, same thing.
When booting with no failsaife, I see that it finds the radeon KMS video module and crashes at the same point with it.
tried the other failsafe options. really only boots if using no vid drivers(or the radeon one).

also, it happens regardless of whether the HDD&SSD are connected or not.

could the driver itself cause issues? the cpu being unsupported or something?

[kmiles]

Once I install(failsafe) mx on the machine and get a spare ethernet cable, what would be my next step?
Do all the updates? It seems to me that if this old machine can't even use the radeon driver, a fully updated system is of no help.
What else would you guys like me to try?

[Kermit the Frog]

Do this after first reboot (on the installed system):

Code: Select all

sudo rm /etc/X11/xorg.conf

Then reboot once more.


Cause that file (which will be generated due to failsafe, will still be there especially if you select to save the changes during installation) will be forcing the xorg to use vesa driver instead of Radeon.

[kmiles]

Hi, I'm back. I'm currently on Linux Lite on the problem system(with radeon driver, checked in inxi) as I write this.

I got around to trying again recently and here's what I've done:

- I remembered that I could just use my phone connected through usb to get net access so I proceeded to boot ventoy into MX23.5(xfce) with failsafe nomodeset and installed to the HDD then booted from it(still needs nomodeset) and did all updates.

- I tried both antix v4.19(as instructed by @j2mcgreg) and v4.9 with and without 'acpi=off'.

- after setting antix v4.19 as default in boot options, I rm'ed xorg.conf (as instructed by @Kermit the Frog) then removed nomodeset in boot options, then restarted, still only boots to mx login in tty.

it might be the radeon driver itself (or something with it) is the issue as @Stevo and @dolphin_oracle suggested.
What should I type in boot options to force the radeon driver to load? and do you need any other info? (like the output of inxi when it boots into tty login)

[j2mcgreg]

From here:
https://www.reddit.com/r/debian/comment ... 8hme33_v2/
and here:
https://forum-en.msi.com/index.php?thre ... ly.406555/
It appears that your motherboard is incompatible with Debian 12.

[kmiles]

ah, so that's why I was having similar issues when i tried mint last year.

it seems to me that if removing read-only in boot params allows the OS to boot, then couldn't I just remove read-only, allow the system to make the changes that makes it boot and make it persistent, then restart (which brings back the read-only as I removed it only during kernel selection)?

or am I understanding this wrong?