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 RepliesI'd like to change the existing kernel module (driver) file and compile a custom kernel.
Is this the correct way:
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 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 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'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!
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 am trying to get my Debian system running. I have an older Dell Precision 490 with two dual core CPUs. It has 16G Ram, an 150G Intel solid state drive, a 230G data drive, and a 600G backup drive. I have two Samsung monitors attached to the NVIDIA Geforce FX 5xx card. I have been using this machine for several years with Etch, then Lenny, running KDE 3.5. I recently needed to upgrade to Squeeze and KDE4 and have had nothing but problems since. I keep having issues with the video drivers, every time I touch anything the drivers seem to upgrade from the legacy 173 to the current 195.
There have been other library compatibility issues as well (gclib) and the machine has not been stable. This morning the system was running very slowly with X running at 100% (from top) and then the entire system froze. After a hard reboot, X did restart. The Xorg.0.log has the following message:
"Failed to initialize the NVIDIA kernel module! Please ensure that there is a supported NVIDIA GPU in this system, and that the NVIDIA device files have been created properly..."
When 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' 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 RelatedSqueeze's latest update has upgraded my kernel from 2.6.32-3-686 to 2.6.32-5-686.My wireless stopped working and then I realised that I had to rebuild the wifi modules. I had followed this earlier.URL...For this new kernel, which I step of the process should I repeat? Rebuild module? Or just do a modprobe?
View 4 Replies View RelatedMy problem is that it won't load the dkms module and Virtualbox will not run.
View 14 Replies View RelatedI'm trying to use module-assistant to add the vboxdrv using instructions also found here in the debian forum. However, m-a can't find the linux-headers because it looks for the package linux-headers-2.6.32-5-trunk-686. I attempted to specify were the headers were by using:
m-a prepare --kernel-dir /usr/src/linux-headers-2.6.32-5-686/
but also doesn't work. Instead, I get the error:
Bad kernel version specification at /usr/bin/m-a line 566.
Anyone knows how to work around this?
By the way, the reason I am doing this is because when I installed virtualbox (following the instructions in debian wiki) there's no vboxdrv. When I try to modprobe it, I get:
FATAL: Module vboxdrv not found.
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 RelatedHow do I determine which nVidia kernel to use with my system? I'm running a GeForce9800GT
View 11 Replies View RelatedI'm encountering a problem running X and Gnome from a Xen-enabled Kernel with NVIDIA Binary driver compiled with IGNORE_XEN_PRESENCE=y on debian squeeze
Hardware:
NVIDIA NVS 5100M
Kernel:
Debian Squeeze : 2.6.32-5-xen-amd64
NVIDIA Kernel from the official package
Boot and module loading are successful, but when X starts, I only get a black screen. I attached here my Xorg.0.log, however it doesn't seems to have any problem.
I spent quite a lot of time jumping from one thread to another trying to fix a problem with my NVIDIA drivers in Lucid. I was getting the error message on startup: NVIDIA: Failed to load the NVIDIA kernel module ...Failed to load module "nvidia" (module-specific error, 0) No drivers available".
After a lot of trial and error, this is what worked for me (I have updated this thread following [URL]):
- Download the latest NVIDIA driver from www.nvidia.com/page/drivers.html
- In the terminal cd to the directory where you downloaded the driver package (e.g., $ cd Downloads)and make it executable (e.g., $ sudo chmod +x ./NVIDIA-Linux-x86_64-256.53.run)
- Edit blacklist.conf $ gksu gedit /etc/modprobe.d/blacklist.conf
and add the following lines to the end of the file:
#recommended by http://ubuntuforums.org/showthread.php?t=1467074
blacklist vga16fb
blacklist nouveau
blacklist rivafb
[Code].....
I updated kernel and everything seemed ok, except HD-PVR is locking up and recording only two minutes of every show it records. So, I have gone back to my previous kernel, but it seems that X isn't starting:
Code:
(II) NVIDIA dlloader X Driver 195.36.31 Thu Jun 3 08:27:29 PDT 2010
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[code]....
Fatal server error:no screens found I had done a yum install kmod-nvidia for the newer kernel. I am thinking I need to get the kmod for the current kernel again (2.6.32.12-115.fc12.x86_64 #1 SMP Fri Apr 30 19:46:25 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux), but am not sure how that is done?
Squeeze-beta was my first foray into Debian, and I love it. I changed my setup to a rolling setup with testing (Wheezy), and have done that for several months. Lately, I got a new kernel, but it reboots to a terminal rather than GUI (I'm a simple laptop user). I think it's because of the NVIDIA drivers, and here is what I've tried (meanwhile, I'm using the previous kernel):
# apt-get install module-assistant nvidia-kernel-common
# m-a auto-install nvidia-kernel${VERSION}-source
A blue screen appears that says:
module-assistant error message Bad luck, the kernel headers for the target kernel version could not be found and you did not specify other valid kernel headers to use.
You can try:
module-assistant prepare
or
apt-get install linux-headers-2.6.38-2-amd64
I have done both, rebooted, and I still get the blue screen. I also see this message:
nvidia-kernel-source was not built successfully, see:
/var/cache/modass/nvidia-kernel-source*buildlog*
...and I have copy/pasted the file below (which omits lines 101-200 because this message is too long then):
/usr/bin/make -f debian/rules clean
make[1]: Entering directory `/usr/src/modules/nvidia-kernel'
test -f debian/control || cp debian/control.template debian/control
[code]....
I've posted here before (viewtopic.php?f=5&t=66322) about problems arising from my attempts to get an nVidia driver to work with my custom kernel. Now those problems are all fixed, and I'm back to where I was: the built kernel boots fine, but the nVidia driver fails.
The custom kernel is as near to the stock one as I can make it, I'm just trying to find a working build process at present, before trying to build a later-version kernel.
I used sgfxi with "-! 40" to build the nVidia driver for my custom kernel; it reported that everything was fine.
With stock kernel - 2.6.32-5-amd64 ...
Extracts from /var/log/Xorg.0.log:
X.Org X Server 1.7.7
Release Date: 2010-05-04
X Protocol Version 11, Revision 0
code....
I've built a new kernel (2.6.34) on our workstation at work. It boots and runs beautifully, but there is one minor problem. I created the kernel as a Debian package along with the kernel headers. Upon installing both and attempting to build the nVidia driver for said kernel, the installer tells me that it cannot determine the version and quits. This happens even if I manually specify the path to the headers. What's going on here, did I miss something during my compilation of the new kernel?
View 14 Replies View RelatedI installed the latest kernel liquorix (2.6.35) but when i want to install the Nvidia driver downloaded on the Nvidia website (256.53), i have an error message because Nvidia doesn't found the kernel source tree.
I install linux-image-2.6.35-6.dmz.2-liquorix-686_2.6.35-16_i386.deb, linux-headers-2.6.35-6.dmz.2-liquorix-686_2.6.35-16_i386.deb and build-essential. I don't understand why the installation doesn't works.
I recently installed debian squeeze 32bit on a second partition of my amd athlon 64 X2 dual core machine.Currently it is using linux-image-2.6.32-trunk-686 kernel.But linux-image-2.6.32-trunk-amd64 is available.on the repository.Is it a 64bit kernel or 32bit kernel optimized for amd64 architecture?
View 12 Replies View RelatedI had the 180.xxx nvidia drivers on my FC10 setup.I installed the 185.xxx and am running into issues. It gives me the fatal server error: no screens found message. Before that it says that the nvidia kernel module is 180.xxx and the driver component has 185.xxx. I can't seem to figure out how to uninstall the previous module to make this work. I removed the yum kmod nvidia. I'm running this using sh nvidia.185xxx.xxxx.run . The weird thing is that it sometimes would work but then I would restart and it would break again.
Thanks in advance,
im trying to install the driver for my nvidia GeForce 7300 GS.i have Fedora 12 installed in an Intel duo core 2 processor 64 bits.kernel installed is 2.6.31.5-127.fc12.x86_64...i followed leigh's guide i did the 4 steps but after reboot screen goes blanck and X dont work.the log says:
-> Kernel module load error: insmod inserting './usr/src/nv/nvidia.ko'
-1 no such device
Code:
# dmesg | grep nvidia
nvidia: module license 'NVIDIA' taints kernel.
I searched around and found out the kernel accepts only GPL modules, which is pretty dumb. People recommended using rpmfusion's akmods, but that's what I'm using to begin with.
How can I fix this without having to recompile the kernel?
Code:
# uname -r
2.6.35.6-48.fc14.x86_64