Hello, I'm new to mol and have a question

[Percy Zahl]

Hi!

Thanks for the good hint, the modules compiled with the wrong header
files, which were installed by debian in /usr/include/linux|asm... I
fixed it and mol starts up fine with my OS 9.2 in a X box!

But the Alti Vec is still disabled.

Here the cpuinfo of my PBG4:
$ cat /proc/cpuinfo 
cpu             : 7410, altivec supported
temperature     : 12 C (uncalibrated)
clock           : 400MHz
revision        : 17.3 (pvr 800c 1103)
bogomips        : 797.90
machine         : PowerBook3,2
motherboard     : PowerBook3,2 MacRISC2 MacRISC Power Macintosh
detected as     : 71 (PowerBook Titanium)
pmac flags      : 00000003
L2 cache        : 1024K unified
memory          : 384MB
pmac-generation : NewWorld

I've an additional question, can I mount a HFS partition with linux
and use it at the same time with mol -- would be handy, but I'm afraid
this will make some trouble... How do you move data "on the fly"?

Thanks again,

Percy

  .^.     my home:  http://www.mines.edu/~pzahl
  /V\     my Project:
 //G\\    Visit Gxsm now! Unlimited and free SPM+ software:
/(xsm)\        ----->  http://gxsm.sf.net  <------
 ^^-^^

samuel@ibrium.se writes:
 > On Fri, May 03, 2002 at 12:43:16AM -0600, Percy Zahl wrote:
 > > I've installed MOL on my PBG4 running Debian/Woody and the 2.4.19-pre7
 > > kernel.
 > > 
 > > Mol starts end exits like this:
 > > 
 > > Debugger nub disabled
 > > The session save/restore feature is disabled
 > ... 
 > > Loading 'System Folder:Mac OS ROM' from /dev/hda5
 > > 
 > > Mapping GC at 80800000
 > > RVEC Internal Error 700
 > > exiting...
 > > cleaning up...
 > > Terminating threads...
 > > DONE
 > > 
 > > I've two questions:
 > > 1) RVEC Internal Error 700
 > >    exiting...
 > >    
 > >    What does this mean and how to get it fixed?
 > 
 > Your MOL kernel module is alsmost certainly compiled against
 > 2.4.19 instead of 2.4.19-pre7. I get this error with the
 > 2.4.19-pre6 kernel when I load a mol module compiled
 > against 2.4.19. I guess I should add a version
 > incompatible barrier in order to refuse to load the
 > module in the first place...
 > 
 > > 2) AltiVec unavailable or disabled by user - reverting to G3 mode
 > > 
 > >    My kernel has AltiVec Support enabled... and I have the line 
 > > 
 > > disable_altivec:        no
 > > 
 > >    in my /etc/molrc
 > 
 > Hmm. MOL might not know the ID of newer PowerPC chips.
 > What does "cat /proc/cpuinfo" say?
 > 
 > Cheers,
 > 
 > /Samuel
 >