Just installed Fedora 12 on my Dell Precision M4400 and I'm trying to install the Broadcom wireless driver. When I try to compile the driver, I get:make: *** /lib/modules/18.104.22.168-127.fc12.i686/build: No such file or
directory. Stop.So I followed the link and /lib/modules/22.214.171.124-127.fc12.i686/build is a soft link:lrwxrwxrwx. 1 root root 47 2009-11-09 14:17 build -> ../../../usr/src/kernels/126.96.36.199-127.fc12.i686But in /usr/src/kernels all I see is:
Basically, About 50% of the time, the system boots and sets the console resolution to something strange, and the console renders in a small box in the top-left hand corner of my screen. This causes problems not only with the display of the console, but with the display of X as well.
I have an Intel GL40 chipset on this laptop, with an integrated GMA4500 GPU. I am using the latest stable Intel video drivers (2.10.0-1), and have tried using the git drivers. In addition, the problem has been occuring since December, when I install Arch linux on this machine, I have just now had the time to address it. So basically, the issue has persisted with all driver versions since mid-December to the latest releases.
In addition, I have tried using several kernels, including:
But the problem persists with each.
I wish I could give you relevant diagnostic information for this issue, but if I had any idea where to start...
I will gladly post any information necessary. I was going to post a copy of everything.log for a successful and unsuccesful boot, but unfortunately they put me over the posing limit by about 100,000 characters each.
I guess, on second thought, that my Intel video driver really wouldn't have anything to do with my console, now would they?
I've only a small /boot sector and rpm -qa | grep kernel kernel-188.8.131.52-174.2.22.fc12.i686 kernel-PAE-devel-184.108.40.206-70.fc12.i686 kernel-PAE-220.127.116.11-70.fc12.i686 kernel-18.104.22.168-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?
When I installed fedora 11 the other day using the live CD it installed the i586 kernel and not the i686, despite the fact that smolt seems to know that that the hardware is i686 (well, actually it's x86, but I'm not going to argue because I forgot to get that one...). Why would it install the i586 one though? (uname -r 22.214.171.124-213.fc11.i586) But more importantly, are there any specific issues which this version can cause that I should be aware of? I can't really be bothered to change it at the moment if there is no real issue with it but I'm not too sure what difference it makes? Is it slower? It seems to know that I have a quad-core processor and seems to use them fine.
My distro is ClearOS, which is RHEL so I assume this is the right place.I moved my sytem from an old PATA-drive to a bigger SATA. ClearOS uses LVM for the root directory and the swap directory, so this VolumeGroup was moved using lv-commands. I left the old hda drive in for the time being and hda also remained the BIOS start up disk. /boot is at hda2.Now, clearly there are 2 VolGroup00/ LogVol00 's: on hda and sda.
Eventually I wanted to unload my hda. I copied /boot from the hda disk to sda, changed (hd0,1) to (hd0,0) as /boot is in different locations, later found out that I needed to do the same for the location of the splash image and did that as well, but I don't get access to my new VolGroup.I did an /sbin/mkinitrd and a grub-install on the new sda but no luck. I have seen various error messages. The latter one is that grub loader 1.5 is active, giving me a grub prompt.
I have a system running openSUSE 11.2 with Desktop and XEN kernel, as well as Windows 7 (not by choice though...). I have noticed a strange time issue, with Windows 7 and the desktop kernel the time is correct (like for example now: 1:32 PM) but in the XEN kernel it is ahead several hours (6:32 PM). If it was an issue between openSUSE and windows then I would think that it is a problem with the system clock but I don't know what would cause a time issue between kernels like that.
I have recently installed the Maverick backport kernel (2.6.35 - from the lucid-updates/main repo) and while I was at it I also manually (through synaptic) got rid of some old kernels. I made sure that I kept the current Lucid kernel though (that was working fine). All seemed well (although I didn't actually check - just no errors) so I rebooted.On reboot I have lost all my Ubuntu kernel options!
jed@lightning:/boot$ ls abi-2.6.32-31-generic memtest86+.bin abi-2.6.32-32-generic System.map-2.6.32-31-generic
Even reinstalled burg (used to use it but it got broken by a kernel update long ago and never bothered to fix it as I only use Linux these days anyway)Funny thing is that BURG finds the kernels and reports no problem, but then drops to the grub-error prompt on boot.
I upgraded to 2.6.35-30.56 last night and now my system's a little flaky. Everything seems to be running ever-so-slightly slower and fullscreen flash is now choppy. The weird thing is the Grub menu upon bootup only shows the latest kernel, but not the previous kernels. Doing an "ls" of the /boot folder only shows this newest kernel. I'd like to revert back to the previous kernel but don't know how.
I downloaded the minimal boot image and installation CDs for F12 i386. On booting either I get the following messages: Code: This kernel requires the following features not present on the CPU: cmov Unable to boot - please use a kernel appropriate for your CPU Looks to me like the installation media for i386 doesn't have an i386 kernel! I'm trying to install to an i586 CPU.
Today I was trying to clean up my system and am a little bit stumped on something.
I used synaptic to clean up installed kernels, except for the one that was currently running. Once done I went ahead and restarted my computer.
Grub lists only one kernel available. However when I go to a prompt and
issue dpkg --list|grep linux-image I get several items listed code...
2.6.32-22-generic is the kernel I am running so I assume the "ii" files have something to do with the kernel in memory.
However, what are the "rc" files that are listed? Resource files? All three kernels referenced have been removed a LONG time ago and when I look for installed headers, or anything else, there is nothing installed for *-12, *-12 or *-14.
And when I check Synaptic for just the kernel number I get a list of packages with no version install, no latest version notation and no description (attached screenshot).
Just what are those references and how does one remove them?
I'm running Scientific Linux 5.5 (equivalent to CentOS 5.5), and over the past two weeks, I have had a problem with my root partition filling up, preventing anyone from logging into the server.After searching for large files, and finding none, I was mystified when du told me that the root partition had only 660 MB of disk space used, whilst df showed it full. The problem was this: the /var/crash directory had been filled up by an 8GB crash file. Now, I'm a 'proper' sysadmin and make sure that /var has its own mount point, so the crash should not have touched the root partition at all. Except it did - instead of writing to /var/crash on /dev/mapper/VolGroup00-LogVol04 which is mounted as /var, it wrote the file to /dev/md0 directly, so when all the file systems were mounted, those files were hidden under the mounted /var.
With kernel 2.6.35 I get wrong readings on lm_sensors. They are about 20C off than the real values (e.g. if the CPU is at 50C, lm_sensors will show 70C). If I boot with any other kernel (like 2.6.32) I get the correct values. I'm using the 'coretemp' module on an Acer 7720 laptop. My distro is 64-bit Arch Linux.
I just installed Slackware 13.1 x86 on a new laptop (you probably remember me from my audio post). I am having one other issue. My root file system is formatted as EXT4. When my computer boots, it tries to mount it as EXT3 then EXT2, fails both types and then tries EXT4. Here are the messages.
Code: EXT3-fs (sda2): error: couldn't mount because of unsupported optional features (240) EXT2-fs (sda2): error: couldn't mount because of unsupported optional features (240) EXT4-fs (sda2): mounted filesystem with ordered data mode So, eventually / is mounted correctly, but I think this is slowing down my boot time. Does anyone know how to fix this.
I am having issues trying to compile the alsa-linuxtant module and I am getting errors about not being able to find some files and the source needing to be reconfigured. Anyway the developers told me to try compiling on a pristine source to see if I could compile that way. When I went looking at kernel.org I did not find a 2.6.32-5 version. So I did some checking and to see just what version I have.
ii linux-image-2.6-amd 64 2.6.32+27 Linux 2.6 for 64-bit PCs (meta-package) ii linux-image-2.6.26-2-amd64 2.6.26-24 Linux 2.6.26 image on AMD64 ii linux-image-2.6.32-5-amd64 2.6.32-15 Linux 2.6.32 for 64-bit PCs
So the actual package that is installed is 2.6.32-15 but uname -r reports 2.6.32-5 as the kernel version.
Grub use to open an old kernel I tried to edit /boot/grub/menu.lst to open the one I wanted. The edit gets saved but it still opens in the wrong kernel. i.e when edit menu.lst it has no effect. I have tried running sudo grub-update. I've read piles of forum entries to no avail. I am running Jaunty.
Ok.. when it comes to drivers and kernels...I have a rented server - so I do not have local access to it, and I do not have a KVM or remote console to it.
This is the current kernel that came with it:
Linux version 2.6.26-2-686 (Debian 2.6.26-22lenny1) (firstname.lastname@example.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Wed May 12 21:56:10 UTC 2010 the network card module according to support is r8169 (when i do lsmod i see r8169 listed), lspci lists it as: Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03).
So.. where everything went bad is after I installed grsecurity kernel via apt-get install linux-image-grsec. It installed and rebooted successfully, but without the right network card module. The datacentre support had to reboot it to the original kernel for me.
So - i don't know how to update the network card drivers of the grsecurity kernel? It has to be perfect (I can't do trial and error) because each attempt that fails, I have to engage the datacentre support to reboot the system back into the original kernel. Apparently the new kernel detected it as a gigabit fibre card.
I am an openSuSE user for many years. My current installation is openSuSE 11.2. However, my first was SuSE 6.4 and I have been _constantly_ upgrading since then until reaching the current openSuSE 11.2. The technical issue I have been facing lately is with the kernel version of my current system: although it should be 126.96.36.199-0.1-desktop, as this is the one I have chosen via the online update mechanism and the yast2 system boot-loader procedure, grub shows it as preselected, the boot procedure in the end greets me mentioning this very kernel version, _but_ when I issue the command: uname -a in a command prompt, I am informed of using linux kernel version: 188.8.131.52-34-default #1 SMP PREEMPT
I am really quite puzzled, since I _cannot_ find any such vmlinuz file under /boot/ ! Could it be that my system properly runs with the expected kernel version, but uname mistakes it with a different one? Is there a way to determine the actual version of the linux kernel that my system currently runs with? If it's a problem with uname, have you got any suggestions that could potentially shed some light towards the origin/cause of the reported issue?
We are trying to implement a firewall as kernel module through netfilter hooking (in C). In the following code we are allowing only TCP traffic. Source port number and destination port number are printed for every TCP packet. On execution, this code prints wrong port numbers. This is the first time we are using skb_transport_header function for accessing tcp headers.
We verified port numbers being printed by firewall through NFS traffic. On the same machine where firewall is running, we hosted an NFS server. An NFS client (from a different system) puts a file in exported mount. Firewall is able to capture packets for this file transfer but port numbers printed are wrong. It prints '69' for source portnumber (whereas ethereal capture shows it as 790) and prints '553231' for destination port (whereas for nfs version 4 it has to be 2049).
I switched today to slackware-current on one of my desktops to play with it and ran directly into a problem.
Since ages my lilo.conf has two entries for slackware. One for runlevel 3 and one for runlevel 4.
Since the upgrade this is no more possible because I get a kernel panic as soon as udevadm trigger is called. The stack says something about an unknown boot option. Because that i removed the append lines from my lilo.conf and i was able to boot the system. The crash happens when udev is called from within the ramdisk and afterwards. I tried both.
My question is now. Is this a bug in udev or expected? I have this setup since at least 5 years and had never problems with that. What do I have to do to be able to select the runlevel at boot time?
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.
My 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?
operating system : fedora 15 kernel 184.108.40.206-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 220.127.116.11-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