Re: Installation Question (IBM TP 560)
Justin, I hope you get an answer to your question: I've been battling for several weeks to get a Linux partition up that will boot when the IBM boot manager is used to select the linux partition, but with Debian, I get the same result you report. I've been able to install RedHat without any problems unless I tell it to write the MBR. Big mistake: after that, I could not boot my first partition - my Win95B/fat32 partition. My local linux guru located an undocumented DOS fdisk switch (fdisk /mbr) that cleared the problem, saving me having to reformat and reinstall all my Win95 software. I've been real unwilling to mess with the linux stuff since then. Dave Justin Liu wrote: and used the Tecra boot disks and got it to work. My problem now is that I want to have Linux coexist with other OS's via the OS/2 Boot Manager. I set up my partitions using OS/2 fdisk and installed Boot Manager. Then I ran the Debian install program to get a base system installed. When prompted about having LILO write the MBR and making Linux the default, I answered no to both questions. Now, when I reboot and select the Linux partition in BM, it reports that the partition is not formatted. and goes back to BM. I can boot up with the boot floppy created during installation. - Justin [EMAIL PROTECTED] -- --David E. Scott Ohio Administrative Services [EMAIL PROTECTED] [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Installation Question (IBM TP 560)
David E. Scott [EMAIL PROTECTED] writes: Justin, I hope you get an answer to your question: I've been battling for several weeks to get a Linux partition up that will boot when the IBM boot manager is used to select the linux partition, but with Debian, I get the same result you report. I've been able to install RedHat without any problems unless I tell it to write the MBR. Big mistake: after that, I could not boot my first partition - my Win95B/fat32 partition. My local linux guru located an undocumented DOS fdisk switch (fdisk /mbr) that cleared the problem, saving me having to reformat and reinstall all my Win95 software. I've been real unwilling to mess with the linux stuff since then. I've used the OS/2 Warp 3.0 Boot Manager with Debian for over a year now. The trick is to put the linux loader to the boot block of the Linux root partition by putting the command boot=/dev/hdNUMBER where /dev/hdNUMBER is your the aforementioned root partition in the file /etc/lilo.conf and running lilo. /Tommi Kääriäinen/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Installation Question (IBM TP 560)
Tommi Kaariainen wrote: I've used the OS/2 Warp 3.0 Boot Manager with Debian for over a year now. The trick is to put the linux loader to the boot block of the Linux root partition by putting the command boot=/dev/hdNUMBER where /dev/hdNUMBER is your the aforementioned root partition in the file /etc/lilo.conf and running lilo. /Tommi Kääriäinen/ Tommi, My system initially was a Win95B system using FAT32 for the full 5 gig drive. I bought Powerquest Partition Magic to resize the FAT32 partition down so that I could put an msdos partition (800M) and a 1.5G extended partition containing both the Linux partition and swap partitions). Partition Magic comes with IBM's Boot Manager which I installed as the fourth primary partition at the top of the 5gig drive so I could select between Win 95, Linux, and I also wanted to be able to boot to the msdos partition to run the Win 3.1 system from my previous computer. To your knowledge, is the Boot Manager referred to here one and the same as the Boot Manager you're using? Thanks, Dave -- --David E. Scott Ohio Administrative Services [EMAIL PROTECTED] [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Installation Question (IBM TP 560)
David E. Scott [EMAIL PROTECTED] writes: Tommi, My system initially was a Win95B system using FAT32 for the full 5 gig drive. I bought Powerquest Partition Magic to resize the FAT32 partition down so that I could put an msdos partition (800M) and a 1.5G extended partition containing both the Linux partition and swap partitions). Partition Magic comes with IBM's Boot Manager which I installed as the fourth primary partition at the top of the 5gig drive so I could select between Win 95, Linux, and I also wanted to be able to boot to the msdos partition to run the Win 3.1 system from my previous computer. To your knowledge, is the Boot Manager referred to here one and the same as the Boot Manager you're using? I don't know, however as far as I know putting the Linux Loader (lilo) to the boot block of the Linux root partition (the logical partition i this case) shouldn't break anything. /Tommi Kääriäinen/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Installation Question (IBM TP 560)
Tommi Kaariainen wrote: I don't know, however as far as I know putting the Linux Loader (lilo) to the boot block of the Linux root partition (the logical partition i this case) shouldn't break anything. Tommi, That's really interesting: putting LILO in the boot block of the Linux root partition. I understood that LILO would allow you to boot into various partitions, like the IBM Boot Manager does. When I was in IBM Systems Programming, it was useful to follow the sequence of events from the label record to the Volume Table of Contents (VTOC) and from there into the specific file you're looking for. Perhaps it would be useful to clarify the sequence of events here. According to the Partition Magic documentation, there is a Master Boot Record at the beginning of the drive which consists of a master boot program and partition table. Then for each bootable partition there is a partition boot record as well. So if I install the IBM Boot Manager in its own partition at the top of the drive, then it would seem logical that the system would first go to the first sector on the drive, find out there is a boot manager partition and go there, display the menu selection and then after input go to the selected partition where it presumably finds a partition boot record which presumably tells it where the first program is for loading that operating system. So if LILO is installed, it would appear that it might override the Boot Manager, but where is it installed and how does it control the sequence of events? If it overrides the IBM Boot Manager, which it seems to do, then one or more of the non-linux partitions would not be accessable. In my case when I let RedHat use LILO, I lost the ability to boot into my Win95 partition until I used the DOS boot diskette and gave the fdisk /mbr command. However, it would be nice to be able to boot into 1. first partition: Win 95 2. second partition: Win 3.1 and 3. first logical partition in an extended partition: Linux. Dave -- --David E. Scott Ohio Administrative Services [EMAIL PROTECTED] [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Installation Question (IBM TP 560)
David E. Scott [EMAIL PROTECTED] writes: That's really interesting: putting LILO in the boot block of the Linux root partition. I understood that LILO would allow you to boot into various partitions, like the IBM Boot Manager does. When I was in IBM Systems Programming, it was useful to follow the sequence of events from the label record to the Volume Table of Contents (VTOC) and from there into the specific file you're looking for. Perhaps it would be useful to clarify the sequence of events here. According to the Partition Magic documentation, there is a Master Boot Record at the beginning of the drive which consists of a master boot program and partition table. Then for each bootable partition there is a partition boot record as well. So if I install the IBM Boot Manager in its own partition at the top of the drive, then it would seem logical that the system would first go to the first sector on the drive, find out there is a boot manager partition and go there, display the menu selection and then after input go to the selected partition where it presumably finds a partition boot record which presumably tells it where the first program is for loading that operating system. LILO can be installed to override the Boot Manager (if it's installed on the MBR), but it can also be installed to be started by something other (when installed on the boot block of the Linux partition). The sequence of events in my machine is like this: 1. The Master Boot Record (modified by OS/2 Boot Manager) of the hard disk is read and executed. 2. The MBR starts Boot Manager 3. The user tells the Boot Manager to boot from the Linux partition. 4. The Boot Manager starts LILO boot loader on the boot block of the Linux partition. 5. LILO starts Linux /Tommi Kääriäinen/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Installation Question (IBM TP 560)
Tommi Kaariainen wrote: The sequence of events in my machine is like this: 1. The Master Boot Record (modified by OS/2 Boot Manager) of the hard disk is read and executed. 2. The MBR starts Boot Manager 3. The user tells the Boot Manager to boot from the Linux partition. 4. The Boot Manager starts LILO boot loader on the boot block of the Linux partition. 5. LILO starts Linux Tommi, Now that *does* make sense. However it appears that one should not allow RedHat or debian to install LILO as part of their automated process -- better to run some program to install LILO specifically in the boot block of the Linux partition, correct? Dave -- --David E. Scott Ohio Administrative Services [EMAIL PROTECTED] [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Installation Question (IBM TP 560)
On 26 Jan 1998 00:06:17 +0200 Tommi Kaariainen ([EMAIL PROTECTED]) wrote: David E. Scott [EMAIL PROTECTED] writes: The sequence of events in my machine is like this: 1. The Master Boot Record (modified by OS/2 Boot Manager) of the hard disk is read and executed. 2. The MBR starts Boot Manager 3. The user tells the Boot Manager to boot from the Linux partition. 4. The Boot Manager starts LILO boot loader on the boot block of the Linux partition. 5. LILO starts Linux So can you use (easily) LILO to manage your whole system with 3+ different OSs? That is what I will want to do with it, soon. -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- David Goodwinhttp://www.peak.org/~goodwid Corvallis, Oregon, USA [EMAIL PROTECTED] * -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Installation Question (IBM TP 560)
David Goodwin [EMAIL PROTECTED] writes: On 26 Jan 1998 00:06:17 +0200 Tommi Kaariainen ([EMAIL PROTECTED]) wrote: David E. Scott [EMAIL PROTECTED] writes: The sequence of events in my machine is like this: 1. The Master Boot Record (modified by OS/2 Boot Manager) of the hard disk is read and executed. 2. The MBR starts Boot Manager 3. The user tells the Boot Manager to boot from the Linux partition. 4. The Boot Manager starts LILO boot loader on the boot block of the Linux partition. 5. LILO starts Linux So can you use (easily) LILO to manage your whole system with 3+ different OSs? That is what I will want to do with it, soon. Some OSs (Linux, DOS, W95(at least without FAT32), maybe others) can be loaded by LILO, and on the other hand LILO (and thus Linux) can be loaded by OS/2 Boot Manager (it works for me), NT-loader (according to Linux+NT-Loader-mini-HOWTO) and some others. /Tommi Kääriäinen/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Installation Question (IBM TP 560)
Hi - I've been trying to get Debian installed on my IBM Thinkpad 560 for a couple days now and I'm still having some problems. Initially it wouldn't boot, except with loadlin, but I looked through the mailing list archives and used the Tecra boot disks and got it to work. My problem now is that I want to have Linux coexist with other OS's via the OS/2 Boot Manager. I set up my partitions using OS/2 fdisk and installed Boot Manager. Then I ran the Debian install program to get a base system installed. When prompted about having LILO write the MBR and making Linux the default, I answered no to both questions. Now, when I reboot and select the Linux partition in BM, it reports that the partition is not formatted. and goes back to BM. I can boot up with the boot floppy created during installation. Is it possible that the problem is that Linux is reading the wrong disk geometry and is writing at the wrong location? I installed IBM's 4 Gig drive, which lists a geometry of 7944 cyl, 16 heads, 63 sectors in the databook. But Linux fdisk reports something like 993 cyl, 128 h, 63 s. Is there some option I can pass to LOADLIN to set the correct geometry or is this not related to my problem. My system is an IBM Thinkpad 560, with a 120MHz Pentium, 12.1 active screen, 72 Megs or RAM and the 4 Gig hard drive. On another note, I was also wondering which packages I need to install to make Debian recognize my Sony PRD-650 PCMCIA CD-ROM drive to complete my installation? Its a SCSI drive and comes bundled with a PCMCIA SCSI adapter which is basically a repackaged Adaptec 1460 SlimSCSI. Thanks very much in advance, - Justin [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
