i have recompiled kernel on my netbook (lenovo s10-3t).suspend works correctly but then i cannot wake up. i think i just missed some kernel options.what options must be set for suspend/wake up?
View 7 RepliesHow do I force recompilation of the kernel .deb packages. After a small change I make to the sources without having to clean the sources and recompile the whole kernel again?
Code: Select all$ fakeroot make -f debian/rules.gen setup_i386_none_686
$ fakeroot make -f debian/rules.gen binary-arch_i386_none_686 binary-indep
Calling the second command again does not recompile the modified code, just recreates the .deb packages.
If I use:
Code: Select all$ make -f debian/rules clean before the build command, then it will recompile everything which takes ages.
How can I force recompilation of the files/objects I changed (and dependencies)?
I use this guide: [URL] .... ('Building only a single kernel variant' section)
I recently switched back to Debian after getting fed up with Ubuntu. The one feature that I haven't been able to get back since the switch is Wake on LAN.If I turn on the computer and watch tcpdump, I can see the packets hitting my machine. I don't think it's a router configuration issue.If I shut down from windows, WOL works.Another sign that it's not a networking or BIOS thing.Here's some stuff I've tried:When I boot up in linux, if I run ethtool eth0, it tells me that wake is set to g (which every guide I've read says is correct).Just in case, I added "post-up /usr/sbin/ethtool -s $IFACE wol g" to /etc/network/interfaces (as shown here: ewtopic.php?f=5&t=42049&p=244736&hilit=wakeonlan#p244736). Also added same thing for post-down.
In /etc/init.d/halt, I changed NETDOWN to no (also from previous guide) to keep my eth card from being shut down.Also changed /etc/init.d/networking to exclude eth0 (as documented in Added "pre-down false" to /etc/network/interfaces.. trepid+wol), to keep eth0 from being shut off.Anyway, I'm guessing that either there's another script somewhere shutting off eth0 or I'm completely wrong in assuming that's the problem. I've been googling this problem for a couple weeks now and I'm totally out of ideas.
I'm am able to WOL my computer when it has been halted (or shutdown, which is basically the same thing for the problem I'm facing). The problem comes when I try to WOL the computer when it is suspended or hibernated. Then, it does not work.
I've been investigating for a while and have found that when halting, the following is done in the /etc/init.d/halt script:
[code]...
But I don't know which script must be modified in case I want the network not to be brought down when the computer is suspended or hibernated.
Suspend worked before I completely reinstalled Testing from scratch. Now it seems to suspend OK, but when it tries to wake up it fails. Details here: [URL]
View 6 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 recieve the following error:
Cannot find swap device, try swapon -a
/bin/echo: write error: No such device
If I type swapon -a, I get something like this:
swapon: cannot find the device for UUID=4d79c009-9464-41d5-9f78-90644bca9ba3
It worked great before I did the upgrade... I've upgraded to 2.6.37-rc5.
May i know how to do kernel recompiling.step by step explanation will help me. i am new to this.
View 1 Replies View RelatedIf I compile the kernel once fully and if I wan't to make a minor change how do I do that without having to go through the whole recomiliation? Commands like "rpmbuild -bb" and "make rpm" seem to recompile everything but it should just compile the changes I made.I'm using Fedora 12 with the latest stable kernel.
View 11 Replies View RelatedI only have basic experience recompiling a Linux kernel, and I have a question about adding dynamic modules.In case I want to add a brand new module, do I need to recompile the kernel to include a reference to that new module, or is simply compiling a kernel with generic support of dynamic modules all it takes to add whatever modules I need later on, without recompiling the kernel and rebooting the host?
View 2 Replies View Relatedif i wanted to just download and install a module, how does centos have it where i don't have download the source and recompile the whole kernel withthe module enabled? i read about install kernel-devel but nothing much more on using it. for instance, if i wanted to download ext4 module and have the kernel use it?
View 1 Replies View RelatedI'm currently upgrading my clients' CentOS 5 installation to use httpd-2.2.14 as we need it for the server to past some of the Hardware checks used in the PCI [Payment Card Industry] security test. I was basically wondering if anyone had the standard CentOS 'configure options' for building httpd/Apache so I could copy them to ensure it is a straight replacement for my existing 2.2.3?
[Code]...
I just up-graded to the latest version of the stable 11.4 64bit kernel on my laptop and it appears that the repositories have not compiled the VirtualBox driver module for the current kernel ... When I make /vboxdrv setup the message is:
Recompiling VirtualBox vboxadd kernel module, NOT. It has been packaged
I think this means that the installed module will not recompile has it was packaged. My kernel version is the lattest :
2.6.37.6-0.5-1
And my VirtualBox was installed from the Virtualization repos (4.0.8.11-1) even made the Vendor change and all. The version Before the lattest (4.0.4-1.6) did not work either. With the same problem. It is very easy to install VirtualBox from the Sun site and every time there is a Kernel up-date one can always make /etc/vboxdrv setup.
I use CentOS 5.3 with kernel 2.6.18-128.1.6.el5 for Clonezilla. It would be simpler for me if any of IDE or SATA drives detects as /dev/sdX device. Because when I cloning computers with Clonezilla it is matter which type of drive connected to cloned computer. So I must firstly clone computers with IDE drives, after that with SATA drives. If all drives would detected as /dev/sda I would can clone all computers at once! Is there simple way to enable new libata library without recompiling kernel? Is there already compiled kernels with this feature?
View 7 Replies View RelatedI 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 am using DEBIAN 6.0 and I wannna update my kernel from 2.6.32 to 2.6.38. Every time, I do it but after the installation & rebooting into the new kernel it gives me error "UNABLE TO BOOT INTO THE KERNEL".
View 1 Replies View RelatedI 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 RelatedI have a set of vm's with stable, testing, and sid to keep track of how things are going. When I did an apt-get dist-upgrade with squeeze last week, things seemed to OK (350 package updates) until the end. It didn't seem to like and / or was confused by a kernel dependency.
I am not too concerned yet. Because these are in vm's, I do a snapshot before any significant change. I can futz around with impunity because I have that backup.
I re-booted, and tried the apt-get dist-upgrade again with same results. I think I also tried apt-get -f install.
So I reverted to the snapshot, and will simply try again in the future. I recall that with lenny as testing, the font-desktop was really screwed up for about a period of 6 weeks.
However, just in case someone else runs into this:
1) a re-boot worked, but the failure of apt-get made me nervous enough to revert.
2) waiting for corrections has seemed to work in the past (with a single exception with a 4-disk SCSI software RAID10 update that failed to re-boot lenny successfully after what seemed to be a minor update -- that was on a real system, not a vm. I haven't gotten back to look at that.)
I am running a Fedora 12 installation in my bedroom as a slave mythtv frontend. I have set it up to be able to put the PC to sleep and wake up with a MCE remote. This has been working for near on a year now with no issues. Yesterday I did a yum update and ended up with kernel 2.6.32.16-141.fc12.i686.PAE (up from 2.6.32.12-115.fc12.i686.PAE)
Now everything seems to work fine however I can put the PC to sleep with the remote but I cannot wake it up with the remote. a cat of /proc/acpi/wakeup shows
Code:
DeviceS-state Status Sysfs node
SMB0 S4 disabled pci:0000:00:03.2
USB0 S4 enabled pci:0000:00:04.0
USB2 S4 enabled pci:0000:00:04.1
US15 S4 enabled pci:0000:00:06.0
[Code]...
At the grub prompt if I select the old kernel 2.6.32.12-115.fc12.i686.PAE then the computer will start up with no graphical prompt (need to figure out how to work kmod-nvidia i guess), but I can use the remote to put the pc to sleep and wake it up again. Also using the old kernel and telneting into the PC I see that /proc/acpi/wakeup is no different. Does anyone have any clues on hoiw to get wakeup to work with this new kernel? Or how do I roll back everything to the older kernel and get my graphics driver back (i tried to reboot with old kernel and then yum erase kmod-nvidia-PAE and then yum install kmod-nvidia-PAE but no luck.
Another thing worth noting is that I can wake the computer with the power button, just not the USB remote. THere is also nothing in the motherboard bios for setting wake on USB.
That the Linux bridge configuration does not work afer I upgraded the kernel to 2.6.33.2. Why I can't find the device vmbr0?
[Code]...
I've had this problem two times before and solved it once by following a guide, the other time by formatting. It always happens when it fails to wake up from suspend. Usually I am unable to even mount the drive or access the files. This one is different in that now I can actually access my files for the most part but this comes up on boot. I backed up most of my files (except it still says I don't have permission to access some of them) but I would like to get it back up and running without formatting. If I boot in recovery mode it stops at this. I took a picture but I rewrote some of it here.
Firewire_core: created device fw0: GUID 00016c000061b4b4. S4???
in/sh: cannot open ro
Kernel panic - not syncing: attempted to kill init!
Call Trace:
[<c05c8283>] ? printk+0x2d/0x32
etc
Image posted here: [URL]
is it save to install linux kernel 2.6.35.2 on Debian Lenny 5.0.5 or stick with automatic updates...
View 14 Replies View RelatedI am trying to compile a kernel 2.6.31-12 in my machine which is running ubuntu 9.0(kernel version 2.6.31-14). I don't have internet connection on that machine. I somehow downloaded the kernel sources on some other machine and copied it the my PC which is running ubuntu.I have installed the kernel sources (.gz file) by un-zipping and un-tarring the archive. For compiling the kernel I am following the traditional approach:
1. make oldconfig ( make menu config is not working )
2. make dep
2. make clean
3. make bzImage
4. make modules
5. make modules_install
6. make install
7. Modify the /boot/grub/grub.cgf
I didnt encounter any error in the above steps till step no. 6. However in the
step 7, I am not getting the /boot/initrd.img-2.6.31.12 file which is needed for the ramfs. However I am getting the vmlinuz file in the /boot.
I'm trying to get WOL to work on my web server built on an ASUS P4A800D-X motherboard (which supports wol).I have it enabled in my BIOS and I've tried several different tools with no results, including my dd-wrt based router which has this functionality built into the firmware.All the guides I've read say it has to be enabled in the driver settings in the Windows Control panel before it will work, but I'm running Ubuntu Server 10.04.
Is there any special steps that must be taken in the OS to enable my web server to power on from the LAN? I've never used this feature before and would like to just shove my web server in a corner some where and have 100% remote control from my main PC.
On Lenny, due to some compatibility issues: kernels before 2.6.26 don't recognize part of my vaio laptop's hardware, while the last drivers of my videocard (version: 260, card: nvidia gt 230m) suffer some incompatibility problem (this is one of the most problematic computers I ever had), so I have to use version 256, which doesn't work with kernels after (perhaps) 2.6.32. So, I suppose I have to check each kernel between that two versions and hope that one of them will be ok. I searched quite deeply over the net but didn't find anything related to debian, except for generic kernels [URL], but as someone told me that it's better if I only install stuff from the stable repository or backports. What can I do? Is there any backports archive or something like that? Otherwise, what should I do?
View 5 Replies View RelatedI'm getting some trouble with Wake on Lan. The main question is: when I shutdown a PC through Windows, the WOL works well, but it doesn't happen when I shutdwon the same PC through Linux. It happens in all of my PCs here in the company.
View 8 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?
Upgraded Wheezy to Jessie, by changing my apt sources to point at stable instead of wheezy. Ran upgrade, and dist-upgrade, all fine etc.
Then tried to update the kernel by installing linux-image-amd64 package .. seemed to work fine, but after a reboot my kernel version still says 3.10.23
What have I missed?
Code: Select allroot@hostname:~# apt-cache search linux-image
linux-headers-3.16.0-4-amd64 - Header files for Linux 3.16.0-4-amd64
linux-image-3.16.0-4-amd64 - Linux 3.16 for 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)
[Code] .....
I have a MyBookLive where i installed a Debian 2.6 kernel. The system is running fine so far. Because of an error message when apt-get upgrade (udev) i tried to upgrade to 3.16. Here's what i did:
- apt-get install linux-image-xx
- apt-get install linux-source-xx
- extract the source
- copied the old .config from running 2.6 kernel over to the 3.16 directory
- make oldconfig
- make uImage
- make modules
- make modules_install
- copied uImage to /boot
No error messages because its a headless device - its just not booting up.
I was wondering if anyone can assist me. I am looking to build a server with Debian as the host. When I installed Debian (Squeeze) the default kernel was "2.6.32-3-trunk-amd64". When I tried to install 'Virtualbox' application, I got a failure because I didn't have the 'kernel-headers' installed on my machine. I noticed there are no specific header package the 'trunk' kernel I was using. I have a few questions so I guess I should begin:
Is it safe to remove the 'trunk' kernel and boot my system on just the regular 2.6.32-3-amd64 kernel? Is this OK or not recommended? Please explain whatever is the correct answer. This is my 1st time using a 'Trunk' kernel so I don't know the in's and out's of it.
If I am using Debian 'Testing' for virtualization via 'Vbox', is there a specific kernel I "should" be using?