Subject: Re: PCI G4 Troubles
From: Robert Neugebauer (rneugeba@undergrad.math.uwaterloo.ca)
Date: Sat Feb 12 2000 - 10:28:31 MST
That worked. MOL now runs fine on my machine. I did a few things in it and
it seems to be fine.
But, I could only get MOL to start under X, which is much better than no
MOL. I would prefer to run it under its own VT if that is possible. Lots
of messages and config options seem to imply that it is. Whenever I tried
to start mol, it pumped out a whole bunch of lines like the following to
my screen.
** Video mode '1152x864-75' is unavailable
For every mode in my fb.modes file. I had never even heard of this file
before, so I don't know what it does, except that mol uses it and it has
lots of video modes in it.
After rejecting every mode in that file, it says that no usable console
modes where found. If my DISPLAY variable is set it then starts MOL in X.
The output from fbset is below.
mode "name"
# D: 100.000 MHz, H: 83.893 kHz, V: 92.190 Hz
geometry 1152 870 1152 870 32
timings 10000 16 16 16 16 8 8
endmode
I am using BootX, so this is what my computer boots into.
Any ideas on this one. Thanks for the help in getting MOL running.
Bob
On Sat, 12 Feb 2000, Samuel Rydh wrote:
> On Fri, Feb 11, 2000 at 10:02:31AM -0500, Robert Neugebauer wrote:
> > My kernel is _not_ compiled with CONFIG_MODVERSIONS. I recompiled my
> > kernel with CONFIG_MODVERSIONS option, and it did not make a difference,
> > the same error occured.
> >
> > Although, when it was examining my System.map is said that the
> > Using_Versions symbol was undefined. Then it patched the kernel, said that
> > it's hooks were installed and then kernel panicked.
> >
> > I also tried MacOS 9 last night and it's rom v3.2.1, but it didn't get any
> > further.
>
> I've identified the problem. The main trouble is that there is no
> safe way to probe the kernel for the altivec support
> (depending fully upon CONFIG_ALTIVEC breaks binary compatibility).
>
> I suggest you comment out the
>
> #ifdef CONFIG_ALTIVEC
> ...
> #else
> ...
> #endif
>
> block in the kernel_module/init.c file (lines 210-220)
> and then recompile the MOL kernel module. Also make sure
> /usr/src/linux/include points to the correct kernel
> headers (or change the path in Rules.make).
This archive was generated by hypermail 2a24 : Wed Mar 01 2000 - 00:06:20 MST