I am using DEBIAN 6.0 and I wannna update my kernel from 2.6.32 to 2.6.38. Every time, I do it but after the installation & rebooting into the new kernel it gives me error "UNABLE TO BOOT INTO THE KERNEL".
View 1 RepliesI am runing debian-5 (lenny), the default kernel 2.6.26 was unable to start the x so i installed the new kernel linux-image-2.6.32-5-686_2.6.32-28_i386.deb, now x works, but there is problem building modules for the intel soft modem linux driver hsfmodem-7.60.00.00oem which is supplied in the modem cd by the intel company.
I installed these kernel packages for this purpose:
linux-base_2.6.32-28_all.deb
linux-image-2.6.32-5-686_2.6.32-28_i386.deb
linux-headers-2.6.32-5-486_2.6.32-28_i386.deb
[code]....
in all these cases hsfconfig failed with the above error,
From the securing-debian-howto [URL] ...
"4.2.2 Security update of the kernel
First, make sure your kernel is being managed through the packaging system."
which suggests...
Code: Select all$ dpkg -S ‘readlink -f /vmlinuz‘
When I try to confirm by running the above, I get a lot of characters of output but the last line reads...
Code: Select alldpkg-query: no path found matching pattern /vmlinuz‘
How do I make sure my kernel is being managed through a packaging system?
I've just installed debian sid and see that I've the kernel 2.6.32. I was a bit surprise as on ubuntu I had the 2.6.35 and debian sid is supposed to be more up to date that ubuntu (maybe I'm wrong).So I checked what were the packages available :
mart@mart-laptop:~$ uname -a
Linux mart-laptop 2.6.32-5-686-bigmem #1 SMP Sat Oct 30 23:25:58 UTC 2010 i686 GNU/Linux
mart@mart-laptop:~$ sudo aptitude search ^linux-image
[code]...
After running update last night from 2.6.35.9-64 to 2.6.35.10-68 my laptop fails to start. Boot process goes most of the way to startup and then hangs just before login screen. Not sure what else to give as far as info.
View 12 Replies View RelatedThis morning, I booted into my administrator account and checked for updates. There were a number (bogofilter, for one) but also a update to the 2.6.32-24 kernel. I installed the updates and rebooted the system. When I rebooted, the thought occurred to me (from reading another thread) that one of the reasons my Zareason desktop boots slower than my laptop (55 seconds vs 35) was that I have an external floppy drive attached, and perhaps the delay was a difference in my system checking for a bootable floppy.
So I went into the BIOS when it was booting to check to see if the floppy was enabled (it wasn't). Then I selected "Exit without saving" and resumed booting. What happened next was instead of seeing the Ubuntu icon and the six dots, I see "Ubuntu 10.04" and four dots. Then I get on the black screen these errors (sorry for any mistyping, I wrote them down on a sheet of paper as I had no other computer available to troubleshoot):
udevadm trigger is not permitted while udev is unconfigured
udevadm settle is not permitted while udev is unconfigured
udevadm settle is not permitted while udev is unconfigured
udevadm settle is not permitted while udev is unconfigured
ALERT! /dev/disk/by-uiid/939af864-c1a8-41d7-9b24-91d25685b6 does not exist. Dropping to shell
Busybox v1.13.3 (Ubuntu 1:1.13:3-1ubuntu11 built-in shell (ash).
Enter 'help' for built-in commands
initramfs
Googling around once I got into work and had computer access, it seems that the problem is GRUB has lost track of what partition I should boot from? Here is a thread which might be relevant: [URL]. Before I left for work, I went into the BIOS again and looked at the CMOS settings--everything looked normal. I once again exited without saving anything. I was going to try selecting an earlier kernel from the GRUB menu on boot, but couldn't remember the key to press.
I found out later today, to enter GRUB 2 it's been changed to the shift key, and not the F2 key like it used to be. One poster on the aforementioned thread said his system would boot ok to the earlier kernel. The thread above has as its solution to either try to tell GRUB where your boot partition is and/or re-installing GRUB. I have /home on a separate partition, so if I need to do a re-install I can do so without it being a major pain. Sda1 is the partition which has the OS.
I had a Centos 5.5 system working great...and then due to crazy curiosity, installed the kernel update. Did this through the graphical interface, uncheck all update other than kernel. It downloaded, installed fine..After reboot now all I get is GRUB_ and then nothing else! I waited 3-4 minutes and had to shut down system. Have been googling around but thought I will post it here as well..When I boot with Win7 and use Ext2fsd to check, the boot folder is empty. Not sure if this is because ext2fsd does not read boot folder or it got wiped out by the yum upgrade process.
View 9 Replies View RelatedI have recently run an update and now we are unable to boot the newer kernel. We get stuck as below;
Memory for crash kernel (0x0 to 0x0) notwithin permissible range
Red Hat nash version 5.1.19.6 starting
Unable to access resume device (/dev/VolGroup00/LogVol06)
[Code]...
The kernel version we were at was 2.6.18-194.el5 and the update move us to 2.6.18-194.17.1.el5. I've done some googleing but I'm unable to work out exactly what I need to do. I'm guessing the new kernal is missing a module?
I've just upgraded my kernel to 2.6.32 and I cant use sound anymore!!! My card was detected ,here is the output of lspci |grep Audio
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
also frimware is installed ,gstreamer as well the sound is not on mute and it was working on the previous kernel .
I am unable to boot my Fedora 14 after last nights kernel update. When I start the boot up and hit F2 the system fails after outputting the line : Starting vservers of type 'default'. At some point the console displays an error message :
serial8250 : Too much work for irq17
How do I restore my previous version? I know some people have suggested in the past - just modify the grub.conf but how? When I boot off the cd I only get access to the liveuser disk. I need to have access to my own /boot/grub/grub.conf file.
I have the following strange thing with a RHEL4 installation. Since last week, the system did a reboot and now something is really fucked up. During boot we get the following messages (don't care about 'strange' typo's, my colleague typed it 'blind' from the screen)
Code:
The strange thing is that we never see a 'could not mount blabla' or similar messages. First we thought it was a failing kernel update by plesk, but even after manually updating the kernel with RHN RPM's, still the same message. Booting with rescue mode and then chroot the system works. After that we even can start things like plesk and so on.
We double checked things with another RHEL4 install, and at least two things were odd:
1: the working machine has /dev/dm-0 and /dev/dm-1, the broken one doesn't
2: some files on /dev didn't have group root, but 252
We tried to recreate the /dev/dm-X nodes with [vgmknodes -v], output:
Code:
A fdisk /dev/sda shows: /dev/sda2 XX XXX XXXXX Linux LVM (I removed the numbers because this line is from another machine, but rest was identical)
We have a copy of the boot partition so if one need more info please let me know.
grub.conf:
Code:
last part of init extracted from initrd-2.6.9-78.0.8.ELsmp.img:
Code:
A few days ago on my rss reader, I have read article about Ksplice uptrack that check updates for kernel and update kernel without reboot!
View 1 Replies View RelatedSqueeze's latest update has upgraded my kernel from 2.6.32-3-686 to 2.6.32-5-686.My wireless stopped working and then I realised that I had to rebuild the wifi modules. I had followed this earlier.URL...For this new kernel, which I step of the process should I repeat? Rebuild module? Or just do a modprobe?
View 4 Replies View RelatedI'm using Squeeze amd64, installed latest kernel 2.6.38 from backport yesterday. Just now try to check for any update but failed, these messages show.
View 2 Replies View RelatedI recently installed debian squeeze 32bit on a second partition of my amd athlon 64 X2 dual core machine.Currently it is using linux-image-2.6.32-trunk-686 kernel.But linux-image-2.6.32-trunk-amd64 is available.on the repository.Is it a 64bit kernel or 32bit kernel optimized for amd64 architecture?
View 12 Replies View RelatedI ran the update through yum (replicated results twice) and whenever I boot to the new kernel it either freezes on the F logo or screen goes black right after f logo. No commands work whatsoever (tried em all). I can boot to an older kernel (2.6.33.3-85.fc13.x86_64). the ones that fail are: 2.6.33.6-147.fc13.x86_64 and 2.6.33.6-147.2.4.fc13.x86_64.
The Fedora error system gave me a bug report I submitted, here's what I got:
Package: kernel
Latest Crash:Tue 03 Aug 2010 09:46:33 PM
Command: not_applicable
Reason: BUG: unable to handle kernel NULL pointer dereference at 00000000000005b8
Bug Reports:Kernel oops report was uploaded
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 use a pretty fresh installed RHEL 5.4, which should be very similar to Fedora. After the basic installation I installed xen and xen-kernel via yum with no errors. I can select the xen-kernel at boot time. But after booting the normal kernel shows up.
[root@noname boot]# uname -r
2.6.18-164.11.1.el5
My /boot/grub/menu.lst looks like:
default=1
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
[code]....
I can't see anything wrong and I did not change/try anything.
I do not know if this is really something I should worry about. I am running Debian testing on my laptop (HP Pavillon dv6). Today, the aptitude update---aptitude upgrade gave me a new kernel (2.6.39). However, if I boot with that kernel, I get a warning (do not know if that is the way I should call this) telling me that the machine failed to get the i915 symbols so turbo graphics will be disabled.I have not done any serious test, but at first sight I do not notice any difference performance-wise with respect to the previous kernel. what am I supposed to do to fix this?
View 8 Replies View RelatedLately I'm encountering a somewhat annoying malfunction: almost every boot, my desktop is stuck, HD red led is constatnly on, and i get a message from kerneloops that I had a kernel failure. I can move the cursor a little and slowly or not at all. Few violent reboots and I get a clean boot. Running Debian Lenny kernel 2.6.26-2-686 on a Pentium 4 2.0 GHz with 250 MiB ram.
View 4 Replies View RelatedI got a new laptop the other day, repartitioned it and installed Lenny. The wireless did not work. From some searching, I decided that I have the 14e4:4727 broadcom chipset. The driver I need is partially supported by the 2.6.33 kernel. I installed squeeze and downloaded the 2.6.35-7 kernel from kernel.org Then compiled it with the debian 2.6.32 kernel config file. Once it was done I installed the kernel deb files, and restarted it.
Kernel 2.6.35.7 Compiled with commands
make oldconfid
make menuconfig
export CONCURRENCY_LEVEL=2
make-kpkg clean
fakeroot make-kpkg --append-to-version "-hermes" --revision "10-5-2010" --initrd kernel_image kernel_headers
[0.433831] PCI_root PNP0A03:00: address space collision : host bridge window [mem 0xafffffff-0xdfffffff] conflicts with PCI bus 000:00 [mem 0xd0000000-0xffffffff]
And it seems to hang until I manually hold the power button to shut it down.
Before I compiled my own kernel I tried to use the liquorix-2.6.35-amd64 kernel with the same result. Am I doing something incorrectly?
Computer: DELL Inspiron m5010
4g ram
phenom 2 triple core
ATI Mobility Radeon HD 4250
I have been using linux primarily for a year or two.
I'm running Squeeze and I've been running into the r8169 hang problem (see [url]for example). A temporary (until the driver foibles in the kernel are resolved) solution that seems to be working for many people is passing the boot option "pcie_aspm=off" to the kernel.
Apparently, either I don't understand grub2 at all or my kernel doesn't like me very much. I put the option in grub.cfg like so:
However, it appears that the kernel, for whatever reason, is either not being given this boot option or it's not interpreting it correctly. When I run lspci -vv I get this for my r8169 ethernet card:
The relevant section is LnkCtl: ASPM L0s L1 Enabled; indicating that ASPM is still on.
I have squeeze and I've created my own custum kernel. Howto configure grub 2 to boot with this custom kernel automaticaly?
View 5 Replies View Relatedsince upgrading the squeeze kernel from 2.6.26-2-686 to 2.6.32-5-686 I´ve been unable to boot my HP D510S/845G without attached monitor. As this computer serves as router and print/faxserver, there is/was neither a monitor nor a keyboard/mouse attached. With monitor everything works fine, without monitor the computer hangs somewhere. Unfortunately it hangs without logging anything in /var/log.
Reinstalling xorg and xserver-xorg didn´t change anything, neither was the new xorg.conf from dpkg-reconfigure -phigh xserver-xorg of any use. (After booting with attached monitor I disconnected the monitor and ran dpkg-reconfigure) Maybe disabling Xorg would solve the problem, but I want to be able to log in via vnc and use a GUI - for example to configure mythtv. Up to the kernel-update everything was working fine, so I think some changes to the new kernel are responsible. how to fix it or how to start logging earlier in the boot process?
After some updates Jessie 8 my boot grub shows now 2 kernel versions to boot from.
3.16.0-4-amd64
3.16-3-amd64
- How do I know which one is the newest and if happy with it, how to remove the older one?
I use a static compiled kernel and a fully encrypted disk apart from a boot partition. I have recompiled and installed kernels many times. When I tried with the latest kernel from Testing, 4.2.6, the system will not boot. Not only that but the previous kernel now does not boot. However, a stock modular kernel does boot. The static kernel hangs at:
Code: Select allVolume group "dk" not found
Cannot process volume group dk
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
Reading all physical volumes. This may take a while...
/run/lvm/lvmetad.socket: connect failed: No such file or directory
[Code] ....
And after giving the password the boot continues successfully. How to diagnose it further?
I've got a fresh install of Squeeze on a 32bit host and I have been unable to boot into XEN/dom0.The Xen Kernel is "linux-image-2.6.32-5-xen-686" (pvops) and Hypervisor is xen-hypervisor-4.0-i386.The system default installed with grub2.It boots quite happily in normal mode, using the above Kernel, but just reboots itself if I try run it as Xen/dom0. (reboots within a second of pressing <enter> ... there is no messages displayed on the screen that I have noticed)The relevant menu (generated by /etc/grub.d/20_linux_xen) entry for running Xen is as below;
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-686 and XEN 4.0-i386' --class debian --class gnu-linux --class gnu --class os --class xen {
insmod part_msdos
[code]....
I need to install any version of Debian with the Debian Kernel version 2.6.22-3-686. I don't mind what version of Debian it is, I just need it to have this specific kernel! Debian Etch comes with 2.6.18-4-686 and Lenny comes with 2.6.26-2-686 so the kernel I need is obviously somewhere in between.
I have tried using the following commands to see if kernel 2.6.22-3-686 is available for download via the apt-get method in both Debian Etch and Lenny but it is not...
apt-cache search linux-kernel
apt-cache search linux-source
So does anyone know where/how I can download specific kernels and install them for use? I have a computer sitting next to me that has multiple kernels as an option on boot, and they all boot into the same system, however I do not know the person who set up the computer so cannot ask them how they did it
I am running Debian squeeze. A while ago I upgraded my kernel to 2.6.38 from backports. Just now I thought it would be good to upgrade to 2.6.39 from backports. Upgrade went fine, but after rebooting I get a kernel panics rightaway.
"No filesystem could mount root, tried:"
"Kernel panics = not syncing: VFA: Unable to mount root fs on unkown-block(0,0)."
This is the first time one of Linux installations halts/panics on booting, so I don't know what to do now. I tried booting the recovery entry from the grub boot menu, but same result.
Since I got the liquorix kernel installed on my machine I got an error of setting kernel variable error. net.ipv6.bindv6only at boot time, since it wasnt a big deal I never looked further into it, but now that I had some spare time and I didnt want to see any errors on my machine I found a solution for it, with a little googling all we need to do is read the /usr/share/doc/procps/README.Debian and bingo no more error i hope this help anyone else with the same problem. I did the 3rd suggestion on that file to load the module in /etc/modules cheers.
View 4 Replies View Related