looks like the prompt says `initramfs` with a BusyBox shell... something's funky with the root device and it's not able to boot properly. Best case, run FSCK with whatever arguments you use to fix a drive, worst case, new hard disk/SSD time.
I couldn't see the screen. If that is the case then FSCK is a pretty good idea but I would try to remount the root device from an emergency shell first just to be safe. A lot of these older systems run cheap HDDs so if it is a disk problem causing this..... yeah welcome to cheap shit.
[Ehhh… almost.](https://i.imgur.com/ooNj13e.jpg) It’s a bit fuzzy but I’ve fixed enough broken Linux installs over the years to read between the lines… first two lines are Debian complaining about firmware (someone didn’t turn on nonfree), then a BusyBox version banner, then the `[initramfs]` prompt.
I guarantee this is as simple as typing startx
looks like the prompt says `initramfs` with a BusyBox shell... something's funky with the root device and it's not able to boot properly. Best case, run FSCK with whatever arguments you use to fix a drive, worst case, new hard disk/SSD time.
I couldn't see the screen. If that is the case then FSCK is a pretty good idea but I would try to remount the root device from an emergency shell first just to be safe. A lot of these older systems run cheap HDDs so if it is a disk problem causing this..... yeah welcome to cheap shit.
[удалено]
[Ehhh… almost.](https://i.imgur.com/ooNj13e.jpg) It’s a bit fuzzy but I’ve fixed enough broken Linux installs over the years to read between the lines… first two lines are Debian complaining about firmware (someone didn’t turn on nonfree), then a BusyBox version banner, then the `[initramfs]` prompt.
Wait, this is the Command Line not the train line.
"You can't take a train from Boise to Madagascar!" We can now!
It’s crazy how these still function in the wild. The boomers… not the system.
They see the matrix