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.
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.
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:
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 220.127.116.11-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?
Today I decided to try to install 18.104.22.168 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
I 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?
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 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 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.
I'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.
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 been trying all day to compile a kernel i downloaded from http://www.kernel.org/ (22.214.171.124 )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.
I wasn't using my laptop for at least a few hours, but when I looked at it, it had seemed to crash. I am hoping to figure out what caused this, and to prevent it from happening again. I believe it has something to do with drm or b43 as that is what I could decipher from the screen. I have checked some logs and found nothing irregular. I do not want this to happen again. I am running kernel 126.96.36.199 with no patches and a custom config tailored to my processor. The reason I am running 188.8.131.52 is because of support for my Wifi.
I would like to try and optimize my kernel a bit. Since I am doing this on a fresh install, I don't really care if the os gets bricked in the process, and I am sure I can bring it back if I can boot into a recovery console from the old kernel. So, I followed thispost. I patched it and copied and edited a config file from /boot/, saved it as .config, I tried it several times with both removing and not removing /debian and /debian.master directories from the source, yet I always get the same error when I run "make oldconfig".
Code: $ make oldconfig scripts/kconfig/conf -o arch/x86/Kconfig *** Error during writing of the kernel configuration. make: *** [oldconfig] Error 1
Had a custom kernel (184.108.40.206) running under Slackware 12.1 and also the same kernel on an Ubuntu 10.04 machine just fine, however after a clean install of Slackware 13.1 this kernel no longer works (This kernel was re-compiled with the same .config file under Slack 13.1) as I keep getting the the following: -Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,3) The strange thing is it keeps looking for the root file system in hda1, however the stock 13.1 kernel finds it in /dev/sda1 so the root partition is /dev/sda1 in lilo and the harddisk is known as /dev/sda.
When I build the kernel 2.6.30 source, the rpm package is very big and needed or root filesystem 800-900 Mb. I use "make rpm" as described in Configure, Build and Install a Custom Linux Kernel - openSUSE.
I've about 5.5GB of free space....whenever I try to compile the kernel my system runs out of space...says zero bytes remaining maybe I din't configure it that well I cant exactly figure out which drivers/modules I need in order to obtain a working kernel.
All I want is a lxde based desktop to play with and tweak. The problem is that I am using rather esoteric hardware. An xcore86 device on chip to be precise. I have a custom kernel in deb format, and I managed to install UNR 9.10 and then install the custom kernel. Strip out as much obvious gnome stuff and install an lxde desktop. Now this is a quite good solution but still leaves me with a lot of junk that I am not sure I need. 2 ideas occurred to me. Install lubuntu and then install the custom kernel(this failed to work because lubuntu's kernel refused to play nicely with the xcore) or do a minimal install and work my way up adding the things that I wanted. (Again this ground to a halt when the screen went blank)
I looked at unetbootin to try and put in a custom kernel but to a novice like myself it did not work very well.Can anyone help, either a list of everything that can be removed safely from a UNR install to leave me with a minimal install, or a way to insert a custom kernel into a lubuntu iso?
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.
I am using uuntu 8.04 and I am trying to make live cd with running kernel. I know that there is documentation in ubuntu website in "how to make live cd" but the thing is this is my custom kernel. I have my own configuration. So I want this kernel to be work in live cd.
I have a custom built 2.6.37 kernel where I have most of my devices compiled into the kernel. The only modules are related to nouveau (in case I want to go back to proprietary nvidia) and sound drivers. Everything seems to be running fine. However, in /proc/acpi, I'm missing a number of entries, such as thermal_zone/, dsdt, etc. I do have ac_adapter/, battery/, button/, event, processor/ and wakeup. I've gone through what I think is a very detailed review of my kernel config, and I can't find where I've missed something ACPI related. Here is my kernel config with the ACPI section.
Code: # Power management and ACPI options CONFIG_ARCH_HIBERNATION_HEADER=y CONFIG_PM=y # CONFIG_PM_DEBUG is not set CONFIG_PM_SLEEP_SMP=y CONFIG_PM_SLEEP=y CONFIG_SUSPEND_NVS=y CONFIG_SUSPEND=y CONFIG_SUSPEND_FREEZER=y CONFIG_HIBERNATION=y .....
I compiled my own custom kernel for the first time. I tinkered with different options, nothing to difficult. I actually didn't expect it to work the first time.
I had kept the original lilo boot config just in case something was to go wrong. Now when I try to boot the system, I always get a "VFS: cannot mount root system on (8,3)". I googled this and found that my kernel did not support my root filesystem (btrfs). So I made an initrd with btrfs kernel module, but it didn't help. I then got a string of errors about how /dev could not be mounted.
My question is two-fold. First, how come when I configure the system back to when it was first installed, it still won't boot? Im using the same kernel (220.127.116.11-smp). Second, how can I get myself out of this rut without reinstalling?
Code: lba32 append=" vt.default_utf8=0" boot=/dev/sda vga = normal # Linux - Slackware image = /boot/vmlinuz-huge-smp-18.104.22.168-smp root = /dev/sda3 label = Linux read-only
BTW, I have been maintenancing the system by chrooting into the device off of my slackware boot disk. Im on slack 13.37
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.
I am trying to build a custom kernel but I couldn't. Here are the steps to reproduce it: 1. Set Up an RPM Build Environment as its is explained in [URL] 2. Then follow the instructions in [URL] 3. When I try to install the kernel source rpm I get the following error:
[matias@Centos ~]$ rpm -i [URL warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root . . . warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root error: unpacking of archive failed on file /home/matias/rpmbuild/SOURCES/linux-2.6.18.tar.bz2;4ba24901: cpio: read
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.
i need to install openSUSE 11.2 from an USB stick. I followed this article SuSE install from USB drive - openSUSE using the openSUSE-11.2-NET-i586.iso. Unfortunately the kernel provided in this image doesn't load on my target as it needs a few extra modules for its chipset.
Thus i copied our custom kernel (which is verified to run on the target) and its initrd to the usb stick and i also created a new entry in the syslinux.config. The kernel loads, but then it can't find the root device.Does anybody know, how i need to configure the initrd to make the USB stick the root device?