Linux Mint KDE 18.2
Linux Manjaro 17.2 XFCE
The laptop is a Core i7 with a Nvidia 850m and 12Gb of RAM.
Well, this is not just a simple question,
It’s actually quite a story.
I really need some advanced technical advice and assistance.
well, where to start… please bear this with me.
Ok, so I have a laptop that came with Windows 8.1 so I installed Linux Mint and I could boot both OS, just fine. I had to sort my way through all the cumbersome uEFI setup, and I think everything was fine because I could use both Windows 8.1 and Linux mint without much trouble.
Everything changed when I added Linux Manjaro to the already complicated mix.
The only way to make the laptop boot into any other thing than Windows 8.1 was pressing F9 at startup, so the uEFI system would show a list with boot options. That has always been that way.
But after installing Manjaro, I ended up with two Grubs! Yes! that menu shows three entries, the first one boots windows, the second one opens Linux Mint’s Grub (wich also includes “linux mint advanced options”)
and now I have this third Manjaro Grub which shows this list:
*Advanced options for Manjaro
*Advanced options for Linux Mint
Now, what gives? It shouldn’t be a problem, should it?
So I decided to customize the Manjaro Grub, and everything went just fine, it looks cool with the modified theme I choose. So I decided to customize the other Grub.
So I end up with two grubs, each one looks beautiful with it’s own different theme with different background each and set of icons each (after running the grub update command in linux mint, it seems manjaro was detected too so now both Grubs have a very similar boot options list)
Ok, so everything looks good, everything seems to be fine. I can boot the three operating systems just fine, Windows boots and works fine, Linux Mint appears to be running fine too, and Manjaro, well, since I had never used it before, all I can say is that I’m still learning lots of things, but it boots just fine too. I would have expected a “Kernel panic” because that’s what I heard that could happen, but everything seems just fine!
Even though everything seems fine, nothing is actually allright under the hood. One day I selected the Manjaro Grub, but instead of selecting the manjaro option I selected the mint option. Everything seemed fine. Now I don’t remember exactly why but after some reboots installing things in both Manjaro and Mint, something wrong began to reveal itself.
This laptop is somewhat new and both Mint and Manjaro are fairly fresh installs, it has been just about some weeks for the first and just about some days for the second. However, I know my linux mint, I have been using it for a much longer time in my older desktop, and I also had mint installed in this laptop but for other reasons I ended up reinstalling it fresh.
I began to get very strange problems (is this thing haunted?)
I think it started when I installed CdEmu at linux Mint. I have CdEmu working just fine in my desktop PC, but after installing it in the laptop and rebooting (I think that time I choose Mint within Manjaro’s Grub)
I got a very cryptical error. It was something like
:: Loading vhba and loop modules [BUSY]
FATAL: Module vhba not found. [FAIL]
:: Waiting for /dev/vhba_ctl [FAIL]
:: Starting cdemud [FAIL]
I followed the instructions here
But the problem didn’t solve. However, after rebooting with the right option (Mint within Mint’s Grub)
it seemed to solve itself!
After that, for some reason I booted manjaro, installed Cdemu there, nothing fancy, it seemed to be OK. Then Mint again (I don’t remember which Grub I used) but my Mint’s KDE graphics looked strange, Cairo-dock had a black border which I had usually seen when virtualbox guest utils weren’t installed, but this is a physical machine! Oh, true, it asked for the compositor to become activated. How strange! Why did it deactivate itself? That kind of thing didn’t happen to me before! After digging in the options I found out that I had to manually activate the desktop composition because somehow something turned it off after considering that it couldn’t run OpenGl.
After turning it on, everything seemed fine.
Again, everything seemed to be just making sure I boot the right distro with it’s native Grub. But things started to show that something may already be damaged under the hood.
When using PlayOnLinux I restored some backed up virtual drives to find that they don’t work well. I really don’t know what is wrong because I’m doing the same kind of things I usually do and usually work for me in my older desktop with all this! All I get is all sorts of errors! Just like CdEmu, lots of already installed libraries are shown as inaccesible by PlayOnLinux in the logs.
I tried reinstalling PlayOnLinux, but that didn’t help.
Thanks for reading until here and please help me.Maybe I will have to give some more specific info. but this is already a wall of text.
Maybe I should start from scratch?