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?
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 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 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:
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:
creating your own notification icon for Gnome? Like the Power, Network, and Sound ones. I found something called Zenity but it doesn't seem to be able to create a drop-down menu and I can't see how I'd update the information in the icon once it is created. I have a script set up to check something and want to report the results back via a persistent notification icon, with the ability to change the icon and its properties (mouseover/tooltip text) and drown-down menu text as appropriate.
How do I create a custom application launcher in Gnome 3? I used to be able to right click on the panel and choose 'Create custom launcher' in Gnome 2, but that doesn't seem to work here.
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
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?
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 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 have just installed Fedora 14 and am using the Gnome Desktop. There is no sound on any application at all. I have tried checking that nothing is muted or turned down to no sound by using pulseaudio volume control I have tried reinstall alsa and pulseaudio I have got this information Your ALSA information is located at [URL]... Where to from here?
there is no errors in log, also the AV shows PCM input for all sound (pcm/ac3/dts and so on) but there is silence (trying with both pulseaudio and alsa). Everything works with kernel 2.6.35.6-48 and before. the problem exists at least for 2.6.35.9-64.fc14 and 2.6.36.1-11.fc15
my audio is
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06) # aplay -l **** List of PLAYBACK Hardware Devices **** card 0: Intel [HDA Intel], device 0: ALC889 Analog [ALC889 Analog]
I just updated my kernel to 2.6.34.7-56.fc13.x86_64 last night and now I have no system sounds. Audacious plays my mp3's just fine, just as all my multimedia works in my web browser, vlc, etc... The only thing being affected is system sounds. I tried playing a sample with aplay and I got loud, crackling nonsense and this output code...
Sound disappears as soon as I try to use an application e.g. News Video Fox, CNN, BBC or playing a video disk or cd disk, and a kernel module crash is reported (listed below from logs) After this happens no sound, and the desktop freezes (X11 only Linux is fine). Restarting X obviously do not solve the problem.
It seems that Fedora 12 has sever problems with Intel Sound cards.
I guess it is not really a Kernel developers problem but more the authors for the sound module causing the crash. I already reported it through the popup to "kernel-oops" by clicking on the "black screen" popup reporting the crash on FC12.
Here follows the logs containing the crash info.
WARNING: at sound/pci/hda/hda_intel.c:565 azx_send_cmd+0x36/0x1df [snd_hda_intel]() (Tainted: G W ) Hardware name: Macmini2,1 BUG?
I've managed to get some sound through the system with kernel 2.6.40.1. I use multiple sound cards, I have problems with keeping the same order. I added in etc/modprobe.conf The list of sound devices, putting my D66 card as device 3, Rebooted and cat /proc/asound/cards showed all fore devices in the correct order. I got audio through one of the apps , and started to try and get another ,wsjt, to function.
I been trying all day to compile a kernel i downloaded from http://www.kernel.org/ (2.6.32.8 )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 2.6.33.1 with no patches and a custom config tailored to my processor. The reason I am running 2.6.33.1 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[1]: *** [oldconfig] Error 1
Had a custom kernel (2.6.35.5) 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.
Applied several updates last night including a 2.6.30.5-43 kernel and a suggest kmod-nvidia but the 5-43 kernel boots to a wallpaper gnome screen the first time.
Booted to the "fallback" 2.6.29....17 kernel and it worked fine.
Then 2.6.30.5.-43 also booted but without nvidia.
Installing akmod-nvidia as sugggested in other posts. Also see a kmod for this kernel.
Just installed FC10 and noticed no sound with latest kernel (2.6.27.15-170.2.24), however I do have sound with kernel 2.6.27.5-117. No other differences. Anybody else have this problem?
