Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: Quixote on June 22, 2003, 02:33:36 AM
-
;-) I just bought the appropriate 68 conductor cable and 68 pin 50 pin adaptor to hook my CD ROM drive to my CyperStormIII's SCSI III controller.
:-( Unfortunately, CD0 won't mount. SnoopDOS reports that the system cannot find cybppc.device, and neither can I. It doesn't seem to be included with the CyberStorm Install disks, nor on Aminet, et.al.
:-? Where would I be able to download this driver?
-
It's in the ROM of the PPC card. It is not a separate device handler like say ahi.device in devs:
5.Ram Disk:> version cybppc.device
cybppc.device 44.69
Do note that on the BPPC cards, its not called cybppc.device though.
-
First check if cabling is correct. SCSI bus termination matters a lot on the MK3. The SCSI cable must be *actively* terminated on *both* ends !
Then check if the SCSI ID of the CD-ROM is set correctly. Remember the number you set.
Then check the firmware menu (hold down Esc key during reset). Check that the SCSI bus is enabled (SCSI Patch or NCR Patch must be disabled) and check that the ID number you chose it not disabled.
Then look into the CD0 file and check that the unit number matches the SCSI ID you chose. Check the tooltypes of CD0's icon, too. Tooltypes override mountlist entries.
Finaly you could get the IDEfix archive from Aminet, unpack it to RAM: and start the FindDevice program. It will tell you if your CD-ROM drive is recognised. If it is, then you can read the correct values for device and unit from the program's listviews.
Bye,
Thomas
-
:-( Unfortunately, the trouble is more complicated than that. Currently, I have a SCSI hard drive terminated at the end of the chain, with the CD ROM unterminated in the middle. SCSI Inquire reports the hard drive as unit number 0 and the CD ROM as unit number 3. It even correctly reports the manufacturers' names, so I am confident that the connection is sound.
For whatever reason, CD0: does not mount, so the icon doesn't appear, and CD0: is not available in a DOpus lister.
It's probably down to the mountlist. The one supplied with the CyberStorm install disks differs from other CD mountlists in a number of particulars, but neither version will mount the drive. In fact, attempting to use the supplied mountlist will block some applications from launching, such as the shell, while other applications can still launch. I suspect that the Mount command is waiting on some event that isn't happening. A reboot is necessary to restore the 'miggy. SnoopDOS doesn't report anything wrong.
:-? Has anyone gotten a fifty pin SCSI CD ROM to run on the CyberStormIII's sixty-eight pin SCSI bus? How is it done? May I copy the mountlist?
-
Has anyone gotten a fifty pin SCSI CD ROM to run on the CyberStormIII's sixty-eight pin SCSI bus? How is it done? May I copy the mountlist?
The mountlist should not change.
-
KennyR kibitzed:
The mountlist should not change.
:-? Not even changing the device from scsi.device to cybppc.device, or the unit number from 1 (the default) to 3 (the scsi device number to which my CD ROM is set?)
And if these are "obvious" exceptions, what else are "obvious" exceptions that I've missed?
How about HighCyl=11000 when other CD ROM mountlists use HighCyl=999? I thought that the CD itself didn't change when moved from a CD ROM drive on a Warpdrive SCSI bus, to a CD ROM drive on a CyberStorm SCSI bus.
-
Please post your mountlist(s).
Bye,
Thomas
-
ot even changing the device from scsi.device to cybppc.device, or the unit number from 1 (the default) to 3 (the scsi device number to which my CD ROM is set?)
Well, that's pretty obvious. :-) Although I do prefer to use the UNIT and DEVICE as tooltypes on the mountfile icon... But apart from these, nothing should change. Your host controller still thinks its connected to a 50pin device. Besides which there is no difference in control codes between 50 and 64. Your drive should automatically 'downgrade' itself to SCSI-2 (64 pin drives are usually SCSI-3 or UW). This is transparent.
How about HighCyl=11000 when other CD ROM mountlists use HighCyl=999? I thought that the CD itself didn't change when moved from a CD ROM drive on a Warpdrive SCSI bus, to a CD ROM drive on a CyberStorm SCSI bus.
These perameters make no sense for a CDROM, and any CD filesystem worth its salt will ignore them anyway. On my mountfile they are both set to 0.
-
Hi!
I have 1 CD ROM, 1 DVD ROM and 1 CD-R connected to my CSPPC. Here is a quick cut`n`paste from my CD ROM. Try it! They are all connected to a 50 pin cable which in turn is connected to a 68 pin cable via a active terminated 68 to 50 pin adapter.
/***************************************************************/
/* CacheCDFS mountlist entry © 2000 Amiga Inc. */
/***************************************************************/
FileSystem = L:CacheCDFS /* The name of the game */
Device = "cybppc.device" /* Name of exec device driver */
Unit = 3 /* exec device unit */
Flags = 0 /* OpenDevice flags */
BlocksPerTrack = 351000 /* Unused */
BlockSize = 2048 /* True, but unused */
Mask = 0x7ffffffe /* Memory mask for direct read */
MaxTransfer = 0x1000000 /* Maximum amount of bytes for direct read */
Reserved = 0 /* Unused */
Interleave = 0 /* Unused */
LowCyl = 0 /* Unused */
HighCyl = 0 /* Unused */
Surfaces = 1 /* Unused */
Buffers = 50 /* Number of cache lines */
BufMemType = 1 /* MEMF_PUBLIC */
BootPri = 2 /* Boot priority for MountCD */
GlobVec = -1 /* Do not change! */
Mount = 1 /* Mount it immediately */
Priority = 10 /* Priority of FileSystem task */
DosType = 0x43443031 /* Currently unused */
StackSize = 3000 /* Minimum stack required is 3000! */
Control = "MD=0 LC=1 DC=8 L LV AL LFC=1 S NC AUDIO=Utilities/PlayCD"
/* The Control field is for special adjustments */
/* L/S convert all file/volume names to lowercase */
/* LV/S convert volume names to lowercase */
/* AL/S Auto-Lower converts only non-Amiga CDs */
/* LFC/N start converting at this character */
/* LC/N/A number of blocks per cache line */
/* DC/N/A number of cache lines for the data cache */
/* MD/N/A number of blocks, when starting direct read, not using */
/* the cache. 0 will be a reasonable default (LC*DC+1) */
/* S/S Do SCSI direct commands, no Trackdisk like commands! */
/* NC/S Do NOT use TD_ADDCHANGEINT, poll for DiskChange! */
/* M/S Issue a TD_MOTOR (OFF) command after read */
-
RiFF_RaFF revealed:
I have 1 CD ROM, 1 DVD ROM and 1 CD-R connected to my CSPPC. Here is a quick cut`n`paste from my CD ROM. Try it! They are all connected to a 50 pin cable which in turn is connected to a 68 pin cable via a active terminated 68 to 50 pin adapter.
;-) Thank you, sir! I'll give it a try, and let you know how it goes. Is there anything special in your CyberStorm's flash ROM settings?
-
You said you kave a MK3 ?
Is the scsi device called cybppc.device on an MK3 ?
I thought cybPPC.device would be only for PPC cards.
Cybscsi.device for the mk3 maybe ?
-
All of them is set to Auto. BTW: Doubleclick any unused units and set them to 0 LUNS to disable them. This will speed up booting considerably as the scsi controler doesn`t need to waste time to scan them!
-
@cdfr
The CS-MK3 IS a CS-PPC, just without the 604-CPU ....
(but don't try to "update" one, that won't work ;-) )
-
OK, I have got the MK1 and the Mk2. Never got a MK3.
It sounded weird that a non PPC card would have a *PPC.device
Forget my post then ;-)
-
:-? Now I'm confused about the designation. My CyberStorm has the 604e processor, running at 233 mhz, and a 68 pin SCSI III controller. Maybe that's where the "3" comes in?
-
@ Quixote,
Thomas wrote:
Then check the firmware menu (hold down Esc key during reset). Check that the SCSI bus is enabled (SCSI Patch or NCR Patch must be disabled) and check that the ID number you chose it not disabled.
I saw no mention in any of your posts that suggests that you did the above. If the ID for your device is disabled in the firmware (FlashROM settings), it will cause the symptoms you are seeing. Did you do the above that Thomas said?
-
@Quixote
You got a CS_CPP, and there is only one version of that (sort of).
The CS-MK1 is 040/060-card, consisting of several seperate moduls
(carrier, RAM, CPU and SCSI).
The CS-MK2 is the same card with everything on one pcb.
The MK3 is a pure 060/040-card based on the design of the CS_PPC with all the extras
(costum-PCI-slot for CVPPC and SCSI3).
-
Speaking of driver's....when I got my Amiga
the cd-rom wasn't working and os 3.9 wasn't installed, the network card wasn't working.
OK, I used IDEFIX to get the cd-rom drive working,
and that in turn allowed me to install OS 3.9.
However, that install was not trouble free, and
if I try to save any prefs, it says is cannot find
ENVARC:Sys/screemode.prefs
which doesn't surprise me...it's not there...how do I fix this? I see such a thing in ENV:Sys/screenmode.prefs
Also....the mediator I cannot tell for sure that it works just yet....I mean Genesis just keeps complaining that it cannot open MediatorNET.device unit 0...and thats all there is to it.
I have a very old version of the software, installed from a floppy...does it just not work? I don't have time to order a CD on the hope that might fix it...I don't even know whats wrong.
Any help you all could give would be appreciated.
-
In case I wasn't clear above...I wonder if my MediatorNET.device will work with Genesis.
Or if later version of the driver is needed.
If later versions are not available, am I just stuck?
Get another stack?
It's been so frustrating how everything doesn't work, and takes hours of trouble shooting...the first time I got the cd-rom drive working I was on top of the world...but now to only find out I cannot save any settings....
That emergency boot disk, even flubbed the CD0 device, but I was able to fix that manually....geez, I am running scared here ppl... :-)
-
SilverDrgn suggested:
I saw no mention in any of your posts that suggests that you did the above. If the ID for your device is disabled in the firmware (FlashROM settings), it will cause the symptoms you are seeing. Did you do the above that Thomas said?
Yep, I've accessed the FlashROM data, and the device numbers that I need are active. SCSI patch is not set, but I am uncertain about the NCR patch, as I didn't see anything related to it anywhere.
:-( It seems that the mounlist, filesystem, etcetera are not the problem. At one point, everything seemed to work fine in that "CD0: No disk present" would appear in the list returned by the shell's "info" command, and a DOpus lister would display all of the mounted voulmes, except for those that had no disks present, such as PC0:, MAC0: and CD0:
Once a disk is inserted in the CD ROM drive, the "info: command fails to return, though other shell commands work just fine. Also DOpus listers opened by double-clicking the disk icons work normally, but those opened by double-clicking on the desktop fail to display anything, because they're waiting on the results of the "info" command. Also, the SCSI bus slows to a crawl.
Just today, I moved the CD0 mountlist and icon to the Sys:storage/DOSdrivers drawer, but the problem detailed above still occurs. As soon as a CD is inserted in the drive, everything bogs down. As this happens without any attempt to mount CD0, it is most likely one of the firmware settings, but I've no idea which need to be changed. Currently, they're set as follows:
SCSI:
All are disabled except for ID 0 (hard drive) and 3 (CD ROM) These have everything set for "auto."
CDFS:
CD ROM Mount
No CDFS HD RDB Scan
Boot Prioroity = 3
Name = CD3
Cache Sets = 40
Cache Set Blocks = 4
System:
No MapROM
SuperScalar Off
Branch Cache Off
Write Buffer Off
;-) If I had a friendly manual to read, the answer may be obvious, but without one, I'll rely on you
guys here.
-
Do you mean you have CD-Rom enabled in Cyberstorm Early Startup screen? I've never even tried it as it was called rudimentary in some connection I think and buggy at least until the latest flash versions.
-
Hmm.. What do you get if in a shell you do a version cybppc.device?
As far as I can see your settings sounds right. The SCSIPatch can disable the A4kD (and T?) onboard IDE if the ROM is mapped.. Doesn`t work with OS3.5 and 3.9 as these do their own rom "mapping" and patching. The NCR SCSI thing is the same thing for disabling the onboard A4kT SCSI and maybe also the A3k SCSI (?) These settings are described in the flashrom updates found at www.dcecom.de, or at least they were described in earlier Phase5 flashupdates. As I run the PCI enabled flashrom here my cybppc.devive is version 44.71. The last official Phase5 update contains 44.67. There was also a unofficial release with P5 copyrights removed, this has 44.69 cybppc.device. So if your cybppc.device is less than 44.67 I would flash the CS with the flash from dcecom.. .http://www.dcecom.de/pub/ppc/FlashUpdates-300399.lha
-
;-) In a shell, "version cybppc.device" returns a value of 44.57
There is better news, now. It seems that termination was the hurdle after all. Odd, though, that the hard drive worked just fine before.
:-? Another puzzle is that the CD will now mount even without a mountlist or icon in Devs:DOSdrivers. Unfortunately, while I can now access the old Amiga Format cover CD's and PC CD's, I cannot access Mac CD's, and I used to be able to. Also, I cannot access Linux CD's Would I need to disable the CD-Rom in the CDFS portion of the FlashROM data, and use a traditional mountlist, etcetera, to mount one from the OS? That makes sense. I'll make notes regarding my current setup, and try that.
:-( Also unfortunately, I cannot boot from CD, even though the CyberStorm Early Startup is set to enable it. I guess I need a later version of cybppc.device, or maybe that feature was never perfected.
:idea: Maybe AmigaOS4.0 will permit this?
-
Quoth Quixote:
Would I need to disable the CD-Rom in the CDFS portion of the FlashROM data, and use a traditional mountlist, etcetera, to mount one from the OS? That makes sense. I'll make notes regarding my current setup, and try that.
;-) Yep. That worked. Now my A4000 can read Mac, Linux, etcetera CD's, just as it could with the WarpDrive's SCSI 1 controller.
:-( Unfortunately, now there's no way to boot from CD.
-
If you need to boot from CD you may temporarily enable the P5 CDrive from early startup but the latest flash is highly recommended as the CDrive system (or what it was called) was updated in the latest flashes.
-
Hi Quixote :-)
The cybppc.device is part of the boot rom of the cyberstorm cards (MKIII and PPC -on the MKI and MKII it was called cybscsi.device)
The best place for a CDRom type drive is the end of the scsi chain, with all harddrives before it, as all "empty" removable units will not be configured at boot time by the cybppc.device but if connected after harddrives can be "late mounted" without problems.
So, it would be wise to connect your harddrive (with it's scsi terminaison on) at the beginning of the scsi cable (connector 1), the cyberstorm scsi connector on the 68-->50 pins adaptator on the connector 2, and then the CDRom unit at the end of the chain (with terminaison on too) on connector 3. (assuming your cyberstorm is inside an A4000 Desktop supercomputer :-)
You read right, the two unit MUST BE terminated, as Phase 5 hadn't installed any terminator on the cyberstorm MKIII and PPC and an scsi chain MUST BE terminated at BOTH ENDs for proper functionning.
That's why you have to connect the haddrive (terminated) first, next the scsi controller, last any removable units (CDRom, CDR and CDRW, ZIP, JAZ, SyQuests etc...) again with the last unit fully terminated.
You must pay attention too at the 68-->50 pins adaptator you use as it MUST BE terminated on the 8 lasts lines (not used by 50 pins drives) to have a well balanced scsi chain, at least on the CyberStorms.
2/ you said your CDRom is unit 3 so you can use these mountlist with (I'm using it on my Cyb everyday, no problems ;-) :
/snip/
/***************************************************************/
/* CacheCDFS mountlist entry © 1999 Amiga Internation Inc. */
/***************************************************************/
FileSystem = L:CacheCDFS /* The name of the game */
Device = "cybppc.device" /* Name of exec device driver */
Unit = 3 /* exec device unit */
Flags = 0 /* OpenDevice flags */
BlocksPerTrack = 351000 /* Unused */
BlockSize = 2048 /* True, but unused */
Mask = 0xffffffff /* Memory mask for direct read */
MaxTransfer = 0x00ffffff /* Maximum amount of bytes for direct read */
Reserved = 0 /* Unused */
Interleave = 0 /* Unused */
LowCyl = 0 /* Unused */
HighCyl = 0 /* Unused */
Surfaces = 1 /* Unused */
Buffers = 50 /* Number of cache lines */
BufMemType = 1 /* MEMF_PUBLIC */
BootPri = 2 /* Boot priority for MountCD */
GlobVec = -1 /* Do not change! */
Mount = 1 /* Mount it immediately */
Priority = 10 /* Priority of FileSystem task */
DosType = 0x43443031 /* Currently unused */
StackSize = 16384 /* Minimum stack required is 3000! */
Control = "MD=1 LC=1 DC=8 S L LV AL LFC=1 HD=.dat HR=.rsrc AUDIO=Utilities/PlayCD RET=5"
/* The Control field is for special adjustments */
/* L/S convert all file/volume names to lowercase */
/* LV/S convert volume names to lowercase */
/* AL/S Auto-Lower converts only non-Amiga CDs */
/* LFC/N start converting at this character */
/* LC/N/A number of blocks per cache line */
/* DC/N/A number of cache lines for the data cache */
/* MD/N/A number of blocks, when starting direct read, not using */
/* the cache. 0 will be a reasonable default (LC*DC+1) */
/* S/S Do SCSI direct commands, no Trackdisk like commands! */
/* NC/S Do NOT use TD_ADDCHANGEINT, poll for DiskChange! */
/* M/S Issue a TD_MOTOR (OFF) command after read */
/snip/
Note : as the CDRom is the last on the 50 pins scsi chain you would like to set it to unit 6.
Hope this will help you :-)
Amigalement,
Jean-François.
-
;-) For what it's worth, I've gotten the setup working, so I'm mostly happy. Termination had indeed been the key. I have one bit of circuit board with connections for 68 pin SCSI, 50 pin SCSI, power, and a weird connector that resembles a card slot, in miniature, with about 80 conductors. The 50 and 68 pin connections have sockets for termination resistors, three next to the 50 pins, two near the 68 pin connector. Putting resistors into the two sockets next to the 68 pin connector did the trick.
:-? However, the rest of the setup goes contrary to normal expectations. My SCSI chain begins with the Cyberstorm controller, then to the powered terminator/adapter. A fifty conductor ribbon continues from there to the CD-ROM, which is terminated, and from there to an external connector at the rear of the A4000. From there, a cable is connected to the SCSI hard drive, which is also terminated. The whole thing works, whether the outside hard drive is hooked up, or not.
I chose to connect the CD ROM to the fifty conductor ribbon instead of using a simple adapter plug because, as many already know, there is not enough room between the rear of the CD ROM and the power supply to fit the adapter.
Hopefully, upgrading the FlashROM will permit booting from CD to work, but I wonder. When mounting the CD from ROM, the CyberStorm seems to use its own file system, and the CyberStorm file system doesn't support Mac or Linux format CD's, while later file systems available to AmigaOS do. So it's a bit of a trade-off.