Ubuntu :: Option To Boot From The New Kernel Does Not Appear?
Dec 1, 2010
I installed Jolicloud in a new partition to give it a try. It's pretty nice. Anyway, it took over my bootloader, which didn't really bother me.
Now my kernel has automatically been updated to 2.6.35-22.41 or something. The option to boot from the new kernel does not appear. As you might imagine, I want to do that. My old bootloader updated this stuff automatically.
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 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...
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 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.
Code:
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 installed 11.04 after Windows 7. when the GRUB boot menu starts up there is an option for Win 7 boot but it will not boot windows. When that option is selected the screen changes colour for 2 seconds and then reverts to the GRUB menu. Ubuntu boots fine.I downloaded the Boot Info Script and ran it, the results are
Code: Boot Info Script 0.55 dated February 15th, 2010 ============================= Boot Info Summary: ==============================[code].....
I have been reading for hours and just do not get how to do this simple task. I need to add a couple of kernel options to the 3rd menu item that shows in my grub.cfg list. I understand which files to edit (not grub.cfg) and run the updater.
If I look in /etc/default/grub I cannot figure out how to add a kernal parameter unless it is the default.
So basically I want to change the equivilent of this line below:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
But for a kernel menu item that is not the default.
I loaded the dvd (one that came with Linux Format Magazine No. 139), changed BIOS to boot from dvd, and then:
I get the welcome screen with the options to boot Ubuntu, KUbuntu, XUbuntu or Boot from First Hard Disk. As I have an older laptop I was going to try XUbuntu. However, the arrow keys did not change the boot option. In fact nothing worked, Tab did not bring up a menu and Enter did not initiate boot.
I tried reloading the dvd, switching off the laptop (no way to shutdown) and restarting but always come up with the same problem.
My DVD drive works fine and the dvd appears not to be faulty since all the info is readable when it is loaded with windows running.
My system details are:
HP compaqnx9000 Mobile Intel Pentium(R) 4-m CPU 2.20 GHz 219GHz 704MB RAM Optiarc DVD RW AD-7580A Radeon 1GP 340M
I have had Linux running in our product that has several serial ports.(Another Ethernet to Serial port translator). It has been running OK for about 6 years, using kernel 2.6.11, then 2.6.18. Now I just got 2.6.39.1 running and suddenly I get these "I/O Possible" messages and my programs shutdown. I found elsewhere that the cure for this is to put a "signal(SIGIO, SIG_IGN)" call to stop this signal from crashing the program. This works, but I would really like to know the reason that this started happening in the first place.
Could there possibly be a 'config' option I missed that causes this? It just surprises me that the kernel writers would implement something that has such a large impact on the existing code base, causing anyone using serial ports, or anything else that might trigger a SIGIO, to have to edit, recompile, and redistribute their programs.
How to change the kernel behavior, short of going in and hacking the kernel. Or at least an idea as to why they would have changed the default behavior.
I have Suse 10 and Suse 11 and I need to add the option elevator=noop
Code: Suse 11
Code:
By the way I think I added correctly
Ok my question is: I can add this noop option on the fly by
Code:
But since I have sdb and sdc... I have to run that command three times it does not bother me I am worry about is what happens when my server is rebooted.
There won't be any noop option for sdb and sdc since they are not included on my boot parameter.
How can I automatically add noop to my sdb and sdc?
I downloaded kernel 2.6.30 for my project. But I want to see the all symbol and debugging information. So, I try to use option "-g" with make file I don't know how...
I just know the make kernel "make all"
If I want to use "-g" option for vmlinuz with whole symbol for debugging, how can I put that "-g" option into the "make"
Do I have to modify the "Makefile" ? or "only command is possible like make -g something...."
Is there an easy way to change just one option in the kernel? I need to set something from =M to =N I tried installing the kernel source rpm according to the centos wiki site, then changing the .config, make oldconfig etc. but the always build always fails.
I have a loadable module, simple enough I believe it should run on any 2.6 kernel. I want to force the load and test that assumption. How can I do it?
ismod does not seem to notice the -f in 2.7 modprobe has -f but cannot locate the module.No go. So I read the manpage for modprobe which says: modprobe looks in the module directory /lib/modules/'uname -r'.So I copied MYMODULE.ko to /lib/modules/2.6.(the only directory in here) and type: modprobe -f MYMODULE.ko.Still can't locate MYMODULE.ko.I notice there are no other .ko modules in that directory; so I go in deeper to kernel/drivers/char, guessing about the char directory, and copy MYMODULE.ko there.
I've set up a triple boot system (Ubuntu Karmic, Windows Vista and OSX86 -- a patched OS X which works on a PC) on a Dell 9200 (C2D 2.13 GHz, 4GB RAM, nVidia G210). I sue Grub2 as the bootloader and update-grub picks up OS X and it boots without any problem.
However, although when booting OS X using its own Darwin bootloader, I can apply the boot option "Graphics Mode"="1680x1050x32" to ensure that I get the screen resolution that I want, when OS X boots from Grub2, the only resolution available is 1024x768 which is disappointing. I have tried adding gfxmode=1650x1050x32 to the OS X section of /boot/grub/grub.cfg in Ubuntu but this does nothing.
I was trying to know if relatime or noatime was set on a filesystem, but i didn't found the information, neither in /etc/fstab, neither in kernel boot options.
First of all, it seems clear that i don't have the "normal" behaviour on atime:
I'm using 2 cloned disks with CentOs5.3 and I need to be able to control which one is booted. I can specify which disk in the BIOS but after stage 2 it is always running from disk 2. When I have puppy linux on one disk and CentOs on the other I can boot off of either as selected by the system BIOS so the BIOS is not the issue. I think it is how the root option is passed in the kernel command in the grub.conf.
I think when the OS searches for the /dev/VolGroup00/LogVol00 share is locates 2 since the disks are clones and uses the last one found. On information I have found for the kernel command and the root option it appears CentOs uses it differently. CentOs uses a volume name as specified /dev/VolGroup00/LogVol00 instead of a partition designator /dev/hda2. Is there a different way to specify /dev/VolGroup00/LogVol00 in CentOS for the root option for the kernel command of grub.conf?
When using make menuconfig - under Device Drivers --> Character Devices --> there should be an option with the label "Enhanced Real Time Clock Support" (CONFIG_JS_RTC).
The problem is that this option seems to only show up while using the menu method when other options are either enabled or disabled and I've entirely forgotten what should be what. I swear fingered it out once.
This is on an older computer (P4) so HPET is no good.
You would think that disabling the HPET option would enable the RTC option but that does not appear to be the case.
I understand I can just add the option to the .config file and avoid this hassle but I'm very interested to know how to make this work.
To show my appreciation I will do something nice for you such as call you a nice name or tell you that you are pretty (or ugly if that's what you prefer).
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".
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:
I installed a fresh copy of Slackware 13.1 (stable) on one of my media servers and I am experiencing something strange.... When I power up the machine, I see the kernel booting, no errors, until it gets to the point where it says:
And then randomly freeze there.... Well the machine is not totally frozen because the cursor still blinks. But it will never continue... Like I said, this happens on a random basis... After a reset, it might go through or simply stall at the same spot.
I remember after installing Slack 13.1, I rebooted the machine but forgot to remove the DVD from the player, so the install routine started up, and froze at the same point when it was loading the kernel for the setup programs...
My mobo is a MSI k9N platinum.
I never had this problem before.... (well I never used 13.1 before). Since I got this machine, I used slack 12.2 and slack 13-current with success.
This problem makes the machine extremely unreliable because I intent to use it as a backup and media server, so chances I will WOL the machine and use it remotely... if that happens.
I 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.
I compiled my kernel, compiled scsi support into kernel, used the new kernel and initrd, the boot failed.Then ,i unzip my initrd, found that sd_mod.ko can't be insert, i added it manual, and reboot OK.so, why! in the kernel configure , the sd_mod.ko is set to <M> , but why it can't be found in initrd?
I have an HTPC that dual boots Ubuntu 9.10 (upgraded from 9.04, so still using GRUB 1.x) and Windows (for Netflix duties). I recently rebooted the machine to watch some Netflix movies, only to discover that the GRUB menu no longer has an option to boot Windows.I imagine that this could have happened after an apt-get upgrade installing a new kernel; it has been a while since I rebooted the machine and could have missed it.
I've just installed 10.04 and its the best distribution i've seen yet! But I can no longer switch between windows and ubuntu like I have in previous installs. I get the normal boot screen options which are something along the lines off.
Boot ubuntu 10.04 recover ubuntu 10.04 restore factory default settings of your Toshiba machine
but no option to boot into windows, I can still access all my files and settings from within Ubuntu, so i haven't overwritten Windows
I have windows 7 installed to one hd, and installed Ubuntu to another internal. The install went well, and when it was done, it said it had to restart. But upon restarting, i wasnt give the option to boot ubuntu. It just keeps loading windows. I went back to my bios and chose to boot from both hd's, but nothing is happening. With the hd with ubuntu on it, it wont load up.
i have ubuntu 10.04 server on a usb (it is an .img file) , and i.m trying to install it on an ancient machine (64mb of ram to be exact), and it has no usb option in the bios menu.
I have just installed Ubuntu 11.04 alongside Windows 7. Once the install was complete it asked me to restart and when it went to boot i never got the choice in which OS i wanted to start. How can I fix this?