'd morning 8)
We received a UDB (Universal Desktop Box) from our
local dealer 2 days ago, and I'm currently testing if it's
worth buying additional campus-licenses for this box and
install DUnix on it or if we have to bite the dust and
install Linux on it.
So I grabbed the V3.2C DUnix Installation-CD, booted
and voila: It seemed to work. Some errors came up, but
who cares 8) Well, when trying to do a netsetup i discovered
that it might be worth looking at the error-messages, since
there was no way to connect to our local ethernet.
so here is what might be the cause (booting genvmunix):
[...]
Digital Unix V3.2C (Rev.148)...
[...]
(PCI ISA) System running at 167 MHz
Firmware revision: 3.5-72
PALcode: OSF version 1.35
Unsupported PCI configuration header found
Module c028:c1 not in pci_option data table, can't configure it
Module 1e03:0 not in pci_option data table, can't configure it
Module 1cd:0 not in pci_option data table, can't configure it
Module 1e03:0 not in pci_option data table, can't configure it
Module 1ab:0 not in pci_option data table, can't configure it
Module 1e03:0 not in pci_option data table, can't configure it
Module 1e03:0 not in pci_option data table, can't configure it
pci0 at nexus
psiop0 at pci0 slot 6
Loading SIOP: script 8019000, reg 81000000, data 40c9d898
scsi0 at psiop0 slot 0
rz0 at [...]
[...]
tu0: DECchip 21040-AA: Revision 2.3
tu0 at pci0 slot 8
tu0: DEC TULIP Ethernet Interface, hardware address 08-00-2B-E4-31-91
tu0: autosensing: selected AUI (10Base5) port: no carrier
[...]
a) "Module not in pci_option" pops up on both Multia (which was
100% running on the net with WinNT) and UDB.
b) The same problem with "tu0: autosensing...port: no carrier"
on both boxes.
c) The installation was no problem at all, but i cannot get the ethernet
working. No, there is NO chance of broken cables, network trouble etc.
There are other machines connected to this 10Base5, the (ex-)Multia
was connected there 1 day ago.
I heard some people succesfully installed DUnix on either Multia or UDB,
and i wonder how they did this. (wouldn't make sense to run unix on a
machine which isn't connected to a network, would it ? 8)
1) So how did they (you?) do this ?
2) Are there ways to fix these pci_option-table-errors ?
3) Firmware states something like "BL 3.5". I grepped the whole
Firmware-CD, the whole firmware-ftp.digital.com trying to
figure out what firmware might fix this. But it seems like
Multia's and UDB's don't have firmware 8) (at least none to
update). I wonder if it's possible to try to burn pciaxp33-firmware
on such a box (didn't try this, because of the big questionmark:
"What to do, if updating firmware fails and leaves the flashrom empty ???"
I know I loose support if i overwrite firmware, but who cares as long
as alpha-osf-managers_at_ornl.gov is alive 8))))
Any experiences ? Any hints, patches, firmwares, dip-switches ?
regards,
Peter
##===========================##============================================##
Dipl.Ing. Peter Marquardt/// SysAdmim Max-Planck-Institute Molecular Genetics
|| /// || --==> Earth-Germany-Berlin-Dahlem <==-- ||
:: +49-30-8413-1230 \\\/// :: marquardt_p_at_mpimg-berlin-dahlem.mpg.de ::
.. wwwutz on IRC \XX/A4k .. marquardt_p_at_fhi-berlin.mpg.de ..
..===========================..============================================..
Received on Fri Apr 26 1996 - 11:11:53 NZST