Jas Posted November 3, 2004 Report Share Posted November 3, 2004 i recently installed winxp on the rest of the hdd space i had, but now when i turn on teh computer, it just goes straight into xp, i asked around other places they said something about my MBR being overwritten? eh they told me to boot from the cd, i posted back that the cd just takes me into setup, and when i hit F1 for options, it goes into setup anyway, so question now is, how do i get into mandrake...? Quote Link to comment Share on other sites More sharing options...
liquidzoo Posted November 3, 2004 Report Share Posted November 3, 2004 2 ways that I can think of: 1: boot to cd, hit F1 and type rescue. Then reinstall the bootloader from the menu there, but apparently that option is not working for you. 2: boot to a livecd (like knoppix), open a konsole and su to root, mount your / partition in /mnt (ie: mount /dev/hdb1 /mnt for me), then type chroot /mnt to chroot into your Mandrake installation. Now would also be a good time to add XP to lilo.conf so edit that (vim /etc/lilo.conf) and add something like this: other=/dev/hda1 label="XP" table=/dev/hda Save that file, then type lilo -v to reload lilo. Exit out and reboot and all should be well. Quote Link to comment Share on other sites More sharing options...
SpikeyKlitske Posted November 3, 2004 Report Share Posted November 3, 2004 :woops: stupid addition perhaps, but uh make sure your f-lock is on (if your using a fancy m$ keyboard) otherwise the function keys do not work. Quote Link to comment Share on other sites More sharing options...
Jas Posted November 4, 2004 Author Report Share Posted November 4, 2004 ok im in knoppix right now, starting to get REALLY pissed off now, i cant chroot, i get: bash: /dev/null: Permission denied bash: /dev/null: Permission denied bash: /dev/null: Permission denied and i tried editing lilo.conf, says i cant write it, so i go as su and chmod a=rwx and i still cant write to it, what do i do now?! Quote Link to comment Share on other sites More sharing options...
liquidzoo Posted November 4, 2004 Report Share Posted November 4, 2004 Are you issuing the chroot command as root? If not, you have to do that. Also, you will have to modify the lilo file as root as well. In knoppix, there is no root password. Just open a console, type su and hit enter Quote Link to comment Share on other sites More sharing options...
Jas Posted November 4, 2004 Author Report Share Posted November 4, 2004 okay, after about a half hour of that, i finally decided to just try option 1, this time it actually worked, i went to reinstall boot loader, and i got the SAME error msg i was getting that i got in knoppix Fatal: APPEND or LITERAL may not contain "vga=" Quote Link to comment Share on other sites More sharing options...
liquidzoo Posted November 4, 2004 Report Share Posted November 4, 2004 You need to edit your lilo.conf line then. The vga= line needs to be separate from the append= line Here's my lilo.conf file for comparison: # File generated by DrakX/drakboot # WARNING: do not forget to run lilo after modifying this file default="linux" boot=/dev/hda map=/boot/map vga=794 keytable=/boot/us.klt prompt nowarn timeout=100 message=/boot/message menu-scheme=wb:bw:wb:bw image=/boot/vmlinuz label="linux" root=/dev/hdb1 initrd=/boot/initrd.img append="devfs=nomount splash=silent" vga=788 read-only other=/dev/hda1 label="XP" table=/dev/hda image=/boot/vmlinuz-2.6.8.1-8mdk label="linux-2681-8" root=/dev/hdb1 initrd=/boot/initrd-2.6.8.1-8mdk.img append="devfs=nomount splash=silent" vga=788 read-only Quote Link to comment Share on other sites More sharing options...
Jas Posted November 4, 2004 Author Report Share Posted November 4, 2004 i've edited it, i just keep getting root@ttyp0[sbin]# ./lilo Unrecognized token "! Please edit /etc/lilo.conf before running lilo!" at or above line 20 in file '/etc/lilo.conf' why doesnt it reinstall the whole thing when i go into rescue? what the hells the point at looking at my conf file if i want it to reinstall anyway? BTW: that line its saying on line 20, i took that out a long time ago. Quote Link to comment Share on other sites More sharing options...
liquidzoo Posted November 4, 2004 Report Share Posted November 4, 2004 Can you post the contents of lilo.conf here for us to look at? Also, you don't need the ./ before lilo, just typing lilo will work. Quote Link to comment Share on other sites More sharing options...
durvish Posted November 4, 2004 Report Share Posted November 4, 2004 don't you have to run /sbin/lilo after editing lilo? Quote Link to comment Share on other sites More sharing options...
liquidzoo Posted November 4, 2004 Report Share Posted November 4, 2004 don't you have to run /sbin/lilo after editing lilo? <{POST_SNAPBACK}> Yes, but if he's getting an error after that, I want to see his /etc/lilo.conf and see if we can find the error Quote Link to comment Share on other sites More sharing options...
durvish Posted November 4, 2004 Report Share Posted November 4, 2004 I agree. I just wanted to make sure he was running that command and editing. Quote Link to comment Share on other sites More sharing options...
Jas Posted November 6, 2004 Author Report Share Posted November 6, 2004 ok, just got back in knoppix, config file: # /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)', # --------------- `install-mbr(8)', `/usr/share/doc/lilo/', # and `/usr/share/doc/mbr/'. # +---------------------------------------------------------------+ # | !! Reminder !! | # | | # | Don't forget to run `lilo' after you make changes to this | # | conffile, `/boot/bootmess.txt', or install a new kernel. The | # | computer will most likely fail to boot if a kernel-image | # | post-install script or you don't remember to run `lilo'. | # | | # +---------------------------------------------------------------+ # Support LBA for large hard disks. # lba32 # Specifies the boot device. This is where Lilo installs its boot # block. It can be either a partition, or the raw device, in which # case it installs in the MBR, and will overwrite the current MBR. # boot=/dev/hda # Specifies the device that should be mounted as root. (`/') # # Enable map compaction: # Tries to merge read requests for adjacent sectors into a single # read request. This drastically reduces load time and keeps the # map smaller. Using `compact' is especially recommended when # booting from a floppy disk. It is disabled here by default # because it doesn't always work. # # compact # Installs the specified file as the new boot sector # install=/boot/boot-menu.b backup=/dev/null # Specifies the location of the map file # map=/boot/map # You can set a password here, and uncomment the `restricted' lines # in the image definitions below to make it so that a password must # be typed to boot anything but a default configuration. If a # command line is given, other than one specified by an `append' # statement in `lilo.conf', the password will be required, but a # standard default boot will not require one. # # This will, for instance, prevent anyone with access to the # console from booting with something like `Linux init=/bin/sh', # and thus becoming `root' without proper authorization. # # Note that if you really need this type of security, you will # likely also want to use `install-mbr' to reconfigure the MBR # program, as well as set up your BIOS to disallow booting from # removable disk or CD-ROM, then put a password on getting into the # BIOS configuration as well. Please RTFM `install-mbr(8)'. # # password=tatercounter2000 # Specifies the number of deciseconds (0.1 seconds) LILO should # wait before booting the first image. # # delay=20 timeout=100 # You can put a customized boot message up if you like. If you use # `prompt', and this computer may need to reboot unattended, you # must specify a `timeout', or it will sit there forever waiting # for a keypress. `single-key' goes with the `alias' lines in the # `image' configurations below. eg: You can press `1' to boot # `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'. # # message=/boot/bootmess.txt # prompt # single-key # delay=100 # timeout=100 # Specifies the VGA text mode at boot time. (normal, extended, ask, <mode>) # # vga=ask # vga=9 # vga=normal # Kernel command line options that apply to all installed images go # here. See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in # the Linux kernel `Documentation' directory. # append="" # Boot up Linux by default. # default=Knoppix image=/vmlinuz append="lang=de apm=power-off hda=scsi hdb=scsi hdc=scsi hdd=scsi hde=scsi hdf=scsi hdg=scsi hdh=scsi vga=791 quiet BOOT_IMAGE=knoppix" root=/dev/hda5 label=Knoppix read-write # restricted # alias=1 #image=/vmlinuz.old # label=Linux-OLD # read-only # optional # restricted # alias=2 # If you have another OS on this machine to boot, you can uncomment the # following lines, changing the device name on the `other' line to # where your other OS' partition is. # other=/dev/hda1 label=WinXP restricted alias=3 Quote Link to comment Share on other sites More sharing options...
Jas Posted November 7, 2004 Author Report Share Posted November 7, 2004 uhm, anyone know how i could fix it, or am i just gonna have to format the partition =( Quote Link to comment Share on other sites More sharing options...
durvish Posted November 7, 2004 Report Share Posted November 7, 2004 That looks like your Knoppix Lilo can you post your Mandrake installed Lilo Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.