On Wed, 2 Sep 1998, Nils Rennebarth wrote:
> Appears it does not try to mount /dev/ram0 as root device as it should.
>
> Did you really run rdev.sh right?
> (Make sure the floppy is writeable)
>
> mount /dev/fd0 /mnt
> sh /mnt/rdev.sh
> umount /mnt
Thanks very much. This must have been i
On Tue, Sep 01, 1998 at 11:35:21AM -0400, James G. MacKinnon wrote:
> Steve Hsieh kindly pointed out that we should have read readme.txt on the
> rescue disk and run rdev.sh after transferring the kernel to it. We have
> now done this, using both a bzImage (as recommended in the readme file)
> and
I don't know if it's any help at all, but after figuring out to type
linux floppy=thinkpad
at the prompt, I had no problems at all on a thinkpad 755c . . . save
that I still don't have the battery working
rick
--
These opinions will not be those of ISU until it pays my retainer.
Re my earlier message about being unable to install Debian 2.0 on a
ThinkPad 600 that runs Red Hat 5.0 fine. We are still unable to create a
kernel that will allow the rescue disk to boot.
Steve Hsieh kindly pointed out that we should have read readme.txt on the
rescue disk and run rdev.sh after t
On Tue, 1 Sep 1998, James G. MacKinnon wrote:
> I have been trying to help a colleague install Debian 2.0 on his ThinkPad
> 600. Red Hat 5.0 previously installed fine. However, he has been unable to
> boot from either the standard Debian 2.0 rescue disk or the Tecra rescue
> disk.
It's probably
I have been trying to help a colleague install Debian 2.0 on his ThinkPad
600. Red Hat 5.0 previously installed fine. However, he has been unable to
boot from either the standard Debian 2.0 rescue disk or the Tecra rescue
disk.
Believing that this is a problem caused by all the extra drivers in t
6 matches
Mail list logo