I have debian wheezy amd64 and I am sure, that older liquorix packages would work on my system without messing with gcc/glibc.

I found as the oldest these:


I need headers to rebuild some kernel modules and I am unable to - dkms failed on nvidia driver:


Is there some place where I can go to? If not...why?
Back to top

smxi offers the last of each major liquorix kernel series back to I think 2.6.32. The installer has both headers and image files in it, because you should in general always install the headers, for the reason you show clearly here, you never know when headers will be needed, and it's often hard to find old kernel headers that match your kernel, which is why smxi always in all cases installs the image/headers both, including for the archived kernels.

I only offer this via smxi as a service to smxi users.

It's in alternate-kernel-install section of smxi kernel section.

You can actually run this in X, if you use the -G option for smxi.

Only the last liquorix kernel for each major kernel version are stored, but since that's the one you should be using anyway due to patches and fixes, that's not a real drawback.

Note that the last liquorix kernel for a major version, say 3.9, might not correspond to the last actual kernel released because damentz doesn't always release them, and never, almost, for kernels more than 2 major versions back, so it's whatever it was at that point.

I do not track which liquorix kernels are compatible with which debian stable release, or ubuntu lts release, I leave that up to users to discover for themselves, which is an easy process, takes about 5 minutes per kernel, depending on your system/network download speed, if the install fails, it didn't work, if it worked, it worked.

I don't track dkms issues because I don't care about them, I prefer more reliable methods that have worked for many years, so I have nothing to say about how a non debian kernel will work with a debian dkms package, but I can tell you that each nvidia driver supports specific linux kernels, period, which is the problem with using non debian kernels with debian dkms nvidia, there's no guarantee they will work together unless the kernel major version is the same in both cases.
Back to top

Many thanks for so detailed answer :)

But still before I end up in trying with smxi, which I never used before, I must ask again. There is no place with old packages than those in here: liquorix.net/debian/ ?

I really looked for some, but I have to resolve in writing this topic.

I understand that there can be failures with nvidia dkms, so I would be forced to trying a few version builds, but I just didn't find any.

And I guess that at least some close to my current distro-default 3.2.0-4-amd64 would satisfy dependencies and nvidia dkms.

P.S. I am not from english speaking country, so, pls, excuse me for bad grammer :)
Back to top

I, that is, smxi, is the place old liquorix kernels are offerered/archived. Obviously anyone is free to do the job and also create their own archives, but I'm the person who actually did it over years. the smxi archived kernel versions contain an installer etc to make the process failry smooth. The main issue is gcc version re older systems and liquorix kernels.

I do this because between 100 and 400 people a month seem to find this a valuable option, if nobody used it, I'd probably stop doing it, but actually more people have used this lately, so I take that as a vote for the feature in smxi.

Damentz is cool and maintains up to three branches, past, main, and future, but those only cover 2 kernels usually, future is not often used, but there's no reason to expect him to maintain endless old branches, I don't do that, I just take his last present/past kernel released for each major version and create the zip installer file.

As self defense, however, smxi does not support ubuntu, otherwise I'd lose all my time and just see my frustration level skyrocket, ie, no fun. smxi is for debian and true debian derived distro users, period. True debian means quite simply that you can run, always, apt-get dist-upgrade and have the upgrade more or less work, ie, not ubuntu.

sgfxi does support mint/ubuntu at this point.

your english is fine, no problems.

this is what smxi currently offers:


on my system, though each user's system will show slightly different distro kernel options depending on what sources they have enabled. And my memory worked, 2.6.32 is actually the oldest, though I will probably remove most of the 2.6 ones soon, leaving just a few. As you can see, I switched to even numbered releases to keep the offerings fairly simple, except for the latest ones.

Keep in mind, it takes far less time to install smxi and the kernel than it took me to type this.
Back to top

Many thanks again :) and for effort and your time - I start to read smxi website to know something about it ;)
Back to top

smxi.org/docs/navigation.htm

that shows the basic structure, but: smxi -G
by passes the beginning sections, the first kernel install/upgrade sections, and takes you to the main options section.
Back to top

Hi, so I just installed and tried smxi and when I go through those menus and options I don't see anywhere similar to yours:


This is where I allways end up:



Can You help me? I just want to get to the menu with liquorix kernels and test the most up-to-date which would be working.
Back to top

You're in the wrong section, Advanced Kernel Options, that does other stuff.

All you have to do is go back one level then pick the right option. Or, rather, restart smxi, go to kernel options, then pick the right option.
Back to top

I am so sorry, I am ashamed....I just should go to sleep yesterday :)

Thank You very much ;)


So now when I pick any kernel I keep getting this errors (snippet from smxi.log):


Is that some kind of bug, or I am doing something wrong again? Script sm-lib-misc-tweaks definitively exist and it is in same place as others (/usr/local/bin) - I have done first install option from website.

And from that log it seems, that installation finds one, but compares script's versions and fail.
Back to top

I've never seen this issue. Show the results of this:

echo $PATH
for both regular user and root.

that's the only thing I can think of, that your system doesn't have /usr/local/bin in PATH, though I don't see why that would matter.

it could be a wget failure, possibly, which means a networking failure usually, or an isp failure, it's hard to say, but since the compare numbers function shows the numbers equal, smxi would not have tried to download a new version of the lib file.

There's almost certainly something different in your system, something done that you have forgotten or didn't realize would cause issues, that's my first guess.

Also paste the entire smxi log file from this session to pastebin.com

I'm also assuming you are running smxi as root, not using sudo, which should exit with error. sudo is another area where writes can fail by the way, which is why smxi now doesn't allow it.
Back to top