Re: [newbie] Back to the forgotten beginning ~ lilo
SnapafunFrank wrote: *** I had this hdd drive only to start with and successfully got dual booting with it before consigning it to be slave when I went to update to Mandrake10. *** *** Now everything Mikkel writes here has finely woken me up to what needs to be done and I look forward to the challenge because Mikkel has 'hit the nail on the head', so to speak. As Mandrake 9 was installed whilst the slave was the only hdd on my system then of course everything in the config files points to hda and of course will need to be changed. So where do I start and what do I look for once I have booted into this system ? [ This is an exercise only for me and not a mission critical requirement so I will, hopefully with the help offered here, take this one step at a time and if it is worthwhile and others agree, I will post it to the TWiki as a possible system recovery idea.] Anyway, with sleeves rolled up I venture forth. Here are the files I need to investigate that I know about to date - please add others as you think of them. I'm of course referring to the hdb files only here. /etc/fstab /etc/lilo.config mkdir /boot-9 mount /dev/hdb2 /boot-9 Use this in lilo: image=/boot-9/vmlinuz label=linux90 root=/dev/hdb5 initrd=/boot-9/initrd.img append=noapic devfs=mount acpi=ht splash=silent vga=788 read-only Add a line in /etc/fstab to mount boot-9 in the future. (Coppy the line for /boot, and change /boot to /boot-9 and /dev/hda2 to /dev/hdb2) Now, if /dev/hdb was /dev/hda when you installed MDK9, then you will have to edit /etc/fstab on that version, and change everything that refers to /dev/hda to /dev/hdb. Another way to do it is use: other=/dev/hdb label=linux90 Then, in 9.0, change /etc/lilo.conf so that it installs in the MBR of the second drive. Hmmm Not sure I can do this without actually having MDK9 running at the time otherwise to my way of thinking, it will install directly to the master MBR surely?? Even then I'm not sure how to control running /sbin/lilo to be sure it actually installs onto the hdb MBR. boot=/dev/hda becomes boot=/dev/hdb. What happens then is when you pick linux90, you get a second boot screen. Again, if you installed 9.0 when the drive was the first hard drive, you have some editing to do. Both in /etc/fstab, and /etc/lilo.conf. You will also need to run lilo when in 9.0 to update the boot loader on the second drive. Can you boot 9.0 now, or do you need instructions on how to mount the partitions, and make the changes? I haven't gone this way yet Mikkel because I think things will only fall over until all changes to config files are made. I do like your idea of having the second logon screen option and will venture that way first once files are changed. One thought also for now so as to keep my options open, will # ln -s my MDK9 vmlinuz from within the master hdd /boot partition offer a way? I'm not sure that the link would cross hdd's at this point of booting a system so thought I'd just ask. ( Once the config files are dealt with of course ). Another issue I may need to face is the fact that I have updated my nVidia driver - is it possible to recompile a kernel on another harddrive? I think I ought to be able to re-configure the kernel from text mode once I have access to the old installation - just a'wondering again. Well that ought to do for now, back to forming a project list so as to not waste any of the valuable help given here. A great way to get to know more of Linux and my own system even. You can compile a kernel for 9.0 in 10.1, but it would probably be simpler to get 9.0 working, and then compile the kernel there. It shouldn't be too hard. Try this: (Without the parts after # mkdir /mnt/root-9 #Mount point for 9.0 / mount /dev/hdb5 /mnt/root-9#Mount your 9.0 root file system. mount /dev/hdb2 /mnt/root-9/boot #Get the 9.0 boot directory mounted. chroot /mnt/root-9 #Change to 9.0 file system. At this point, your file system for that login secion looks the same as if you had booted into 9.0. From here, you will want to edit 3 files. /etc/lilo - change all references to /dev/hda to /dev/hdb. (/dev/hda2 becomes /dev/hdb2, /dev/hda becomes /dev/hdb, and so on.) /etc/fstab - same changes. Also, if the CD-ROM changed, update that. /etc/inittab - change id:5:initdefault to id:3:initdefault. This sets teh system to boot to the CLI. Now, after you have made the changes, run lilo -v to update the boot record on the slave hard drive. You can then type exit to return to 10.1. You should now be able to boot to 9.0 using the other=/dev/hdb entry in 10.1's lilo.conf. The trick to all this is the chroot command. It changes the root file system to the directory you specify, but only for the user running the command, and only for terminal. It works both in the command line, and in an xterm. If
Re: [newbie] Back to the forgotten beginning ~ lilo
Mikkel L. Ellertson wrote: SnapafunFrank wrote: Basically, I have two hdd's with the now slave having suffered my first attempts at Linux and of course, the last 9x going [ WinMe }. I can boot into WinMe without any hassles whatsoever but am unable to get lilo.conf right to boot into the old linux9.1 OS I have also installed on that hdd. Latest attempt: other=/dev/ide/host0/bus0/target1/lun0/part2 [ My boot partition on this hdd ] label=linux90 table=/dev/hdb image=/boot/vmlinuz root=/dev/hdb5 initrd=/boot/initrd.img append=noapic devfs=mount acpi=ht splash=silent vga=788 read-only I have tried other=/dev/hdb2 ( my boot partition on this drive ) and tried also other=/dev/hdb2 [ WinMe starts out as other=/dev/hdb1 ] I have made sure that vmlinuz and initrd.img exist on that boot partition still. I added the table=/dev/hdb but still no go. So someone want to slap me over the wrist for being dump here somewhere? Dumb question time - Is this lilo.conf you are working with on the second hard drive? Was the drive /dev/hdb when you installed Linux on it, or did you just have the drive with Linux on it in the machine when you installed it, and added back the Windows drive? Or do you have both Linux and Windows on the first drive, and you are trying to boot a second Linux install from the second drive? Mikkel Sorry for the delay in getting back to you folk but hopefully I can make up for it now. First my lilo.conf [ Note: this is on my master hdd and is booting Mandrake10 Official and then of course my WinMe which is on the slave hdd.] # File generated by DrakX/drakboot and reconfigured by SnapafunFrank. # WARNING: do not forget to run lilo after modifying this file boot=/dev/hda map=/boot/map default=windows keytable=/boot/us.klt prompt nowarn timeout=200 message=/boot/message menu-scheme=wb:bw:wb:bw image=/boot/vmlinuz263 label=linux263 root=/dev/hda5 initrd=/boot/initrd263.img append=noapic devfs=mount acpi=ht splash=silent vga=788 read-only image=/boot/vmlinuz2610 label=linux2610 root=/dev/hda5 vga=788 append= noapic devfs=mount acpi=ht splash=silent initrd=/boot/initrd2610.img read-only image=/boot/vmlinuz267 label=linux267 root=/dev/hda5 initrd=/boot/initrd267.img append=noapic devfs=mount acpi=ht splash=silent vga=788 read-only image=/boot/vmlinuz263 label=linux-nonfb263 root=/dev/hda5 initrd=/boot/initrd263.img append=noapic devfs=mount acpi=ht splash=silent read-only image=/boot/vmlinuz2610 label=linux-nonfb2610 root=/dev/hda5 initrd=/boot/initrd2610.img append=noapic devfs=mount acpi=ht splash=silent read-only image=/boot/vmlinuz267 label=linux-nonfb267 root=/dev/hda5 initrd=/boot/initrd267.img append=noapic devfs=mount acpi=ht splash=silent read-only image=/boot/vmlinuz263 label=failsafe263 root=/dev/hda5 initrd=/boot/initrd263.img append=failsafe noapic acpi=ht devfs=nomount read-only image=/boot/vmlinuz2610 label=failsafe2610 root=/dev/hda5 initrd=/boot/initrd2610.img append=failsafe noapic acpi=ht devfs=nomount read-only image=/boot/vmlinuz267 label=failsafe267 root=/dev/hda5 initrd=/boot/initrd267.img append=failsafe noapic acpi=ht devfs=nomount read-only other=/dev/hdb1 label=windows table=/dev/hdb map-drive=0x80 to=0x81 map-drive=0x81 to=0x80 image=/boot/vmlinuz2422 label=linux2422 root=/dev/hda5 initrd=/boot/initrd2422.img append=noapic devfs=mount acpi=ht splash=silent read-only #other=/dev/ide/host0/bus0/target1/lun0/part2 # label=linux90 # table=/dev/hdb # image=/boot/vmlinuz # root=/dev/hdb5 # initrd=/boot/initrd.img # append=noapic devfs=mount acpi=ht splash=silent # vga=788 # read-only image=/boot/memtest-1.11.bin label=memtest-1.11 read-only Hope someone is suitably impressed ~ I can boot the lot seen here (other than the system on the slave hdd) albeit that except for linux263, the others are only to text consoles at the moment because I have yet to compile the new nVidia drivers as I have done for the 2.6.3-7 kernel. And oh yeah - haven't convinced Jan yet so the default is still Windows - got to get my LAN started so that she can play her cards on Linux without probably knowing it initially. No, she ain't dumb, I'm just being a little sneaky is all. Anyway, back to my problem. I do not believe that starting out with image=/boot/vmlinuz will not work because there is nothing in that to tell lilo to find the image on the slave (hdb) drive. Please correct me if'n I'm wrong here! To explain how I got WinMe to work you need to
Re: [newbie] Back to the forgotten beginning ~ lilo
On Thu, 10 Feb 2005 00:24:04 +1300 SnapafunFrank [EMAIL PROTECTED] wrote: Dumb question time - Is this lilo.conf you are working with on the second hard drive? Was the drive /dev/hdb when you installed Linux on it, or did you just have the drive with Linux on it in the machine when you installed it, and added back the Windows drive? Or do you have both Linux and Windows on the first drive, and you are trying to boot a second Linux install from the second drive? Mikkel Sorry for the delay in getting back to you folk but hopefully I can make up for it now. First my lilo.conf [ Note: this is on my master hdd and is booting Mandrake10 Official and then of course my WinMe which is on the slave hdd.] # File generated by DrakX/drakboot and reconfigured by SnapafunFrank. # WARNING: do not forget to run lilo after modifying this file boot=/dev/hda map=/boot/map default=windows keytable=/boot/us.klt prompt nowarn timeout=200 message=/boot/message menu-scheme=wb:bw:wb:bw image=/boot/vmlinuz263 label=linux263 root=/dev/hda5 initrd=/boot/initrd263.img append=noapic devfs=mount acpi=ht splash=silent vga=788 read-only image=/boot/vmlinuz2610 label=linux2610 root=/dev/hda5 vga=788 append= noapic devfs=mount acpi=ht splash=silent initrd=/boot/initrd2610.img read-only image=/boot/vmlinuz267 label=linux267 root=/dev/hda5 initrd=/boot/initrd267.img append=noapic devfs=mount acpi=ht splash=silent vga=788 read-only image=/boot/vmlinuz263 label=linux-nonfb263 root=/dev/hda5 initrd=/boot/initrd263.img append=noapic devfs=mount acpi=ht splash=silent read-only image=/boot/vmlinuz2610 label=linux-nonfb2610 root=/dev/hda5 initrd=/boot/initrd2610.img append=noapic devfs=mount acpi=ht splash=silent read-only image=/boot/vmlinuz267 label=linux-nonfb267 root=/dev/hda5 initrd=/boot/initrd267.img append=noapic devfs=mount acpi=ht splash=silent read-only image=/boot/vmlinuz263 label=failsafe263 root=/dev/hda5 initrd=/boot/initrd263.img append=failsafe noapic acpi=ht devfs=nomount read-only image=/boot/vmlinuz2610 label=failsafe2610 root=/dev/hda5 initrd=/boot/initrd2610.img append=failsafe noapic acpi=ht devfs=nomount read-only image=/boot/vmlinuz267 label=failsafe267 root=/dev/hda5 initrd=/boot/initrd267.img append=failsafe noapic acpi=ht devfs=nomount read-only other=/dev/hdb1 label=windows table=/dev/hdb map-drive=0x80 to=0x81 map-drive=0x81 to=0x80 image=/boot/vmlinuz2422 label=linux2422 root=/dev/hda5 initrd=/boot/initrd2422.img append=noapic devfs=mount acpi=ht splash=silent read-only #other=/dev/ide/host0/bus0/target1/lun0/part2 # label=linux90 # table=/dev/hdb # image=/boot/vmlinuz # root=/dev/hdb5 # initrd=/boot/initrd.img # append=noapic devfs=mount acpi=ht splash=silent # vga=788 # read-only image=/boot/memtest-1.11.bin label=memtest-1.11 read-only Hope someone is suitably impressed ~ I can boot the lot seen here (other than the system on the slave hdd) albeit that except for linux263, the others are only to text consoles at the moment because I have yet to compile the new nVidia drivers as I have done for the 2.6.3-7 kernel. And oh yeah - haven't convinced Jan yet so the default is still Windows - got to get my LAN started so that she can play her cards on Linux without probably knowing it initially. No, she ain't dumb, I'm just being a little sneaky is all. Anyway, back to my problem. I do not believe that starting out with image=/boot/vmlinuz will not work because there is nothing in that to tell lilo to find the image on the slave (hdb) drive. Please correct me if'n I'm wrong here! To explain how I got WinMe to work you need to understand that windows must think it's in control, hence the 'map' entries - I turn things on for windows then turn them off again ~ enough to fool windows into believing it is in control. So, though starting with other- may not be the way, I need to tell lilo where to find the image I want it to use, and that critter is in the boot partition on hdb which the current system sees as /mnt/hdb2_boot . Lilo of course would see it as /dev/hdb2. Basically, lilo needs to be pointed at that partition the moment I select it as an option. What I've done in the past (not saying it is the correct way to do it, or the only way) is to copy all the necessary files out of /boot from all partitions which
Re: [newbie] Back to the forgotten beginning ~ lilo
SnapafunFrank wrote: Mikkel L. Ellertson wrote: SnapafunFrank wrote: Basically, I have two hdd's with the now slave having suffered my first attempts at Linux and of course, the last 9x going [ WinMe }. I can boot into WinMe without any hassles whatsoever but am unable to get lilo.conf right to boot into the old linux9.1 OS I have also installed on that hdd. Latest attempt: other=/dev/ide/host0/bus0/target1/lun0/part2 [ My boot partition on this hdd ] label=linux90 table=/dev/hdb image=/boot/vmlinuz root=/dev/hdb5 initrd=/boot/initrd.img append=noapic devfs=mount acpi=ht splash=silent vga=788 read-only I have tried other=/dev/hdb2 ( my boot partition on this drive ) and tried also other=/dev/hdb2 [ WinMe starts out as other=/dev/hdb1 ] I have made sure that vmlinuz and initrd.img exist on that boot partition still. I added the table=/dev/hdb but still no go. So someone want to slap me over the wrist for being dump here somewhere? Dumb question time - Is this lilo.conf you are working with on the second hard drive? Was the drive /dev/hdb when you installed Linux on it, or did you just have the drive with Linux on it in the machine when you installed it, and added back the Windows drive? Or do you have both Linux and Windows on the first drive, and you are trying to boot a second Linux install from the second drive? Mikkel Sorry for the delay in getting back to you folk but hopefully I can make up for it now. First my lilo.conf [ Note: this is on my master hdd and is booting Mandrake10 Official and then of course my WinMe which is on the slave hdd.] # File generated by DrakX/drakboot and reconfigured by SnapafunFrank. # WARNING: do not forget to run lilo after modifying this file boot=/dev/hda map=/boot/map default=windows keytable=/boot/us.klt prompt nowarn timeout=200 message=/boot/message menu-scheme=wb:bw:wb:bw image=/boot/vmlinuz263 label=linux263 root=/dev/hda5 initrd=/boot/initrd263.img append=noapic devfs=mount acpi=ht splash=silent vga=788 read-only image=/boot/vmlinuz2610 label=linux2610 root=/dev/hda5 vga=788 append= noapic devfs=mount acpi=ht splash=silent initrd=/boot/initrd2610.img read-only image=/boot/vmlinuz267 label=linux267 root=/dev/hda5 initrd=/boot/initrd267.img append=noapic devfs=mount acpi=ht splash=silent vga=788 read-only image=/boot/vmlinuz263 label=linux-nonfb263 root=/dev/hda5 initrd=/boot/initrd263.img append=noapic devfs=mount acpi=ht splash=silent read-only image=/boot/vmlinuz2610 label=linux-nonfb2610 root=/dev/hda5 initrd=/boot/initrd2610.img append=noapic devfs=mount acpi=ht splash=silent read-only image=/boot/vmlinuz267 label=linux-nonfb267 root=/dev/hda5 initrd=/boot/initrd267.img append=noapic devfs=mount acpi=ht splash=silent read-only image=/boot/vmlinuz263 label=failsafe263 root=/dev/hda5 initrd=/boot/initrd263.img append=failsafe noapic acpi=ht devfs=nomount read-only image=/boot/vmlinuz2610 label=failsafe2610 root=/dev/hda5 initrd=/boot/initrd2610.img append=failsafe noapic acpi=ht devfs=nomount read-only image=/boot/vmlinuz267 label=failsafe267 root=/dev/hda5 initrd=/boot/initrd267.img append=failsafe noapic acpi=ht devfs=nomount read-only other=/dev/hdb1 label=windows table=/dev/hdb map-drive=0x80 to=0x81 map-drive=0x81 to=0x80 image=/boot/vmlinuz2422 label=linux2422 root=/dev/hda5 initrd=/boot/initrd2422.img append=noapic devfs=mount acpi=ht splash=silent read-only #other=/dev/ide/host0/bus0/target1/lun0/part2 # label=linux90 # table=/dev/hdb # image=/boot/vmlinuz # root=/dev/hdb5 # initrd=/boot/initrd.img # append=noapic devfs=mount acpi=ht splash=silent # vga=788 # read-only image=/boot/memtest-1.11.bin label=memtest-1.11 read-only Hope someone is suitably impressed ~ I can boot the lot seen here (other than the system on the slave hdd) albeit that except for linux263, the others are only to text consoles at the moment because I have yet to compile the new nVidia drivers as I have done for the 2.6.3-7 kernel. And oh yeah - haven't convinced Jan yet so the default is still Windows - got to get my LAN started so that she can play her cards on Linux without probably knowing it initially. No, she ain't dumb, I'm just being a little sneaky is all. Anyway, back to my problem. I do not believe that starting out with image=/boot/vmlinuz will not work because there is nothing in that to tell lilo to find the image on the slave (hdb) drive. Please correct me if'n I'm wrong here! To explain how I got WinMe to
Re: [newbie] Back to the forgotten beginning ~ lilo
Steve Jeppesen wrote: On Thu, 10 Feb 2005 00:24:04 +1300 SnapafunFrank [EMAIL PROTECTED] wrote: Mikkel Big SNIP to focus on problem- made by Frank #other=/dev/ide/host0/bus0/target1/lun0/part2 # label=linux90 # table=/dev/hdb # image=/boot/vmlinuz # root=/dev/hdb5 # initrd=/boot/initrd.img # append=noapic devfs=mount acpi=ht splash=silent # vga=788 # read-only End of first big SNIP Bit of a SNIP here - Frank You are correct that image=/boot/vmlinuz probably wouldn't work on your system because that is typically a link to which ever kernel version is installed. Your system appears to be setup to not use such a link, so you would just have to show it as image=/boot/vmlinuz-2.whatever.version.youhave then you would also need to modify initrd=/boot/initrd.img to point to what ever version of initrd you would be using, like your other entries in lilo.conf do. if you were to copy vmlinuz, initrd, config, etc. (not exactly sure off the top of my head which files you need to copy out of /boot - anybody know off hand?) from your 9.1 install IRC to which ever partition that controls your bootup, then instead of; other=/dev/ide/host0/bus0/target1/lun0/part2 label=linux90 table=/dev/hdb image=/boot/vmlinuz root=/dev/hdb5 initrd=/boot/initrd.img append=noapic devfs=mount acpi=ht splash=silent vga=788 read-only how about this; image=/boot/vmlinuz.your.version.here label=linux90 root=/dev/hdb5 initrd=/boot/initrd.your.version.here.img append=noapic devfs=mount acpi=ht splash=silent vga=788 read-only other than that, I would tend to suspect that maybe root=/dev/hdb5 may need to have a different partition number instead of 5. Hope I am not too confusing! It isn't that it is confusing because it raises question that my technical logic trips up and that is what may make things confusing. Keep the input coming as it is most helpful. Brought over from another reply I still don't know how you installed Linux on the second drive. But there are a couple of things you could do. One would be to something like this: *** I had this hdd drive only to start with and successfully got dual booting with it before consigning it to be slave when I went to update to Mandrake10. *** *** Now everything Mikkel writes here has finely woken me up to what needs to be done and I look forward to the challenge because Mikkel has 'hit the nail on the head', so to speak. As Mandrake 9 was installed whilst the slave was the only hdd on my system then of course everything in the config files points to hda and of course will need to be changed. So where do I start and what do I look for once I have booted into this system ? [ This is an exercise only for me and not a mission critical requirement so I will, hopefully with the help offered here, take this one step at a time and if it is worthwhile and others agree, I will post it to the TWiki as a possible system recovery idea.] Anyway, with sleeves rolled up I venture forth. Here are the files I need to investigate that I know about to date - please add others as you think of them. I'm of course referring to the hdb files only here. /etc/fstab /etc/lilo.config mkdir /boot-9 mount /dev/hdb2 /boot-9 Use this in lilo: image=/boot-9/vmlinuz label=linux90 root=/dev/hdb5 initrd=/boot-9/initrd.img append=noapic devfs=mount acpi=ht splash=silent vga=788 read-only Add a line in /etc/fstab to mount boot-9 in the future. (Coppy the line for /boot, and change /boot to /boot-9 and /dev/hda2 to /dev/hdb2) Now, if /dev/hdb was /dev/hda when you installed MDK9, then you will have to edit /etc/fstab on that version, and change everything that refers to /dev/hda to /dev/hdb. Another way to do it is use: other=/dev/hdb label=linux90 Then, in 9.0, change /etc/lilo.conf so that it installs in the MBR of the second drive. Hmmm Not sure I can do this without actually having MDK9 running at the time otherwise to my way of thinking, it will install directly to the master MBR surely?? Even then I'm not sure how to control running /sbin/lilo to be sure it actually installs onto the hdb MBR. boot=/dev/hda becomes boot=/dev/hdb. What happens then is when you pick linux90, you get a second boot screen. Again, if you installed 9.0 when the drive was the first hard drive, you have some editing to do. Both in /etc/fstab, and /etc/lilo.conf. You will also need to run lilo when in 9.0 to update the boot loader on the second drive. Can you boot 9.0 now, or do you need instructions on how to mount the partitions, and make the changes? I haven't gone this way yet Mikkel because I think things will only fall over until all changes to config files are made. I do like your idea of having the second logon screen option and will venture that way first once files are changed. One thought also
[newbie] Back to the forgotten beginning ~ lilo
Basically, I have two hdd's with the now slave having suffered my first attempts at Linux and of course, the last 9x going [ WinMe }. I can boot into WinMe without any hassles whatsoever but am unable to get lilo.conf right to boot into the old linux9.1 OS I have also installed on that hdd. Latest attempt: other=/dev/ide/host0/bus0/target1/lun0/part2 [ My boot partition on this hdd ] label=linux90 table=/dev/hdb image=/boot/vmlinuz root=/dev/hdb5 initrd=/boot/initrd.img append=noapic devfs=mount acpi=ht splash=silent vga=788 read-only I have tried other=/dev/hdb2 ( my boot partition on this drive ) and tried also other=/dev/hdb2 [ WinMe starts out as other=/dev/hdb1 ] I have made sure that vmlinuz and initrd.img exist on that boot partition still. I added the table=/dev/hdb but still no go. So someone want to slap me over the wrist for being dump here somewhere? -- Newbie Seeking USER_FUNCTIONALITY always! Regards SnapafunFrank Big or small, a challenge requires the same commitment to resolve. Registered Linux User # 324213 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] Back to the forgotten beginning ~ lilo
On Tue, 08 Feb 2005 23:42:49 +1300 SnapafunFrank [EMAIL PROTECTED] wrote: Basically, I have two hdd's with the now slave having suffered my first attempts at Linux and of course, the last 9x going [ WinMe }. I can boot into WinMe without any hassles whatsoever but am unable to get lilo.conf right to boot into the old linux9.1 OS I have also installed on that hdd. Latest attempt: other=/dev/ide/host0/bus0/target1/lun0/part2 [ My boot partition on this hdd ] label=linux90 table=/dev/hdb image=/boot/vmlinuz root=/dev/hdb5 initrd=/boot/initrd.img append=noapic devfs=mount acpi=ht splash=silent vga=788 read-only I have tried other=/dev/hdb2 ( my boot partition on this drive ) and tried also other=/dev/hdb2 [ WinMe starts out as other=/dev/hdb1 ] I have made sure that vmlinuz and initrd.img exist on that boot partition still. I added the table=/dev/hdb but still no go. So someone want to slap me over the wrist for being dump here somewhere? I might be wrong, but isn't other used only for windows? At least all the lilo.conf's I've looked at on my systems had other=/dev/hda1 for the first line to boot into windows. I hate to take a stab at what exactly you should have in your lilo.conf, but my first guess is that the section refering to your linux install would start with something like image=/boot/vmlinuz label=linux90 root=/dev/hdb ---seems like maybe a partition number goes behind? and-so-on and-so-on maybe attach your whole lilo.conf and someone might be able to help you better. Myself, I am sort of curious how you have windows working with it. -- Linux user #280097 http://counter.li.org http://www.mozilla.org/products/firefox/ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] Back to the forgotten beginning ~ lilo
On Tue, 08 Feb 2005 23:42:49 +1300 SnapafunFrank [EMAIL PROTECTED] wrote: Basically, I have two hdd's with the now slave having suffered my first attempts at Linux and of course, the last 9x going [ WinMe }. I can boot into WinMe without any hassles whatsoever but am unable to get lilo.conf right to boot into the old linux9.1 OS I have also installed on that hdd. Latest attempt: other=/dev/ide/host0/bus0/target1/lun0/part2 [ My boot partition on this hdd ] label=linux90 table=/dev/hdb image=/boot/vmlinuz root=/dev/hdb5 initrd=/boot/initrd.img append=noapic devfs=mount acpi=ht splash=silent vga=788 read-only I have tried other=/dev/hdb2 ( my boot partition on this drive ) and tried also other=/dev/hdb2 [ WinMe starts out as other=/dev/hdb1 ] I have made sure that vmlinuz and initrd.img exist on that boot partition still. I added the table=/dev/hdb but still no go. So someone want to slap me over the wrist for being dump here somewhere? noticed I botched that root=/dev/hdb line... didn't notice the root listing below your table entry (gotta slow down on reading!). I did manage to find my lilo.conf from my 9.1 install for an example; boot=/dev/hda map=/boot/map vga=normal default=Mandrake9.1 keytable=/boot/us.klt prompt nowarn timeout=100 message=/boot/message menu-scheme=wb:bw:wb:bw image=/boot/vmlinuz label=Mandrake9.1 root=/dev/hdb5 initrd=/boot/initrd.img append=quiet devfs=mount hdc=ide-scsi hdd=ide-scsi acpi=off vga=788 read-only image=/boot/vmlinuz-2.4.20-8 label=RedHat9 root=/dev/hda5 initrd=/boot/initrd-2.4.20-8.img append=hdc=ide-scsi hdd=ide-scsi acpi=off vga=788 read-only other=/dev/hda1 label=Windows2000 table=/dev/hda I would say drop the other= line and replace it with image=/boot/vmlinuz and remove the table= line as well for starters. -- Linux user #280097 http://counter.li.org http://www.mozilla.org/products/firefox/ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] Back to the forgotten beginning ~ lilo
SnapafunFrank wrote: Basically, I have two hdd's with the now slave having suffered my first attempts at Linux and of course, the last 9x going [ WinMe }. I can boot into WinMe without any hassles whatsoever but am unable to get lilo.conf right to boot into the old linux9.1 OS I have also installed on that hdd. Latest attempt: other=/dev/ide/host0/bus0/target1/lun0/part2 [ My boot partition on this hdd ] label=linux90 table=/dev/hdb image=/boot/vmlinuz root=/dev/hdb5 initrd=/boot/initrd.img append=noapic devfs=mount acpi=ht splash=silent vga=788 read-only I have tried other=/dev/hdb2 ( my boot partition on this drive ) and tried also other=/dev/hdb2 [ WinMe starts out as other=/dev/hdb1 ] I have made sure that vmlinuz and initrd.img exist on that boot partition still. I added the table=/dev/hdb but still no go. So someone want to slap me over the wrist for being dump here somewhere? Dumb question time - Is this lilo.conf you are working with on the second hard drive? Was the drive /dev/hdb when you installed Linux on it, or did you just have the drive with Linux on it in the machine when you installed it, and added back the Windows drive? Or do you have both Linux and Windows on the first drive, and you are trying to boot a second Linux install from the second drive? Mikkel -- Do not meddle in the affairs of dragons, for you are crunchy and taste good with Ketchup! Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
