Debian Configuration :: No Rule To Make Target Modules
Sep 17, 2015
i'm trying to install driver for some PCI device but i have problems with it - when i run it it gives me an error
Code: Select allmake: Entering directory `/lib/modules/2.6.32-5-686/build'
make: *** No rule to make target `modules'. Stop.
make: Leaving directory `/lib/modules/2.6.32-5-686/build'
i've tried to find solution in internets but have no success usually they say that problem is that ppl forget to download kernel-headers and kernel-sources or unpack kernel-sources or make symlink usr/src/linux but i've done it all and the result is the same.i think the root of problem is that `/lib/modules/ 2.6.32-5-686/build' folder is empty but there have to be this RULE, so what i have to do to have it there? my system is Debian 6.0.10 Squeeze, Kernel 2.6.32-5-686.
After reading all the forum entries and tutorials I could find, which all make it sound very easy to do, however I type the command 'make' in the folder where I have the "rtl8192su_linux_2.4_2.6.0003.1019.2009.tar.gz " unzipped and get the following output:
make: Entering directory `/lib/modules/184.108.40.206-45.fc14.i686/build' make: *** No rule to make target `modules'. Stop. make: Leaving directory `/lib/modules/220.127.116.11-45.fc14.i686/build'
I am relatively new to linux and am running into a problem. I just got a new laptop and need to configure/install it's wireless driver but am getting an error when running "make". The error is: make: Entering directory `/lib/modules/18.104.22.168-1.2-desktop/build' make: *** No rule to make target `modules'. Stop.
I have scoured these forums and know that others have the same issue (when configuring other drivers/programs). I am sorry if this post is redundant. It sounds like the Makefile is pointing to the wrong directory. I am using opensuse 11.4, have make and gcc installed. My kernel is linux-22.214.171.124-1.2 (I just re-installed the desktop kernel to make sure it was up to date). The driver I am trying to install is located here: AUR (en) - rtl8192ce.
Another forum suggests pointing somewhere in the /usr/src/linux-126.96.36.199-1.2 directory instead. Is this correct? Should I be pointing to a folder within this? I am not a programmer but any description about what I am actually putting in this directory and why would be awesome (so I can learn a bit more). Or just helping me solve the problem would be great too.
I have googlled and get these commands to install extracted .tar.gz file such as ./configure, make and make install, after extraction it becomes a directory called eclipse. But when i giving these commands also i got error like this
I am following the instructions on Section 8.1.* Device Driver ConceptsHere I was able to proceed till section 8.1.4.After making the hello.c file,the make file and patching the Kconfig as mentioned,I tried to run the $ make ARCH=ARM CROSS_COMPILE=xscale_be- gconfig This gave error as:make: *** No rule to make target `gconfig'. Stop.I am not sure if my kernel is correctly compliled,but I was able to complie and build the kernel for arm before by cloning the kernel and building from the following link without any error. https://omapzoom.org/gf/project/omap...ux+OMAP+Kernel
I've had qmail running on a server for three years, almost forgot how difficult that installation was. I got away with it because I downloaded Qmail Rocks and followed all their instructions step by step. However, Qmail Rocks is based on qmail 1.03. I just had to install qmail on a new server, so this time I looked around and found netqmail 1.06 and decided to go with it, following the instructions on Life With Qmail. It was a good decision. A read a lot more documentation and now I understand qmail a lot better.
But I can't get past one point: authentication. Consider this test on Qmail Rocks: Code: telnet localhost 25 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 somewhere.anywhere.com ESMTP ehlo localhost 250-somewhere.anywhere.com 250-AUTH LOGIN CRAM-MD5 PLAIN 250-AUTH=LOGIN CRAM-MD5 PLAIN 250-STARTTLS 250-PIPELINING 250 8BITMIME starttls 220 ready for tls quit quit Connection closed by foreign host.
That test works fine on my old server. But qmail behaves differently on my new server: Code: # netqmail-1.06> telnet localhost 25 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 domain.com ESMTP ehlo localhost 250-domain.com 250-PIPELINING 250 8BITMIME starttls 502 unimplemented (#5.5.1) quit 221 domain.com Connection closed by foreign host.
That same page on Qmail Rocks says that I need to have a certificate, the procedure is described here. The installation procedure given by LWQ does not include that step. Running 'make cert' inside the source directory of netqmail-1.06 does not work: Code: # netqmail-1.06> make cert make: *** No rule to make target `cert'. Stop.
In my vast ignorance, I copied /var/qmail/control/servercert.pem from my old server over to the new one. I also fixed all ownership and permissions. I don't know if I am allowed to do that. But although those are two different boxes, I am in fact installing the same domain in the new box. The new server is going to replace the old one as soon as it's running perfectly. I restarted qmail and... authentication still does not work.
I recently bought a pci multi io card to give my pc 2 parallel ports. For Linux, Moschip supply the source plus makefile and instructions. I ran make as root and got an error message make: *** /lib/modules/188.8.131.52-0.2-desktop/build/: No such file or directory. So I created a folder called build in /lib/modules/184.108.40.206-0.2-desktop but that isn't good enough as I still get an error cannot make target modules. So I assume there must be something in the build folder. So what packages do I have to install to get the correct environment to be able to build the driver? Has anyone done this and can supply the driver for 11.2?
I'm attempting to build cloog-ppl-0.15.10 but even the configure script tells that everything look good, "make" complains saying "No rule to make target `m4/libtool.m4`, ...". I'm running Scientific Linux 5.5 on a x86_64 machine.
firewall server which runs on Debian and then theres windows 2003fileserver. On this machine runs as well SQL server. Letssay it listens to port 1000. From other windows machines I want to connect to this Sql server which holds library database for users. But the connection cant be made. Possible error that firewall Debian machine want let the packets through.So how to I add a rule into iptabels (what file to open and edit?) So that all localconnections to the server lets say which is 192.168.0.2 and the firefall machine is 192.168.0.1 go through! So the connections allowed would be 192.168.0.3-255. How is it safe to do and how will it look like? Sql server uses TCP/IP connection. Heres what I found from web, I think this may be the right rule, but how i modify it correctly.iptables -A INPUT -p tcp -s 0/0 --sport 1000 -d 192.168.0.2 --dport .........? -m state --state NEW,ESTABLISHED -j ACCEPT
I have an old version of DSL installed, followed by XP. On a further partition I installed Debian 6. Installation of Debian went smoothly, including the final detection of the other two OS for Grub. I had expected that the Debian-version of Grub would override/overwrite the one that came when I installed DSL. It did not - when I boot, Grub comes up with the old DSL menu, in which Debian is not included.
From what I've been reading about Grub, there's two "fases", first in MBR, that points to the second part where the actual boot-commands are given, in my case stored in DSL. When I open the Grub config-file in Debian, both DSL and XP are correctly listed.
Now I'm not sure what to do - I'm a bit hesitant to try and point grub-fase-1 to Debian (if I can write the correct lines at all, I'm very insecure on that) - if that fails, I cannot boot at all. But I'm not really sure either how to formulate a new rule in the DSL-grub, to make Debian boot from the existing menu.
I'm trying to configure auditd to monitor "strange" events with apache2 weberver on Wheezy (though same problem occurs on Jessie), tried both with "vanilla" 3.2 and backports 3.16 kernel I am actually using.
Here's auditd rules I have problem with:
Code: Select all-a exit,never -F arch=b64 -S stat -F path=/var/www/server-status -k web -a exit,always -F arch=b64 -S stat -F uid=www-data -F success=0 -k web
So to recap, I want to log stat syscall failures for www-data user, but excluding some "known" issues, such as that "/var/www/server-status" (after a2enmod status, /server-status path can be accessed for statistics, though apache2 still tries to find physical file for that path and fails).
I have a trayless SATA hotswap bay that is really terrific for quickly attaching and removing SATA hard drives. I'm trying to write a udev rule to create a symbolic link to the device node for the drive that is attached through the hotswap bay (/dev/bay -> /dev/sdX). This eliminates any ambiguity when performing destructive tasks (fdisk, etc). I'm running squeeze amd64. I've read through several tutorials and have it working somewhat. Here's the output of udevadm info for a drive attached via the hotswap bay.
Here is my udev rule DEVPATH=="/devices/pci0000:00/0000:00:11.0/host7/*", SUBSYSTEM=="block", SYMLINK+="bay%n"
This produces the desired behavior and gives me an fdisk-able device node. The problem I am having is that the "host" component of the DEVPATH varies from bootup to bootup. I'm just using on onboard SATA, host2-7, specifically host7. There is also onboard PATA, host0-1. It seems to just be random which "host"s are assigned to which controller. For example, the next time I boot the system, the onboard SATA will be host0-5 and the onboard PATA will be host6-7. In this simple case, I could just write 2 rules, one for each possibility and it would still be correct because of the different PCI addresses of the two controllers. But on systems with more SCSI (uh... libata, actually) controllers, a "host" file can point to different physical ports between bootstraps. This would be bad. Does anyone know of a way to write a rule to tie a device node to a specific physical SATA port on the motherboard/hba?
I have to load the ip_conntrack modules every time I reboot. How do I get the iptables modules to load automatically at boot. It seems they are supposed to auto load when they are needed but they are not doing that. I have to do modprobe on them. also does anyone know where I can download all the modules available for iptables? I looked on the netfiler site and did not learn much.
I have installed an images using debbootstrap command. The problem is there is no module in /lib/modules.For example I have installed lm-sensors but when I run sensors-detect, in the middle of detection I get these:FATAL: Could not load /lib/modules/2.6.32-24-server/modules.dep: No such file or directoryFailed to load module i2c-piix4
After a hiatus I found my machine to be down, but upon turning it on I get significant errors and dropped into emergency mode (see below). This machine wasn't very up-to-date to begin with, so I'm having difficulty determining the order in which to proceed. A couple naive checks and updates on my part are not working. The file system appears to be intact enough to "cd" around and "ls" to see that my files are all (seemingly) there. But the kernel modules aren't loading which is, you know, a problem.
The state I find it in is that it will begin booting to Linux 3.2 (which I know is no longer supported in testing, see below where I tried to update to 3.16), but fails quickly and puts me into emergency mode
Loading, please wait... megasas: INIT adapter done systemd: Failed to insert module 'autofs4' systemd: Failed to open /dev/autofs: No such file or directory systemd: Failed to initialize automounter: No such file or directory systemd: Failed to set up automount Arbitrary Executable File Formats File System Automount Point.
...Then several drives show up as clean....
Running "journalctl -xb" shows that it can't mount the module even though it's there on the disk: ... systemd-modules-load: could not open moddep file '/lib/modules/3.2.0-4-amd64/modules.dep.bin' ... systemd-modules-load: Failed to lookup alias 'firewire-sbp2': Function not implemented ... systemd-modules-load: could not open modeep file '/lib/modules/3.2.0-4-amd64/modules.dep.bin' ... systemd-modules-load: Failed to lookup alias 'loop': Function not implemented
And yet, if I 'ls' that modules.dep.bin file, it's right where it's supposed to be, for the appropriate architecture and everything.
After that (in the journalctl output), it shows several things start up, but systemd-modules-load.service fails: .. systemd: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE .. systemd: systemd-modules-load.service: Failed to start Load Kernel Modules
...and lots of things fail from systemd-udevd: failed to execute '/lib/udev/socket:@/org/freedesktop/hal/udev_ev_event': No such file directory.
I tried updating via apt to the Linux 3.16.0 kernel, but grub wasn't finding it in a way that effects the boot process, and no appropriate "vmlinuz-" file appears with the others on the boot partition. So, I tried switching to grub2 but the update-grub command produces many errors.... For now, grub2 still (attempts to) load the old kernel (3.2) with the same results as I was getting with the old grub-legacy.
Regarding the module-loading features, running "lsmod" shows about 30 lines:
Module ext3 mbcache jbd dm_mod usbhid hid
...I'm at the limit of what I know to check and/or try.
My new laptop works out of the box except for the video and the ethernet. For this, I have to use a later kernel than the Debian kernel (debian squeeze is currently 2.6.32). Upgrading to the new kernel (without moving to the testing dist itself) was pretty easy. I just installed linux-image-2.6.38-2-amd64 and linux-base from the testing distribution by manually downloading and using dpkg. After that, ethernet and video started working.
However, my virtualbox installation no longer works because the drivers do not match the kernel. I am used to this; whenever debian upgrades the kernel on me, I have to run "/etc/init.d/vboxdrv setup". This rebuilds the drivers. This failed for me, however, because it could not find the headers. So, I installed some more packages:
These kernel sources are usually the sources from debian, with a couple of more patches that I add. It appears that for nvidia-driver package versions higher than 352.79-1, the kernel headers/sources need to be prepared with 'make prepare' and 'make prepare scripts'. It's that simple. I concluded this after the nvidia dkms build failed on my custom kernel, but then succeeded after I pointed it to the full sources, but only after running 'make prepare' and 'make prepare scripts' on them. The problem is that this make-kpkg scheme doesn't appear to do this, or if it does, it doesn't properly include in the headers everything that it should.