Debian :: Change The Module And Create Custom Kernel
May 7, 2011I'd like to change the existing kernel module (driver) file and compile a custom kernel.
Is this the correct way:
I'd like to change the existing kernel module (driver) file and compile a custom kernel.
Is this the correct way:
I have a problem with my custom kernel when I want to create the Nvidia kernel module.After this finished I installed the image and headers and created the Nvidia kernel module. Everything worked fine.However, if I remove the linux-source from my home directory then I can't create the kernel module.Even though I have the headers for the kernel installed.
View 2 Replies View RelatedWhen I only change a driver file manually, for example /newkernel/linux-source-.6.32/drivers/gpu/drm/i915_drv.h, do I need to run "make config" or similar like "make menuconfig" or can I just skip? I mean these steps:
1.) apt-get install linux-source-2.6.32
2.) mkdir ~/newkernel/
3.) cp /usr/src/linux-source-2.6.32.tar.bz2 ~/newkernel/
4.) cd /newkernel/
5.) tar xjf linux-source-2.6.32.tar.bz2
6.) cd linux-source-2.6.32
7.) cp /boot/config-$(uname -r) ./.config yes "" | make oldconfig
8.) change the driver file /newkernel/linux-source-2.6.32/drivers/gpu/drm/i915_drv.h manually
8.) make-kpkg clean
9.) make-kpkg --rootcmd fakeroot --initrd --revision=custom.001 kernel_image kernel_headers
10.) dpkg -i *.deb
Is this way OK or do I miss something?
I am trying to write a kernel module that will DMA my custom card. Right now when i plug the card into linux no valid PCI device shows up (meaning I probably have a error on my end, i know) however, If I halt the system at startup in the bootloader (uboot) I am able to directly access the card as I know in uboot the physical memory address that is mapped to my device. Is there a way I can access the card in a simliar fashion in linux?
View 1 Replies View RelatedI'm running CentOS 5.3 and would like to know what the "best" or "proper" method is to build a custom kernel using the generic kernel sources from kernel.org. Most of the references I've found talk about modifying the current CentOS kernel using the RPM way. I really want to have the latest kernel due to some important security issues that haven't been addressed in the current CentOS 5.3 kernel.
View 6 Replies View RelatedI need to install Ubuntu on approximately 50-60 netbooks. None of them have CD drives, and I don't want to have to install them individually, walking around with a USB stick. I figured the fastest way to install on so many machines is to use a combination of apt-cacher (http://www.debuntu.org/how-to-set-up...ith-apt-cacher) and netbooting. I have successfully booted one machine to test, but as soon as the kernel comes up, support for the network interface is gone. Specifically, the "atl1c" module is not included on the netboot initrd image. Also, I would like to try to use preseeding, and I need to get that onto the initrd as well.
So, to summarize my question: How can I create a custom install kernel and initrd? I have a feeling it's related to the "debian-installer" category in the package repository, but I have not found any good documentation about doing this.
I'm trying to create new RAM image file to get my server load raid1 module upon start, I was following redhat documentation & it suggested to use the following command mkinited --with=raid1 inited-raid1-$(uname -r).img $(uname -r) However after running this command I'm getting this message No Kernel available for 'inited-2.6.18-128.el5"
View 4 Replies View RelatedI been trying all day to compile a kernel i downloaded from http://www.kernel.org/ (2.6.32.8 )Following this help thread viewtopic.php?t=4468.When i invoke make xconfig i'm just kinda lost at that point. Not really sure what to do, so i just save it as is and then compile/install.when i try to boot the kernel, a kernel panic happens saying it can't not mount the root partition.So i am sure i am missing a step with the xconfig part but not sure what.
View 5 Replies View RelatedI'm looking for a software running under debian to create and resize custom splash images.
I know just GIMP, but maybe there is a special software.
I'd like to create a custom squeeze kernel. Is it a really bad idea to edit to edit the kernel config file directly instead of using "make config", "make menuconfig" or "make gconfig"? My problem is I missing a search function, for example in "make menuconfig" and cannot find some entries.
View 2 Replies View RelatedThere is a kernel module that connects a SCSI like hard disk to Linux computers, as well as windows and MAC. Some portions of the source code have a GPL license on them, but some remain property of the hardware inventor. The inventor does not agree to GPL the entire code, even just the Linux code. Consequently, the connection package falls behind, the existing users feel left out and the new opportunities fall by the wayside.
The confusing thing for me is that the company gives away the end product, (the compiled module and it's editable source code) but they won't let non-employees edit the official source to keep it up to date. Ultimately they only make money on the SCSI-like connection hardware. Several users have modified the existing package to keep it up with some distributions, but there are others that should be explored and new architectures to employ it.
1) Could I set up a sandbox that hides the non-gpl source code pages, but allows willing developers to join and modify the gpl sections and then compile the modules on different architectures?
2) I have trouble understanding the difference between working on this kind of kernel package for free and releasing the code. In other words, since the company gives away the end product, just as GPL developers do, why not just agree to the same requirements you would have if hired at the company, but do the development for free in the spare time anyway?
I've a problem running jessie on a XEN supervisor; my running kernel and the installed kernel image differ, because the host system forces the kernel at boot time. Current loaded kernel is
Code:
Select all$ uname -r
3.18.12
But I'm not able to install this version from the standard repository.
Code:
Select all# apt-cache search linux-image
linux-headers-3.16.0-4-amd64 - Header-Dateien für Linux 3.16.0-4-amd64
linux-image-3.16.0-4-amd64 - Linux 3.16 für 64-Bit-PCs
linux-image-3.16.0-4-amd64-dbg - Debugging symbols for Linux 3.16.0-4-amd64
linux-image-amd64 - Linux for 64-bit PCs (meta-package)
linux-image-amd64-dbg - Debugging symbols for Linux amd64 configuration (meta-package)
nvidia-kernel-3.16.0-4-amd64 - NVIDIA binary kernel module for Linux 3.16.0-4-amd64
linux-image-2.6.32-5-xen-amd64 - Linux 2.6.32 for 64-bit PCs, Xen dom0 support
Now I'm facing issues loading kernel modules for iptables, because the module path does not exist. Is there an easy way to install a proper kernel image from the standard repositories?
I would like to compile a custom xen dom0 kernel. I installed a Debian Squeeze with precompiled xen kernel, and it works fine, but i would like to compile a custom dom0 kernel from source. I tried install kernel source apt-get source linux-2.6 how can I patch this kernel source with xen? but i alway see only the domU kernel params.
View 3 Replies View RelatedI have squeeze and I've created my own custum kernel. Howto configure grub 2 to boot with this custom kernel automaticaly?
View 5 Replies View RelatedI'm using a custom kernel but the Intel Broadwell GPU hangs and gives the following error messages:
Code: Select allJan 2 19:24:06 debian kernel: [ 34.734460] [drm] stuck on render ring
Jan 2 19:24:06 debian kernel: [ 34.735563] [drm] GPU HANG: ecode 8:0:0x85dffffb, in Xorg [1925], reason: Ring hung, action: reset
Jan 2 19:24:06 debian kernel: [ 34.735566] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[Code]....
I compiled a 2 custom kernels so far (many custom kernels just 2 that I have used) however, both of the kernels display an error message about EXT3-Fs and unable to load custom options even though all my partitions are ext4.
I have looked around and the only reason I find for those are that the file systems are corrupt beyond repair,However the problems always ments EXT3-fs is a ext3 file system problem and EXT4-fs is a ext4 file system poblem. Why is mine saying EXT3 and some times EXT2 when im using EXT4?
Custom Kernels
Debian 2.6.26.Something with RT patch
Debian 2.6.33 with Rt patch
I would like to create a custom boot disk that would include some programs already installed on my computer, so I wouldn't have to re download them, is there a way to do this?
View 2 Replies View RelatedI recently bought an AMD R7 360 videocard and I'd like to use the free Radeon driver.
Problem is, PCI-ID 0x665f is not present in Jessie's 3.16 kernel sources. The hardware however is supported, it's just not recognized. So I'll have to get the Debain sources and patch include/drm/drm_pciids.h
From the 4.1rc1 kernel I know what to patch and where.
Debian page that explains how to use the Debian build system for recompiling the current kernel from Debian packages?
I've compiled 2.6.35 for my eeepc, but I have noticed that resulting .deb file is 30mb large. After investigating i saw that modules (and maybe kernel) are compiled with debugging symbols enabled.I've checked my lenny router and modules there are without debugging symbols.So stock 2.6.26 from lenny comes without debugging symbols and linux-image .deb file is around 20mb.Stock 2.6.32-5-686 from squeeze comes with debugging symbols enabled - linux-image .deb here is 26mb. (I have used 2.6.32's .config file to build my kernel, then i did make oldconfig.)I guess this is what increase my kernel size, but how to disable it?Or maybe enable stripping of debugging symbols.
View 3 Replies View RelatedI 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!
my wireless doggle is not suppoerted out of box on squeeze.It's based on zd1211rw,just lack the vendor and product id.how can I hack the source and rebuild the driver module?
View 1 Replies View RelatedI'vd a problem with loading modules. Booting gives the this error:
Code: Select alllucas@debian8-1:~$ systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● systemd-modules-load.service loaded failed failed Load Kernel Modules
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
[Code] ....
Always the same error when booting. After a period of time, (Graphical User Interface) the mouse click no longer operates, also text input isn't possible.
I had no access to the system at all, even crt alt F1 stopped working, also text input was no't possible. so reinstall was the only option. Maybe there is a connection with this two errors.
I've reinstalled Debian 8 several times. Still, both errors stay.
The same happend again (in the GUI) is nothing possible, no txt input, no mouse click), but now I have access to the system, ctr/alt F1 is working.
I'm having problems to compile XIllybus kernel module. As this guide explains, [URL] ..... (on the top of page 8 of 25) I unpackaged the tar.gz file and compiled the kernel module by typing the make command in the proper path. When I compile the module with make command, I get the following error:
make -C /lib/modules/3.16.0-0.bpo.4-amd64/build SUBDIRS=/home/xillybus/module modules
make: *** /lib/modules/3.16.0-0.bpo.4-amd64/build: No such file or directory. Stop.
make: *** [default] Error 2
/lib/modules/3.16.0-0.bpo.4-amd64/build path does not exist. What does it mean? Should I have to install some kernel packet? www does not work for me.
I'm trying to build the kernel module for dvbhdhomerun. The problem is the linux kernel headers provided by Debian do not have the dvb header files. Trying to set up my own kernel source tree to use is not working out so well.
I'm following the instructions in the Debian section here: [URL] ....
My first try compiled, but the modules ender up under /lib/modules/3.2.51/extra instead of /lib/modules/3.2.0-4-amd64/extra. Why?
I tried to start over, but noticed this while running apt-get source linux-image-3.2.0-4-amd64:
Code: Select allReading package lists... Done
Building dependency tree
Reading state information... Done
Picking 'linux' as source package instead of 'linux-image-3.2.0-4-amd64'
NOTICE: 'linux' packaging is maintained in the 'Svn' version control system at:
svn://svn.debian.org/svn/kernel/dists/trunk/linux/
[Code] ....
The failure to verify the signature has me concerned, but beyond that, what do I do about the different version number when compiling and installing the kernel modules?
I've installed Debian 8.0 Netinst ISO on my old Ubuntu 8.04 Desktop to upgrade it for banking access requirements. I've installed the 32 Bit Jessie (Debian 8.x) and I am trying to get GWintree installed from the .deb file on the Internet. It was missing libtiff4, and I contacted the author about the missing lib. He rebuilt GWintree for Ubuntu 14.04, and uploaded the new .deb file. Now, when I try to install the deb with gdebi, I get another missing lib named libjpeg8, which is a runtime module. libjpeg8 is not available in Jessie, but is available
in Stretch (unstable) & also SID.
Is it possible to change my repositories, and add just the libjpeg8 module and get GWintree installed. That assumes there aren't other missing libs as well. If not, what is the best way to get libjpeg8 backported to Jessie? Who does this type building? GWintree worked well in Squeeze & Wheezy! I hope I can get it working in Jessie.
I' d like to apply this patch into my squeeze: [URL] Can someone pls explain howto apply driver diff patch into a custom kernel?
View 9 Replies View RelatedI recently got a new dell studio 1558 with radeon hd 5470 video card. So far have had lot of small problems and such but been able to fix the via google and a lil luck but now I'm stumped with this one and decided to try and turn here for some possible help. Now on to the details.
Distro - Debian lenny with 2.6.33.3 custom kernel propriatory lgrfx 10.4 drivers installed direct from ati (installed no problem)after compiling the kernel and installing the drivers from ATI my card IS recognized and X will boot up with the proper resolution, but that's where all the problems start. I can no longer switch to virtual terminals (ctrl-alt-F1,F2,F3,F4 etc) and graphics performance in X is extremely poor due to the fact that 3D fails to initialize, and catalyst control fails to load (it tries to but then just disappears)
I built a kernel-module for a new usb wifi-card. This worked well and resulted in a 8821au.ko-file. But now I'm trying to load this kernel module since half an hour and it doesn't work. I copied the ko-file into /lib/modules/3.16.0-4-amd64/kernel/drivers/edimax. If I just type
Code: Select allsudo modprobe 8821au
I get a
Code: Select allmodprobe: FATAL: Module 8821au not found..
But if I enter the full path inside the /lib/modules/3.16.0-4-amd64-folder:
Code: Select allsudo modprobe -v ./kernel/drivers/edimax/8821au.ko
it seems to work:
Code: Select allbuiltin ./kernel/drivers/edimax/8821au.ko.
But lsmod doesn't show me the module after that.
I also added
Code: Select all./kernel/drivers/edimax/8821au.ko
to /etc/modules but this also doesn't seem to work. When booting I get an error-message, but it's too fast to read it and I can't find the right log-file, where the booting-part with the "[ OK ]"-messages is reported.
So my driver is ready, the onliest thing which I can't get working is loading it as a kernel-module.
I upgraded my kernel in my Debian Lenny to version 2.6.32-bpo.4-amd64 to fix a problem with a software and ALSA-related issues. The thing is that now, when I boot, eth1 is not enabled and I have to "load" (I guess) the driver each time. To do this, I go to the folder where all the files for the drivers are and I run:
modprobe lib80211
and then
insmod wl.ko
That I got from the readme file. That gets the wireless working perfectly again, but when I reboot the wireless is dead again and I have to run the commands above again. I imagine that what I should do is to build the driver again, for my new kernel. However, according to the readme file, before I need to install linux-headers-generic and build-essential. With build-essential, it says it's already the newest version, and with the linux-headers, I don't know which one should I install for my kernel! I thought it would be the linux-headers-2.6.32-bpo.4-xen-amd64, but when I tried that, this is what happened:
debian:/home/hernan/Programas/hybrid_wl# apt-get install linux-headers-2.6.32-bpo.4-xen-amd64
Reading package lists... Done
Building dependency tree
[code]....
So the warning says something about the MODULE_LICENSE being missing... how to build the driver again to make it load each time I boot?
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 rpertoire /var/lib/dkms/nvidia/173.14.27/build
[code]....