Welcome, Guest. Please login or register.
Amiga Kit Amiga Store Iridium Banner AMIStore App Store A1200/A600 4xIDE Interface

AuthorTopic: DKB 2632 won't start in OS 3.9  (Read 1860 times)

0 Members and 1 Guest are viewing this topic.

Offline SpeedGeek

Re: DKB 2632 won't start in OS 3.9
« Reply #15 on: October 13, 2021, 01:43:05 PM »
Sorry to be so dense but are we talking about the 2632 resident module?  Because AFAIK that goes away on the next reboot.  The 2632 isn't autoconfig so you have to give the 2632 command on every boot.

I don't understand what you mean by "after you install the Amiga OS ROM update".  Do you mean I should now remove the NOROMUPDATE option from SetPatch?  I assume we'd just go back to the previous state where adding the 2632 causes all commands to fail with error 41.

Yes, we are talking about the 2632 resident module and no, it does not go away after the next reboot. You will have to power down (cold boot) to remove it.

The observed behavior with using the OS 3.9 ROM update was supposed to be an "Auto reboot". Hence, I saw no need to explain it any further. Now, there are 2 possibilities here:

1) 2362 command before Setpatch = resident module conflict with OS 3.9 ROM update  auto reboot

2) 2362 command after Setpatch = resident module conflict with next user reboot

So either way you still have the problem, it just a matter of when.   
« Last Edit: October 13, 2021, 04:36:09 PM by SpeedGeek »
 

Offline Michele31415

Re: DKB 2632 won't start in OS 3.9
« Reply #16 on: October 15, 2021, 07:58:56 PM »
Moving along, I replaced the BB2 AimgaOS ROM Update file (length 321768) with the original one (length 127956) and re-enabled it in startup-sequence, then cold-booted.  I also discovered the magic words "newcli aux:" and connected a serial cable form the Amiga to my Sun so now it's super easy to post output here.  I wanted to see what memory looked like before giving the 2632 command.  Right now I have
Quote
1.FS3:> showconfig
PROCESSOR:      CPU 68030/68882fpu/68030mmu
CUSTOM CHIPS:   ECS NTSC Agnus (id=$0030), ECS Denise (id=$00FC)
VERS:   Kickstart version 40.63, Exec version 40.10, Disk version 45.3
RAM:    Node type $A, Attributes $605 (FAST), at $200000-$9FFFFF (8.0 meg)
        Node type $A, Attributes $703 (CHIP), at $400-$1FFFFF (~2.0 meg)
BOARDS:
 CBM A2630 68030/RAM card:   Prod=514/81($202/$51) (@$200000 4meg Mem)
 Board + ROM (HD?) (Great Valley Products):   Prod=2017/11($7E1/$B) (@$E90000 64K)
 RAM (Great Valley Products):   Prod=2017/10($7E1/$A) (@$600000 4meg Mem)
 Board (Individual Computers):   Prod=4626/23($1212/$17) (@$EA0000 64K)
 Board (unidentified):   Prod=3643/18($E3B/$12) (@$EB0000 64K)
 Board + ROM (HD?) (unidentified):   Prod=3643/19($E3B/$13) (@$EC0000 64K)
The Prod 2017 boards are the GVP 2000.
The Prod 4626/23  board is the DKB 2632.
The Prod 3643/18 board is the x-surf.
The Prod 3643/19 is the Deneb.

I'm also not getting the two "recoverable alert" errors on booting.  Then

Quote
1.FS3:> 2632 -m0
1.FS3:> showconfig
PROCESSOR:      CPU 68030/68882fpu/68030mmu
CUSTOM CHIPS:   ECS NTSC Agnus (id=$0030), ECS Denise (id=$00FC)
VERS:   Kickstart version 40.63, Exec version 40.10, Disk version 45.3
RAM:    Node type $A, Attributes $605 (FAST), at $200000-$9FFFFF (8.0 meg)
        Node type $A, Attributes $5 (FAST), at $1000000-$7FFFFFF (112.0 meg)
        Node type $A, Attributes $703 (CHIP), at $400-$1FFFFF (~2.0 meg)
BOARDS:
 CBM A2630 68030/RAM card:   Prod=514/81($202/$51) (@$200000 4meg Mem)
 Board + ROM (HD?) (Great Valley Products):   Prod=2017/11($7E1/$B) (@$E90000 64K)
 RAM (Great Valley Products):   Prod=2017/10($7E1/$A) (@$600000 4meg Mem)
 Board (Individual Computers):   Prod=4626/23($1212/$17) (@$EA0000 64K)
 Board (unidentified):   Prod=3643/18($E3B/$12) (@$EB0000 64K)
 Board + ROM (HD?) (unidentified):   Prod=3643/19($E3B/$13) (@$EC0000 64K)
1.FS3:> avail
Type  Available    In-Use   Maximum   Largest
chip    1492352    603776   2096128   1441184
fast  121851352   3977768 125829120 117440480
total 123343704   4581544 127925248 117440480
So it looks like the 2632 RAM got added in the right place (1000000 - 7000000).  Or am I reading this wrong?

In any event I then started Poseidon, AmiTCP, AWeb 3.5, DPaintIV, two instances of Cygnus Ed, memacs, Excellence!, AmigaMail, and calculator.  They're all working, all the DOS commnads are working, I'm not getting any Error 41's and now I have:
Quote
1.FS3:> avail
Type  Available    In-Use   Maximum   Largest
chip     342784   1753344   2096128    273728
fast   67427184  58401936 125829120  67108832
total  67769968  60155280 127925248  67108832
We're now well into using the 2632 RAM and things seem stable enough.  So perhaps the 2632 can be used with OS 3.9 after all.  Unless there's some important reason not to, I'm just going to continue using the original AmigaOS ROM Update file from the 3.9 CD instead of the one from BB-2.  How say ye, oh great Gods of Amiga?
« Last Edit: October 15, 2021, 10:11:07 PM by Michele31415 »
Active: B2000 4.4, A2630, GVP 2000 HC+8, DKB 2632, SCSI2SD, Gotek, Deneb USB, XSurf 3cc, CD ROM, Megachip 2000, ECS Agnus, Denise, OS 3.9, GVP Spectrum EGS 28/24, Silicon Springs GOMF
Retired: A2088, 8-Up, A2090a, Oktagon 2008, Kitchen Sync
Busted: A2091
 

Offline Michele31415

Re: DKB 2632 won't start in OS 3.9
« Reply #17 on: November 26, 2021, 07:54:36 PM »
Well it looks like I spoke too soon.  The 2632 is back to causing Error 41's (whatever that is) on random files that work perfectly before either 2632 or addmem are invoked.  I've tried every combination of switches, tried booting different OS's, nothing helps.  So I've had it.  Adios, 2632.  I'm now considering getting a BigRAM  2630 Standard (http://wiki.icomp.de/wiki/BigRAM2630),  My 2630 is a rev. 9 so this should work.  I think.  I hope.
Active: B2000 4.4, A2630, GVP 2000 HC+8, DKB 2632, SCSI2SD, Gotek, Deneb USB, XSurf 3cc, CD ROM, Megachip 2000, ECS Agnus, Denise, OS 3.9, GVP Spectrum EGS 28/24, Silicon Springs GOMF
Retired: A2088, 8-Up, A2090a, Oktagon 2008, Kitchen Sync
Busted: A2091
 

Offline Thomas

Re: DKB 2632 won't start in OS 3.9
« Reply #18 on: November 26, 2021, 09:19:20 PM »
Error 41's (whatever that is)

41 means DMA error.

http://amigadev.elowar.com/read/ADCD_2.1/Includes_and_Autodocs_2._guide/node0043.html

This is well understandable if the HC-8+ tries to do DMA into the DKB's memory, which is not possible.

Offline Michele31415

Re: DKB 2632 won't start in OS 3.9
« Reply #19 on: November 26, 2021, 09:44:29 PM »
Oh!  So would a different SCSI controller help?  Or wou;ld I encounter the same problem if I tried the BigRAM?  So how does the 2632 ever work?  Is it limited to PIO SCSI controllers?

I see in the 2632 manual it says:

Quote
The 32Bit memory that is installed on the 2632 is configured in 32Bit
address space and considered Extended memory. This is placed above the
Amiga's normal Zorro II Auto-config space which only allows a maximum of 8
Megabytes of 16Bit fast ram expansion. With the Ram on the 2632 placed in
32Bit address space you will still be able to use the CBM bridgecards as long as
you do not have more than 6 Megabytes of 16Bit Zorro II expansion memory.
The main hardware difference between the Zorro II auto-config Ram and
the 2632 Extended Ram is that any DMA Peripherals such as SCSI controllers
that are plugged into the Zorro II expansion bus (any one of the five 100 pin
expansion connectors on the A2000 motherboard) cannot directly DMA to or
from Extended Ram. This memory is outside the 8 megabytes of address space
that is defined by the Zorro II bus specifications. The software drivers for these
type of peripherals must be able to recognize the 32Bit Ram installed in the
system in order to mask out these addresses, so that they will not try to DMA to
or from this Ram.

So does this mean I need an updated gvpscsi.device?  And what is this mask of which they speak?
« Last Edit: November 27, 2021, 08:10:13 PM by Michele31415 »
Active: B2000 4.4, A2630, GVP 2000 HC+8, DKB 2632, SCSI2SD, Gotek, Deneb USB, XSurf 3cc, CD ROM, Megachip 2000, ECS Agnus, Denise, OS 3.9, GVP Spectrum EGS 28/24, Silicon Springs GOMF
Retired: A2088, 8-Up, A2090a, Oktagon 2008, Kitchen Sync
Busted: A2091
 

Offline Thomas

Re: DKB 2632 won't start in OS 3.9
« Reply #20 on: November 27, 2021, 10:08:49 PM »
You might remember that I told you about this problem already in my very first reply: https://forum.amiga.org/index.php?topic=75365.msg853537#msg853537

In the meantime I change one of my programs to support BufMemType. It's attached to this post. Copy that lha file to your Amiga and unpack it somewhere where it can be found by the CLI, for example to the C directory of your boot partition. (remove the .zip extension, it was only added because the forum software does not allow .lha files)

It's a command line program. It takes the partition to act on and the parameters which shall be changed as argutments. If no parameters are given it just outputs the current values.

So open an Shell window and enter

changebootpri fs3:

Check the values for Mask and BufMemType.

Now enter

changebootpri fs3: mask ffffff bufmemtype 200

Repeat that step for all partitions on the HC+8.

Now reboot. It's probably a bit slower than before, because it has to copy buffers forth and back. But it should no longer throw DMA errors.
« Last Edit: November 27, 2021, 10:12:27 PM by Thomas »
 

Offline Michele31415

Re: DKB 2632 won't start in OS 3.9
« Reply #21 on: November 28, 2021, 05:27:19 PM »
You might remember that I told you about this problem already in my very first reply: https://forum.amiga.org/index.php?topic=75365.msg853537#msg853537

Ah yes, quite right - I guess I did not appreciate the significance of that at the time.  Sorry about that.


Quote
changebootpri fs3: mask ffffff bufmemtype 200

Repeat that step for all partitions on the HC+8.

Now reboot. It's probably a bit slower than before, because it has to copy buffers forth and back. But it should no longer throw DMA errors.
Uh - now it throws that error immediately during boot.  I canceled it four times and then got an empty WB screen.  I rebooted, got the same error, canceled it four times again but then this time if continued booting to my normal Spectrum display with the usual icons.  But if I do ordinary things like opening the FS3: icon, the error pops up three times.  If I cancel it each time though, it eventually continues,  I was able to say "2632 -m0" and then start Genesis and AWeb 3.5.  Genesis started OK but AWeb threw two of those errors, but then continued after I canceled them.

So this is different anyway.  Before, I wasn't able to continue at all after getting one of those errors after starting 2632.  Now I can, but I can't really use the system this way.  I used your value for mask = FFFFFF (that's six F's).

UPDATE

Now this is very odd.  I let the machine sit idle for about an hour.  When I returned, I tried a bunch of different programs - and they all worked.  In another hour of playing around I ran just about everything on the disk and they all worked fine.  I'm not getting that "FS3 has a read error" at all anymore.  I'm wondering if this could be a heat issue somewhere.
« Last Edit: November 28, 2021, 10:08:08 PM by Michele31415 »
Active: B2000 4.4, A2630, GVP 2000 HC+8, DKB 2632, SCSI2SD, Gotek, Deneb USB, XSurf 3cc, CD ROM, Megachip 2000, ECS Agnus, Denise, OS 3.9, GVP Spectrum EGS 28/24, Silicon Springs GOMF
Retired: A2088, 8-Up, A2090a, Oktagon 2008, Kitchen Sync
Busted: A2091
 

Offline Thomas

Re: DKB 2632 won't start in OS 3.9
« Reply #22 on: November 29, 2021, 02:04:12 PM »

It's rather a cold issue than a heat issue :P

Next time you get a read error please use Retry first and check if you get exactly the same error again or if the block number changes.

If you get a read error at first but on retry can read the block and fail on another one which also is successful on retry and so on, then it's probably a hardware error. Maybe a loose contect on the cable or bad termination.

Although I would have expected that the mask / bufmemtype changes would not show any difference without the DKB memory. Those changes just tell the system that if a buffer is not in 24bit memory then allocate a new buffer in that memory and copy the data across. If there is no other memory than the 24bit memory on the HC+8, there should not be any difference whether these settings are active or not.



Offline Michele31415

Re: DKB 2632 won't start in OS 3.9
« Reply #23 on: November 29, 2021, 05:35:35 PM »

It's rather a cold issue than a heat issue :P

Next time you get a read error please use Retry first and check if you get exactly the same error again or if the block number changes.

If you get a read error at first but on retry can read the block and fail on another one which also is successful on retry and so on, then it's probably a hardware error. Maybe a loose contect on the cable or bad termination.
No, I did multiple retries on each error and they all came back with the same error on the same block.
Quote
Although I would have expected that the mask / bufmemtype changes would not show any difference without the DKB memory. Those changes just tell the system that if a buffer is not in 24bit memory then allocate a new buffer in that memory and copy the data across. If there is no other memory than the 24bit memory on the HC+8, there should not be any difference whether these settings are active or not.
There's 2 MB on the HC+8, 4 MB on the 2630, and 2 MB on the Spectrum.  I got the same pattern today on a cold boot.  Four errors very early in the boot process, three more bringing up my initial WB screen, and then thre more when opening the DF3: icon, all with different block numbers.  I just cancel them all and then after that I can run "2632" from a shell and everything works normally.  I get no further errors, even when running a variety of large programs.  It's puzzling.  I don't have 2632 anywhere in my startup-sequence or user-startup.
Active: B2000 4.4, A2630, GVP 2000 HC+8, DKB 2632, SCSI2SD, Gotek, Deneb USB, XSurf 3cc, CD ROM, Megachip 2000, ECS Agnus, Denise, OS 3.9, GVP Spectrum EGS 28/24, Silicon Springs GOMF
Retired: A2088, 8-Up, A2090a, Oktagon 2008, Kitchen Sync
Busted: A2091