Sponsored Content
Full Discussion: Mandrake 8.1 + W98SE Problem
Top Forums UNIX for Dummies Questions & Answers Mandrake 8.1 + W98SE Problem Post 14133 by merlin on Monday 28th of January 2002 04:12:33 PM
Old 01-28-2002
Well we all got to learn somewhere don't we? I've been there done most of that!

When you didn't have windows in the boot option thats because your 'lilo' couldn't see windows. You need to edit the lilo it can be found in "/etc/lilo" (so at console type "vi /etc/lilo") in there you need to add the lines for lilo to see windows to boot. Before editing this file though you need to know what hdaX your windows partition is on! E.G hda1=windows hda2=linux hda3=swap etc etc! Once you've added the correct lines into lilo go to "/etc/sbin" and just type "lilo" that should then make the changes and tell you if it has ben added correctly or if there was a problem! Make a backup of the lilo file before you write it!

With the graphics problem and screen could be because you picked the wrong graphics chipset in the install. At the console type "xconfigurator" then you can change the configuration of your linux box! (just a little tip if you type "xcon" then hit {tab} it should finsih the command off as long as only one command will end with "figurator" if 2 commands end with just the "fig" part in it, it still wont work)

Still after deleting linux your lilo if still there. This is due to your lilo be written into the master boot record (MBR). Few ways you can clean this out. Best easy way I have found is using the only thing Bill Gates made that is good. A windows 98 startup disk. Put the disk in boot the computer at DOS prompt type "fdisk /mbr" That should clean your MBR. Don't have to boot from it but if you can't get to a DOS prompt any other way boot from if!

Well hope that helps you out a little.

:-)
merlin
 

10 More Discussions You Might Find Interesting

1. UNIX Desktop Questions & Answers

Mandrake 8.1

Hi all, I have copied three .ISO files for Mandrake 8.1 from a Linux DVD onto my work LAN. They are: Mandrake81-cd1-inst.I586.iso Mandrake81-cd2-ext.I586.iso Mandrake81-cd3-supp.I586.isoThey're all +650M in size and I'd like to know what I need to do in order to create the three CD's... (3 Replies)
Discussion started by: Cameron
3 Replies

2. UNIX for Dummies Questions & Answers

Here's the fix for the SiS 7012/7018 sound problem in Mandrake 8.2

Edit your /etc/modules.conf file to either remove or comment out the two lines : alias sound-slot-0 snd-card-intel8x0 above snd-card-intel8x0 snd-pcm-oss ...and replace them with the following line: alias sound i810_audio ....viola! After saving and rebooting, now I gots da sound!... (0 Replies)
Discussion started by: DownSouthMoe
0 Replies

3. UNIX for Dummies Questions & Answers

mandrake and os X

can i run mac os X stuff in mandrake? on a intel computer? (1 Reply)
Discussion started by: amicrawler
1 Replies

4. UNIX for Dummies Questions & Answers

Mandrake

I read the old posts about dual booting windows and linux, and I just wanted to clarify something: If I buy the mandrake version of linux, will that by itself partition the hard drive, or do I still have to get a copy of partition magic? If the mandrake version can do it, is it an easy process? ... (6 Replies)
Discussion started by: luke314pi
6 Replies

5. UNIX for Dummies Questions & Answers

need help mandrake os

my hdd root dir keeps dumping on me but when i install i use native linux format i i lost again yesterday is there a recovery methead? or a safe mode that i can go into ? i made a boot disk is it wise to let the formater program to auto alcate? give me a 5gb root drive and a 37gb home i relly... (1 Reply)
Discussion started by: amicrawler2000
1 Replies

6. UNIX for Advanced & Expert Users

Problem with installing mandrake 7.2

I was trying to install mandrake 7.2 in my newly brought used intel pentium III processor with no operating system installed in it. In the boot sequence in the BIOS there is no "boot from the cdrom" option so I made a "boot disk" to boot from the floppy drive. While booting from the floppy I got... (2 Replies)
Discussion started by: cyno
2 Replies

7. UNIX for Dummies Questions & Answers

mandrake 10

i just got mandrake 10 and i installed xine the latest why does it crash my xserver and how do i fix this problem in mandrake 8 - 9.2 i had no problmes with xine until now with 10 (2 Replies)
Discussion started by: amicrawler2004
2 Replies

8. SuSE

mandrake problem

ihave mandrake 9.2 (will upgrade soon to 10) but anyways, i can't get the Hard drive or the CD-ROM or Floppy to show up on the desktop. can anyone help me out? (11 Replies)
Discussion started by: linux_newbe
11 Replies

9. Linux

mandrake

I just installed mandrake 9.2, and all I want right now is for gaim to allow me to use msn.. The version I got now is 0.59.? and I have tried to get the latest version but when I downloaded the rpm it said that there were errors... can someone help... for my rpm packaging I have went to Urpmi and... (3 Replies)
Discussion started by: flimzzy
3 Replies

10. Linux

Mandrake 8.00 installation/Booting problem...Plz Help

Hey everyone, I'm new to the forum. I have a problem with Mandrake 8.00; i have installed it on my old PC with no problems (none mentioned) but on re-booting after the installation it just hangs after listing the devices: Hard Disk, CD-ROM & Floppy A. I have installed it on Packard Bell with... (2 Replies)
Discussion started by: sybella1
2 Replies
GRUBBY(8)						      System Manager's Manual							 GRUBBY(8)

NAME
grubby - command line tool for configuring grub, lilo, and elilo SYNOPSIS
grubby [--add-kernel=kernel-path] [--args=args] [--bad-image-okay] [--boot-filesystem=bootfs] [--bootloader-probe] [--config-file path] [--copy-default] [--default-kernel] [--grub] [--info=kernel-path] [--initrd=initrd-path] [--lilo] [--make-default] [-o path] [--remove-kernel=kernel-path] [--set-default=kernel-path] [--title=entry-title] DESCRIPTION
grubby is a command line tool for updating and displaying information about the configuration files for the grub, lilo, elilo (ia64), and yaboot (powerpc) boot loaders. It is primarily designed to be used from scripts which install new kernels and need to find information about the current boot environment. On Intel x86 platforms, grub is the default bootloader and the configuration file is in /boot/grub/grub.conf. On Intel ia64 platforms, elilo mode is used and the default location for the configuration file is /boot/grub/grub.conf. On PowerPC platforms, yaboot parsing is used and the configuration file should be in /etc/yaboot.conf. There are a number of ways to specify the kernel used for --info, --remove-kernel, and --update-kernel. Specificying DEFAULT or ALL selects the default entry and all of the entries, respectively. If a comma separated list of numbers is given, the boot entries indexed by those numbers are selected. Finally, the title of a boot entry may be specified by using TITLE=title as the argument; all entries with that title are used. OPTIONS
--add-kernel=kernel-path Add a new boot entry for the kernel located at kernel-path. --args=kernel-args When a new kernel is added, this specifies the command line arguments which should be passed to the kernel by default (note they are merged with the arguments from the template if --copy-default is used). When --update-kernel is used, this specifies new arguments to add to the argument list. Multiple, space separated arguments may be used. If an argument already exists the new value replaces the old values. The root= kernel argument gets special handling if the configuration file has special handling for specifying the root filesystem (like lilo.conf does). --bad-image-okay When grubby is looking for a entry to use for something (such as a template or a default boot entry) it uses sanity checks, such as ensuring that the kernel exists in the filesystem, to make sure entries that obviously won't work aren't selected. This option over- rides that behavior, and is designed primarily for testing. --boot-filesystem=bootfs The grub boot loader expects file paths listed in it's configuration path to be relative to the top of the filesystem they are on, rather then relative to the current root filesystem. By default grubby searches the list of currently mounted filesystems to deter- mine this. If this option is given grubby acts as if the specified filesystem was the filesystem containing the kernel (this option is designed primarily for testing). --bootloader-probe grubby tries to determine if grub or lilo is currently installed. When one of those bootloaders is found the name of that bootloader is displayed on stdout. Both could be installed (on different devices), and grubby will print out the names of both bootloaders, one per line. The probe for grub requires a commented out boot directive grub.conf identical to the standard directive in the lilo configuration file. If this is not present grubby will assume grub is not installed (note that anaconda places this directive in grub.conf files it creates). This option is only available on ia32 platforms. --config-file=path Use path as the configuration file rather then the default. --copy-default grubby will copy as much information (such as kernel arguments and root device) as possible from the current default kernel. The kernel path and initrd path will never be copied. --default-kernel Display the full path to the current default kernel and exit. --elilo Use an elilo style configuration file. --grub Use a grub style configuration file instead of lilo style. This is the default on ia32 platforms. --info=kernel-path Display information on all boot entries which match kernel-path. I --initrd=initrd-path Use initrd-path as the path to an initial ram disk for a new kernel being added. --lilo Use a lilo style configuration file. --make-default Make the new kernel entry being added the default entry. --remove-args=kernel-args The arguments specified by kernel-args are removed from the kernels specified by --update-kernel. The root argument gets special handling for configuration files that support separate root filesystem configuration. --remove-kernel=kernel-path Removes all boot entries which match kernel-path. This may be used along with --add-kernel, in which case the new kernel being added will never be removed. --set-default=kernel-path The first entry which boots the specified kernel is made the default boot entry. --title=entry-title When a new kernel entry is added entry-title is used as the title (lilo label) for the entry. If entry-title is longer then maximum length allowed by the bootloader (15 for lilo, unlimited for grub and elilo) the title is shortened to a (unique) entry. --update-kernel=kernel-path The entries for kernels matching kernel-path are updated. Currently the only items that can be updated is the kernel argument list, which is modified via the --args and --remove-args options. --version Display the version of grubby being run and then exit immediately. --yaboot Use an yaboot style configuration file. BUGS
The command line syntax is more then a little baroque. This probably won't be fixed as grubby is only intended to be called from shell scripts which can get it right. SEE ALSO
grub(8), lilo(8), yaboot(8), mkinitrd(8) AUTHOR
Erik Troan <ewt@redhat.com> 4th Berkeley Distribution Thu Jun 21 2002 GRUBBY(8)
All times are GMT -4. The time now is 03:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy