[Date Prev] [Date Next] [Thread Prev] [Thread Next] Date Index Thread Index Search archive:
Date:Thu Jan 26 17:42:21 2006 
Subject:pop-forum Why does poplog work on a locally compiled new kernel but not a pre-built one 
From:Aaron Sloman 
Volume-ID: 

I have mentioned previously that poplog will not run, and cannot be
linked on recent versions of linux -- e.g. I could not run it when
I temporarily installed fedora core 4, and when I installed a new
kernel with number above 2.6.11-1.27

The symptom is that I can run basepop11, and then compile arbitrary
pop11 code and run it, but if I try to run pop11, or xved, or anything
else that requires starting basepop11 together with a saved image I
get a 'segmentation fault', though I recently found that it was random:
i.e. I usually get the fault but not always. I cannot imagine what
there might be about starting up a saved image that would randomly
fail.

I had assumed that this had something to do with a change in the kernel
between 2.6.11 and 2.6.12.

But now I have discovered that it isn't so. If, instead of installing a
pre-built kernel, I fetch the sources, and compile them myself, and
install, using the default kernel compilation instructions, then poplog
works perfectly, whether it is on my laptop where I have installed the
very latest stable kernel 2.6.15.1 or on my desktop machine, both of
which still have fedora core 3, apart from the kernel.

So if it's not a problem of incompatibility with new kernels what could
it be. I had thought it might have something to do with a change to
gcc4, but on reflection that doesn't sound right, since when I install a
pre-built kernel I am not installing gcc4 on my machine.

I have not found anything else that worked in fedora core 3 that stopped
working after I installed a pre-built kernel.

I did have a problem with my Intel ipw2200 wireless card on the laptop,
for which the driver is included with the latest kernel, requiring the
latest firmware from Intel). The problem arises only with use of
wpa_supplicant, but that does not depend on whether it is a pre-built
kernel or one I have compiled, so I assume it cannot be related to
the poplog problem.

Any ideas?

I still have not found time to upgrade the sources so that they all work
without varargs. (I was going to start from Waldek's amd64 poplog port,
and move things into the 32bit poplog: but for that I need to know which
of the 64bit sources were changed because of varargs and which are 64bit
specific, so it will take me some time to work laboriously through lots
of diff files).

Any volunteers?

Aaron
http://www.cs.bham.ac.uk/~axs/