[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: misc_(_at_)_openbsd_(_dot_)_org
- Subject: problems installing
- From: Horacio <homega_(_at_)_wanadoo_(_dot_)_es>
- Date: Tue, 4 Sep 2001 21:25:58 +0200
This I guess is a h/w related problem, but I would appreciate
if someone points out to other possible problem or other part
of h/w before I spend money on a replacement m/board.
I´ve tried installing the 03 and 26 aug i386 snapshots, and
now I´m trying with 26 sept. I had to disable pcibios at
UKC> prompt, else it does not recognize any scsi device (used
to with pcibios enabled, and dmesg does show them anyways).
There are three scsi devices attached to a AHA-2940AU card
(hd, zip and cd/dvd). Also an ide hd which I give to the
OpenBSD installation too.
dmesg shows them all, but when I´m asked which disk is the
root disk, it shows them in a strangely fashion:
sd0 sd1 sd18 wd0
So I ignore it and continue, getting to label both hds (sd0
and wd0), and even extracting the tarballs from the zip drive
(sd1) ... sometimes, as it reboots at some point!
On other occasions I can´t go that far and get these errors
Specify terminal type [vt220]
blah... Available disks are:
dmesg: sysctl: KERN_MSGBUF: Cannot allocate memory
Which disk is the root disk? 
it shows no disk, so I press enter and:
dmesg: sysctl: KERN_MSGBUFSIZE: Device not configured
again no disk, press enter and:
dmesg: syctl: KERN_MSGBUF: Bad address
And so forth. I had to change the power supply a few weeks
ago, as the old one burned due to high temperatures (oh yes,
I have one additional fan and had the box full-opened). This
makes me think that the m/board got f****d up at the time...
or may be something else?
Visit your host, monkey.org