Liquorix + Debian stable tip

mrneilypops · 2017-06-09 18:04:55

I have often used Liquorix kernel on testing/sid on my own 'distrolettes' and others...
With stretch about to be released;
https://lists.debian.org/debian-devel-a … 00002.html
and with this in mind... I once asked the question to the Liquorix dev about Liquorix+Debian stable;

liquorix dev wrote:

the liquorix kernel is installable on a 'new' stable for a while because of the gcc version used to build liquorix happens to be still available in the new stable.
As soon as testing/sid gcc version moves on, and liquorix now runs with a newer gcc than by now older but still current stable runs, you can't install any new kernel modules that require that gcc version, ie, the ilquorix version.

http://techpatterns.com/forums/about248 … highlight=

I am not really sure if this will cause issues short or long term when stretch is stable...but just for general info

...unless, of course, you plan to stick with 'testing' or sid...

Hope this tip is some use to the commnunity.
I know that some use Liquorix + Debian 'stable' without issues...but maybe best to take heed of the Liquorix dev.

Head_on_a_Stick · 2017-06-09 18:13:01

Thanks for the tip, this issue did come up with jessie when testing/unstable switched to gcc 5 a while ago.

I think @stevep has some jessie-compatible Liquorix kernel versions (plus the essential headers, ofc) in his OBS repository.

Also, the Liquorix kernel could still be used after a gcc version bump as long as no custom modules (eg, VirtualBox, Broadcom, NVIDIA) are needed.

Sector11 · 2017-06-09 18:53:41

I ran #! -> SID a while back and started with the liquorix kernal. Can't remember why but I went back to the regular #! (Debian) kernel before I borked the whole thing with a "stupid human, typical s11, error - tpyo"

Thank's for the tip.

stevep · 2017-06-10 02:27:32

Yes, I have a subproject with various backported versions of the kernel from 4.8 to 4.11, along with some patched drivers that will build on the 4.11 kernel:

https://build.opensuse.org/project/show … r:codelite

I added it to an existing codelite repo, since the kernel doesn't generate any arch-independent package names, and I need that for the automatic instructions to work--so just follow the instructions to add the repo for the codelite package.

kols · 2017-07-16 21:47:42

Hi!

I remember using Liquourix with Crunchbang a few years back. How exactly does one install on Stable?

I looked up the installation guide on the Liqourix website, which says to add this:

# /etc/apt/sources.list.d/liquorix.list
deb http://liquorix.net/debian sid main
deb-src http://liquorix.net/debian sid main

Apparently, the "main" way of installing is on Sid, however I'm using Stable. The features for Liqourix seem nice (in short - the performance seems to be enhanced), so I'd like to give it a go again. Could it be as simple as using "...stable main" instead of "...sid main" in liqourix.list?

If it's not possible - how will using the sid kernel affect my install, seeing as the rest of it will be from stable?

I'm not even sure why I'd need this, but hey, it just installs a kernel alongside the regular 3.16 kernel. It's cool to test things;)

Cheers!

damo · 2017-07-16 22:23:07

Liquorix + Debian stable tip

kols · 2017-07-16 22:29:09

damo wrote:

Liquorix + Debian stable tip

Hehe, reading comprehension is overrated... So to conclude, the gcc version is higher in Sid than it is in Stable, thus using Liquorix with Stable is not recommended.

damo · 2017-07-16 22:56:03

Well you could try one of @stevep's builds above. Don't forget that YMMV, and anyway you get to keep the pieces ]:D

Head_on_a_Stick · 2017-07-17 06:47:35

I think you can still use the kernel as long as you don't need the headers but I really would advise sticking with the stock kernel unless you have a problem with hardware support.

stevep · 2017-07-17 22:08:06

My backports of the Liquorix kernel are fully compatible with Debian Jessie, but the new kernel can break some Jessie out-of-tree driver packages. I have updated/patched versions of the nvidia-driver, fglrx-driver, ndiswrapper, and broadcom-sta-dkms packages in the same repo that will build with the 4.11 kernel. If you use virtualbox, Jessie's is too old to build; you'll have to use the new version direct from Oracle.

Head_on_a_Stick · 2017-07-18 06:18:30

stevep wrote:

the new kernel can break

That's certainly my experience 8.(

DeepDayze · 2017-07-18 11:17:33

stevep wrote:

My backports of the Liquorix kernel are fully compatible with Debian Jessie, but the new kernel can break some Jessie out-of-tree driver packages. I have updated/patched versions of the nvidia-driver, fglrx-driver, ndiswrapper, and broadcom-sta-dkms packages in the same repo that will build with the 4.11 kernel. If you use virtualbox, Jessie's is too old to build; you'll have to use the new version direct from Oracle.

The Jessie version of VirtualBox from Oracle works fine for me on BL Hydrogen.

#1 2017-06-09 18:04:55

Liquorix + Debian stable tip

#2 2017-06-09 18:13:01

Re: Liquorix + Debian stable tip

#3 2017-06-09 18:53:41

Re: Liquorix + Debian stable tip

#4 2017-06-10 02:27:32

Re: Liquorix + Debian stable tip

#5 2017-07-16 21:47:42

Re: Liquorix + Debian stable tip

#6 2017-07-16 22:23:07

Re: Liquorix + Debian stable tip

#7 2017-07-16 22:29:09

Re: Liquorix + Debian stable tip

#8 2017-07-16 22:56:03

Re: Liquorix + Debian stable tip

#9 2017-07-17 06:47:35

Re: Liquorix + Debian stable tip

#10 2017-07-17 22:08:06

Re: Liquorix + Debian stable tip

#11 2017-07-18 06:18:30

Re: Liquorix + Debian stable tip

#12 2017-07-18 11:17:33

Re: Liquorix + Debian stable tip

Board footer