You will not be able to post if you are still using Microsoft email addresses such as Hotmail etc
See here for more information viewtopic.php?f=20&t=7296
DO NOT USE MOBILE / CGNAT DEVICES WHERE THE IP CHANGES CONSTANTLY!
At this time, it is unfortunately not possible to whitelist users when your IP changes constantly.
You may inadvertently get banned because a previous attack may have used the IP you are now on.
So I suggest people only use fixed IP address devices until I can think of a solution for this problem!
alenppc wrote: 16 Dec 2018 23:11
Now it doesn't boot with any full 68030 (grey screen, tried two of them) but boots fine with EC030. Could it be something related to the MMU?
Not likely. I have the opposite issue anyways. The MMU CPUs work and the ones without them dont. I'll figure it out eventually. just strange.
The original pre_alpha firmware doesnt work?
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
It seems they all work fine with the EC ones only for the moment. The gold CPU works on and off randomly.
EDIT: The gold full cpu now booted with the firmware you just sent me but reports no fast ram. I put back the plastic EC one and it works fine, including ram. Very odd..
Could everyone close the MMUDIS jumper and see if that makes a diff. Just want to eliminate the MMU from enquiries.
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
You do not have the required permissions to view the files attached to this post.
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
Its possible I screwed up the mmudis circuit. I’ll check later
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
Supaduper, that's a software issue. The CPU command cannot distinguish between EC030 and regular 030. So if you issue a CPU FASTROM on an EC030, the command will then report "68030 FASTROM" when queried, but you won't get the desired effect. For example, do a speed test on the IDE. Sysinfo will report about 2 mb/sec without fastrom and over 6.5 mb/sec with fastrom, and the entire system will be a lot more responsive if the fastrom actually works. There will be no change on an EC030.
I don't know how good Sysinfo is at distinguishing between the two CPUs, it could be the same as the CPU command.
alenppc wrote: 17 Dec 2018 16:22
Supaduper, that's a software issue. The CPU command cannot distinguish between EC030 and regular 030. So if you issue a CPU FASTROM on an EC030, the command will then report "68030 FASTROM" when queried, but you won't get the desired effect. For example, do a speed test on the IDE. Sysinfo will report about 2 mb/sec without fastrom and over 6.5 mb/sec with fastrom, and the entire system will be a lot more responsive if the fastrom actually works. There will be no change on an EC030.
I don't know how good Sysinfo is at distinguishing between the two CPUs, it could be the same as the CPU command.
Cheers Alen
Ok so I left the MMUDIS open(two pins furthest away from the TF330 connector) and did a` cpu fastrom` command and the did a `Drive speed` test in sysinfo on my DH0: part and the speed increase was there.
Then I did the same as above with the Jumper closed and the speed of the drive did not increase so the MMUDIS is working :)
