obtaining an appropiate version of the kernel header

English Install/Boot/Login
1

I did do some Google search on my issue before deciding to post. I know it was a common issue for VirtualBox, however, I am not needing the kernel headers for that. The kernel I get when I do a uname -r is 3.16.7-24-desktop. I am trying to perform an installation of Dell Displaylink drivers and I had all c++ compiler and gcc stuff installed including the linux-glibc-devel package. When I was looking at the version of the linux-glibc-devel package, I see that it is for version 3.16-2.1.7. Is there anyway to get the package specifically for 3.16.7-24-desktop, even if I have to get a generic version of it somewhere? Was it even available or still in the works?

I also made a post regarding to this issue on the displaylink forum
http://www.displaylink.org/forum/showthread.php?p=78127#post78127

2

No.
linux-glibc-devel is not kernel version specific.

What you probably miss is kernel-devel and kernel-desktop-devel in the appropriate version.
If that doesn’t help, install kernel-source too.

3

In openSUSE you only have to “update” the system to re-sync installed kernel headers with the installed kernel. The following command updates your system, and assumes the package “kernel-devel” is already installed, else it needs to be installed.

zypper update

TSU

4

Unfortunately, even updating and installing additional kernel packages like the first reply mentioned isn’t even working

Distribution discovered: "openSUSE 13.2 (Harlequin) (x86_64)"
Unsatisfied dependencies. Missing component: Linux headers for running kernel, 3.16.7-24-desktop.
This is a fatal error, cannot install DisplayLink Linux Software.
5

I took a closer look at the shell script that it telling it to pull a linux header and it is making it read this directory

/lib/modules/$KVER/build/Kbuild

It turns out in none of the kernel build folders, there is no Kbuild folder. Is it possible to force it to read a different part of a build directory? The script is of course is originally written for Ubuntu which also means in that script, it it going to tell the system to add a systemd service which I know won’t work for OpenSUSE. Is there an equivalent to systemd that I can tell the script to add the service to?

add_systemd_service()
{
    cat > /lib/systemd/system/displaylink.service <<'EOF'
[Unit]
Description=DisplayLink Manager Service
After=display-manager.service
Conflicts=getty@tty7.service

[Service]
ExecStartPre=/sbin/modprobe evdi
ExecStart=/usr/lib/displaylink/DisplayLinkManager
Restart=always
WorkingDirectory=/usr/lib/displaylink
RestartSec=5
EOF
    chmod 0644 /lib/systemd/system/displaylink.service
}

remove_upstart_script()
{
    rm -f /etc/init/displaylink.conf
}

remove_systemd_service()
{
    rm -f /lib/systemd/system/displaylink.service
}
6

I also did notice that in place of systemd, it adds an upstart script if the system doesn’t do systemd (or earlier versions of ubuntu). Will upstart also work with OpenSuSE?

7

On 2015-08-18 00:26, miketheibm417 wrote:
>
> I also did notice that in place of systemd, it adds an upstart script if
> the system doesn’t do systemd (or earlier versions of ubuntu). Will
> upstart also work with OpenSuSE?

Nope.

But maybe you can figure out from what it installs there what to do
yourself.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

8

IIRC you need to install kernel-source for that and then run “make prepare” inside the /usr/src/linux/ folder or something like that.

It turns out in none of the kernel build folders, there is no Kbuild folder. Is it possible to force it to read a different part of a build directory? The script is of course is originally written for Ubuntu which also means in that script, it it going to tell the system to add a systemd service which I know won’t work for OpenSUSE. Is there an equivalent to systemd that I can tell the script to add the service to?

openSUSE does use systemd, so a systemd service should work.

But the path is wrong, openSUSE uses /usr/lib/systemd/, not /lib/systemd/.