It is 100% unnecessary to set the later kernel as dependent on the higher libc6 version. Why does Canonical (and only Canonical does this...) do this?
Ok, so we have established that the drivers included in the kernel for Arc resolve the issue. But, the Linux Headers have a set dependency higher than the system.
What we can try for ease of use is to test a slightly earlier kernel like 6.7 and see if it is using the dependency of libc6 current to the system, but also contains the Arc drivers.
I'm now on kernel 9.7, and I've still the same problems.
The command uname -r returns 6.7.0-060700-generic.
When I run sudo dpkg --configure -a I get :
dpkg: dependency problems prevent configuration of linux-headers-6.7.0-060700-generic :
linux-headers-6.7.0-060700-generic depends on libc6 (>= 2.38); however :
libc6:amd64 version on system is 2.35-0ubuntu3.6.
dpkg: linux-headers-6.7.0-060700-generic package processing error (--configure) :
dependency problems - left unconfigured
dpkg: dependency problems prevent configuration of linux-headers-6.8.1-060801-generic :
linux-headers-6.8.1-060801-generic depends on libc6 (>= 2.38); however :
libc6:amd64 version on system is 2.35-0ubuntu3.6.
dpkg: linux-headers-6.8.1-060801-generic package processing error (--configure) :
dependency problems - left unconfigured
Errors were encountered during execution :
linux-headers-6.7.0-060700-generic
linux-headers-6.8.1-060801-generic
If Yes:
Can you use the Mainline tool to go ahead and remove those kernels.
Once that is done, ensure Secure Boot is disabled in BIOS / EFI settings.
Then install the 6.7 kernel supplied by TuxInvader:
The 6.8 and 6.7 kernels. Since they are giving a dependency error, the best action is to remove them and revert to a fully working kernel; otherwise you are left with a broken package as well as not running on the Linux-Image from that kernel.
The TuxInvader supplied kernel has a fix tot he depends file that allows you to add the kernel on your system. TuxInvader is not currently offering the 6.8, which is why I asked if the 6.7 works.
Reading package lists... Done
Build dependency tree... Done
Read status information... Done
Some packages cannot be installed. This may mean
you've asked for the impossible, or, if you're using the
unstable distribution, that some packages have not yet been
been created or have not been released from Incoming.
The following information should help you resolve the situation:
The following packages contain unsatisfied dependencies:
linux-generic-6.07 : Depends on: linux-headers-6.7.5-060705-generic but is not installable
Depends on: linux-image-unsigned-6.7.5-060705-generic but it is not installable
Depends: linux-modules-6.7.5-060705-generic but it cannot be installed
E: Unable to fix problems, faulty packages are in "keep as is" mode.
Looking at the 6.7 packaging, there is a fault in the uploaded files. The TuxInvader supplied packaging sets its dependency on those uploaded.
The 6.6 kernel supplied by TuxInvader have no upload fault - and that installation works.
Let me see if I can setup a corrected kernel .deb for you.
Currently (Thanks solar storms) I am on minimal internet, so cannot download a file quite that large at this time.
Well, after a very lengthy download, I too, am running into build failures. It appears related to gcc and rust, and when I looked into it; it led me back to tux and that it appears I am not the only one who is baffled by why the same configuration that works on other builds:
Misery loves company; I do not feel so bad, now.
So, another alternative is to use the Zabbly kernel which member @AhavaLeaf suggested on the forum previously:
To add the repository, copy paste the below long-winded command into terminal:
sh -c 'cat <<EOF > /etc/apt/sources.list.d/zabbly-kernel-stable.sources
Enabled: yes
Types: deb
URIs: https://pkgs.zabbly.com/kernel/stable
Suites: $(. /etc/os-release && echo ${VERSION_CODENAME})
Components: main
Architectures: $(dpkg --print-architecture)
Signed-By: /etc/apt/keyrings/zabbly.asc
EOF'
sudo sh -c 'cat <<EOF > /etc/apt/sources.list.d/zabbly-kernel-stable.sources
Enabled: yes
Types: deb
URIs: https://pkgs.zabbly.com/kernel/stable
Suites: $(. /etc/os-release && echo ${VERSION_CODENAME})
Components: main
Architectures: $(dpkg --print-architecture)
Signed-By: /etc/apt/keyrings/zabbly.asc
EOF'
I get no output and if I run sudo apt install linux-zabbly I get error E: I can't find the linux-zabbly package, so I must have installed the repository incorrectly.
What have I done wrong?