Re: Problem(s) installing OpenBSD/hppa 3.3 on a model 735/125

Peter Wright <[email protected]>
Newsgroups gmane.os.openbsd.hppa
Message-ID <[email protected]>
On 26/06 07:03:01, Paul Weissmann wrote:
> Peter Wright [[email protected]] wrote:
> > Hi all. I've got a HPPA/PA-RISC machine, model 735/125, that I've been
> > hoping I could turn into a replacement for my current (OpenBSD 3.0/i386)
> > gateway/firewall/mailserver machine.
[ snip the rest ]
> The problem is that the 8-bit SCSI chip on this machine (53C700) is
> not yet supported, so far as I know.

Aha. Now that I look on the OpenBSD/hppa page, I realise that this
SCSI controller is listed under the "Projects":

  * Support the NCR53C700 SCSI Narrow SE controller

D'oh. :(

> You mention NetBSD lifimage work fine - how far have you tried that
> and from which date?

The NetBSD lifimage I used is dated July 6 2002, as you can see below.
I grabbed it from:

ftp://ftp.netbsd.org/pub/NetBSD/arch/hp700/snapshot/20020706-1.6D/installation/lifboot/SYSNBSD.gz

Fairly old, but still the most recent snapshot available (I get the
impression the NetBSD/hp700 port has been stagnating for quite some
time).

The NetBSD/hp700 page - http://www.netbsd.org/Ports/hp700/ -
specifically lists "5 MB/s NCR 53C700 SCSI controller (osiop)" as
supported (in its otherwise rather small list of supported hardware).
Also, having just had a look through the recent NetBSD/hp700 mailing
list archives, I ran across this post:

"Both 53c700 (on 735/125) and 53c710 (on 712/60) SCSI are working.
(53c710 on EISA and 53c720 won't work, though)"

http://mail-index.netbsd.org/port-hp700/2003/05/11/0000.html

(BTW, is there an archive of the OpenBSD/hppa mailing list anywhere? I
had a look around but couldn't find one.)

Below is a transcript of me netbooting the SYSNBSD lifimage on my
735/125 - it appears that NetBSD/hp700 is designed to run diskless at
this stage; and I couldn't be bothered setting up the NFS root, so it
stops when trying to find an NFS to mount. You'll notice, however,
that it does appear to correctly identify and use the NCR53C700 SCSI
controller.

----------------------------------------------------------------------
Trying lan.0004e2-0b86db.0.0
Boot path initialized.
Attempting to load IPL.


Hard booted.



>> NetBSD/hp700 LIF Boot, Revision 1.1
>> ([email protected], Sat Jul  6 20:53:40 EDT 2002)
>> Enter "reset" to reset system.
Boot: [[[dk0a:]netbsd][-a][-c][-d][-s][-v][-q]] :-
4881296+118784+352256 [607360+135041]=0x628f00
Start @ 0x80000 [1=0x5f3000-0x6a8f00]...
SPID bits: 0x0, error = -2
[ using 745216 bytes of netbsd ELF symbol table ]
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002
    The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
    The Regents of the University of California.  All rights reserved.

NetBSD 1.6D (GENERIC) #0: Sat Jul  6 19:41:42 EDT 2002
    [email protected]:/data/union-hp700-c/src/sys/arch/hp700/compile/GENERIC
HP9000/735/130 (Snake Cheetah) PA-RISC 1.1
real mem = 128 MB (512 KB reserved for PROM, 58368 KB used by NetBSD)
avail mem = 51340 KB
using 1664 buffers containing 6656 KB of memory
mainbus0 (root) [flex fff80000]
pdc0 at mainbus0
mem0 at mainbus0 hpa fffbf000: viper rev 3, ctrl cd330000<lpmc_en,ipref_en> size 128MB
cpu0 at mainbus0 hpa fffbe000 irq 31: PCXL rev 0, lev 1, cat A, 125 MHz clk
cpu0: shadows, 256K/256K D/I caches, 120 shared TLB, 16 shared BTLB
cpu0: PCX-T (Rolex - CMOS-26B) floating point, rev 1
mongoose0 at mainbus0 hpa fc000000 irq 17: HWPC000 rev 34, 33 MHz
eisa0 at mongoose0
isa at mongoose0 not configured
asp0 at mainbus0 hpa f082f000 irq 28: Hardball rev 19, lan 1 scsi 7
gsc0 at asp0: wordleds
"Advanced audio (int.)" at gsc0 (type a, sv 7f) hpa f1000000 not configured
"Core FW SCSI" at gsc0 (type a, sv 7c) hpa f0830000 not configured
lpt0 at gsc0 hpa f0824000 irq 7
com0 at gsc0 hpa f0822000 irq 5: ns16550a, working fifo
com1 at gsc0 hpa f0823000 irq 6: untouched, assumed serial console
"Core HIL" at gsc0 (type a, sv 73) hpa f0821000 not configured
ie0 at gsc0 hpa f0826000 irq 8: v0.0 address 08:00:09:41:b6:44, type i82596DX
osiop0 at gsc0 hpa f0825000 irq 9: NCR53C700 rev 0, 31MHz, SCSI ID 7
scsibus0 at osiop0: 8 targets, 8 luns per target
"SGC Graphics" at mainbus0 (type a, sv 77) hpa f8000000 not configured
biomask 00000203 netmask 00000303 ttymask 000003a7
i82586_tint: command still busy; status=0x6c33; tail=0
iestatus = 0xa000
scsibus0: waiting 2 seconds for devices to settle...
sd0 at scsibus0 target 5 lun 0: <DEC, DSP3210S, 441G> SCSI2 0/direct fixed
sd0: 2048 MB, 3045 cyl, 16 head, 86 sec, 512 bytes/sect x 4194685 sectors
sd0: async, 8-bit transfers
Kernelized RAIDframe activated
sd0: no disk label
boot device: ie0
root on ie0
nfs_boot: trying DHCP/BOOTP
nfs_boot: DHCP next-server: 192.168.0.130
nfs_boot: my_addr=192.168.0.135
nfs_boot: my_mask=255.255.255.0
nfs_boot: getfh - no pathname
no file system for ie0
cannot mount root, error = 79
root device (default ie0): ie0: receiver not ready; scbstatus=0x5000
ie0: reset

----------------------------------------------------------------------

> 	- paul


Hm... Paul, do you know if anyone's likely to be working on an Open
driver for the NCR53C700 controller at the moment?  Actually, looking
again at my failed attempts with the OpenBSD "snapshot" lif33.fs
images, it _appears_ that the controller is being mis(?)- identified
as an NCR53C710 instead of a NCR53C700... 

------- snippet from OpenBSD "snapshot" lifimage boot ----------------
ie0 at gsc0 offset 26000 irq 8: i82596DX v0.0, address 08:00:09:41:b6:44
osiop0 at gsc0 offset 25000 irq 9: NCR53C710 rev 0, 31MHz, SCSI ID 7
scsibus0 at osiop0: 8 targets
osiop0: osiop_select while connected?

------- snippet from OpenBSD "snapshot" lifimage boot ----------------

Can anyone shed any light on this? Should the NCR53C700 controller
actually be identified as a NCR53C710, or is this a known bug?


Pete.
-- 
http://akira.apana.org.au/~pete/
infinite loop, n. See loop, infinite.
		-- The Devil's IT Dictionary
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.