Deneb install

[Ianoakley]

When installing Poseidon I requested that it be available at boot up and has added the following to my user start up
;BEGIN Poseidon
ENVARC:PsdStackloader
;END Posieidon

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 ?

[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.

[bash64]

Hello,

My DENEB is working fine.
Stack and all.
I have:
A2000 brand new (no, I am not joking).
A2630 030/25
6mb fast 2mb chip
gvp HC+8 with 2mb active.
gvp video card
4GB boot drive.
OS 3.9.

I added a 160GB SATA drive.
I launched HDToolbox and found the drive using usbscsi.device.
It said it was a 149GB drive.
I INSTALLED it.
I partitioned it but got only 7.2GB.
I turned on 'Fix Capacity' and got 50.2GB.
I get no icon on the desktop.
The drive is available through dos as WHD0:
I cannot complete a format.

I am using a usb -> SATA/IDE2.5/IDE3.5 adapter.
The adapter has a limit for 400GB.
The drive is powered using a 5 1/4" Amiga PS connector.

What do I do to get the full 149GB?

[Darrin]

platon42 wrote:

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.

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.

Are you aware of any problems with the Deneb and the Cybervision 643D?  Before I left home I had them both in the A4000 (along with the Fast ATA4000) and the Deneb was working fine and the CV643D card showed up on the early boot, but whenever I tried to install the CV4 drivers I would get an error on installer and the machine would reboot.  I didn't have time to investigate it any further or to try installing Picasso64 instead.

[Darrin]

bash64 wrote:

What do I do to get the full 149GB?

If it is a second HD then how about partitioning and formatting it as a PC FAT drive?  The Deneb folder has the installer for the FAT98 file system, but I've never played with a drive that big from the Amiga side.

[Ianoakley]

@Platon42

Thank you for this advice. I assume therfore that having PsdStackloader in the start up sequence therefore serves no purpose if the Deneb remains offline.

As far as configuring Trident is concerned I have tried everything but whatever I do the save button remians greyed out. Any reason why I cannot save the prefs ? For information I have selected the Deneb USB device and then gone online. Connected USB devices then work.

Finally if we overcome this hurdle will that mean the USB devices will be available without maually configuring Trident each time I start my Amiga.

[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).

[bash64]

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.


Ok, well,...

I am using OS 3.9.
I opened HDToolBox.
I selected the usbscsi.device.
I selected the WD160GB drive (149GB).
(I know that it will come up as 149GB since all of the hard drive producers are liars about their drive sizes nowadays.)

I select INSTALL and it reads the configuration as a 7.2GB drive.
I select partition and it creates 7 partitions.
I reselect for 1 partition.
It creates one 7.2GB partition.

The partitioning tool believes the drive to be a 7.2GB drive based on the info read by the READ CONFIGURATION button.

Oh, and yes, I did a QUICK format only, but it got an error.

My understanding is that OS 3.9 breaks the 4GB barrier.
Somehow it cannot read the dimensions of the drive correctly.
I am using the FastFileSystem that came with OS 3.9.

What is SFS?
Is this a safe filesystem to use?
Don't want to end up with trashed files.
I was planning on making this my boot drive.
I will try to get that info to you soon.
I am just now plugging in the usb netgear ethernet card to get online with Miami.

[Darrin]

platon42 wrote:
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.

Ah, it must be me then.  It just seems to have trouble detecting the memory stick for the first time and then after that it's happy to accept any device and correctly mounts and dismounts them on the fly (DVD drive and various hard drives connected to a IDE/SATA-to-USB adapter are all I've tested).

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).

Ah, thanks for that info.  I'll see if I can track down an email for Michael and drop him a line.  I can live without the CV643D, but it would be nice to have it working.

Cheers.

[bash64]

After removing the Fix Capacity checkmark and formatting as a 7.2GB drive the drive now works.
I am copying to it just fine.
The speed is not half bad.
I will use sysinfo to test it against my 4gb scsi drive.

I hope you got all of my emails.
I sent you debug logs and screenshots.

Sincerely, Roger.