Re: Can't boot from hard disk--solved
On Wed, 11 Aug 1999, Mark Lawrence wrote: > problematic for certain machines. The case that is sited most often > is the IBM Tecra laptop, so the problem is often referred to as the > "tecra problem." Since I wasn't installing on a laptop of any kind, I Actually, IBM doesn't make the Tecra's. To
Re: Can't boot from hard disk--solved
My booting problem has been solved. In case anyone else has a similar problem, here is what was wrong, how I fixed things, and what I would do differently if I were to start over again. To recap, the problem was that after installing slink, I could boot from the boot floppy, but not from the hard
Re: Can't boot from hard disk
Well since you are "grasping at straws"... 1. You did _run_ lilo after changing /etc/lilo.conf, yes? 2. What does rdev /boot/vmlinuz-2.0.36 give you? (although your "root=/dev/hda1" should over-ride) 3. Should you have the argument "compact" in your lilo.conf? 4. You don't have one of thos
Re: Can't boot from hard disk
Paul Miller wrote: > > Mark Lawrence wrote: > > > > The /etc/lilo.conf looks like this: > > > > boot=/dev/hda1 > > root=/dev/hda1 > > install=/boot/boot.b > > map=/boot/map > > vga=normal > > delay=20 > > image=/vmlinuz > > label=Linux > > read-only > > > You should try 'boot=/dev/hda'. No
Re: Can't boot from hard disk
Mark Lawrence wrote: > The /etc/lilo.conf looks like this: > > boot=/dev/hda1 perhaps boot=/dev/hda ? -- hafi
Can't boot from hard disk
Just installed 2.1 (slink) from cdrom. Boots from floppy OK, but hangs after "Loading Linux." The machine is a Pentium 200 with 96 MB of RAM. The master EIDE hd has 6.4 GB and is partitioned like this: device startstopmount point /dev/hda1 1 65
Re: newbie² in trouble: installation failshello there, (please forgive my poor English)I've got an interesting case for you linux wizzkids...I tried to install Debian 2.1 and now i can't boot from hard disk andfloppy, or reinstall the system:I tried to install Debian 2.1 on a 486 with floppies.I managed to bootfrom hard disk, and started doing some linux. Soon i got tired ofdownloading the packages each time i wanted to try something new andordered the cdroms. First wanted to configure the cd-driver for mycreative labs CR-563 B in linux, it never worked out(also in dselect).After a while i convinced myself it would be better to reinstall (whatwould allow me to repartition as well). I still had a rescue and a bootdisk. I repartitioned, and wanted to continue with a cdrom-installation.I couldn't configure my cdrom-driver. I tried a few things, and gave itup. When i wanted to reboot, i found out my hard disk was empty(ipartitioned it), and i tried to reboot with my boot disk. Linux stoppedbooting with an 'unable to open an initial console' message. Then icould only try to reinstall with floppies. When i started the wholeinstallation once again everything seemed allright, till i came at'install the OS kernel and modules' where you have to insert the rescuedisk (it was already inserted). i got 'this is not the rescuefloppy...'message. tried it again and again, nothing helped. I threw thefloppy away, took another computer, rawrited2 resc1440.bin to it, thisone didn't work either, nor did any other floppy.(all formatted 14.4disks that allowed me to start the installation but stopped at the samepoint).So these are my questions: how can i get Linux to understand that i'musing the right floppies?how can i configure my CR-563creative labs in the installation program?what is this message when i bootfrom a boot-floppy:'unable to open an initial console'?here are some technical details: MB: Sis85c47,BIOS: Award v 4.50G,12MBram, SB16 with CR-563B CDROM (proprietary), linuxver: Debian 2.1, kernel
Holy smoke! I didn't know one could get that much into a Subject header!!! -- __ _ Mark Wagnon Debian GNU/ -o) / / (_)__ __ __ Chula Vista, CA /\\/ /__/ / _ \/ // /\ \/ / [EMAIL PROTECTED] _\_v/_/_//_/\_
newbie² in trouble: installation failshello there, ( please forgive my poor English)I've got an interesting case for you linux wizzkids...I tried to install Debian 2.1 and now i can't boot from hard disk andfloppy, or reinstall the system:I tried to install Debian 2.1 on a 486 with floppies.I managed to bootfrom hard disk, and started doing some linux. Soon i got tired ofdownloading the packages each time i wanted to try something new andordered the cdroms. First wanted to configure the cd-driver for mycreative labs CR-563 B in linux, it never worked out(also in dselect).After a while i convinced myself it would be better to reinstall (whatwould allow me to repartition as well). I still had a rescue and a bootdisk. I repartitioned, and wanted to continue with a cdrom-installation.I couldn't configure my cdrom-driver. I tried a few things, and gave it up. When i wanted to reboot, i found out my hard disk was empty(i partitioned it), and i tried to reboot with my boot disk. Linux stopped booting with an 'unable to open an initial console' message. Then i could only try to reinstall with floppies. When i started the whole installation once again everything seemed allright, till i came at 'install the OS kernel and modules' where you have to insert the rescue disk (it was already inserted). i got 'this is not the rescue floppy...'message. tried it again and again, nothing helped. I threw the floppy away, took another computer, rawrited2 resc1440.bin to it, this one didn't work either, nor did any other floppy.(all formatted 14.4 disks that allowed me to start the installation but stopped at the same point).So these are my questions: how can i get Linux to understand that i'musing the right floppies? how can i configure my CR-563 creative labs in the installation program? what is this message when i boot from a boot-floppy:'unable to open an initial console'?here are some technical details: MB: Sis85c47,BIOS: Award v 4.50G,12MBram, SB16 with CR-563B CDROM (proprietary), linuxver: Debian 2.1, kernel
>hello there, (please forgive my poor English) Hi Damiaan No need, Your English is very good. I don't know anything about your cdrom, but I do have allot Of experience with bad disks. Try A different disk and redownload resc1440.bin and rawrite it again it may have gotten corrupted ( con
