Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 1 Aug 2002 09:13:40 -0400
From:      "Tim Strike" <tstrike@zaq.com>
To:        <stable@freebsd.org>
Subject:   RE: FreeBSD 4.6 Installation on SCSI-only server - SOLVED -- USB RELATED
Message-ID:  <0802E6A56AA390479CD80AD308CA66343F3205@zaq-msg-02.corp.zaq.com>

next in thread | raw e-mail | index | archive | help
Thanks to some good advice from Sean, it turned out that these servers =
had
disabled USB IRQ's, so that no IRQ was being generated by the system =
BIOS
resulting in a hang during boot of the 4.6/4.5 kernels.  After enabling =
the=20
USB IRQ, the installation proceeded without problem.  Apparently, this =
was
introduced around 4.4 with new PCI routing code MFC's.

I guess the remaining question(s) are:

1) Why is the USB IRQ required by the later 4.x releases -- especially =
if
we don't want USB (and shouldn't it recover more gracefully?)

2) If this is a known "common" problem should it be noted in UPDATING

.ts

-----Original Message-----
From: Tim Strike=20
Sent: Thursday, July 25, 2002 2:38 PM
To: scsi@FreeBSD.ORG; stable@FreeBSD.ORG
Subject: FreeBSD 4.6 Installation on SCSI-only server


I'm attempting to install FreeBSD 4.6-RELEASE on several i386 systems
(clones) that have dual SCSI and no IDE disks.  These systems are=20
currently running an older version of FreeBSD (3.3 through 3.5, I'm
not sure how they were installed as that pre-dates me tenure).

The installation of 4.6-RELEASE locks shortly after a message=20
regarding ppc0 (something to the effect of "ppc0: Parallel port not
found"), when I think it is looking for disk controllers or disk drives.
For kicks, I tried 4.5-RELEASE as well, and it failed in the same way.
When I get a chance, I'll try 4.4, 4.3 and 4.2 as well since those were=20
the last installations that I completed myself (on similar but not=20
identical hardware).

I've tried booting from floppy (to use a network install), and from both
SCSI and IDE CD-ROM.  I've tried the ATA workaround on the odd chance
that was the problem, but still no luck.

Has anyone experienced this kind of problem before?  Any ideas on how to
either fix it or get more information on what is going wrong (and what=20
it's trying to do just before lockup)?

Any help is appreciated.

Regards, -ts.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0802E6A56AA390479CD80AD308CA66343F3205>