Subject: Re: 'Unmapped 'RAM-read-access'
From: Erick Singley (singley@clinpharm.niaaa.nih.gov)
Date: Tue Mar 28 2000 - 15:42:09 MST
>On Mon, Mar 27, 2000 at 09:33:48PM -0500, Adam Price wrote:
> > On Mon, 27 Mar 2000, Ettouati wrote:
> >
> > > I tried to install Mac-on-linux on my Performa 6400/180 with that result:
> > >
> > > -------------------------
> > > 32MB RAM mapped at 0x20000000
> > > <ROM_FIX> 4096K ROM mapped at 0x4fc00000
> > > <Physical ROM mapping>
> > > ROM checksum = 0x150
> > <<<SNIPS-O'JOY>>
> > > Unmapped 'RAM-read-access', 08000000
> > > Unmapped 'RAM-read-access', 08000000
> > > Unmapped 'RAM-read-access', 08000000
> > > Unmapped 'RAM-read-access', 08000000
> > > Unmapped 'RAM-read-access', 08000000
> > > Unmapped 'RAM-read-access', 06000000
> > > .........
> > > ---------------------------------
> > > I used the patched kernel 2.2.15pre3 and mol-0.9.41. On the
>Mac side I have
> > > got MacOS 8.1. MacOS is on partition sda5. Is there a solution
>to solve this
> > > kind of problem ?
> >
> > I have heard it is possible to run mol with 8.1 - I tried for a long time
> > (months), and couldn't get it to work. I recommmend upgrading the macos
>
>I've got my 6400/180 running mol with macos8.1( I was scared to upgrade
>to 8.6 because of how badly 8.5 performed) Anyways, your log message
>looks very simillar to mine, execpt I use my an IDE/ATA drive. Does mol
>not run at all for you?
>
>happy hacking
>shawn a.
I think I was getting errors like this when I set my MOL RAM to an
odd number (like 102 MB) . once I reset it to a nice number like
128MB that stopped.
We've got 8.6 running on all our machines here - (2) 6100 upgraded
with a sonnet g3 card, G3 233, 7200/90, G4 400 - but that's all
G3/G4. Maybe the 6400 isn't as happy.... [kernel 2.2.15pre14 on G4
that works]
This archive was generated by hypermail 2a24 : Sun Apr 02 2000 - 21:06:30 MDT