@Jens Glathe
problem is official Ubuntu Mainline Kernel from 5.15.7 change depends package
from libssl1 to libssl3...
Package: linux-headers-5.15.6-051506-generic
Depends: linux-headers-5.15.6-051506, libc6 (>= 2.34), libelf1 (>= 0.142),
libssl1.1 (>= 1.1.0), zlib1g (>= 1:1.2.3.3)
Package:
@k3dar7 now... I did some search on what installs libssl3.
$ ldconfig -p | grep ssl3
libssl3.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libssl3.so
$ apt-file search libssl3.so
firefox: /usr/lib/firefox/libssl3.so
libnss3: /usr/lib/x86_64-linux-gnu/libssl3.so
thunderbird:
@k3dar7 interesting, had no error yesterday on building 5.15.7 Need to
investigate.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926938
Title:
Recent mainline packages are built with Hirsuite
is there really any reason to add in 5.15.7 dependence on libssl3
package, when it is only in unreleased 22.04??
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926938
Title:
Recent mainline
@roguescholar
is "nice" change info on wiki, but really, why is not supported last LTS
release? need as mainly because st*pid blocking hibernation with enabled secure
boot in stock kernel...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
> I believe we can close this bug.
The change to the wiki is welcome, since it now reflects the current
situation.
However, in my opinion, the real problem uncovered here has not been
addressed:
Ubuntu should provide mainline kernels built with the latest LTS
toolchain alongside the current one
I've updated the Wiki page with my best approximation of the consensus
which developed here. If it meets with the satisfaction of all concerned
parties, I believe we can close this bug.
https://wiki.ubuntu.com/Kernel/MainlineBuilds#Mainline_kernel_build_toolchain
** Changed in: linux (Ubuntu)
Hmm. Got 5.14.9 running directly from the
https://kernel.ubuntu.com/~kernel-ppa/mainline/ repository. Works with
nvidia driver 4.70 on Mint 20.2 :)
build sequence:
- checkout cod/mainline/v5.14.9 from
git://git.launchpad.net/~ubuntu-kernel-test/ubuntu/+source/linux/+git/mainline-crack
- install
@DanglingPointer (ferncasado)
gonna try #74. i really do want to understand how all this works. this
might be the most reliable option since even ppa's break.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@k3dar7: Thanks a lot for your valuable help!
Following script works for me on Ubuntu 21.04 (64-bit):
sudo wget https://raw.githubusercontent.com/k3dar/kumk/main/kumk -O
/usr/local/bin/kumk
sudo chmod a+x /usr/local/bin/kumk
sudo kumk install latest
--
You received this bug notification
@2021yunotcompile
kumk has been used workaround way only on system with libc6 <2.33...
but i changed this in just updated kumk version,
now is used if kernel package "need" higher libc6 than is installed...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@k3dar7
i did this option -> 4. sudo ./kumk install 5.14.4
this is popping up now:
$ dpkg: dependency problems prevent configuration of
linux-headers-5.14.4-051404-generic:
linux-headers-5.14.4-051404-generic depends on libc6 (>= 2.34); however:
Version of libc6:amd64 on system is
@2021yunotcompile
you missed:
3b. sudo cp -a kumk /usr/local/bin/
or without "installing"
4. sudo ./kumk install 5.14.4
or completely different way for "installing"
1. sudo wget https://raw.githubusercontent.com/k3dar/kumk/main/kumk -O
/usr/local/bin/kumk
2. sudo chmod a+x /usr/local/bin/kumk
@k3dar7 i tried using your tool however it keeps saying command not
found.
steps:
1. dl zip
2. extract
3. cd to folder (kumk-main)
4. sudo kumk install 5.14.4
no dice. am I doing something really dumb?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@tuxinvader @k3dar7 many thanks for the replies.
Yes, I installed packages from mainline. Sorry, I thought this bug
report is for mainline packages.
Now I did see your PPA through AskUbuntu thread but is it just for
"Focal" or from your PPA, I can install kernels in Hirsute too?
--
You
@jagsdesai
both #81 #57 still work with 5.14.3, installed yesterday on Xubuntu 20.04 ;-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926938
Title:
Recent mainline packages are built with
Hi @jagsdesai
I think you're using the package from mainline. I publish a PPA for
20.04 LTS, and version 5.14.3 has just finished building on launchpad
this morning, so any package you installed yesterday was nothing to do
with me ;-)
Here's my dependencies
$ dpkg -I
@tuxinvader
While trying to install Kernel 5.14.3 (Sep 12, 2021) on Ubuntu MATE
21.04, I ran into similar issue but for libc6 2.34.
Error:
dpkg: dependency problems prevent configuration of linux-
headers-5.14.3-051403-generic: linux-headers-5.14.3-051403-generic
depends on libc6 (>= 2.34);
@hashratez
right/official command (without adding any 3rd repository) is:
sudo apt install --install-recommends linux-generic-hwe-20.04
on officialy supported HW is done automatically, on other you must manualy run
for upgrade to latest HWE line, more info:
I suppose I found a super simple solution by chance. Just ran
sudo apt update && sudo apt upgrade -y
There were 3 repositories returning errors in my case. Such as,
E: The repository 'cdrom://Ubuntu 20.04 LTS _Focal Fossa_ - Release amd64
(20200423) focal Release' does not have a Release file.
Dear TuxInvader...
I have no idea why you do what you do but THANK YOU. I HAVE BEEN GOING
NUTS trying to get past the kernel bug for Ubuntu upgrades. WTF, they
call 20.04 an LTS but you cannot keep up with kernel security patches.
ARE YOU KIDDING?
YOU SAVED ME.
Hours and hours of install
@nvrmndr - Works for me :-)
Please open a bug on my github project if you want help debugging it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926938
Title:
Recent mainline packages are built
@nvrmndr #76
steps in #57 still work for 5.14 ;-)
anyway i did make some changes in my private tool, so can be published and is
here:
https://github.com/k3dar/kumk
you can simply install 5.14 via: sudo kumk install 5.14
--
You received this bug notification because you are a member of Ubuntu
So this is still a problem with kernel 5.14 without a working
straightforward solution. This is becoming frustrating since this issue
is now 4 months old.
@TuxInvader: I tried your repository (ppa:tuxinvader/lts-mainline) with
5.14, but something went very wrong - after booting with this kernel,
@72
opening salvo of " Ignorance doesn't mean knowledge, it is quite the
opposite..."
...nd then completely misreading a simple line of text.
k.
where have I said it's something to do w/ the headerz??? I've only meant
that the whole frigging exercise is to get the modules to work on my
site
@Jens Glathe - Good stuff!
I wrote down some high-level steps in #32.
the mainline kernels from kernel.org have a lot of stuff disabled which
will make things "fiddly". Easiest way to enable them for all the new
hardware is to download the same mainline ubuntu kernel version even if
it is
For penryn the -march option is "core2" in that GCC options link.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926938
Title:
Recent mainline packages are built with Hirsuite 21.04, not Focal
@tlk,- Ignorance doesn't mean knowledge, it is quite the opposite...
DKMS doesn't break because of headers when using clang with lto. The
headers are there and complete! Everything complete with well produced
binaries from LLVM/Clang.
The problem is because programs (not the headers and not
Was an interesing day, I was able to build and run mainline 5.13.12 on
Mint 20.2. Was the first time I used the mainline package from
kernel.org, and it was a bit fiddly, however copying over debian/ and
debian.master/ is a great start, thanks for the tip. Only thing that
doesn't work (yet) is
^ Recent gentoo convert?
"only problem" it breaks stuff, esp. those DKMS modules - the reason we
need those headers to begin with. Noice.
Your OS kernel will make your system feel and run snappier! - fake news)
especially funny for someone on a Ryzen 9 lol.
and clang... meh.
--
You
Good stuff @Jens Glathe!
I recommend everyone stuck to just build it and they'll see it work
perhaps even better than before, especially if you start natively
optimising the build against your hardware. Your OS kernel will make
your system feel and run snappier!
This is my build command post
Since HWE in focal changed today (?) to 5.13.0-14, trying to get it to
run I tried #66 DanglingPointer's approach (was on the same path trying
to build from the hirsute repo on Mint 20.2 - success with 5.11.0-25
after building dwarves locally :)). libbpf was missing, installed from
debian. zstd
@65
tbh I haven't analyzed what you've offered, but a quick glance over your post
*and* knowing what *I've* done to get it working tells me that no, it's not the
same. What I've done barely breaks into the usual workflow of installing the
image/headers from mainline and building the out-of-tree
You guys mocking around trying to hack headers and wotnot, just build
the bloody kernel and you'll have a full kernel without wondering if you
broke something by hacking stuff! You could have built the kernel a
100x by now!
1) Just build dwarves from hirsute
2) build libbpf from hirsute
3)
@tlk this is similar/same workaround, info posted in #57 is in principles:
1. install problematic package without configuring
2. replace binary files in unpacked package path
3. configure package (this also do dkms modules build)
4. fake libc depend version in status file
this (details in #57)
can confirm this (simpler) workaround works https://askubuntu.com/a/1335849
tested with 5.13.0
force-install the newer headers (edit out the libc6 2.33 dep in the dpkg
status file)
Then just dpkg -x linux-headers-5.11.16-051116-generic_5.11.16 and
replace fixdep and modpost
--
You received
Can anyone please confirm the #57 works without any major problem? If yes, I
request someone please write the instructions comprehensively.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Matias N. Goldberg (dark-sylinc) #61
not sure ;-) as i write in #57, this way is installable on 20.04...
k3dar@t430s:/$ lsb_release -d
Description:Ubuntu 20.04.2 LTS
k3dar@t430s:/$ uname -a
Linux t430s 5.13.7-051307-generic #202107310732 SMP Sat Jul 31 07:53:42 UTC
2021 x86_64 x86_64
This bug is related to
https://bugs.launchpad.net/ubuntu/+source/dwarves-dfsg/+bug/1928244
https://bugs.launchpad.net/ubuntu/+source/dwarves-dfsg/+bug/1912811
Kernel 5.13 can be compiled in one of the two ways:
1. Use dwarves 1.21, which needs Ubuntu 21.04 and breaks installation for
older
Hardware compatibility means that I need 5.11 and up, but this was
keeping me from getting newer kernels with up to date security. I am
kinda shocked that it is apparently being ignored by devs.
Thanks to tuxinvader, as builds on that ppa seem to work well with mint.
--
You received this bug
Awesome.
I've been building dwarves and libbpf using the c library from 20.04. I
believe you are too Tuxinvader.
But yes, there are extra hoops to jump over having to do those! If they
get it in then that would be a couple less things to boilerplate.
Would be good if they fixed DKMS as well
FYI - This bug is for back-porting dwarves and libbpf to focal fixing
support for newer kernels:
https://bugs.launchpad.net/ubuntu/+source/dwarves-dfsg/+bug/1912811
It wont make mainline releases work on focal, but it will again be
possible to compile a kernel using the focal toolchain.
--
You
@DanglingPointer #55
"If you want to stay with Ubuntu 20.04 LTS with latest stable mainline,
you'll need to build it."
not true... if not have external kernel modules (ex. using dkms builded
module for VirtualBox, Nvidia, tlp, wifi driver for card not supported
by mainline, etc..) then only not
It's becoming increasingly difficult to build your own kernels on focal
due to the kernel dependencies on newer tool-chain elements. You now
need dwarves 1.21 (or 1.20 with this patch
https://bugs.launchpad.net/ubuntu/+source/dwarves-dfsg/+bug/1928244 ) to
build a 5.13 kernel.
I have a focal
If you want to stay with Ubuntu 20.04 LTS with latest stable mainline, you'll
need to build it.
Otherwise, try openSuse-Tumbleweed or Fedora.
I'm sticking with ubuntu so just building my own kernels. Runs faster
now as well since it is optimised for my rig specifically now.
--
You received
The above does not work for me. Any update?
Is it worth compile my own kernel?
Or, time to switch to another distro?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926938
Title:
Recent mainline
Neon unstable switched last week (June 15th unstable ISO) to Kernel
5.8.0.55 default (Focal base). For mainline Kernel, this is the second
month, that the debian packages boot properly.
Full cycle next Sunday.
All we do is not downloading the first header (2.4MB), the smallest one.
No error and
DanglingPointer: you should take a look at Gentoo Linux, I guess you
will like it.
Most others out here, including myself, are using Ubuntu because we
cannot afford the time to configure and compile packages for all our
machines (it gets crazy when you manage an heterogeneous cluster).
Ubuntu
Thanks to this "bug", yes it IS a"bug"; thousands of ubuntu users have
learnt to compile mainline kernels!
I never had to compile a linux kernel until this happened to 5.11.17+!
I've always just installed whatever the mainline kernel team built.
The silver lining here is that my ivy-bridge
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926938
Title:
Recent mainline packages are built with Hirsuite 21.04, not Focal
20.04 LTS
To manage notifications about this bug go to:
It's a shame that mainline don't build LTS compatible kernels anymore,
but what can we do about it? It would be nice if they would build for
ubuntu-next *and* previous LTS, but they don't.
So new kernels for any Ubuntu release relies on the HWE updates that
come with the point releases. The next
Hello folks,
Im also affected by this issue
In the meantime, you can try with this PPA:
https://launchpad.net/~tuxinvader/+archive/ubuntu/lts-mainline-longterm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
So we will just let it go? Or, somebody from mainline kernel team is looking
into the matter?
This is ridiculous, what is the point of having a 5 year LTS which can't
support the newest kernels that are necessary for newer hardware? In simple
words, one cannot use Ubuntu LTS with new hardware.
5.10 the official kernel LTS release. If Ubuntu decides to long-term
other releases, it's their choice, I'm sticking to 5.10. Making 5.10
even more difficult to install than it already is (going to the mainline
"PPA", which isn't really a PPA, is already unfriendly), even if they
document the fact
Same issue with the latest stable kernel published today:
linux-headers-5.12.9-051209-generic : Depends: libc6 (>= 2.33) but
2.31-0ubuntu9.2 is installed
Ubuntu Server 20.04.2 LTS machine.
Please fix it. I don't feel comfortable installing 3rd party Kernels and I need
to use mainline kernel to
Hi all,
Controversial and TL;DR version - If one of the kernel devs can update
the wiki page here
https://wiki.ubuntu.com/Kernel/MainlineBuilds#Mainline_kernel_build_toolchain,
then as far as I'm concerned they can close this bug as resolved.
The longer version.
Ubuntu is great! Thank you
sudo apt update && sudo apt upgrade -y
The following packages will be upgraded:
dnsmasq-base evolution-data-server evolution-data-server-common
firefox-locale-en google-chrome-unstable libcamel-1.2-62 libdrm-amdgpu1
libdrm-common libdrm-intel1 libdrm-nouveau2 libdrm-radeon1 libdrm2
I truly do not understand why this is even a debate. The simple fact is
that either 20.04 is or is not an LTS release. If you are telling people
that you are going to support it for 5 years, then that means being able
to provide security updates to them as well as allowing them to use
hardware
Don't underestimated our capabilities, a Debian user is like red wine,
the more experience he gets, the better he is.
lsb_release -a && uname -r
No LSB modules are available.
Distributor ID: Linuxmint
Description:Linux Mint 20.1
Release:20.1
Codename: ulyssa
This bug and there is no bug started in Mint 20.1 with Kernel 5.12-rc7
alongside the shim 1.46 multiple issues. Since then it works here secure
boot enabled or not.
The bug comes with a broken header and it kills update manager.
All we do here to make it work is to delete the broken header in
Ok, this gets emotional, so let's concentrate on what's important.
Is there anyone speaking for the official mainline builds? What problems
would it bring to change the policy and build the mainline kernels with
latest (or even oldest!) LTS tooling?
It is apparent that the community would
What a joke! So how is the community going to contribute, help, and
support the mainline kernels for "debug purposes" now?
Everyone on LTS that wants mainline will now be forced to compile their
own kernels or arbitrarily trust PPAs of unofficial 3rd parties if
choosing to stay with Ubuntu.
Within the context of this bug report it is valid, as it is specifically
about the mainline PPA.
** Changed in: linux (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Like many of you out there I totally disagree with the decision to mark
this bug as invalid. I myself am running newer hardware that requires
support from kernel 12.x and can now only use compatible kernels like
the ones produced by tux-invader, not the ones on the mainline ppa.
--
You received
Might as well delete a completely useless page then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926938
Title:
Recent mainline packages are built with Hirsuite 21.04, not Focal
20.04 LTS
To
Mainline kernel is not supported:
https://wiki.ubuntu.com/Kernel/MainlineBuilds#Support_.28BEWARE:_there_is_none.29
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This has become a security issue!
So the kernels are now being built with impish, and unless people are
using my PPA or building their own, then the last install-able kernel
for LTS (focal) was 5.11.16.
The 5.11.x series went EOL with 5.11.22, and all 5.11.x have a level 7.8
CVE:
@eitch
Try Dougss steps without the aggressive optimisations first so you get
the hang of it. Make sure it works and your hardware all works.
My steps are a little different to Doug's and perhaps a little more
complicated. But once you get the hang of it, it is repeatable and can be
When we try to help people, either here on launchpad or on forums, very
often we would like them to try the latest mainline kernel, just as a
test to determine if the issue has already been fixed upstream. This bug
prevents that useful option for previous Ubuntu versions.
This dependency should
I think we're getting way off topic here. The fundamental issue in this
bug report is that the policy being employed when building the mainline
kernels does not follow the policy documented. Either the mainline
builders need to start following the policy (and building on LTS) or
change the policy
@DanglingPointer
Could you write down your way of building the kernel? I've been using
mainline debs, but i would like to profit from the optimizations by
building from source. Thanks a lot!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
PPAs are a mechanism for "moving around raw debs"... ;-)
But you have a point, however if all systems are in the same network, it
is far much more easier to copy all debs to all servers and sudo dpkg
-i./*.deb in automation.
If systems are geographically not in the same network and crossing
Just a quick tip: to see all available 5.10.3* packages,
printf '%s\0' linux-{image-unsigned,headers,modules}-5.10.{3,4} |
xargs -0 -n 1 apt-cache pkgnames | LC_ALL=C sort | less
@DanglingPointer the PPA is based on a Docker image which in turn is
based on a GitHub project (see comment 11) of
All you guys mocking around with ppas could have compiled 5.12.5 by now
20x!
The last working mainline kernel is 5.11.16. Nothing later works when
installing into 18.04 LTS.
I've been forced to compile each latest kernel since. But because of
that predicament, I've now got it down to a fixed
@tuxinvader is there a tutorial somewhere on how to manually replicate
your build (specifically on building dependencies)? most tuts are wildly
out of date and are not working. i'd like to install the ppa but also
learn how you did it.
--
You received this bug notification because you are a
I was able to install 5.12.4 using @tuxinvader ppa on 20.04 with current
libc6 2.31. Great work @tuxinvader!
I have used:
sudo add-apt-repository ppa:tuxinvader/lts-mainline
sudo apt install linux-image-unsigned-5.12.4-051204-generic
linux-modules-5.12.4-051204-generic
Ah, you're right. I expected there should be a metapackage linux-5.12.4,
but now I see I have to install the respective packages like linux-
header-5.12.4* etc. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@peci1 there's nothing to stop you adding my focal ppa to your bionic
system. The apt-add tool might refuse to add it, but you can manually
create the ppa.list file yourself if it does?
Create: /etc/apt/sources.list.d/mainline-ppa.list with the below content
deb
@tuxinvader Could you please also set up a bionic PPA? I manually
download the DEBs and install them on Bionic and everything works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926938
Title:
Running fine on 5.10.36 from tuxinvader's
https://launchpad.net/~tuxinvader/+archive/ubuntu/lts-mainline-longterm
(mentioned above).
Mainline PPA official packages still broken on focal, 5.10.38 is coming
up.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Still present on 5.12.4 as well
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926938
Title:
Recent mainline packages are built with Hirsuite 21.04, not Focal
20.04 LTS
To manage notifications
Yesterday new version (5.12.3-051203) of mainline kernel was issued. The
problem is still there:
. . .
Setting up linux-headers-5.12.3-051203 (5.12.3-051203.202105120733) ...
dpkg: dependency problems prevent configuration of
linux-headers-5.12.3-051203-generic:
Nice work and very timely, @tuxinvader. Perhaps leave an answer on
askubuntu for future reference.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926938
Title:
Recent mainline packages are built
I'll upload the latest 5.11.x kernel to a lts-mainline-previous PPA, and
longterm 5.10.x kernels to lts-mainline-longterm.
5.10.35 will be available here:
https://launchpad.net/~tuxinvader/+archive/ubuntu/lts-mainline-longterm
5.11.19 will be available here:
There is/was also some discussion on
https://askubuntu.com/questions/1334633/mainline-kernel-now-depends-on-
libc6-2-33-non-installable-in-focal -- I'm also interested in 5.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Even 5.10 series is affected. I'm on 20.04 and was installing 5.10
series. Now I'm stuck on 5.10.32 because 5.10.33 requires new version of
libc6.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926938
I updated my container so you can pick which flavour to build (generic
or lowlatency), and exclude some of the packages (udebs, cloud-tools).
The PPA now has enough space to build the source package.
So I've published 5.12.2 generic packages here:
Super, I was just looking for a way to build kernels in a Docker
container.
Maybe the Docker image could be modified to build dwarves for itself at
some point.
I think you can request more space for a PPA from launchpad.
--
You received this bug notification because you are a member of Ubuntu
I built a container for building mainline kernels. It build debs by
default, but it can also build signed source packages, but unfortunately
the sources are too big to be used with a PPA (they fill up the disk
during build).
There is another issue with building mainline on focal, and that's the
Still seeing this spurious libc 2.33 dependency (I *assume* it's not the
kernel people who decide to change their libc policy in the middle of a
release series -- so it's spurious) in 5.10.35.
Are the Ubuntu / Canonical people notified? I'm not sure who takes care
of this "Mainline PPA" (which
It would be a shame for 20.04 LTS users to no longer be able to make use
of the Mainline kernel PPA
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926938
Title:
Recent mainline packages are built
It would be unfortunate for the "LTS" kernel version to not be
installable on LTS Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926938
Title:
Recent mainline packages are built with
This bug appears to be either:
1. A documentation bug. The wiki
(https://wiki.ubuntu.com/Kernel/MainlineBuilds) needs updating to
indicate that mainline kernels are built for the current Ubuntu release
only. Remove the section about using the LTS tool-chain.
2. The automated build system is
> Shouldn't there be libc6>=2.33 dependency in the .deb so that it won't
allow itself to install?
linux-headers-*.deb has such dependency but not the other debs
This results in a broken installation where the kernel image and modules are
installed but the header isn't
--
You received this bug
A user just claimed that the new kernel packages allow themselves to install on
systems that don't have new enough libc6. Shouldn't there be libc6>=2.33
dependency in the .deb so that it won't allow itself to install?
https://github.com/bkw777/mainline/issues/87#issuecomment-831777690
** Bug
Though this problem also just appeared for me on ubuntu 20.10, when I
tried to upgrade my working mainline kernel from 5.11.16 to 5.11.17.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926938
Title:
> Should mainline kernels work on the previous LTS or not?
I think the main issue is with focal, the *current* LTS, which can't use
mainline kernels.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is not a bug report, but a question on the build policy of the
mainline kernels?
Should mainline kernels work on the previous LTS or not?
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
98 matches
Mail list logo
