Re: Linux booting from HD on Promise Ultra ATA 100
On Fri, 12 Jan 2001, Stephen Torri wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Fri, 12 Jan 2001, Martin Josefsson wrote: > > > My setup looks like this, I boot from hde > > I configured my BIOS to boot from SCSI (I have no scsi-adapter but the > > promise card reports itself as one at boottime) > > > > boot = /dev/hde3 > > delay = 50 > > message = /boot/message > > vga = extended > > read-only > > lba32 > > disk=/dev/hde > > bios=0x80 > > > The line "lba32" is for what? I have to ask this because I have never seen > it in an example of a lilo.conf file before. it is a BIOS extension that allows you to boot of a partition thats located above cylinder 1024. I think it's called EDB or something like that. > Also you put "disk=/dev/hde and bios=0x80" to inform lilo that there was a > disk there and its bios address is 0x80. Is this right? yes. > If I would follow your example then I would put: > > lba32 > disk=/dev/hdf >bios=0x82 I think that would be correct yes, and install LILO on hde (I think the promise-card only tries to boot from primary master when you have selected SCSI in BIOS. But I'm not sure. /Martin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux booting from HD on Promise Ultra ATA 100
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 12 Jan 2001, Martin Josefsson wrote: > My setup looks like this, I boot from hde > I configured my BIOS to boot from SCSI (I have no scsi-adapter but the > promise card reports itself as one at boottime) > > boot = /dev/hde3 > delay = 50 > message = /boot/message > vga = extended > read-only > lba32 > disk=/dev/hde > bios=0x80 The line "lba32" is for what? I have to ask this because I have never seen it in an example of a lilo.conf file before. Also you put "disk=/dev/hde and bios=0x80" to inform lilo that there was a disk there and its bios address is 0x80. Is this right? If I would follow your example then I would put: lba32 disk=/dev/hdf bios=0x82 Stephen - -- Buyer's Guide for a Operating System: Don't care to know: Mac Don't mind knowing but not too much: Windows Hit me! I can take it!: Linux -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.1 (GNU/Linux) Comment: For info see http://www.gnupg.org Filter: gpg4pine 4.0 (http://azzie.robotics.net) iD8DBQE6XyltI7ZT+dSlizsRAiM/AJ9SdDSNbYk1Pep2+guGakfYcYUYjQCgzLWR BcrGeMP0DKwgZWo3m0KdEho= =gGWn -END PGP SIGNATURE- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux booting from HD on Promise Ultra ATA 100
On Fri, 12 Jan 2001, Stephen Torri wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > I'm having difficulty booting from the Promise controller. Here is the > story: > > I originally had my system setup with all drives working off the > mainsboard IDE controller (Intel 82371AB PIIX4). The setup was > > /dev/hda - ST310232A, FwRev=3.09 (Seagate) > /dev/hdb - 927308, FwRev=RA530JNO (Maxtor) * Linux installed here > /dev/hdc - CD-532E-B (Teach CDROM) > /dev/hdd - CD-RW4224A (Smart & Friendly CDRW). > > Well I got an Promise Ultra ATA 100 controller card. Went over to > linux-ide.org and get the patches for kernel-2.2.16. Took a pristine > kernel-2.2.16 and patched it and then compiled it on a RedHat 6.2 > system. I then made a bootdisk with this new kernel. > > So then I installed the drives in this order: > > (Mainsboard controller) > primary master - ST310232A (Seagate) > primary slave - none > secondary master - CDROM > secondary slave - CDRW > > (Promise controller) > primary slave - IBM-DLTA-307045 (IBM) > primary slave - 927308 (Maxtor) * Linux install here > secondary master - none > secondary slave - none > > The system boots if I use the bootdisk and tell it "linux > root=/dev/hdf3". I edited the lilo.conf and the fstab for the new > setup. I can log in and do my business with my the linux partition but > when I tried to use lilo to setup the MBR on the first disk (mainsboard) I > got this: > > warning: BIOS Drive 0x82 may not be accessible. > > Is there some settings that I need to give to the lilo to boot? My setup looks like this, I boot from hde I configured my BIOS to boot from SCSI (I have no scsi-adapter but the promise card reports itself as one at boottime) boot = /dev/hde3 delay = 50 message = /boot/message vga = extended read-only lba32 disk=/dev/hde bios=0x80 image=/boot/kernel/vmlinuz-2.4.1-pre2 label = Linux root = /dev/hde5 image=/boot/kernel/vmlinuz-2.4.0-test10 label = test10 root = /dev/hde5 This works perfectly fine here /Martin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Linux booting from HD on Promise Ultra ATA 100
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm having difficulty booting from the Promise controller. Here is the story: I originally had my system setup with all drives working off the mainsboard IDE controller (Intel 82371AB PIIX4). The setup was /dev/hda - ST310232A, FwRev=3.09 (Seagate) /dev/hdb - 927308, FwRev=RA530JNO (Maxtor) * Linux installed here /dev/hdc - CD-532E-B (Teach CDROM) /dev/hdd - CD-RW4224A (Smart & Friendly CDRW). Well I got an Promise Ultra ATA 100 controller card. Went over to linux-ide.org and get the patches for kernel-2.2.16. Took a pristine kernel-2.2.16 and patched it and then compiled it on a RedHat 6.2 system. I then made a bootdisk with this new kernel. So then I installed the drives in this order: (Mainsboard controller) primary master - ST310232A (Seagate) primary slave - none secondary master - CDROM secondary slave - CDRW (Promise controller) primary slave - IBM-DLTA-307045 (IBM) primary slave - 927308 (Maxtor) * Linux install here secondary master - none secondary slave - none The system boots if I use the bootdisk and tell it "linux root=/dev/hdf3". I edited the lilo.conf and the fstab for the new setup. I can log in and do my business with my the linux partition but when I tried to use lilo to setup the MBR on the first disk (mainsboard) I got this: warning: BIOS Drive 0x82 may not be accessible. Is there some settings that I need to give to the lilo to boot? Stephen - -- Buyer's Guide for a Operating System: Don't care to know: Mac Don't mind knowing but not too much: Windows Hit me! I can take it!: Linux -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.1 (GNU/Linux) Comment: For info see http://www.gnupg.org Filter: gpg4pine 4.0 (http://azzie.robotics.net) iD8DBQE6XyOTI7ZT+dSlizsRAu3BAKCdtwlgiJ9+isy9NOlltIs+logHMgCfViiy ofYOmWxhH6Qt8FDeoJNZvsg= =+RwL -END PGP SIGNATURE- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Linux booting from HD on Promise Ultra ATA 100
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm having difficulty booting from the Promise controller. Here is the story: I originally had my system setup with all drives working off the mainsboard IDE controller (Intel 82371AB PIIX4). The setup was /dev/hda - ST310232A, FwRev=3.09 (Seagate) /dev/hdb - 927308, FwRev=RA530JNO (Maxtor) * Linux installed here /dev/hdc - CD-532E-B (Teach CDROM) /dev/hdd - CD-RW4224A (Smart Friendly CDRW). Well I got an Promise Ultra ATA 100 controller card. Went over to linux-ide.org and get the patches for kernel-2.2.16. Took a pristine kernel-2.2.16 and patched it and then compiled it on a RedHat 6.2 system. I then made a bootdisk with this new kernel. So then I installed the drives in this order: (Mainsboard controller) primary master - ST310232A (Seagate) primary slave - none secondary master - CDROM secondary slave - CDRW (Promise controller) primary slave - IBM-DLTA-307045 (IBM) primary slave - 927308 (Maxtor) * Linux install here secondary master - none secondary slave - none The system boots if I use the bootdisk and tell it "linux root=/dev/hdf3". I edited the lilo.conf and the fstab for the new setup. I can log in and do my business with my the linux partition but when I tried to use lilo to setup the MBR on the first disk (mainsboard) I got this: warning: BIOS Drive 0x82 may not be accessible. Is there some settings that I need to give to the lilo to boot? Stephen - -- Buyer's Guide for a Operating System: Don't care to know: Mac Don't mind knowing but not too much: Windows Hit me! I can take it!: Linux -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.1 (GNU/Linux) Comment: For info see http://www.gnupg.org Filter: gpg4pine 4.0 (http://azzie.robotics.net) iD8DBQE6XyOTI7ZT+dSlizsRAu3BAKCdtwlgiJ9+isy9NOlltIs+logHMgCfViiy ofYOmWxhH6Qt8FDeoJNZvsg= =+RwL -END PGP SIGNATURE- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux booting from HD on Promise Ultra ATA 100
On Fri, 12 Jan 2001, Stephen Torri wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm having difficulty booting from the Promise controller. Here is the story: I originally had my system setup with all drives working off the mainsboard IDE controller (Intel 82371AB PIIX4). The setup was /dev/hda - ST310232A, FwRev=3.09 (Seagate) /dev/hdb - 927308, FwRev=RA530JNO (Maxtor) * Linux installed here /dev/hdc - CD-532E-B (Teach CDROM) /dev/hdd - CD-RW4224A (Smart Friendly CDRW). Well I got an Promise Ultra ATA 100 controller card. Went over to linux-ide.org and get the patches for kernel-2.2.16. Took a pristine kernel-2.2.16 and patched it and then compiled it on a RedHat 6.2 system. I then made a bootdisk with this new kernel. So then I installed the drives in this order: (Mainsboard controller) primary master - ST310232A (Seagate) primary slave - none secondary master - CDROM secondary slave - CDRW (Promise controller) primary slave - IBM-DLTA-307045 (IBM) primary slave - 927308 (Maxtor) * Linux install here secondary master - none secondary slave - none The system boots if I use the bootdisk and tell it "linux root=/dev/hdf3". I edited the lilo.conf and the fstab for the new setup. I can log in and do my business with my the linux partition but when I tried to use lilo to setup the MBR on the first disk (mainsboard) I got this: warning: BIOS Drive 0x82 may not be accessible. Is there some settings that I need to give to the lilo to boot? My setup looks like this, I boot from hde I configured my BIOS to boot from SCSI (I have no scsi-adapter but the promise card reports itself as one at boottime) boot = /dev/hde3 delay = 50 message = /boot/message vga = extended read-only lba32 disk=/dev/hde bios=0x80 image=/boot/kernel/vmlinuz-2.4.1-pre2 label = Linux root = /dev/hde5 image=/boot/kernel/vmlinuz-2.4.0-test10 label = test10 root = /dev/hde5 This works perfectly fine here /Martin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux booting from HD on Promise Ultra ATA 100
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 12 Jan 2001, Martin Josefsson wrote: My setup looks like this, I boot from hde I configured my BIOS to boot from SCSI (I have no scsi-adapter but the promise card reports itself as one at boottime) boot = /dev/hde3 delay = 50 message = /boot/message vga = extended read-only lba32 disk=/dev/hde bios=0x80 The line "lba32" is for what? I have to ask this because I have never seen it in an example of a lilo.conf file before. Also you put "disk=/dev/hde and bios=0x80" to inform lilo that there was a disk there and its bios address is 0x80. Is this right? If I would follow your example then I would put: lba32 disk=/dev/hdf bios=0x82 Stephen - -- Buyer's Guide for a Operating System: Don't care to know: Mac Don't mind knowing but not too much: Windows Hit me! I can take it!: Linux -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.1 (GNU/Linux) Comment: For info see http://www.gnupg.org Filter: gpg4pine 4.0 (http://azzie.robotics.net) iD8DBQE6XyltI7ZT+dSlizsRAiM/AJ9SdDSNbYk1Pep2+guGakfYcYUYjQCgzLWR BcrGeMP0DKwgZWo3m0KdEho= =gGWn -END PGP SIGNATURE- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux booting from HD on Promise Ultra ATA 100
On Fri, 12 Jan 2001, Stephen Torri wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 12 Jan 2001, Martin Josefsson wrote: My setup looks like this, I boot from hde I configured my BIOS to boot from SCSI (I have no scsi-adapter but the promise card reports itself as one at boottime) boot = /dev/hde3 delay = 50 message = /boot/message vga = extended read-only lba32 disk=/dev/hde bios=0x80 The line "lba32" is for what? I have to ask this because I have never seen it in an example of a lilo.conf file before. it is a BIOS extension that allows you to boot of a partition thats located above cylinder 1024. I think it's called EDB or something like that. Also you put "disk=/dev/hde and bios=0x80" to inform lilo that there was a disk there and its bios address is 0x80. Is this right? yes. If I would follow your example then I would put: lba32 disk=/dev/hdf bios=0x82 I think that would be correct yes, and install LILO on hde (I think the promise-card only tries to boot from primary master when you have selected SCSI in BIOS. But I'm not sure. /Martin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
