The latest update changed the default boot from 0 to 1 and added extra parameters to the new kernel boot line.
default=1
timeout=8
splashimage=(hd0,7)/boot/grub/splash.xpm.gz
# hiddenmenu
title Fedora (2.6.31.6-145.fc12.x86_64)
root (hd0,7)
[Code]...
after yesterday's update to kernel 2.6.35.10-72 my grub.conf didn't get updated and ll /boot shows that neither vmlinuz or initramfs exist for that kernel. uname -r though tells me I'm running 2.6.35.10-72.
How can I do that? and on another more reallystic matter how can I generate the missing files so I can manually update grub.conf?
I'm I seeing this wrong or is the initrd file in kernel-2.6.27.25-170.2.72.fc10.x86_64 a zero byte file and that's why I can't boot with it( get this "kernel panic not syncing VFS unable to mount root fs on known -block (0,0)" message)
View 2 Replies View RelatedI'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.
kernel /vmlinuz-2.6.18-128.el5 ro root=/dev/VolGroup00/LogVol00
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?
since i have installed the nvidia drivers i have lost the graphical boot and just had a bar at the bottom of the screen instead. i tried to get the graphical screen back by adding vga=795 to my /boot/grub/grub.conf but when i rebooted not only did i not get the graphical boot or the toolbar at bottom.
i got list of all the drivers and services it is starting with ok next to it. i have also since doing this lost the bit when restarting or shutting down getting the words restarting or shutting down and just get blank screen with flashing cursor. i removed the vga=795 and i still get the list of drivers/services loading.
how do i get the quiet option back. i have checked /boot/grub/grub.conf and it has the quiet in it.i have also tried running update-grub but get message command not found. i have attached the grub.conf file
I would like to modify the boot loader settings and triedo open the file grub.confHowever, it is said that the file could not be opened, as seen in the attachment.Tried to authenticate as 'root' before opening the file, but the problem still exist...
View 10 Replies View RelatedI have just updated my kernel and immediately struck trouble. The kernel update is marked as security update.
When booting I get a multiple warnings " deprecated config file /etc/modprobe...", then "no root device found" followed by "boot has failed, sleeping forever"!Clearly something is amiss with this update, so figured the best thing might be to remove it and wait on a fix, but attempting to remove the kernel via the package manager would cause a whole lot of other packages to be removed as well.Instead, I edited grub.conf, commenting out all the kernel-2.6.34.7-63 lines, so that the default is now the previous kernel (2.6.34.7-61).
I tried to update my f12 today. In the list it showed an update for kernel-2.6.31.6-145.fc12.x86_64 It all seemed to go OK but when I restated my computer it spit up an error and wouldn't boot"Could not load /lib/modules/2.6.31.6-145.f12.x86_64/modules.dep: No such file or directory"Luckily the old kernel still works.
I do have the disk encryption set, could this be related to that? Updated my laptop today with the xx.6-145.f12.PAE kernel and now it's borked to. Same problems.12/07/2009OK today's kernel update seemedto fix the problems and now all is well, execpt for my inkscape not working problem. But I put ubuntu 9.10 in a VBox and it works. So for now that's my work around.
I have an issue with kernel-2.6.31.9-174.fc12.x86_64. I ran the updates on Christmas Eve and it updated from kernel-2.6.31.6-166.fc12.x86_64 to kernel-2.6.31.9-174.fc12.x86_64. When I rebooted, I no longer received the Fedora Bubble boot screen. It comes up with the Fedora boot bar (across the bottom). Also, I receive failures during boot with the following:
[Code]...
I just responded to a (packagekit?) prompt to update packages, which included new kernel 2.6.35.12-88.fc14.x86_64. I use nVidia on my notebook and usually the new driver is installed automatically. This time, the computer would not boot to the stage that the nVidia logo appears, indicating the driver is not present. I edited grub.conf to take me back a version and I am now running under the previous kernel 2.6.35.11-83.fc14.x86_64. I tried a yum search for kmod-nvidia-2.6.35.12-88.fc14.x86_64 and nothing was found. I have enabled these repos:
[Code]...
In an attempt to ameliorate some other problems (lm_sensors, and loopback), and based on several forum entries, I decided to update the default f15 kernel (2.6.38.35) using kernel-2.6.39-1.fc16.x86_64.rpm from rawhide. It seemed to install without problems and when I rebooted it seemed to hang just before completing the boot process. The on screen boot messages ended with:
Started Display Manager
Started LSB: daemon for libvirt ........
Starting LSB: suspend/resume libvirt guests on shutdown/boot
[ 12 ......
about a dozen similar lines ending with
[25.030991 hci_cmd_timer: hci0 command tx timeout
then it apparently hangs
However, at that point I can log into to a console using Cntl-Alt-f2, so most, if not all, the crucial boot processes seem to have completed. There is an issue with the nVidia driver that I will deal with by modifying /boot/grub/grub.conf to re-enable nouveau, but I am stumped by what is causing the hang up. There is a certain amount of traffic regarding a similar problem with Ubuntu 11.04, but no solution other than it seems to be related to a BIOS bug (NFI)
what sub-system uses the "hci_cmd_timer" and why it might interfere with the boot process? Has anyone else run into a similar problem with f15?
Is there a better way to get an updated kernel in f15? I do want to keep all the Red Hat patches and back ports, so reluctant to build a kernel from scratch from upstream sources at kernel.org (and maybe just a bit apprehensive ;-})
I generally check what updates are being installed. This time sadly I didn't and again this kernel had one missing module. VirtualBox-OSE stopped working. It had been working fine with other upgrades. No it's not a problem with dkms or other stuff. This kernel doesn't have vboxdrv module like other kernels...i verified it...
[Code]...
The 2.6.38.8 version doesn't have vboxdrv module!....hence again I have to roll back to older kernel. So before blindly upgrading....read this message!
Keep trying update the packages (36 in total) and every time I keep getting this error
ERROR with rpm_check_debug vs depsolve:
kernel-x86_64 is needed by kmod-nvidia-2.6.26.6-49.fc8-173.14.12-5.fc8.2.x86_64
kernel-x86_64 is needed by kmod-nvidia-2.6.26.8-57.fc8-173.14.12-5.fc8.3.x86_64
Please report this error at [URL]
I just built some machines with the Intel 82574L gigabit ethernet chip, loaded Fedora 14, and discovered a problem with the e1000e driver dying after a few minutes. A little time spent perusing the web told me that the same driver had problems in Fedora 12 and Fedora 13 as well. Congrats to Fedora for the hat trick.As of kernel 2.6.35.10-74.fc14.x86_64, e1000e driver 1.0.2-k4 still had bugs.[URL]
View 6 Replies View RelatedPartition info:
sda2: Win7
sdb1: /boot
sdb2: LVM, containing , home, swap...
[code]....
I've installed Fedora 10 on the third partition of an external HDD. It has with the following partitions:
(hd0,0) - GRUB bootloader files [PRIMARY]
(hd0,1) - Chainload LILO for another Linux [PRIMARY]
(hd0,2) - Fedora 10, no LVM or Swap (labeled F10) [PRIMARY]
I'm trying to boot Fedora 10 using the following grub.conf:
[Code]....
What is the configuration issue in the other-than-Fedora-11 stanza below that prevents that OS from booting? That stanza is taken directly from the /boot/grub/menu.lst of that OS, whose root partition is on sda5. All I get upon choosing the menu entry is a blinking cursor and a steady HD light. obsessing over this for a couple of weeks, reading what I can find about grub configuration but without joy.
Here is /boot/grub/grub.conf:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You do not have a /boot partition. This means that
# all kernel and initrd paths are relative to /, eg.
[Code]......
I am testing my crash recovery strategy for my linux system and I am having trouble with GRUB. I am basically restoring my backup (i.e. tar) unto a different hard drive, but I am having problems getting the machine to boot without me having to type the GRUB commands at the GRUB prompt that is presented when the machine boots up off the new hard drive. I have tried to restore the MBR in two ways (the 2nd one is the one that gets me to the GRUB prompt):
1. Get the MBR off the original drive and write it unto the new drive (all via dd), but that did not work at all: the machine hangs right away during boot up. It seems to hang right at the point where the BIOS tries to read the MBR.
Code:
On original drive:
# dd if=/dev/sda of=mbr+part.bin bs=512 count=1
On new drive (new drive is now in place of original drive):
# dd if=mbr+part.bin of=/dev/sda bs=1 count=446 conv=notrunc
2. By using the FEDORA rescue CD, I installed grub unto the new hard drive as follows:
Code:
# chroot /mnt/sysimage
# grub-install --root-directory=/boot hd0
reboot and remove FEDORA CD Using the 2nd option above, I get the GRUB> prompt during bootup. I can then boot into the system by issuing the commands that are in the menu.lst file, followed by the "boot" command. However, I would like for those commands to happen automatically, just like in the original configuration. It seems to me that GRUB is actually finding all its stage files because I doubt the GRUB program (the one displaying the prompt) fits entirely in the 446 bytes it has on the MBR. So, it must be loading its stage 2 (and stage 1.5??) files from my /boot partition. However, if GRUB is loading its stage files off the boot partition, why does it not load/read the menu.lst/grub.conf contained in the boot partition also?
Code:
# ls -l /boot
total 22888
-rw-r--r--. 1 root root 1274567 2009-05-27 16:39 System.map-2.6.29.4-167.fc11.i686.PAE
-rw-r--r-- 1 root root 1274538 2009-06-16 22:27 System.map-2.6.29.5-191.fc11.i686.PAE
[code]....
After a kernel upgrade on my linux, my grub.conf become empty. How can I auto generate grub.conf file? I don't want to do it from scratch.
View 3 Replies View RelatedI have windows vista on one sata HDD, and fedora on a second sata HDD. After installing fedora of course the grub is auto booting fedora. I would like vista to be the default O/S. I dont care if i modify the grub file to have it manually boot vista, or to remove the grub interface all together, i just want it to auto boot vista. My bios is programed to boot my vista drive before my fedora drive, however it keeps booting the grub and it boots fedora, which i find kind of odd. below is the contents of my grub.conf file:
[Code]....
*NOTE: i have already tried changing the 'default=0' to 'default=1' and restarting the computer, as i saw in a different post on these forums, however that did not fix my problem. Im guessing its because i have the operating systems on two seperate drives, where the other guy just had them on a single drive.
**EDIT: after posting i had to modify lines 6 and 10 of my grub.conf file because it had smileys at the end lol. i put a space in between the 8 and the ) for posting purposes only, my actuall file does not have these spaces.
I have just completed a clean install of Fedora 14 on a new disc (/dev/sdc)My old system disc (/dev/sda, an LVM 'vg_phenom00') is still installed.I note that my /etc/fstab has entries for the swap space on both disks;
Code:
# /etc/fstab
# Created by anaconda on Mon Jan 3 09:00:29 2011
[code]....
I just tried setting my vga mode in grub.conf so that I can have my boot splash back after disabling nouveau. Works great. Problem is, now, that after doing this my touchpad is disabled. Anyone else run into this? I'm on an HP dv6, FC13, vga=0x37b. I remove vga mode setting and touchpad works again.
View 1 Replies View RelatedI'm trying to set up some shares on this pc and every time I try to edit the /etc/exports file I get this error. I get the same error when I try to edit /boot/grub.conf file or any other files. Does not matter what editor I use. I'm running f14.
View 3 Replies View RelatedI have just installed a new hard drive with Fedora 14.
How can I edit it when my kernel version is 2.6.35.12-88.fc14.i686.PAE?
I want to dualboot with Windows XP?
Here's what I tried:
It didn't work? What did I type wrong?
I've just installed Fedora (F13) for the first time, on a new HDD, to give myself a dual-boot system. So currently I have:
So, at the appropriate stage in the install menu, there is an option for where to install GRUB, and a drop-down to choose which drive is the primary BIOS boot drive.
However, in both cases, no other drive except my new sdc is visible. So, I can install GRUB to MBR of sdc, or to first sector of boot partition - but no option to put it to my primary boot drive MBR on sda.
Likewise, in the GRUB configuration page, if I go to Add another OS, the only option it gives me is my new Fedora install. It doesn't list the Vista OS on sda at all.
The result is that I can boot to either OS by changing the boot drive priority in BIOS.
I guess my question is this:
- is this expected behaviour from the installer, meaning that I'll need to configure GRUB manually somehow? (gulp ) or
- did I do something wrong in the install process? or
- is this some weird bug manifesting itself?
the latest kernel 2.6.40-4.fc15.x86_64 is somewhat buggy !It does not the include module for the USB Atheros chip 9170.As a result the TP-LINK TL-821N wireless N (very good) does not work !The previous kernel 2.6.38.8-35.fc15.x86_64 does include them as modules.grep AR9170 config-2.6.38.8-35.fc15.x86_64CONFIG_AR9170_USB=mCONFIG_AR9170_LEDS=yHopefully a version including those will be posted soon as an update.
View 14 Replies View RelatedSo I completely fail at making a kernel x86_64, used to make them fine for just x86 but I haven't a clue on how to make them specifically for 64-bit systems.
View 3 Replies View RelatedI suffered a kernel crash today - then noticed a newer kernel was available, so I updated to it.However, it's since crashed again! Here's the message - can anyone tell me what's going on, is this a known issue or is it bad hardware?
general protection fault: 0000 [1] SMP
last sysfs file: /devices/pci0000:00/0000:00:00.0/irq
CPU 2
[code]....
I am trouble trying to get vpnc to work on my laptop.
Using the same computer via Ubuntu, it works fine.
I used to use an older kernel with the cisco vpn client, but had to go through the motions of turning off cpus in order for it to work. I gave that trick a try and it does not work.
I pretty much followed the instructions from: Gentoo Linux Documentation -- Gentoo vpnc HOWTO
The machine completely locks up right after I enter my password...
I don't see anything relevant in the /var/log/messages file.
Is there another log file to look into specific to the vpnc?
i have lot of google search and make lot of suggestion found in google but without any solving for the problem. try to install vmware workstation any verion on my vps which have openvz and kernel 2.6.18-164.15.1.el5.028stab068.9-x86_64 when try to install for exampil vmware workstation 5.5.3 found this problem
root@server [~]# vmware-config.pl
Making sure services for VMware Workstation are stopped.
Stopping VMware services:
Virtual machine monitor [ OK ]
Configuring fallback GTK+ 2.4 libraries.
In which directory do you want to install the mime type icons?
[/usr/share/icons]
[Code]...
