Debian bug report logs - #1808
No boot parameters available on final boot disk

Message received at debian-bugs:

From pixar.com!bruce Mon Nov  6 17:12:00 1995
Return-Path: <bruce@pixar.com>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0tCcZz-000FIeC; Mon, 6 Nov 95 17:11 PST
Received: from mongo.pixar.com by pixar.com with SMTP id AA13259
  (5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Mon, 6 Nov 1995 17:11:30 -0800
Received: by mongo.pixar.com (Smail3.1.28.1 #15)
	id m0tCcXF-000FJTC; Mon, 6 Nov 95 17:09 PST
Message-Id: <m0tCcXF-000FJTC@mongo.pixar.com>
X-Mailer: exmh version 1.6.2 7/18/95
To: Jan M|ller <fwiffo@daimi.aau.dk>, debian-bugs@Pixar.com
Cc: bruce@Pixar.com
Subject: Re: Bug#1808: No boot parameters available on final boot disk 
In-Reply-To: Your message of "Mon, 06 Nov 1995 16:12:56 PST."
             <199511061512.QAA22117@dollar.daimi.aau.dk> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 06 Nov 1995 17:09:09 -0800
From: Bruce Perens <bruce@Pixar.com>

I will eventually fix the root disk to use syslinux when it creates the
boot floppies. In the meantime, here's a work-around:

Look at the files in /usr/lib/syslinux (install the "syslinux" package
if you don't have them) and use them to create a boot floppy, or use LILO
(package "lilo", documentation in /usr/doc/lilo) to set the hard disk boot
parameters.

	Thanks

	Bruce


--
See Pixar's "Toy Story", at a theater near you starting November 22.
"Toy Story" Toys and Soundtrack Album are available now!

Message received at debian-bugs:

From daimi.aau.dk!fwiffo Mon Nov  6 07:13:03 1995
Return-Path: <fwiffo@daimi.aau.dk>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0tCTEM-000F8IC; Mon, 6 Nov 95 07:13 PST
Received: from dollar.daimi.aau.dk by pixar.com with SMTP id AA29326
  (5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Mon, 6 Nov 1995 07:12:31 -0800
Received: (from fwiffo@localhost) by dollar.daimi.aau.dk (8.6.11/8.6.11) id QAA22117 for debian-bugs@pixar.com; Mon, 6 Nov 1995 16:12:56 +0100
From: Jan M|ller <fwiffo@daimi.aau.dk>
Message-Id: <199511061512.QAA22117@dollar.daimi.aau.dk>
Subject: No boot parameters available on final boot disk
To: debian-bugs@pixar.com
Date: Mon, 6 Nov 1995 16:12:56 +0100 (MET)
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Content-Length: 1472      

This bug is not a package bug, but a bug in the installprocedure.

I am using debian-0.93 R6

When I start installing debian from scratch using the boot disk, i
have to write:

boot: linux ether=5,0x300,eth0

As a boot-parameter or else the system freezes when coming to the 
'IP Protocols: ICMP, UDP, TCP'
part of the boot sequence

It seems that there are problems detecting my NE2000 compatible
netcard

That is not the problem that I wan't to report, cause when I type the
ether parameter it works fine. The problem appears when I have
installed the base system, and have made my second boot disk, which
will enable me to boot in the new debian system. When I boot on the
second boot disk, I can't give my ether-parameter, and thus the system
freezes again in the same spot 

So in order to fix the problem I had to remove the netcard, and boot
without it, which actually worked. Or, as I really did, boot Linux
from a previous Slackware-installation on an other hard-disk, and
mount the debian base system, and copy the kernel on to my a
dos-partition, and use 'loadlin' with the ether boot-parameter.

A solution might bo to prompt for bootparameters as on the first boot
disk.


- Jan Moeller

PS: I like debian :)

Jan Moeller   fwiffo@daimi.aau.dk   http://www.daimi.aau.dk/~fwiffo
Computer Science Department, Aarhus University. 
Ny Munkegade, DK-8000 Aarhus C, Denmark. Phone: + 45 89 42 32 21
'Eat recycled food. It's goot for the environment and OK for You!'

Your message didn't have a Package: line at the start (in the pseudo-header following the real mail header), or didn't have a psuedo-header at all.

This makes it much harder for us to categorise and deal with your problem report; please ensure that you say which package(s) and version(s) the problem is with next time. Some time in the future the problem reports system may start rejecting such messages.

Full text available.