Wheelerof4te wrote:You shouldn't have broken dependencies for linux-headers, dkms and glx. Some package(s), that you removed, caused them to be considered by apt for removal. What did you do before these packages started appearing there?Better yet, what does your sources.list look like?

Are you still having to use nomodeset to boot with the modesetting driver that Debian uses as default? That seems at cross-purposes, and may be why you have trouble with it. I use the xserver-xorg-video-intel "intel" driver myself with my Optimus setup. To use that, make sure that package is installed and create an /etc/X11/xorg.conf.d/20-intel.conf file with the contents:

stevepusser wrote:Are you still having to use nomodeset to boot with the modesetting driver that Debian uses as default? That seems at cross-purposes, and may be why you have trouble with it. I use the xserver-xorg-video-intel "intel" driver myself with my Optimus setup. To use that, make sure that package is installed and create an /etc/X11/xorg.conf.d/20-intel.conf file with the contents:

First I wanna mention I know realized that indeed the computer rarely boots when using nouveau.modeset=0 instead of nomodeset. Sometimes it does but it seems VERY random and rare.

Turns out, xserver-xorg-video-intel was already installed and the latest version... The file however, did not exist. So I created it and rebooted. (Using nouveau.modeset=0 still). I got to the login screen but when it was about to show the desktop it typically went black (this is what always happens if I don't use nomodeset). So I put nomodeset as boot option instead of nouveau.modeset=0 and rebooted.Now I didn't even get into X... Verbose boot stopped at a screen saying "FAILED to start Light Desktop Manager"... So to even get it booted in anyway again, after trying your fix, I had to set "nomodeset" in /etc/default/grub and also rm -rf /etc/X11/xorg.conf.d

Thanks to openSUSE for providing the build farm and hosting the repo for free! I just edit a few lines in a few files in the Liquorix debian folder, run a command to regenerate the files in /debian from the changed defines, regenerate the source files with "debuild -S -uc -us -d", upload them and it does the rest. If someone wants to do it locally, the recipe is

/debian/config/defines: change where it reads "gcc-7" to "gcc". This means it will use the default gcc for your release.

Hello guys. A quick update. I got fed up and got rid of debian. These optimus computers really are pain with linux... Anyway, I managed to get Manjaro Linux working using its architect-iso. The way I got bumblebee working on there might have worked on debian too... who knows. But I am perfectly happy with my Manjaro now so I won't switch back. It's working without problems but if anyone wanna know how I made it work it can be read here: https://forum.manjaro.org/t/cant-get-in ... =matheos96

^Glad that you solved your problem. Manjaro is good for people who need quick Arch and AUR features. In my experience, it is a very buggy, duct-tape patched version of Arch that is seriously understaffed for what it tries to do.