SEO

Hi,

I rebuilt here an ancient HP9000/385. This machine is
necessary to operate a spectrometer.
In principle the new machine works fine, but there is a driver
problem.
To connect the machine to the spectrometer I have two interface
cards. One is a GPIO (select code 12) and one is a A/D converter
from TEAC (select code 18).
I installed all drivers with the exception of the A/D converter.

As a somewhat strange consequence the A/D converter is recognized
as a GOIO during startup. Here my dmesg


Apr 12 05:41
Internal HIL at 0x428000
CONSOLE is ITE
ITE + 1 port(s)
MC68040 processor
HP98620C DMA
Internal HP-IB Interface - system controller at select code 7
Parallel poll interrupts enabled.
HP98644 Advanced RS-232C Serial Interface at select code 9
With 16 byte rcv fifo, 16 byte xmit fifo, hardware handshake, and
high speed clock.
HP98622 GPIO Interface at select code 12
HP98265A (SCSI Interface) 5 MB/s; parity enabled at select code 14
HP98622 GPIO Interface at select code 18
HP98643 at select code 21
Parallel Interface at select code 23
HP98550 Bit Mapped Display at 0x560000
SCSI Bus: hard reset (isc: 14)
real mem = 16769024
using 268 buffers containing 1097728 bytes of memory
Root device major is 0, minor is 0x70000, root site is 0
Battery-backed real-time clock
WARNING: bad date in real-time clock--check and reset the date
Swap device table: (start & size given in 512-byte units)
entry 0 - auto-configured on root device; start = 247590, size =
49518
Warning: unable to configure dump device...using primary swap instead.
core image of 4095 pages will be saved at block 132174 on device
0x70000
avail mem = 13516800
lockable mem = 13414400


As you see, the GPIO itself is recognized correctly, but the A/D
converter is treated as GPIO.

My questions:

1. Where could I have a look for the driver?
I have application software for the spectrometer, but I have no
idea, where I could find the driver. An idea concerning the name
conventions of drivers would be helpful for the search.

2. How do I inform sam, that there is a driver for a special
interface card available?

3. Is there maybe a misconfiguration of the interface cards?
I took the unchanged A/D intercace card from the old computer
but I am not sure concerning the GPIO. To get a running HP9000/385
I had to provide a lot of spare parts from different sources and now
I have at least three GPIOs. ;-)


Maybe my questions are wrong here with respect to this ancient
machine. In this case I would be happy to get a hint for a more
appropriate group.

Thank in advance for any hint.

Rainer Haessner

Rainer Haessner wrote:
> Maybe my questions are wrong here with respect to this ancient
> machine. In this case I would be happy to get a hint for a more
> appropriate group.
>
> Thank in advance for any hint.

Try posting to comp.sys.hp.hardware

-Kirk

Rendrag Krik wrote:

> Rainer Haessner wrote:
>> Maybe my questions are wrong here with respect to this ancient
>> machine. In this case I would be happy to get a hint for a more
>> appropriate group.
>>
>> Thank in advance for any hint.
>
> Try posting to comp.sys.hp.hardware

What for? This is definitely a HP-UX-related question, and even HP9000
hardware problems are on-topic here since not everyone with HP-UX knowledge
has the time to look for a few HP-UX threads between hundreds of "my Deskjet
blabla doesn't work under xp" or "my Pavilion often crashes"...

Benjamin

Rainer Haessner <new@haessner.net> wrote:
[deleted]
> 1. Where could I have a look for the driver?
> I have application software for the spectrometer, but I have no
> idea, where I could find the driver. An idea concerning the name
> conventions of drivers would be helpful for the search.

I have not worked with the Series 300/400 for a long time, but IIRC
driver 'names' (actually keywords) are used in the 'dfile'. IIRC, these
dfiles live in /etc/config and can have "dfile.*" like names as well.
For details, see the config(1M) manual page. It would be best if you had
the 'dfile' from the old system, i.e. before it was rebuilt.

> 2. How do I inform sam, that there is a driver for a special
> interface card available?

SAM is unlikely to be aware of or made to be aware of a non-HP/
non-supported device, i.e. don't use SAM, use config(1M) instead.

> 3. Is there maybe a misconfiguration of the interface cards?
> I took the unchanged A/D intercace card from the old computer
> but I am not sure concerning the GPIO. To get a running HP9000/385
> I had to provide a lot of spare parts from different sources and now
> I have at least three GPIOs. ;-)

IIRC, the address (Select Code) of a Series 300/400 card is set on the
card, with switches, so yes there could be an address conflict.

> Maybe my questions are wrong here with respect to this ancient
> machine. In this case I would be happy to get a hint for a more
> appropriate group.

No, this group is fine. If you get no/few responses, you may want to
*add* other comp.sys.hp.* groups, but, as you said yourself, this is a
perfectly fine group for the HP-UX part and the general/non-PC hardware
part.

On 16 Apr 2004 01:47:51 -0700, Rainer Haessner wrote:

>Hi,
>
>I rebuilt here an ancient HP9000/385. This machine is
>necessary to operate a spectrometer.
>In principle the new machine works fine, but there is a driver
>problem.
>To connect the machine to the spectrometer I have two interface
>cards. One is a GPIO (select code 12) and one is a A/D converter
>from TEAC (select code 18).
>I installed all drivers with the exception of the A/D converter.
>
>As a somewhat strange consequence the A/D converter is recognized
>as a GOIO during startup. Here my dmesg
>
>
(Snip)

>
>Rainer Haessner

Is the part number for the SCSI interface correct? I thought it was 98658
for
a SCSI interface. Or is this a builtin SCSI interface.

I would suspect one of your boards might be causing an addressing
conflict. What happens if you take out all of the boards except for the
TEAC interface? What boot up messages do you get then?

Also, is the BIOS level on the 382 the same as on the old machine? A
older BIOS might have trouble recognizing some interfaces.


Aidan Grey

Hi Frank and Aidan,

"Aidan Grey" <apgrey@nospam.con> wrote:

> >As a somewhat strange consequence the A/D converter is recognized
> >as a GOIO during startup. Here my dmesg
> >
> >
> (Snip)
>
> >
> >Rainer Haessner
>
> Is the part number for the SCSI interface correct? I thought it was
98658
> for
> a SCSI interface. Or is this a builtin SCSI interface.

Thank you very much for your valuable responses.
You gave me a lot of hints for the further search.

In detail:

The SCSI device is part of the CPU card. The CPU card
contains SCSI, LAN, HP-IB, HP-IL, RS-232 and speaker
output.
Until now, the SCSI interface is unused. The old computer
ran with a HP-IP disk and I have no original HP-SCSI disk.
That's why I had to begin with that HP-IB disk to create
an appropriate Filesystem at the SCSI disk. Unfortunately
the old kernel was not compatible with the 68040 CPU
(exception FFFFFFe4 or somewhat comparable ...). That's
why I had to do a complete reinstallation and of course
I lost all prevous informations. -(

>
> I would suspect one of your boards might be causing an addressing
> conflict. What happens if you take out all of the boards except for the
> TEAC interface? What boot up messages do you get then?

A very good idea. I will check out this as soon as possible.
Unfortunately I am out of lab for a week.

>
> Also, is the BIOS level on the 382 the same as on the old machine? A
> older BIOS might have trouble recognizing some interfaces.

The old machine was equipped with a 68030 processor. I assume,
that machine had the older BIOS. But of course I am far from being
sure concerning this fact. What could I do to update the BIOS?
I still have the old board but maybe it is damaged. The original
problem was a fault of the power supply. I got a new power supply,
but this new power supply was damaged 2 seconds after power on.
That's why one of the cards seems to be damaged. I wanted to
exchange the cards piece by piece but due to lucky circumstances
I got the machine with the new processor and the doubled amount of
memory (and the additional SCSI interface).

Once again thank you very much for your and Franks help.

Rainer

Rainer Haessner wrote:

> Until now, the SCSI interface is unused. The old computer
> ran with a HP-IP disk and I have no original HP-SCSI disk.

You don't need an original HP SCSI disk. The few remaining 68k-based HP9000
in our company run with plain old Seagate and IBM 1GB and 2GB drives...

Benjamin