Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!howland.erols.net!news.nacamar.de!news.b-1.de.contrib.net!news.space.net!news.muc.de!eisbaer.bb.bawue.de!news.bawue.de!luva.lb.bawue.de!luva.lb.bawue.de!not-for-mail
From: migieger@luva.lb.bawue.de (Michael Giegerich)
Newsgroups: comp.unix.bsd.bsdi.misc
Subject: Re: compaq deskpro 2000 can't run BSDI 2.1
Date: 23 Nov 1996 10:36:11 +0100
Organization: BaWue-Net Ludwigsburg
Lines: 56
Message-ID: <576gib$f7t@luva.lb.bawue.de>
References: <32946DA4.5326@unitech.com.hk> <573r65$d6s@nike.volvo.se>
NNTP-Posting-Host: luva.lb.bawue.de
In article <573r65$d6s@nike.volvo.se>,
peter hakanson <peter@cyklop.volvo.se> wrote:
>We have had nasty problems with compac.
>
>One problem is (was?) that compac stores the 'bios' on
>a separate partition on the disk. Without this
>partition you dont have access to the normal setup stuff.
Compaq don't store their BIOS on disk, it's on E(E)PROM
like most others.
What Compaq do is to create a separate partition containing
important files (as they define them, e.g. config.sys or
windows.ini) and setup information.
When installing BSDI you have 2 choices:
- leave intact this Compaq partiton and give to BSDI
the rest (or part thereof) of the disk or
- never use Compaq setup anymore and then use the whole
disk for BSDI.
>A person wanted to adjust the setup, halted bsdi, and rebooted
>with the supplied compac setup diskette ("as the setup
>does not work anymore").
>
>When booting, the diskett software noticed that "hey there is
>no dos-partition here".. "hmm i'll make a tiny partition
>and store myself here"..
>
>Needless to say that bsdi had to be reinstalled :-(
See above.
>: The last week i got a BSDI internet server 2.1 and tried to install the
>: BSDI into a compaq deskpro 2000, but i got some troubles on
>: installation.
>
>: The install program always prompt "wd0: lost interrupt" "wd0: restting
>: controllor" when it try to copy the system files into the hard drive.
This looks like a hardware problem to me (a timing problem
of either the wd controller and/or the hard disk).
Perhaps it's also related to the wd driver of BSDI?
Did you try to swap the hard disk against another
brand/type? (the wd controller is on board?).
>: Today, my BSDI host prompt the error "wd0:lost interrupt" "wd0:restting
>: controllor" frequently and then down. After resetting the machine, the
>: system prompt me to run "fsck" manually to fix the disk problems. But
>: the fsck can't fix the disk completely, the system can't boot success
>: now!!
--
Michael Giegerich, E-Mail: migieger@luva.lb.bawue.de, Voice: +49 7144 39337