From owner-freebsd-i386@FreeBSD.ORG Thu Jul 29 22:40:37 2004 Return-Path: Delivered-To: freebsd-i386@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 11D4516A4D0 for ; Thu, 29 Jul 2004 22:40:37 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECA6E43D72 for ; Thu, 29 Jul 2004 22:40:36 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id i6TMePgM002732 for ; Thu, 29 Jul 2004 22:40:25 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i6TMeOs4002731; Thu, 29 Jul 2004 22:40:24 GMT (envelope-from gnats) Date: Thu, 29 Jul 2004 22:40:24 GMT Message-Id: <200407292240.i6TMeOs4002731@freefall.freebsd.org> To: freebsd-i386@FreeBSD.org From: "Systems Admnistrator" Subject: Re: i386/63776: [boot] hang during boot on a toshiba p25 s509 series [5.x] X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Systems Admnistrator List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jul 2004 22:40:37 -0000 The following reply was made to PR i386/63776; it has been noted by GNATS. From: "Systems Admnistrator" To: , Cc: Subject: Re: i386/63776: [boot] hang during boot on a toshiba p25 s509 series [5.x] Date: Thu, 29 Jul 2004 18:42:42 -0400 This is a multi-part message in MIME format. ------=_NextPart_000_0001_01C4759B.D50E2070 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I have tried the solution you mentioned without any luck using fresh = disks and new 5.2.1 iso's from ftp5,ftp6 and = ftp13.freebsd.net . =20 I have spent many years using FreeBSD and successfully deploying it on a variety of platforms and have tried just about every possible solution = using various boot options without any success. I would like to note that a colleague of mine had a similar problem with = the a Toshiba p20 and that the solution mentioned by Gary worked for him = with limited success. He was able to install FreeBSD but after 5 successful subsequent boots = the same problem occurred and even adding=20 set hw.pci.allow_unsupportable_io_range=3D"1" to a boot config didn't help. =20 On attempt to boot off the disks afterwards he managed to achieve a successful boot to the installer on 1 out of every 5 tries=20 =20 Very Odd no ? =20 I'm at a loss myself . =20 If it's any consolation all versions of sunOS from 5.6 to current fail = due to problems with the Toshiba cardbus as well. =20 So at this point it's fair to say this Bug still exists and still has = not been fixed, nor is there an effective workaround. =20 Sincerely Joshua Harris ------=_NextPart_000_0001_01C4759B.D50E2070 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I have tried the solution you mentioned without any = luck using fresh disks and new 5.2.1 iso’s from ftp5,ftp6 and ftp13.freebsd.net.

I have spent many years using FreeBSD and = successfully deploying it on a variety of platforms and have tried just about every possible = solution using various boot options without any success.

I would like to note that a colleague of mine had a = similar problem with the a Toshiba p20 and that the solution mentioned by = Gary worked for him with limited success.

He was able to install FreeBSD but after 5 successful subsequent boots the same problem occurred and even adding =

set =
 hw.pci.allow_unsupportable_io_range=3D"1"

to a boot config didn’t help.

On attempt to boot off the disks afterwards he = managed to achieve a successful boot to the installer on 1 out of every 5 tries =

Very Odd no ?

I’m at a loss myself .

If it’s any consolation all versions of sunOS = from 5.6 to current fail due to problems with the Toshiba cardbus as = well.

So at this point it’s fair to say this Bug = still exists and still has not been fixed, nor is there an effective = workaround.

Sincerely Joshua Harris

------=_NextPart_000_0001_01C4759B.D50E2070--