From: claunia@claunia.com (Natalia Portillo)
Subject: [TUHS] DG/UX user/admin around?
Date: Tue, 24 Aug 2010 02:01:56 +0100 [thread overview]
Message-ID: <43599C01-574E-48C6-A192-8C587A814178@claunia.com> (raw)
In-Reply-To: <AANLkTinTbTke=2tGeQsHfk3G6_e9cdF7OvTKN+rCU2qK@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2100 bytes --]
Hi,
Just a question.
How did you checked the PCI bus and slot numbers?
Counting physically on the motherboard?
If this is the case you're doing it wrong.
The chipset could have various buses and slot numbers and so what appears physically to be slot 0 can easily be bus 2 slot 6.
El 11/08/2010, a las 15:14, DG UX escribió:
> Sorry to bother you all with my questions over this ancient machine
> and my failing trials with it..
> Trying to get a DGUX system (Intel based) to work, as is, on a 'regular' x86 PC.
>
> Just a couple of things :
>
> 1. I did find out that that DG machine is looking for an Adaptec PCI
> SCSI Controller, and so I got an AHA-2940UW PCI card, installed it in
> an old PC, got a matching 9GB HDD and booted it up from my image I've
> 'DD'ed from the original DG machine.
> Boot prompt came up and said it's trying to load
> sd(apsc(pci(0),d,0,7),1,0)root:/dgux -3
> it didn't, no error msg, just gave me back a "Boot command:" prompt.
> Bootpath of the original machine is sd(apsc(pci(0),d,0,7),1,0)root:/dgux -3.
> The disk drive parameters are correct, according to the docs, its -
> dev(ctrl(pci[pci_num]),slot[,func_num[,ctrl_id]])[,dev_id[,LUN]]).
> I've checked the PCI slot in which I installed the card, it's 3, and
> so I've tried '3' instead of 'd' in the command above, just got the
> boot prompt back again.
> Also tried - sd(apsc(pci(),3),0)root:/dgux -3 which should also work
> according to the docs (all other params are default).
> Tried to play with it and tried tons of combinations, just for the
> heck of it, still nothing. If I do type in some nonsense it does give
> me an error msg : "Error: No device specifications found in the boot
> command. Invalid boot command line".
> According to the docs, once I get the correct syntax, the system should load up.
> Anyone got any advice about that?
>
> 2. Anyone here a/was a DG/UX user/admin? you guys are very hard to find :)
>
> Thanks,
> D'
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
next prev parent reply other threads:[~2010-08-24 1:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 14:14 DG UX
2010-08-24 1:01 ` Natalia Portillo [this message]
2010-08-24 14:44 ` DG UX
2010-08-24 15:34 ` Natalia Portillo
2010-08-25 7:33 ` DG UX
2010-08-25 14:29 ` M. Warner Losh
2010-08-26 7:14 ` DG UX
2010-08-26 15:47 ` DG UX
2010-08-26 16:11 ` M. Warner Losh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43599C01-574E-48C6-A192-8C587A814178@claunia.com \
--to=claunia@claunia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).