Re: [expert] LILO v GrUB
Anne Wilson wrote: As for lilo and grub - I've never even tried grub, since lilo works fine for me. I use GrUB because of its simplicity. Configuring means simply editing a text file. Nothing to run afterwards. This makes chroot on rescue boots unnecessary, which makes explaining rescue over the phone or email much easier. -- A fool gives full vent to his anger, but a wise man keeps himself under control.Proverbs 29:11 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://members.ij.net/mrmazda/ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] LILO v GrUB
Felix Miata wrote: Anne Wilson wrote: As for lilo and grub - I've never even tried grub, since lilo works fine for me. I use GrUB because of its simplicity. Configuring means simply editing a text file. Nothing to run afterwards. This makes chroot on rescue boots unnecessary, which makes explaining rescue over the phone or email much easier. Another capability of grub that, afaik, does not come with lilo is command line completion from the grub prompt, allowing you to suss out partitions, kernels, etc. on a completely unknown system and boot from a grub floppy, e.g: grub root (hd [Tab] Possible disks are: hd0 hd1 hd2 hd3 grub root (hd3, [Tab] Possible partitions are: Partition num: 0, Filesystem type is reiserfs, partition type 0x83 Partition num: 4, Filesystem type is reiserfs, partition type 0x83 Partition num: 5, Filesystem type is reiserfs, partition type 0x83 Partition num: 6, Filesystem type is reiserfs, partition type 0x83 Partition num: 7, Filesystem type is reiserfs, partition type 0x83 Partition num: 8, Filesystem type is reiserfs, partition type 0x83 Partition num: 9, Filesystem type is reiserfs, partition type 0x83 Partition num: 10, Filesystem type is reiserfs, partition type 0x83 grub root (hd3,7) [Enter] Filesystem type is reiserfs, partition type 0x83 grub kernel (hd3,7)/boot/ [Tab] Possible files are: map initrd-2.4.21-0.18mm-mdk.img grub memtest-3.0.bin System.map-2.4 .21-0.17mdkcustom kernel.h-2.4.21-0.17mdk config-2.4.21-0.17mdk message-graphic System.ma p vmlinuz-2.4.21-0.17mdk message System.map-2.4.21-0.18mm-mdk kernel.h-2.4.21-0.18mm-mdk config initrd.img System.map-2.4.21-0.17mdk vmlinuz-2.4.21-0.18mm-mdk vmlinuz.old us.klt kernel.h-2.4.21-0.17mdkcustom vmlinuz-2.4.21-0.17mdkcustom config-2.4.21-0.18mm-mdk vmlin uz message-text initrd-2.4.21-0.17mdk.img initrd-2.4.21-0.17mdkcustom.img kernel.h boot.2 208 config-2.4.21-0.17mdkcustom grub kernel (hd3,7)/boot/vmlinuz [Enter] [Linux-bzImage, setup=0x1400, size=0x134a74] grub initrd (hd3,7)/boot/ [Tab] Possible files are: map initrd-2.4.21-0.18mm-mdk.img grub memtest-3.0.bin System.map-2.4 .21-0.17mdkcustom kernel.h-2.4.21-0.17mdk config-2.4.21-0.17mdk message-graphic System.ma p vmlinuz-2.4.21-0.17mdk message System.map-2.4.21-0.18mm-mdk kernel.h-2.4.21-0.18mm-mdk config initrd.img System.map-2.4.21-0.17mdk vmlinuz-2.4.21-0.18mm-mdk vmlinuz.old us.klt kernel.h-2.4.21-0.17mdkcustom vmlinuz-2.4.21-0.17mdkcustom config-2.4.21-0.18mm-mdk vmlin uz message-text initrd-2.4.21-0.17mdk.img initrd-2.4.21-0.17mdkcustom.img kernel.h boot.2 208 config-2.4.21-0.17mdkcustom grub initrd (hd3,7)/boot/initrd.img [Enter] [Linux-initrd @ 0x3bc000, 0x338cb bytes] grub You can add kernel commands and boot with boot. Not a common need but still neat. More commonly useful is the capability to edit from the menu screen, which I have used when a partition change or unusable kernel left the system unbootable from the old menu. Tom Berger wrote a page about grub's capabilities here: http://www.mandrakeuser.org/docs/install/iboot2.html Rolf Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] LILO v GrUB
On Fri, 2003-08-01 at 10:03, Felix Miata wrote: Anne Wilson wrote: As for lilo and grub - I've never even tried grub, since lilo works fine for me. I use GrUB because of its simplicity. Configuring means simply editing a text file. Nothing to run afterwards. This makes chroot on rescue boots unnecessary, which makes explaining rescue over the phone or email much easier. Now that is the first real reason I've heard for the grub advantage (the chroot part.) hm. James Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] lilo ?? install 9.1
I think the MBR can't be of any trouble, because it is completely overwritten by the bootloader (as far as I know) It's only a small space, where a link to the rest of the booting files resides. Is it really possible to manipulate the MBR so that it can cause troubles with other OS' ? I know some windows-versions rewrote the MBR on startup, but I never experienced this with win2k. (I used lilo as bootloader) according to my personal experiences, winXP sucks bigtime. The only 'good' windows versions I know are NT and 2000 (NT, btw, wasn't developed by MS but bought from some other company, and 2k was NT + some extra features) Again, I could be wrong, but that's why I write this and hope for replies :-) Steven On Thu, 2003-06-12 at 22:07, richard bown wrote: Hi all I've had a real bad experience using a hard drive that previously had winxp on it. I ran very low on HD space so I took the 60GB HD out of the winxp machine , installed as hdc and backed up what files I needed off that drive. next step was to delete the ntfs partitions and repartition with ext3, All apparently went well, and I transfered wanted files from hda to hdc. Checked everything was all right, and all the files moved across were in a partiton on hdc. the next step was to reinstall the system on to the 60GB drive(was hdc), and to use just 1 HD on this machine. So fresh install of 9.1 and this is were things went horribly wrong, on boot up no partitions had been written, tried to repair and failed, tried using the rescue facility ...that failed. So again another fresh install and this time made a boot floppy as well. again on reboot failure, so used the rescue facility to rerun the boot loader, Tried another bootup , same again reran the boot sector loader from rescue and this time the next reboot was successful.. After speaking to a few people I'm not the only person to have had problems with drives after winxp was installed on them. I suspect this may be a gates measure to deliberately make it awkward to change OS's once winxp has been installed, microsoft have done this before. Maybe ,and this is the point I'm trying to make, the developers need to look at the lilo or grub, to assume the MBR to contain hostile material and delete it before installing. If a newbie had decided to kick winxp off their machine and move to linux, I feel they would give up trying to install linux and go back to winblows. regards Richard Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] lilo ?? install 9.1
Its all very well Steven but., I 've installed many times all the way from Redhat 4.5 upwards, the first version of Mandrake was 7.0 then onward to MDK9.1. Not only on my machines,also on other peoples to get them started on Linux, and on numerous HD's with all sorts of variations of windows and OS2. The only times I've had lilo or grub fail has been due to a kernel I've compiled and made a few mistakes . The install of MDK9.1 is as close to idiot proof as you can get, and the developers should be proud of their work, but for 3 installs to fail to boot on a system which had only been running well on MDK9.1, with only one change the HD, makes me very suspicious. When I find others have have problems installing on a HD which previously had windowsXP on it, points the finger towards microsoft. I did consider the possibility of a virus on the MBR , but I had Macfee running on the windows machine before I used the HD on this machine, and it showed no trace of any infection. All I'm suggesting is the developers take a look at the bootloader on the Distro and see if it can be made more aggressive. Richard On Fri, 2003-06-13 at 16:49, Steven Broos wrote: I think the MBR can't be of any trouble, because it is completely overwritten by the bootloader (as far as I know) It's only a small space, where a link to the rest of the booting files resides. Is it really possible to manipulate the MBR so that it can cause troubles with other OS' ? I know some windows-versions rewrote the MBR on startup, but I never experienced this with win2k. (I used lilo as bootloader) according to my personal experiences, winXP sucks bigtime. The only 'good' windows versions I know are NT and 2000 (NT, btw, wasn't developed by MS but bought from some other company, and 2k was NT + some extra features) Again, I could be wrong, but that's why I write this and hope for replies :-) Steven On Thu, 2003-06-12 at 22:07, richard bown wrote: Hi all I've had a real bad experience using a hard drive that previously had winxp on it. I ran very low on HD space so I took the 60GB HD out of the winxp machine , installed as hdc and backed up what files I needed off that drive. next step was to delete the ntfs partitions and repartition with ext3, All apparently went well, and I transfered wanted files from hda to hdc. Checked everything was all right, and all the files moved across were in a partiton on hdc. the next step was to reinstall the system on to the 60GB drive(was hdc), and to use just 1 HD on this machine. So fresh install of 9.1 and this is were things went horribly wrong, on boot up no partitions had been written, tried to repair and failed, tried using the rescue facility ...that failed. So again another fresh install and this time made a boot floppy as well. again on reboot failure, so used the rescue facility to rerun the boot loader, Tried another bootup , same again reran the boot sector loader from rescue and this time the next reboot was successful.. After speaking to a few people I'm not the only person to have had problems with drives after winxp was installed on them. I suspect this may be a gates measure to deliberately make it awkward to change OS's once winxp has been installed, microsoft have done this before. Maybe ,and this is the point I'm trying to make, the developers need to look at the lilo or grub, to assume the MBR to contain hostile material and delete it before installing. If a newbie had decided to kick winxp off their machine and move to linux, I feel they would give up trying to install linux and go back to winblows. regards Richard __ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com -- richard bown [EMAIL PROTECTED] Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo conf lines
On Tuesday 18 Mar 2003 8:24 pm, diego wrote: I already sent a email out explaining this but it seems it got lost :-(( (This is not the first time I suspect I'm not sending/receiving all the email...) IMHO you have to tell lilo to load the mbr in another drive (lilo -b /dev/hdc or something similar). I think that when you swith on the computer, BIOS boots from your 100MHz ides, but as soon as kernel is loaded it reorders ides so hda is one of the 66MHz ides, not the 100MHz ones. This makes that when running lilo will default to load mbr in hda (if not specified another unit) which is *not* the boot drive. I copy the explanation sent before (please tell me if you got a email from me on 12 Mar 2003 just to check if I'm relly losing emails...): Sorry for the delay - my isp has been having a lot of problems and I got more than 2 days worth of mail at lunchtime today. Joerge is right - I did forget to run lilo. I appreciate your longer explanation, it does make a lot of sense. And no, I did not get your earlier email. Anne -- Registered Linux User No.293302 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo conf lines
On Tuesday 18 Mar 2003 4:39 pm, Klar Brian D Contr MSG/SICN wrote: Did you rerun lilo after editing /etc/lilo.conf ? Thanks, Brian. You're right. I was so relieved to have things working again that I forgot that. Anne -- Registered Linux User No.293302 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo conf lines
Thanks!!! You then confirmed me that this mails server sucks (I have the confirmation sending log of the outgoing mail). I'll make a new account on another server... El jue, 20-03-2003 a las 16:26, Anne Wilson escribió: On Tuesday 18 Mar 2003 8:24 pm, diego wrote: I already sent a email out explaining this but it seems it got lost :-(( (This is not the first time I suspect I'm not sending/receiving all the email...) IMHO you have to tell lilo to load the mbr in another drive (lilo -b /dev/hdc or something similar). I think that when you swith on the computer, BIOS boots from your 100MHz ides, but as soon as kernel is loaded it reorders ides so hda is one of the 66MHz ides, not the 100MHz ones. This makes that when running lilo will default to load mbr in hda (if not specified another unit) which is *not* the boot drive. I copy the explanation sent before (please tell me if you got a email from me on 12 Mar 2003 just to check if I'm relly losing emails...): Sorry for the delay - my isp has been having a lot of problems and I got more than 2 days worth of mail at lunchtime today. Joerge is right - I did forget to run lilo. I appreciate your longer explanation, it does make a lot of sense. And no, I did not get your earlier email. Anne -- Registered Linux User No.293302 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com -- Diego Dominguez __/\__ | | Andalucia /\ Spain \/ |__ __| \/ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo conf lines
On Thu, 2003-03-20 at 09:25, diego wrote: Thanks!!! You then confirmed me that this mails server sucks (I have the confirmation sending log of the outgoing mail). I'll make a new account on another server... Diego, Just don't shoot it!... really messes with your guarantee. (refrence the guy who got so p/o'd at his windows laptop he shot it four times) James El jue, 20-03-2003 a las 16:26, Anne Wilson escribió: On Tuesday 18 Mar 2003 8:24 pm, diego wrote: I already sent a email out explaining this but it seems it got lost :-(( (This is not the first time I suspect I'm not sending/receiving all the email...) IMHO you have to tell lilo to load the mbr in another drive (lilo -b /dev/hdc or something similar). I think that when you swith on the computer, BIOS boots from your 100MHz ides, but as soon as kernel is loaded it reorders ides so hda is one of the 66MHz ides, not the 100MHz ones. This makes that when running lilo will default to load mbr in hda (if not specified another unit) which is *not* the boot drive. I copy the explanation sent before (please tell me if you got a email from me on 12 Mar 2003 just to check if I'm relly losing emails...): Sorry for the delay - my isp has been having a lot of problems and I got more than 2 days worth of mail at lunchtime today. Joerge is right - I did forget to run lilo. I appreciate your longer explanation, it does make a lot of sense. And no, I did not get your earlier email. Anne -- Registered Linux User No.293302 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo conf lines
On Wednesday 12 Mar 2003 10:49 pm, Joerg Mertin wrote: Anne Wilson wrote: On Wednesday 12 Mar 2003 6:46 pm, Joerg Mertin wrote: Hi Anne, so - here we go :) Well blow me down :-) Windows_2 boots! Glad to hear it works :) Joerg - strange things are happening. When you told me to add the new windows stanza, I saved the old file as lilo.conf.March 'just in case'. I then added the stanza to lilo.conf. As I said, it worked. Examining lilo.conf afterwards, I found that the odd mapping lines had disappeared, and I then seemed to have WindowsOriginal stanza and Windows2 stanza identically set up. I then deleted WindowsOriginal, and renamed Windows2 to Windows98. To my surprise, when I get the lilo menu I still see WindowsOriginal and Windows2. I have no idea where it's reading these from. The current lilo.conf is attached. Can you point me at an explanation? Anne -- Registered Linux User No.293302 boot=/dev/hde map=/boot/map vga=normal default=win4lin keytable=/boot/uk.klt prompt nowarn timeout=200 message=/boot/message menu-scheme=wb:bw:wb:bw disk=/dev/hde bios=0x80 image=/boot/vmlinuz-2.4.19-16mdk label=Mandrake_9.0-2. root=/dev/hdf1 initrd=/boot/initrd-2.4.19-16mdk.img append=nobiospnp nopentium mem=512M devfs=mount hdc=ide-scsi read-only image=/boot/vmlinuz label=failsafe root=/dev/hdf1 initrd=/boot/initrd.img append=failsafe nopentium mem=512M devfs=nomount hdc=ide-scsi read-only other=/dev/hde1 label=Windows98 table=/dev/hde other=/dev/fd0 label=floppy unsafe image=/boot/win4lin label=win4lin root=/dev/hdf1 initrd=/boot/initrd.img append=nobiospnp nopentium mem=512M devfs=mount hdc=ide-scsi read-only Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
RE: [expert] Lilo conf lines
Did you rerun lilo after editing /etc/lilo.conf ? Brian D. Klar - CVE Multimax Network Engineer WPAFB -Original Message- From: Anne Wilson [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2003 11:42 AM To: [EMAIL PROTECTED] Subject: Re: [expert] Lilo conf lines On Wednesday 12 Mar 2003 10:49 pm, Joerg Mertin wrote: Anne Wilson wrote: On Wednesday 12 Mar 2003 6:46 pm, Joerg Mertin wrote: Hi Anne, so - here we go :) Well blow me down :-) Windows_2 boots! Glad to hear it works :) Joerg - strange things are happening. When you told me to add the new windows stanza, I saved the old file as lilo.conf.March 'just in case'. I then added the stanza to lilo.conf. As I said, it worked. Examining lilo.conf afterwards, I found that the odd mapping lines had disappeared, and I then seemed to have WindowsOriginal stanza and Windows2 stanza identically set up. I then deleted WindowsOriginal, and renamed Windows2 to Windows98. To my surprise, when I get the lilo menu I still see WindowsOriginal and Windows2. I have no idea where it's reading these from. The current lilo.conf is attached. Can you point me at an explanation? Anne -- Registered Linux User No.293302 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo conf lines
Hi Anne, Looks like youy forgot to rerun lilo after the changes. Cheers Joerg Anne Wilson wrote: [...] Joerg - strange things are happening. When you told me to add the new windows stanza, I saved the old file as lilo.conf.March 'just in case'. I then added the stanza to lilo.conf. As I said, it worked. Examining lilo.conf afterwards, I found that the odd mapping lines had disappeared, and I then seemed to have WindowsOriginal stanza and Windows2 stanza identically set up. I then deleted WindowsOriginal, and renamed Windows2 to Windows98. To my surprise, when I get the lilo menu I still see WindowsOriginal and Windows2. I have no idea where it's reading these from. The current lilo.conf is attached. Can you point me at an explanation? Anne boot=/dev/hde map=/boot/map vga=normal default=win4lin keytable=/boot/uk.klt prompt nowarn timeout=200 message=/boot/message menu-scheme=wb:bw:wb:bw disk=/dev/hde bios=0x80 image=/boot/vmlinuz-2.4.19-16mdk label=Mandrake_9.0-2. root=/dev/hdf1 initrd=/boot/initrd-2.4.19-16mdk.img append=nobiospnp nopentium mem=512M devfs=mount hdc=ide-scsi read-only image=/boot/vmlinuz label=failsafe root=/dev/hdf1 initrd=/boot/initrd.img append=failsafe nopentium mem=512M devfs=nomount hdc=ide-scsi read-only other=/dev/hde1 label=Windows98 table=/dev/hde other=/dev/fd0 label=floppy unsafe image=/boot/win4lin label=win4lin root=/dev/hdf1 initrd=/boot/initrd.img append=nobiospnp nopentium mem=512M devfs=mount hdc=ide-scsi read-only Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com -- | Joerg Mertin : [EMAIL PROTECTED](Home)| | in Neuchâtel/Schweiz : [EMAIL PROTECTED] (Work)| | Stardust's LiNUX System : | | PGP 2.6.3in Key on Demand : Voice Fax: +41(0)32 / 725 52 54 | Home-Page: http://www.solsys.org Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo conf lines
I already sent a email out explaining this but it seems it got lost :-(( (This is not the first time I suspect I'm not sending/receiving all the email...) IMHO you have to tell lilo to load the mbr in another drive (lilo -b /dev/hdc or something similar). I think that when you swith on the computer, BIOS boots from your 100MHz ides, but as soon as kernel is loaded it reorders ides so hda is one of the 66MHz ides, not the 100MHz ones. This makes that when running lilo will default to load mbr in hda (if not specified another unit) which is *not* the boot drive. I copy the explanation sent before (please tell me if you got a email from me on 12 Mar 2003 just to check if I'm relly losing emails...): Let's have first some background before breaking it all ;-)) I have a board with 2 IDE ports (HighPoint's raid) and 2 normal IDE ports. That's why I had to add those 2 disk-stanzas I will describe the issues in my board (that might be quite similar to your case): At startup, BIOS makes raid to be ide 0 and 1, and normal ones 2 and 3. It then tryies to boot from first drive in the first ide available. Let's say it is a master drive in ide 0. We should call it hda. So far so good. The problem is that Linux does not use BIOS to do it's I/O, so as soon as it has been loaded into memory it won't use BIOS conventions. In my case it thinks normal ide port's are 0 and 1, and raid ones are 2 and 3, just the opposite as BIOS stated!!! That's all. All you have to do to make thinks easier is to think is how to force a remapping of ide's so as to be the same as BIOS, and you'll get rid of many mistakes. For example, if Linux mappings of hard disks does not match with BIOS ones, and you run lilo to update mbr (OS boot menu) on hda, that drive might not be first drive for BIOS, so it will boot another mbr and you'll be wondering why you are booting with the same menu as always, but nothing to do with the one you have spacified!! All this can be solved by typing into lilo.conf the spells of remaping drives (or by specifing boot=/dev/hdyour_BIOS_boot_drive, but taking into account that drive is the letter of BIOS remapped to what Linux wnted/was told to). Remapping can be done with disk's or map-drive spells (use disk's, cause map-drive is mainly for DOS and the first one can be used with all OS and it's clearer). Anyway, what you specify is: real_drive -- how_I_want_it_to_be_seen_by_the_OS Now to your point: Try to coment out those 2 stanzas and run lilo to see if Windows will boot. Sincerely, I can't see a reason for them to be there provided there is not a previous remapping of drives in lilo.conf. Anyway it probably won't change much if all partitions in hdf are invisible to Windows. El mar, 18-03-2003 a las 17:41, Anne Wilson escribió: On Wednesday 12 Mar 2003 10:49 pm, Joerg Mertin wrote: Anne Wilson wrote: On Wednesday 12 Mar 2003 6:46 pm, Joerg Mertin wrote: Hi Anne, so - here we go :) Well blow me down :-) Windows_2 boots! Glad to hear it works :) Joerg - strange things are happening. When you told me to add the new windows stanza, I saved the old file as lilo.conf.March 'just in case'. I then added the stanza to lilo.conf. As I said, it worked. Examining lilo.conf afterwards, I found that the odd mapping lines had disappeared, and I then seemed to have WindowsOriginal stanza and Windows2 stanza identically set up. I then deleted WindowsOriginal, and renamed Windows2 to Windows98. To my surprise, when I get the lilo menu I still see WindowsOriginal and Windows2. I have no idea where it's reading these from. The current lilo.conf is attached. Can you point me at an explanation? Anne -- Registered Linux User No.293302 boot=/dev/hde map=/boot/map vga=normal default=win4lin keytable=/boot/uk.klt prompt nowarn timeout=200 message=/boot/message menu-scheme=wb:bw:wb:bw disk=/dev/hde bios=0x80 image=/boot/vmlinuz-2.4.19-16mdk label=Mandrake_9.0-2. root=/dev/hdf1 initrd=/boot/initrd-2.4.19-16mdk.img append=nobiospnp nopentium mem=512M devfs=mount hdc=ide-scsi read-only image=/boot/vmlinuz label=failsafe root=/dev/hdf1 initrd=/boot/initrd.img append=failsafe nopentium mem=512M devfs=nomount hdc=ide-scsi read-only other=/dev/hde1 label=Windows98 table=/dev/hde other=/dev/fd0 label=floppy unsafe image=/boot/win4lin label=win4lin root=/dev/hdf1 initrd=/boot/initrd.img append=nobiospnp nopentium mem=512M devfs=mount hdc=ide-scsi read-only Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com -- Diego Dominguez __/\__ | | Andalucia /\ Spain \/ |__ __| \/ ___ Yahoo!
Re: [expert] Lilo conf lines
On Wednesday 12 Mar 2003 10:49 pm, Joerg Mertin wrote: Anne Wilson wrote: However - if you don't intend using that version anymore - just ignore what I said ;) guess it'll be easyer ... Thanks for all your help, Joerg. One last question, if I may? I hope to soon have 9.1, and would like to avoid the sort of problems I've had this time. I shall reformat the partition that had 8.2 on, and make another partition available for /home. I know that I'l have to make sure fstab isn't trying to mount them, and clean up lilo.conf first. What other precautions should I take? Anne -- Registered Linux User No.293302 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo conf lines
Hi Anne, actually - when I do an operating System backup - there are only 2 things I do backup. From my Home partition /home/smurphy I perform as user root a: tar zcvf backup_etc.tar.gz /etc tar zcvf bac,up_mail.tar.gz /var/spool/mail This backups the entire /etc directory. All configuration files are held in there - should be. The other things I do always do. I always create a /usr/local and an /opt partition. These are very important. If I install/compile software on my own - it goes under /usr/local/. If I install a big package using so called install.sh scripts - they always go into /opt . OK - whjat is very important here is to make sure you remember the partition of the /usr/local /opt and /home partitions. B.e. on my System these are: Filesystem 1K-blocks Used Available Use% Mounted on /dev/hda1 577096164548383232 31% / /dev/hda3 3960976 1150992 2809984 30% /home /dev/hda8 8159388 5046008 2698908 66% /opt /dev/hda1014594836 7120312 6733128 52% /scratch /dev/hda7 489960 62377402284 14% /tmp /dev/hda2 3960976 2148128 1611636 58% /usr /dev/hda9 4055776195284 3654464 6% /usr/local /dev/hda6 3083440172068 2754740 6% /var Here you see - /home is hda3 /opt is hda8 The etc-Directory - e.g. configuration files - are backuped in the /home directory. Another thing you see here is the /scratch Directory. I usually put all stuff - anything - source-files, mirrors etc. into the /scratch directory. All Mails of the /var/spool/mail directory are also backed up. The Users - are all in the etc-backup - so that shouldn't be a problem :) What you need to realize in the process of reinstalling a new operating System - is that you only need to reformat the directories where you do not have private data in. So - what is left ? During install - all you need to do is: 1. Do not repartition your partitions - where data you want to keep relies in ! In my case these are always: /opt /home /scratch /usr/local 2. During Install - * make sure the installer assigns the partitions to the existing mount points. Best is to do a hardcopy of it first. * reformat the partitions the Operating System is in. In my case: / /usr /var /tmp I always do a tmp and a var partition. This to prevent filling of /log/* or /tmp/* files to fill the / partition and make the system unusable. The content of the /home, /opt and /scratch (in my case) will be preserved. So - I'll find all that data in there. Of course - if you are not familiar with all that stuff - make backups on another media before doing so. I do it the Linus Torvalds way: Backups are for cowards. Post it and the Internet will backup it up for you :))) Well, Linus once sent something like this to a newsgroup ;) Was a great laugh I had - but wheh I became more confident with the Systems and knewing what I was doing - i adopted the same way of thinking :) Weird - but I really never lost data since then as I always had to make sure there wouldn't be data losses. What you need to remember - the etc-backup contains all configuration stuff you had. I would never opt to copy the files over to the new system - using the backup file - if the major-number of the application has changed. If it has not changed - most probably it wouldn't make a big difference. If it has changed - open both fils in Emacs - and adapt. The /home and /opt directories will held the data/applications you had. Eventually you'll have to create ne entries in the KDE-menus for the apps if they where global (e.g. root had installed these in the KDE-System menus). If it was installed as user - the links are still in your home. If the KDE-System gets update - always move your .kde and Desktop Directories to a backup location and restore these. e.g.: cd ~ mkdir Backup mv .kde* Desktop Backup ctrl-Alt-Back-Space Log in again - and the system will recreate you new: .kde and Desktop directories and default configuratons. Try to reconfigure your system using the KDE-Control-Center. Applications - that had a configuration files or data file as kmail or organizer, kaddressbook - copy the ~Backup/.kde/share/apps/application-dir ~/.kde/share/apps/ ~Backup/.kde/share/config/application-cfgfile ~/.kde/share/config/ Note that the second line - you should test. Eventually the major release numbers have changed - so you should best reconfigure manually. For the rest - if a problem occurs - send a Mail to the list ;) There always somewhere here to help ... Cheers Joerg Anne Wilson wrote: On Wednesday 12 Mar 2003 10:49 pm, Joerg Mertin wrote: Anne Wilson wrote: However - if you don't intend using that version anymore - just ignore what I said ;) guess it'll be easyer ... Thanks for all your help, Joerg. One last question, if I may? I hope to soon have 9.1, and would
Re: [expert] Lilo conf lines
On Thursday 13 Mar 2003 9:46 pm, Joerg Mertin wrote: Hi Anne, actually - when I do an operating System backup - there are only 2 things I do backup. Thank you Joerg. Printed out and stored for reference g Anne -- Registered Linux User No.293302 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo with multiple hard drives...
Is lilo installed on hdb? Boot from floppy with hdb removed. linux root=/dev/hdc? ? being partition number. run lilo and reboot to see if it boots from hard drive. Gary. On Monday 10 March 2003 09:34 pm, Mark Watts wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ok, answers to questions: No, I wasnt using cable select. No, I wasnt changing any jumpers. This has nothing to do with fstab - that doesnt get processed at the lilo point. With all 3 drives in, I get a lilo prompt. With hdb removed I get LI LI LI LI... hdb is NOT mentioned in lilo.conf, so why does removing that drive affect lilo? Cheers. Mark. On Friday 07 March 2003 09:33 pm, Gary Hodder wrote: Hi Mark, with the 3 drives in and it boots normally, edit the fstab file and change the hdc? to hdb? ? being the partition number. Change lilo to be hdb instead of hdc. Reboot with a floppy, at lilo promp: linux root=/dev/hdb? ? being the partition number the os is on. Run lilo. Reboot to boot from kernel on harddrive. Gary. and next time, don't use cable select as the way to choice master and slave HDs, use the jumpers on the drive itself. On Fri, 2003-03-07 at 22:19, Mark Watts wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I have a system with 3 harddrives in it (hda = Windows, hdb = spare (part XFS, part FAT32) and hdc = Linux (resierfs). I installed Windows first, followed by 9.0 on hdc, and chose to install lilo to hda's boot sector. This has been working just fine since I installed. I've come to a point where I'm moving hdb out of the system... Whenever I remove it, I get the ubiquitos LI LI LI LI LI across the screen, indicating that lilo is toast. Putting the drive back makes everything work as before. 2 questions: 1) Should lilo really be doing this, bearing in mind that hdb isnt mentioned in lilo.conf (It has an old 8.2 install I havent removed yet on it, but I'd have to make a boot disk to boot from it). 2) If I re-reun lilo (from a rescue cd and chrooting stuff) without changing lilo.conf, will that fix the LI LI LI issue? Cheers, Mark. - -- Mark Watts Systems Engineer QinetiQ TIM St Andrews Road, Malvern GPG Public Key available on request. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+aIA5Bn4EFUVUIO0RAhuvAKCzIzCZDqFlr6+RWzdSEmrpglnB8QCgxetA gfpHOl0qRleNXs2VLEiSQcY= =wfFV -END PGP SIGNATURE- Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com - -- Mark Watts Systems Engineer QinetiQ TIM St Andrews Road, Malvern GPG Public Key available on request. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+bGpLBn4EFUVUIO0RAkDeAJ0WLGqDCacQRyYIE0O2qNY5kCZ6BgCeNPsc S+knuDCAmZocwoLKJ8l15tU= =11Y0 -END PGP SIGNATURE- Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo conf lines
Damn folks, there's too much M$-itis going on. Why does almost anyone in here believes that Formatting and reinstalling will solve you problems ? They eventually will - but if you didn't understand the source of the issue - it won't work. Also - understanding what is happeneing will spare you hours next time :) Anne - could you give a exact explanation of your drives ? By that, I mean, how many disks are in there - best would be a dmesg-grep. Short after boot, make a: dmesg | egrep hd|dev Or if you have huge uptimes - go to the /var/log directory and issue a: egrep hd|dev dmesg and post it here. Another thing you need to specify us - are the boot drives. We then can recreate you a lilo.conf file you could try. Also - please repost you actual lilo.conf. Note - lilo will not break anything on your system if you reinstall it. If you want to backup the last master-boot record, just issue a: dd if=/dev/boot disk of=bootsector.raw bs=512 count=1 If you need to recover your old bootsector - use: dd if=bootsector.raw of=/dev/boot disk while the bootisk is most probably hda. Can be something else too. Note - this also works for saving the MBR. And - as long as you folks do not touch the partition tables - nothing of your data is lost. Regarding ATA100. I don't know of a drive yet that really needs the bandwidth ATA100 provides. Most drives have still a very good throughput wth ATA33, while ATA66 is not maxed with actual drives. S - the importand stuff IMHO with harddisks is to have the DMA mode active, and if you don't want your mouse to jump over the screen while having big data transfers on your disk - activate the unmask IRQ options using hdparm. on my server, that's what I use; /sbin/hdparm -d 1 -W 1 -k 1 -c 1 -m 16 /dev/hda you might want to check the hdparm manpages to know the exact meaning of the flags. which results in: Capabilities: LBA, IORDY(cannot be disabled) Buffer size: 1945.0kB ECC bytes: 4Queue depth: 1 Standby timer values: spec'd by standard, no device specific minimum r/w multiple sector transfer: Max = 16 Current = 16 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 *udma4 udma5 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=120ns IORDY flow control=120ns and Timed buffered reads do come out with: Timing buffered disk reads: 64 MB in 2.11 seconds = 30.31 MB/sec which even ATA33 would handle fine. Regarding moving disks around. All you need to keep in mind - is that you then need to adapt your /etc/fstab with the corrected values. For this - I usually boot off of Knopix (Live FS Distribution), mount the root-partition of existing Mandrake dist. and modify the device names accordingly. means - in your case - you had to modify all /dev/hdbX instances to /dev/hdc instances and you would have been fine. Of course - you need to make sure to check your CMOS settings. Many people I know do turn of the secondary Port to save Interrupts. So - if you do not see the drive 2 at all while booting up - that's most probably what happened. OK - I hope I have not been too long here - but this thread could be solved soo fast ;o) Cheers Joerg On Tue, 11 Mar 2003, Dave Laird wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Good afternoon, Anne... I've been avidly following this discussion regarding ATA100 drives because I saw something quite akin to that just last week. I formatted and installed two ATA100 drives, both on the primary cable as Master/Slave, and did a bunch of other install configuration thingees. About an hour later, I decided in a rash moment of heat, to put one drive as primary/master and one drive as secondary/master. The second drive disappeared. Since I really didn't have the time to figure it out, I put them back where they were formatted and all was well. Several attempts resulted in the same findings and finally I put the case on it and all was well. That day there simply wasn't enough time. sigh On Tuesday 11 March 2003 01:57 pm, Anne Wilson wrote: I hate not knowing what has caused this. Me too. 8-( Dave - -- Dave Laird ([EMAIL PROTECTED]) The Used Kharma Lot / The Phoenix Project Web Page: http://www.kharma.net updated 03/05/2003 Usenet News server: news.kharma.net Musicians Calendar and Database access: http://www.kharma.net/calendar.html An automatic random thought For the Minute: Utility is when you have one telephone, luxury is when you have two, opulence is when you have three -- and paradise is when you have none. -- Doug Larson -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+bl4/aE1ENZP1A28RAgkqAJ4+xAk145RGbHz9qY7lUcLZeFEfRACfUOym urv/RVotjIeiDTGlzvqEh9k= =CBro -END PGP SIGNATURE- --
Re: [expert] Lilo conf lines
On Wednesday 12 Mar 2003 8:02 am, Joerg Mertin wrote: Anne - could you give a exact explanation of your drives ? By that, I mean, how many disks are in there - best would be a dmesg-grep. Short after boot, make a: dmesg | egrep hd|dev Or if you have huge uptimes - go to the /var/log directory and issue a: egrep hd|dev dmesg Attached, also comment on drives. and post it here. Another thing you need to specify us - are the boot drives. We then can recreate you a lilo.conf file you could try. Also - please repost you actual lilo.conf. MBR is on hde fstab and lilo.conf attached. Note - lilo will not break anything on your system if you reinstall it. If you want to backup the last master-boot record, just issue a: dd if=/dev/boot disk of=bootsector.raw bs=512 count=1 Will do that before attempting anything drastic g If you need to recover your old bootsector - use: dd if=bootsector.raw of=/dev/boot disk /sbin/hdparm -d 1 -W 1 -k 1 -c 1 -m 16 /dev/hda you might want to check the hdparm manpages to know the exact meaning of the flags. OK - I have the info, I'll study it. means - in your case - you had to modify all /dev/hdbX instances to /dev/hdc instances and you would have been fine. Of course - you need to make sure to check your CMOS settings. Many people I know do turn of the secondary Port to save Interrupts. So - if you do not see the drive 2 at all while booting up - that's most probably what happened. Not sure I understand here - I did not move any drives at all, just formatted some partitions and made a new install. OK - I hope I have not been too long here - but this thread could be solved soo fast ;o) Thanks, Joerg. I hope the attached files will help you come to some conclusion. Anne -- Registered Linux User No.293302 egrep hd|dev dmesg egrep: dmesg: No such file or directory [EMAIL PROTECTED] anne]# cd /var/log [EMAIL PROTECTED] log]# egrep hd|dev dmesg Kernel command line: BOOT_IMAGE=win4lin ro root=2141 nobiospnp mem=nopentium devfs=mount hdc=ide-scsi ide_setup: hdc=ide-scsi isapnp: No Plug Play device found devfs: v1.12a (20020514) Richard Gooch ([EMAIL PROTECTED]) devfs: boot_options: 0x1 VP_IDE: IDE controller on PCI bus 00 dev 21 ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:pio PDC20265: IDE controller on PCI bus 00 dev 88 PCI: Found IRQ 10 for device 00:11.0 ide2: BM-DMA at 0x7800-0x7807, BIOS settings: hde:DMA, hdf:DMA ide3: BM-DMA at 0x7808-0x780f, BIOS settings: hdg:DMA, hdh:pio hda: HITACHI DVD-ROM GD-5000, ATAPI CD/DVD-ROM drive hdc: CR-48X9TE, ATAPI CD/DVD-ROM drive hde: FUJITSU MPG3204AT E, ATA DISK drive hdf: Maxtor 91731U4, ATA DISK drive hdg: FUJITSU MPA3043ATU, ATA DISK drive hde: 40031712 sectors (20496 MB) w/512KiB Cache, CHS=39714/16/63, UDMA(100) hdf: 34004880 sectors (17410 MB) w/512KiB Cache, CHS=33735/16/63, UDMA(66) hdg: 8544940 sectors (4375 MB), CHS=9042/15/63, UDMA(33) /dev/ide/host2/bus0/target0/lun0:6 [PTBL] [2491/255/63] p1 p2 p5 p6 p7 p8 /dev/ide/host2/bus0/target1/lun0:6 [PTBL] [2116/255/63] p1 p2 p5 p6 p7 /dev/ide/host2/bus1/target0/lun0:6 [PTBL] [531/255/63] p2 p5 Mounted devfs on /dev PCI: Found IRQ 9 for device 00:0a.0 Mounted devfs on /dev usb.c: registered new driver usbdevfs PCI: Found IRQ 9 for device 00:04.2 PCI: Found IRQ 9 for device 00:04.3 usbdevfs: remount parameter error hub.c: USB new device connect on bus2/1, assigned device number 2 hub.c: USB new device connect on bus2/2, assigned device number 3 hub.c: USB new device connect on bus2/1/1, assigned device number 4 usb.c: USB device 4 (vend/prod 0x718/0x2) is not claimed by any active driver. hub.c: USB new device connect on bus2/1/2, assigned device number 5 printer.c: usblp0: USB Bidirectional printer dev 5 if 0 alt 0 proto 2 vid 0x03F0 pid 0x3304 scsi1 : SCSI emulation for USB Mass Storage devices /dev/scsi/host1/bus0/target0/lun0: I/O error: dev 08:00, sector 0 I/O error: dev 08:00, sector 0 USB Mass Storage device found at 4 scsi2 : SCSI host adapter emulation for IDE ATAPI devices hda: ATAPI 40X DVD-ROM drive, 512kB Cache, DMA /dev/scsi/host1/bus0/target0/lun0: I/O error: dev 08:00, sector 0 I/O error: dev 08:00, sector 0 /dev/scsi/host1/bus0/target0/lun0: I/O error: dev 08:00, sector 0 I/O error: dev 08:00, sector 0 VFS: Can't find a valid FAT filesystem on dev 21:05. PCI: Found IRQ 10 for device 00:0c.2 hda: DMA disabled hdc: DMA disabled PCI: Found IRQ 9 for device 00:09.0 [EMAIL PROTECTED] log]#Drive geometry - hde1 windows98 5 fat32 6 ext3, Mandrake 8.2 - no longer used 7 swap 8 fat32, data hdf1 ext3, / Mandrake 9.0 5 swap 6 fat32, Data 7 ext3, /home MCC lists them in order of: hde 1, 5, 8, 6, 7 hdf 1, 5, 7, 6 hdg - front half empty, back half, 8.2's home. This drive to be taken out next time it's convenient. No longer used./dev/hdf1 / ext3 defaults 1 1 none /dev/pts devpts mode=0620 0 0 /dev/hdf7
Re: [expert] Lilo conf lines
Hi Anne, so - here we go :) Hardware-Detection in progress: So - from what I see - you have a very interesting setup. Never saw such kind of setup to be honest. First drive on IDE-Controller 1 - a DVD-Rom Drive :) Cool. Most probably due to the fact you use the ATA100 Controller for your Harddrives, and the ATA66 controller for the DVD-Rom/CDrom. So - let's identify the appartenance: IDE-Controller 0 - ATA66 hda: HITACHI DVD-ROM GD-5000, ATAPI CD/DVD-ROM drive - Master bus0 hdc: CR-48X9TE, ATAPI CD/DVD-ROM drive - Master bus 1 IDE-Controller 1 - ATA100 hde: FUJITSU MPG3204AT E, ATA DISK drive - Master Bus 0 hdf: Maxtor 91731U4, ATA DISK drive - Slave Bus 0 hdg: FUJITSU MPA3043ATU, ATA DISK drive - Master Bus 1 So - acfording to the dmesg output - you also disable DMA for boith CD/DVD Rom Drives. I usually ativate these :) Works here :) MBR is on hde - Good. First Harddisk of IDE-Controller 1 OK - now go to the Lilo stuff. boot=/dev/hde map=/boot/map vga=normal keytable=/boot/uk.klt prompt nowarn timeout=100 message=/boot/message menu-scheme=wb:bw:wb:bw # Here - we tell lilo what the BIOS tells the System upon boot. disk=/dev/hde bios=0x80 image=/boot/vmlinuz-2.4.19-16mdk label=Mandrake_9.0-2. root=/dev/hdf1 initrd=/boot/initrd-2.4.19-16mdk.img append=nobiospnp mem=512M nopentium devfs=mount hdc=ide-scsi read-only image=/boot/vmlinuz label=failsafe root=/dev/hdf1 initrd=/boot/initrd.img append=failsafe mem=512M nopentium devfs=nomount hdc=ide-scsi read-only other=/dev/hde1 label=windowsOriginal table=/dev/hde map-drive=0x80 to=0x81 map-drive=0x81 to=0x80 # My proposal is to try out if the System takes everything as is - # without the remapping - as the hde is already declared as 0x80 by the # BIOS. Right now - I boot windows from hdc - well - last time I did is # 4 weeks back. other=/dev/hde1 label=windows_2 table=/dev/hde other=/dev/fd0 label=floppy unsafe I'm actually missing hde6 in your fstab. Dunno what kernel version was there - but I bet that you could boot it still by adding: image=/mnt/hde6/boot/vmlinuz-2.4.your kernel version label=Mandrake_8.2 root=/dev/hde6 initrd=/mnt/hde6/boot/initrd-2.4.19-16mdk.img append=nobiospnp mem=512M nopentium devfs=mount hdc=ide-scsi read-only You need to take into account that you have to mount your /dev/hde6 partition under /mnt/hde6 before you execute lilo. Be very carefull to not execute lilo under Mandrake 8.2 though - as it would overwrite your Master Boot record again - and make it not possible for you to boot into 9.0 :) Back in time - I used another trick for that kind of setups. Very easy - but very efficient. I installed on the old operating Linux partition the lilo into the partition table of my root-partition while running under OS that version - means in your case under Mandrake-8.2: boot=/dev/hde6 map=/boot/map vga=normal keytable=/boot/uk.klt prompt nowarn timeout=0 message=/boot/message menu-scheme=wb:bw:wb:bw # Here - we tell lilo what the BIOS tells the System upon boot. disk=/dev/hde bios=0x80 image=/boot/vmlinuz-your kernel version label=Mandrake_8.2 root=/dev/hdf1 initrd=/boot/initrd-your kernel version append=nobiospnp mem=512M nopentium devfs=mount hdc=ide-scsi read-only Execute Lilo - then boot into the new version, and append only a little: other=/dev/hde6 label=Mandrake_8.2 table=/dev/hde It has one advantage - you won't write with one LILO into the partition of the other LILO - and you can update your kernels under both operating systems without having to fear you go out of sync anywhere, or overwriting the Lilo-information of the other OS-Version. The Drawback is that you'll have to navigate through 2 LILO's. That's also the reason I did set the timeout message to 0. Holding the Ctrl-Key down while going into the second-Lilo instance will give you the ability to add something though ;) Please note that you might need to tweak the settings a little bit. Back in time - it was easyer to cheat on lilo. They have built many logical-Checkings into it - to prevent from user-mistakes, if they don't know what to do. I still prefere doing the lilo.conf using vi :) Hardcore way :) Note2: If the LIlO tells you he made a mistake - don't reboot as long as you have not fixed it ;) usually lilo should write only if syntax and logic checkings have occured - but I happened to have screwed my lilo install several times. Always keep a Bootdisk by hand that works before fiddling with lilo ... Cheers Joerg -- | Joerg Mertin : [EMAIL PROTECTED](Home)| | in Neuchâtel/Schweiz : [EMAIL PROTECTED] (Work)| | Stardust's LiNUX System : | | PGP 2.6.3in Key on Demand : Voice Fax: +41(0)32 / 725 52 54 |
Re: [expert] Lilo conf lines
Let's have first some background before breaking it all ;-)) I have a board with 2 IDE ports (HighPoint's raid) and 2 normal IDE ports. That's why I had to add those 2 disk-stanzas I will describe the issues in my board (that might be quite similar to your case): At startup, BIOS makes raid to be ide 0 and 1, and normal ones 2 and 3. It then tryies to boot from first drive in the first ide available. Let's say it is a master drive in ide 0. We should call it hda. So far so good. The problem is that Linux does not use BIOS to do it's I/O, so as soon as it has been loaded into memory it won't use BIOS conventions. In my case it thinks normal ide port's are 0 and 1, and raid ones are 2 and 3, just the opposite as BIOS stated!!! That's all. All you have to do to make thinks easier is to think is how to force a remapping of ide's so as to be the same as BIOS, and you'll get rid of many mistakes. For example, if Linux mappings of hard disks does not match with BIOS ones, and you run lilo to update mbr (OS boot menu) on hda, that drive might not be first drive for BIOS, so it will boot another mbr and you'll be wondering why you are booting with the same menu as always, but nothing to do with the one you have spacified!! All this can be solved by typing into lilo.conf the spells of remaping drives (or by specifing boot=/dev/hdyour_BIOS_boot_drive, but taking into account that drive is the letter of BIOS remapped to what Linux wnted/was told to). Remapping can be done with disk's or map-drive spells (use disk's, cause map-drive is mainly for DOS and the first one can be used with all OS and it's clearer). Anyway, what you specify is: real_drive -- how_I_want_it_to_be_seen_by_the_OS Now to your point: Try to coment out those 2 stanzas and run lilo to see if Windows will boot. Sincerely, I can't see a reason for them to be there provided there is not a previous remapping of drives in lilo.conf. Anyway it probably won't change much if all partitions in hdf are invisible to Windows. Good luck, and tell us what comes out. El dom, 09-03-2003 a las 13:01, Anne Wilson escribió: On Sunday 09 Mar 2003 11:57 am, Greg Meyer wrote: On Sunday 09 March 2003 05:19 am, Anne Wilson wrote: In another thread, Mark Watts wrote: I do have these lines in the global options of my lilo.conf though: disk=/dev/hde bios=0x81 disk=/dev/hdg bios=0x82 This reminded me of another unsolved puzzle on my machine. In my lilo.conf there is the following stanza: other=/dev/hde1 label=windowsOriginal table=/dev/hde map-drive=0x80 to=0x81 map-drive=0x81 to=0x80 I don't know how these last two lines got there. The windows stanza doesn't boot, but that may be because I mistakenly broke the chain of fat partitions. I have restored them, but I probably need to re-install windows, I guess. But that's a different issue. The point here is that those two lines appear to contradict each other. Is there a point to this? If so, what's happening? That is lilo remapping your drives from what the BIOS reports so that Windows can be on the first drive which it likes. Basically it allows Windows to physically reside on the second drive, while making it think that it is on the first drive. But windows is on hde1, which *is* my first hdd. And don't the two lines contradict each other? Anne -- Registered Linux User No.293302 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com -- Diego Dominguez __/\__ | | Andalucia /\ Spain \/ |__ __| \/ ___ Yahoo! Messenger - Nueva versión GRATIS Super Webcam, voz, caritas animadas, y más... http://messenger.yahoo.es Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo conf lines
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Joerg Mertin wrote on Wed, Mar 12, 2003 at 07:46:29PM +0100 : Execute Lilo - then boot into the new version, and append only a little: other=/dev/hde6 label=Mandrake_8.2 table=/dev/hde That's the way I do multiple instances of Linux on a single system. Blue skies... Todd - -- | MandrakeSoft USA | Security is like an onion. It's made | | http://www.mandrakesoft.com | made up of several layers and makes | | http://www.mandrakelinux.com | you cry. --Howard Chu| Mandrake Cooker Devel Version, Kernel 2.4.21-0.13mdk -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+b4+hlp7v05cW2woRAj4jAKCczvarohkG89SDg7bAIbFoQv/SXwCdEw9D toJCshYhhcv4FWhcYtunU+k= =f4fr -END PGP SIGNATURE- Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo conf lines
On Wed, Mar 12, 2003 at 07:47:34PM +0100, diego wrote: Let's have first some background before breaking it all ;-)) I have a board with 2 IDE ports (HighPoint's raid) and 2 normal IDE ports. That's why I had to add those 2 disk-stanzas I will describe the issues in my board (that might be quite similar to your case): At startup, BIOS makes raid to be ide 0 and 1, and normal ones 2 and 3. It then tryies to boot from first drive in the first ide available. Let's say it is a master drive in ide 0. We should call it hda. So far so good. The problem is that Linux does not use BIOS to do it's I/O, so as soon as it has been loaded into memory it won't use BIOS conventions. In my case it thinks normal ide port's are 0 and 1, and raid ones are 2 and 3, just the opposite as BIOS stated!!! On my wife's SOYO Dragon+ the BIOS sees the raid controller as a scsi device and will not boot windows from it unless scsi boot is enabled in the bios.I haven't tried to dual boot this board , so I don't know if it's actually relevant,but it might be worth checking the next time you reboot. Ray Warren Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo conf lines
On Wed, 12 Mar 2003 13:51:35 -0600 Ray Warren [EMAIL PROTECTED] wrote: On my wife's SOYO Dragon+ the BIOS sees the raid controller as a scsi device and will not boot windows from it unless scsi boot is enabled in the bios.I haven't tried to dual boot this board , so I don't know if it's actually relevant,but it might be worth checking the next time you reboot. This applies to any board with multiple controllers, be they onboard or added. The system BIOS must be used to set Which controller is to be used as boot device. The default will always be set to ide0. And as Ray noted the designation for the second controller in the BIOS is normally SCSI and or Raid. BTW Ray I have a Dragon+ on this system with all hds connected to the ATA100 controller. System BIOS is set to boot SCSI/ATA100 and linux has no problem with it, Charles -- Insults are effective only where emotion is present. -- Spock, Who Mourns for Adonais? stardate 3468.1 - Mandrake Linux 9.1 on PurpleDragon Kernel- 2.4.21-0.13mdk - pgp0.pgp Description: PGP signature
Re: [expert] Lilo conf lines
On Wednesday 12 Mar 2003 6:46 pm, Joerg Mertin wrote: Hi Anne, so - here we go :) Well blow me down :-) Windows_2 boots! I'm actually missing hde6 in your fstab. Dunno what kernel version was there - but I bet that you could boot it still by adding: image=/mnt/hde6/boot/vmlinuz-2.4.your kernel version label=Mandrake_8.2 root=/dev/hde6 initrd=/mnt/hde6/boot/initrd-2.4.19-16mdk.img append=nobiospnp mem=512M nopentium devfs=mount hdc=ide-scsi read-only You need to take into account that you have to mount your /dev/hde6 partition under /mnt/hde6 before you execute lilo. Be very carefull to not execute lilo under Mandrake 8.2 though - as it would overwrite your Master Boot record again - and make it not possible for you to boot into 9.0 :) I'm not sure I understand this, and it sounds drastic if I get it wrong. Maybe getting it wrong is what caused the problem in the first place. I have a mount-point /mdk8_2, which I didn't put under /mnt because I thought I would only be using it to look at conf files and check that I had duplicated settings that worked. I had no problem with that. I can still mount the partition and read it, but I would not choose to boot to it, as I will soon not have the old /home partition. What I don't understand, though, are your comments about not executing lilo under 8.2, and installing lilo into the partition table of 8.2. Nor about having to navigate through 2 lilos. It seems that only the lilo under hdf1 is being read, and the choices come from there. I must be missing the point. Can you explain more? Back in time - I used another trick for that kind of setups. Very easy - but very efficient. I installed on the old operating Linux partition the lilo into the partition table of my root-partition while running under OS that version - means in your case under Mandrake-8.2: boot=/dev/hde6 map=/boot/map vga=normal keytable=/boot/uk.klt prompt nowarn timeout=0 message=/boot/message menu-scheme=wb:bw:wb:bw # Here - we tell lilo what the BIOS tells the System upon boot. disk=/dev/hde bios=0x80 image=/boot/vmlinuz-your kernel version label=Mandrake_8.2 root=/dev/hdf1 initrd=/boot/initrd-your kernel version append=nobiospnp mem=512M nopentium devfs=mount hdc=ide-scsi read-only Execute Lilo - then boot into the new version, and append only a little: other=/dev/hde6 label=Mandrake_8.2 table=/dev/hde It has one advantage - you won't write with one LILO into the partition of the other LILO - and you can update your kernels under both operating systems without having to fear you go out of sync anywhere, or overwriting the Lilo-information of the other OS-Version. The Drawback is that you'll have to navigate through 2 LILO's. That's also the reason I did set the timeout message to 0. Holding the Ctrl-Key down while going into the second-Lilo instance will give you the ability to add something though ;) Please note that you might need to tweak the settings a little bit. Back in time - it was easyer to cheat on lilo. They have built many logical-Checkings into it - to prevent from user-mistakes, if they don't know what to do. I still prefere doing the lilo.conf using vi :) Hardcore way :) Note2: If the LIlO tells you he made a mistake - don't reboot as long as you have not fixed it ;) usually lilo should write only if syntax and logic checkings have occured - but I happened to have screwed my lilo install several times. Always keep a Bootdisk by hand that works before fiddling with lilo ... Thank Anne -- Registered Linux User No.293302 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo conf lines
Anne Wilson wrote: On Wednesday 12 Mar 2003 6:46 pm, Joerg Mertin wrote: Hi Anne, so - here we go :) Well blow me down :-) Windows_2 boots! Glad to hear it works :) For getting windows to work - you just have to know what it wants... Unfortunatly. That's why my choice went to unix type systems. In there - I know what I want, and I tell my system what to do ;) [...] I'm not sure I understand this, and it sounds drastic if I get it wrong. Maybe getting it wrong is what caused the problem in the first place. I have a mount-point /mdk8_2, which I didn't put under /mnt because I thought I would only be using it to look at conf files and check that I had duplicated settings that worked. I had no problem with that. I can still mount the partition and read it, but I would not choose to boot to it, as I will soon not have the old /home partition. What I don't understand, though, are your comments about not executing lilo under 8.2, and installing lilo into the partition table of 8.2. Nor about having to navigate through 2 lilos. It seems that only the lilo under hdf1 is being read, and the choices come from there. I must be missing the point. Can you explain more? I migh have expressed myself bad. The Problem is that depending on what Mandrake version you have booted, you have an own lilo configuration file. The problem is that you need always to sync the kernel-version inside the lilo.conf, mount the other Operating-Systems root / drive before you can be sure the lilo is configured correctly. However - if you don't intend using that version anymore - just ignore what I said ;) guess it'll be easyer ... Cheers Joerg -- | Joerg Mertin : [EMAIL PROTECTED](Home)| | in Neuchâtel/Schweiz : [EMAIL PROTECTED] (Work)| | Stardust's LiNUX System : | | PGP 2.6.3in Key on Demand : Voice Fax: +41(0)32 / 725 52 54 | Home-Page: http://www.solsys.org Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo conf lines
On Sunday 09 Mar 2003 1:18 pm, g wrote: Anne Wilson wrote: I'm trying to get to grips with both this one and the one that follows it. Bear with me, it's brain-spinning g you may not have an hda and hdb, but, when 'what ever' wrote your 'lilo.conf', it thought you need to have them. so, to give them to you, a 1st re mapping is to issue, disk=/dev/hde bios=0x81 disk=/dev/hdg bios=0x82 which ;logically' changes hde to hda, and hdf to hdb, so that bios will think you have an hda and hdb... That sounds reasonable. BUT, windows is on hde/hda and Mdk9.0 is on hdf/hdb. So why would it want to make further mappings? Isn't that what we are trying to achieve? My brain aches, but I'm sticking with it g I appreciate your time. Anne -- Registered Linux User No.293302 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: Re: [expert] Lilo conf lines
I'm not sure if this is the case or not, but might this problem be due to how your drives are partitioned as in primary vs extended partitions? Could it be that if your OS, doesn't matter which is actually in an extended partition, that LILO need to mount the primary partition containing it to boot? I'm not a LILO guru, so I could be totally wrong. I do know that I've mounted extended partitions (usually when installing Linux in a dual boot environment) and have come up with some pretty strange mappings. One other thought. This isn't a large harddrive that has had a bootmanager installed to override the bios settings on the computer is it? I know that a lot of drives over 32GB have special boot loaders (regardless of the OS) to handle booting. Linux doesn't actually need it (Windows does, sometimes), but does LILO respect it if it is there? A lot of questions, and no real answers, Joeb ---Original Message--- From: Anne Wilson [EMAIL PROTECTED] Sent: 03/11/03 07:05 AM To: [EMAIL PROTECTED] Subject: Re: [expert] Lilo conf lines On Sunday 09 Mar 2003 1:18 pm, g wrote: Anne Wilson wrote: I'm trying to get to grips with both this one and the one that follows it. Bear with me, it's brain-spinning g you may not have an hda and hdb, but, when 'what ever' wrote your 'lilo.conf', it thought you need to have them. so, to give them to you, a 1st re mapping is to issue, disk=/dev/hde bios=0x81 disk=/dev/hdg bios=0x82 which ;logically' changes hde to hda, and hdf to hdb, so that bios will think you have an hda and hdb... That sounds reasonable. BUT, windows is on hde/hda and Mdk9.0 is on hdf/hdb. So why would it want to make further mappings? Isn't that what we are trying to achieve? My brain aches, but I'm sticking with it g I appreciate your time. Anne -- Registered Linux User No.293302 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: Re: [expert] Lilo conf lines
On Tuesday 11 Mar 2003 1:02 pm, Joe Braddock wrote: Hi, Joe I'm not sure if this is the case or not, but might this problem be due to how your drives are partitioned as in primary vs extended partitions? Could it be that if your OS, doesn't matter which is actually in an extended partition, that LILO need to mount the primary partition containing it to boot? No, windows is on hde1, a primary, and Mandrake 9 is on hdf1, also a primary. I'm not a LILO guru, so I could be totally wrong. I do know that I've mounted extended partitions (usually when installing Linux in a dual boot environment) and have come up with some pretty strange mappings. One other thought. This isn't a large harddrive that has had a bootmanager installed to override the bios settings on the computer is it? No - the drives are 19GB and 16GB respectively - no need for anything exotic. I know that a lot of drives over 32GB have special boot loaders (regardless of the OS) to handle booting. Linux doesn't actually need it (Windows does, sometimes), but does LILO respect it if it is there? The only thing odd about the setup is this having 2 ATA100 connectors and 2 ATA66 connectors. Anne -- Registered Linux User No.293302 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo conf lines
Anne Wilson wrote: On Sunday 09 Mar 2003 1:18 pm, g wrote: I'm trying to get to grips with both this one and the one that follows it. Bear with me, it's brain-spinning g not having been into hardware, i can understand how it is confusing to you. i am looking forward to your comments on 'one that follows'. it is almost, 'it works, accept it'. but, such an approach does not answer your questions. That sounds reasonable. BUT, windows is on hde/hda and Mdk9.0 is on hdf/hdb. So why would it want to make further mappings? Isn't that what we are trying to achieve? first re mapping moves drives from ata100 'logical' position, second moves them again to proper positions. it would be better to have a single re map, but for some reason that is not done. why, i can not answer. My brain aches, but I'm sticking with it g I appreciate your time. perseverance. it does my brain good to meet someone like you with a quest for knowledge. :) you are most welcome. this has me wondering just what you at a loss about. *** Date: Tue, 11 Mar 2003 15:14:32 + On Tuesday 11 Mar 2003 1:02 pm, Joe Braddock wrote: The only thing odd about the setup is this having 2 ATA100 connectors and 2 ATA66 connectors. *** why is it odd for a mainboard to have 2 ata controllers? it is an extra feature that one day will/may become a standard. with availability of fast ata100 drives, those 2 controllers will both end up being ata100. ata33 is gone, ata66 is on it's way. -- peace out. tc,hago. g . =+= think green... save a tree, save a life, save time, save bandwidth, save storage. send email: text/plain - disable pgp/gpg/geek code attachments. =+= if you are proud to be an american, then buy made in america. =+= Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo conf lines
On Tuesday 11 Mar 2003 5:00 pm, g wrote: Anne Wilson wrote: On Sunday 09 Mar 2003 1:18 pm, g wrote: I'm trying to get to grips with both this one and the one that follows it. Bear with me, it's brain-spinning g not having been into hardware, i can understand how it is confusing to you. i am looking forward to your comments on 'one that follows'. it is almost, 'it works, accept it'. but, such an approach does not answer your questions. Trouble is, it doesn't work, and hasn't done since these appeared in lilo - not that I am saying they are to blame, just that the loss of windows and the appearance of these lines happened when I installed 9.0. In fact I have checked back, and it seems that it appeared during the period when I was trying to find out why I could not boot to 8.2 as well as 9.0. It is definitely not in the lilo.conf that I saved at that time. That sounds reasonable. BUT, windows is on hde/hda and Mdk9.0 is on hdf/hdb. So why would it want to make further mappings? Isn't that what we are trying to achieve? first re mapping moves drives from ata100 'logical' position, second moves them again to proper positions. it would be better to have a single re map, but for some reason that is not done. why, i can not answer. Since it was not there from the start, I am beginning to wonder if something I did when trying to understand the multipart lilo booting has caused this, and upset things. this has me wondering just what you at a loss about. Sorry - it's just a gut feeling that something is wrong here - and my guts are usually to be trusted g The only thing odd about the setup is this having 2 ATA100 connectors and 2 ATA66 connectors. why is it odd for a mainboard to have 2 ata controllers? Unusual, would have been more precise than odd. Large drives were, of course, not common or cheap when this mobo came out. I don't see many people bothering with 6 hdds + 2 cds at today's sizes, without a raid mobo. Something is not quite right, here, g. I'm pretty sure that if I wiped the disk and started afresh this would not appear, but I still wouldn't know what had caused it. Anne -- Registered Linux User No.293302 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo conf lines
Anne Wilson wrote: Trouble is, it doesn't work, and hasn't done since these appeared in lilo that was a part i was not sure about. if lilo.conf had been working. this puts a whole different light on subject. Since it was not there from the start, I am beginning to wonder if something I did when trying to understand the multipart lilo booting has caused this, and upset things. are you saying that you had both drives on ata100 controller and it was working. now it has diff layout? it would have to be something you have brought about. this has me wondering just what you at a loss about. Sorry - it's just a gut feeling that something is wrong here - and my guts are usually to be trusted g you know your gut better than i do. :) why is it odd for a mainboard to have 2 ata controllers? Unusual, would have been more precise than odd. Large drives were, of course, not common or cheap when this mobo came out. I don't see many people bothering with 6 hdds + 2 cds at today's sizes, without a raid mobo. i will accept unusual. only other way is to add an ide controller card. Something is not quite right, here, g. I'm pretty sure that if I wiped the disk and started afresh this would not appear, but I still wouldn't know what had caused it. before you wipe drive and reinstall, which may not cure problem, what about moving slow drive to ata66 controller. as in move drive to 'primary master'. you could even move both drives to ata66. ata100 will not give full ability, but you would at least have a diff light on things. that is, if it works, then something is wrong with ata100 controller, or you have a prob with lilo.conf. if you do try move, be sure to have a boot disk and change fstab before you shut down and move drives. peace out. tc,hago. g . =+= think green... save a tree, save a life, save time, save bandwidth, save storage. send email: text/plain - disable pgp/gpg/geek code attachments. =+= if you are proud to be an american, then buy made in america. =+= Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: Re: Re: [expert] Lilo conf lines
Are the ATA66 controllers connected to anything? If not, is the controller disabled in CMOS (the hde and hdf correspond to the 3rd and 4th primary controller). Of course, disabling the controller in CMOS might cause nothing to boot as your drives might change from hde/hdf to hdc/hdd, so you might want to proceed cautiously. Joeb ---Original Message--- From: Anne Wilson [EMAIL PROTECTED] Sent: 03/11/03 09:14 AM To: [EMAIL PROTECTED] Subject: Re: Re: [expert] Lilo conf lines On Tuesday 11 Mar 2003 1:02 pm, Joe Braddock wrote: Hi, Joe I'm not sure if this is the case or not, but might this problem be due to how your drives are partitioned as in primary vs extended partitions? Could it be that if your OS, doesn't matter which is actually in an extended partition, that LILO need to mount the primary partition containing it to boot? No, windows is on hde1, a primary, and Mandrake 9 is on hdf1, also a primary. I'm not a LILO guru, so I could be totally wrong. I do know that I've mounted extended partitions (usually when installing Linux in a dual boot environment) and have come up with some pretty strange mappings. One other thought. This isn't a large harddrive that has had a bootmanager installed to override the bios settings on the computer is it? No - the drives are 19GB and 16GB respectively - no need for anything exotic. I know that a lot of drives over 32GB have special boot loaders (regardless of the OS) to handle booting. Linux doesn't actually need it (Windows does, sometimes), but does LILO respect it if it is there? The only thing odd about the setup is this having 2 ATA100 connectors and 2 ATA66 connectors. Anne -- Registered Linux User No.293302 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo conf lines
On Tuesday 11 Mar 2003 8:44 pm, g wrote: Anne Wilson wrote: are you saying that you had both drives on ata100 controller and it was working. now it has diff layout? Yes. I have made no change to the physical layout. The drives are where they have always been. I was booting between windows and Mdk 8.2 before I installed 9.0. it would have to be something you have brought about. My feeling exactly, but what? only other way is to add an ide controller card. I have no reason to believe that the controller was working before but is not now. before you wipe drive and reinstall, which may not cure problem, what about moving slow drive to ata66 controller. as in move drive to 'primary master'. you could even move both drives to ata66. ata100 will not give full ability, but you would at least have a diff light on things. that is, if it works, then something is wrong with ata100 controller, or you have a prob with lilo.conf. if you do try move, be sure to have a boot disk and change fstab before you shut down and move drives. It may come to that. But I'm still convinced it is something that I did that accidentally upset it. Going back to the start. When I installed 9.0 I could boot to 9.0 but not 8.2 (I don't think I tried windows at that point). With JRS's help I eventually sorted it out. I do not have a separate /boot partition. We had to find which partition was booting (i.e. which kernel booting from where). Once we did that, renamed the kernel and initrd files, then copied across the missing pair, renaming them, and all was well. So I breathed a sigh of relief, and booted windows for a quick but overdue job. It didn't boot, and hasn't done since. I think I did something during that period that has caused this. I have lived without windows native on this machine since that install, but as I still have hardware as yet unrecognised I occasionally need windows. At the moment I am borrowing a machine when that's essential. I could, of course, hang on until I get 9.1. I am thinking of making that a clean install of windows and 9.1 on a new large hdd, then perhaps wiping the better of these two disks and reinstalling 9.0 on that. Still, though, I hate not knowing what has caused this. Anne -- Registered Linux User No.293302 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: Re: Re: [expert] Lilo conf lines
On Tuesday 11 Mar 2003 7:29 pm, Joe Braddock wrote: Are the ATA66 controllers connected to anything? If not, is the controller disabled in CMOS (the hde and hdf correspond to the 3rd and 4th primary controller). Of course, disabling the controller in CMOS might cause nothing to boot as your drives might change from hde/hdf to hdc/hdd, so you might want to proceed cautiously. Joeb I use the ATA66 controllers for cd-rw and cd-dvd. Anne -- Registered Linux User No.293302 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo conf lines
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Good afternoon, Anne... I've been avidly following this discussion regarding ATA100 drives because I saw something quite akin to that just last week. I formatted and installed two ATA100 drives, both on the primary cable as Master/Slave, and did a bunch of other install configuration thingees. About an hour later, I decided in a rash moment of heat, to put one drive as primary/master and one drive as secondary/master. The second drive disappeared. Since I really didn't have the time to figure it out, I put them back where they were formatted and all was well. Several attempts resulted in the same findings and finally I put the case on it and all was well. That day there simply wasn't enough time. sigh On Tuesday 11 March 2003 01:57 pm, Anne Wilson wrote: I hate not knowing what has caused this. Me too. 8-( Dave - -- Dave Laird ([EMAIL PROTECTED]) The Used Kharma Lot / The Phoenix Project Web Page: http://www.kharma.net updated 03/05/2003 Usenet News server: news.kharma.net Musicians Calendar and Database access: http://www.kharma.net/calendar.html An automatic random thought For the Minute: Utility is when you have one telephone, luxury is when you have two, opulence is when you have three -- and paradise is when you have none. -- Doug Larson -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+bl4/aE1ENZP1A28RAgkqAJ4+xAk145RGbHz9qY7lUcLZeFEfRACfUOym urv/RVotjIeiDTGlzvqEh9k= =CBro -END PGP SIGNATURE- Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo conf lines
Dave Laird wrote: decided in a rash moment of heat, to put one drive as primary/master and one drive as secondary/master. The second drive disappeared. did you change fstab and lilo.conf? peace out. tc,hago. g . =+= think green... save a tree, save a life, save time, save bandwidth, save storage. send email: text/plain - disable pgp/gpg/geek code attachments. =+= if you are proud to be an american, then buy made in america. =+= Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo conf lines
Anne Wilson wrote: Yes. I have made no change to the physical layout. The drives are where they have always been. I was booting between windows and Mdk 8.2 before I installed 9.0. there is a diff with 8.2 and 9.0. what i do not know. something to do with how booting is handled. if you do try move, be sure to have a boot disk and change fstab before you shut down and move drives. It may come to that. But I'm still convinced it is something that I did that accidentally upset it. doing so would insure that your ata100 controller did not die on you. it may well be something you did, but only you know what that was. ;) Going back to the start. When I installed 9.0 I could boot to 9.0 but not 8.2 i believe that it has something to do with diff kernels. i put rh 8.0 on a box that had md 8.1 on it and let rh 8.0 write a new lilo. that is where i made a big error. rh 8.0 trashed md 8.1 beyond any recovery. pair, renaming them, and all was well. So I breathed a sigh of relief, and booted windows for a quick but overdue job. It didn't boot, and hasn't done since. all of this is with drives on ata100 controller? I could, of course, hang on until I get 9.1. I am thinking of making that a clean install of windows and 9.1 on a new large hdd, then perhaps wiping the better of these two disks and reinstalling 9.0 on that. Still, though, I hate not knowing what has caused this. even with a new large drive, i would put oos on it's own drive and put it at hda. to prove out some of potential causes, if it where my system, i would move drives to hda and hdb, just to set what will happen. it may work, it may crap out. but at this point, what harm would it do and what would you loose but time it takes. it would give deeper insight to what might be happening. peace out. tc,hago. g . =+= think green... save a tree, save a life, save time, save bandwidth, save storage. send email: text/plain - disable pgp/gpg/geek code attachments. =+= if you are proud to be an american, then buy made in america. =+= Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo conf lines
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 G'afternoon, g... On Tuesday 11 March 2003 02:24 pm, g wrote: did you change fstab and lilo.conf? Yup. I looked in dmesg, and everything matches. I think the problem is with the MB BIOS, since the secondary drive is a 120 G EIDE on an 80 pin cable. Last night I tried the same experiment here, using two drives and a more-recent Motherboard and BIOS and saw no such problems, no matter where I put the drives. I think I'll go back out that way next week and flash the BIOS with the latest and see what happens. Thanks, though... Dave - -- Dave Laird ([EMAIL PROTECTED]) The Used Kharma Lot / The Phoenix Project Web Page: http://www.kharma.net updated 03/05/2003 Usenet News server: news.kharma.net Musicians Calendar and Database access: http://www.kharma.net/calendar.html An automatic random thought For the Minute: Women, when they have made a sheep of a man, always tell him that he is a lion with a will of iron. -- Honor'e de Balzac -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+bmf2aE1ENZP1A28RAkOQAKC+W4KmvucgCkeo/5XN+HWqFL56iACggM9D 1q/cs5ZbtbpSJcHKaDc57o0= =+Kvf -END PGP SIGNATURE- Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo with multiple hard drives...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ok, answers to questions: No, I wasnt using cable select. No, I wasnt changing any jumpers. This has nothing to do with fstab - that doesnt get processed at the lilo point. With all 3 drives in, I get a lilo prompt. With hdb removed I get LI LI LI LI... hdb is NOT mentioned in lilo.conf, so why does removing that drive affect lilo? Cheers. Mark. On Friday 07 March 2003 09:33 pm, Gary Hodder wrote: Hi Mark, with the 3 drives in and it boots normally, edit the fstab file and change the hdc? to hdb? ? being the partition number. Change lilo to be hdb instead of hdc. Reboot with a floppy, at lilo promp: linux root=/dev/hdb? ? being the partition number the os is on. Run lilo. Reboot to boot from kernel on harddrive. Gary. and next time, don't use cable select as the way to choice master and slave HDs, use the jumpers on the drive itself. On Fri, 2003-03-07 at 22:19, Mark Watts wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I have a system with 3 harddrives in it (hda = Windows, hdb = spare (part XFS, part FAT32) and hdc = Linux (resierfs). I installed Windows first, followed by 9.0 on hdc, and chose to install lilo to hda's boot sector. This has been working just fine since I installed. I've come to a point where I'm moving hdb out of the system... Whenever I remove it, I get the ubiquitos LI LI LI LI LI across the screen, indicating that lilo is toast. Putting the drive back makes everything work as before. 2 questions: 1) Should lilo really be doing this, bearing in mind that hdb isnt mentioned in lilo.conf (It has an old 8.2 install I havent removed yet on it, but I'd have to make a boot disk to boot from it). 2) If I re-reun lilo (from a rescue cd and chrooting stuff) without changing lilo.conf, will that fix the LI LI LI issue? Cheers, Mark. - -- Mark Watts Systems Engineer QinetiQ TIM St Andrews Road, Malvern GPG Public Key available on request. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+aIA5Bn4EFUVUIO0RAhuvAKCzIzCZDqFlr6+RWzdSEmrpglnB8QCgxetA gfpHOl0qRleNXs2VLEiSQcY= =wfFV -END PGP SIGNATURE- Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com - -- Mark Watts Systems Engineer QinetiQ TIM St Andrews Road, Malvern GPG Public Key available on request. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+bGpLBn4EFUVUIO0RAkDeAJ0WLGqDCacQRyYIE0O2qNY5kCZ6BgCeNPsc S+knuDCAmZocwoLKJ8l15tU= =11Y0 -END PGP SIGNATURE- Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo with multiple hard drives...
On Mon, 10 Mar 2003 10:34:50 + Mark Watts [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ok, answers to questions: No, I wasnt using cable select. No, I wasnt changing any jumpers. This has nothing to do with fstab - that doesnt get processed at the lilo point. With all 3 drives in, I get a lilo prompt. With hdb removed I get LI LI LI LI... hdb is NOT mentioned in lilo.conf, so why does removing that drive affect lilo? If you have more than one bootable system, depending on the mount points, location of bootable images, etc, lilo may be correctly configured for one OS; but wrong for another... before removing the drive, boot up every system, and check their lilo configs based on how the system is configured for EACH... it can really test your sanity in some setups... it'll help to draw a map showing how everything points to what... while drawing the map, remember: it's a sanity test you may be quite surprised to find where the entries point to... Good luck! Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo with multiple hard drives...
On Monday 10 March 2003 05:34 am, Mark Watts wrote: Ok, answers to questions: No, I wasnt using cable select. No, I wasnt changing any jumpers. This has nothing to do with fstab - that doesnt get processed at the lilo point. With all 3 drives in, I get a lilo prompt. With hdb removed I get LI LI LI LI... hdb is NOT mentioned in lilo.conf, so why does removing that drive affect lilo? Cheers. This discussion is a perfect example of why I use GrUB. -- Greg Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo conf lines
On Sunday 09 Mar 2003 1:18 pm, g wrote: Anne Wilson wrote: On Sunday 09 Mar 2003 11:59 am, Joerg Mertin wrote: this is actually a BIOS remapping, telling the System to change the Now I'm really confused. First, I dpn't have a hda - I think that's something to do with the unusual setup on this mobo, which has the usual 2 IDE interfaces + 2 UDMA interfaces with a software Promise controller. you may not have an hda and hdb, but, when 'what ever' wrote your 'lilo.conf', it thought you need to have them. so, to give them to you, a 1st re mapping is to issue, disk=/dev/hde bios=0x81 disk=/dev/hdg bios=0x82 which ;logically' changes hde to hda, and hdf to hdb, so that bios will think you have an hda and hdb... then because 'what ever' 'thinks' 'windowsOriginal' has to be on hda, which in fact it does not, it again re wrote what is in bios to move logical hdb to logical hda, and logical hda to logical hdb. i would guess this to happen because when 'table=/dev/hde' is seen, it thinks this is not 'hda/0x80' so it re maps again with, map-drive=0x80 to=0x81 map-drive=0x81 to=0x80 in effect, hde is 'logically' moved to hdb/0x81, then moved to hda/0x80. just a new play on old term 'faking it'. hthth. g - I've been away a couple of days, so I'm just picking this up. If windows is on hde1, and hde has been mapped to appear to be hdb, then windows will not boot. Correct? Does this mean that I should comment out the second mapping and try it? Anne -- Registered Linux User No.293302 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo conf lines
On Sunday 09 Mar 2003 4:41 pm, Rolf Pedersen wrote: map-drive=0x80 to=0x81 map-drive=0x81 to=0x80 Seems relevant. Maybe there is some correlation to your situation(s). hth. Rolf Rolf, I've been away, and come in rather late at night. I'm going to need to digest this. I may well be back with more questions, but thanks for the answer. It certainly looks relevant. Anne -- Registered Linux User No.293302 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo conf lines
Anne Wilson wrote: On Sunday 09 Mar 2003 1:18 pm, g wrote: Anne Wilson wrote: On Sunday 09 Mar 2003 11:59 am, Joerg Mertin wrote: this is actually a BIOS remapping, telling the System to change the Now I'm really confused. just a new play on old term 'faking it'. hthth. but it did not. :P g - I've been away a couple of days, so I'm just picking this up. If windows is on hde1, and hde has been mapped to appear to be hdb, then windows will not boot. Correct? incorrect. }}- understand a miss understanding, up to and including w98se, }}- ms os boots active drive and designates it as 'c:\'. es. 1st, go back and re read your lilo.conf. 2nd, re read my last. lilo maps drives from ata100 controller to _bios_ position 0x81, 0x82. this is not a 'physical', but a 'bios software' position. at label 'other', bios positions are changed to move 'hde1', now '0x81', to bios '0x80' and bios '0x80' becomes '0x81'. this is all done in bios memory, where a byte of data can be a binary 'command', or, a binary 'switch', or, a 'pointer'. regardless of what it is, it is located in an assigned place for a specific reason. if you looked at these bytes as they 'may be' in bios they would look on an order of; normal value assignment 0x80 /dev/hda 0x81 /dev/hdb 0x82 /dev/hdc 0x83 /dev/hdd 0x88 /dev/hde [ 0x88 - 0x8b are example ] 0x89 /dev/hdf [ have yet to see hw byte table ] 0x8a /dev/hdg 0x8b /dev/hdh 1st re mapped 0x80 /dev/hda 0x88 /dev/hdb 0x89 /dev/hdc 0x83 /dev/hdd 0x81 /dev/hde 0x82 /dev/hdf 0x8a /dev/hdg 0x8b /dev/hdh 2nd re mapped 0x88 /dev/hda 0x80 /dev/hdb 0x89 /dev/hdc 0x83 /dev/hdd 0x81 /dev/hde 0x82 /dev/hdf 0x8a /dev/hdg 0x8b /dev/hdh now that you are more confused, grasp this; in control of hardware, bytes are bits, and bits are switches. a byte can turn on or off any single device, by bit position. in assigning devices, 2 bytes used, msb is device type or group. lsb is device in type or group. as i believe i mentioned else where, ata66 to ata66, ata100 to ata100. you will need to change lilo.conf and fstab. but it may end up less of a confusion. ;) Does this mean that I should comment out the second mapping and try it? no. try what i just suggested, again. bwg that is, unless it works as it is and you are trying to understand why your lilo has drive reassignment and how it is done. peace out. tc,hago. g . =+= think green... save a tree, save a life, save time, save bandwidth, save storage. send email: text/plain - disable pgp/gpg/geek code attachments. =+= if you are proud to be an american, then buy made in america. =+= Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo conf lines
On Sunday 09 March 2003 05:19 am, Anne Wilson wrote: In another thread, Mark Watts wrote: I do have these lines in the global options of my lilo.conf though: disk=/dev/hde bios=0x81 disk=/dev/hdg bios=0x82 This reminded me of another unsolved puzzle on my machine. In my lilo.conf there is the following stanza: other=/dev/hde1 label=windowsOriginal table=/dev/hde map-drive=0x80 to=0x81 map-drive=0x81 to=0x80 I don't know how these last two lines got there. The windows stanza doesn't boot, but that may be because I mistakenly broke the chain of fat partitions. I have restored them, but I probably need to re-install windows, I guess. But that's a different issue. The point here is that those two lines appear to contradict each other. Is there a point to this? If so, what's happening? That is lilo remapping your drives from what the BIOS reports so that Windows can be on the first drive which it likes. Basically it allows Windows to physically reside on the second drive, while making it think that it is on the first drive. -- Greg Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo conf lines
Hi Anne, this is actually a BIOS remapping, telling the System to change the Bios-Mappings for the harddrives from 0x80 - 0x81 and vice versa, or in better terms, change the the order the harddisks will be presented to the Windows-Boot loader. In the MSDos Times, and windows OS's based on DOS (98, ME etc.), the OS needed to boot from drive 0x80 (Except when using SCSI) or Linux ;). In your case, the default Old-times boot drive 0x80 (hda) is replaced with the 0x81 (hde) entry, which from your lilo-default configuration is correct. However - I do not know how the global parameters do interact with your /dev/hde1-settings. Never tried it myself. Cheers Joerg Anne Wilson wrote: In another thread, Mark Watts wrote: I do have these lines in the global options of my lilo.conf though: disk=/dev/hde bios=0x81 disk=/dev/hdg bios=0x82 This reminded me of another unsolved puzzle on my machine. In my lilo.conf there is the following stanza: other=/dev/hde1 label=windowsOriginal table=/dev/hde map-drive=0x80 to=0x81 map-drive=0x81 to=0x80 I don't know how these last two lines got there. The windows stanza doesn't boot, but that may be because I mistakenly broke the chain of fat partitions. I have restored them, but I probably need to re-install windows, I guess. But that's a different issue. The point here is that those two lines appear to contradict each other. Is there a point to this? If so, what's happening? Anne Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com -- | Joerg Mertin : [EMAIL PROTECTED](Home)| | in Neuchâtel/Schweiz : [EMAIL PROTECTED] (Work)| | Stardust's LiNUX System : | | PGP 2.6.3in Key on Demand : Voice Fax: +41(0)32 / 725 52 54 | Home-Page: http://www.solsys.org Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo conf lines
On Sunday 09 Mar 2003 11:57 am, Greg Meyer wrote: On Sunday 09 March 2003 05:19 am, Anne Wilson wrote: In another thread, Mark Watts wrote: I do have these lines in the global options of my lilo.conf though: disk=/dev/hde bios=0x81 disk=/dev/hdg bios=0x82 This reminded me of another unsolved puzzle on my machine. In my lilo.conf there is the following stanza: other=/dev/hde1 label=windowsOriginal table=/dev/hde map-drive=0x80 to=0x81 map-drive=0x81 to=0x80 I don't know how these last two lines got there. The windows stanza doesn't boot, but that may be because I mistakenly broke the chain of fat partitions. I have restored them, but I probably need to re-install windows, I guess. But that's a different issue. The point here is that those two lines appear to contradict each other. Is there a point to this? If so, what's happening? That is lilo remapping your drives from what the BIOS reports so that Windows can be on the first drive which it likes. Basically it allows Windows to physically reside on the second drive, while making it think that it is on the first drive. But windows is on hde1, which *is* my first hdd. And don't the two lines contradict each other? Anne -- Registered Linux User No.293302 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo conf lines
On Sunday 09 Mar 2003 11:59 am, Joerg Mertin wrote: Hi Anne, this is actually a BIOS remapping, telling the System to change the Bios-Mappings for the harddrives from 0x80 - 0x81 and vice versa, or in better terms, change the the order the harddisks will be presented to the Windows-Boot loader. In the MSDos Times, and windows OS's based on DOS (98, ME etc.), the OS needed to boot from drive 0x80 (Except when using SCSI) or Linux ;). In your case, the default Old-times boot drive 0x80 (hda) is replaced with the 0x81 (hde) entry, which from your lilo-default configuration is correct. However - I do not know how the global parameters do interact with your /dev/hde1-settings. Never tried it myself. Now I'm really confused. First, I dpn't have a hda - I think that's something to do with the unusual setup on this mobo, which has the usual 2 IDE interfaces + 2 UDMA interfaces with a software Promise controller. My hard drives are listed as hde and hdf. Windows is on hde1, and Mdk 9.0 is on hdf1. With that in mind, could you please spell it out again? Sorry if I'm being obtuse, but I really do want to understand. Anne -- Registered Linux User No.293302 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo conf lines
Anne Wilson wrote: On Sunday 09 Mar 2003 11:59 am, Joerg Mertin wrote: this is actually a BIOS remapping, telling the System to change the Now I'm really confused. First, I dpn't have a hda - I think that's something to do with the unusual setup on this mobo, which has the usual 2 IDE interfaces + 2 UDMA interfaces with a software Promise controller. you may not have an hda and hdb, but, when 'what ever' wrote your 'lilo.conf', it thought you need to have them. so, to give them to you, a 1st re mapping is to issue, disk=/dev/hde bios=0x81 disk=/dev/hdg bios=0x82 which ;logically' changes hde to hda, and hdf to hdb, so that bios will think you have an hda and hdb... then because 'what ever' 'thinks' 'windowsOriginal' has to be on hda, which in fact it does not, it again re wrote what is in bios to move logical hdb to logical hda, and logical hda to logical hdb. i would guess this to happen because when 'table=/dev/hde' is seen, it thinks this is not 'hda/0x80' so it re maps again with, map-drive=0x80 to=0x81 map-drive=0x81 to=0x80 in effect, hde is 'logically' moved to hdb/0x81, then moved to hda/0x80. just a new play on old term 'faking it'. hthth. -- peace out. tc,hago. g . =+= think green... save a tree, save a life, save time, save bandwidth, save storage. send email: text/plain - disable pgp/gpg/geek code attachments. =+= if you are proud to be an american, then buy made in america. =+= Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo conf lines
Anne Wilson wrote: In another thread, Mark Watts wrote: I do have these lines in the global options of my lilo.conf though: disk=/dev/hde bios=0x81 disk=/dev/hdg bios=0x82 This reminded me of another unsolved puzzle on my machine. In my lilo.conf there is the following stanza: other=/dev/hde1 label=windowsOriginal table=/dev/hde map-drive=0x80 to=0x81 map-drive=0x81 to=0x80 I don't know how these last two lines got there. The windows stanza doesn't boot, but that may be because I mistakenly broke the chain of fat partitions. I have restored them, but I probably need to re-install windows, I guess. But that's a different issue. The point here is that those two lines appear to contradict each other. Is there a point to this? If so, what's happening? Anne I think two sections from 'info lilo.conf' would be germane: disk=device-name Defines non-standard parameters for the specified disk. See section Disk geometry of user.tex for details. Especially useful is the `bios=' parameter. The BIOS numbers your disks 0x80, 0x81, etc. and it is impossible to decide which Linux disk corresponds to which BIOS disk (since this depends on the BIOS setup, and on the type of BIOS), so if you have an unusual setup you need to state the correspondence between Linux disks and BIOS disks. For example, disk=/dev/sda bios=0x80 disk=/dev/hda bios=0x81 would say that your SCSI disk is the first BIOS disk, and your (primary master) IDE disk is the second BIOS disk. [...] map-drive=num Maps BIOS calls for the specified drive to the device code spec- ified on the next line as to=num. This mapping is useful for booting operating systems, such as DOS, from the second hard drive. The following, swaps the C: and D: drives, map-drive=0x80 to=0x81 map-drive=0x81 to=0x80 Seems relevant. Maybe there is some correlation to your situation(s). hth. Rolf Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo with multiple hard drives...
Stupid question: when removing hdb, you aren't changing hdc jumpers, are you?? El vie, 07-03-2003 a las 12:19, Mark Watts escribió: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I have a system with 3 harddrives in it (hda = Windows, hdb = spare (part XFS, part FAT32) and hdc = Linux (resierfs). I installed Windows first, followed by 9.0 on hdc, and chose to install lilo to hda's boot sector. This has been working just fine since I installed. I've come to a point where I'm moving hdb out of the system... Whenever I remove it, I get the ubiquitos LI LI LI LI LI across the screen, indicating that lilo is toast. Putting the drive back makes everything work as before. 2 questions: 1) Should lilo really be doing this, bearing in mind that hdb isnt mentioned in lilo.conf (It has an old 8.2 install I havent removed yet on it, but I'd have to make a boot disk to boot from it). 2) If I re-reun lilo (from a rescue cd and chrooting stuff) without changing lilo.conf, will that fix the LI LI LI issue? Cheers, Mark. - -- Mark Watts Systems Engineer QinetiQ TIM St Andrews Road, Malvern GPG Public Key available on request. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+aIA5Bn4EFUVUIO0RAhuvAKCzIzCZDqFlr6+RWzdSEmrpglnB8QCgxetA gfpHOl0qRleNXs2VLEiSQcY= =wfFV -END PGP SIGNATURE- Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com -- Diego Dominguez __/\__ | | Andalucia /\ Spain \/ |__ __| \/ ___ Yahoo! Messenger - Nueva versión GRATIS Super Webcam, voz, caritas animadas, y más... http://messenger.yahoo.es Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo with multiple hard drives...
On Friday 07 March 2003 09:33 pm, Gary Hodder wrote: Hi Mark, with the 3 drives in and it boots normally, edit the fstab file and change the hdc? to hdb? ? being the partition number. Change lilo to be hdb instead of hdc. Reboot with a floppy, at lilo promp: linux root=/dev/hdb? ? being the partition number the os is on. Run lilo. Reboot to boot from kernel on harddrive. Gary. and next time, don't use cable select as the way to choice master and slave HDs, use the jumpers on the drive itself. On Fri, 2003-03-07 at 22:19, Mark Watts wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I have a system with 3 harddrives in it (hda = Windows, hdb = spare (part XFS, part FAT32) and hdc = Linux (resierfs). I installed Windows first, followed by 9.0 on hdc, and chose to install lilo to hda's boot sector. This has been working just fine since I installed. I've come to a point where I'm moving hdb out of the system... Whenever I remove it, I get the ubiquitos LI LI LI LI LI across the screen, indicating that lilo is toast. Putting the drive back makes everything work as before. 2 questions: 1) Should lilo really be doing this, bearing in mind that hdb isnt mentioned in lilo.conf (It has an old 8.2 install I havent removed yet on it, but I'd have to make a boot disk to boot from it). 2) If I re-reun lilo (from a rescue cd and chrooting stuff) without changing lilo.conf, will that fix the LI LI LI issue? Cheers, Mark. - -- Mark Watts Systems Engineer QinetiQ TIM St Andrews Road, Malvern GPG Public Key available on request. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+aIA5Bn4EFUVUIO0RAhuvAKCzIzCZDqFlr6+RWzdSEmrpglnB8QCgxetA gfpHOl0qRleNXs2VLEiSQcY= =wfFV -END PGP SIGNATURE- Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo with multiple hard drives...
I think that happens cause of the auto remapping of your drives. I think hdc becomes hdb when you pull hdb out. So modifying lilo.conf and replacing hdc with hdb, running lilo afterwards, removing hdb and rebooting should solve it. - Original Message - From: Mark Watts [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, March 07, 2003 12:19 PM Subject: [expert] Lilo with multiple hard drives... -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I have a system with 3 harddrives in it (hda = Windows, hdb = spare (part XFS, part FAT32) and hdc = Linux (resierfs). I installed Windows first, followed by 9.0 on hdc, and chose to install lilo to hda's boot sector. This has been working just fine since I installed. I've come to a point where I'm moving hdb out of the system... Whenever I remove it, I get the ubiquitos LI LI LI LI LI across the screen, indicating that lilo is toast. Putting the drive back makes everything work as before. 2 questions: 1) Should lilo really be doing this, bearing in mind that hdb isnt mentioned in lilo.conf (It has an old 8.2 install I havent removed yet on it, but I'd have to make a boot disk to boot from it). 2) If I re-reun lilo (from a rescue cd and chrooting stuff) without changing lilo.conf, will that fix the LI LI LI issue? Cheers, Mark. - -- Mark Watts Systems Engineer QinetiQ TIM St Andrews Road, Malvern GPG Public Key available on request. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+aIA5Bn4EFUVUIO0RAhuvAKCzIzCZDqFlr6+RWzdSEmrpglnB8QCgxetA gfpHOl0qRleNXs2VLEiSQcY= =wfFV -END PGP SIGNATURE- Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo with multiple hard drives...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I think that happens cause of the auto remapping of your drives. I think hdc becomes hdb when you pull hdb out. So modifying lilo.conf and replacing hdc with hdb, running lilo afterwards, removing hdb and rebooting should solve it. Shouldn't do - on other boxes I run a single drive on each channel, so I never get an hdb (or hdd/hdf/hdh) Mark - -- Mark Watts Systems Engineer QinetiQ TIM St Andrews Road, Malvern GPG Public Key available on request. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+aJnUBn4EFUVUIO0RAsVFAJ0YOnvmW7+xrDAkUx3auZLigIOqawCgi7kh oAydSM3ts7EZLOMBC4uc9cc= =K5lm -END PGP SIGNATURE- Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo with multiple hard drives...
well.. in my case it helped when I had the prob (though can't remember exactly which drive was remapped in my case. Can you post your lilo.conf? Best regards, Adrian - Original Message - From: Mark Watts [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, March 07, 2003 2:08 PM Subject: Re: [expert] Lilo with multiple hard drives... -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I think that happens cause of the auto remapping of your drives. I think hdc becomes hdb when you pull hdb out. So modifying lilo.conf and replacing hdc with hdb, running lilo afterwards, removing hdb and rebooting should solve it. Shouldn't do - on other boxes I run a single drive on each channel, so I never get an hdb (or hdd/hdf/hdh) Mark - -- Mark Watts Systems Engineer QinetiQ TIM St Andrews Road, Malvern GPG Public Key available on request. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+aJnUBn4EFUVUIO0RAsVFAJ0YOnvmW7+xrDAkUx3auZLigIOqawCgi7kh oAydSM3ts7EZLOMBC4uc9cc= =K5lm -END PGP SIGNATURE- Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo with multiple hard drives...
Hi Mark, with the 3 drives in and it boots normally, edit the fstab file and change the hdc? to hdb? ? being the partition number. Change lilo to be hdb instead of hdc. Reboot with a floppy, at lilo promp: linux root=/dev/hdb? ? being the partition number the os is on. Run lilo. Reboot to boot from kernel on harddrive. Gary. On Fri, 2003-03-07 at 22:19, Mark Watts wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I have a system with 3 harddrives in it (hda = Windows, hdb = spare (part XFS, part FAT32) and hdc = Linux (resierfs). I installed Windows first, followed by 9.0 on hdc, and chose to install lilo to hda's boot sector. This has been working just fine since I installed. I've come to a point where I'm moving hdb out of the system... Whenever I remove it, I get the ubiquitos LI LI LI LI LI across the screen, indicating that lilo is toast. Putting the drive back makes everything work as before. 2 questions: 1) Should lilo really be doing this, bearing in mind that hdb isnt mentioned in lilo.conf (It has an old 8.2 install I havent removed yet on it, but I'd have to make a boot disk to boot from it). 2) If I re-reun lilo (from a rescue cd and chrooting stuff) without changing lilo.conf, will that fix the LI LI LI issue? Cheers, Mark. - -- Mark Watts Systems Engineer QinetiQ TIM St Andrews Road, Malvern GPG Public Key available on request. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+aIA5Bn4EFUVUIO0RAhuvAKCzIzCZDqFlr6+RWzdSEmrpglnB8QCgxetA gfpHOl0qRleNXs2VLEiSQcY= =wfFV -END PGP SIGNATURE- Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] lilo and change rules for extended partition
felix well, thanks to you i revisited my partitioning setup and of course it transpires that the partition numbers had been altered somewhere along the way due to me doing two things at once while altering the id, so xp was booting of the other drive but not mounting the other ntfs volume, i'm used to this with linux, in fact i hardly think about it if i repartition but it's a first with win since i never used junction points before with ntfs! aside: the volume name for a win ntfs volume is 46 characters long, now that's an easy to use command line! so having messed in safe mode command line i'm up and running with it, thankyou for making me look twice! :) bascule On Tuesday 18 Feb 2003 7:13 pm, Felix Miata wrote: bascule wrote: thanks felix but my winxp will not see the ntfs partition that is within the extended partition unless the typ is other than 05, specifically it will not mount it onto it's filesystem and since that partition is the 'documents and settings' stuff i can hardly do without it :) if you are sure that winxp pro should be able to do this from within a 05 id extended partition then i shall have to double check the integrity but there are no signs of errors, this linux install is booted from within the same extended partition I don't have WXP to try, but W2K has no such problem, and I've never heard of anyone else with XP unable to access logicals within a standard 05 extended. -- The truth may be out there, but lies are inside your head. (Hogfather) Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] lilo and change rules for extended partition
bascule wrote: when using lilo to hide partitions in the past i have relied on the examples i found online and in man lilo.conf, but now that i wish to alter the id of the extended partition (so that both os/2 and winxp will both work) i can't find any confirmation of the appropriate nomenclature. the examples that i can find, for example: set=DOS16_big_normal or set=NTFS_normal do not actually coincide with the partition id list given by fdisk so i'm not sure if it is safe to just put: change partition=/dev/hda2 set=0x05 and so forth; the extended partition is a primary partition so i'm assuming it's id can be changed (i read that this can't be done for logical partitions) can anyone tell me what the nomenclature is for the set= line to change the extended partition to id 05 (Extended) and to 0f (ExtendedX) Use FDISK to change it to 05 and leave it that way. 0F is for W95OSR2, W98, and WME. NT and its derivatives aren't so brain dead as to require a non-standard extended type to know how to deal with a big disk. See below URL for more. -- Democracy is two wolves and a lamb voting on what to have for lunch. Liberty is a well-armed lamb contesting the vote. Benjamin Franklin Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://members.ij.net/mrmazda/partitioningindex.html Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] lilo and change rules for extended partition
thanks felix but my winxp will not see the ntfs partition that is within the extended partition unless the typ is other than 05, specifically it will not mount it onto it's filesystem and since that partition is the 'documents and settings' stuff i can hardly do without it :) if you are sure that winxp pro should be able to do this from within a 05 id extended partition then i shall have to double check the integrity but there are no signs of errors, this linux install is booted from within the same extended partition bascule On Tuesday 18 Feb 2003 6:25 pm, Felix Miata wrote: bascule wrote: when using lilo to hide partitions in the past i have relied on the examples i found online and in man lilo.conf, but now that i wish to alter the id of the extended partition (so that both os/2 and winxp will both work) i can't find any confirmation of the appropriate nomenclature. the examples that i can find, for example: set=DOS16_big_normal or set=NTFS_normal do not actually coincide with the partition id list given by fdisk so i'm not sure if it is safe to just put: change partition=/dev/hda2 set=0x05 and so forth; the extended partition is a primary partition so i'm assuming it's id can be changed (i read that this can't be done for logical partitions) can anyone tell me what the nomenclature is for the set= line to change the extended partition to id 05 (Extended) and to 0f (ExtendedX) Use FDISK to change it to 05 and leave it that way. 0F is for W95OSR2, W98, and WME. NT and its derivatives aren't so brain dead as to require a non-standard extended type to know how to deal with a big disk. See below URL for more. -- Anyone who is capable of getting themselves made President should on no account be allowed to do the job. -- Some wisdom from The Book. Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] lilo and change rules for extended partition
bascule wrote: thanks felix but my winxp will not see the ntfs partition that is within the extended partition unless the typ is other than 05, specifically it will not mount it onto it's filesystem and since that partition is the 'documents and settings' stuff i can hardly do without it :) if you are sure that winxp pro should be able to do this from within a 05 id extended partition then i shall have to double check the integrity but there are no signs of errors, this linux install is booted from within the same extended partition I don't have WXP to try, but W2K has no such problem, and I've never heard of anyone else with XP unable to access logicals within a standard 05 extended. -- Democracy is two wolves and a lamb voting on what to have for lunch. Liberty is a well-armed lamb contesting the vote. Benjamin Franklin Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://members.ij.net/mrmazda/partitioningindex.html Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] LILO and switching hard drives
Anthony, This may seem trivial ... but I did it so I know it's possible. I left the second drive with the jumper on master when it should have been slave... Did the same thing you are reporting. James On Mon, 2002-12-23 at 00:06, Anthony wrote: Im having some lilo troubles. I'm trying to switch out a hard drive and replace it with another one. However when I do this, lilo gives me an error on boot L 01 01 01 etc with 01's going on forever down the screen until I hit reboot. The hard drive I'm swapping out (/dev/hdc) doesn't have any Linux stuff on it, and I only use it for storage. Windows is installed on it's own hard drive (/dev/hda) and linux is on it's own hard drive as well (/dev/sda). The MBR is on /dev/hda. So I'm not seeing how switching out my hard drive would affect lilo at all. Ive tried rerunning the lilo command, but doesn't help any. So to get to Linux or Windows, I have to use a bootdisk and then I can see and write to the new hard drive with no problems. Any suggestions on what's wrong or what I need to do to make Lilo work? Thanks, Anthony __ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] lilo question
On Mon, 20 May 2002, Dodd, David J wrote: I had to rebuild my windoz partition on my desktop and the lilo does not point to the proper windoz file. How do I fix this? thanks Hi David, put the Mandrake 8.2 disk 1 into the CDROM and boot the CD. at the install prompt that comes up type rescue and hit ENTER. when things get done loading the routine into memory you'll be presented with a menu. from the menu choose repair/reinstall lilo boot loader. reboot your machine and all should be just fine. -- daRcmaTTeR -- Registered Linux User #186492 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] LILO error message
At 08:46 AM 2/20/2002 +0200, Haim Ashkenazi wrote: even simpler, man lilo.conf (you can find a description of the problem in one of the files in '/usr/share/doc/lilo...'. if I remember correctly the solution is something like that: disk=/dev/sda bios=0x80 disk=/dev/hda bios=0x81 but I could be mistaken (it was a while ago, since I had this problem..) Son of a gun, that worked! Thanks Haim. Encryption isn't just for secrets...
RE: [expert] LILO Problem - Loading Linux EBDA too big
On Tue, 2002-02-19 at 12:45, Jorge A. Pichardo wrote: Yep. I updated the kernel through the Mandrake wizard and it burped until the machine was booted. Anyway, thanks for the clues Braian and BillK! It is up and running again! By the way when I run the boot CD and going to the process of the expert mode choosing the update I got the error fsck failed with exit code 4 or signal 0 when it reaches the security check. I tried to run a series of switches in the LILO in rescue mode to rebuild the device and I didn't work telling me Fatal:open /boot/vmlinuz: no such file or directory. I looked into the /boot and I had to rebuild the symbolic link pointing to the right file for the vmlinuz file and that was it. It worked charmy. Thanks folks yeah...see updating the kernel through Software manager is a definate no..no. That's been a rule of thumb since 8.0 came out. Not quite sure why, but I know, as do you now too, that it does bad things. And yes, I did it too and didn't remember Civileme's warning about doing so until after I'd done it. By then it was too late. the deed had been done. the best way to handle the kernel updates is to just download the packages to your drive and do them that way. -- daRcmaTTeR Registered Linux User 182496 Mandrake 8.2beta1 - 3:05pm up 2:39, 2 users, load average: 0.03, 0.10, 0.05 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
RE: [expert] LILO Problem - Loading Linux EBDA too big
Yep. I updated the kernel through the Mandrake wizard and it burped until the machine was booted. Anyway, thanks for the clues Braian and BillK! It is up and running again! By the way when I run the boot CD and going to the process of the expert mode choosing the update I got the error fsck failed with exit code 4 or signal 0 when it reaches the security check. I tried to run a series of switches in the LILO in rescue mode to rebuild the device and I didn't work telling me Fatal:open /boot/vmlinuz: no such file or directory. I looked into the /boot and I had to rebuild the symbolic link pointing to the right file for the vmlinuz file and that was it. It worked charmy. Thanks folks -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of William Kenworthy Sent: Monday, February 18, 2002 5:23 PM To: Mandrake Expert Subject: Re: [expert] LILO Problem - Loading Linux EBDA too big To add a bit more: when you changed the kernel, lilo is trying to load the kernel using the old boot info and what the obtuse error message is saying is that it doesnt match what it thinks it should be loading. The cure is to read man lilo and use the chroot option to to write the new kernel information to the boot sector whilst mounted in rescue mode. BillK On Tue, 2002-02-19 at 09:04, Brian Parish wrote: Have you upgraded the kernel by any chance? This is usually the scenario that causes this. Anyway, the easiest way out is to boot from the install CD, choose expert mode, choose update, choose no packages to install, then just run through a standard install (very quickly). This should straighten on the chaos in your /boot and get you running again. If it was a kernel upgrade that caused it, note for the future that even though the kernel appears in the security updates list, it should NEVER be installed that way. Instead, download it and do rpm -ivh kernel... so that it gets installed alongside your existing kernel. HTH Brian On Tue, 2002-02-19 at 11:34, Jorge A. Pichardo wrote: Hi all, I posted my problem in the newbies group and didn't get no answer yet. So I posted it here. For some reason this morning appeared a message in my linux box: Loading Linux EBDA too big and the system halts. It is the same everytime I boot it. I tried to rescue it with the mandrake install CD and tried chroot /mnt and all my directory structure seems ok (boot, dev, home,...) now in / then I tried to mount /boot but I had this error can't find boot in /etc/fstab or /etc/mtab I looked into those files and I saw nothing about the /boot and I can't get it booted yet. I read somewhere else that I need to remount the /boot and run sync a couple of times followed by a lilo -v -v as commands. But I have no luck yet. At this point I don't know how to proceed. Any thoughts, recommendations Regards, Jorge Pichardo Victoria - Vancouver British Columbia, Canada Tel: +250-370-5250 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com This message has been 'sanitized'. This means that potentially dangerous content has been rewritten or removed. The following log describes which actions were taken. Sanitizer (start=1014081124): Part (pos=2727): SanitizeFile (filename=unnamed.txt, mimetype=text/plain): Match (rule=2): Enforced policy: accept Part (pos=4603): SanitizeFile (filename=message.footer, mimetype=text/plain): Match (rule=default): Enforced policy: defang Replaced mime type with: application/DEFANGED-8988 Replaced file name with: message_footer.DEFANGED-8988 Total modifications so far: 1 Anomy 0.0.0 : Sanitizer.pm $Id: Sanitizer.pm,v 1.32 2001/10/11 19:27:15 bre Exp $ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] LILO error message
On Tuesday 19 February 2002 11:45 pm, you wrote: /dev/sda is not on the first disk LILO mini-HOWTO http://www.linuxdoc.org/HOWTO/mini/LILO.html -- Hoyt http://www.maximumhoyt.com Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] LILO error message
On Wed, Feb 20, 2002 at 12:11:08AM -0500, Hoyt wrote: On Tuesday 19 February 2002 11:45 pm, you wrote: /dev/sda is not on the first disk LILO mini-HOWTO even simpler, man lilo.conf (you can find a description of the problem in one of the files in '/usr/share/doc/lilo...'. if I remember correctly the solution is something like that: disk=/dev/sda bios=0x80 disk=/dev/hda bios=0x81 but I could be mistaken (it was a while ago, since I had this problem..) Bye -- Haim http://www.linuxdoc.org/HOWTO/mini/LILO.html -- Hoyt http://www.maximumhoyt.com Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] LILO Problem - Loading Linux EBDA too big
Have you upgraded the kernel by any chance? This is usually the scenario that causes this. Anyway, the easiest way out is to boot from the install CD, choose expert mode, choose update, choose no packages to install, then just run through a standard install (very quickly). This should straighten on the chaos in your /boot and get you running again. If it was a kernel upgrade that caused it, note for the future that even though the kernel appears in the security updates list, it should NEVER be installed that way. Instead, download it and do rpm -ivh kernel... so that it gets installed alongside your existing kernel. HTH Brian On Tue, 2002-02-19 at 11:34, Jorge A. Pichardo wrote: Hi all, I posted my problem in the newbies group and didn't get no answer yet. So I posted it here. For some reason this morning appeared a message in my linux box: Loading Linux EBDA too big and the system halts. It is the same everytime I boot it. I tried to rescue it with the mandrake install CD and tried chroot /mnt and all my directory structure seems ok (boot, dev, home,...) now in / then I tried to mount /boot but I had this error can't find boot in /etc/fstab or /etc/mtab I looked into those files and I saw nothing about the /boot and I can't get it booted yet. I read somewhere else that I need to remount the /boot and run sync a couple of times followed by a lilo -v -v as commands. But I have no luck yet. At this point I don't know how to proceed. Any thoughts, recommendations Regards, Jorge Pichardo Victoria - Vancouver British Columbia, Canada Tel: +250-370-5250 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] LILO - Fatal Error (for a friend-rush please?)
Hi, This suggestion will NOT work if your Win2K is installed on an NTFS partition, as there IS NO fdisk in Win2K (and win95 floppy will NOT recognize NTFS drive); You will have to boot into rescue mode (by using the install floppies OR the rescue floppy set you made), and use fixmbr. HTH, David Charles On Sun, 23 Sep 2001, Eric Paynter wrote: On September 23, 2001 01:18 pm, Leif Madsen wrote: Friend of mine recently installed Mandrake 8.0 onto his laptop. He now can't get into his Win2K partition (which is important for school tommorow). This is his current lilo.conf file. The quick and dirty way to get back into windoze (while blowing away LILO for now) is to boot to DOS and rewrite the master boot record. Your windoze recovery disk should have the appropriate files present. Simply run fdisk /mbr from the DOS command line. Then run fdisk and select your windoze partition as active. Then remove your recovery disk and reboot. It should come up with windoze. You can fix LILO later by booting from your madrake install CD. Good luck! -Eric -- arctic bears - email and name services 25 email addresses@yourdomain CA$11.95/month DNS starting at CA$3.49/month - domains from CA$25.95/year for details contact [EMAIL PROTECTED] or visit http://www.arcticbears.com Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] LILO - Fatal Error (for a friend-rush please?)
On September 23, 2001 01:18 pm, Leif Madsen wrote: Friend of mine recently installed Mandrake 8.0 onto his laptop. He now can't get into his Win2K partition (which is important for school tommorow). This is his current lilo.conf file. The quick and dirty way to get back into windoze (while blowing away LILO for now) is to boot to DOS and rewrite the master boot record. Your windoze recovery disk should have the appropriate files present. Simply run fdisk /mbr from the DOS command line. Then run fdisk and select your windoze partition as active. Then remove your recovery disk and reboot. It should come up with windoze. You can fix LILO later by booting from your madrake install CD. Good luck! -Eric -- arctic bears - email and name services 25 email addresses@yourdomain CA$11.95/month DNS starting at CA$3.49/month - domains from CA$25.95/year for details contact [EMAIL PROTECTED] or visit http://www.arcticbears.com Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] LILO - Fatal Error (for a friend-rush please?)
On Sun, 23 Sep 2001 13:32:32 -0700 Eric Paynter [EMAIL PROTECTED] wrote: On September 23, 2001 01:18 pm, Leif Madsen wrote: Friend of mine recently installed Mandrake 8.0 onto his laptop. He now can't get into his Win2K partition (which is important for school tommorow). This is his current lilo.conf file. The quick and dirty way to get back into windoze (while blowing away LILO for now) is to boot to DOS and rewrite the master boot record. Your windoze recovery disk should have the appropriate files present. Simply run fdisk /mbr from the DOS command line. Then run fdisk and select your windoze partition as active. Then remove your recovery disk and reboot. It should come up with windoze. You can fix LILO later by booting from your madrake install CD. NO Do not do that. With the error you are receiving when trying to boot Win2k if fdisk/ MBR is run it will make the system unbootable. Rather, login to linux and as root run /sbin/lilo -u. This will unistall Lilo and restore the previous bootloader, Win2Ks. Charles (-: Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] LILO - Fatal Error (for a friend-rush please?)
First of all, what's with the backslash after message in his lilo.conf? If that's of no help, try removing the table= line in his. Also, is it just me or do you have duplicate Linux entries? Other than that, I can be of no help. Sorry. Best of luck -- Asheesh. On Sun, 23 Sep 2001, Leif Madsen wrote: message\/boot/message What is this? Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo
El Mié 12 Sep 2001 19:58, escribiste: Hi, Yesterday I lost my lilo boot sector, so I had to re-install LM8.0. It installed 6 more menus in it's boot setup. I don't know how to take them out. I read the lilo manual and there's nothing in there to tell you how to take them out. Does anyone here know, and if so, I'd appreciate it if you would share that knowledge with me. Thanks. Guy Edit /etc/lilo.conf as root and remove the sections you don't want. Example of section: image=/boot/vmlinuz label=failsafe root=/dev/hda1 (...) Another example: other=/dev/hda3 label=windows table=/dev/hda Remove the sections you don't want, save lilo.conf, run lilo and reboot to see the chages. (of course, be carefully when removing sections ;-) Salu2 óscar. -- Usuario de Linux Registrado #227443 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo
On Wednesday 12 September 2001 12:58, you wrote: Hi, Yesterday I lost my lilo boot sector, so I had to re-install LM8.0. It installed 6 more menus in it's boot setup. I don't know how to take them out. I read the lilo manual and there's nothing in there to tell you how to take them out. Does anyone here know, and if so, I'd appreciate it if you would share that knowledge with me. Thanks. Guy GET INTERNET ACCESS FROM JUNO! Juno offers FREE or PREMIUM Internet access for less! Join Juno today! For your FREE software, visit: http://dl.www.juno.com/get/tagj. You may edit Lilo in /etc/lilo.conf and 'remove' the entries you do not use. (old ones) -- SedeComp Comunicaciones Internet Solutions MandrakeSoft's VAR and System Integrator mailto:[EMAIL PROTECTED] OpenPGP key available on:http://www.keyserver.net/en/ |--| Current Linux kernel 2.4.8-22mdk uptime: 20 hours 12 minutes. Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Lilo
On Wednesday 12 September 2001 20:10, Oscar wrote: El Mié 12 Sep 2001 19:58, escribiste: Hi, Yesterday I lost my lilo boot sector, so I had to re-install LM8.0. It installed 6 more menus in it's boot setup. I don't know how to take them out. I read the lilo manual and there's nothing in there to tell you how to take them out. Does anyone here know, and if so, I'd appreciate it if you would share that knowledge with me. Thanks. Guy Edit /etc/lilo.conf as root and remove the sections you don't want. Example of section: image=/boot/vmlinuz label=failsafe root=/dev/hda1 (...) Another example: other=/dev/hda3 label=windows table=/dev/hda Remove the sections you don't want, save lilo.conf, run lilo and reboot to see the chages. (of course, be carefully when removing sections ;-) Salu2 óscar. What he said PLUS Losing a boot sector is not a reason to reinstall. Take the install CD and boot, hitting F1 at the splash screen and typing rescue (without the quotes). If you know what your partition that mounts as / is, then it is easy. If not, you get a list of the partitions with fdisk -l /dev/hda and then do a trail and error until you find it with the instructions below and reboots if it fails. (The developers put an autolocator in 8.1 so you don't have to try that any more--nice guys that they are, especially gc) The # is the system prompt--the rest you type. # mount /dev/hda6 /mnt # chroot /mnt # lilo That will rebuild your boot sector. If hda6 isnt the one to mount as / then you get an error message response to the chroot command. Civileme Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] lilo problem?
I'm wondering if you might have to do some drive mapping. My windows install is on hdb, so to get it to boot, I do: other=/dev/hdb1 label=windows table=/dev/hdb map-drive=0x80 to=0x81 map-drive=0x81 to=0x80 This is just a guess, but maybe you can do: image=/boot/vmlinuz label=ic-linux map-drive=0x84 to=0x80 root=/dev/hde6 initrd=/boot/initrd.img append=hdc=ide-scsi ide0=noautotune ide1=noautotune ide2=noautotune It might have to do with restrictions on booting from hde, but I could very well be wrong. :( -- Stephen On Monday 13 August 2001 08:31 am, Lonnie Cumberland wrote: Hello All, How are you doing today? Good I hope. I have an interesting problem with my Lilo that I hope someone might have a solution for. I have Mandrake 7.2 booting from my /dev/sda SCSI drive and also have an UltraDMA 66 drive installed and is accessible as well. Currently my Mandrake 7.2 runs just fine and I have made a clean partition on my /dev/hde6 to install a test copy of Mandrake 8.0 to run the 2.4.x kernel. The install had gone just fine onto the /dev/hde6 partition for the Mandrake 8.0, and I then added the entries to my lilo.conf on my Mandrake 7.2. The problem is that when I try to boot the IC (Mandrake 8.0) entry from lilo, it appears that my old 2.2.17 kernel is booted (even though there is NONE in the /dev/hde6 partition) and then it tries to use the files located on the /dev/hde6 partition from which the kernel cannot locate the required 2.2.17 kernel modules. My confusion is that when I boot IC, lilo hould be trying to boot the 2.4.x kernel from /dev/hde6 and NOT the kernel 2.2.17 from the /dev/sda5 partition. I have included a copy of the LILO.CONF from my Mnadrake 7.2 so that you can take a look at, ok. lilo.conf --- boot=/dev/sda map=/boot/map install=/boot/boot.b vga=normal default=linux keytable=/boot/us.klt lba32 prompt timeout=50 message=/boot/message menu-scheme=wb:bw:wb:bw image=/boot/vmlinuz label=linux root=/dev/sda5 initrd=/boot/initrd.img append= hdc=ide-scsi ide0=noautotune ide1=noautotune ide2=noautotune ide3=noautotune mem=128M read-only image=/boot/vmlinuz label=failsafe root=/dev/sda5 initrd=/boot/initrd.img append= hdc=ide-scsi failsafe read-only other=/dev/fd0 label=floppy unsafe image=/boot/vmlinuz label=ic-linux root=/dev/hde6 initrd=/boot/initrd.img append=hdc=ide-scsi ide0=noautotune ide1=noautotune ide2=noautotune ide3=noautotune read-only - does anyone have any ideas? Want to buy your Pack or Services from MandrakeSoft? Go to http://.mandrakestore.com
Re: [expert] lilo problem?
On Mon, 13 Aug 2001, Lonnie Cumberland wrote: Hello All, How are you doing today? Good I hope. I have an interesting problem with my Lilo that I hope someone might have a solution for. I have Mandrake 7.2 booting from my /dev/sda SCSI drive and also have an UltraDMA 66 drive installed and is accessible as well. Currently my Mandrake 7.2 runs just fine and I have made a clean partition on my /dev/hde6 to install a test copy of Mandrake 8.0 to run the 2.4.x kernel. The install had gone just fine onto the /dev/hde6 partition for the Mandrake 8.0, and I then added the entries to my lilo.conf on my Mandrake 7.2. The problem is that when I try to boot the IC (Mandrake 8.0) entry from lilo, it appears that my old 2.2.17 kernel is booted (even though there is NONE in the /dev/hde6 partition) and then it tries to use the files located on the /dev/hde6 Hello All, How are you doing today? Good I hope. I have an interesting problem with my Lilo that I hope someone might have a solution for. I have Mandrake 7.2 booting from my /dev/sda SCSI drive and also have an UltraDMA 66 drive installed and is accessible as well. Currently my Mandrake 7.2 runs just fine and I have made a clean partition on my /dev/hde6 to install a test copy of Mandrake 8.0 to run the 2.4.x kernel. The install had gone just fine onto the /dev/hde6 partition for the Mandrake 8.0, and I then added the entries to my lilo.conf on my Mandrake 7.2. The problem is that when I try to boot the IC (Mandrake 8.0) entry from lilo, it appears that my old 2.2.17 kernel is booted (even though there is NONE in the /dev/hde6 partition) and then it tries to use the files located on the /dev/hde6 Hello All, How are you doing today? Good I hope. I have an interesting problem with my Lilo that I hope someone might have a solution for. I have Mandrake 7.2 booting from my /dev/sda SCSI drive and also have an UltraDMA 66 drive installed and is accessible as well. Currently my Mandrake 7.2 runs just fine and I have made a clean partition on my /dev/hde6 to install a test copy of Mandrake 8.0 to run the 2.4.x kernel. The install had gone just fine onto the /dev/hde6 partition for the Mandrake 8.0, and I then added the entries to my lilo.conf on my Mandrake 7.2. The problem is that when I try to boot the IC (Mandrake 8.0) entry from lilo, it appears that my old 2.2.17 kernel is booted (even though there is NONE in the /dev/hde6 partition) and then it tries to use the files located on the /dev/hde6 Hello All, How are you doing today? Good I hope. I have an interesting problem with my Lilo that I hope someone might have a solution for. I have Mandrake 7.2 booting from my /dev/sda SCSI drive and also have an UltraDMA 66 drive installed and is accessible as well. Currently my Mandrake 7.2 runs just fine and I have made a clean partition on my /dev/hde6 to install a test copy of Mandrake 8.0 to run the 2.4.x kernel. The install had gone just fine onto the /dev/hde6 partition for the Mandrake 8.0, and I then added the entries to my lilo.conf on my Mandrake 7.2. The problem is that when I try to boot the IC (Mandrake 8.0) entry from lilo, it appears that my old 2.2.17 kernel is booted (even though there is NONE in the /dev/hde6 partition) and then it tries to use the files located on the /dev/hde6 Hello All, How are you doing today? Good I hope. I have an interesting problem with my Lilo that I hope someone might have a solution for. I have Mandrake 7.2 booting from my /dev/sda SCSI drive and also have an UltraDMA 66 drive installed and is accessible as well. Currently my Mandrake 7.2 runs just fine and I have made a clean partition on my /dev/hde6 to install a test copy of Mandrake 8.0 to run the 2.4.x kernel. The install had gone just fine onto the /dev/hde6 partition for the Mandrake 8.0, and I then added the entries to my lilo.conf on my Mandrake 7.2. The problem is that when I try to boot the IC (Mandrake 8.0) entry from lilo, it appears that my old 2.2.17 kernel is booted (even though there is NONE in the /dev/hde6 partition) and then it tries to use the files located on the /dev/hde6 partition from which the kernel cannot locate the required 2.2.17 kernel modules. My confusion is that when I boot IC, lilo hould be trying to boot the 2.4.x kernel from /dev/hde6 and NOT the kernel 2.2.17 from the /dev/sda5 partition. Your first image in the /etc/lilo.conf file is the default that the system will try to boot. In order to choose another image you have to manually use the tab key when the lilo: prompt appears. After you decide which image you want to actually be the default, simply edit the /etc/lilo.conf file to put the corresponding lines in the proper position. -sen I have included a copy of the LILO.CONF from my Mnadrake 7.2 so that you can take a look at, ok. lilo.conf --- boot=/dev/sda
Re: [expert] lilo problem?
Hello, I can select the proper image to boot in the LILO selections, but the problem is that the incorrect vmlinuz is being booted. The vmlinuz pointed to on the SCSI /dev/sda5 is being booted instead of the vmlinuz pointed to on the /dev/hde6 UltraDMA 66 controller. The correct root filesystem is being loaded and setup, but the incorrect kernel. -- Lonnie Quoting Sheldon E. Newhouse [EMAIL PROTECTED]: On Mon, 13 Aug 2001, Lonnie Cumberland wrote: Hello All, How are you doing today? Good I hope. I have an interesting problem with my Lilo that I hope someone might have a solution for. I have Mandrake 7.2 booting from my /dev/sda SCSI drive and also have an UltraDMA 66 drive installed and is accessible as well. Currently my Mandrake 7.2 runs just fine and I have made a clean partition on my /dev/hde6 to install a test copy of Mandrake 8.0 to run the 2.4.x kernel. The install had gone just fine onto the /dev/hde6 partition for the Mandrake 8.0, and I then added the entries to my lilo.conf on my Mandrake 7.2. The problem is that when I try to boot the IC (Mandrake 8.0) entry from lilo, it appears that my old 2.2.17 kernel is booted (even though there is NONE in the /dev/hde6 partition) and then it tries to use the files located on the /dev/hde6 Hello All, How are you doing today? Good I hope. I have an interesting problem with my Lilo that I hope someone might have a solution for. I have Mandrake 7.2 booting from my /dev/sda SCSI drive and also have an UltraDMA 66 drive installed and is accessible as well. Currently my Mandrake 7.2 runs just fine and I have made a clean partition on my /dev/hde6 to install a test copy of Mandrake 8.0 to run the 2.4.x kernel. The install had gone just fine onto the /dev/hde6 partition for the Mandrake 8.0, and I then added the entries to my lilo.conf on my Mandrake 7.2. The problem is that when I try to boot the IC (Mandrake 8.0) entry from lilo, it appears that my old 2.2.17 kernel is booted (even though there is NONE in the /dev/hde6 partition) and then it tries to use the files located on the /dev/hde6 Hello All, How are you doing today? Good I hope. I have an interesting problem with my Lilo that I hope someone might have a solution for. I have Mandrake 7.2 booting from my /dev/sda SCSI drive and also have an UltraDMA 66 drive installed and is accessible as well. Currently my Mandrake 7.2 runs just fine and I have made a clean partition on my /dev/hde6 to install a test copy of Mandrake 8.0 to run the 2.4.x kernel. The install had gone just fine onto the /dev/hde6 partition for the Mandrake 8.0, and I then added the entries to my lilo.conf on my Mandrake 7.2. The problem is that when I try to boot the IC (Mandrake 8.0) entry from lilo, it appears that my old 2.2.17 kernel is booted (even though there is NONE in the /dev/hde6 partition) and then it tries to use the files located on the /dev/hde6 Hello All, How are you doing today? Good I hope. I have an interesting problem with my Lilo that I hope someone might have a solution for. I have Mandrake 7.2 booting from my /dev/sda SCSI drive and also have an UltraDMA 66 drive installed and is accessible as well. Currently my Mandrake 7.2 runs just fine and I have made a clean partition on my /dev/hde6 to install a test copy of Mandrake 8.0 to run the 2.4.x kernel. The install had gone just fine onto the /dev/hde6 partition for the Mandrake 8.0, and I then added the entries to my lilo.conf on my Mandrake 7.2. The problem is that when I try to boot the IC (Mandrake 8.0) entry from lilo, it appears that my old 2.2.17 kernel is booted (even though there is NONE in the /dev/hde6 partition) and then it tries to use the files located on the /dev/hde6 Hello All, How are you doing today? Good I hope. I have an interesting problem with my Lilo that I hope someone might have a solution for. I have Mandrake 7.2 booting from my /dev/sda SCSI drive and also have an UltraDMA 66 drive installed and is accessible as well. Currently my Mandrake 7.2 runs just fine and I have made a clean partition on my /dev/hde6 to install a test copy of Mandrake 8.0 to run the 2.4.x kernel. The install had gone just fine onto the /dev/hde6 partition for the Mandrake 8.0, and I then added the entries to my lilo.conf on my Mandrake 7.2. The problem is that when I try to boot the IC (Mandrake 8.0) entry from lilo, it appears that my old 2.2.17 kernel is booted (even though there is NONE in the /dev/hde6 partition) and then it tries to use the files located on the /dev/hde6 partition from which the kernel cannot locate the required 2.2.17 kernel modules. My confusion is that when I boot IC, lilo hould be trying to boot the 2.4.x kernel from /dev/hde6 and NOT the kernel 2.2.17 from the /dev/sda5 partition. Your first image
Re: [expert] lilo problem?
Ok, you have /boot/vmlinuz as the image for both kernels. You should have the two different images listed separately. Try putting a different image e.g. image=/boot/vmlinuz-new in your /etc/lilo.conf file where /boot/vmlinuz-new is a link to your new kernel image. -sen On Mon, 13 Aug 2001, Lonnie Cumberland wrote: lilo.conf --- boot=/dev/sda map=/boot/map install=/boot/boot.b vga=normal default=linux keytable=/boot/us.klt lba32 prompt timeout=50 message=/boot/message menu-scheme=wb:bw:wb:bw image=/boot/vmlinuz label=linux root=/dev/sda5 initrd=/boot/initrd.img append= hdc=ide-scsi ide0=noautotune ide1=noautotune ide2=noautotune ide3=noautotune mem=128M read-only image=/boot/vmlinuz label=failsafe root=/dev/sda5 initrd=/boot/initrd.img append= hdc=ide-scsi failsafe read-only other=/dev/fd0 label=floppy unsafe image=/boot/vmlinuz label=ic-linux root=/dev/hde6 initrd=/boot/initrd.img append=hdc=ide-scsi ide0=noautotune ide1=noautotune ide2=noautotune ide3=noautotune read-only - Want to buy your Pack or Services from MandrakeSoft? Go to http://.mandrakestore.com
Re: [expert] lilo problem?
--- Lonnie Cumberland [EMAIL PROTECTED] wrote: lilo.conf --- boot=/dev/sda map=/boot/map install=/boot/boot.b vga=normal default=linux keytable=/boot/us.klt lba32 prompt timeout=50 message=/boot/message menu-scheme=wb:bw:wb:bw image=/boot/vmlinuz -- this and label=linux root=/dev/sda5 initrd=/boot/initrd.img append= hdc=ide-scsi ide0=noautotune ide1=noautotune ide2=noautotune ide3=noautotune mem=128M read-only image=/boot/vmlinuz label=failsafe root=/dev/sda5 initrd=/boot/initrd.img append= hdc=ide-scsi failsafe read-only other=/dev/fd0 label=floppy unsafe image=/boot/vmlinuz --- thiis causing the problem label=ic-linux root=/dev/hde6 initrd=/boot/initrd.img append=hdc=ide-scsi ide0=noautotune ide1=noautotune ide2=noautotune ide3=noautotune read-only - copy the MDK8 kernel (vmlinuz-2.4.3-20mdk) from /dev/hde6's /boot directory to the /boot dir of /dev/sda5, then change image=/boot/vmlinuz (with 2nd arrow) to image=/boot/vmlinuz-2.4.3-20mdk. run /sbin/lilo ... make sure no errors encountered, then reboot using image ic-linux. hope that works. does anyone have any ideas? Cheers, Lonnie Lonnie Cumberland OutStep Technologies Incorporated URL: http://www.outstep.com EMAIL: [EMAIL PROTECTED] : [EMAIL PROTECTED] Want to buy your Pack or Services from MandrakeSoft? Go to http://.mandrakestore.com __ Do You Yahoo!? Send instant messages get email alerts with Yahoo! Messenger. http://im.yahoo.com/ Want to buy your Pack or Services from MandrakeSoft? Go to http://.mandrakestore.com
Re: [expert] LILO name
On Mon Jun 04, 2001 at 12:29:28AM -0500, [EMAIL PROTECTED] wrote: LInux LOader Thanks to everyone who responded.. I got it now. =) -- [EMAIL PROTECTED], OpenPGP key available on www.keyserver.net 1024D/FE6F2AFD 88D8 0D23 8D4B 3407 5BD7 66F9 2043 D0E5 FE6F 2AFD - Danen Consulting Serviceswww.danen.net, www.freezer-burn.org - MandrakeSoft, Inc. Security www.linux-mandrake.com Current Linux kernel 2.4.3-20mdk uptime: 1 day 17 hours 31 minutes. PGP signature
Re: [expert] LILO name
Rusty Carruth wrote: Jerry Sternesky [EMAIL PROTECTED] wrote: I think it is as simple as Linux Loader if I recall, it's has been awhile since I thought about it. So a guess would be SI is Solaris Loader and MI could be for minix. Don't know what the 'I' in SILO is for, but: LILO - LInux LOader SILO - Sparc lInux LOader (I'm guessing) Since SILO muddies the waters (should have been SPLO, SLLO or LISP :^), maybe *ILO should have been: Linux Initial LOader Sparc Initial LOader Minix Initial LOader for consistency. I recall reading something about some trademark problems with 'sparc' or something - perhaps a trip to the sparc linux pages would help there... Or that's what I've been understanding since about the 0.xx days (what, 10 years ago! yikes, I'm an old man! ;-) But are you retired yet..? :^) Pierre On Saturday 02 June 2001 19:35, Vincent Danen wrote: Does anyone know what LILO stands for? I thought it meant Linux In Linux Out, but if that's the case, what does SILO or MILO stand for? (if any of the above words are trademarks, well then they are!) rc Rusty Carruth Email: [EMAIL PROTECTED] or [EMAIL PROTECTED] Voice: (480) 345-3621 SnailMail: Schlumberger ATE FAX: (480) 345-8793 7855 S. River Parkway, Suite 116 Ham: N7IKQ @ 146.82+,pl 162.2 Tempe, AZ 85284-1825 ICBM: 33 20' 44N 111 53' 47W
Re: [expert] LILO name
I think it is as simple as Linux Loader if I recall, it's has been awhile since I thought about it. So a guess would be SI is Solaris Loader and MI could be for minix. On Saturday 02 June 2001 19:35, Vincent Danen wrote: Does anyone know what LILO stands for? I thought it meant Linux In Linux Out, but if that's the case, what does SILO or MILO stand for? I don't think SILO stands for Solaris In Linux Out... =) Of course, I'm probably really showing my ignorance here, but I've never bothered to find out before. Now that I'm writing an article on it, I've got a pressing need to figure out what it stands for. Thanks. Content-Type: application/pgp-signature; charset=iso-8859-1; name=Attachment: 1 Content-Transfer-Encoding: 7bit Content-Description:
Re: [expert] LILO name
Vincent Danen wrote: Does anyone know what LILO stands for? I thought it meant Linux In Linux Out, but if that's the case, what does SILO or MILO stand for? I don't think SILO stands for Solaris In Linux Out... =) LInux LOader. -- A fool gives full vent to his anger, but a wise man keeps himself under control.Proverbs 29:11 NKJV Team OS/2 Felix Miata *** http://mrmazda.members.atlantic.net/
Re: [expert] LILO name
On Saturday 02 June 2001 16:35, Vincent Danen wrote: Does anyone know what LILO stands for? I thought it meant Linux In Linux Out, but if that's the case, what does SILO or MILO stand for? I don't think SILO stands for Solaris In Linux Out... =) Of course, I'm probably really showing my ignorance here, but I've never bothered to find out before. Now that I'm writing an article on it, I've got a pressing need to figure out what it stands for. Thanks. Content-Type: application/pgp-signature; charset=iso-8859-1; name=Attachment: 1 Content-Transfer-Encoding: 7bit Content-Description: LInux LOader -- Thank you. - Gary A. Garibaldi Linux-Mandrake 8.0 Registered Linux User: 188550 - Why on earth do people buy old bottles of wine when they can get a fresh one for a quarter of the price? - 8:15pm up 10:40, 2 users, load average: 2.21, 2.58, 2.49
Re: [expert] LILO name
LInux LOader On Sat, 2 Jun 2001, Vincent Danen wrote: Does anyone know what LILO stands for? I thought it meant Linux In Linux Out, but if that's the case, what does SILO or MILO stand for? I don't think SILO stands for Solaris In Linux Out... =) Of course, I'm probably really showing my ignorance here, but I've never bothered to find out before. Now that I'm writing an article on it, I've got a pressing need to figure out what it stands for. Thanks. -- [EMAIL PROTECTED], OpenPGP key available on www.keyserver.net 1024D/FE6F2AFD 88D8 0D23 8D4B 3407 5BD7 66F9 2043 D0E5 FE6F 2AFD - Danen Consulting Serviceswww.danen.net, www.freezer-burn.org - MandrakeSoft, Inc. Security www.linux-mandrake.com Current Linux kernel 2.4.3-20mdk uptime: 0 hours 51 minutes.
Re: [expert] LILO no longer works
This probably won't work. Check what other's say about this (obviously) but i think that / is seperate from the MBR and so formatting / will do nothing for how your machine is(n't) booting. Although when you have exausted the possible, start probing the impossible. What you need is some hardware/harddrive guru to tell you what kind of geometry-of-your-drive info you have to set up explicitly in LILO/GRUB/whatever. Have you posted all the information possible on your hd setup? Should you upgrade your motherboard bios? When you have exausted the possible. dunno :-) j --- Jay DeKing [EMAIL PROTECTED] wrote: Sorry, that didn't work either. I tried it with both LILO and GRUB, with the same results as always. The next step, I guess, is to boot up with the install CD and do an install/update. Since I have most of the programs and data on partitions separate from /, I shouldn't lose too much stuff when it makes me format / itself. Thanks, Jay Charles A Edwards wrote: I'll give you something else to try. Boot your system with a win98 start-up disk and fdisk /MBR. Remove the win98 disk and insert your Mandrake boot disk. Reboot your system. Your system should now boot to Linux before Win rewrites the boot record. Use sbin lilo or grub sh to install the one of your choice, either should now be able to fully install and be operational. Charles (-: Forever never goes beyond tomorrow. -- There is a fine line between 'hobby' and 'mental illness'. __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
Re: [expert] LILO no longer works
Yes, I realize that formatting / won't affect the MBR (especially since / is on hdb), but when I installed Mandrake last time it did give me a working GRUB setup. I'm not sure why the stand-alone GRUB and LILO utilities can't seem to do this, but they obviously are not up to the task for some reason. My motherboard (and everything else in the machine) is only about 6 months old, and I've kept up-to-date on all BIOS and firmware for everything I have, from the system board down to the CD drives, and all devices in between. The thing that really gets me is, the only thing that has changed is the contents of hda. Wait a minute ... that's not entirely true; the partition sizes have changed. hda1 was only 2GB in size before. The partition table was trashed, which is what precipitated the reformatting, and after a lot of mucking about I decided to fdisk the whole drive. I made the whole 30GB a single partition, formatted it, then fdisk'd it into two 15GB partitions and formatted them. Overkill? Sounds like it, but it was apparently necessary. Formatting the partitions individually didn't get the thing working. I've been working on my own hardware for over 10 years, and have never been through such an ordeal except in the bad old days of 20MB Seagate drives. (Harkening back to a recent thread in this group -- the drive that gave me all of this trouble is a Maxtor, six months old. My 30GB WD [hde] performed valiantly and flawlessly though all of this.) Jay John Wolford wrote: This probably won't work. Check what other's say about this (obviously) but i think that / is seperate from the MBR and so formatting / will do nothing for how your machine is(n't) booting. Although when you have exausted the possible, start probing the impossible. What you need is some hardware/harddrive guru to tell you what kind of geometry-of-your-drive info you have to set up explicitly in LILO/GRUB/whatever. Have you posted all the information possible on your hd setup? Should you upgrade your motherboard bios? When you have exausted the possible. dunno :-) j --- Jay DeKing [EMAIL PROTECTED] wrote: Sorry, that didn't work either. I tried it with both LILO and GRUB, with the same results as always. The next step, I guess, is to boot up with the install CD and do an install/update. Since I have most of the programs and data on partitions separate from /, I shouldn't lose too much stuff when it makes me format / itself. -- There is a fine line between 'hobby' and 'mental illness'.
Re: [expert] LILO no longer works
Sorry, that didn't work either. I tried it with both LILO and GRUB, with the same results as always. The next step, I guess, is to boot up with the install CD and do an install/update. Since I have most of the programs and data on partitions separate from /, I shouldn't lose too much stuff when it makes me format / itself. Thanks, Jay Charles A Edwards wrote: I'll give you something else to try. Boot your system with a win98 start-up disk and fdisk /MBR. Remove the win98 disk and insert your Mandrake boot disk. Reboot your system. Your system should now boot to Linux before Win rewrites the boot record. Use sbin lilo or grub sh to install the one of your choice, either should now be able to fully install and be operational. Charles (-: Forever never goes beyond tomorrow. -- There is a fine line between 'hobby' and 'mental illness'.
RE: [expert] LILO no longer works
I'll give you something else to try. Boot your system with a win98 start-up disk and fdisk /MBR. Remove the win98 disk and insert your Mandrake boot disk. Reboot your system. Your system should now boot to Linux before Win rewrites the boot record. Use sbin lilo or grub sh to install the one of your choice, either should now be able to fully install and be operational. Charles (-: Forever never goes beyond tomorrow. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jay DeKing Sent: Friday, May 11, 2001 10:20 PM To: Civileme Cc: [EMAIL PROTECTED] Subject: Re: [expert] LILO no longer works I have had to boot Linux with a floppy ever since I was forced to reformat my Win98 drive (hda1). Before the unfortunate incident which precipitated the reformatting, I had been using grub - very happily. Now, I have gone through grub-install many times since then, which gives me a Stage1 Read Error every time. I have also tried lilo (both graphical and command-line methods) and klilo. Both of them give me screens full of 10 10 10 10 ... ad infinitum. Every time I look for an answer, I am always told the proper method for installing GRUB and/or LILO. While I am thankful for the advice, I have gone through both procedures, carefully, in letter-perfect fashion many, many times, with precisely the same results every time. My fstab, lilo.conf, and menu.lst have not changed since I had to reformat; they should not need to, since the drives are configured exactly the same way as they were when GRUB worked. The last time somebody asked me to post my menu.lst file so they could see if anything was wrong with it, I never heard another word about it. So, either there was nothing interesting about it or I was forgotten. Imagine my pleasure when I saw a new idea (Civileme's - see below)! I tried it, and ... guess what? A screen full of 10 10 10 10 ... ad infinitum. Sigh. So, here is my menu.lst file again: timeout 5 color black/cyan yellow/cyan i18n (hd1,0)/boot/grub/messages keytable (hd1,0)/boot/us.klt altconfigfile (hd1,0)/boot/grub/menu.once default 4 title linux kernel (hd1,0)/boot/vmlinuz-secure root=/dev/hdb1 hdg=ide-scsi hdd=ide-floppy vga=788 title linux-up kernel (hd1,0)/boot/vmlinuz root=/dev/hdb1 hdg=ide-scsi hdd=ide-floppy title failsafe kernel (hd1,0)/boot/vmlinuz root=/dev/hdb1 hdg=ide-scsi hdd=ide-floppy failsafe title hack kernel (hd1,0)/boot/vmlinuz-hack root=/dev/hdb1 hdg=ide-scsi hdd=ide-floppy vga=788 initrd (hd1,0)/boot/initrd-hack.img title windows root (hd0,0) map (0x81) (0x80) map (0x80) (0x81) makeactive chainloader +1 And my lilo.conf: boot = /dev/hda map = /boot/map timeout = 200 prompt vga = normal read-only image = /boot/vmlinuz-secure label = linux append = hdg=ide-scsi hdd=ide-floppy root = /dev/hdb1 image = /boot/vmlinuz label = linux-up append = hdg=ide-scsi hdd=ide-floppy root = /dev/hdb1 image = /boot/vmlinuz label = failsafe append = hdg=ide-scsi hdd=ide-floppy failsafe root = /dev/hdb1 image = /boot/vmlinuz-hack label = hack append = hdg=ide-scsi hdd=ide-floppy root = /dev/hdb1 other = /dev/hda1 label = windows table=/dev/hda Oh great Linux masters, can you help ? Thanks Jay DeKing Civileme wrote: If you do NOT have reiser, then the mbr is probably damaged with respect to the new Mobo. To fix this use the 7.1 install CD, hit F1, type rescue without the quotes, and ... when the system comes up # mount /dev/hdax /mnt ## where x is the number for your / partition # chroot /mnt # /sbin/lilo EVEN if you were using grub, which you obviously were not. You should then be bootable from the hard disk, take out the CD and type # reboot Civileme -- There is a fine line between 'hobby' and 'mental illness'.
Re: [expert] LILO no longer works
I have had to boot Linux with a floppy ever since I was forced to reformat my Win98 drive (hda1). Before the unfortunate incident which precipitated the reformatting, I had been using grub - very happily. Now, I have gone through grub-install many times since then, which gives me a Stage1 Read Error every time. I have also tried lilo (both graphical and command-line methods) and klilo. Both of them give me screens full of 10 10 10 10 ... ad infinitum. Every time I look for an answer, I am always told the proper method for installing GRUB and/or LILO. While I am thankful for the advice, I have gone through both procedures, carefully, in letter-perfect fashion many, many times, with precisely the same results every time. My fstab, lilo.conf, and menu.lst have not changed since I had to reformat; they should not need to, since the drives are configured exactly the same way as they were when GRUB worked. The last time somebody asked me to post my menu.lst file so they could see if anything was wrong with it, I never heard another word about it. So, either there was nothing interesting about it or I was forgotten. Imagine my pleasure when I saw a new idea (Civileme's - see below)! I tried it, and ... guess what? A screen full of 10 10 10 10 ... ad infinitum. Sigh. So, here is my menu.lst file again: timeout 5 color black/cyan yellow/cyan i18n (hd1,0)/boot/grub/messages keytable (hd1,0)/boot/us.klt altconfigfile (hd1,0)/boot/grub/menu.once default 4 title linux kernel (hd1,0)/boot/vmlinuz-secure root=/dev/hdb1 hdg=ide-scsi hdd=ide-floppy vga=788 title linux-up kernel (hd1,0)/boot/vmlinuz root=/dev/hdb1 hdg=ide-scsi hdd=ide-floppy title failsafe kernel (hd1,0)/boot/vmlinuz root=/dev/hdb1 hdg=ide-scsi hdd=ide-floppy failsafe title hack kernel (hd1,0)/boot/vmlinuz-hack root=/dev/hdb1 hdg=ide-scsi hdd=ide-floppy vga=788 initrd (hd1,0)/boot/initrd-hack.img title windows root (hd0,0) map (0x81) (0x80) map (0x80) (0x81) makeactive chainloader +1 And my lilo.conf: boot = /dev/hda map = /boot/map timeout = 200 prompt vga = normal read-only image = /boot/vmlinuz-secure label = linux append = hdg=ide-scsi hdd=ide-floppy root = /dev/hdb1 image = /boot/vmlinuz label = linux-up append = hdg=ide-scsi hdd=ide-floppy root = /dev/hdb1 image = /boot/vmlinuz label = failsafe append = hdg=ide-scsi hdd=ide-floppy failsafe root = /dev/hdb1 image = /boot/vmlinuz-hack label = hack append = hdg=ide-scsi hdd=ide-floppy root = /dev/hdb1 other = /dev/hda1 label = windows table=/dev/hda Oh great Linux masters, can you help ? Thanks Jay DeKing Civileme wrote: If you do NOT have reiser, then the mbr is probably damaged with respect to the new Mobo. To fix this use the 7.1 install CD, hit F1, type rescue without the quotes, and ... when the system comes up # mount /dev/hdax /mnt ## where x is the number for your / partition # chroot /mnt # /sbin/lilo EVEN if you were using grub, which you obviously were not. You should then be bootable from the hard disk, take out the CD and type # reboot Civileme -- There is a fine line between 'hobby' and 'mental illness'.
Re: [expert] LILO no longer works
Bruce Endries wrote: Hello everyone; I have a LM 7.1 system on a which the motherboard had to be replaced. The system worked fine. While the motherboard was out, I put the (IDE) drive into another system (LM8) as a secondary drive. The primary drive in this system is SCSI. I was able to access the IDE drive okay after putting the proper entries into fstab and mounting it. Then I get the new motherboard back, and I put the drive back with it again, and it won't boot. I get LI.. the first two letters of LILO, and that's it. I thought it might be the manner the motherboard was addressing the drive, so I tried LBA, Large, CHS and Auto, and always get the same result. Anyone have any ideas? Boot from floppy and rerun /sbin/lilo See also http://sdb.suse.de/en/sdb/html/kgw_lilo_errmsg.html Pierre Thank you in advance for any light you can shed on this problem. I really don't want to re-install the system if I don't have to. Bruce Endries Bruce Endries Consulting (607) 433-2677 [EMAIL PROTECTED] -- Support Linux development: http://www.linux-mandrake.com/donations/ Last reboot reason: 01/03/27: winter storm 6hr power outage
Re: [expert] LILO no longer works
This was answered on the Caldera list earlier this month(maybe). It's a drive geometry error(can't see or recognize the drive), the solution was to try the linear option in lilo to fix it. Randy Donohoe Mediocrity sucks. - Original Message - From: Bruce Endries [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, May 10, 2001 8:38 PM Subject: [expert] LILO no longer works Hello everyone; I have a LM 7.1 system on a which the motherboard had to be replaced. The system worked fine. While the motherboard was out, I put the (IDE) drive into another system (LM8) as a secondary drive. The primary drive in this system is SCSI. I was able to access the IDE drive okay after putting the proper entries into fstab and mounting it. Then I get the new motherboard back, and I put the drive back with it again, and it won't boot. I get LI.. the first two letters of LILO, and that's it. I thought it might be the manner the motherboard was addressing the drive, so I tried LBA, Large, CHS and Auto, and always get the same result. Anyone have any ideas? Thank you in advance for any light you can shed on this problem. I really don't want to re-install the system if I don't have to. Bruce Endries Bruce Endries Consulting (607) 433-2677 [EMAIL PROTECTED]
Re: [expert] LILO no longer works
On Thursday 10 May 2001 17:38, Bruce Endries wrote: Hello everyone; I have a LM 7.1 system on a which the motherboard had to be replaced. The system worked fine. While the motherboard was out, I put the (IDE) drive into another system (LM8) as a secondary drive. The primary drive in this system is SCSI. I was able to access the IDE drive okay after putting the proper entries into fstab and mounting it. Then I get the new motherboard back, and I put the drive back with it again, and it won't boot. I get LI.. the first two letters of LILO, and that's it. I thought it might be the manner the motherboard was addressing the drive, so I tried LBA, Large, CHS and Auto, and always get the same result. Anyone have any ideas? Thank you in advance for any light you can shed on this problem. I really don't want to re-install the system if I don't have to. Bruce Endries Bruce Endries Consulting (607) 433-2677 [EMAIL PROTECTED] Did you have reiser partitions on the drive? In particular was / reiser? If so, you must now update to 8.0 and then back up your data to ext2 and reinstall 7.1. If your data is mostly in /home, then I think it will be best to actually install 8.0 then back it up Alternatively you can use your other system for the backup. If you do NOT have reiser, then the mbr is probably damaged with respect to the new Mobo. To fix this use the 7.1 install CD, hit F1, type rescue without the quotes, and ... when the system comes up # mount /dev/hdax /mnt ## where x is the number for your / partition # chroot /mnt # /sbin/lilo EVEN if you were using grub, which you obviously were not. You should then be bootable from the hard disk, take out the CD and type # reboot Civileme
Re: [expert] LILO problem with LM7.2
[EMAIL PROTECTED] wrote: I just istalled LM7.2 on my new drive (20GB). It's got a 13GB Win98 partition and the rest for LM7.2. The install goes fine, but LILO doesn't install. I tried with every distro I own and the same thing happens, LILO refuses to install. In order to get the thing to boot, I installed FreeBSD 4.0, and it's bootloader installed. I re-installed LM7.2 over BSD, but again, LILO won't install. The BSD loader is still there. Any clues why? As Al Baker mentioned, Windows systems install on the first available partition on the first hard drive. This is cast in stone. In addition, MS FDISK will only create one Primary partition and an Extended partition (with multiple logical drives) whereas the Linux system can create up to 4 primary partitions (the limit for a hard drive). Lilo must be installed within the first 1024 cylinders of the drive being booted, or it will not boot/install properly. A workaround is to create a small primary partition (10 MB) at the start of the drive which will be mounted as /boot. This will ensure that LILO is within the first 1024 cylinders. This works even if it is being installed on a second or third drive. If it is on the first drive, it will be labeled as C. I am using Norton's GDISK to do this. Next, a primary partition of a suitable size is defined for Windows. This partition will be labeled as D. The first primary must then be marked as hidden. This will force the second partition to be labeled as C so Windows can be installed on it. It should be also set to active. You can then define a partition for swap (128 MB?) and one for the balance of the Linux system which will be mounted as root. Install Windows first. It will automatically go to the default C partition. Once Windows is configured, you can proceed to install Mandrake Linux. When the install gets to the disk partitioning question, choose diskdrake. It will display the various partitions including the hidden one. Click on EXT2 and then on the first small partition, and set its mount point as /boot. On a second or third drive, there should be only 3 partitions. The first at the drive start will be the small one which will be mounted as /boot. In either case, the remaining partitions can be set to swap or / as required. Note that GDISK leaves the default format of these partitions a FAT, so you will have to click either SWAP or EXT2 before clicking on a partition to set a mount point. Diskdrake also will detect the Windows partition, and will set its mount point as /mnt/windows. When the install gets to the question of installing LILO, (or GRUB), have it installed on the master boot record (MBR) of the first drive - hda. Mandrake automatically detects Windows and includes it in its menu. I am currently configuring a system to use Win98, LM7.2 and BeOS. I used Nortons GDISK running on a Win98 system floppy to configure a 10 GB hard drive as follows: P1 - 13 MB mount as /boot P2 - 2 GB Windows 98 EXT2 L1 - 2 GB for BeOS L2 - 133 MB Swap L3 - 5.1 GB mount as root I can start either Windows or LM7.2 at boot time, and am going to install BeOS next. BeOS has a nice boot loader and I may use it to control the system startup. Hope this helps... Tom. Tom Cada Great Lakes Systems
Re: [expert] LILO problem with LM7.2
I believe Windows likes to be the first partition on the drive, and then you have to set LILO to the MBR (master boot record). I think FreeBSD defaults it's loader to the master boot record as well. --- [EMAIL PROTECTED] wrote: I just istalled LM7.2 on my new drive (20GB). It's got a 13GB Win98 partition and the rest for LM7.2. The install goes fine, but LILO doesn't install. I tried with every distro I own and the same thing happens, LILO refuses to install. In order to get the thing to boot, I installed FreeBSD 4.0, and it's bootloader installed. I re-installed LM7.2 over BSD, but again, LILO won't install. The BSD loader is still there. Any clues why? __ Do You Yahoo!? Yahoo! Auctions - Buy the things you want at great prices. http://auctions.yahoo.com/
Re: [expert] lilo help
Bug Hunter wrote: try going into your bios and enabling LBA for the disk drive mode It's my experience that doing that will only 'take' as long as the drive is empty, ie there are no partitions. Which is very sensible. You will have to copy all the partitions off to another drive (with Partition Magic) before you can set that drive to LBA. Then copy them back again. Bootable Linux partitions now may no longer boot, which is fixed by chrooting from a runniung Linux to the mounted bad partition to run /sbin/lilo. -- Regards, Ron. [au]
RE: [expert] lilo help
Lilo will not boot my system from the hd. Although I haven't tried booting from hd for some time, I believe the error is the 01 01 01 scrolling to fill the screens. Here is my lilo.conf file too this is really bugging me as I want to try out different kernels and the such, and the floppy boot thing has to go. [root /home/brian] cat /etc/lilo.conf default=linux boot=/dev/hda read-only prompt timeout=150 vga=normal image=/boot/vmlinuz-2.2.17-21mdk root=/dev/hdc11 label=linux append=" hdd=ide-scsi hdb=ide-floppy" image=/boot/vmlinuz-2.2.17-21mdk root=/dev/hdc11 label=failsafe append=" hdd=ide-scsi hdb=ide-floppy failsafe" image=/boot/vmlinuz-2.2.18-8mdk root=/dev/hdc11 label=2218-8 append=" hdd=ide-scsi hdb=ide-floppy" image=/boot/vmlinuz-2.4.0-5mdk root=/dev/hdc11 label=240-5 append=" hdd=ide-scsi hdb=ide-floppy" other=/dev/hda1 label=Windows table=/dev/hda other=/dev/fd0 label=floppy table=/dev/hda -Original Message- From: Milnes Terry SSgt 52LSS/LGLOE [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 13, 2001 12:33 AM To: [EMAIL PROTECTED] Cc: Expert Linux Mandrake (E-mail) Subject: RE: [expert] lilo help Here is the gist I get from reading the LILO README. Warning 0x82 is saying that Hard Drive Primary Slave has cylinders larger than the magical 1024 limit. This does not mean that you can not use LILO. More than likely your /etc/lilo.conf file has a line that reads LINEAR. What this does when you run /sbin/lilo is it checks the HDD "capabilities"(?) and then writes out the map file. LILO then uses this map file to boot the system. LILO does not have a clue as to what your HDD looks like so this map file tells it what it looks like and where to find the information to boot. Does LILO work at all? What is the error that you are getting? Each letter at the boot prompt represents a different step in the boot process. I.e. if LILO is stopping with LI then the second stage of the boot is finished, but the map file is wrong. That's just my two cents. Hopefully it can help you. -Original Message- From: Christian A Strmmen [Number1/NumeroUno] [mailto:[EMAIL PROTECTED]] Sent: Monday, February 12, 2001 7:14 PM To: [EMAIL PROTECTED] Subject:Re: [expert] lilo help On Monday 12 February 2001 18:24, you wrote: When I try to run lilo on my desktop I get the following errors: Which has left me with having to boot from floppy. Any help so I can boot from hd again appreciated [root ~] lilo Warning: BIOS drive 0x82 may not be accessible Warning: BIOS drive 0x82 may not be accessible Warning: BIOS drive 0x82 may not be accessible Added linux * Warning: BIOS drive 0x82 may not be accessible Added failsafe Warning: BIOS drive 0x82 may not be accessible Added 2218-8 Warning: BIOS drive 0x82 may not be accessible Added 240-5 Added Windows Fatal: Partition entry not found. These "Warnings" I get too when running lilo after getting my new computer about 5 months ago. I boot from a scsi disk, and I have to go into the bios, disable the ide-controllers, restart and login again, run lilo, reboot, enter the bios, enable the ide-controllers, and then reboot... If I run lilo while my ide controllers are active I get the warnings you describe and lilo doesn't work anymore.. -- \ Christian A Strmmen / \ Number1/NumeroUno @ Undernet - Email: [EMAIL PROTECTED] / \ Web: www.realityx.net - Cell: +47 911 43 948 / Live your life by your dreams, not by the limits of reality...
RE: [expert] lilo help
try going into your bios and enabling LBA for the disk drive mode On Tue, 13 Feb 2001, Klar Brian D Contr MSG SICN wrote: Lilo will not boot my system from the hd. Although I haven't tried booting from hd for some time, I believe the error is the 01 01 01 scrolling to fill the screens. Here is my lilo.conf file too this is really bugging me as I want to try out different kernels and the such, and the floppy boot thing has to go.
