Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi, I run windowsXP (on hda1) and i wanted to check linux out. So i downloaded Debian.
I Installed it to hdd4. the installer installed Lilo to the MBR, and when i rebooted after the install, i only got "L 01 01 01 01" (the 01 went on and on).
To get into windows again, i had to fix the mbr using the recovery console.
After that i tried installing lilo to hdd4, and using the windowsXP boot chooser thingy to boot from hdd4, but i got the same result when i tried this.
Now i am wondering what i did wrong.
I'm a total linux newbie, the only linux distribution i tried before was knoppix. If this is a stupid question, feel free to spank me.
Spank me too. I have the exact same problem. Except I've had different variations, like 01010101010 being blasted on the screen scrolling up forever, and LI 99 99 99 99..., and just LI.
Currently I'm using the bootable slackware CD#2 to get slack, ie using the root=/dev/hda3 paramater.
The only way I figured out how to fix it last time was spend 3 hours low-level formatting the drive. I know theres a real solution somewhere..out there..
this seems to be a common thing with lilo... it's at the wrong place most of the time this happens. open the /etc/lilo.conf and check for a line wich says root=<bla>, change it to root=/dev/hda. if it's there already, something else is wrong. you could also try add a line with just "compact" (without the quotes) wich will make lilo more compact (doh...)
I'm stumped, this lilo stuff is so confusing. I've just been booting off the CD. I'd love to sort it out without pulling out CAPTAIN LOW-LEVEL FORMAT & destroying everything.
a kernel image must be placed in the /boot directory. copy the compiled kernel to the /boot dir and change the lilo configuration for it.
when done, run /sbin/lilo, wich installs lilo
greetz & succes,
.-=~ iluvatar ~=-.
ps: you may also remove the very first line wich states "root=/dev/hda3"... don't know what it's doing there....?
never give up can you boot from a rescue cd or some kind? if you can, nothing is lost... boot from a cd / floppy, and check if the linux partition (hda3) is mounted. if not, mount it. now do a chroot command to the mountpoint. for example if the hda3 partition is not mounted already, try this:
cd /
mkdir hd
mount /dev/hda3 hd/
chroot hd /bin/bash
this will create a mount point (hd), mount the hda3 partition on it, and chroot to it. chroot means this directory will become the root dir, wich has far going effects... you are more or less working on your installed linux now. now you can edit the lilo.conf file, just do:
cd /etc
<editor of choice> lilo.conf
now repair the config, save it, exit the editor and run /sbin/lilo. the lilo command will re-install lilo according to the config file.
Originally posted by LordGoddard how did you fix the MBR using windows? i really REALLY need to know...
I used fixmbr in the windows recovery console (you can enter the recovery console when you boot from your windows cd, if you didn't know that allready).
Originally posted by iluvatar never give up can you boot from a rescue cd or some kind? if you can, nothing is lost... boot from a cd / floppy, and check if the linux partition (hda3) is mounted. if not, mount it. now do a chroot command to the mountpoint. for example if the hda3 partition is not mounted already, try this:
cd /
mkdir hd
mount /dev/hda3 hd/
chroot hd /bin/bash
this will create a mount point (hd), mount the hda3 partition on it, and chroot to it. chroot means this directory will become the root dir, wich has far going effects... you are more or less working on your installed linux now. now you can edit the lilo.conf file, just do:
cd /etc
<editor of choice> lilo.conf
now repair the config, save it, exit the editor and run /sbin/lilo. the lilo command will re-install lilo according to the config file.
greetz & more succes...
.-=~ iluvatar ~=-.
I don't have a boot disc or anything. Is it possible to do it from knoppix?
I think you should be able to boot from any distro CD / floppy.
Mainly, as iluvatar stated, you meerly need to boot, then chroot into your existing system.
If you don't have a boot disk or anything, how did you install the OS in the first place?
As i said before, i'm a total newbie (it took me HOURS to figure out how to edit lilo.conf), so i would say the probabillity i made a giant mistake is high.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.