I was trying to follow instructions in http://acx100.sourceforge.net/wiki/ACX

There is a reference to build in my kernel (with red background), se below:

linux-om4s:/lib/modules/2.6.31.5-0.1-default # ls
build modules.alias modules.alias.temp modules.builtin.bin modules.dep.bin modules.symbols source updates
kernel modules.alias.bin modules.builtin modules.dep modules.order modules.symbols.bin systemtap vdso

However,when trying make from my dictionary :

linux-om4s:/usr/src/dlink1/acx-20080210 # make -C /lib/modules/`uname -r`/build M=`pwd`

build is not recognized, i.e.the following occurs:

make: *** /lib/modules/2.6.31.5-0.1-default/build: No such file or directory. Stop.

Both make and build have been properly installed in Software Manager.

Whatś wrong?

What is the output of:
Most likely you miss the kernel-source, kernel-default packages

Regards

0 members found this post helpful.

Thanks for your orinot answer,

stefan@StaryLaptop:~> ls -l /lib/modules/`uname -r`/build results in:

lrwxrwxrwx 1 root root 44 2010-07-01 08:34 /lib/modules/2.6.31.5-0.1-default/build -> /usr/src/linux-2.6.31.5-0.1-obj/i386/default

and the background from /lib on is red

What an I supposed to do in order to take care of /include kernel-source and kernel-default?

Sorry for my stupid questions, but I am really a newbie to Linux. .

Well.. kernel-default is the name of your kernel. Kernel sources are the development files (headers and libraries) that are mandatory to build kernel modules. OpenSuSE used to call kernel-source the package containing these headers and libraries, but since release 11.2 the package has been renamed kernel-name-devel.

You have to check the exact kernel you have installed on your system and (if missing) install the matching kernel-default-devel package. Example: in Yast Software Management or from the command line using rpm or zypper, you can easily verify if you have:
and install the following accordingly:
Just be sure the kernel name (default) and the version numbers (kernel: 2.6.31.5, package: 0.1.1 in the example above) are exactly the same.

0 members found this post helpful.

Sorry gentlemen, but I am a complete newbie, which means that "What" to do is still too complicated.
What I need is "How" to do it.

Anyway, after having looked around a lot, I finally inquired the system with rpm and found that I have only
the "kernel-default" package. I found also the other packages, i.e. "kernel-default-base" and "kenel-defaoult-devel" on Internet
and downloaded them. However, when trying to install them (via Gnome), I received the following:

"The request failed. .... failed to get supported types for the backend. Launch helper exited with unknown return code 1"

Best regards,
Stefan

Ok, sorry. The error message reveals a problem with the graphical front-end for the GNOME package installer, so let's try from a terminal by now. Be sure the system is connected to internet, open a terminal and login as root using:
Please note the # sign is only the command prompt (you don't have to type it). After that you will use zypper to download and manage the required packages. First check the installed kernel packages and the available ones:
this will give you a list of all the kernel-default packages (most likely you will see multiple versions, but only one kernel-default package is installed - check the i in the first column). If it correctly lists also kernel-default-base and kernel-default-devel matching exactly the version of the installed kernel, you can proceed to installation:
zypper will automatically select the correct version, matching the running kernel. If in doubt answer "no" when prompted for confirmation and post the output of both commands here (please use CODE tags for doing so - in advanced mode you have to select the text and click the # button - you will see the text embedded in [CODE]some text[/CODE]).
Hope this helps.

Thanks a lot. And sorry for posting my previous message twice: things happen when you try to hack in the middle of the night.

The kernel files are already installed, and the make -command with nuild (which initited the tree) have been properly executed, albeit with some errors. But it may be the beginning of another tree.