Sgfxi fails on Liquorix past 3.8-10
Mono
Status: Contributor
Joined: 21 Jun 2012
Posts: 115
Reply Quote
On all the Liquorix kernels past 3.8-10 the nVidia driver fails to compile citing unmet dependencies.

:: Code ::
$ inxi -bxx
System:    Host: ronin Kernel: 3.8-10.dmz.1-liquorix-amd64 x86_64 (64 bit, gcc: 4.7.2)
           Desktop: Cinnamon 1.8.8 (Gtk 3.4.2) dm: mdm Distro: Linux Mint Debian Edition
Machine:   Mobo: ASUSTeK model: M5A99FX PRO R2.0 version: Rev 1.xx Bios: American Megatrends version: 0803 date: 08/15/2012
CPU:       Octa core AMD FX-8350 Eight-Core (-MCP-) clocked at 4008.326 MHz
Graphics:  Card: NVIDIA G73 [GeForce 7600 GS] bus-ID: 01:00.0 chip-ID: 10de:0392
           X.Org: 1.12.4 driver: nvidia Resolution: 1280x960@60.0hz
           GLX Renderer: GeForce 7600 GS/PCIe/SSE2 GLX Version: 2.1.2 NVIDIA 304.88 Direct Rendering: Yes
Network:   Card: Realtek RTL8111/8168B PCI Express Gigabit Ethernet controller
           driver: r8169 ver: 2.3LK-NAPI port: a000 bus-ID: 0a:00.0 chip-ID: 10ec:8168
Drives:    HDD Total Size: 164.2GB (41.0% used)
Info:      Processes: 329 Uptime: 10:13 Memory: 4088.6/7898.0MB Runlevel: 2 Gcc sys: 4.7.2 alt: 4.4/4.6
           Client: Shell (bash 4.2.36 running in gnome-terminal) inxi: 1.8.38


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:

:: Code ::
$ sudo dpkg -i '/home/keantoken/Setup/Packages/libc6_2.17-3_amd64.deb'
dpkg: regarding .../libc6_2.17-3_amd64.deb containing libc6:amd64:
 libc6:amd64 breaks locales (<< 2.17)
  locales (version 2.13-37) is present and installed.

dpkg: error processing /home/keantoken/Setup/Packages/libc6_2.17-3_amd64.deb (--install):
 installing libc6:amd64 would break locales, and
 deconfiguration is not permitted (--auto-deconfigure might help)
Errors were encountered while processing:
 /home/keantoken/Setup/Packages/libc6_2.17-3_amd64.deb


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

Thanks
Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 4076
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
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.

:: Code ::
inxi -bxx
System:    Host: yawn Kernel: 3.9-5.dmz.1-liquorix-686 i686 (32 bit, gcc: 4.7.3)
           Desktop: KDE 4.8.4 (Qt 4.8.2) dm: kdm Distro: sidux-20070102-d:1
Machine:   Mobo: ASRock model: A770DE+ Bios: American Megatrends version: P1.70 date: 09/07/2010
CPU:       Dual core AMD Athlon 64 X2 5000+ (-MCP-) clocked at 2600.00 MHz
Graphics:  Card: NVIDIA GT218 [GeForce 210] bus-ID: 02:00.0 chip-ID: 10de:0a65
           X.Org: 1.12.4 driver: nvidia Resolution: 1280x1024@75.0hz, 1280x1024@60.0hz
           GLX Renderer: GeForce 210/PCIe/SSE2/3DNOW! GLX Version: 3.3.0 NVIDIA 319.23 Direct Rendering: Yes
Network:   Card: Intel 82574L Gigabit Network Connection
           driver: e1000e ver: 2.2.14-k port: c800 bus-ID: 01:00.0 chip-ID: 8086:10d3
Drives:    HDD Total Size: 810.2GB (76.8% used)
Info:      Processes: 252 Uptime: 15 min Memory: 2595.5/6079.1MB Runlevel: 3 Gcc sys: 4.7.2 alt: 4.0/4.2/4.4/4.5/4.6
           Client: Shell (bash 4.2.37 running in konsole) inxi: 1.9.7


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.

:: Code ::
smxi -v
smxi :: Version: 8.38.44 :: Last Updated: May 28 2013
------------------------------------------------------------------
Your installed version of Debian Sid is: sidux-20070102-d:1
Operating system: 32 bit
Your CPU is:  AMD Athlon(tm) 64 X2 Dual Core Processor 5000+
File System Information:
/  -  Type: rootfs Size: 13G Used: 12G ( 94% ) Free: 783M
/  -  Type: ext3 Size: 13G Used: 12G ( 94% ) Free: 783M
/home  -  Type: ext3 Size: 20G Used: 16G ( 81% ) Free: 3.8G
------------------------------------------------------------------
Your current kernel version is:       3.9-5.dmz.1-liquorix-686
------------------------------------------------------------------
Last apt-get package database update: 2013-06-12-09:49
Last apt-get package install or upgrade: 2013-06-12-09:49
Last use of smxi: 2013-06-12-09:45
Last dist-upgrade using smxi: 2013-03-09-21:10

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
Mono
Status: Contributor
Joined: 21 Jun 2012
Posts: 115
Reply Quote
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
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 4076
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
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
Display posts from previous:   

All times are GMT - 8 Hours