[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#38517: marked as done ([slink] Debian 2.1 Install Hangs)



Your message dated 26 Mar 2000 04:59:40 -0500
with message-id <oag0te9hmb.fsf@arroz.fake>
and subject line bugs closed in potato boot-floppies
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Darren Benham
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 29 May 1999 12:46:54 +0000
Received: (qmail 4328 invoked from network); 29 May 1999 12:46:54 -0000
Received: from corpmail1.jps.net (209.63.224.250)
  by master.debian.org with SMTP; 29 May 1999 12:46:54 -0000
Received: from dellbox (209-239-214-34.lax.jps.net [209.239.214.34])
	by corpmail1.jps.net (8.9.0/8.8.5) with SMTP id FAA03724
	for <submit@bugs.debian.org>; Sat, 29 May 1999 05:45:30 -0700 (PDT)
Message-ID: <000401bea9d1$5dd5bc20$22d6efd1@dellbox>
Reply-To: "Tom Harincar" <tomh@quad.com>
From: "Tom Harincar" <tomh@quad.com>
To: <submit@bugs.debian.org>
Subject: Debian 2.1 Install Hangs
Date: Sat, 29 May 1999 05:47:08 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3


I'm trying to install Debian Ver. 2.1 (I'm a first timer with
Debian.) I changed the bios to boot from the CD and everything seems
to proceed correctly until it gets to the following:

aha152x: BIOS test: passed, auto configuration ok, detected 1
controller(s)
aha152x0: vital data: PORTBASE=0x340, IRQ=12, SCSI ID=7,
reconnect=enabled, parity=enabled, synchronous=disabled, delay=100,
extended translation=disabled
aha152x: trying software interrupt, ok.
Failed initialization of WD-7000 SCSI card!
scsi0: Adaptec 152x SCSI driver: $Revision $
scsi : 1 host.
Vendor MICROP    Model 1578-15    UP Rev:  DG02
Type: Direct-Access               ANSI SCSI revison: 01 CCS
Detected scsi disk sda at scsi 0, channel 0, id 0, lun 0
scsi0 : channel 0 target 0 lun 1 request sense failed, performing reset.
scsi bus is being reset for host 0, channel 0.

At this point, the process hangs and I have to reboot.  I tried some
alternate boot arguments as per the Install Help screen and per the scsi
Howto but no success.  Maybe I had the syntax wrong because I couldn't even
continue the boot.  It kept coming back with an error "unable to find boot
image"

The actual device is an old (and I mean old) combination QIC tape drive with
a small hard drive that I don't even .  The thing is, Red Hat, Caldera and
SuSE all have no problem detecting this thing properly.


Do you folks have any ideas?  What is the proper form of a boot argumant in
Debian?  Where is the message about a "WD-7000 SCSI card" coming from? I've
not seen that on any other install.

TIA for any tips you can provide

****************************************************************
Tom Harincar <tomh@quad.com>
Quadratron Systems
2899 Agoura Road, Suite 107
Westlake Village, CA 91361
Phone: (805) 495-7774
Fax:      (805) 495-3606
Web:    www.quad.com
****************************************************************



---------------------------------------
Received: (at 38517-done) by bugs.debian.org; 26 Mar 2000 09:07:27 +0000
Received: (qmail 17109 invoked from network); 26 Mar 2000 09:07:26 -0000
Received: from 209-122-226-105.s359.tnt1.nyw.ny.dialup.rcn.com (HELO arroz.fake) (@209.122.226.105)
  by master.debian.org with SMTP; 26 Mar 2000 09:07:26 -0000
Received: by arroz.fake (Postfix, from userid 421)
	id 0C6459385A; Sun, 26 Mar 2000 04:59:41 -0500 (EST)
Sender: apharris@arroz.fake
To: 37721-done@bugs.debian.org, 34331-done@bugs.debian.org,
	35195-done@bugs.debian.org, 35338-done@bugs.debian.org,
	35638-done@bugs.debian.org, 38517-done@bugs.debian.org,
	42356-done@bugs.debian.org, 38721-done@bugs.debian.org,
	39133-done@bugs.debian.org, 39815-done@bugs.debian.org,
	42109-done@bugs.debian.org, 42211-done@bugs.debian.org,
	42811-done@bugs.debian.org, 49222-done@bugs.debian.org,
	52819-done@bugs.debian.org, 55060-done@bugs.debian.org,
	55144-done@bugs.debian.org
Subject: bugs closed in potato boot-floppies
From: Adam Di Carlo <adam@onshore.com>
Date: 26 Mar 2000 04:59:40 -0500
Message-ID: <oag0te9hmb.fsf@arroz.fake>
Lines: 25
User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.5
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii


We believe that the bug you reported has been fixed in the potato
boot-floppies, such as version 2.2.8 or higher.

Note that many boot problems are fixed in 2.2.8 since they use the 2.2
kernels.  There are many additional flavors of kernels for i386 as
well.

In some cases, bugs are closed due to lack of feedback from the user.

Many problems are also fixed by the inclusion of new packages from
Potato, such as makedev, modconf, etc.

The management of the boot sector has also changed, which solves many
problems.

We encourage you to test the potato boot-floppies on your system.  If
your problem persists, please either respond to debian-boot and CC
your original bug and we will reopen the bug, or else submit a new bug
against the boot-floppies package.

Thanks so much for helping to improve the debian installation system.

-- 
.....Adam Di Carlo....adam@onShore.com.....<URL:http://www.onShore.com/>


Reply to: