i'm trying to compile a custome 2.6.10 kernel, and i have a Dell Truemobile wireless pcmcia card. i know i need the pcmcia_core and ds modules (or at least these are the only ones i'm missing after comparing lsmod with my 2.4.26 kernel), but i can't figure out which options to enable in the kernel to build these modules. does anyone know?

I'm trying to do the same thing. I've looked through almost EVERY option in the 2.6.10 kernel but to no avail.

What do I need to do to get the ds.o module?

To get the pcmcia_core module select:

Bus options ---> PCCARD (PCMCIA/CardBus) support ---> [M] PCCard (PCMCIA/CardBus) support

You'll probably need the yenta_socket as well. To get that select

Bus options ---> PCCARD (PCMCIA/CardBus) support ---> [M] CardBus yenta-compatible bridge support

Anyone know where the ds.o module comes from?!

wow, thanks i'll check those options when i get home. mind if i ask what your symptoms are? you've got pcmcia_core and your wireless card modules loaded right? does cardctl info find your card?

actually... i can't bring my pcmcia slot up.

i type /etc/init.d/pcmcia start but it fails stating
cardmgr[20174]: no pcmcia driver in /proc/devices


can you even get that far?

my situation is very strange. when i boot my 2.6.10 kernel, cardmgr says no sockets found! lsmod shows only yenta_socket loaded, no orinoco, hermes, pcmcia_core, or ds modules (which are all present in my working 2.4.26 kernel). cardctl ident shows all 3 sockets empty.

after stopping rc.inet1, rc.inet2 and rc.pcmcia i started them each up again one by one. cardmgr said it was watching 3 sockets, and cardctl ident shows my truemobile 1150 in socket 3. but i can't get an IP address. i don't get any errors when i start rc.inet1 or 2, but when i iwconfig eth0 is empty, same for ifconfig. orinoco, orinoco_cs, and hermes are all loaded, as well as yenta_socket. but no pcmcia_core and no ds.

also, by using slocate, i found that i had xxxxx.ko files in /lib/modules/2.6.10/kernel/drivers/net/wireless/ for both orinoco modules, as well as hermes and yenta_socket. that's why i can insert them be running my rc.d scripts i think. my guess is that the /drivers/net/wireless is a new layout, and it can't find the path during boot. but slocate shows that the only pcmcia_core and ds modules in /lib/modules/ are in the 2.4.26 directory. i can see pcmcia_core.o and ds.o in the 2.6.10 build directory, which is in my home directory. i just don't know which options they are in menuconfig, and i don't know how to turn ds.o into ds.ko.

Silly question, but are you sure that eth0 is a wireless device? Usually eth0 is the wired portion.

2.6.x kernels create *.ko files for modules vs. 2.4.x's *.o files.

When configuring your kernel options, look for section:
PCCard (PCMCIA/CardBus) support
and read the help that comes with each option. Have you
used the new make xconfig? The window has three frames open
by default, and bottom right is the help info.

You will also probably want to enable the 'hotplug' support.

Wireless card drivers do not all create the same ethernet device name,
some use ethX, some use wlanX, some use their own unique name like
athX.

I have read the help for each item that I thought pretains to the PCMCIA slot. Nowhere did I see the hotplug support. Could you give the path to those options we should enable?

I am using the make menuconfig right now because i just started installing gentoo on my laptop and don't have the X server set up yet.

Example:

general drivers-->blah-->[M] foo

Device Drivers -> Generic Driver Options -> Hotplug blah blah

and just after Bus options -> PC Card is
PCI Hotplug, but I don't think you need that one unless you've
got Cardbus cards (which look like PCMCIA, but they're not)

HTH

i'm not home right now, so i can't try recompiling atm, but i'm curious about modules. you said 2.6.x kernels build .ko files, and 2.4.26 build .o files. but i've got lots of .o files in my /home/severian/src/linux-2.6.10/ directory (the source directory). it looks like the .o files are the original (unbuilt or something) source files for the modules. if you elect to build something as a module, it gets turned into a .ko file and moved to /lib/modules/2.6.10/xxxx. is that right?


if that IS right, is there any way to do it only for a specific module. i'm assuming these are written in c, right? so can i run

gcc pcmcia_core.o /lib/modules/2.6.10/drivers/pcmcia/pcmcia_core.ko

or something like that? is there a make file for each module so i could install them individually with ./configure, make, make install? or is the ONLY way to do it through editing the .config file and running make modules, make modules_install?

EDIT: sorry for the double post, it was an accident!

alright, i looked at my config and i have

CONFIG_PCCARD=y
CONFIG_PCMCIA=y
CONFIG CARDBUS=y

CONFIG_YENTA=m

CONFIG _PCMCIA_PROBE=y

CONFIG_HOTPLUG_PCI is not set

CONFIG_NET=y

CONFIG_PCMCIA_HERMES=m

CONFIG_NET_WIRELESS=y



none of the PCMCIA character devices are set.

There is a makefile in each directory, so I suppose it is possible to build individual _sets_ of
modules -- what is built will depend on your .config file. But I have never bothered to try to
build individual kernel modules, or at least none that are included in the kernel sources, individually.

It is so very easy, and only takes a few minutes on a recent machine to just

make modules
su
make modules_install

That said, if you don't want to build all the modules over and over while you are trying to
tweak a specific module, give it a shot in the specific directory. There might be some
clues about doing things that way in the 'Documentation' directory, I can't remember.

but the problem is that i don't know which option in config produces the ds module. i've now recompiled like 5 times, and i've managed to get all the modules i want built except for ds. and my wireless card still isn't working. cardmgr and cardctl can see the card, but dhcpcd doesn't assign me an IP address, and if i try to manually iwconfig eth0 essid xxxx it says operation not supported. so the only thing i can think of is the ds module.