Skip to Content.
Sympa Menu

baslinux - Re: [BL] PCMCIA support was BL3 Options Specific for Old Toshiba Laptop

baslinux AT lists.ibiblio.org

Subject: Baslinux mailing list

List archive

Chronological Thread  
  • From: sindi keesan <keesan AT sdf.lonestar.org>
  • To: baslinux AT lists.ibiblio.org
  • Subject: Re: [BL] PCMCIA support was BL3 Options Specific for Old Toshiba Laptop
  • Date: Fri, 10 Mar 2006 04:18:14 +0000 (UTC)

On Thu, 9 Mar 2006, David Moberg wrote:

Official site with source code: http://pcmcia-cs.sourceforge.net

what do I do with it,

Compile and use it.
Hopefully this will just produce the modules appropriate to the kernel pointed at by /usr/src/linux.


and do I need to configure the kernel somehow to support it?

Try to set at least the PCMCIA core modules to =M, e.g. the
drivers for various PCMCIA host controllers/sockets. You

Those five questions about PCMCIA scsi adaptors? Are PCMCIA slots scsi?

also will want to turn generic wireless networking support on.

Only if there is a real chance of getting our wireless ethernet card to work soon, or if anyone else wants that compiled in. I may eventually compile a laptop-specific kernel with pcmcia and wireless support but not sound or most scsi or some other stuff, to make it smaller since the laptops have 24-32MB RAM.

David, how did you get matroxfb.o to compile?

make modules; make modules_install

It is supposed to just work. Maybe you should try setting
matroxfb to Y instead?

You had it set to M and it compiled as a module. Do you want to try compiling with my configsy.431 with matroxfb set to Y and M?

The only change I made to your fb configuration was to add M for the
PCI voodoo card which I discovered in one of our computers and Hercules
framebuffer - how would those affect matrox?

They shouldn't affect matrox.

Maybe some bug? Can I compile just matroxfb.o, from within the /matrox directory, by linking the *.o already compiled there with reference to Makefile?

/2.4.31 at my site). For some reason vesafb.o was compiled though I
answered CONFIG_VESAFB=Y not M.

In addition to being the extension for loadable modules in Linux 2.4 and
earlier, .o is also the extension for the compiled source code files,
before they are linked together into the vmlinux and eventually z or
bzImage.

David

I have not run make modules_install, and was just picking out the modules and copying them over to a simplified set of directories under /lib/modules/2.4.31. I will remove vesafb.o (and test the kernel on a non-matrox VESA 2.0 card).

I discovered my ppp_async and/or ppp_generic don't work with your kernel.

Do 2.6 modules have some other naming system?

Does PCMCIA work differently in 2.4? There was something about yenta.

Sindi




Archive powered by MHonArc 2.6.24.

Top of Page