Hey, just to confirm what Brock already said, here's what I load upon boot
ray_cs 18368 1 ds 6120 1 [ray_cs] i82365 21340 1 pcmcia_core 48864 0 [ray_cs ds i82365] However, just to voice my experience, I can't get my wireless card to be anything but eth0 if I boot up with it in it, which required me to fix the configs to make eth1 my external interface. --Pat On Tue, 25 Dec 2001, Brock Nanson wrote: > Pete, > > When I built my (Eiger) BreezeCOM box, I loaded, in this order: > > pcmcia_core > i82365 > ds > > I'm not real sure of what each does exactly but I *think*: > > pcmcia_core is the basic pcmcia functionality > i82365 is the driver for the pcmcia chip (in my case an ISA - PCMCIA adapter > board) > ds is the actual card services to recognize a card has been inserted and > load the appropriate driver. > > This only laces your skates - it doesn't win the hockey game. There is a > directory /etc/pcmcia that has some config files for the card services. The > actual wireless card driver is in /lib/modules/pcmcia. From what I can see > (and someone can correct me if I'm wrong), the regular LRP modules file > causes the listed modules to be loaded. In the order they appear. So the > PCMCIA capability gets started, and probably a regular NIC if you have one. > But the big catch is ----- the wireless card doesn't get loaded until the > card services gets run! This is well after the modules file is read. In > other words, wireless and other PCMCIA devices don't get loaded from the > modules file. > > A side issue that comes from this is - there doesn't seem to be a simple way > to cause your PCMCIA device to be eth0... it gets loaded after the NIC in > modules, so by default becomes eth1. This means adjusting the remainder of > the config files. > > Hopefully someone will jump in and correct my mistakes! As well, note that > this is all based on Eiger - I have no idea what Dachstein does in this > regard! > > Good luck, > > Brock > > > > Message: 7 > > Date: Tue, 25 Dec 2001 20:09:06 -0800 > > From: Pete Dubler <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > > Subject: [Leaf-user] loading PCMCIA modules > > > > The saga continues... I refuse to ask a question until after I have > > spent a good 18 hours suffering and researching on my own... > > > > I am trying to get a wireless router going based on the Cisco Aironet > > 342 ISA card and the Dachstein release, combined with IDE and PCMCIA > > services, as posted by FABbnet (http://www.fabbnet.net/lrp.htm). (I > > promise to write a very explicit HOWTO about all this once I (with your > > help) get it working.) We are going to be building several of these for > > our neighborhood, so the days and days I have put into it will > > eventually pay so dividends in terms of public service... > > > > I must not be loading all of the necessary modules. Do you have any > > pointers?. > > > > I am loading: > > > > airo irq=5 io=0x340 > > airo_cs > > pcmcia_core > > > > What else, and if necesary, in what order, must I have them? > > > > I am getting the following messages at boottime: > > > > airo: Trying to configure ISA adapter at irq=5 io=0x340 > > airo: Rid ff15 has a length of -2 which is too short > > airo: bad MAC enable reason=85, rid=ff10, offset=16 > > airo: MAC could not be enabled > > ... > > airo_cs:... > > insmod: unresolved symbol register_pccard_driver > > insmod: unresolved symbol unregistered_pccard_driver > > insmod: unresolved symbol CardServices > > > > > > Looking forward to 11mbs before the new year.... > > > > Happy Holidays, > > > > Pete Dubler > > Fort Collins, CO > > > > _______________________________________________ > Leaf-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/leaf-user > _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
