A2410... how the heck do you use it!?
(Mark D. Manes), Norfolk State University
I am in the need for a bit of information. We just got an Amiga 3000UXG
at the Amiga dealership where I work. It has 8 megabytes of memory and
has the University of Lowell board in it. It (unfortunately) came with
Amiga UNIX v1.1.
Now the questions:
- Does Amiga UNIX 1.1 support the Lowell board? If so, how do we
make it work under X?
- The UNIX kernal only seems to know about 4 megabytes of memory and
the system has 8. How do we change it?
- Are two monitors required if you want to see system boot messages
when the system is first started?
- How many of you have the UofL card? Did you get any documentation or
software with it? When I tried to use ADpro 2.0 at the store on the
system it complained that 'a2410.device' could not be found. Alas,
no A2410 disks of any type were shipped with the system.
Thanks all for your help.
-mark=
ma...@vger.nsu.edu
"CDTV - It's an Amiga!"
Frank Crash Edwards
>Greetings,
>
>I am in the need for a bit of information. We just got an Amiga 3000UXG
>at the Amiga dealership where I work. It has 8 megabytes of memory and
>has the University of Lowell board in it. It (unfortunately) came with
>Amiga UNIX v1.1.
Lucky you! :-(
I'm going to try some of these from memory, but any of you other folks
feel free to just jump in!
>Now the questions:
>- Does Amiga UNIX 1.1 support the Lowell board? If so, how do we
> make it work under X?
Wasn't there a "-tm" option under 1.1? I don't recall. There was a
posting here a long time ago that listed what the effects were of each
of the integer values that could follow the "-tm" option. (If anyone
kept a copy of that, would you please send it to me?)
>- The UNIX kernal only seems to know about 4 megabytes of memory and
> the system has 8. How do we change it?
There are other memory models in /stand; you need to do something like:
# cd /stand
# adb
---
make some patches to A3008unix to tell it which
partitions are the boot, swap, and root partitions.
see your ROOT installation floppy, /etc/profile, for details:
# mount -r /dev/dsk/fd0 /mnt
# cp /mnt/etc/profile /tmp
# umount /mnt
---
# (cat coff.boot; cat A3008unix) > /dev/<boot_partition>
>- Are two monitors required if you want to see system boot messages
> when the system is first started?
Huh? You mean one cable for the UofL board and one for the system console?
Yes, so far. Under 2.0 you can tell the system to startup "xdm" when it
boots, which immediately brings up a login screen under X Windows. (This
may be possible under 1.1, but it's pre-configured under 2.0)
>- How many of you have the UofL card? Did you get any documentation or
> software with it? When I tried to use ADpro 2.0 at the store on the
> system it complained that 'a2410.device' could not be found. Alas,
> no A2410 disks of any type were shipped with the system.
Then you're missing software. Under Amix, the appropriate code is part
of the X server (and one external file downloaded to the TIGA board).
Yes, I've got one of the DMI Resolver boards, but I haven't gotten any
software from them yet. I talked to a guy out in CA a few weeks ago,
and was told they'd let me beta-test the Amix code, but I haven't heard
anything recently (I'll have to call him on Monday...) The Resolver
is a TIGA board, 34010 @ 60MHz. Mine has 2MB video RAM, 8MB of program
RAM (DRAM) for downloading code to the board.
>Thanks all for your help.
I'm sure others will jump in if I got this wrong...
>-mark=
>ma...@vger.nsu.edu
>"CDTV - It's an Amiga!"
^^^^^^^^^^^^^^^^^^^^^^
Don't let Gail Wellington hear you say that!!
--
Frank J. Edwards, Owner Edwards & Edwards Consulting, Unix / AmigaDOS
2677 Arjay Court Voice: (813) 786-3675 (with answering machine)
Palm Harbor, FL 34684-4505 Data: (813) 787-3675 (2400 baud)
Jan Carlson
>
> I am in the need for a bit of information. We just got an Amiga 3000UXG
> at the Amiga dealership where I work. It has 8 megabytes of memory and
> has the University of Lowell board in it. It (unfortunately) came with
> Amiga UNIX v1.1.
Get an upgrade to AmigaUNIX 2.0 as soon as possible.
>
> Now the questions:
> - Does Amiga UNIX 1.1 support the Lowell board? If so, how do we
> make it work under X?
Yes, AmigaUNIX 1.1 does support the Lowell board. Use a high
resolution multisync monitor capable of 1024x768 pixels. More
affordable monitors such as the Commodore 1950 will support 800x600
pixels.
1. Connect the monitor to the normal 31mhz port.
2. Log in on screen except Alt-F1.
3. For 1024x768 color on the Lowell board, type:
olinit -- tiga
For 800x600 color on the Lowell board, type:
olinit -- tiga -tm 3
For 640x480 pixels black and white on the 15 or 31mhz ports, type:
olinit
4. Reconnect the monitor to the Lowell board if needed.
5. You will notice some flicker with -tm 3. To clear it, type:
1950_kludge
Other X Notes:
o AmigaUNIX 2.0 has 1950_kludge, 1.1 does not. SEE NEXT POST.
o On AmigaUNIX 2.03, replace "tiga" with "-tiga" in X and olinit commands.
o X needs 20mb of swap space for reliability.
o X needs 8mb of fast ram for speed.
> - The UNIX kernal only seems to know about 4 megabytes of memory and
> the system has 8. How do we change it?
Your hard drive was installed in a machine that had 4mb of memory, so
that is what it is using. If you get AmigaUNIX 2.0 you don't have to
do anything. It will automatically use all available memory. For
version 1.1 you can reinstall from tape or follow these steps:
1. Find your hard disk scsi id. As root, type:
devnm /
The reply will be this if your scsi disk id is 6:
/dev/dsk/c6d0s1 /
2. Find the partition number of your Unix_Boot partition.
Lets say your disk is scsi id 6. Then type:
rdb -H /dev/dsk/c6d0s0
The reply will include this line if the Boot partition is partition 3:
3: Unix_Boot 999999 4096 2mb
3. Load the kernel. If you know that the boot partition is
the 3rd partition on the disk at scsi id 6, and you have 8mb
of fast ram, type:
cd /stand
ln A3008unix unix
cat coffboot unix >/dev/dsk/c6d0s3
shutdown -y -g0 -i6
4. Reinstall from tape (preferably AmigaUNIX 2.0) if you make a mistake
in step 3 and your machine does not come up again.
> - Are two monitors required if you want to see system boot messages
> when the system is first started?
Just attach the monitor to the normal 31 or 15mhz port when you are
booting. If you type "cat /dev/noise&" in an xterm or olterm, system
messages will be redirected to that window.
To shutdown, first close down X, connect the monitor to the 31 or
15mhz port and "cd /" on Alt-F1.
>
> Thanks all for your help.
You're welcome.
--------------------------------------------------------------------------
Jan Carlson ja...@amix.commodore.com Product Assurance
Peter da Silva
> The reply will be this if your scsi disk id is 6:
> /dev/dsk/c6d0s1 /
That doesn't make sense. Wouldn't that be c0d6s1? What naming conventions do you
use if you have multiple disk controllers? What does c6d1s1 refer to?
--
-- Peter da Silva
-- Ferranti International Controls Corporation
-- Sugar Land, TX 77487-5012; +1 713 274 5180
-- "Have you hugged your wolf today?"
Markus Wild
> 1950_kludge
Could you explain what this kludge does exactly? With my monitor (not a 1950..)
applying it makes it lose its Sync completely...
>o On AmigaUNIX 2.03, replace "tiga" with "-tiga" in X and olinit commands.
Which makes me ask, is the 2.03 tiga server part considerably different to
the 2.02 one?? 2.02 is a very stable OS version (compared to its ancestors;-))
BUT the tiga server.. That one could probably easily get the `mosty buggy'
award of the package ;-)
>Jan Carlson ja...@amix.commodore.com Product Assurance
Nice to see there's someone back at Commodore caring for Unix ;-)
-Markus
--
Markus M. Wild - mw...@iiic.ethz.ch | wi...@nessie.cs.id.ethz.ch
A transistor protected by a fast-acting fuse will protect the fuse by
blowing first.
Mike Ford Ditto
pe...@ficc.ferranti.com (Peter da Silva) writes:
>> The reply will be this if your scsi disk id is 6:
>> /dev/dsk/c6d0s1 /
>
>That doesn't make sense. Wouldn't that be c0d6s1?
No. The disk controller at SCSI ID 6 is "c6". If that controller had
multiple disks attached to it, they would be "c6d0", "c6d1", etc. But
for most SCSI disks, the controller is built in to the drive, so the
combined unit is "c6d0".
>What naming conventions do you use if you have multiple disk controllers?
I think you mean multiple SCSI interfaces, in which case we just keep
counting SCSI addresses (c9d0 for ID 1 on the second SCSI bus). That is
pretty arbitrary but was considered preferable to making everyone use
longer names (/dev/dsk/s1c1d0s0) even though few people have more than
one SCSI bus.
>What does c6d1s1 refer to?
SCSI ID (controller) 6, SCSI LUN (drive) 1, partition (slice) 1. Since
SCSI disk controllers that control more than one drive are becoming
quite rare and were never shipped with Amigas, Amiga Unix doesn't
actually support LUNs other than zero.
-=] Ford [=-
"Look over there!... A dry ice (In Real Life: Mike Ditto)
factory -- a good place to get fo...@yoda.uucp
some thinking done." uunet!cbmvax!kenobi!ford
- Talking Heads, "Cities"
peter da silva
> In article <id.RW...@xds13.ferranti.com>
> pe...@ficc.ferranti.com (Peter da Silva) writes:
> >> The reply will be this if your scsi disk id is 6:
> >> /dev/dsk/c6d0s1 /
> >That doesn't make sense. Wouldn't that be c0d6s1?
> No. The disk controller at SCSI ID 6 is "c6". If that controller had
> multiple disks attached to it, they would be "c6d0", "c6d1", etc. But
> for most SCSI disks, the controller is built in to the drive, so the
> combined unit is "c6d0".
Are there any significant SCSI controllers not built into the drive, apart
from adaptors? How many SCSI controllers out there in the real world support
more than one drive?
Certainly, having a clean aming scheme for multiple disk types would be
more generaly useful. Intel does this: the first SCSI bus is c0d[0-7]s?
We have systems with multiple types of drives here (though we haven't yet
mixed SCSI with ESDI, we could).
> >What naming conventions do you use if you have multiple disk controllers?
> I think you mean multiple SCSI interfaces,
No, I mean multiple disk controllers. Say, a SCSI bus and a couple of IDE
drives (in a souped up Amiga 500) or MFM drives (in a 2000 with a 209x).
What would the non-SCSI drives be called?
> >What does c6d1s1 refer to?
> SCSI ID (controller) 6, SCSI LUN (drive) 1, partition (slice) 1. Since
> SCSI disk controllers that control more than one drive are becoming
> quite rare and were never shipped with Amigas, Amiga Unix doesn't
> actually support LUNs other than zero.
So then it's always gotta be "d0", right?
I agree that *technically* you're correct, but the Intel naming convention
seems more natural and useful.
Jan Carlson
> Could you explain what this kludge does exactly? With my monitor (not a 1950..)
> applying it makes it lose its Sync completely...
1950_kludge should be run ONLY if you ran olinit, etc. with "-tm 3".
It tweeks the Lowell board in a way that helps only in "-tm 3" mode.
> Which makes me ask, is the 2.03 tiga server part considerably different to
> the 2.02 one??
The X server on AmigaUNIX 2.03 has significant improvements over 2.02.
Mike Ford Ditto
>>5. You will notice some flicker with -tm 3. To clear it, type:
>> 1950_kludge
>Could you explain what this kludge does exactly? With my monitor (not a
>1950..) applying it makes it lose its Sync completely...
1950_kludge directly pokes the A2410 hardware to increase the scan
rate to a point that is still within the 1950 specs but has less (no)
visible flicker. A better solution would be to fix the X server's
builtin scan rate for its "mode 3", but since we didn't want to
re-open the fairly stable 2.0 X server for new changes, it was safe
and easy to throw in the 1950_kludge program that we had had around
for a while.
For some unknown reason, the 1950_kludge program was broken in 2.02
(it worked in 2.01, and was supposedly fixed for 2.03).
>Which makes me ask, is the 2.03 tiga server part considerably different to
>the 2.02 one?? 2.02 is a very stable OS version (compared to its ancestors;-))
>BUT the tiga server.. That one could probably easily get the `mosty buggy'
>award of the package ;-)
The 2.02 and 2.03 TIGA X servers are beta versions only. I think C=
got a few bug fixes into 2.03, but it's still basically the same code.
I think there is still some chance of a final, supported TIGA X server
coming out of Commodore (most of the work of it has been done), but I
haven't seen much sign of it lately.
-=] Ford [=-
"But everybody wants a rock (In Real Life: Mike Ditto)
to wind a piece of string around." fo...@yoda.uucp
- They Might be Giants, uunet!cbmvax!kenobi!ford
"We want a rock"
The Laughing Prophet
>the 2.02 one?? 2.02 is a very stable OS version (compared to its ancestors;-))
>BUT the tiga server.. That one could probably easily get the `mosty buggy'
>award of the package ;-)
It does seem rather buggy, doesn't it? I never knew xv was allowed to
cause kernel panics or, worse yet, lockups bad enough to keep the kernel
from panicing.
Obviously, a newer version of the tigagm.coff file (not to mention *any*
amigados support) would be great. :)
>-Markus
>--
>Markus M. Wild - mw...@iiic.ethz.ch | wi...@nessie.cs.id.ethz.ch
>A transistor protected by a fast-acting fuse will protect the fuse by
>blowing first.
-s
--
se...@acc.stolaf.edu "Forgive them, Father, for they do not get the joke."
Amiga - Hack or die. Reading news so I can put off my work.
Unix - Live free or die. Monogamy is a disease.
em was tsrif uoy woh morf sdrawkcab em ypoc - a.2.2 suriv erutangis.
Mike Ford Ditto
se...@asgaard.acc.stolaf.edu (The Laughing Prophet) writes:
>It does seem rather buggy, doesn't it? I never knew xv was allowed to
>cause kernel panics or, worse yet, lockups bad enough to keep the kernel
>from panicing.
Of course, xv, no matter how buggy it might be, wouldn't cause a panic
or system crash unless there was a bug in the kernel. No such panics
or lockups related to "xv" have been reported to Commodore. If
someone knows of a system panic or lockup, especially a repeatable
one, it should be reported.
This reminds me to point out that even though Commodore "reduced" its
Unix development staff, it is still useful to send bug reports to
bu...@amix.commodore.com. There are still people at Commodore who read
these reports and at least consider fixing them (although their
resources are rather limited). And some of the original developers
still have access to the bug list and volunteer their knowledge or
theories about problems when they are reported.
-=] Ford [=-
"A just machine to make big decisions (In Real Life: Mike Ditto)
programmed by fellows with compassion fo...@yoda.uucp
and vision." - Donald Fagen, "IGY" uunet!cbmvax!kenobi!ford