I have a grub.conf (below) with pci=nomsi, also /proc/cmdline and dmesg | more do not show the pci=nomsi.
How can this be? there are no strange characters after quiet and before pci=nomsi. It was edited with vi.
What can I do to get this parameter in my kernel boot line.
Jerry
----------------- default=0 timeout=5 splashimage=(hd0,0)/boot/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.18-164.11.1.el5) root (hd0,0) kernel /boot/vmlinuz-2.6.18-164.11.1.el5 ro root=LABEL=/ rhgb quiet pci=nomsi initrd /boot/initrd-2.6.18-164.11.1.el5.img
cat /proc/cmdline ro root=LABEL=/ rhgb quiet
dmesg | more Linux version 2.6.18-164.11.1.el5 (mockbuild@builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-46)) #1 SMP Wed Jan 20 07:32:21 EST 2010 Command line: ro root=LABEL=/ rhgb quiet BIOS-provided physical RAM map:
Jerry Geis wrote:
I have a grub.conf (below) with pci=nomsi, also /proc/cmdline and dmesg | more do not show the pci=nomsi.
Have you tried booting up, and before GRUB goes on to boot, trying to edit the command line? Then you'll see what GRUB actually thinks it needs to do.
Mike
Jerry Geis wrote:
I have a grub.conf (below) with pci=nomsi, also /proc/cmdline and dmesg | more do not show the pci=nomsi.
How can this be? there are no strange characters after quiet and before pci=nomsi. It was edited with vi.
What can I do to get this parameter in my kernel boot line.
Jerry
default=0 timeout=5 splashimage=(hd0,0)/boot/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.18-164.11.1.el5) root (hd0,0) kernel /boot/vmlinuz-2.6.18-164.11.1.el5 ro root=LABEL=/ rhgb quiet pci=nomsi initrd /boot/initrd-2.6.18-164.11.1.el5.img
cat /proc/cmdline ro root=LABEL=/ rhgb quiet
dmesg | more Linux version 2.6.18-164.11.1.el5 (mockbuild@builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-46)) #1 SMP Wed Jan 20 07:32:21 EST 2010 Command line: ro root=LABEL=/ rhgb quiet BIOS-provided physical RAM map:
I think this was my fault. I accidentally broke the link between /etc/grub.conf and /boot/grub/grub.conf So any changes to /etc/grub.conf were not reflected.
Jerry
Jerry Geis wrote on Fri, 05 Mar 2010 08:02:19 -0500:
I accidentally broke the link between /etc/grub.conf and /boot/grub/grub.conf So any changes to /etc/grub.conf were not reflected.
wait, wait, wait. /etc/grub.conf should be the symlink, not vice versa!
Kai