the 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 RepliesDoes aptitude(or apt-get) have the functionality to remove the packages installed from using build-dep? It just seems convenient if you want to remove a program that was built from source.
View 4 Replies View RelatedI 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 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.
I am working with linux-source-2.6.30 from squeeze.
The only changes I made in the config file were the processor type, and I disabled CONFIG_SYSFS_DEPRECATED_V2 to avoid some warnings from udev.
When I tried to build the kernel package, this is what I get:
(The bottom bit is from 'time').
Searching for this error turned up a plethora of results, none of which seemed relevant.
I see that it tells me to file a bug report, but I'm not sure if that is meant for the Debian kernel team or upstream.
I used make-kpkg to build the 3.0.0 source debian wheezy on a dual 3.4GHz Xeon/L1-16k/L2-1mb/800Mhz bus with 4GB PC2-3200 ECC ram and Ultra 320 SCSI, using CONCURRENCY_LEVEL=4 (2 hyperthreading cpus=4 cores). The build was slower than molasses in January! Top reported cpu usage total between 10% and 25%. Why won't the build use the amount of machine it has available. One footnote: I wasn't using swap space. It literally took over an hour to build the deb kernel package.
My notebook from 2003 is at least three times faster building the 3.0.0 debian kernel source. Is it possible that this might cause improvement: make -j4 KDEB_PKGVERSION=version deb-pkg
over
CONCURRENCY_LEVEL=4 make-kpkg --initrd --revision=123x kernel_image?
Could amd64 vs. i386 have some influence? Could the small processor caches on the XEON cpus have an effect. The 64-bit machine absolutely flies doing everything else. I'm miffed! I've used debian since woody, although I am not an expert, but I'm no slouch!
I'm trying to build the package zaptel on debian, but I'm encountering two errors:
1- When I try to run the "make menuselect" command, I get an error stating that I need ncurses which is missing. I tried to get it installed but didn't get to do it yet.
2- After that, there's the command "make" I think it's to build the package. Yet again this fails, and the error I get is "you do not appear to have the sources for the 2.6.26-2-686 kernel installed".
I was wondering how can I determine among the modules loaded at boot which of them are really necessary and which are not, in order to reduce the boot process time and have a more "elegant" system start.
I know this theme is a little bit of complicated because it depends of the user's point of view and demand a high knowledge of which things are happening in your system but I need somewhere to start improving the performance of my debian system.
I 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 RelatedJust like title.can i disable mmu, and build it? how to do that?
View 4 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?
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
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 use ltib for mpc8272ads. How to build kernel with 'make CONFIG_DEBUG_SECTION_MISMATCH=y'?
View 3 Replies View RelatedI have just started to work with BeagleBoard and built the Linux kernel (version 2.6.30.5) and download to the board and it start. I have also connected to the board over serial to Putty terminal.
Now I want to connect to the Beagle Board using USB instead of serial and I am looking for some info on how to do this.
My goal would be to connect to board over USB and then be able to:
* Download my own binary files/programs from PC over USB to BeagleBoard
* Communicate over USB instead of UART/Putty to get log and execute commands
Question:
How do I build the Linux kernel with USB support, meaning what settings should be ticked in menuconfig? Or is it already included?
How do I enable USB OTG in menu config?
I assume I would need some driver on my PC with Windows XP to connect to my BeagleBoard over USB. Were can I find this USB driver?
I'm trying to debug a module I programmed but I don't want to do it on the running host but against UML (don't want to reboot every 5 minutes).
The UML kernel I downloaded is 2.6.38.2. I have already downloaded the ubuntu kernel headers for this version (they belong to natty though I'm running maverick.... when I installed the .deb file with dpkg I had no problem at all).
Now I'd like to build said module against these headers. How can I do it?
Here's the makefile for my module code...