MX Linux Forum

Well, this is getting silly interesting. I have just changed monitors and plugged in a different (but equally ancient!) monitor display screen.... Yay!!! Not only do SolydX and Mint boot up perfectly - but MX16.1 boots up too, and I have the normal screen display in front of me. No more black screen...

Well my hopes were raised, only to be dashed... I tried adding xdriver=vesa to the relevant line in the Grub menu. No joy. It went through the boot process and ended on a black screen. Having done some forum-browsing, I tried two other variations. First I put in xforcevesa on that grub line. Same re...

Stop press: I have another update which seems to narrow the troubleshooting down considerably. It seems to be a graphics/software/driver problem. We know that the installed MX16.1, the same OS on an external drive, and any and all Live session media, won't boot up properly but end up with a black sc...

Call me stubborn, but I don't like being defeated by a machine - even an old 32-bit machine. It seems clear that there is more than one problem with the current setup. In a nutshell I can't boot up the installed MX16 properly. At the end of the boot process it is running, but with a black screen (no...

Hey male , I'd like to think I'm not beaten yet. But I always expect some bumps in the road. My slogan is "Keep Calm and Carry On"! But I have taken a short pause, to try to figure out where we are. I seem to be in a Catch 22 situation, because the evidence suggests that there are actually two probl...

Well, male...... I have to say that advice, or set of instructions, looks a bit daunting to me. I'm not sure I understand what you are explaining in point 1. Is this a way of checking that the ISO image on the stick is not corrupted? Or is this a command that has to be executed - and if so what is i...

Well, thank you male (and earlier, timkb4cq) for all your advice. I really hate giving up, or being defeated, by a problem that - in the beginning - did not seem too difficult to solve. But this one seems to have become much more complicated than I expected. What bugs me is that we still don't seem ...

You wanted it this way to learn and I repeat, you're learning well! You're can all still install MX17... Thanks for your patience and support, male. I am learning a lot, even if I was not expecting all this. Yes indeed - I am beginning to think that installing MX17 in place of my MX16 would be a mo...

Okay.... this is getting into deeper and deeper waters. So just to be clear about what I might now try to do: we know that my MX16 won't boot up in my multiboot system so the approach we are trying is to get into MX as root via <ctrl><alt><F1> in order to update MX16 but we have now found that apt-g...

Sorry, my mistake... I did use the correct command apt-get update when in the terminal of MX. I just typed it wrongly in my post above. Just to be sure, I ran the correct command again when signed in as root in the MX terminal. It did indeed produce all the "could not resolve" and "failed to fetch" ...

MX Linux Forum

Search found 83 matches

Re: MX16.1 won't boot in a multi-boot setup

Re: MX16.1 won't boot in a multi-boot setup

Re: MX16.1 won't boot in a multi-boot setup

Re: MX16.1 won't boot in a multi-boot setup

Re: MX16.1 won't boot in a multi-boot setup

Re: MX16.1 won't boot in a multi-boot setup

Re: MX16.1 won't boot in a multi-boot setup

Re: MX16.1 won't boot in a multi-boot setup

Re: MX16.1 won't boot in a multi-boot setup

Re: MX16.1 won't boot in a multi-boot setup