On all the Liquorix kernels past 3.8-10 the nVidia driver fails to compile citing unmet dependencies.



When I try to run sgfxi on the other kernels it tells me something along the lines of:

...lib6.so.6: version GLIBC_2.14 not found

The same applies to the WINE in the Liquorix repositories. However if I try to install version 2.17 from a .deb file, Gdebi complains about locales, which is something I have not learned about:



Maybe my LMDE is not up to date enough? What do you suggest?

Thanks
Back to top

My honest first suggestion is to stop using LMDE. When an allegedly 'debian' distribution breaks such a core dependency, I see little reason to continue using it. I knew they'd have problems when they started doing their semi frozen monthly or whatever releases, that was one of the worst ideas I've ever seen anyone come up with. Not a huge suprise that the main creator of LMDE, ikey, decided to leave and form SolusOS. And yes, that's an endorsement, assuming you want a stable based distribution. If more rolling is desired, try siduction. If you want Debian Testing then use debian testing or AntiX, which I believe is testing based.



For what it's worth, I've seen precisely two issue reports from 3.9/319 nvidia latest here, and both are from LMDE users. Also, after starting to read your report, before I saw your inxi output, I said to myself, I bet he's using LMDE.

Although I still have the old sidux type /etc/sidux-version file from my sidux dev days, my system is actually basically Debian Sid, updated infrequently.


as you can see, I haven't done a full upgrade for 3 months. But I am running debian from debian repositories, so when core packages upgrade as with for example kernel installs, all the packages match, because this is Debian, and that's how Debian works.
Back to top

Thanks for the info.

What do you think of this:

scottlinux.com/2013/05/14/convert-lmde-to-debian-wheezy/

That was in may and this is june, so maybe I'm just in time? And, should I use smxi during and after this?
Back to top

seems reasonable, though these things are not theoretical, if the core mint packages can be cleanly uninstalled, then it should be fine.

I haven't tested it or heard of it, but that's standard debian methods so there's no real technical thing, you simply don't always know what happens when you remove packages, or if mint packages will conflict, for example, lmde had a terrible habit of including ubuntu mint packages in lmde, which is a really bad idea in general.

It will probably boot after the change I'd guess so you can fix any glitches.

Do NOT ignore any apt error messages in the process, do not go to next step until all reported errors are corrected.
Back to top