I asked this in the F18 development forum shortly before it was archived, so I figured I'd re-ask here again in hopes of some actual conversation.
See:
http://forums.fedoraforum.org/showthread.php?t=287518
I noticed after a fedup upgrade that GRUB_CMDLINE_LINUX was changed quite a bit.
I need an eth0 device for the Matlab licence manager. Under fc18, the following worked:
1. Create ifcfg-eth0 file in /etc/sysconfig/network-scripts with NAME=eth0 line.
2.
I have two partitions, one M$ and one FC. Right now grub2 lists FC first in the menu and M$ as 3rd, thus FC is the default. I want to make M$ the default; I don't care if M$ stays 3rd on the list, I just want it default.
Hello I am trying to passthrow video card in xen.
I am using xen 4.1 fedora 17 and Nvidia 9400GT
pciback supported by kernel as module
When I pass xen-pciback.hide="(01:00.0)" param to grub I got error in dmesg
So I removed it from grub and created modprobe.d/zzz.conf
Code:
install nouveau /sbin/modprobe pciback ; /sbin/modprobe --first-time --ignore-install nouveau
Hi folks, I'm installing a brand new Arch Virtualbox VM and I got stuck trying to install Grub2 with a LVM /boot. The command:grub-install --target=i386-pc --recheck --debug /dev/sda The error:/usr/sbin/grub-bios-setup: info: Looking for /dev/sda.
/usr/sbin/grub-bios-setup: info: /dev/sda is a parent of /dev/sda.
/usr/sbin/grub-bios-setup: info: /dev/dm-4 i
Upgraded from F17 to F18 just now using : fedoraproject.org/wiki/FedUp#Network
Command I used:
Code:
sudo fedup --network 18 --debuglog fedupdebug.log --instrepo http://dl.fedoraproject.org/pub/alt/qa/fedup/f18-RC4/x86_64/
Upgrade went smoothly and everything works out the box, but I'm hitting with dependency issues when trying to install new stuff.
Example (when trying to install a
$ sudo grub-install -v
grub-install (GRUB) 2.00-7ubuntu11
$ sudo grub-install /dev/sda3
/usr/sbin/grub-bios-setup: warning: File system `ext2' doesn't support embedding.
/usr/sbin/grub-bios-setup: warning: Embedding is not possible. GRUB can only be installed in this setup by using blocklists.
My desktop PC is dual-boot: Fedora and Ubuntu. Grub2 is "owned" by Ubuntu. In Ubuntu /etc/grub.d I have a 40_custom entry for Fedora. Every time there is a Fedora kernel update, I must edit the 40_custom entry, boot Ubuntu, and run update-grub.
I'm planning to use fedup to upgrade from F17 to F18.
OP, I did just follow WW's suggestion, and successfully upgraded, and rebooted without any issue at all - which should really be no surprise in hindsight, as none of those files should actually be needed for grub to boot properly (AFAIK) - they are all tools for reconfiguring or updating the MBR code (I think!).But in any case, this was the extent of itmv /sbin/grub* /usr/bin/
mv /sbin/instal