Deneb install

[platon42]

Ianoakley wrote:

However Poseidon does not start at boot up and I have to run Poseidon manually before I can use any USB device. Is there a stage I missed after installing my Deneb and the Poseidon stack ?

There is a glitch in the installer routine. If you boot with the  Deneb  in
Rescue  mode,  it  will  place  the  Deneb itself in Zorro II mode for best
compatiblity. If you now run the  installer,  it  will  always  generate  a
PsdStackloader  with  the  denebz2usb.device  for Zorro II and not with the
denebpiousb.device for Zorro III operation.

If you remove the jumper for normal operation and have a Zorro III machine,
the  Z2-Device  driver  won't be working and the Deneb stays offline -- you
have to open Trident and configure the right device  and  save  the  prefs.
That should do the trick (if this is the problem in your case). I apologise
for the inconveniences.

Best regards and enjoy your Deneb board.

[platon42]

I added a 160GB SATA drive.
I launched HDToolbox and found the drive using usbscsi.device.
It said it was a 149GB drive.

Well, that 149 GB looks good enough for me.

I INSTALLED it.
I partitioned it but got only 7.2GB.

What do you mean by you only got 7.2 GB? What size did you specify for the partition? What filesystem did you use, what blocksize? I think SFS has a limitation for 128 GB per partition on 512 byte blocks, but I might be wrong there.

I turned on 'Fix Capacity' and got 50.2GB.

Fix capacity only changes the total number of blocks returned by (faulty) device firmwares by 1 block. So this cannot be an effect of Fix capacity.

I get no icon on the desktop.
The drive is available through dos as WHD0:
I cannot complete a format.

Be sure to NEVER do a full format but only a quick format for any partitions.

Please send in a full bug report of the PsdErrorlog and PsdDevlister with Debug enabled in the mass storage settings.

[platon42]

Darrin wrote:
Ah, is that why it seems to have a hard time detecting devices after a clean install on my A4000?  I always had to click around, open trident, restart it, etc and then after a reboot or two it would then work perfectly.

It's not about detecting USB devices, but about activating the USB hardware driver *at all*. If you have correctly added the right device, there shouldn't be these kind of problems.

Are you aware of any problems with the Deneb and the Cybervision 643D?  

Yes. The CV64/3D has problems with quick timing the Deneb uses (though they are all within the Zorro specifications) and causes bus errors for memory accesses which are not meant for the CV64/3D at all. This at least affects the DMA mode. Michael Böhmer has an experimental firmware upgrade available to fix this (please contact him).