From owner-freebsd-stable Thu Jan 4 22:15:51 2001 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 4 22:15:46 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mass.osd.bsdi.com (dhcp244.osd.bsdi.com [204.216.28.244]) by hub.freebsd.org (Postfix) with ESMTP id 7C72137B400 for ; Thu, 4 Jan 2001 22:15:46 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f056SHt02906; Thu, 4 Jan 2001 22:28:23 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200101050628.f056SHt02906@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Rune Mossige" Cc: heckfordj@psi-domain.co.uk, freebsd-stable@FreeBSD.ORG Subject: Re: ASUS A7V and promise problems, SOLVED In-reply-to: Your message of "Tue, 02 Jan 2001 18:32:37 +0100." <005b01c074e2$03d9a500$2aa17dd4@kleppst.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Jan 2001 22:28:17 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The UHCI driver (at least) is very fragile in the presence of interrupts it's not expecting, or if the hardware is not behaving exactly as predicted (eg. it hasn't been initialised by the BIOS properly). In the general case, interrupt sharing between those two devices should actually work, and for your other (PCI) devices, you shouldn't have any problems with shared interrupts. > My problems about the promise appears to have been solved....it was an IRQ > conflict between the 3COM 3C905C and the onboard USB controller, both using > irq5. Why this caused the disks on the promise (irq 10) to fail, I do not > know.....Now I just ned to figure out how to get all adapters (SoundBlaster > Live!, 3com network adapter and RIVA TNT AGP adapter) to coexist happily > with their own IRQ's. > ----- Original Message ----- > From: "Rune Mossige" > To: > Cc: > Sent: 2. januar 2001 17:22 > Subject: Re: ASUS A7V and promise problems > > > > The Promise identifies itself as 'UltraDMA (tm) v2.01 (Build 33)' > > > > Prior to the BIOS upgrade earlier today from 1004d to 1005a, it identified > > itself as 'v2.01 (Build 28)' > > > > Is that the same version? This board boots, and dmesg output looks proper > to > > me. > > > > ----- Original Message ----- > > From: "Jamie Heckford" > > To: "Rune Mossige" > > Cc: > > Sent: 2. januar 2001 16:21 > > Subject: Re: ASUS A7V and promise problems > > > > > > > We had to send back about 50 ABit boards because they had the same > problem > > > on > > > ATA100 - Wouldnt boot FreeBSD, Linux, Windoze anything. > > > > > > Maybe the problem has affected the ASUS boards as well - would be > > > interesting > > > to know if they use the same / v. similar firmware. > > > > > > The problems we had were that we were not able to boot of any IDE/ATAPI > > > devices, we > > > installed FreeBSD using boot floppys and Network, however when booting > > from > > > an > > > IDE device no luck. > > > > > > Maybe dodgy, could be a BIOS issue. > > > > > > J > > > > > > On 2001.01.02 14:49:10 +0000 Rune Mossige wrote: > > > > I just bought myself a Christmas present, a new ASUS A7V, Amd Athlon > > 750, > > > > onboard Promise, and 2 x IBM-DTLA-30745 45GB ATA100 disks. > > > > > > > > In order to install FreeBSD 4.2, I also installed an older 540MB IDE > > > > disk. > > > > > > > > FreeBSD 4.2 was CVSUP'ed and buildworld/installworld done on 31. > > December > > > > 2000. > > > > > > > > FreeBSD boots fine, and finds the promise and disks. But, whenever > try > > > > to > > > > access the disks, the box freeze solid after 2-4 seconds....a hard > reset > > > > is > > > > required. > > > > > > > > New BIOS are also installed (1005a) with no luck. I have also reduced > > all > > > > relevant speed settings in the bios, with no luck. > > > > > > > > The disks are connected with brand new ATA100 cables. > > > > > > > > There is a working fan on the CPU, and I do not think it is too hot. > The > > > > BIOS reports MB at 33C and CPU at 41C. Both disks are primary on their > > > > own > > > > Promise channel. > > > > > > > > Is there anyone who have some hints as to what might be wrong? I have > > > > rebuilt the kernel (GENERIC) and enabled debug. Everything else is > left > > > > as > > > > defaults. But, there is no core, no debug, nothing. Just solid freeze. > > > > > > > > > > > > > > > > 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 > > > > > > > > > > > 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 -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message