Re: debian 1.3 on thinkpad 760xl
-BEGIN PGP SIGNED MESSAGE- On Fri, 2 Jan 1998, Steve Hsieh wrote: John, On the IBM thinkpad 760, you must use the tecra boot disk in the special directory, and not the standard bootdisk. If you build your own kernel, you must build it with 'make zimage' and not 'make bzimage'. The thinkpad will hang as you describe otherwise. Or use the same patch as the tecra disks, available from http://www.cck.uni-kl.de/misc/tecra710/toshiba-a20.diff Nils -BEGIN PGP SIGNATURE- Version: 2.6.3ia Charset: noconv iQB1AwUBNLMw6lptA0IhBm0NAQEcqQMAtVpZ4STsh4TWBqDaPMTesCGeRYzB71Xg qdvGy8OB/UvxrzXHqh9dQpr1OFP1aTdjlKLqVP5WNlXHuO2g+0yl5zYOou5DYVpI 0y2AKjKx3oAY84TFVyp1NQd4IJuHS9BX =3m9i -END PGP SIGNATURE- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: debian 1.3 on thinkpad 760xl
If the thinkpad problem persist, try the tecra bootdisk (in the special directory I think). Brandon - Brandon Mitchell [EMAIL PROTECTED] We all know linux is great... it PGP: finger -l [EMAIL PROTECTED] does infinite loops in 5 seconds Phone: (757) 221-4847 --Linus Torvalds -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: debian 1.3 on thinkpad 760xl
John, On the IBM thinkpad 760, you must use the tecra boot disk in the special directory, and not the standard bootdisk. If you build your own kernel, you must build it with 'make zimage' and not 'make bzimage'. The thinkpad will hang as you describe otherwise. The alternative, as you may have discovered, is to use loadlin to boot from DOS. Steve On Thu, 1 Jan 1998, LKloss wrote: attempts to install debian 1.3 and always the same problem. On reboot the system hangs at LILO loading linux So the two main things here 1) I cannot install linux without first booting a DOS rescure disk and loading the install using loadlin. If I just try the boot-rescue disk (with resc1440.bin rawrite2'in to it) the system hangs after loading linux 2) After reboot (whether from floppy or hard drive, I've tried both) the system hangs at LILO loading linux So I'm thinking that debian doesn't now how to read the IDE Hard Drive interface and can't boot. So what do I do about this? - John Kloss -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: debian 1.3 on thinkpad 760xl
Have you tried useing the tecra boot disks ... you might try these boot disk ... try installing from there as it will add that kernel to the hard drive ... I think that the tecra boot disks are made for the Laptops that can't handle BzImages I think they can be found in the /disks directory On Thu, 01 Jan 1998 15:54:16 -0800 [EMAIL PROTECTED] (David Stern) writes: On Thu, 01 Jan 1998 14:14:13 EST, LKloss wrote: [..proper pre-install procedure snipped..] Now, first problem. I take the boot-rescue disk, put it in the disk drive, reboot the system, get a message from debian giving me various help screens, and then the boot: prompt. So I press return and see loading root.bin . loading linux . and then nothing, the machine hangs. Thinking that maybe it was the disk drive, I try againwith boot: linux floppy=thinkpad I think this is the parameter I was hinting at in the notebook urls (although I see they weren't very helpful now). The syntax looks good, too. I seem to recall someone else reporting they couldn't get their thinkpad to boot even after using this parameter, that another was required (?). and same thing. My CD-Rom is NOT bootable, the thinkpad770 has one but not 760XL which is what I have. So I currently can't start the install from floppy. So I try a second method. I use an old DOS 6.2 boot-rescue disk to boot up a small version of DOS. I then put in the debian boot-rescue disk (which I made above, only now I have copied loadlin.exe to the disc as well). Now, at the dos prompt I type loadlin linux root=/dev/ram initrd=root.bin which were the instructions given to me in the Debian Linux User's Guide which I bought and read (I also read the more recent version which you point to). So anyway, now the install gets past loading root.bin loading linux and the install continues fine. After that I follow the menus and do the following choose color display select US keyboard partition the hard drive with the following parameters /dev/hda1/ bootable /linux 500Mb -- this is my root partition /dev/hda2/ / linux-swap 100Mb /dev/hda3/ /linux - for /usr ... then hda5,6 /var and /home I then write the partions to the partition table and continue with the install initialize and activate the swap partition initialize all the linux partitions (having the install format each partition) install operating system kernel and modules during which it asks for the boot-rescue floppy and then the drivers floppy which I have (from above) and everything goes fine then it asks which device driver modules I want, specifically the menu says Next Configure Device Driver Modules well, I don't know which I need. The menu screen looks like this ExitFinished with modules. Return to previous menu. block Disks and disk-like devices cdrom Device drivers for CD-Rom drivers fsDevice drivers that allow many dirrerent filesystems to be accessed. ... etc. ... Oh,that. I wondered what you were referring to. block devices are things like hard drives, tape drives. All the bugfixes and chipset patches found here should be compiled into the kernel, which leaves some really old hard drive types which don't pertain to you and PCMCIA and the loopback device, both of which you're not using right now. cdrom is for propreitary interfaces, and I think you have ide/atapi, which is probably already supported because if it weren't you wouldn't have been able to access your cdrom without first setting this up (I think). fs is for network and other filesystems foreign to linux, none of which are pertinent to you now. so I don't know which to load so I choose Exit. Then I configure the network (I don't have any) Then it asks to intall the base system, here is where I feed the install the five base-n.bin disks, so yes I intall the base package. Then I choose the time zone (EST5EDT) tell debian my system clock is not set to GMT then it asks me Make Linux Bootable Directly From Hard Disk Make a Boot Floppy Reboot the System so I make a boot-floppy and reboot the system and then I get LILO loading linux and nothing. I hope that was everything. I've had the Debian Linux User's Guide open in front of me the whole time while doing the install. The main things is I can't boot into linux after the install so I can't edit the /etc/lilo.config file. I'm stuck. What did I do wrong? Something I didn't mention before is that loadlin is a veritable bootloader, so if it works to install, you should be able to use it to boot linux from a dos partition, although in your case I see no reason why you'd want to. loadlin is good when your drive configuration is incompatible with lilo, but this isn't the case for you. You have the right idea with your partitions, but if you want to further eliminate just to see if
debian 1.3 on thinkpad 760xl
I recently bought the debian 1.3 cd's and an IBM thinkpad 760xl. The IBM came with windows NT preinstalled. I have a 2.1Gig HD which I repartitioned into two gig partitions using fips.exe. That worked fine. My NT partition was booting fine (first partition) until I tried to install linux. I made the boot-floppies via the method recommended by the Debian Linux User's Guide (using rawrite2.exe to copy resc1440.exe, drivers1440.exe, and the base-1.bin - 5.bin to seven dos formatted disks). I tried to boot the install via disk drive and the boot-rescue and the boot: prompt came up. I hit return and the system said loading root.bin .. loading linux .. and then just hung there doing nothing. I waited about 5 minutes and then decided that I had done something wrong but I didn't know what. So I copied the install files (root.bin, linux, resc1440.bin, driv1440.bin, base-1.bin - 5.bin) to my d: partition (created via fips). I then booted the system with a DOS 6.2 rescue floppy I had, changed to the d: partition and loaded the install with loadlin (I had that on d:, too) using loadlin linux root=/dev/ram initrd=root.bin and the install began and continued along fine. During install I partitioned my hardrive being careful not to touch the 1Gig Dos16 partition I had (which housed NT). I then completed the install (installing no modules because I had no idea which ones to load, and I had read in the HOWTO's that linux would detected the IDE interface for the hard disk and the interface for the floppy drive), created a boot floppy and rebooted using the boot-floppy and got this LILO loading linux and nothing else, the machine just hung there. So I removed the boot-floppy, and restarted the thinkpad and saw this error in partition tables so now NT is gone. Ah, well so much for learning NT. So now I've tried several attempts to install debian 1.3 and always the same problem. On reboot the system hangs at LILO loading linux So the two main things here 1) I cannot install linux without first booting a DOS rescure disk and loading the install using loadlin. If I just try the boot-rescue disk (with resc1440.bin rawrite2'in to it) the system hangs after loading linux 2) After reboot (whether from floppy or hard drive, I've tried both) the system hangs at LILO loading linux So I'm thinking that debian doesn't now how to read the IDE Hard Drive interface and can't boot. So what do I do about this? - John Kloss -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: debian 1.3 on thinkpad 760xl
On Thu, 01 Jan 1998 04:35:24 EST, LKloss wrote: I recently bought the debian 1.3 cd's and an IBM thinkpad 760xl. The IBM came with windows NT preinstalled. I have a 2.1Gig HD which I repartitioned into two gig partitions using fips.exe. That worked fine. My NT partition was booting fine (first partition) until I tried to install linux. I made the boot-floppies via the method recommended by the Debian Linu User's Guide (using rawrite2.exe to copy resc1440.exe, drivers1440.exe, and the base-1.bin - 5.bin to seven dos formatted disks). I tried to boot the install via disk drive and the boot-rescue and the boot: prompt came up. I hi return and the system said If your bios allows bootable cdroms, just stick it in and forget the floppies. loading root.bin .. loading linux .. and then just hung there doing nothing. I waited about 5 minutes and then decided that I had done something wrong but I didn't know what. So I copied the install files (root.bin, linux, resc1440.bin, driv1440.bin, base-1.bin - 5.bin) to my d: partition (created via fips). I then booted the system with a DOS 6.2 rescue floppy I had, changed to the d: partition and loaded the install with loadlin (I had that on d:, too) using loadlin linux root=/dev/ram initrd=root.bin In linux-land we refer to the d: as /dev/hda2 (hd=ide, a=first ide port, first cable position, 2=second partition), assuming this information matches. and the install began and continued along fine. During install I partitioned my hardrive being careful not to touch the 1Gig Dos16 partition I had (which housed NT). I then completed the install (installing no modules because I had ^ What do you mean installing no modules? I don't remember anything about installing modules. I hope you installed the base packages and followed along in the manner prescribed in the installation doc (http://www.debian.org/doc). The packaged kernel is very modular, and there's no choices to be made, either you get it or you don't. If you haven't done so, you might want to read the Linux Gazzette article on getting started with debian, also at the above url and possibly this as well Debian Linux User's Guide http://www.linuxpress.com/001001.htm no idea which ones to load, and I had read in the HOWTO's that linux would detected the IDE interface for the hard disk and the interface for the floppy drive), created a boot floppy and rebooted using the boot-floppy and got this LILO loading linux and nothing else, the machine just hung there. So I removed the boot-floppy, and restarted the thinkpad and saw this error in partition tables so now NT is gone. Ah, well so much for learning NT. So now I've tried several I wouldn't be so quick to make that conclusion. Maybe you just overwrote the mbr. A dos fdisk /mbr might fix that. Or perhaps the wrong partition is marked active. The error could even be on the Linux side. Lilo has some advanced documentation in /usr/doc/lilo which might prove helpful (warning: perhaps after confusing you further). attempts to install debian 1.3 and always the same problem. On reboot the system hangs at LILO loading linux If you can boot from your boot disks, then you should be able to get in and reconfigure lilo. I thought you were supposed to do this, i.e.: it was not optional. So the two main things here 1) I cannot install linux without first booting a DOS rescure disk and loading the install using loadlin. If I just try the boot-rescue disk (with resc1440.bin rawrite2'in to it) the system hangs after loading linux I don't have a working knowledge of loadlin (though I understand what it does), so I'm a little unclear about what exactly is happening here, but it seems to me the only problem with linux booting is that lilo isn't configured properly, and possibly some inconsistencies in fdisk. You also didn't indicate anything which would lead me to believe nt was damaged in any way, only that there was a glitch during install. Where did you install lilo? If you install lilo on the linux / (root) partition, then lilo won't touch your master boot record and you can boot linux by setting the active partition to your linux partition to boot linux (lilo) or your nt partition to boot nt (ntloader). I do this to prevent mbr mangling. Of course, if your mbr was overwritten, you'll need to fix that, and a dos fdisk /mbr is probably the easiest and safest way, if the backup copy still exists. 2) After reboot (whether from floppy or hard drive, I've tried both) the system hangs at LILO loading linux So I'm thinking that debian doesn't now how to read the IDE Hard Drive interface and can't boot. I doubt that. Try reinstalling and pay attention to the part where you install the base packages, ... , also look at your partition table to see which parition is marked active (bootable, it will
Fwd: debian 1.3 on thinkpad 760xl
---BeginMessage--- ---BeginMessage--- Let me be a bit more specific ... I no longer have NT on the machine. I formatted the whole disk in disgust. So lets just assume that currently I have nothing on the machine. I made the debian 1.3 floppies on a machine with a CD-Rom drive and DOS command prompt (a windows 95 machine) in the following manner, copying the files from the custom cd to floppies using rawrite2.exe boot-rescure - resc1440.bin drivers- driv1440.bin base-1.bin - base-1.bin base-2.bin - base-2.bin ... base-5.bin - base-5.bin so seven 1.44Mb floppies with the basic debian install on them plus one extra (dos formatted) to be used as a boot-floppy. Now, first problem. I take the boot-rescue disk, put it in the disk drive, reboot the system, get a message from debian giving me various help screens, and then the boot: prompt. So I press return and see loading root.bin . loading linux . and then nothing, the machine hangs. Thinking that maybe it was the disk drive, I try again with boot: linux floppy=thinkpad and same thing. My CD-Rom is NOT bootable, the thinkpad770 has one but not the 760XL which is what I have. So I currently can't start the install from floppy. So I try a second method. I use an old DOS 6.2 boot-rescue disk to boot up a small version of DOS. I then put in the debian boot-rescue disk (which I made above, only now I have copied loadlin.exe to the disc as well). Now, at the dos prompt I type loadlin linux root=/dev/ram initrd=root.bin which were the instructions given to me in the Debian Linux User's Guide which I bought and read (I also read the more recent version which you pointed to). So anyway, now the install gets past loading root.bin loading linux and the install continues fine. After that I follow the menus and do the following choose color display select US keyboard partition the hard drive with the following parameters /dev/hda1/ bootable /linux 500Mb -- this is my root partition /dev/hda2/ / linux-swap 100Mb /dev/hda3/ /linux - for /usr ... then hda5,6 /var and /home I then write the partions to the partition table and continue with the install initialize and activate the swap partition initialize all the linux partitions (having the install format each partition) install operating system kernel and modules during which it asks for the boot-rescue floppy and then the drivers floppy which I have (from above) and everything goes fine then it asks which device driver modules I want, specifically the menu says Next Configure Device Driver Modules well, I don't know which I need. The menu screen looks like this ExitFinished with modules. Return to previous menu. block Disks and disk-like devices cdrom Device drivers for CD-Rom drivers fsDevice drivers that allow many dirrerent filesystems to be accessed. ... etc. ... so I don't know which to load so I choose Exit. Then I configure the network (I don't have any) Then it asks to intall the base system, here is where I feed the install the five base-n.bin disks, so yes I intall the base package. Then I choose the time zone (EST5EDT) tell debian my system clock is not set to GMT then it asks me Make Linux Bootable Directly From Hard Disk Make a Boot Floppy Reboot the System so I make a boot-floppy and reboot the system and then I get LILO loading linux and nothing. I hope that was everything. I've had the Debian Linux User's Guide open in front of me the whole time while doing the install. The main things is I can't boot into linux after the install so I can't edit the /etc/lilo.config file. I'm stuck. What did I do wrong? - John Kloss ---End Message--- ---End Message---
Re: debian 1.3 on thinkpad 760xl
On Thu, 01 Jan 1998 14:14:13 EST, LKloss wrote: [..proper pre-install procedure snipped..] Now, first problem. I take the boot-rescue disk, put it in the disk drive, reboot the system, get a message from debian giving me various help screens, and then the boot: prompt. So I press return and see loading root.bin . loading linux . and then nothing, the machine hangs. Thinking that maybe it was the disk drive, I try againwith boot: linux floppy=thinkpad I think this is the parameter I was hinting at in the notebook urls (although I see they weren't very helpful now). The syntax looks good, too. I seem to recall someone else reporting they couldn't get their thinkpad to boot even after using this parameter, that another was required (?). and same thing. My CD-Rom is NOT bootable, the thinkpad770 has one but not 760XL which is what I have. So I currently can't start the install from floppy. So I try a second method. I use an old DOS 6.2 boot-rescue disk to boot up a small version of DOS. I then put in the debian boot-rescue disk (which I made above, only now I have copied loadlin.exe to the disc as well). Now, at the dos prompt I type loadlin linux root=/dev/ram initrd=root.bin which were the instructions given to me in the Debian Linux User's Guide which I bought and read (I also read the more recent version which you point to). So anyway, now the install gets past loading root.bin loading linux and the install continues fine. After that I follow the menus and do the following choose color display select US keyboard partition the hard drive with the following parameters /dev/hda1/ bootable /linux 500Mb -- this is my root partition /dev/hda2/ / linux-swap 100Mb /dev/hda3/ /linux - for /usr ... then hda5,6 /var and /home I then write the partions to the partition table and continue with the install initialize and activate the swap partition initialize all the linux partitions (having the install format each partition) install operating system kernel and modules during which it asks for the boot-rescue floppy and then the drivers floppy which I have (from above) and everything goes fine then it asks which device driver modules I want, specifically the menu says Next Configure Device Driver Modules well, I don't know which I need. The menu screen looks like this ExitFinished with modules. Return to previous menu. block Disks and disk-like devices cdrom Device drivers for CD-Rom drivers fsDevice drivers that allow many dirrerent filesystems to be accessed. ... etc. ... Oh,that. I wondered what you were referring to. block devices are things like hard drives, tape drives. All the bugfixes and chipset patches found here should be compiled into the kernel, which leaves some really old hard drive types which don't pertain to you and PCMCIA and the loopback device, both of which you're not using right now. cdrom is for propreitary interfaces, and I think you have ide/atapi, which is probably already supported because if it weren't you wouldn't have been able to access your cdrom without first setting this up (I think). fs is for network and other filesystems foreign to linux, none of which are pertinent to you now. so I don't know which to load so I choose Exit. Then I configure the network (I don't have any) Then it asks to intall the base system, here is where I feed the install the five base-n.bin disks, so yes I intall the base package. Then I choose the time zone (EST5EDT) tell debian my system clock is not set to GMT then it asks me Make Linux Bootable Directly From Hard Disk Make a Boot Floppy Reboot the System so I make a boot-floppy and reboot the system and then I get LILO loading linux and nothing. I hope that was everything. I've had the Debian Linux User's Guide open in front of me the whole time while doing the install. The main things is I can't boot into linux after the install so I can't edit the /etc/lilo.config file. I'm stuck. What did I do wrong? Something I didn't mention before is that loadlin is a veritable bootloader, so if it works to install, you should be able to use it to boot linux from a dos partition, although in your case I see no reason why you'd want to. loadlin is good when your drive configuration is incompatible with lilo, but this isn't the case for you. You have the right idea with your partitions, but if you want to further eliminate just to see if you can boot, you might try making one big partition (900+MB?), even though I doubt partitions are your problem (could be your /etc/fstab options, though). If you try this and it fixes the problem, then figure out what you did wrong and go back to your nicely divided partition scheme before you install a lot of software (btw: consider 32-64MB swap vs. 100MB) Another important thing is
