Re: Boot netbsd 2.0 on RiscPC
David Brownlee <[email protected]> Sat, 26 Mar 2005 01:13:04 +0000 (GMT)
| Newsgroups | gmane.os.netbsd.ports.acorn32 |
|---|---|
| Message-ID | <[email protected]> |
On Thu, 24 Mar 2005, Peter Teichmann wrote: > Am Donnerstag, 24. März 2005 00:01 schrieb Neil Walker: >> On Wed, 23 Mar 2005, Peter Teichmann wrote: >>> * manually execute boot32, in many variants, including from the >>> supervisor prompt by pressing * while starting the computer, from a !Zap >>> taskwindow, ... >> >> On my StrongARM RiscPC, I ended up reverting to the old bootloader >> (BtNetBSD), rather than boot32. >> >> The changes to the !Run file were pretty minimal, but drop me an email if >> you want more info. >> >>> Acorn RiscPC 600 >>> Strongarm rev.K >>> 64MB RAM (2 SIMMs) >>> 2MB VRAM >>> RISC OS 4.02 >> >> I'm running RISC OS 3.70, but otherwise my machine configuration is pretty >> similar. >> >> Hope this is of help. > > Yes! That was really of help. It works without any problems. Thank you very > much! (But I would really like to know what is wrong with boot32... Is there > anyone for who it works? And what is the difference of those machines?) I'm using the 2.0 !BtNetBSD (+boot32) to boot on a 32MB Arm 710 Risc PC with RISC OS 3.60. Running InstKern works both inside the sparkive and outside. It also works with shift held down on machine boot to avoid running the RISC OS boot sequence (mode set manually to 28). So to clarify - both the 2.0 !BtNetBSD using boot32, and direct use of the 2.0 boot32 fail for you, but work with an earlier BtNetBSD? > Anyway, i tried it with several combinations of the following 6 SIMMs: > > SIMM A,B: 32MB, with 2 banks 16MB each (the original ones) > SIMM C,D: 32MB, with 2 banks 16MB each (different type) > SIMM E,F: 64MB, with 1 bank of 64MB > > Needless to say, all SIMMS were stable in the machines they were in > originally. BtNetBSD was able to boot with any combinations of them. > > Boot32 was only able to boot with SIMM C or D in any of the slots, but not > with both of them. It failed with any other combinations I tried. > > How can we explain this? That is very strange. Could you look at the messages boot32 gives (load an invalid kernel - README works quite well :) and see if they are any different between one of C/D and one of A/B? -- David/absolute -- www.NetBSD.org: No hype required --