Cardbus Failure "cs: warning: no high memory space available!"

Mark Fortescue mark at mtfhpc.demon.co.uk
Tue Dec 5 14:49:44 EST 2006


Hi Peter,

Thank you for your comments.

At the moment, I can't use kernels later than 2.6.16.x due to a dynamic
linker/ELF loader issue in the later kernels that prevents any executables
from running due to an address mismatch.
I would prefer to be using a Linux-2.6.18 kernel but until I have the time
to create a workaround for the above mentioned problem, I can do little
about.
This is why I was after patches, not a full kernel update.

I will upgrade to udev-104 and see if I can remove the previous udev
installations and get a clean start-up as the earlier udev-031 and udev-103
start-up systems appear to be competing with one another. The udev
documentation has (from my point of view) a lot to be desired so my hand
crafted start-up is far from ideal. I do not believe it is an issue in this
case, as pcmcia-socket-startup has no observable effect.

I will get a 2.6.19 kernel and have a look at the differences. Maybe I can
generate a patch that fixes things for the 2.6.16 kernel that will allow me
to continue without a complete system re-build of all application
code/libraries.

Regards
	Mark Fortescue.

-----Original Message-----
From: linux-pcmcia-bounces at lists.infradead.org
[mailto:linux-pcmcia-bounces at lists.infradead.org]On Behalf Of Peter Stuge
Sent: Tuesday, December 05, 2006 6:50 PM
To: linux-pcmcia at lists.infradead.org
Subject: Re: Cardbus Failure "cs: warning: no high memory space available!"

On Tue, Dec 05, 2006 at 04:35:00PM -0000, Mark Fortescue wrote:
> I am using a generic Linux-2.6.16.29 kernel

Ouch, that's a bit old.


> 1) What (if any) patches need to be applied to the kernel and where
> can I get them.

I would suggest a fresh 2.6.19 kernel from ftp.<country>.kernel.org.


> 2) What (if any) special configuration options do I need to set
> (build time and/or kernel command line). My current kernel is
> mostly not modular.

Mine too. You'll need Yenta and either PCMCIA IDE or PCMCIA PATA
support, or possibly both of the latter. I've started to use the
experimental PCMCIA PATA code with success.


> 3) What additional pieces of software do I need (including version
> numbers and patches as there appears to be a great deal of
> incompatibility between different versions of tools like UDEV).

Updating from udev-084/087 to udev-104 made hotplugging work on a
system I worked on yesterday. With the older udev I had to run
pcmcia-socket-startup manually to get the socket going.


Generally, try the latest version of both kernel and udev and see if
it works better. There have been a lot of changes lately, all for the
better. :)


//Peter

_______________________________________________
Linux PCMCIA reimplementation list
http://lists.infradead.org/mailman/listinfo/linux-pcmcia




More information about the linux-pcmcia mailing list