Re: lilo trouble
(following up on myself and on an ancient posting, too. Just for the sake of completeness and the search-egines in case someone else experiences such a problem) On Fri, 22 Jun 2001 00:06:24 +0200, Robert Waldner writes: >I have a machine with a large IDE-disk (hda) and a smaller, but also > faster SCSI-disk (sda). So the system resides on SCSI, bulk data on > IDE. So far, so good. But I can´t, for whatever reason, just boot > completely from the SCSI-disk, so I installed the MBR on the IDE one. > >boot=/dev/hda >root=/dev/sda7 > >There is a small /boot-partition on sda1, also. <...> >When I try to boot from the disk, all I get after the lilo-prompt is > Error 0x01 > Unable to load Linux > Error 0x01 > I´ve given the problem a new shot and, lo! behold!, got it. There was a "compact"-line in lilo.conf, which works with kernel 2.2.18 but *not* 2.2.19 in that setup. Don´t ask me why, but that did it. >From lilo.conf(5) I´d not guessed that that could pose any problem when just upgrading the kernel. compact Tries to merge read requests for adjacent sectors into a single read request. This drastically reduces load time and keeps the map smaller. Using `compact' is especially recommended when booting from a floppy disk. cheers, &rw -- -- Debating unix flavors in the context of anything Microsoft -- is like talking about which ice cream flavor tastes least -- like sawdust with turpentine sauce. Joe Zeff, asr pgpxX0zq0Y9Mz.pgp Description: PGP signature
Re: lilo trouble
On Fri, Jun 22, 2001 at 12:06:24AM +0200, Robert Waldner wrote: > > Hi! > > I have a machine with a large IDE-disk (hda) and a smaller, but also > faster SCSI-disk (sda). So the system resides on SCSI, bulk data on > IDE. So far, so good. But I can´t, for whatever reason, just boot > completely from the SCSI-disk, so I installed the MBR on the IDE one. > > boot=/dev/hda > root=/dev/sda7 > > There is a small /boot-partition on sda1, also. > > This setup worked flawlessly since 09/2000 until today I changed a > flaky network card and needed to upgrade from kernel 2.2.18 to 2.2.19 > to get the via-rhine-module in a recent version. > > I installed (am I already grinding on your nerves? I know this is > rather long, but I can´t figure out how to keep it shorter and yet > include all vital information) kernel-image 2.2.19-2, although I > decided to write lilo.conf and run lilo myself, JIC it would bitch > about the SCSI/IDE-setup otherwise. > > When I try to boot from the disk, all I get after the lilo-prompt is >Error 0x01 >Unable to load Linux >Error 0x01 > > > I googled up the following advice: > - re-recreate the map-file > - check BIOS-settings > - disable internal CPU-cache > - make conservative DRAM-settings > - make the IDE-drive known to the BIOS > - attach the IDE-drive as master, without any slave > - upgrade BIOS > - run lilo with append - pci=nobios > pci=conf1 > pci=conf2 > > did/checked all that, didn´t help. > > But best is the explanation for lilo-error 0x01: > "`Illegal command''. This shouldn't happen, but if it does, it may > indicate an attempt to access a disk which is not supported by the > BIOS." > > Then why did it work flawlessly until today? I´m out of clues, here, > definitely. > > Can´t run the old kernel also. I´m just that: >< short now of > crunching the whole setup and getting a SCSI-controller with BIOS so I > can (maybe?) boot directly from SCSI, but somehow that doesn´t seem > right. > > So, any hints for a clueless? > I am not an expert but you could try the following: Edit the lilo.conf file and put in the following disk=/dev/sda bios=0x80 # boot=/dev/hda (get rid of this and change to the following) boot=/dev/sda root=/dev/sda7 install=/boot/boot.b map=/boot/map ... then the rest of your lilo.conf ... You could also experiment with the linear option - it may be needed. Basically IIRC the first line tells lilo the geometry of the boot disk (dev/sda7) and the second line tells it to treat the sda7 device as the first bios hard disk (0x80) and boot from this. Then rerun lilo Hopefully, this will allow you to install lilo on your scsi disk and allow you to boot from it. Good luck. ps I don't have any scsi devices so not sure. Mark.
lilo trouble
Hi! I have a machine with a large IDE-disk (hda) and a smaller, but also faster SCSI-disk (sda). So the system resides on SCSI, bulk data on IDE. So far, so good. But I can´t, for whatever reason, just boot completely from the SCSI-disk, so I installed the MBR on the IDE one. boot=/dev/hda root=/dev/sda7 There is a small /boot-partition on sda1, also. This setup worked flawlessly since 09/2000 until today I changed a flaky network card and needed to upgrade from kernel 2.2.18 to 2.2.19 to get the via-rhine-module in a recent version. I installed (am I already grinding on your nerves? I know this is rather long, but I can´t figure out how to keep it shorter and yet include all vital information) kernel-image 2.2.19-2, although I decided to write lilo.conf and run lilo myself, JIC it would bitch about the SCSI/IDE-setup otherwise. When I try to boot from the disk, all I get after the lilo-prompt is Error 0x01 Unable to load Linux Error 0x01 I googled up the following advice: - re-recreate the map-file - check BIOS-settings - disable internal CPU-cache - make conservative DRAM-settings - make the IDE-drive known to the BIOS - attach the IDE-drive as master, without any slave - upgrade BIOS - run lilo with append - pci=nobios pci=conf1 pci=conf2 did/checked all that, didn´t help. But best is the explanation for lilo-error 0x01: "`Illegal command''. This shouldn't happen, but if it does, it may indicate an attempt to access a disk which is not supported by the BIOS." Then why did it work flawlessly until today? I´m out of clues, here, definitely. Can´t run the old kernel also. I´m just that: >< short now of crunching the whole setup and getting a SCSI-controller with BIOS so I can (maybe?) boot directly from SCSI, but somehow that doesn´t seem right. So, any hints for a clueless? cheers#tia, &rw -- -- A classic is something that everyone wants -- to have read and nobody wants to read. -- Mark Twain pgp4jnzs9AVqt.pgp Description: PGP signature
Re: LILO trouble (still there...)
Hi, I finaly found some time to take a second look at my LILO trouble. Thanx for all your suggestions they have taken me one more step along the way. First of all the Geometry settings was the same in the BIOS as linux reported. > I made the same mistake that Joshua and Hakan made. The READMEFIRST file > in /usr/doc/lilo gives two possible fixes: > > - In linux you can remove lilo from the master boot record with: > lilo -U > > - In MSDOS you can remove lilo by: > fdisk /mbr > > The lilo -U fix did not work for me since I had already re-partitioned. > fdisk /mbr was successful. The same goes for me. I successfully uninstalled lilo with fdisk /mbr, but when I reinstalled it I was back where I started. But now at least I can boot my system in msdos mode and the turn to linux with loadlin, and I can live with that setup, even if I found LILO interface smooter. And thanx again for all your grate support. Thanx to you I once again have a usable system. > > Mike > > > > On Wed, 14 Aug 1996, Joshua Stockwell wrote: > > > > > I had this exact same setup. Slackware on the slave disk and msdos on > > the other master disk. And I just recently upgraded to Debian and ran > > into the exact same problem. Silly me to forget to uninstall lilo > > first! The reason your boot is hanging is that it is looking for the > > old lilo that doesnt't exist anymore. You need to re-install lilo. If > > your lilo.conf is setup right just type "lilo" and it should re-write > > the MBR so you'll be able to boot normally. Lilo should be on your > > linux partition, not your dos partition. Good luck! > > > > - Josh Stockwell > > > > Hakan wrote: > > >>> I have a 486 on which I untill recently had MSDos and Slackware > > >>> installed > on > > >>> two diffrent harddisks, with LILO installed in the master boot block of > > >>> t > he > > >>> msdos harddisk allowing me to select between the two operating systems. > > >>> T > his > > >>> worked just fine. > > > > >>> Now, I decided to convert into Debian (I just love it's package > > >>> system), > so I > > >>> through out the Slackware stuff and installed the three disks base > > >>> system > . I > > >>> had to install LILO by hand because the instalation package tried to > > >>> inst > all > > >>> it on the linx partion, which is the second partion on the secon > > >>> harddisk > > >>> (/dev/hdb2). I placed it on (/dev/hda). Then I rebootet. Then insted of > > >>> t > he > > >>> LILO text that is supposed to show up when LILO loads I only got "L" > > >>> foll > owd > > >>> by "04" repeated in what seemsed to infinity. > > > > >>> I have tried bothe my old Slackware lilo configuration file, the new > > >>> crea > ted > > >>> by Debian. I have tried both the lilo version that came with Debian and > > >>> t > he > > >>> old one used by Slackware. I have tried having both the MSDos hd and > > >>> the > Linux > > >>> HD as the first HD. And Gud knows what else, but the result is just the > > >>> s > ame. > > >>> What am I doing wrong? > > > > >>> I have temporarity solved the problem by using a MSDos boot disk with a > > >>> m > enu > > >>> that allows me to either run the startup files from my HD after load > > >>> MSDO > S > > >>> from the floppy, or execute loadlin to load a linux kernerel from my > > >>> msdo > s HD > > >>> and mount the root system. And this works acceptable. But it is not a > > >>> dec > ent > > >>> solution. And since LILO worked with Slackware, I see no reason for it > > >>> no > t to > > >>> work with Debian. Any sugestions will be appricialed. Thanx. > > > > > > >
Re: LILO trouble
I made the same mistake that Joshua and Hakan made. The READMEFIRST file in /usr/doc/lilo gives two possible fixes: - In linux you can remove lilo from the master boot record with: lilo -U - In MSDOS you can remove lilo by: fdisk /mbr The lilo -U fix did not work for me since I had already re-partitioned. fdisk /mbr was successful. Mike On Wed, 14 Aug 1996, Joshua Stockwell wrote: > > I had this exact same setup. Slackware on the slave disk and msdos on > the other master disk. And I just recently upgraded to Debian and ran > into the exact same problem. Silly me to forget to uninstall lilo > first! The reason your boot is hanging is that it is looking for the > old lilo that doesnt't exist anymore. You need to re-install lilo. If > your lilo.conf is setup right just type "lilo" and it should re-write > the MBR so you'll be able to boot normally. Lilo should be on your > linux partition, not your dos partition. Good luck! > > - Josh Stockwell > > Hakan wrote: > >>> I have a 486 on which I untill recently had MSDos and Slackware installed > >>> on > >>> two diffrent harddisks, with LILO installed in the master boot block of > >>> the > >>> msdos harddisk allowing me to select between the two operating systems. > >>> This > >>> worked just fine. > > >>> Now, I decided to convert into Debian (I just love it's package system), > >>> so I > >>> through out the Slackware stuff and installed the three disks base > >>> system. I > >>> had to install LILO by hand because the instalation package tried to > >>> install > >>> it on the linx partion, which is the second partion on the secon harddisk > >>> (/dev/hdb2). I placed it on (/dev/hda). Then I rebootet. Then insted of > >>> the > >>> LILO text that is supposed to show up when LILO loads I only got "L" > >>> followd > >>> by "04" repeated in what seemsed to infinity. > > >>> I have tried bothe my old Slackware lilo configuration file, the new > >>> created > >>> by Debian. I have tried both the lilo version that came with Debian and > >>> the > >>> old one used by Slackware. I have tried having both the MSDos hd and the > >>> Linux > >>> HD as the first HD. And Gud knows what else, but the result is just the > >>> same. > >>> What am I doing wrong? > > >>> I have temporarity solved the problem by using a MSDos boot disk with a > >>> menu > >>> that allows me to either run the startup files from my HD after load MSDOS > >>> from the floppy, or execute loadlin to load a linux kernerel from my > >>> msdos HD > >>> and mount the root system. And this works acceptable. But it is not a > >>> decent > >>> solution. And since LILO worked with Slackware, I see no reason for it > >>> not to > >>> work with Debian. Any sugestions will be appricialed. Thanx. > > >
Re: LILO trouble
I had this exact same setup. Slackware on the slave disk and msdos on the other master disk. And I just recently upgraded to Debian and ran into the exact same problem. Silly me to forget to uninstall lilo first! The reason your boot is hanging is that it is looking for the old lilo that doesnt't exist anymore. You need to re-install lilo. If your lilo.conf is setup right just type "lilo" and it should re-write the MBR so you'll be able to boot normally. Lilo should be on your linux partition, not your dos partition. Good luck! - Josh Stockwell Hakan wrote: >>> I have a 486 on which I untill recently had MSDos and Slackware installed >>> on >>> two diffrent harddisks, with LILO installed in the master boot block of the >>> msdos harddisk allowing me to select between the two operating systems. >>> This >>> worked just fine. >>> Now, I decided to convert into Debian (I just love it's package system), so >>> I >>> through out the Slackware stuff and installed the three disks base system. I >>> had to install LILO by hand because the instalation package tried to install >>> it on the linx partion, which is the second partion on the secon harddisk >>> (/dev/hdb2). I placed it on (/dev/hda). Then I rebootet. Then insted of the >>> LILO text that is supposed to show up when LILO loads I only got "L" followd >>> by "04" repeated in what seemsed to infinity. >>> I have tried bothe my old Slackware lilo configuration file, the new >>> created >>> by Debian. I have tried both the lilo version that came with Debian and the >>> old one used by Slackware. I have tried having both the MSDos hd and the >>> Linux >>> HD as the first HD. And Gud knows what else, but the result is just the >>> same. >>> What am I doing wrong? >>> I have temporarity solved the problem by using a MSDos boot disk with a >>> menu >>> that allows me to either run the startup files from my HD after load MSDOS >>> from the floppy, or execute loadlin to load a linux kernerel from my msdos >>> HD >>> and mount the root system. And this works acceptable. But it is not a >>> decent >>> solution. And since LILO worked with Slackware, I see no reason for it not >>> to >>> work with Debian. Any sugestions will be appricialed. Thanx.
Re: LILO trouble
Hi, > Now, I decided to convert into Debian (I just love it's package system), so I > through out the Slackware stuff and installed the three disks base system. I > had to install LILO by hand because the instalation package tried to install > it on the linx partion, which is the second partion on the secon harddisk > (/dev/hdb2). I placed it on (/dev/hda). Then I rebootet. Then insted of the > LILO text that is supposed to show up when LILO loads I only got "L" followd > by "04" repeated in what seemsed to infinity. # 0x04 "Sector not found". This typically indicates a geometry mismatch. #If you're booting a raw-written disk image, verify whether it was #created for disks with the same geometry as the one you're using. If #you're booting from a SCSI disk or a large IDE disk, you should check, #whether LILO has obtained correct geometry data from the kernel or #whether the geometry definition corresponds to the real disk geometry. #(See section "Disk geometry".) Removing COMPACT may help too. So may #adding LINEAR. You can see if the Geometry in the Bios is the same as Linux reports on startup of the kernel. If not, you should specify the geometry in lilo.conf as you have enterd it in the System Bios. Greetings Bernd PS: read /usr/doc/lilo/Manual.txt (of lilo_19-1.deb). -- (OO) -- [EMAIL PROTECTED] -- ( .. ) [EMAIL PROTECTED],ka.sub.org} http://home.pages.de/~eckes/ o--o *plush* 2048/A2C51749 [EMAIL PROTECTED] +4972573817 *plush* (OO) If privacy is outlawed only Outlaws have privacy
LILO trouble
Hi, I have a 486 on which I untill recently had MSDos and Slackware installed on two diffrent harddisks, with LILO installed in the master boot block of the msdos harddisk allowing me to select between the two operating systems. This worked just fine. Now, I decided to convert into Debian (I just love it's package system), so I through out the Slackware stuff and installed the three disks base system. I had to install LILO by hand because the instalation package tried to install it on the linx partion, which is the second partion on the secon harddisk (/dev/hdb2). I placed it on (/dev/hda). Then I rebootet. Then insted of the LILO text that is supposed to show up when LILO loads I only got "L" followd by "04" repeated in what seemsed to infinity. I have tried bothe my old Slackware lilo configuration file, the new created by Debian. I have tried both the lilo version that came with Debian and the old one used by Slackware. I have tried having both the MSDos hd and the Linux HD as the first HD. And Gud knows what else, but the result is just the same. What am I doing wrong? I have temporarity solved the problem by using a MSDos boot disk with a menu that allows me to either run the startup files from my HD after load MSDOS from the floppy, or execute loadlin to load a linux kernerel from my msdos HD and mount the root system. And this works acceptable. But it is not a decent solution. And since LILO worked with Slackware, I see no reason for it not to work with Debian. Any sugestions will be appricialed. Thanx. -- -- Name: Hakan Ardo E-Mail:[EMAIL PROTECTED] WWW: HTTP://www.ub2.lu.se/~hakan/sig.html Interests: WWW, Programming, 3D graphics Thought for the day: As long as one understands, the spelling does not matter :-) --
