I try to create/compile custom kernel from kernel.org. But is that a problem later to install headers? For example to install nvidia driver from nvidia.com I need header from my kernel and I havenot got all kernels or not? I am not very sure about this. Can somebody explain a littel, what happned with custom kernel and headers? Are there linux-headers only for some kernels? Which ones? All from kernel.org?
View 2 Replies
Yesterday, I think I did something stupid: I removed kernel-headers, gcc, glibc-devel and glibc-headers. My box is a CentOS 5.4 webserver (it has loads of packages installed, but that was done through Virtualmin config, so it's quite coherent all in all). The thing is that now I need to reinstall at least the headers and glibc, but hey! this is what I get :
[Code]...
Just spent three whole days barking up the wrong tree, solving Fedora 11 and Fedora 12 boot failures because the correct hypothesis was illogical: installation did not update/modify the initrd.
The first couple of times I installed Fedora 11 on the HighPoint Technologies RocketRaid 2640x4, the installation inserted my "custom" driver module (rr26xx) into the initrd, permanently, so that the system booted off the controller card for which the custom driver was inserted. (I yelled about this success in this thread: [url]
My most recent installs of BOTH F11 and F12 on the RocketRaid failed to properly set up the boot. It turns out that the "rr2640" module I "slipstreamed" into the installation process was *NOT* permanently added to the initrd by anaconda. (F12 gave me "no root device found boot has failed, sleeping forever", on boot; F11 hung also, without such error, I presume, during the init script execution). Because of limited resources and time, I only know for sure the module was missing from the F11 initrd, and am ASSUMING the same was the case with F12.
The only difference between the successful installs and the ones with failed boot is that the successful installs were made on a single-drive (JBOD) mode on the controller; whereas, the failed ones were placed on RAID 5. But, AFAIK, the created logical device for the card is "/dev/sda", in both cases, and the kernel can not distinguish between the two cases (or can it?). Thus, the inconsistency cost me a lot of time, and is still inexplicable to me.
Question: What is the best way to deal with custom drivers, today? There are custom spins, and many tools, like isomaster. Stupid question: Is there a way to modify the initrd inside an installer ISO -- be it for CD/DVD/USBboot drive -- beefing the init RAM disk with whatever modules you'd like, for the boot process (using, say, isomaster)?
And what makes anaconda understand that a module must be added to the initrd ? How can one force anaconda to do so?
How does moving to dracut as the initrd tool affect any/all of the above?
been a programmer for a while; on windows mostly but I'm starting to learn all that I can about linux software.I've picked up a funky little NAS which has ssh access to its (i believe uLinux) environment. I've also managed to find a compiler for it (gcc compiled for ARM - GNU/Linux).The plot thickens.I've had some headaches but I've now managed to compile Apache2 without DSO support... so far so good.In getting this far I've been told by a number of people i will need "the headers" specific to the device (the NAS didn't come with source code).
Since Apache 2 (without DSO) compiled fine I know i definitely have some headers. But DSO won't build with errors that lead me to believe it may be a header issue.The question:So i have some headers which educated guess work suggests to me that these are the headers for the std c/c++ libraries.finding "the headers" to know what they are the headers for
I have a fairly aged Pentium 4, RAID, desktop computer with Fed 11. I started off with the 686 PAE kernel and update it whenever the update software tells me to. Some time ago I downloaded an NVidia driver which said it needed the 586 kernel so I installed that as well.I then uninstalled the NVidia driver as it caused some minorish problems without any improvement to the graphics. The bottom line is I now have the last three 686 kernels and the last three 586 kernels, which I'm pretty sure I don't need. The machine seems to run fine whichever I use with no discerable differences.My questions are, what is the difference between the two types, which should I actually use and how do I get rid of the other. It would at the very least reduce bandwidth use when updating.
View 3 Replies View RelatedMy MythTV system is running under F12. It is in "appliance mode;" all configured and happily doing the PVR thing without a pressing need for upgrades.However, there is a feature in the upcoming 2.6.32 kernel that I'd like to take advantage of; internal support for a certain capture card.
I see 2.6.32 mentioned as part of the F13 release. My question is, will it also be available for F12 . . . maybe sooner than the F13 release?Another way to put this is: How wedded are Fx releases and kernel releases? Is a major kernel goalpost like 2.6.32 the reason why Fx releases are made?
i installed the PAE kernel and was wondering if it's safe (and how) to remove the non-PAE kernels. from the system.This is F13.
View 2 Replies View Relatedoperating system : fedora 15 kernel 2.6.38.8-32.fc15.x86_64 bugs : when updated with the latest update it always log into the fallback, i read somewhere that the nvidia driver version 275.09.07 does not work correctly with gnome shell so i did reinstall it and it fix the log in issue but now it gives me a screen with lots of bad mixed color after returning back from suspend. kernel 2.6.38.8-35.fc15.x86_64
bugs : it gives me this error at boot time "alg: skcipher: Failed to load transform for ecb-aes-aesni: -2" and this message does not save at boot.log anyone have any idea how to fix those issue
I use lilo, and have two different kernels. One is newer and use KMS with it.What I would like to do, is to be able to set vga=xxx for only one of the kernels.Is this possible?I would also like to be able to code into lilo.conf options that I pass on the commandline, but am unsure how to do thisedit:
adding my current lilo.conf
append=" vt.default_utf8=0"
boot = /dev/sda
[code]....
I am using Ubuntu 9.10 and am facing an issue while booting up. It goes into initfs command prompt on one of the 4 kernels that show up in the boot menu. I tried to look around for a likely solution and hence did the following:1. ran "chkdsk c: /f" in my windows partition.2. Added "rootdelay=90" in "/boot/grub/menu.lst" file.This is how my /boot/grub/menu.lst file looks and the problem is with the kernel 2.6.31-20-generic:
title Ubuntu 9.10, kernel 2.6.31-20-generic
uuid ceacd229-2b68-41bf-a967-8ee470085fd8
kernel /boot/vmlinuz-2.6.31-20-generic root=UUID=ceacd229-2b68-41bf-a967-8ee470085fd8 ro quiet
[code]....
I have an issue with apt-get that has been bugging me, namely that it tries to delete kernels I did not specify for deletion.
This is an issue that has been present over at least the last three releases and is present for both 32bit and 64bit, so it might actually be a feature and not a bug, however I can't see it's usefulness.
When I use the command:
Code:
sudo apt-get remove --purge 2.6.32-21*
It not only tries to remove the kernel 2.6.32.21 but gives me the following output:
Code:
sudo apt-get remove --purge 2.6.32-22*
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting linux-headers-lbm-2.6.32-24-generic for regex '2.6.32-22*'
Note, selecting linux-headers-2.6.32-21-preempt for regex '2.6.32-22*'
[Code]....
When I go through with this command to remove the oldest kernel on the system, it will actually delete all kernels present on my PC (as I painfully learned when I first tried it). Why is that the case? Wouldn't it make more sense to only remove the kernel 2.6.32.22?
I am running Maverick and I have installed through the terminal those two kernel versions (26 and 27). Once I restart the system and choose either of those kernels to start, I can only work in console mode. I am using 2.6.35-23 without a problem and I have been having this same problem with version 25 too.
View 2 Replies View RelatedI'm having an issue with my suspend, and nothing seems to be fixing it. Every time I suspend, the computer starts up as if it were shut down. Somebody recommended that I use a previous kernel, such as 2.6.35-28, rather than the current kernel, 2.6.38-. When I open Synaptic, no previous kernels are listed, so I wanted to see if anybody else knew how to install previous kernels.
View 1 Replies View RelatedWhat is the best way to uninstall old kernels in Ubuntu 9.10?
View 8 Replies View RelatedI've installed glibc and downloaded 2.6.33.3 tar ball from kernel.org.
I created a symlink /usr/src/linux -> /drive/linux-2.6.33.3
But there's something missing because when I run
make mrproper
make config
I get errors about not finding headers:
asm/socket.h
It seems like I am missing some other symlink, I've tried creating other links, like /usr/include/asm -> /drive/linux-2.6.33.3/arch/x86/asm
Does it mean that a 64 bit version is not multi-core?
View 11 Replies View RelatedI am using CentOS 5.5. After upgrading i have at present 4 kernels in the menu.lst.If i try to remove any kernel, 2.6.18-194.3.1.el5.i686 via Package Manager, i am told that i am removing critical software for system functionality etc. How delete older kernels?
View 4 Replies View RelatedI have several classes that I use for multiple programs. Where should I keep the h/cpp files so I only have to add the #include for the compiler to find them?
View 9 Replies View RelatedMostly just curious since everything works but in the essence of learning I'd like to know what this means.
Code:
The following packages have been kept back: linux-generic linux-headers-generic linux-image-generic 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
It is easy to see what is held back, so the question is why? I'm running Linux Mint 10 Gnome edition.
Code:
Linux 2.6.35-22-generic #35-Ubuntu SMP Sat Oct 16 20:36:48 UTC 2010 i686 GNU/Linux
I have 3 kernels installed. When I look at my installed kernels with yumex or package kit all I see is the latest kernel. rpm -qa lists them and I was able to remove the oldest using rpm -e.Is this some new feature of YUMEX and package kit to only show the latest version installed?
View 6 Replies View RelatedI'm sure there is a thread on this somewhere, but after looking though the first 100+ search results, I can't seem to find it.
After a kernel update today, I noticed that new kernels are not being added to my grub menu.lst (so consequently, I was running an older kernel).
Any obvious reason why this would happen (kernels being installed normally, with yum update)? I thought the whole process was supposed to be automagic.
Would it have anything to do with the fact that I just kept my F11 menu.lst, and added a F12 kernel to it when I installed F12 (to a separate partition), then eventually (today, finally) removed the f11 kernels from it?
Here's my menu.lst, in case it's useful:
Code:
The latest kernel screwed up my laptop and I would like to reload the
previous kernel to get back to where I was but I dont see it as available
anymore... Is there an archive to pull previous versions from ?
2.6.33.6-147.2.4.fc13.i686
I'm unable to boot my box since the first 2.6.34 kernel arrived.I hoped the second will fix the problem but it didn't.The display just enters in the power save mode after a second and that's it.The system boots fine with the 2.6.33.8-149.fc13.i686 kernel.The lspci result is:
Code:
00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02)
[code]....
Install fglrx driver for ATI but it just installed for one old kernel 2.6.34.6-54. and 2.6.34.6-54.fc13.i686 i have also kernel 2.6.34.7-56.fc13.i686.PAE, how can i compile the fglrx for it?can i just copy fglrx.ko from /lib/modules/2.6.34.6-54.fc13.i686.PAE/extra/catalyst/fglrx.ko to /lib/modules 2.6.34.7-56.fc13....
View 1 Replies View RelatedI'm running FC 13. I believe that the base install is kernel 2.6.33.6-147.x86_64. That is the last version of the kernel that I have installed that includes an initramfs file. Neither 2.6.34.7-56 nor 2.6.34.8-68 installed an initramfs file. Since my root volume is in LVM, I can't boot with those kernels. I saw in another post that doing a "yum install kernel" would install the missing files. I tried that and it tells me that kernel-2.6.34.8-68.fc13.x86_64 is already installed and latest version.
I ultimately want to upgrade to FC 15 because I've got a new nVidia video card and need driver 270.41.06 for fc15. My fear is that if I upgrade I might not get the initramfs files in the new versions of FC and end up with an unusable system. Is there a way to add the initramfs files for the newer kernels and/or will I have the files after an upgrade?
I am trying to install some patches and drivers needed for a wifi card, but im getting an error that says: "build your kernel with CONFIG_LIBIPW=m." How can I recompile the kernel to add that? And can I do it without having to download a new kernel package? (i mean recompiling the existing kernels)
View 2 Replies View RelatedI've been using the instructions on the Wiki to compile audio drivers for the Macbook Pro 5,3, and it has worked for a while. But I tried doing the same thing with kernels 2.6.31-17 and 2.6.31-18, but it seems to have no effect: alsamixer only shows one channel (Master) which does nothing, just like a fresh install. Does anyone have updated instructions for these kernels?
View 9 Replies View RelatedInstaled ubuntu 9.10 and i like it more than win xp because you can setup it in your way. Now my problem is when i compile older kernel with my setup and restart ubuntu i get grub with no loads like config is gone or something so i cant boot any of default kernels. I folowed this guide for compile [URL]... because i want to create lan hlds server with 1000hz kernel and have best response and latency server. can anyone confirm is this guide working with this 9.10 version or problem is that i cant set older kernel with newest ubuntu? Compiled few times and annoyed to wait again 2h just to try some other explanations i found on internet.
View 1 Replies View Relatedyesterday I removed old kernels via. the synaptic manager- I'm 100% certain I did not removed the latest stable kernel, and the version before- I did however removed the oldest two. Now after restart I'm dead in the water- i cant get past the initial boot- the screen goes black. I i'm running ubuntu 9.10 double-booted with windows vista, and right now I cant even get into vista...
Let's say that I messed up with removing old kernels, and removed sth, that shouldn't be removed- but how does this mess up vista?
I can't boot any kernels now, even old ones...
View 8 Replies View Related
