brucer@sheoak.bcae (Bruce Rivendell) (05/07/90)
We have just upgraded an 11/780 from VMS to ULTRIX, and are having trouble with the Able VMZ/32N controller (used to be OK with VMS). doconfig interpreted it as a dmz controller, then wouldn't recognize it. I changed the config file entries to 4 similar to: device dmf0 at uba0 csrXXXXXXX flags 0xff vector dmfrint dmfxint without being sure that this was exactly the right entry. At startup this doesn't produce any errors, but when we try to connect via our micom is gets nowhere after the CONNECTED message. Any feedback, advice etc would be welcomed....please! Bruce Rivendell brucer@sheoak.bcae.oz Bendigo College of Advanced Education Victoria, Australia. Ph +61 54 447221
grr@cbmvax.commodore.com (George Robbins) (05/07/90)
In article <469@sheoak.bcae.oz> brucer@sheoak.bcae (Bruce Rivendell) writes: > We have just upgraded an 11/780 from VMS to ULTRIX, and are having > trouble with the Able VMZ/32N controller (used to be OK with VMS). > > doconfig interpreted it as a dmz controller, then wouldn't recognize it. > I changed the config file entries to 4 similar to: > device dmf0 at uba0 csrXXXXXXX flags 0xff vector dmfrint dmfxint I'm not sure that the two interfaces have enough in commmon for this to make sense. The auto-config probe routines just poke a the device enough to get an interrupt, so you could be misled into expecting further action. I'd contact Able and make sure that you have the most recent Microcode version and see if they can give you the standard "Berkeley" config file entries for their device. This failing, try over in comp.unix.wizards, since there are probably more people with BSD vs. Able problems over there. -- George Robbins - now working for, uucp: {uunet|pyramid|rutgers}!cbmvax!grr but no way officially representing: domain: grr@cbmvax.commodore.com Commodore, Engineering Department phone: 215-431-9349 (only by moonlite)
thorinn@skinfaxe.diku.dk (Lars Henrik Mathiesen) (05/08/90)
brucer@sheoak.bcae (Bruce Rivendell) writes: >We have just upgraded an 11/780 from VMS to ULTRIX, and are having >trouble with the Able VMZ/32N controller (used to be OK with VMS). >I changed the config file entries to 4 similar to: >device dmf0 at uba0 csrXXXXXXX flags 0xff vector dmfrint dmfxint >without being sure that this was exactly the right entry. >At startup this doesn't produce any errors, but when we try to connect >via our micom is gets nowhere after the CONNECTED message. This is what we use -- unchanged from 4.2BSD through Mt. Xinu MORE/bsd 12/89 release. Are you sure that you have 32 lines on your VMZ/32N? Ours only has 16 according to the manual. # 1 VMZ/32N emulating 2 DMF/32s # We do not need the carrier even though the vmz has it on all 16 lines device dmf2 at uba? csr 0160540 flags 0xff vector dmfsrint dmfsxint dmfdaint dmfdbint dmfrint dmfxint dmflint device dmf3 at uba? csr 0160600 flags 0xff vector dmfsrint dmfsxint dmfdaint dmfdbint dmfrint dmfxint dmflint I think that the "flags 0xff" means that the driver should not look at the carrier bit in the interface, but just act as if it is always on (one bit for each line). The many vectors are because our kernel also supports the line printer and synchronous line interfaces (with dual buffer DMA). -- Lars Mathiesen, DIKU, U of Copenhagen, Denmark [uunet!]mcsun!diku!thorinn Institute of Datalogy -- we're scientists, not engineers. thorinn@diku.dk