I am trying to update my fedora 8 kernel, is there a way to do that? I build the one of kernel.org but when i want to boot it a get a lot of messages like:
mount: cant find /dev/root
I tried to follow the guide at building a custom kernel for fedora, but thats just for the last supported version of the kernel of fedora 8.
I have builded my kernel through wiki manual, BUT, the kernel-headers rpm-package has not been builded. Now i have only two packages: kernel and kernel-devel. Is that ok? (i think, that it is not ok, because when i build the same version of kernel on x86_64 platform, after rpmbuild command i have kernel, kernel-devel and kernel-headers packages) My CentOS version is 5.2; platform i686; kernel, kernel-headers, kernel-devel packages 2.6.18-92.el5.
View 6 Replies View RelatedI've built a custom livecd. On my cd files like /lib*/dbus-1/dbus-daemon-launch-helper are owned by bin not root and the rws is rwx on the owner permission.
There are many files like this.
After the bunch of updates with current, my custom kernel (2.6.33) can't boot.
The error is:
/sbin/e2fsck: No such file or directory while trying to open /dev/sda6
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate
superblock:
e2fsck -b 8193 <device>
The /dev/sda6 is ext4 and is ok since it can boot with official huge smp kernel 2.6.33.
My custom kernel can boot before this bunch of updates in current.
What i missing in kernel?
I am using FC15.I need a kernel with a different configuration - with the "Preemptible Kernel (Low-Latency Desktop)" option in the Processor Type and features menu. I need this to support my firewire audio device. I would like to build a new kernel RPM from the SRPM so that i can keep a clean system with RPMs for all files, and I don't really want to manually override the kernel bypassing RPM.I am following **exactly** the process described there - I install the SRPM, unpack the source, then use the starting sample config files in the BUILD folder to create a new customised .config file with the new option, then copy this back to the SOURCE folder.
This works perfectly if I make a standard kernel. But I cannot get the process to work if I change the config file. Every time I compile I end up with exactly the standard kernel -- a vanilla i686 kernel, without my custom config.I believe the problem is that when I run rpmbuild to compile the kernel, this process overwrites my config option. I found that there is a script (merge.pl) which creates new config files dyanmically for all kernel options based on fragments in the SOURCE folder. It looks like the script never uses the config file that I am putting into the SOURCE folder.The wiki page suggests using this command to copy my custom config file cp .config ~/rpmbuild/SOURCES/config-`uname -m`
I am using Centos 5 with an old kernel. I want to build the latest version for atheros 5K wireless drivers. So i downloaded, and compiled with the ".config" which is already in /boot , and made it ready to run.
However, whenever i try to boot with new kernel, after choosing it from the grub menu, i got the following error. I tried many many .config files but the result was the same.
Here is the screen capture of the error;
I'm trying this process for a week without any success...
I need to build customs liveCd (usb) to run a distributed application that I'm developing. I have been using debian live-helper to build debian live cds, and it's very flexible, and works. But I'm looking for an alternative to it. I have heard about fedora livecd-creator. What do you think is a better tool?: livehelper or livecd-creator, maybe about good hardware recognition, easy to use, flexibility, reliability, etc. What others good tools are to do this job?
View 7 Replies View RelatedSupposed I have built customized kernel rpm four times in a row and the latest built kernel failed. If I still have all four kernel.xxx.rpm files, is there any way that I could get back the .config file used for each of those four builds? I really could not recall exactly what changes I had made in .config for each build.
View 3 Replies View RelatedI'd like to have a shot at building FBReader 12.1 from source for use within F12 (kernel 2.6.31.9-174.fc12.i686.PAE) but am having problems locating the following .rpm files:
libz and libbz2 -- libraries for zip and bzip2 (de)compression
libfribidi -- for bidirectional text support
lincurl, version >= 7.17 -- for network libraries integration
I've only a small /boot sector and
rpm -qa | grep kernel
kernel-2.6.31.12-174.2.22.fc12.i686
kernel-PAE-devel-2.6.32.9-70.fc12.i686
kernel-PAE-2.6.32.9-70.fc12.i686
kernel-2.6.32.9-67.fc12.i686
abrt-addon-kerneloops-1.0.8-2.fc12.i686
I'm using the PAE kernels, need the devs for nvidia kernel building,can I remove all the non PAE kernels without damage please?
a stock fedora 11 install on my embedded board results in the primary CompactFlash card being driven by the SCSI driver and is called SDA..running my custom kernel which i have slimmed down and yanked out the SCSI stuff because I dont need it, results in my CompactFlash card being called HDA of course driven by the ATA driver.which should I be using? both work just fine.. the CompactFlash card is on board and according to Soekris is actually run from an IDE controller, as there is no SCSI on board..
so im assuming the less amount of system overhead is to run it as IDE?I have no issues running it either way I just want to do whats right.. and what is going to be supported in kernels down the line, as im considering a bump from my current 2.6.30 kernel upwards for my project.
This is (I'm sure) a silly question, but when reading the guide for custom kernel [url] it mentions I need to use yumdownloader to pull the source as an RPM.
How exactly do I find mirrors etc for this (and where do I configure it)?
I've already got the source locally along with the patches I want to use, and want to try this the 'fedora' way. I'd normally just use make/make modules etc, but I've never tried it via RPM.
i just upgraded myself with all available packages from the kde-testing, and fedora-updates-testing repo's. i am dealing with one problem..... i am running kernel:
Code:
@localhost ~]$ uname -r
2.6.32.10-44.fc11.i686.PAE
however,, there are no kmod-wl packages for that kernel, so i have no wireless at the moment. how do i build / obtain kmod-wl package for my kernel? rebuilding the kmow-wl src packages does occure in build for an older kernel:
the command
Code:
rpmbuild -ba --target=`uname -m` wl-kmod.spec
results in:
Code:
Checking for unpackaged file(s): /usr/lib/rpm/check-files /home/-/rpmbuild/BUILDROOT/wl-kmod-5.60.48.36-1.fc11.4.i386
Wrote: /home/-/rpmbuild/SRPMS/wl-kmod-5.60.48.36-1.fc11.4.src.rpm
Wrote: /home/-/rpmbuild/RPMS/i686/kmod-wl-PAE-5.60.48.36-1.fc11.4.i686.rpm
Wrote: /home/-/rpmbuild/RPMS/i686/kmod-wl-2.6.30.10-105.2.23.fc11.i686.PAE-5.60.48.36-1.fc11.4.i686.rpm
Wrote: /home/-/rpmbuild/RPMS/i686/wl-kmod-debuginfo-5.60.48.36-1.fc11.4.i686.rpm
I have a strange and inexplicable problem I've never had before - I can play audio as usual from the terminal on Fedora 14 with my custom 2.6.38 kernel. But, when I log into GNOME, any attempt to use an application that uses audio gives me a "permission denied". The "Sound preferences" shows a dummy output device and no entry in the "hardware" section. Using the distro kernel and a 2.6.33.7-rt kernel from planet ccrma works fine.
Is there anything I'm supposed to build into the kernel that Fedora 14 requires that wasn't a requirement for earlier versions?
I installed openSUSE 11.2 on virtualbox. My host is windows 7. I tried to install the guest additions, but i get an error saying
Code:
Building VirtualBox Guest Additions Kernel Modules...Failed
(Your system does not seem to be set up to build kernel modules)
How should i go about to let my system build kernel modules?
Today I decided to try to install 2.6.31.1 on Fedora 11, x86_64.I did it differently from what appears to be the RPM way, I instead just compiled it from the source.Anywho, ndiswrapper with NetworkManager doesn't work in the new kernel
View 12 Replies View RelatedI am building a series of custom kernels...for one of them i am using a kernel that is older than my currently installed ones.
I am using rpm to install this kernel and it will not install, period. i don't get why i can't install this....what does it matter that i am installing an older kernel? and why is fedora/rpm designed to not let me do this?
Code:
There should be an easy way to get around this, but i haven't figured it out yet. i've googled around, no luck. i bounce between kernel versions all the time without problems on my system, so why is rpm setup for strict versions on a kernel? and is there no way around this, and i just have to delete all three of those kernels, i don't really want to. 2 of them are awesome and i shouldn't have to build them again, that would be complete crap! and i wouldn't have this problem on my debian setup, so why fedora? (i generally think fedora is better)
I opted to install my Linux Fedora distribution, in a SUN VM (Virtualbox). [URL] I have 2 questions:
My current max res available to select is 1024x768. Can I run at 1920x1200? My display indicated that it is 'Unknown'. I don't know if that is in on the deal, or not...
Second question: When installing VBOXADDITIONS_3.1.2_56127, I am getting the error: Building the VirtualBox Guest Additions kernel modules [FAILED]
If I am displaying the log correctly, it indicates: Makefile:23: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again.. Stop Pictures are located here, in the EVGA Linux forum: [URL] I am new to both Linux, and Fedora.
My mission statement: To run Linux using the Fedora distribution, in a VM window under Windows 7 64bit Ultimate, with the ability for scripting using Bash, with the Perl programming language installed, and use Apache Tomcat to monitor both apps, and various VM installs, on numerous Servers via the internet.
I am compiling and installing the custom kernel based on the instructions provided in Building_a_custom_kernel on fedoraproject.org/wiki site.
However, according to the instructions, anytime I change anything in the kernel source files(e.g /driver/ata/libata-core.c), I have to create a patch a rebuild the whole kernel and install this new kernel which takes 2 hours. Is there a simpler way of recompiling what has changed(without creating patch) and try that changed kernel? Since my changes are not in the drivers which can be dynamically loaded but is in the static code of the kernel, it is making life cumbersome.Are there any instructions for this? How does other kernel developers manage this?
I installed ubuntu on my laptop recently and would like to have trim support. (Because I have a ssd drive (crucial c-300 256gb). The current kernel that I am using is the 2.6.32 (standard lucid kernel I believe). Unfortunately TRIM support is only available from 2.6.33 and up. So I thought I'd install a new kernel using this howto:
[Code]....
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 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 RelatedFrom F12 to F13. Is there anything I should remove before updating? I have few programs isntalled from source/binary installers in /usr for example. Would it cause problems?
And is there any chance to be able to switch from a 32 bit kernel to 64 bit kernel during the update? The hardware is capable of this.
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?
I am trying to build linux kernel I am getting out of space after a while. I unpacked it in /usr/src directory. It seems I have plenty of space. How much space does it need to compile & build kernel. I am using VirtualBox.
root@vinay-VirtualBox:/usr/src/linux-2.6.39.3# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 6.9G 3.2G 3.4G 49% /
none 669M 640K 668M 1% /dev
none 675M 24K 675M 1% /dev/shm
none 675M 96K 675M 1% /var/run
none 675M 0 675M 0% /var/lock
/dev/sr0 39M 39M 0 100% /media/VBOXADDITIONS_4.0.10_72479
I tried to build linux-2.6.36 but I got this error message
Code:
I looked into gcc-version.sh but the problem is located somewhere else I thought at first one of the files might have been corrupted and I downloaded the archive again.
I must also say that this happened in different versions of slackware (the distro I use): 12.0, 12.1, 12.2, 13.0, 13.1
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 have an x86 pc and installed lucid these are the details of my distribution version:
I am trying to build a kernel module i am getting the following error:
How to build kernel modules
I'm trying to set up a netbook I purchased that has a lot of more recent hardware, and so I'm having to compile some kernel modules on my own. I've installed Debian on this particular system, and so the version of gcc that was used to compile the kernel is older than the one currently in the repos. Now, I've installed the version I need, but can't remember how to specify building the modules in question with said version.
I've done this in the past, and recall temporarily changing some variable to use the different version, but it's been a while and I just can't remember. Is there an easier way to do this on the fly for any compilation? Or is changing a variable necessary? If there is no way to explicitly specify gcc version used prior to a compilation, could someone remind me of the variable I need to change to use x.x.x version?
Since there was a lot of talk about virtualization I thought I try kvm -- before I used VirtualBox. I took the SlackBuild from SlackBuilds.org and got an error with u8 as type in /usr/include/scsi/scsi.h. (sorry, I don't have the exact error message anymore..) I searched for its definition and I only found __u8 in /usr/include/linux/types.h. Then I searched the web and found a "fix" which says I have to change u8 from /usr/include/scsi/scsi.h to __u8. This problem was solved, but when I run the SlackBuild now it stops at some point and I don't know why. These are the last few lines of output:
CC arm-softmmu/translate.o
CC arm-softmmu/tcg/tcg.o
CC arm-softmmu/tcg/tcg-runtime.o
CC arm-softmmu/fpu/softfloat.o .....
LINK i386-softmmu/qemu
AR arm-softmmu/libqemu.a
LINK arm-softmmu/qemu-system-arm
root@tux:/home/christian/Downloads/kvm#
I put an echo after the make for building kvm and I put an echo after "make install". None of them are printed.