search for: makeact

...ering logical partition to a primary, hda4. Then I ran "syslinux d:" from a Win98SE DOS-box to (try to) initialize the partition's boot record. And added this from a DOS/Windows example to grub.conf: title LEAF/Bering via syslinux hide (hd0,0) unhide (hd0,3) makeactive rootnoverify (hd0,3) chainloader +1 But the boot failed in grub. I'm also going the path of making grub boot LEAF-Bering directly, and I seem to have that part-way to working. Paul Rogers (paul.rogers at juno.com) http://www.xprt.net/~pgrogers/ http://www.angelfire.com/o...

...inuz-2.6.9-42.ELsmp ro root=LABEL=/ rhgb quiet # initrd /initrd-2.6.9-42.ELsmp.img #title CentOS-4 i386-up (2.6.9-42.EL) # root (hd1,1) # kernel /vmlinuz-2.6.9-42.EL ro root=LABEL=/ rhgb quiet # initrd /initrd-2.6.9-42.EL.img title XP SP2 rootnoverify (hd1,0) makeactive chainloader +1 And, finally... [root at seth ~]# cat /boot/grub/device.map # this device map was generated by anaconda (fd0) /dev/fd0 (hd0) /dev/hdb (hd1) /dev/sda Alls seems good but the problem stills there: no error messages, simply hangs... ?Any clue? -- Jordi Espas...

HI all, I had centos on a laptop (dual boot xp). I am giving the laptop to another person so I removed centos. Now when I reboot grub is confused... I tried to manually enter rootnoverify (hd0,0) makeactive chainloader +1 boot This does boot into XP but how do I tell grub that this is the new rules and do this everytime at boot. Thanks, Jerry

HI, i have updatete to 6.1-PRERELEASE and after the "installworld" step GRUB is unable to boot FreeBSD. After i did the installworld and rebooted the GRUB error was: 23 : Error while parsing number I have reinstalled the standard FreeBSD loader for now. Booting with a GRUB boot-floppy i am able to start either XP or Linux but trying to start FreeBSD the system just reboots, no

...06.unsupported.img title CentOS (2.6.9-11.EL) root (hd0,5) kernel /vmlinuz-2.6.9-11.EL ro root=LABEL=/ rhgb quiet initrd /initrd-2.6.9-11.EL.img title Solaris 10 root (hd1,0) kernel /platform/i86pc/multiboot module /platform/i86pc/boot_archive makeactive chainloader +1 title Windows xp rootnoverify (hd0,0) chainloader +1 Note: This is my first post and I have learned a lot from your forum since I moved from mandrake 3 months ago. Thanks alot guys __________________________________________________ Do You Yahoo!? Tired...

...machine, then modify /boot/grub/grub.conf similar to the following: default=0 *** this will point to the default OS, WIN2k in this case, =1 for RH *** timeout=10 splashimage=(hd0,2)/grub/splash.xpm.gz *** add these lines to point to YOUR WIN2K partition *** title Win2K root (hd0,0) makeactive chainloader +1 *** END ADDITION *** title Red Hat Linux (2.4.18-3) root (hd0,2) kernel /vmlinuz-2.4.18-3 ro root=/dev/hda5 initrd /initrd-2.4.18-3.img Next you will have to mount your drive using: mount -t vfat /mnt/windows *** This assumes that your have defined the MOUNT location to be...

...d0,1) kernel (hd0,1)/kernel-2.6.11-gentoo-r4 init=/linuxrc # For booting XEN title Xen 2.0 / XenLinux 2.6.10 root (hd0,1) kernel /xen.gz module /vmlinuz-2.6.10-xen0 root=/dev/hda3 ro console=tty0 # For booting Windows NT or Windows95 #title Windows NT / Windows 95 boot menu #rootnoverify (hd0,0) #makeactive #chainloader +1 # For loading DOS if Windows NT is installed # chainload /bootsect.dos # For installing GRUB into the hard disk title Install GRUB into the hard disk root (hd0,1) setup (hd0) ############################# snap ###################################### mount -l: ###########...

...are called initrd.img-2.6.18-something... while > CentOS initrd is initrd-2.6.18-something.img. Hence the confusion. You could consider installing GRUB from CentOS in the MBR of the CentOS disk (though, the boot partition would be fine too), and add something like --- title CentOS root (hd1) makeactive chainloader +1 --- To your Debian GRUB configuration. This prevents that you'll have to update your Debian GRUB configuration again after n kernel updates (where n is the number set with the installonlyn yum plugin). -- Daniel ------------------------------ Message: 10 Date: Mon, 28 Ma...

...are called initrd.img-2.6.18-something... while > CentOS initrd is initrd-2.6.18-something.img. Hence the confusion. You could consider installing GRUB from CentOS in the MBR of the CentOS disk (though, the boot partition would be fine too), and add something like --- title CentOS root (hd1) makeactive chainloader +1 --- To your Debian GRUB configuration. This prevents that you'll have to update your Debian GRUB configuration again after n kernel updates (where n is the number set with the installonlyn yum plugin). -- Daniel ------------------------------ Message: 10 Date: Mon, 28 Ma...