Blank & wipe the disk
reboot the machine
check after REBOOT
if it was really done
start the installer again
chose 'Automatic' when it comes to this decision to make
report
AH, forgot:
check the dam bios for
AHCI mode (should be selected!) (if available in your bios)
there can be different things, the first is to know if nvidia compiles successfully on your side and if is the correct driver, this is simple to know by looking at the "suggested" version of the driver and verifying that it doesn't fails (message shown) when installing it
the second possible problem would be on that case that you have a wrong configuration to use for xorg, maybe the one shipped by default is not good for you (or it changed in these new versions of elive)
what i suggest you to better test the issue, is to boot in the "console mode" (since you need to select the Privative Drivers menu option, you can do that by just pressing TAB and adding the parameter: nox11autologin) - after to have boot, you should probably see a message about "how to install nvidia manually", with a very powerful tool in Elive where you can try as much times as you wish installing / uninstalling the nvidia drivers (without messing up your system with them):
~ ❯❯❯ sudo nvidia-privative-drivers-install
I: No nvidia graphic cards found on this machine
~ ❯❯❯ sudo nvidia-privative-drivers-install -h
Usage: nvidia-privative-drivers-install [options]
-a: auto install
-d: detect only (return true or false if we have nvidia or not)
-l: live mode (don't pre-download packages, pre-ask if want to install, more interactive)
-f: force install (if no nvidia cards are found)
-q: quiet mode
-h: help usage
-c: check only (tell which version of the drivers we need)
-t: test driver only (if the driver is correctly installed and working)
-m: model (version of drivers) to use
- like: current, legacy-304xx, legacy-173xx, legacy-96xx
-u: uninstall drivers
-v: verbose mode
~ ❯❯❯
after to play by installing / uninstalling the driver you can just try "startx" to see if launches the graphical system, and / or returning to the console for (change xorg conf maybe?) and trying again startx
you are right LOL I just rebooted my 2 laptop and I don't have it anymore
Me I ran your command, next time I saw or invoked the startup song window manually, the config did worked / was retained(saved) properly
yes, that was the problem, something creates the dir .config/elive as root, and since its owned by root, everything wanted to be used/saved/created on this place fails (a lot of elive tools that saves configurations, like the songs, or multiscreens)
now i need to find, WHAT in all the massive tools around, is creating this dir from root and why in the home of the user
you said it worked lol (note: after reboot you will be asked AGAIN for the song setting, but thats because this time is going to save the configuration, so will not happen after the 2nd reboot)
@Rebel450 by doing -nothing- your system will be upgraded (elive-upgrader takes care of that 2 times per month), you can also run "apug" yourself and elive-upgrader will take care only about possible fixes needed
by other side, by only updating packages your system would not include all the possible fixes, 3.7.0 was a release with a good amount of things to fix, and some of them needs to be set from the installer for example (like the sudo configurations that enabled the brightness buttons to work)
also: by just reinstalling can include fixes/improvements (installer always updated), but some of them cannot be included; on this case, same example about the brightness buttons, it requires an updated version of elive-tools inside the system where it is installing, and this can only happen from a newer version, let's say 3.7.1 on this case. So the installer is updated but things from inside the system is not
in short, always upgrade your system to keep it updated with fixes, but to make sure you have all the functionalities / features / fixes / improvements, reinstall from time to time (migration mode should automate everything so you won't have to deal with new setups / user configurations)