I am trying to setup dkms to automagically build the rr26xx driver for a rocketraid 2640x4 card when the kernel is updated.I followed this guide which sounded like exactly what I was looking for.When I get to the step where you actually use dkms to build the module with:
Code:
sudo dkms build -k `uname -r` -m rr26xx -v 1.2
I got the following error:
[code]....
I'm trying to set it up so that I don't have to recompile the driver for my RAID card manually every time there is a kernel upgrade.I found a thread on it, here and a help page here, and it looks like it builds the module fine, but for some reason it's not being inserted into the new kernel, or something. It's like the new kernel doesn't know it exists, even tho modprobe -l shows the newly built module exists (and is in the correct place)Here's the script that I wrote up to get the drivers set up in DKMS:
Code:
#!/bin/bash
set -e
[code]....
each time i upgrade my kernel, my installation of lirc fails to work after the upgrade, and i have to re-compile (against new kernel) and install the lirc modules... which i do via something like:
Code:
sudo modprobe -r lirc_imon
sudo dpkg-reconfigure lirc-modules-source
sudo modprobe lirc_imon
after which all is well. this of course is a problem that DKMS should solve for me but it doesn't do it. also i get this message in my messages log:
[Code]...
My problem is that it won't load the dkms module and Virtualbox will not run.
View 14 Replies View RelatedWhere I can get my wireless network running by typing the following lines of code:
Code:
But I have to do this every time I boot the machine. Ideally, I want the machine to do this on it's own at startup.
Also, I'm totally new to linux and I don't really understand what the 1st line of code is doing? The 2nd is just to check that the 1st line worked, and the 3rd does the settings for the wireless network I'm connecting to.
If you want to get into why I have to do this every time, then look at my original thread. But I started this new thread just to find out how I can get these lines of code done automatically at startup.
Just like title.can i disable mmu, and build it? how to do that?
View 4 Replies View RelatedI am trying to compile the kernel version 2.6.20-15 on my Linux 10.10 with 2.6.35-22 kernel. Additionally, this is my assignment.After I download kernel, extract it and create a new .config file for the new kernel I am trying to command;make-kpkg clean fakeroot make-kpkg --initrd --append-to-version=-custom kernel_image kernel_headers.after the second command I get an error an it says "nothing to be done" but I expect to have some .deb files for the new kernel. In addition this I have added a new system call to the kernel 2.6.20-15.
View 1 Replies View RelatedI will like to build a Linux Kernel, how easy is it to build one?
View 9 Replies View Relatedmy server are acting weird, how to build a new kernel ?
View 8 Replies View Relatedthe correct way to remove custom kernels? I was trying to install a driver and only got it half way right and I want to wipe the slate clean and try again.Here's the original:Debian GNU/Linux, kernel 2.6.26-2-amd64root(hd0,4)kernel/boot/vmlinuz-2.6.26-2-amd64 root=UUID=64dcc531-f5b0-47e8-99c4-abeecfab9353 ro quietinitrd/boot/initrd.img-2.6.26-2-amd64
View 2 Replies View RelatedI need to build a new kernel. I was directed toI tried following the instructions but I think I may have ended up with way more than I wanted. After just over 3 hours the build exhausted the 5.2GB I had available and fell over. The .config file used was nearly twice the size of the one I supplied. Why was it changed?I don't need an rpm.Are the patches supplied with the 2.6.38 sources required or nice to have?
View 3 Replies View RelatedWe are working on 2.6.28. We have a requirement that we should boot using a non compressed kernel image. how can I build a non compressed kernel?
View 1 Replies View Relatedtrying to build parted 2.3, but I always end-up in the same error:
Code:
In file included from arch/linux.c:42:
/usr/include/scsi/scsi.h:152: error: expected specifier-qualifier-list before 'u8'
[code]...
Im trying to build parted 2.3, but I always end-up in the same error:
Code:
In file included from arch/linux.c:42:
/usr/include/scsi/scsi.h:152: error: expected specifier-qualifier-list before 'u8'
/usr/include/scsi/scsi.h: In function 'scsi_varlen_cdb_length':
/usr/include/scsi/scsi.h:163: error: 'struct scsi_varlen_cdb_hdr' has no member named 'additional_cdb_length'
[Code]...
running current on a Lenovo S10
the b43 driver craps out every few minutes.
so i decided to try the sta driver.
i downloaded the slackbuild but it crashes with the following see attached
I need to install latest xen 3.4.2 to my centOS. I have:
* xen 3.4.2
* Linux 2.6.18 with Xen 3.4.x support source tarball, updated for Xen 3.4.2
* CentOS kernel-2.6.18-164.11.1.el5
Linux 2.6.18 with Xen 3.4.x have old cciss and scsi drivers. It don't support my hardware.
CentOS kernel-2.6.18-164.11.1.el5 works normaly, but was not compiled with xen 3.4.2.
How can I patch Linux 2.6.18 kernel or upgade CentOS kernel to the latest xen?
This feels like dumb question but here goes...I am wondering what it takes to edit the Linux kernel source and build it with my modifications!
View 5 Replies View Relatedbefore i get a lot of annoyed responses, I did check the forum and found a couple older previous threads on this topic, but they don't seem to really explain any real solutions to the problem im having.Here's the story- I was looking around for instructions and found this "howto guide" on installing nvidia display driver [URL]I went through the steps he listed:
downloaded the driver packages, install the dependencies from the shell, and then i pressed CTRL+ALT+F2 to get out of X and into text mode. I stopped my gdm with the command: sudo /etc/init.d/gdm stopand then i tried to install the driver using: sudo sh (on my NVIDIA driver- his version was a bit outdated compared to the one I downloaded)But here is where the problem starts, as I go through the installation process and click yes, i reach the "progress bar" then the screen says "unable to build the NVIDIA kernel module". and then it just exits. What is going on here? Am I missing some other package or file?
I'd like to compile a generic kernel for my netbook on my desktop. They are both F12 64bit. On my desktop can I do:
make xconfig
make
make modules_install
Then copy the folder to my netbook then:
make install? Is there a better way? I don't really want to make .rpms.
My VMWare Player was working fine After updating the kernel it is throwing the error "Unable to build kernel module" my kernel is 2.6.40-4.fc15.x86_64 what to do?
View 2 Replies View RelatedWhen I build the kernel 2.6.30 source, the rpm package is very big and needed or root filesystem 800-900 Mb. I use "make rpm" as described in Configure, Build and Install a Custom Linux Kernel - openSUSE.
View 7 Replies View RelatedI'm building the 2.6.34 kernel and I notice some interesting options, which you may want to consider including in the build, if you are building it:
Code:
Code:
How to build uimage from my kernel linux-2.6.10_mvl401 ,then need to port on my arm PXA 300 through TFTP . What all steps I require to do.In which configuration file i should make changes for ethernet for boot
View 6 Replies View RelatedI am using the 13.1 build scripts from slackbuilds.org. I modified the scripts to build 3.2.12 rather than 3.2.10.
In 13.1 the main VirtualBox 3.2.12 OSE package built and installed without errors. The VirtualBox GUI starts without errors.
Running the virtualbox-kernel-mksrctarball.sh script built a kernel source package without errors.
Yet the VirtualBox kernel module won't build. I receive the following error:
Code:
]*** Building 'vboxdrv' module ***
make[1]: Entering directory `/dev/shm/virtualbox-kernel-3.2.12/vboxdrv'
make KBUILD_VERBOSE= -C /lib/modules/2.6.33.11-smp-2/build SUBDIRS=/dev/shm/virtualbox-kernel-3.2.12/vboxdrv SRCROOT=/dev/shm/virtualbox-kernel-3.2.12/vboxdrv modules
[Code].....
I am trying to build a custom kernel but I couldn't. Here are the steps to reproduce it:
1. Set Up an RPM Build Environment as its is explained in [URL]
2. Then follow the instructions in [URL]
3. When I try to install the kernel source rpm I get the following error:
[matias@Centos ~]$ rpm -i [URL
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root . . .
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
error: unpacking of archive failed on file /home/matias/rpmbuild/SOURCES/linux-2.6.18.tar.bz2;4ba24901: cpio: read
This thread describes how to build a 2.6.34 kernel with load-balancing to cut down the number of load balancing wakeups. Running powertop on my amd64 PC shows that this kernel cuts down the number of wakeups by around 30%.
1. Open a gnome-terminal and get root privileges:
Code:
sudo -s
2. Install required packages for building the kernel:
Code:
apt-get install build-essential bin86 kernel-package libqt3-headers libqt3-mt-dev wget libncurses5 libncurses5-dev
3. Download the 2.6.34 kernel source file:
Code:
cd /usr/src
wget http://www.kernel.org/pub/linux/kern...2.6.34.tar.bz2
4a. Download the diff file for the patch from [URL] and save as (eg) patch-load-balancing.diff. Move it to /usr/src once you have downloaded it.
5. Untar the source file:
Code:
cd /usr/src
tar xjf linux-2.6.34.tar.bz2
6. Link /usr/src/linux to the resulting folder:
Code:
cd /usr/src
# the folder linux may exist as a symlink from previously; if so, remove it
if [ -e linux ]; then rm linux; fi
ln -s linux-2.6.34 linux
[code]....
I can't get the nVidia kernel module built. Each time DKMS runs to install it (I'm trying to install it with the nvidia-kernel-legacy-173xx-dkms package on ), the build fails with a different error. Here is an exemple /var/lib/dkms/nvidia/173.14.27/build/make.log (I have a geForce FX 5200 on the computer I'm trying to install the nVidia driver):
DKMS make.log for nvidia-173.14.27 for kernel 2.6.32-5-686 (i686)
dimanche 24 avril 2011, 17:28:09 (UTC+0200)
make: entrant dans le r©pertoire /var/lib/dkms/nvidia/173.14.27/build
[code]....
I'm building a Kernel on System A to use on System B. I've followed the walkthrough on [URL], and I get the following rpms:
kernel-debuginfo-common-i686-2.6.30.8-64.hymerfania_dbg.fc11.i686.rpm
kernel-firmware-2.6.30.8-64.hymerfania_dbg.fc11.i686.rpm
kernel-PAE-2.6.30.8-64.hymerfania_dbg.fc11.i686.rpm
kernel-PAEdebug-2.6.30.8-64.hymerfania_dbg.fc11.i686.rpm
kernel-PAEdebug-debuginfo-2.6.30.8-64.hymerfania_dbg.fc11.i686.rpm
kernel-PAEdebug-devel-2.6.30.8-64.hymerfania_dbg.fc11.i686.rpm
kernel-PAE-debuginfo-2.6.30.8-64.hymerfania_dbg.fc11.i686.rpm
kernel-PAE-devel-2.6.30.8-64.hymerfania_dbg.fc11.i686.rpm
What I don't get are any
kernel-headers-<version>.<arch>.rpm
Files. Don't I need them to rebuild modules and drivers on System B? Otherwise, how should I copy my new headers to System B? BTW, System B crashes when I try to build the Kernel on it, that's why I'm building debugger Kernels on System A.
That's it guys. I have successfully installed the proprietary ati drivers in past 6.34 and 6.35 kernels but not in latest .6.36. I'm wondering if this have something to do with compatibility or not.
Installation log shows me some errors I can't recognize:
Code:
I had a debian installation with kernel 2.6.32 I had a set of instructions to apply a patch to kernel which I followed to the T. The grub now shows the Debian installation with the old kernel and the Debian installation with the patched kernel.
The trouble is the system goes blank after attempting to start gdm3.
I have tried running in recovery mode and then typing startx but it only shows a blank screen.
Code: lspci | grep -i display
00:02.1 Display controller : Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) If i boot with the old kernel, everything works fine. Is this an "X" window configuration issue. I tried X -configure but still nothing changed.
