openbsd gurus,
As my saga continues...
I have a newly built server on which I am attempting to install
openbsd 4.0. Problems occurred on install of sets, where comp
set keeps throwing errors. Suggestion was made that it was probably
a bad CD. Try a previous CD of an earlier version. I had 3.9
Maxim,
> >set keeps throwing errors. Suggestion was made that it was probably
> >a bad CD. Try a previous CD of an earlier version. I had 3.9
> >available. The logs of the attempts are posted at:
>
> In my case when I had the same problem it was the CD-rom reader that
> was bad. Replacing cdr
I've seen this before. On old HP gear. Is your HP? Only FreeBSD would
run on the system. NetBSD/OpenBSD dead in the water. Some obscure bug
when the I/O went up (Symbios SCSI).
One of many reason why I want nothing to do with HP (H-PHUX) ever again.
Anyway, how about underclocking your Du
John Mendenhall <[EMAIL PROTECTED]> writes:
> So, based on these logs, from different openbsd cd versions,
> my hypothesis is there is some weird sort of hardware problem.
> My question is, what tools do you all use to determine where
> the hardware problem could be?
google turns up a few referen
> Things to try (in any order you please):
> 1. check IDE cables
> 2. check whether Master/Slave/CS settings are correct
> 3. In case Brian is right, you might want to put CD on the same cable
> as hd0, to slow-down IDE.
> 4. also check where you disks are connected - to IDE bus or to ATA-133
> con
Peter,
> google turns up a few references on various BSD mailing list for the
> search string "OpenBSD ffs_valloc: dup alloc". No clear cut
> solutions, but the popular suspicion runs in the direction of buggy
> (S)ATA controllers or, of course, possibly subtle, hard to trigger
> bugs in the oper
Brian,
> I've seen this before. On old HP gear. Is your HP? Only FreeBSD would
> run on the system. NetBSD/OpenBSD dead in the water. Some obscure bug
> when the I/O went up (Symbios SCSI).
>
> One of many reason why I want nothing to do with HP (H-PHUX) ever again.
>
> Anyway, how about
> > Anyway, how about underclocking your Duron some? Reset the BIOS timings
> > and power levels to failsafe? The old K7+VIA Chipset boards were a rough
> > crowd.
>
> This is a custom white box server, all put together.
> It is not an HP.
> I will try to reset the bios timings and power level
8 matches
Mail list logo