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
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 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
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
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/hd, 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 \/ |__ __|
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
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
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
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 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 -- 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/ ~/.kde/share/apps/ ~Backup/.kde/share/config/ ~/.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 like to avoid the sort of problems I've had thi
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
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 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. > 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- > label=Mandrake_8.2 > root=/dev/hdf1 > initrd=/boot/initrd- > 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
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 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
-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
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/hd, 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
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. 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- label=Mandrake_8.2 root=/dev/hdf1 initrd=/boot/initrd- 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 | Home-Page: h
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/ of=bootsector.raw bs=512 count=1 > Will do that before attempting anything drastic > If you need to recover your old bootsector - use: > dd if=bootsector.raw of=/dev/ > > /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/
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/ of=bootsector.raw bs=512 count=1 If you need to recover your old bootsector - use: dd if=bootsector.raw of=/dev/ 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. > > 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
-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 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
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
-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. 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: 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
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
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
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 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: [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 > > 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 > 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: > 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 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 itI 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: 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: 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 > > 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 itI 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: [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 > > 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 itI 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: [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. <> 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 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
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
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Anne Wilson wrote on Sun, Mar 09, 2003 at 12:01:33PM + : > > > map-drive=0x80 to=0x81 > > > map-drive=0x81 to=0x80 > But windows is on hde1, which *is* my first hdd. And don't the two lines > contradict each other? No, the format is map-drive=PHYSICAL to=VIRTUAL Blue skies... Todd - -- MandrakeSoft USA http://www.mandrakesoft.com cat /boot/vmlinuz > /dev/dsp #for great justice Mandrake Cooker Devel Version, Kernel 2.4.21-0.12mdk -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+bCHglp7v05cW2woRAt48AKDGJZxb2dtZAj9TIpojOQqWHbL35gCgyBPx wUysO4udvUxzh+iNJ/48HQc= =NSFi -END PGP SIGNATURE- 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= 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= Maps BIOS calls for the specified drive to the device code spec- ified on the next line as to=. 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 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
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
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
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 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
[expert] Lilo conf lines
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 -- Registered Linux User No.293302 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
